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 decode a new protocol
Goto page Previous  1, 2, 3
 
Post new topic   Reply to topic    JP1 Remotes Forum Index -> JP1 - Protocol Decodes
View previous topic :: View next topic  
Author Message
mathdon
Expert


Joined: 22 Jul 2008
Posts: 2844
Location: Cambridge, UK

PostPosted: Thu Aug 13, 2009 6:41 am    Post subject: Reply with quote

The Robman wrote:
mathdon wrote:
... and I also have an interest in knowing what all those bytes at the beginning (pf's and pd's) actually DO.


read this...
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2306

Many thanks, Rob. This has helped me to make sense of some things from my own explorations that I didn't understand. But I think I can add to your description of R2B. The equivalent byte in HCS08 has:
Code:

0-2   special stuff (rather than your 0-1).  Values 1 and 3 as you describe, but also:
      4 = send two-bit values 0,1,2,3 as variable-length patterns 1,10,100,1000.
      This seems to be used by Nokia, with outer coding <-169|164,-276> being turned by this into an inner coding of
      <164,-276|164,-445|164,-614|164,-783>

3-4   0 = all repeat frames are the same
      1 = initial frame given by a second set of device and command bytes that follow the first in DCBUF
      2 = final frame given by a second set of device and command bytes that follow the first in DCBUF
      3 = both initial and final frames given by a second set of device and command bytes that follow the first in DCBUF
      Second set uses words as given by R28 bits 0-3, except when R28 0-1 is 3, when second set of bytes has only
      command bytes, the initial/final frames using same device bytes as all other frames

5     when set, frames after the first use alternate lead-out time given in bytes 20-21 of data block (R1E,R1F).

6     0-burst uses alternate carrier frequency and duty cycle given in bytes 20-21 of data block (R1E,R1F).

But as Mike says the HCS08 engine is the most recent of the IR engines, this may not apply to anything other than HCS08.
______________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


Joined: 22 Jul 2008
Posts: 2844
Location: Cambridge, UK

PostPosted: Sun Aug 16, 2009 10:22 am    Post subject: Reply with quote

Now I have a JP1.3 remote, I have been able to make and test my own translation of the HCS08 executor for the IODATAn-x-y protocol that I gave earlier in this thread. Here is an entry for protocols.ini that includes both HCS08 and S3C8+ code.
Code:
[IODATA]
PID=01 F9
DevParms=Device:7=81,Sub Device:7=75,n:4=1,x:7=0,y:7=0
DeviceTranslator=Translator(lsb,2,4) Translator(lsb,3,7,8) Translator(lsb,0,7,16) \
                 Translator(lsb,1,7,24) Translator(lsb,4,7,32)
CmdParms=OBC:8=0
CmdTranslator=Translator(lsb,0,8)
FixedData=80 00 8A D2 00
Code.HCS08=20 18 23 47 51 8B 45 07 08 01 13 03 39 01 13 01 13 4E 20 11 C6 08 CA FF FF 04 B6 65 62 B8 65 B8 60 B7 66 3C AC CC FF 5F
Code.S3C80=45 8B 51 8B 15 8B 45 07 08 01 13 03 25 01 13 00 FF 4E 20 11 C6 08 B6 FF FF 04 E4 08 09 F0 09 B4 08 09 B4 03 09 20 01 8D 01 46

_______________
Graham
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic       JP1 Remotes Forum Index -> JP1 - Protocol Decodes All times are GMT - 5 Hours
Goto page Previous  1, 2, 3
Page 3 of 3

 
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
Get Smart! the band's official homepage Rockabilly Central