Canal+ CANALSAT remote decodes as Phase Encoded (RC-type)

[gfb107]

It was added in v1.96

[alanrichey]

Sorry, I thought i was running 1.96, turns out i was using 1.92.

[sebpoterie]

Hi,

I try to learn the G5 (canalsat, canal+ sat receiver) IR command

My learning code are not very clean.

For example :

1 is
0000 0044 0014 0000 000F 001E 000F 000F 000F 000F 001E 001E 001E 000F 000F 001E 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 001E 001E

2 is
0000 004A 0015 0000 000E 001C 000E 000E 000E 000E 001C 001C 001C 000E 000E 001C 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 001C 001C 000E 1333 000E 001C

When I check those codes in IR Tool with Ir decodeDLL, I can read :

Protocol CanalSat

for 1 : Device 11, OBC 1, EFC : 34
for 2 : Device 11, OBC 2, EFC : 242

So I try to use IRP notation provided in Decode IR help to built a canalsat.irp file

UEI protocol: 018C
IRP notation: {55.5k,250,msb}<-1,1|1,-1>(1:1,D:7,S:6,T:1,0:1,F:7,-89m)+
EFC translation: 7-bit MSB.

I try this for my canasat.irp file to generate hex list with MakeHex

Device=11
Function=0..255

Protocol=canalsat
Frequency=55500
Time Base=250
Message Time=89m
One=1,-1
Zero=-1,1
Prefix=1,1
First Bit=MSB
Form=D:7,S:6,T:1,0:1,F:7

The hex generated are not recognized in IR Tool.

Maybe someone could help me to find my mistake...
Thanks in advance.

Sébastien.

[3FG]

Try this:
Device=11.0
Function=0..255
Protocol=Canalsat
Frequency=55500
Time Base=250
Message Time=89m
Zero=-1,1
One=1,-1
First Bit=MSB
Form=;1:1,D:7,S:6,T:1,0:1,F:7

Changes--Explicitly set Subdevice to 0. Added a semicolon at the beginning of Form to indicate that the entire [1:1,D:7,S:6,T:1,0:1,F:7] string is repeated, and replaced Prefix with 1:1.

Not important, but reversed the order of Zero and One to match the style in other IRP files. Note that it also possible to write the Form as:
Prefix=1,-1
Form=;*,D:7,S:6,T:1,0:1,F:7
but I think the format shown earlier is easier to understand, because it isn't necessary to remember that * denotes the position of the Prefix.

[sebpoterie]

Thanks 3FG (very much)

The hex generated are now recognized in Ir Tool BUT when I copy past the hex in my pronto, the order is sent twice

press 1 give me 11

I try to remove your semicolon at the beginning of Form and give a try.

[3FG]

DecodeIR.html says:
The repeat frames are not all identical. T toggles within a single signal, with T=0 for the start frame and T=1 for all repeats.

So this may be better, since it explicitly sets the Toggle bit to 0 for the first frame and 1 for the repeats:
Device=11.0
Function=0..255
Protocol=Canalsat
Frequency=55500
Time Base=250
Message Time=89m
Zero=-1,1
One=1,-1
First Bit=MSB
Form=1:1,D:7,S:6,0:1,0:1,F:7;1:1,D:7,S:6,1:1,0:1,F:7

[sebpoterie]

So,

3FG1 : Form=1:1,D:7,S:6,T:1,0:1,F:7 (without ";")

seems to work well than

3FG2 : Form=1:1,D:7,S:6,0:1,0:1,F:7;1:1,D:7,S:6,1:1,0:1,F:7

For "1" 3FG1 gives me
0000 004B 0014 0000 000E 001B 000E 000E 000E 000E 001C 001B 001B 000E 000E 001B 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 001C 001B

Pronto gives me a "1"

For "1" 3FG2 gives me
0000 004B 0014 0013 000E 001B 000E 000E 000E 000E 001C 001B 001B 000E 000E 001B 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 001C 10F8 000E 001B 000E 000E 000E 000E 001C 001B 001B 000E 000E 001B 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 001C 001B 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 001C 10F8

Pronto gives me a "0"

The other functions from 2 to 9 work both with 3FG1: and 3FG2:
I do not find the "0" in 3FG1
It is not Device Code: 11.0 (0x0B.0x00) Function: 0 (0x00)
It is not Device Code: 11.0 (0x0B.0x00) Function: 10 (0x0A)
and I think that "0" in 3FG2 is a dirty "0" !

Thanks again.

[3FG]

Can you try to learn the "0" button?

[sebpoterie]

So...
I have found the "0" without having to learn it. it was lost in the list...

0000 004B 0015 0000 000E 001B 000E 000E 000E 000E 001C 001B 001B 000E 000E 001B 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 001B

I use finally your "3FG1" form without the ";". The hexa codes seem to be clean.
Unfortunately, my 7 prontos do not learn this kind of code well in stand alone mode.
I have asked Pace, who is the manufacturer of the satellite decoder, to provide me their hex codes. I am waiting for an answer...just to see if my (your) codes are right...

My IR setup is very complex (very big house, many IR repeater and RF extenders (that are much more plasma and LCD proof than IR repeater !) but I miss your bases when something is unusual (exotic IR protocol)

Anyway, thank you a thousand times and sorry for my english...French people are very bad in foreign languages.
See U
Regards.

[gbuathier]

This thread just saved my life !

I am using AMX panels and needed new HEX codes for the G5 Cube I just installed in replacement of my old Mediasat Max : the IR codes I had were adding a 0 to any command that was send...

I generated HEX codes using MakeHex with the following IRP file ('3FG2' config) :

Device=11.0
Function=0..255
Protocol=Canalsat
Frequency=55500
Time Base=250
Message Time=89m
Zero=-1,1
One=1,-1
First Bit=MSB
Form=1:1,D:7,S:6,0:1,0:1,F:7;1:1,D:7,S:6,1:1,0:1,F:7

Functions 0-9 are the equivalent digits, I have now to investigate to find out the other commands.

Many thanks to all the contributors of this thread.