Hello I am really happy to have ordered an IR Toy rather than an IR Widget. I live in a country (France) which recently elected a left-wing extremist (well, almost...). I would have been charged a maximum :) Happy New Year to all.
Hello With USBIRToy_irW.hex (IRWidget emulation firmware) flashed in the IR Toy I could decode (with IRScope, via DecodeIR.dll) correctly the codes from 9 different remotes. My test is not very comprehensive, as all my remotes use only 3 protocols : NEC1, NEC2, and Sony15. But at least for those protocols, it works. The only problem I had was with a volume control (repeat code) which was decoded as two codes (NEC2 and unknown) if I pressed the button for a long time. It was enough to press for a short time to get a correct decoding (NEC1 protocol). So AFAIK, IRScope + IR Toy is a good solution for me. My only wish would be for a simpler way to switch back the Toy to its "standard" modes. My previous post was about using the irbin2ict.pl.txt script to convert .bin files produced by the IR Toy (in IR Sampling mode) to .ict files used by IRScope. As I said, it didnt't work, but it's probably because of inaccuracies of the IR Sampling mode, rather than the script itself.
Pio I tried this script on the test.bin file produced by the IR Toy in IR sampling mode (via the command "irtoy.exe -d COM9 -r -f test", after sending 0x00 'S' to put it in IR sampling). The script works correctly (at least I suppose) and creates a test.ict file. But decoding this file with IRScope (via DecodeIR.dll) does not give reliable results. For instance, with a remote using NEC1 protocol, IRScope said "protocol NECx" (meaning "can't determine if NEC1,NEC2,NECx1 or NECx2"). The device number was correctly found, but generally not the OBC numbers. I suppose the problem is that, in IR sampling mode, the IR Toy uses the IR demodulator, which doesn't report accurately the "on" periods. So, for the time being, I think the good way to decode IR signals with the IR Toy is to flash USBIRToy_irW.hex.
KamalS Yes I could flash USBIRToy-irW.hex in the IR Toy via USB, using the commands "Bootloader.exe" and then "fw_update -e -w -v -m flash -vid 0x04D8 -pid 0xFD0B -ix USBIRToy_irW.hex"
But, when I wanted to revert to the original firmware with the commands "Bootloader.exe" and "fw_update -e -w -v -m flash -vid 0x04D8 -pid 0xFD0B -ix USBIRToy.v22.hex" Bootloader.exe didn't work
After shorting PGC/PGD, I could run "fw_update -e -w -v -m flash -vid 0x04D8 -pid 0xFD0B -ix USBIRToy.v22.hex" and the original firmware was correctly flashed
So, no need for a PIC programmer, just a jumper to revert to original firmware
Shame on me, I didn't read the doc to the end ... To flah again the original firmware, no need to use a PIC programmer, it's enough to short PGC/PGD. I tried this, and the USBIRToy.v22.hex was correctly flashed. I suppose this is obvious for a PIC geek, but I am more familiar with Freescale microcontrollers... So, although somewhat laboriously, I can switch between IRScope mode and the standard ones
In my (very slight) experience: - when I received my IR Toy : bootloader.exe was able to activate the bootloader - after flahing USBIRToy.v22.hex : bootloader.exe was still able to activate the bootloader - after flahing USBIRToy_irW.hex : bootloader.exe was no longer able to activate the bootloader, I had to short PGC/PGD
So the commutation between IRScope mode and other modes is possible, although somewhat laborious...
My IR Toy (which I received three days ago) had an older firmware version. So I first updated it with the v22 via the bat file update-USBIRToy.v22.bat which came with the firmware distribution. I didn't try v23, as it seems there are problems with it. Noting that the updated IR Toy didn't work with IRScope (normal as IRScope waits for one sample each 100µs, and IRToy sends only the durations of on and off states, and off durations are flawed by the IR demodulator), I browsed the forum and found the info from JTR with the reference to USBIRToy-irW.hex. I tried it, and everything worked fine, as I said.
Now, I recklessly said it was enough to re-update the Toy with USBIRToy.v22.hex via USB to come back to the original behaviour ! I have been trying it, and nothing happens. I suppose the USBIRToy-irW.hex doesn't contain the bootloader, so now my IRToy is unable to update via USB. For me it's not very annoying, as I bought the IR Toy to work with IRScope and replace the IR Widget which was unavailable at the time. I suppose it's always possible to reload the original firmware with a PIC programmer. If I have time I'll try this. Naturally, the best solution would be to have an "IRScope mode", but it should be the default mode, as IRScope doesn't speak to IR Toy, and I understand this can create problems for the "standard" IR Toy users.
Hello, I downloaded USBIRToy-irW.hex to use the IR Toy with IRScope, and everything worked fine. see viewtopic.php?f=29&t=4838&p=47175#p47175 Thanks to JTR for his good job
As nobody replies, I reply myself ... best way to be sure to get an answer ! I finally baught the Infrared Toy, hoping it would work with IR Scope. As it came, it didn't, but after loading the firmware USBIRToy-irW.hex (found at viewtopic.php?f=29&t=2554&p=30056&hilit=irscope#p30056) via USB, everything worked fine. I could capture IR signals and decode them to Pronto format. Many thanks to JTR, he did a good job. Now I have a wish : every time I want to use the IR Toy to send signals, I must reload the "standard" firmware to have it respond to anything but IRScope. Well, via USB the updating is fast, but it would be fine if IRScope mode was resident in EEprom with the other modes. After reading the thread I understand that IRScope is anaware of the IR Toy and so cannot itself set the good mode, but there was a proposal to make IRScope the default mode, which could be changed by the other applications speaking to the IR Toy. Do you have any information concerning the future relations between IRScope and IR Toy ?
Hello After reading the pages about the Infrared Toy and browsing the forum, I can't figure out if and how the Toy works with IRScope. It seems possible to load a firmware which allows this, but : - is the firmware loadable via USB or does it need a PIC programmer ? - once this firmware is loaded, do we have access to the other modes (IRMan, IR sampling, SUMP, ...) ? I work with IRScope as I have to deal with codes in Pronto Hex format. The IR Widget, usual companion of IRScope is for now unavailable, and before buying the Infrared Toy I would be sure I can use it ! Thanks in advance.
