IR Toy transmit errors, can't get version

Topic: IR Toy transmit errors, can't get version (Read 1805 times) previous topic - next topic

IR Toy transmit errors, can't get version

October 14, 2010, 02:28:51 pm

Quote

Hi,

I've just received the IR toy I bought from seedstudio. I'm trying to check if it's working properly but is being difficult. I would like to get some guidance on this.

Apparently I can receive IR data, but I can't transmit anything.

I started for checking the firmware version, which gave me a strange answer, 0x76 0x40 0x00 0x00 0x00 0x00.

I tried to resend data using the IRIO mode with 8bit format; I've just cloned the information from an original RC5 remote control. The TV didn't react. I tried to check if there is any IR transmission with an digital camera but without success.

I also tried to run the self test, but the device didn't react at all.

Another intriguing question is with the USB IR toy plugin: EventGhost is giving two message errors "Error starting plugin: USB Infrared Toy" and "Initialisation failed!"

For the time being I just want to verify if the hardware is all working properly, can you help me with this?

Hi - I'm sorry you're having problems with the IR Toy, thanks for the report.

First, have you upgraded the firmware? The last batch of IR Toys was manufactured before the recent upgrades that added the mode used by WinLIRC and the EventGhost plugin. Please upgrade to firmware v08 if you haven't already:
http://dangerousprototypes.com/docs/USB ... y#Firmware

The transmitting distance on an unmodified IR Toy is pretty short. Resistor R4 can be as little as 18ohms for maximum range. If you send it to me, I am happy to make this modification for you (or send you parts if you are able to do it yourself).

Can you please post the terminal output or a screenshot of your interacting with the device? That might help debug the problem. The version and self-test are only available from the default RC5 decoder mode. Send 0x00 to make sure you're in IRman mode (should respond OK to 'r').

When retransmitting the 8bit data format in IRIO mode, you must first switch to 8bit output mode. I recommend the new IR sample mode, it does the same thing but is much less bandwidth-intensive and timing sensitive:
http://dangerousprototypes.com/docs/USB ... _protocols

Re: IR Toy transmit errors, can't get version

Reply #1 – October 15, 2010, 01:16:07 am

Hi

"EventGhost is giving two message errors "Error starting plugin: USB Infrared Toy" and "Initialisation failed!""

I have seen the same error when the IR Toy plugin is not configured to match the USB com port.

To do this, double click on the plugin (under the Auostart branch), then set the com port to match.

I have been trying unsuccessfully to get this plugin to transmit. The developer has flagged that the transmit is an area for improvement and also that it has not been tested. My stumbling into the code suggests that it is not complete and does not yet work. I am slowly looking into this - just being delayed by blue screening /dead computer.....

Also a **key** thing to watch is whether the on board LED light flashes. This occurs if the IR Toy is transmitting or receiving. So if this LED is not flashing, NO IR data is being sent.

Re: IR Toy transmit errors, can't get version

Reply #2 – October 15, 2010, 11:14:06 am

I fixed the bugs in winlircs transmit code. Sending from the program itself worked fine, but externally it was pure luck if it worked on not. Essentially the transmit string, the null terminator for the string got lost so whether it worked, or crashed .. anybodies guess.

Re: IR Toy transmit errors, can't get version

Reply #3 – October 16, 2010, 06:19:34 pm

Hi Ian,

Your suggestion has worked, I have upgraded the firmware, now it's working fine.

The distance is quite short, but I can change the resistor.

Thanks

Re: IR Toy transmit errors, can't get version

Reply #4 – October 16, 2010, 06:56:37 pm

Thanks for the update matarab, I'm glad you got it going. Please let me know if there's anything else you need.