502 errors received when I send a command to the TPI

[philetaylor]

Hi. I am developing support for the EnvisaLink for within OpenRemote (it currently supports the IT100) I realise that the protocol is (almost) identical but I tend to get a lot of 502020 errors when I send commands:

Code: Select all

DEBUG 2013-02-10 10:21:50,252 : New packet created [command=060, data=1,checksum=C7]
INFO 2013-02-10 10:21:50,253 : Instantiating new ExecuteCommand instance - [PACKET:command=060, data=1, address=192.168.99.101, target=1]
INFO 2013-02-10 10:21:50,254 : Created DSCIT100 Command [PACKET:command=060, data=1, address=192.168.99.101, target=1]
DEBUG 2013-02-10 10:21:50,255 : Sending data to address 192.168.99.101 : 0601C7

DEBUG 2013-02-10 10:21:50,692 : Received data from 192.168.99.101 : 5000602B
DEBUG 2013-02-10 10:21:50,693 : Received data from 192.168.99.101 : 50202029

And nothing happens (no fire alarm!). I get a similar response when I send ARM/DISARM commands but strangely they work!

Code: Select all

DEBUG 2013-02-10 10:26:31,265 : New packet created [command=033, data=1123400,checksum=F1]
INFO 2013-02-10 10:26:31,266 : Instantiating new ExecuteCommand instance - [PACKET:command=033, data=1123400, address=192.168.99.101, target=1]
INFO 2013-02-10 10:26:31,268 : Created DSCIT100 Command [PACKET:command=033, data=1123400, address=192.168.99.101, target=1]
DEBUG 2013-02-10 10:26:31,269 : Sending data to address 192.168.99.101 : 0331123400F1

DEBUG 2013-02-10 10:26:33,725 : Received data from 192.168.99.101 : 5000332B
DEBUG 2013-02-10 10:26:33,726 : Received data from 192.168.99.101 : 50202029
DEBUG 2013-02-10 10:26:36,725 : Received data from 192.168.99.101 : 5108301
DEBUG 2013-02-10 10:26:36,726 : LED Status update [LED1=ON]
DEBUG 2013-02-10 10:26:36,726 : LED Status update [LED2=OFF]
DEBUG 2013-02-10 10:26:36,727 : LED Status update [LED3=OFF]
DEBUG 2013-02-10 10:26:36,728 : LED Status update [LED4=OFF]
DEBUG 2013-02-10 10:26:36,729 : LED Status update [LED5=OFF]
DEBUG 2013-02-10 10:26:36,731 : LED Status update [LED6=OFF]
DEBUG 2013-02-10 10:26:36,732 : LED Status update [LED7=ON]
DEBUG 2013-02-10 10:26:36,733 : LED Status update [LED8=ON]
DEBUG 2013-02-10 10:26:37,226 : Received data from 192.168.99.101 : 6561D2
DEBUG 2013-02-10 10:26:37,226 : Partition in exit delay [partition=1]
DEBUG 2013-02-10 10:26:40,569 : New packet created [command=040, data=1123400,checksum=EF]
INFO 2013-02-10 10:26:40,570 : Instantiating new ExecuteCommand instance - [PACKET:command=040, data=1123400, address=192.168.99.101, target=1]
INFO 2013-02-10 10:26:40,571 : Created DSCIT100 Command [PACKET:command=040, data=1123400, address=192.168.99.101, target=1]
DEBUG 2013-02-10 10:26:40,573 : Sending data to address 192.168.99.101 : 0401123400EF

DEBUG 2013-02-10 10:26:40,726 : Received data from 192.168.99.101 : 50004029
DEBUG 2013-02-10 10:26:40,727 : Received data from 192.168.99.101 : 50202029
DEBUG 2013-02-10 10:26:42,226 : Received data from 192.168.99.101 : 51081FF
DEBUG 2013-02-10 10:26:42,227 : LED Status update [LED1=ON]
DEBUG 2013-02-10 10:26:42,227 : LED Status update [LED2=OFF]
DEBUG 2013-02-10 10:26:42,227 : LED Status update [LED3=OFF]
DEBUG 2013-02-10 10:26:42,228 : LED Status update [LED4=OFF]
DEBUG 2013-02-10 10:26:42,228 : LED Status update [LED5=OFF]
DEBUG 2013-02-10 10:26:42,231 : LED Status update [LED6=OFF]
DEBUG 2013-02-10 10:26:42,232 : LED Status update [LED7=OFF]
DEBUG 2013-02-10 10:26:42,233 : LED Status update [LED8=ON]
DEBUG 2013-02-10 10:26:42,234 : Received data from 192.168.99.101 : 6551D1
DEBUG 2013-02-10 10:26:42,235 : Partition disarmed [partition=1]
DEBUG 2013-02-10 10:26:46,227 : Received data from 192.168.99.101 : 6501CC
DEBUG 2013-02-10 10:26:46,227 : Partition ready [partition=1]

Any ideas why I keep receiving the 502 errors and why the 060 commands seem not to work? The FIRE button on my "physical" keypads works fine.

Thanks

Phil

[K-Man]

There's an open bug report saying that the FAP key commands don't work. PM me with your email address and I'll put you on the developer mailing list.