Thanks all for the time consuming replies,
Yes I did lose count there with the byte numbering.
Think I have enough info to finish the job.
My question re lead-out time comes about since once having problems with NEC codes I made for a customer. The NEC protocol uses both seq1 and seq2 of thepronto ...
Search found 3 matches
- Fri Feb 06, 2009 8:48 pm
- Forum: Non-JP1
- Topic: Panasonic protocol spec
- Replies: 7
- Views: 28034
- Thu Feb 05, 2009 11:44 pm
- Forum: Non-JP1
- Topic: Panasonic protocol spec
- Replies: 7
- Views: 28034
Thanks for the info.
I never did decipher the makehex method representing the protocol.
My understanding is basically as follows, reading bits from rhs to lhs using your first example, all hex numbers are msb -lsb reversed as usual.
First 2 bytes (2x 8 bit bytes) are the oem device code, always the ...
I never did decipher the makehex method representing the protocol.
My understanding is basically as follows, reading bits from rhs to lhs using your first example, all hex numbers are msb -lsb reversed as usual.
First 2 bytes (2x 8 bit bytes) are the oem device code, always the ...
- Sun Feb 01, 2009 7:37 pm
- Forum: Non-JP1
- Topic: Panasonic protocol spec
- Replies: 7
- Views: 28034
Panasonic protocol spec
Hello JohnsFine,
Clarity needed re terminology ..Panasonic ir protocol
Device = address. cool I get that.
OBC stands for?.. and is it the sub-device address or the function/command number/data?
EFC stands for?.. or is it that the sub-device address or the function/command number, and does pronto ...
Clarity needed re terminology ..Panasonic ir protocol
Device = address. cool I get that.
OBC stands for?.. and is it the sub-device address or the function/command number/data?
EFC stands for?.. or is it that the sub-device address or the function/command number, and does pronto ...