Strange blastcfg.exe & blast.exe repeated digits problem

[fla]

I'm trying a new TV provider and can't get certain channels to work. The STB isn't known by blastcfg.exe so I made it learn the ten digits then tuned to channels 1-10 successfully and thought I was done as all 10 digits worked. I can't however tune to 100, 112, 122, 330, 344, 355 or anything with consecutive identical digits.

I noticed that if I send "10" from blastcfg.exe immediately followed by "0" from the provided remote I need to press "0" twice on the remote to get it to work and tune channel 100. I then tried learning a second "0" onto key '.' (dot) by intentionally missing the IR receiver on the first press thus recording the second "0". I can then tune channel 100 from blastcfg.exe by hitting either "10." or "1.0" but "100" or "1.." both result in "10".

It seems the IR data for the digits includes a sequence number and the STB ignores consecutive identical [digit/seq#] pairs.

Environment:
HDPVR2 with blastercfg.exe & blast.exe from WinTV 10
Windows 11
STB from tv provider: Amigo 7X

Any ideas? It seems I would need two blastcfg.exe setups and to tune to channel "11" I would need to send a "1" from the primary digits cfg and another "1" from a secondary digits config".

[sub]

For most remotes, each time you press a button, they transmit code multiple times. Not all off those will make it to the STB, but the repeats help the odds it'll be received.

Some remotes use toggle bits, so a bit of code changes every button press, so that it can tell two repeated digits are different button presses. It's likely your device is doing this. ie, with 344 it's seeing lots of '4's arriving, and the toggle bit hasn't changed, so it's assuming they're still the same key press.

I don't know how you'd fix it with BlastCFG. Hauppauge might be able to help you.

[fla]

WOW great explanation thanks sub!

I'm just going to return the STB and stick with my old TV provider. Was hoping to support my small local ISP's new TV service but things need to be easy and simple for me now. Back to the big evil national telecom giant. :-(

[mvallevand]

If you break your script to send digits then you could set the pace yourself in the script. That's what I have had to do.

Martin

[fla]

Good idea mvallevand. There's an "Inter-Digit Delay (ms)" field in blastcfg.exe that affects blast.exe. I just tried up to 3000ms and the STB still dropped the second identical digit. Any longer than 3s between digits and the STB was thinking that was all and automatically tuning to the first digit.

The new STB will be going back. Disappointing but at least I learned a few things from the gurus.