USB-UIRT InterCodeDelay - does it work?

[blader_se]

I'm devestated. I've just got a new sattellite reciever (Canal digital, code RC-5 I guess), and the USB-UIRT does not manage to switch correctly to any two-digit channels.
1-9 seems ok though, so I played around with RepeatCount and InterCodeDelay but nothings seems to happen. By that I mean regardless of if i have reapeatcount 90 or 5, intercodedelay 100 or 900 the failure/success rate seems to be the same

I have now repeatedly switch between two-numbered channels and it accept
first digit, next time second digit, then first, then none, then first, then both and so on.

It's almost as if the code was alternating on just the two digits....

I've restarted GBPVR-recording service between each changing in the USBUIRT ir file. I've also relearnt the remote, but same result....

Any ideas?

[sub]

Yes, the repeat count and InterCodeDelay definitely work.

[sub]

You could try downloading the software from USB-UIRT site and see if you can get it work reliably. It doesnt help in the long term, but it'll help us narrow down the problem

[blader_se]

Hmm, not sure what software you are referring to... I only see Windows driver and Girder plugin. I also found Firmware v5.4, which seems to use a new format... But no "Software" :-(

[sub]

hmmm... I was fairly sure they had a simple utility for recording and playing back. Maybe I'm thinking of another blaster.

[blader_se]

I've tried relearning the USB-UIRT, but have not found any info on the format of the USBUIRT definition file. When re-learning, they are pretty close but not identical.

I've also got a JP1 remote so I know the "actual codes" (RC-5, Device 10).
Are there any way to transform these into the USBUIRT definition file?

Example:
The digit 1 have EFC 205, OBC 1 Hex f8 and have on three different occasions been learnt as

Code:

1 0000 0072 0000 000B 0020 0021 0040 0021 0020 0041 0040 0041 0040 0021 0020 0021 0020 0021 0020 0021 0020 0021 0020 0041 0020 0CA4

1 0000 0072 0000 000B 0020 0021 0041 0021 0020 0040 0041 0040 0041 0021 0020 0021 0020 0021 0020 0021 0020 0021 0020 0040 0020 0CBC

1 0000 0072 0000 000B 0020 0021 0020 0021 0041 0040 0041 0040 0041 0021 0020 0021 0020 0021 0020 0021 0020 0021 0020 0040 0020 0CC0

[sub]

I've tried relearning the USB-UIRT, but have not found any info on the format of the USBUIRT definition file. When re-learning, they are pretty close but not identical.

There isnt really information available. The hex part of the line is apparently the Pronto format, but thats about all I know about it. Other than those big hex strings, its pretty self explanitory.

I've also got a JP1 remote so I know the "actual codes" (RC-5, Device 10).
Are there any way to transform these into the USBUIRT definition file?

To be honest I dont know. When I learn these files in GB-PVR, I pretty much write the data support supplied by the USB-UIRT verbatim to the text files. The USB-UIRT header file indicates its in pronto format, but thats all I know.



When you press a key on a remote, it usually sends the IR signal about 3 - 5 times. Some device include a seq bit, which is toggled on/off to help the receiver identify when its a repeat or the next button. For example, if you press a first key on a remote it my have the seq bit set as it sends 3 repeats. When you press the next key the 3 repeats may have the seq bit cleared, so the receiver knows its the next key, not simply another repeat.

...what I'm getting at is, all the codes you've learnt may have this sequencing bit either set or clear, so only the first code works as there is no intelligence built in to toggle this bit. Hopefully this makes sense? This may be your problem.

[blader_se]

...what I'm getting at is, all the codes you've learnt may have this sequencing bit either set or clear, so only the first code works as there is no intelligence built in to toggle this bit. Hopefully this makes sense? This may be your problem.

Yes, this was my original assumption as well (what I meant by "alternating").

So, to overcome this I tried to concatenate the two different definitions (the swap of 0020 and 0040 in column 8 - but that would have been too easy :-(

Back to the ReapeatCount and InterCodeDelay. I would have thought that setting those to 3 and 200 vs 99 and 900 would be possible to distinguish by looking at the flashing red LED on the USBUIRT...

[blader_se]

I think I can confirm that it is the toggling in the RC-5 code that are screwing things up. The old reciever apparently did not care to detect this, but the new one does.

First I define two IR files, 0x.txt and x0.txt that holds the two versions of the code. Then I create a .bat file for each channel, e.g. 30.bat contains

Code:

uutx.exe -fx0.txt 3
uutx.exe -f0x.txt 0

(uutx.exe is the commandline tool for the USB-UIRT)

So, if someone could point me to some info about batch file syntax, hopefully I could make a batch files that takes the {channel} parameter from GBPVR and execute the appropriate uutx.exe commands...

[sub]

There was some discussion about this at the USB-UIRT forums, so you might want to check that out to see if it has some solutions you hadnt thought of.

If you configure it to use the .exe channel changer, and point a batch file of your choosing, the channel number will be passed by default as the first argument. In you batch file you can access this with %0.

Code:

echo Switching to channel %0

Unfortunately I'm not batch file expert, so I dont know how you break that single number into its individual digits.