Info on 0x8D and 0x94 cmds used for keybus communication with wireless expander module #188
Labels
Comments
|
Command 0x94 seems to be used for requesting and getting data from RF module to panel. Probably similar to 0x8D.
0x52 aswell seems to be related to wireless expansion, something for keyfobs? 0xE6.25 after exiting installer programming: |
|
Does anyone have panel version EDIT: as per DSC bulletin panels have Fire Alarm Bells Silenced message. Probably, it is shown when zone defined as [07] or [87] is silenced/delayed but I wasn't able to trigger that message on PC1832 v4.2 with PK5500 v1.1. It will be nice to have that message decoded as well. It could be only keypad-related thing, that keypad itself check if no partition is in alarm and fire alarm is going on but I doubt it as EOL setting would not change that status. Also, it would be interesting to see output from v4.60 with an RFK keypad v1.30 or up, because it uses 3 digits for [804] installer programming subsection and it includes Receiver Placement Test for RF Interference. RFK5564 likely have 0x8D/0x94 byte3 differences for 64 zones. I would put help wanted label on this issue. 0x94 can also be used for other module subsection-programming such as PC5100 2-wire adressable or PC5936 audio interface as it get send after trying to enter their sections but I dont have the modules to verify it: I suppose 0x8D and 0x94 cmds waits to be included in new development branch, after merge of current development branch into master, because as of now, there is no space left for Arduino Uno with KeybusReader.ino sketch. This is an example of entering subsection [20] of section [804] on v5.0 RF module, changing zone 20 ESN from 555555 to 999999: |
|
I've found out that on PC5010 v2.00 panels you can have multiple users having same access code - event buffer will log only the lowest one. Update for 0x94 panel command, byte 4 is always 0x82 when byte 3 contains subsection which was requested to be accessed. More info on Byte4: when its 0x02 it contains HEX data on bytes 5-7. It's way to differ RF5132 v3.x/v5.x versions for 0x8D cmd. However, I'm not so sure that you can differentiate v5.0/v5.1 even for 0x8D. For 0x94 cmd it seems impossible to be sure for which version it's from just single line. |
kricon
added a commit
to kricon/dscKeybusInterface
that referenced
this issue
Jul 1, 2022
Following decoding in taligentx#188 Separated 0x8D and 0x94 cmd, messages only for 0x8D Added checks for printing correct options/data/signal strenght etc Cmd 0x8D data omitted for AVR/Arduino to fit into memory Massively tested with RF5121 v3.14/two v5.0/v5.1 modules
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Command 0x8D seems to be used for programming RF module, and it sends data from panel to RF module after programming entry is done.
Note that PC5102 and RF5108 RF modules have onboard PGM1 and PGM2 outputs and have more programming sections.
Also, there is some difference between versions, earlier only supports 2 partitions and use section 59-60 for assigning function keys to partitions1-2, RF5132 v5.0 assign function keys per partitions1-8 (61-69) and RF5132 v5.1 assign function keys per key1-16 (61-76).
It seems that RF module also save and have record of user codes 17-32 used for keyfobs 1-16. After changing Wls key assign user codes [017][1], you need to enter/remove associated user codes otherwise you wont be able to disarm system.
It's interesting how panel send different Byte3 data for different RF module versions (sample log outputs below), but with checking Byte2 or comparing Bytes6-7 you should be able to differ for what action/section is command send.
This is mostly copy-paste from dump of notes I took thru last days, maybe not nice sorted or labeled out but I've verified byte3 data and sections several times on v3.14, v5.0 and v5.1 rf modules.
Unknown ones can be for earlier versions which supported 4 handheld keypads with 4 function keys per partition (each section for each function) [57]-[64]. [65]-[72] for partition 1/2 function keys 1-4. [90] for handheld keypads partition assingment
The text was updated successfully, but these errors were encountered: