Jump to content


UDP-IQ


  • Please log in to reply
No replies to this topic

#1 Jeff Starnes

Jeff Starnes
  • Members
  • 1 posts

Posted 20 September 2007 - 04:45 PM

Hello,

We have developed a library that communicates to Crown for monitoring health, etc. However, we are experiencing receipt of non-documented packets from Components that have a Destination IQ address of 0xFFFF. The following dump shows what we are receiving:

Bit                                        Byte                    
Offset                Binary               Offset Hexadecimal ASCII
====== =================================== ====== =========== =====

000000 01001001 01010001 00000000 00000000 000000 49 51 00 00 IQ..
000020 00000000 00110010 00000000 00000011 000004 00 32 00 03 .2..
000040 00000001 00000000 00111000 11111000 000008 01 00 38 F8 ..8.
000060 00000011 00001000 11111111 11111111 00000C 03 08 FF FF ....
000080 00000000 00011010 01000011 01001110 000010 00 1A 43 4E ..CN
0000A0 01001101 00110011 00110001 00110000 000014 4D 33 31 30 M310
0000C0 00110001 00100000 00000000 00000000 000018 31 20 00 00 1 ..
0000E0 10000000 00000000 00000000 01100000 00001C 80 00 00 60 ...`
000100 00101011 00000011 00100001 10111101 000020 2B 03 21 BD +.!.
000120 10101100 00010100 10010001 01010100 000024 AC 14 91 54 ...T
000140 11111111 11111111 11111111 00000000 000028 FF FF FF 00 ....
000160 10101100 00010100 10010001 00000001 00002C AC 14 91 01 ....
000180 00111000 11111000 00000000 00000000 000030 38 F8 00 00 8...


Is there any additional documentation explaining the UDP-IQ protocol that is more current than the March 5, 2003 document. This message appears to be some sort of roll-call response and/or broadcast. Moreover, there is no documentation on the contents of Presets and Scenes in the UDP-IQ documentation. I think this document is far out dated...

Best Regards,

Jeff Starnes