Envisalink TPI Programmer's Document v1.04 Errors
Posted: Wed Dec 31, 2014 11:32 am
These are several things I ran across in the manual while I was writing some code.
On page 1, "The 005 command contains the password which is the same password to log into the Envisalink's local web page". The web page allows a password longer than 6 characters, while the 005 command only accepts 1 to 6 characters. This is indicated, but not obvious from the outset that you need to truncate the web page password to 6 characters for the 005 command.
Section 3.1 should indicate that if messages are timestamped (via the 055 command), that the timestamp is NOT part of the checksummed message. Several methods may be used to validate if the message has a timestamp or not. If it does, it the timestamp and the trailing space should be pruned prior to verifying the checksum of the message.
Partition Armed (652) should explicitly indicate 0=away, 1=stay, etc, like Login Interaction (505) documentation does.
Ring Detected states that this command will only be issued if an Escort 5580xx module is present. This functionality is built-in to Power 1616, 1632 and 1664 panels, which don't require the Escort module. Once the firmware is updated to support the temperature broadcast from a CT50 thermostat, Indoor Temperature Broadcast (561) and possibly Outdoor Temperature Broadcast (562) will need to be updated also.
Command Output Pressed (912) states there is 1 parameter, and it's not documented. There are actually two parameters. Byte 1 is the partition number (1-8), and byte 2 is the PGM # (1-4).
On page 1, "The 005 command contains the password which is the same password to log into the Envisalink's local web page". The web page allows a password longer than 6 characters, while the 005 command only accepts 1 to 6 characters. This is indicated, but not obvious from the outset that you need to truncate the web page password to 6 characters for the 005 command.
Section 3.1 should indicate that if messages are timestamped (via the 055 command), that the timestamp is NOT part of the checksummed message. Several methods may be used to validate if the message has a timestamp or not. If it does, it the timestamp and the trailing space should be pruned prior to verifying the checksum of the message.
Partition Armed (652) should explicitly indicate 0=away, 1=stay, etc, like Login Interaction (505) documentation does.
Ring Detected states that this command will only be issued if an Escort 5580xx module is present. This functionality is built-in to Power 1616, 1632 and 1664 panels, which don't require the Escort module. Once the firmware is updated to support the temperature broadcast from a CT50 thermostat, Indoor Temperature Broadcast (561) and possibly Outdoor Temperature Broadcast (562) will need to be updated also.
Command Output Pressed (912) states there is 1 parameter, and it's not documented. There are actually two parameters. Byte 1 is the partition number (1-8), and byte 2 is the PGM # (1-4).