Thanks for trying it out!  Your instinct was correct, the import easygui line was a left over from another program I haven't posted yet, and isn't needed.  I've reposted the code without it. 

As for the other error, I'm not sure what the problem is.  Try to run python from the python interactive shell or IDE (either IDLE or PythonWin), and after you get the error, type sn and then return, and token and then return.   Your serial number and token should be printed out.  If not, let me know what you get instead.  That should help me debug it. 

Are you running Windows, Mac, or Linux?  That may also help me out.

P.S.: If you get the right serial number and token, except the last digit is missing on each, delete the [:-1] from the lines that say
sn=data[0][:-1] 
token=data[1][:-1]

and try that. 

Let me know what happens in any case!

Last edited by ViennaMike (2007-11-28 03:59:29)

Just noticed something about the ear sensor script. It seems that even when the rabbits ears haven't changed position, the tss is still sent. If I run it in IDLE (which seems the only way for me to get it to run for some reason, if I use python launcher nothing seems to happen for me), the python shell log thing reports something like
"http://api.nabaztag.com/vl/FR/api.jsp?token=(my token)&sn=(my serial)&key=&ears=ok
<?xml version="1.0" encoding="UTF-8"?><rsp><message>POSITIONEAR</message><leftposition>5</leftposition><rightposition>14</rightposition></rsp>"
then it sends a tts to the api via the api url. When I run it again without changing the ear position, I get exactly the same thing
"http://api.nabaztag.com/vl/FR/api.jsp?token=(my token)&sn=(my serial number)&key=&ears=ok
<?xml version="1.0" encoding="UTF-8"?><rsp><message>POSITIONEAR</message><leftposition>5</leftposition><rightposition>14</rightposition></rsp>"
and yet it still then calls the api with the tss (sorry if I'm getting the terminology wrong, hope you can understand what I mean).
Not that I know about python at all, but it seems to me that it's not reporting the oldearposition file properly, or if it is, the tts is getting sent anyway.
Am I doing something wrong ?

Also, I've been trying to figure out how to send messages to a different rabbit if I move my rabbits ears. I have figured that changing the serial and token to that of a different bunny in the wxBunnyFile won't work because the program will be looking for THAT bunny's ear position, not mine, am I right ? I'm guessing some in depth code editing would need to be done to be able to do this !

Last edited by rachaelnex (2007-11-30 12:52:59)

Thanks for your reply. This is all new to me as I said so - thanks for bearing with me.

I inserted the line as you said. The shell reported "old ear positions:  /u0 /u0", and sent both the tts messages (I changed my version of the code to say two messages rather than an mp3, one for each ear, as I can't figure out how to find the id number of my mp3s on the nab site since they changed it from being part of the url).
So I changed the ear position on the bunny and ran it again. Again it reported "old ear positions:  /u0 /u0". And sent the messages.
So I did it without changing ears this time and it reported the same ear position "/u0 /u0" and yet still the tts got sent to the api.

Any ideas ?

I put the otherNab code bits in and it sends the messages to my bf's bunny now, but still always despite the ear positions being reported as /u0 /u0.
As it goes, if I try to open the oldearposition file in text edit (just to see what it says) it's blank. It is supposed to be blank ?

For Python programmers, I've significantly expanded the Nabaztag.py code written over at the Nabazlib project, so that it now supports all the capabilities of the Nabaztag API, including the ability to combine several commands into a single call.  It's available at http://www.mcgurrin.com/nabaztag/.

I'm still trying to figure out the problem.  Back when you ran the original program, I assume you ran it multiple times in a row, and still got the same problem?  Is that correct?  It seems like there's a problem in the pickle file (where it stores the ear positions between executions of the program), but with the original program, even if the original file was corrupted, it should default to oldpositions of 0 and 0, run once, send the messages, and then store the new positions in a valid file.  So when it runs again, it should have a good file to work from. 

We might want to take the debugging discussion off-line.  You can email me via the link on this thread, or to the email address on my website.

Tried out this Python based control panel as my first one.  got the python from python.org (win64 amd64 version) loaded it and the py and p files from viennamike here and it worked like a charm.

My plan now is to take a copy of this stuff to my computer at work so from there I can send ear messages back home for stuff like "im running late" or "be home at the usual time" etc.

I think this is going to be fun.

Thanks for creating the app!

You don't need to open a shell at all.  If you have Python on your machine, and have it set up to associate .py files with Python (which usually occurs automatically when you install Python), just unzip all the files into the same directory and then double-click the NabaztagGUI.py file, and it should run. 

The first time, you'll need to select "Add Bunny" and input your bunny's name, serial number, and token.  Then select "Select Bunny" and select the bunny by the name you just entered.  After the first time, you just need to Select Bunny upon startup, because the information you put in the 1st time is stored on the PC. 

If you want to monitor whats happening as it runs, open IDLE or PythonWin Editor (if you have it), and then open the NabaztagGUI.py file in IDLE or PythonWin and then run it.  But this is only really needed if you're debugging, modifying the code, or just curious.