Eventghost. It's a great free automation and remote host software on windows. Pretty lightweight and hosts python plug-ins. It speaks LIRC and HID and some other more wacky serial remote/device dialects. I use EG for more and more as time goes by.
I already have an IRtrans unit so prolly won't get a USB IR toy unless you do some really out there stuff with it. The IRtrans unit does way more than I ask of it as it is. It's a pretty polished lil IR unit.
I'm pretty sure I tried that amongst a few other things. Bascially what I found is that Python on windows does not like the select.select call. From what I read on forums I might have to find another mechanism to replace that call to get this script working, on windows.
When I get home today I'm going to try that line again just in case I messed something else up when I tried it the first time.
Controlling the BlinkM and Rainbowduino via i2c worked just fine using the BP terminal interface. So now I am keen to get python sending i2c commands.
I don't know much about serial comms at the momment so I had a question.
Because there isn't anything in brackets does this mean you are using the select call just for timing - not actually for waiting?
I put something in the brackets based on something I read in another thread and didn't get the error anymore but I did fail to connect so it prolly messed up the timing part?
I am keen to use python to drive a Rainbowduino with I2C and a few BlinkMs too.
I was surprised to see voltage set onto the Vpu pin powering the board when I disconnected the bus pirate from my USB port. Is this meant to happen. I've only just started playing with the BP tonight and thought it was strange. I'm putting 5V on the Vpu pin.
