PanelStatus16 and few new messages, 0x6E/0x70 support for 3 digit decimal data #187
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added printPanelStatus16 and Unknown data messages for unknown Panel Status. RF Delinquency and Trouble acknowledged messages added from event buffer. 0xB3 message on PC1565-2P after activating PGM output, together with 0xB2 which was send few lines before on same cmd milisecond ago. Downlook remote trigger, section [906] on PC5020, I was able to trigger it without having Downlook module.
When panel requires 3 digit input, LCD data which was being send or received on 0x6E and 0x70 cmds is decimal, not hexadecimal like the other ones.
kricon
changed the title
Downloading in progress message is displayed on all LCD keypads while panel is connected on DLS. When 0xB1 byte5 bit1 is zero seems to be related to Wireless notifications, it can be for status/troubles of wireless zones?
Sync with current taligentx:develop
Renamed Keypad going idle notification as it seems to be used for more keypad notifications. Labels on PK5500 have bigger string and doesn't get broadcasted onto LCD5500, also probably vice-versa. 11111111 1 11111111 11110111 11111111 11111111 11111111 11110111 11111111 11111111 [Module/0x05] Partition 2 Key: Menu navigation | Keypad notification 11111111 1 11111111 11111111 11111111 11111111 00011111 11111111 11111111 11111111 [Module/0x1B] Zone label broadcast announced 11111111 1 11111111 11111111 11111111 11111111 01111111 11111111 11111111 11111111 [Module/0x1B] Door chime broadcast announced
|
Merged, thank you! I moved a few other strings out of flash and into SRAM to fit (barely) on Uno after a few other changes. There are a few ways to shave off more space but as it fits for now I'll leave it as-is until there's more to add. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Probably,
printPanelStatus14, 16 and 1B can be merged into one. But maybe better to keep them seperated (to avoid possible conflicts) as there is many (mostly obsolete) modules which isn't decoded yet.When panel requires 3 digit input, LCD data which was being send or received on 0x6E and 0x70 cmds is decimal, not hexadecimal like the other ones.
Using
printPanelMessagesto change boolean may not be the great idea, but it works flawlessly.Panel messages seems to be send on so many different cmds, that it was easiest to just put it there - for example if I just put it into 0x05 cmd, it all works fine on smaller panels but doesn't for PC5020 - where "Enter 3 digit" message was first send on 0x0A then on 0xE6.20 cmds, etc.
RF Delinquency messages in event buffer doesn't seem to have track of zone on which it occured. Zones with RF delinquency is shown when entering *2 zones with rf delinquency section, same way as for zones/keyfobs low battery. It works only on new generation keypads, on older ones it cause them to reboot. RF Delinquency triggered and restored on zone 20:
Keypad idle notification is false-positive and zone expander 2 notification is for all 17-24 zone notifications, it can be on wireless/keypad zones not just on zone expanders. I often have RF Deliquency troubles for no reason, but never together with Zone fault (well, this time RF Deliquency/Zone fault was for a reason as I tampered with sensor). I often got "Wireless notification" and 0xE6.25, Module/0xE6 unknown data after exiting from Installer programming and so on. It seems to answer on Module status query but Im not 100% sure. It will help if 0xE6.25/Module0xE6 data afterwards is known (data send after queryes is same as for RF Delinquency trouble restore).
RF Jamming just makes zone tamper on zone programmed for it in RF Module programming.
0xB3 on PC1565-2P panel after activating PGM outputs. PC585 v2.3 doesn't send it:
Downlook remote trigger, section [906] on PC5020, I was able to trigger it without having Downlook module.
KeybusReader.inostill fits into Arduino Uno memory with 32224 bytes (99%) used (commit 4e3c763), even after syncing my fork with latest taligentx:develop commit ee09e9e.