Page 3 of 3
Posted: Wed Oct 10, 2012 7:39 am
by vickyg2003
alanrichey wrote:Rob: Sorry, I know I should learn how to do this but I do it so infreqently I keep forgetting how to do it. This is the CanalSat protocol, which is the repeat byte ?
Its different in every case. This one is already set not to repeat, while held. It will send one or two frames on the signal, and then flip the toggle bit and send another frame.
So in this case you would remove the logic for the second frame.
CODE.S3C80=2D 5E 31 8B 0F 8F 80 10 08 07 00 7D 00 6F 00 7D 00 6F AD A7 00 10 68 05 E4 06 05 8D 01 46 AF
Edit:
However, when I went to the RM, I found that CanalSat is built in to the RV chip, so you are going to have to convert this to a Manual Setting to get this to work with the RV chip. You'll probably need the latest beta to get this to work as earlier versions were not happy with custom protocols.
Posted: Wed Oct 10, 2012 8:14 am
by alanrichey
Posted: Wed Oct 10, 2012 8:15 am
by vickyg2003
Alan, I'll bet you didn't see my edit to my reply.
Posted: Wed Oct 10, 2012 8:21 am
by alanrichey
No I didn't, too quick to reply

But does that matter ? The NEC is built into the chips but I still use tweaked protocols.
Posted: Wed Oct 10, 2012 8:40 am
by vickyg2003
To tell if it matters, look at the output tab. If there is no protocol in the output section. If the protocol box is empty, the bin will not include the protocol.
It depends on how you did this.
If you introduced a new protocol entry, with a new variant name and variant number [CanalSat non-repeating] then the protocl will be included in the bin. If you just changed your CanalSat entry, then the code will not be added to the bin.
You either needed to
1) use a Manual Upgrade,
or
2) introduce a New Variant with a different name in protocols ini
or
3) tweak your RDF to change the variant on the CanalSat protocol 018C
put a colon and a variant "O18C:repeats".
2 would be the best solution in this case.
Posted: Wed Oct 10, 2012 8:46 am
by alanrichey
That's what I always do. I now have a VERY heavily amended PROTOCOLS.INI with all the non-repeating protocols in. Not looking forward to upgrading RMIR and having to convert the new one

RE-Custom remote sends double, repeating IR signal
Posted: Wed Oct 10, 2012 10:21 am
by Richard Le Beau
Hi Alan and Vicky
Thank you a lot!!!!
This code is working great with my sat Decoder and channels skip to 1 step only, Anymore sending twice the signal.
But now i miss the Realistic Remote skin and will have to use the Default skin.
From your experience, do you think it is possible to merge both files so as to
have a Remote skin as per Manufacturer(canatsat cube) and the working .Bin files
Link:
https://www.hifi-remote.com/forums/dload ... le_id=9945
https://www.hifi-remote.com/forums/dload ... e_id=11411
Thanks
Good job Guys, Keep it up
Greetings from Mauritius
Richard
Posted: Wed Oct 10, 2012 10:40 am
by alanrichey
RE-Custom remote sends double, repeating IR signal
Posted: Wed Oct 10, 2012 11:15 am
by Richard Le Beau
Ok Alan
Good job and fast response
God bless u
Works great now!!! with Realistic remote skin from Manufacturer which Sling Support has not been able to provide to his international Customer.
I know where to find the experts now,....
May this file can help other`s.
You can rename it to Canal-sat HD WIFI (+ Le Cube) for African/Indian ocean STB Repeat 0
I have also 3 WD tv live, will use available code for this device and if there an issue, i will contact you.
Thanks again and have a good day
Regards
javascript:emoticon(':lol:')
Richard
.

Posted: Thu Oct 11, 2012 12:41 am
by alanrichey
Good, glad it works, and many thanks to Vicky for help in tweaking the protocol. I'll upload it at thr weekend along with all the other remotes I have built this week.