I found in irWidget.c the reason why this mode gave erroneous output viewtopic.php?f=29&t=2554&start=45#p53025 and viewtopic.php?f=29&t=2554&start=45#p53026
if (SendCDC_In_ArmNext(irW.RXsamples)) irW.RXsamples = 0;
Widget mode in V22 and V23 are both erroneous. Would a version based on the actual V23 once become the next version? If so are theactual V23 sources available somewhere?
Is there a short description how to compile & link a firmware version? Is the MinGW Shell appropriate?
I tried to fw-update the IRT with USBIRToy_irW.hex. It failed. I tried to re-flash the IRT with V22 (PGC/PGD shorted), it fails too. The following shows the fw-update dialog:
Enter Com Port Number 15 Once the device has entered boot loader mode Press any key to continue . . . U2IO flash erasing: FAILED. Device is not found. Operation aborted. Press any key to continue . . .
When connected to the host USB, the LED on the IRT remains on...
So I installed USBPcap 1.0.0.4 in combination with Wireshark, open USB tracing tool and tried to fw-update once more. Wireshark tells the host receives Malformed Packets. Most likely, because of this the host is unable to Flash even with PGC/PGD shorted, and could explain why the host did not proceed or refuses to associate a COM port to the IRT as encountered last time (see previous message).
This situation is critical as my IRT seems dead. Help!
I was sending some bytes with RealTerm. As usual, when no response came any more (e.g. Widget Mode) I disconnect the IRT from its USB connection and reconnect the IRT.
Although at reconnection the PC (WinXP) gave the dong-ding reconnect sound, the COM port had disappeared. The Led of the IRT remains on. I did it several times with the same result.
I went to a previous XP restore-point, and my COM port of that time also didn't show up. I went to the fw_update procedure. Jumpered PGC and PGD. Although not giving any COM port because it didn't exsit, the firmware was reloaded.
Stil the first deconnection(ding-dong)/reconnection(dong-ding) didn't made the COM port show up and the LED remains on. The second deconnection/reconnection time I was too happy seeing again the missing COM port showing on my XP.
Question: What is the reason the IRT LED remains on, which was tha cause that the COM port never was created. Was the fw-restore the only way to ged rid of that problem?
To accentuate the strange output I derived pulses from the wave. These are shown in red in the following picture. [attachment=0] There were 5705 data bytes in total. On top of the pulses stays the width of the pulse.
The mark widths increases regularely : 31,33,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,101,101,... to stay at 101. The space of the pulse stays at 26.
This seems more test output of the IRToy rather than an encoded form or an IR command. This time I used V223-test, but V222 is the same in this respect.
I wrote my own program (I called it IRToyBoy) which shows the waveform in the 3 modes of the V2.2 Firmware of the IRT. All tests were the reaction of the IRT on the same remote code sent by my IRremote commander. The pictures are captures of my program plot of the waveform.
The Sampling mode is clean. I measured a total code time of 23.13 ms. [attachment=4]
The SUMP mode also shows very nice. Measures time between first pulse raising edge until last pulse falling edge is now 23.73 ms. [attachment=3]
This is very possible as for Sampling mode I rely on the theoretical 21.33 µs count interval.
But I do not understand the output of the Widget Mode. I plot the value of each byte received. The step on the x-axis is assumed 100 µs. First, sometimes I receive about 5600 bytes before transmission stops, sometimes only about 1500. That behaviour already is strange. Secondly 5600*100µs is much longer that the 22µs of one command. What is the IRT doing while nothing is being sent? Following picture is of the same time scale of the two previous ones. I do not see any relation.
[attachment=2]
Here the value of the 25 first bytes received. [attachment=0]
And finally, this last picture shows the full 5600 samples, of which picture 3 represents the beginning of in more detail. [attachment=1]
Is the Widget mode totally erroneous, of do I miss the basics thereof? Maybe I have to compare with the firmware USBIRToy_irW.hex . Unfortunately I did not found that firmware yet.
The firmware, as shipped with the IRT and I used until now, was V212. I had not yet realized it was an older one. Now I updated the firmware to V222 which gives better results. Indeed e.g. IRIO Raw mode has disappeared, but Widget mode has appeared, and I got data using that widget mode:
Set DTR and RTS, then send 'p'.
The data I get back is about 1500 bytes, which however I could not get it in IRScope yet. Sample and SUMP modes seem also to work OK.
Maybe another question. Where can I find the contents of the output in the different operation modes.
1- I imagine in Decode mode, the decoded value. But for this you already have to know the parameters needed for (Win)LIRC. For the time beeing it's too early for me as I don't know the protocol parameters. I also think, reversely, the PC can send remote codes which are sent in IR by the IRT.
2- SUMP mode. After having sent 0x01 followed by a remote code nothing happens with hercules (which I use to understand the data exchange). However with the OLS I get a beatiful wave form. What do I miss here? This mode is only input to the PC.
3- Sampling mode(S). In this mode I can capture data in Hercules. I presume that I get a series of 0 and 1's of the waveform samples at 10 kHz. This mode is only input to the PC.
4- IRIO Raw mode (X). Controlled by the setup parameter is a more general sampling mode, but also bidirectional.
5- USB to serial (U). I have still not figured out how to use that mode. Also here nothing happens in Hercules after I dend U and get U01 back. How can we see its basic working principles through Hercules?
6- IRWidget mode(P), with two flavors: Frequency and Time. Here different viewpoints seem causing trouble yet.
What are the fundamental differences between the protocols of these modes? Which of all these modes is the most versatile to analyse IR codes ?
All this will take me a lot of time and therefore taking a good start will result in time saving later on.
I am new here so apoligize for my poor detailed understanding of the following.
I am actually try to decode IR protocols from various remotes, specially to understand which codes are used on a remote of Telenet (Belgian provider) digibox in order to play them back e.g. from a PC. As the goal is ultimately using th IRT Decode mode, I am playing with all modes to better understand the behaviour and richness of the IRT for the time being.
One one hand I test the IRT through its basic commands: codes sent (TX) and responses or data Received (RX). So everything should work through a Terminal emulator. I use Hercules 3.2.6 and Realterm 2.0.0 70 and thats already very nice.
I understand this is not the most functional approach, but clearly the basic one.
Once for a certain mode I see results from this basic approach, I step further into applications as OLS, and IRSCOPE. So I am now stranded at the IRScope2 hoping to use their protocol decoding expertise and share mine.
But I am stuck in connecting IRT to IRSCope.
I read that there has been a special firmware USBIRToy_irW.hex which successfully linked to IRScope. However it was not distributed in the IRT V2.2 package, therefore I assume this is not the preferred way to go. Also two firmwares to flash and re-flash is not ideal. But I also read that the IRT firmware has a mode called IR Widget mode (ascii command 'P' or 'p') although that mode is not described in the actual firmware V2.2 documentation http://dangerousprototypes.com/docs/USB ... _protocols
Once in this forum there was a discussion point that switching from one application to another application on the same COM-connection would reset the IRT in its default Decode mode. This seems not to be the case. Indeed I tested the Raw IR mode (ascii command 'x') from Hercules. Closed the connection. Reopened the connection, and the IRT still was in its Raw IR mode.
Building on this I sent a 'p' through Hercules, closed the connection, and opened that same COM port with the IRScope. Unfortunately nothing happens. The IRScope does not see any input. Has this sometning to do with DTR or RTS ?
Has anybody ever successfully used the IRToy firmware (V2.2) in IR Widget mode? Feedback greatly appreciated.
