JP1 Remotes Forum Index JP1 Remotes


FAQFAQ SearchSearch 7 days of topics7 Days MemberlistMemberlist UsergroupsUsergroups RegisterRegister
ProfileProfile Log in to check your private messagesLog in to check your private messages Log inLog in

How to get protocol id and fixed data from Pronto

 
Post new topic   Reply to topic    JP1 Remotes Forum Index -> JP1 - General Forum
View previous topic :: View next topic  
Author Message
egn



Joined: 11 Feb 2004
Posts: 50

                    
PostPosted: Tue Feb 17, 2004 10:08 am    Post subject: How to get protocol id and fixed data from Pronto Reply with quote

Hi,

I have several devices I want to control with my URC-7541 remote for which I have no protocol id found in devices.xls but have codes in my Pronto.

I have converted the Pronto ccf file with ccf2efc but I had only partly success with converting this info to working protocol ids. I first tried RM but alway got protocol id 00 5E. As I now use KM with the Device Combiner I then converted with KM an had at least success once.

Working conversion:
Humax IRCI-5400 Pronto NEC2:0.16 -> 00 5A 21 FF F7

Then I tried discrete On/Off codes for a Yamaha RXV-2095. It is NEC:122 which converted to 00 5A 20 FF A1. But when I relearn this code into the pronto I get NEC2:122 and the code doesn't work.

Here is a list of codes I want to convert to protocol ids:
Yamaha RXV-2095 Pronto NEC:122 -> ?
LightControl Pronto "RC5" 5000 0000 0000 0001 001D 0039 -> ?
ScreenControl Pronto "LEARNED" 7000 006D 0000 0008 0011 000D 0010 0002 0017 0003 0003 0003 0003 0003 0003 0003 0002 0002 0000 00BB -> ?
LinuxVDR Pronto "RC5" 5000 0000 0000 0001 001E 0001
Multitainer Pronto NEC2:138.245 -> ?
MultitainerPwr Pronto 56.0 kHz NEC2:80 -> ?
Beamer 3M MP8750 Pronto 35.7 kHz -> ?
Lumagen Vision 38.7 kHz JVC2?:196 ->

Especially the results with RC5 where strange. Instead of getting the above short strings when relearning the commands to pronto I got something like:

IR Code: "LEARNED" 0000 0072 0027 0000 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0041 003F 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0CD1 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0041 003F 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0CD1 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0041 003F 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020
freq=36.4KHz
(RC5):30:63 ODD ?EFC 026 ? 010 ? 034 ? 018 {in single part using 13 of 39 pairs}
timebase=880 Zero = 0.0,0.0 or 2.0 One = 1.0,-1.0 or -2.0 Prefix = 1.0,-1.0 Suffix = 1.0,-102.5 Total = 130
(RC5):30:63 ODD ?EFC 026 ? 010 ? 034 ? 018 {offset 13 in single part using 13 of 39 pairs}
timebase=880 Zero = 0.0,0.0 or 2.0 One = 1.0,-1.0 or -2.0 Prefix = 1.0,-1.0 Suffix = 1.0,-102.5 Total = 130
(RC5):30:63 ODD ?EFC 026 ? 010 ? 034 ? 018 {offset 26 in single part using 13 of 39 pairs}
timebase=880 Zero = 0.0,0.0 or 2.0 One = 1.0,-1.0 or -2.0 Prefix = 1.0,-1.0 Suffix = 1.0,-1.0 Total = 28

Are there the general rules or hints documented somewhere?

Thanks,
Emil
Back to top
View user's profile Send private message
johnsfine
Site Admin


Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA

                    
PostPosted: Tue Feb 17, 2004 10:27 am    Post subject: Re: How to get protocol id and fixed data from Pronto Reply with quote

egn wrote:

I have converted the Pronto ccf file with ccf2efc


ccf2efc is obsolete. Use DecodeCCF instead.

egn wrote:

Then I tried discrete On/Off codes for a Yamaha RXV-2095. It is NEC:122 which converted to 00 5A 20 FF A1. But when I relearn this code into the pronto I get NEC2:122 and the code doesn't work.


A decode of NEC means the learned signal didn't contain enough information to tell whether it is really NEC1 or NEC2. If you've determined that NEC2 is wrong, try the upgrade again with NEC1.

egn wrote:

LightControl Pronto "RC5" 5000 0000 0000 0001 001D 0039 -> ?


That is RC5 protocol, device 29, OBC 57. DecodeCCF would have told you that.

egn wrote:

ScreenControl Pronto "LEARNED" 7000 006D 0000 0008 0011 000D 0010 0002 0017 0003 0003 0003 0003 0003 0003 0003 0002 0002 0000 00BB -> ?


I don't have the patience to do that one by hand. Probably DecodeCCF will get it right. If not, tell me the URL for the CCF file.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
egn



Joined: 11 Feb 2004
Posts: 50

                    
PostPosted: Tue Feb 17, 2004 1:29 pm    Post subject: Reply with quote

Hi John,

thank you for the quick answer. I now use DecodeCCF and it decodes all the data.

But, there is still a problem with the RC5 codes. I know the RC5 data format. When I enter RC5 and 30 into KM I get 00 E8 01 01 01. As I have specific RC5 codes I need a way to convert this codes to EFC s.

In the KM combiner I have used direct hex codes. I.e. for 'RC5 30 1' I used the above protocol and hex code '1'. I testet with the codes RC5 30 1, RC5 30 2 and RC5 30 3:

Code:

Protocol   Device   SubDev   OBC   EFC   Misc   Decode   UDB   Function   Sequence   Key   Panel   DevName   TopFreq   Once   Rept   
RC5   30      63   018_010_034   T=1   0_13      LEARNED   1   Test   General   Verst`E4rker      363.609   39   0
RC5   30      63   018_010_034   T=1   13_13      LEARNED   1   Test   General   Verst`E4rker      363.609   39   0
RC5   30      63   018_010_034   T=1   26_13      LEARNED   1   Test   General   Verst`E4rker      363.609   39   0
RC5   29      63   018_010_034   T=0   0_12      LEARNED   2   Test   General   Verst`E4rker      363.609   36   0
RC5   29      63   018_010_034   T=0   12_12      LEARNED   2   Test   General   Verst`E4rker      363.609   36   0
RC5   29      63   018_010_034   T=0   24_12      LEARNED   2   Test   General   Verst`E4rker      363.609   36   0
RC5   28      63   018_010_034   T=1   0_13      LEARNED   3   Test   General   Verst`E4rker      363.609   26   0
RC5   28      63   018_010_034   T=1   13_13      LEARNED   3   Test   General   Verst`E4rker      363.609   26   0


It seems to be that the device code is counted down instead of staying at 30. I see nothing else related to the used hex code.

Either the protocol ID and fixed bytes are not correct or something is broken in the RC5 protocol in my remote.

Any idea?

Thanks,
Emil
Back to top
View user's profile Send private message
johnsfine
Site Admin


Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA

                    
PostPosted: Tue Feb 17, 2004 1:58 pm    Post subject: Reply with quote

I should have asked earlier why you are going directly to a device combiner upgrade rather than using (or at least testing) individual upgrades for your individual devices. Maybe there is a good reason, or maybe something confused you into thinking you needed to.

egn wrote:

thank you for the quick answer. I now use DecodeCCF and it decodes all the data.

But, there is still a problem with the RC5 codes. I know the RC5 data format. When I enter RC5 and 30 into KM I get 00 E8 01 01 01. As I have specific RC5 codes I need a way to convert this codes to EFC s.


I thought DecodeCCF did give EFCs for RC5. I need to check the released copy and fix it if it doesn't.

egn wrote:

In the KM combiner I have used direct hex codes. I.e. for 'RC5 30 1' I used the above protocol and hex code '1'. I testet with the codes RC5 30 1, RC5 30 2 and RC5 30 3:


Those hex commands don't mean what you think they mean.

Even if you don't intend to use a individual upgrade for just the RC5, you may need to create one in KM so that KM can do the translation for you from OBC number to EFC and hex.

A hex command of 1 or 2 should give you the OBC 63 that you are seeing.

A hex command of 3 should give you two different device numbers. I don't want to try to figure out which two, nor what OBC you would be likely to get. So maybe both the 29:63 and the 28:63 are from that.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
egn



Joined: 11 Feb 2004
Posts: 50

                    
PostPosted: Wed Feb 18, 2004 12:42 am    Post subject: Reply with quote

johnsfine wrote:
I should have asked earlier why you are going directly to a device combiner upgrade rather than using (or at least testing) individual upgrades for your individual devices. Maybe there is a good reason, or maybe something confused you into thinking you needed to.


I saw no reason to test native first because the combiner works for some devices. I also have no advantage of doing it native becauses devices.xls doesn't contain most of my devices.

But if you think it is worth I will try to test RC5 native.

The reason why I have to use the combiner is because the key move memory is very limited on the URC-7541 remote and I have to do a lot of key moves to get the functionality I require.

johnsfine wrote:

I thought DecodeCCF did give EFCs for RC5. I need to check the released copy and fix it if it doesn't.


If you look at the lines I have posted above you can see that for RC5 30 1 I get device=30, OBC=63 and EFC=018_010_034. For RC5 30 2 I get exactly the same.

johnsfine wrote:

Those hex commands don't mean what you think they mean.

Even if you don't intend to use a individual upgrade for just the RC5, you may need to create one in KM so that KM can do the translation for you from OBC number to EFC and hex.


How do I have to enter the device number into KM to get the right protocol id and fixed bytes?
There are 3 device fields below the protocol selection in KM.

How do I translate the command RC5 30 1 into the right code?
Or is RC5 a two byte code that can't be used with the combiner?

johnsfine wrote:

A hex command of 1 or 2 should give you the OBC 63 that you are seeing.

A hex command of 3 should give you two different device numbers. I don't want to try to figure out which two, nor what OBC you would be likely to get. So maybe both the 29:63 and the 28:63 are from that.

[/quote]

This seems to inconsistent to me because I get the same OBC 63 for all the hex codes.

It would be nice to get at least one RC5 example working. There seems to be a missing link between a specific RC5 command that I can enter into the Pronto and the resulting protocol id, fixed bytes and EFC on my remote.

Thanks for your help.

Emil
Back to top
View user's profile Send private message
johnsfine
Site Admin


Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA

                    
PostPosted: Wed Feb 18, 2004 11:05 am    Post subject: Reply with quote

egn wrote:

I saw no reason to test native first because the combiner works for some devices. I also have no advantage of doing it native becauses devices.xls doesn't contain most of my devices.


Maybe I don't understand what you mean by "native". I wasn't suggesting that you try a built-in setup code, such as those listed in devices.xls. I was suggesting you make an ordinary (not device combiner upgrade).

egn wrote:

The reason why I have to use the combiner is because the key move memory is very limited on the URC-7541 remote and I have to do a lot of key moves to get the functionality I require.


OK. That's a good reason to use the combiner. But since you are having trouble with the combiner, it is better to build a simpler upgrade first. Maybe you will need to test the simpler upgrade before copying its contents into the combiner. Maybe it is enough to just use the simpler upgrade to compute the EFC numbers for the combiner.

egn wrote:

If you look at the lines I have posted above you can see that for RC5 30 1 I get device=30, OBC=63 and EFC=018_010_034. For RC5 30 2 I get exactly the same.


That lists the three possible EFC numbers (018, 010 or 034) for the OBC number 63.

egn wrote:

How do I have to enter the device number into KM to get the right protocol id and fixed bytes?
There are 3 device fields below the protocol selection in KM.


One set of fixed data for RC5 protocol supports either half of the possible OBC range for each of three device numbers, or all of the OBC range for one device number and half for another.

Each device field is used to define one of those three "halves". If you need OBC values 0 through 63 for a device number, you put that device number in any one of the three positions. If you need OBC values 64 through 127 for a device number, you put 100 plus that device number in any one of the three positions.

For example, if you need the entire range of OBC values for device 30, you should put 30 in one of those device positions and 130 in another.

egn wrote:

How do I translate the command RC5 30 1 into the right code?


1) You make the selection on either the setup sheet or the Functions sheet to let you control OBC rather than EFC. (So OBC appears in column B of the setup sheet).

2) You select RC5 protocol and put 30 into any one of the three device fields.

3) On the Functions sheet put 30 in the OBC column.

4) If you put the 30 in the first device field, leave the byte2 column blank. If you put it in the second device field, put a 1 in byte2. If you put it in the third device field, put a 2 in byte2.

5) KM will display the right EFC and HEX.

egn wrote:

Or is RC5 a two byte code that can't be used with the combiner?


No. RC-5 is a "mini-combo" code that has two pieces of information in a one byte hex command, so you can combine on two levels: Up to three half ranges of RC-5 combined in one set of RC-5 fixed data and that combined with other protocols and/or other sets of three RC-5 half ranges by the device combiner.

egn wrote:

This seems to inconsistent to me because I get the same OBC 63 for all the hex codes.


The OBC in RC-5 comes from only the top six bits of the hex command, so hex commands 0 through 3 have the same OBC. Hex commands 0 through 2 use the fixed data from the three device fields for the device (KM sets all three items of fixed data the same if you use only the first field). Hex command 3 uses itself as fixed data for device with strange results.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
egn



Joined: 11 Feb 2004
Posts: 50

                    
PostPosted: Thu Feb 19, 2004 6:36 pm    Post subject: Reply with quote

johnsfine wrote:

A hex command of 3 should give you two different device numbers. I don't want to try to figure out which two, nor what OBC you would be likely to get. So maybe both the 29:63 and the 28:63 are from that.


Thanks, this was the critical information. The instructions to convert pure RC5 commands into hex code are in my case:

1. Select RC5 in KM
2. Enter device id in first device field on setup page (i.e. 30 -> 00 E8 01 01 01)
3. Convert command to hex by inverting! command value and shift it 2 times left (i.e. 22h -> 74h)

Thanks a lot for your help.

Emil
Back to top
View user's profile Send private message
johnsfine
Site Admin


Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA

                    
PostPosted: Thu Feb 19, 2004 8:57 pm    Post subject: Reply with quote

egn wrote:

2. Enter device id in first device field on setup page (i.e. 30 -> 00 E8 01 01 01)
3. Convert command to hex by inverting! command value and shift it 2 times left (i.e. 22h -> 74h)


That will work until you get an OBC greater than 63.

Also, assuming you want more RC5 device numbers, your method will use a little extra room in the device combiner, by having seperate fixed data for each device number rather than one set of fixed data for up to three device numbers.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic       JP1 Remotes Forum Index -> JP1 - General Forum All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

Powered by phpBB © 2001, 2005 phpBB Group
Top 7 Advantages of Playing Online Slots The Evolution of Remote Control