sidcha
commented
2 years ago From the logs, the CP sent you a CMD_MFG:
OSDP: PD[1]: Received [1f] =>
0000 ff 53 01 1e 00 0d 02 17 80 af 0b 8a 7d 2d d9 82 |.S..........}-..|
0010 c7 df e0 2a 7c d4 b2 66 ce 32 38 ac d9 a7 fd |...*|..f.28.... |
OSDP: CMD: MFG(80) [5] =>
0000 80 00 11 b9 10 |..... |For which your PD replied with:
OSDP: PD[1]: Sent [f] =>
0000 ff 53 81 0e 00 0d 02 16 40 19 69 28 fb 69 a2 |.S......@.i(.i. |Both those are valid OSDP packets. After this, the CP did not send anything for at least OSDP_PD_SC_TIMEOUT_MS (which causes the secure channel session to timeout with the message "OSDP: INFO : PD[1]: PD: PD SC session timeout!").
After this, things get interesting, your PD thinks it sees the next command but that's just the last command sitting in your rx buffer without being removed plus the new command. (notice that the first 31 bytes are identical to CMD_MFG)
OSDP: PD[1]: Received [3f] =>
0000 ff 53 01 1e 00 0d 02 17 80 af 0b 8a 7d 2d d9 82 |.S..........}-..|
0010 c7 df e0 2a 7c d4 b2 66 ce 32 38 ac d9 a7 fd ff |...*|..f.28.....|
0020 53 01 1e 00 0d 02 17 80 af 0b 8a 7d 2d d9 82 c7 |S..........}-...|
0030 df e0 2a 7c d4 b2 66 ce 32 38 ac d9 a7 fd ff |..*|..f.28..... |This caused LibOSDP PD to think that the CP is resending the same packet twice and that produces this error:
OSDP: ERROR: PD[1]: PHY: seq-repeat/reply-resend not supported!Looks like you are causing this issue with your downstream changes. Can you remove any changes you made to pd_decode_packet() and report what errors you are seeing? In essence, what was the issue you faced that prompted you to patch pd_decode_packet()? -- that fix is not right and is causing this problem for you.
nit:
OSDP: PD: Setup complete - @PROJECT_NAME@-@PROJECT_VERSION@ @GIT_BRANCH@ (@GIT_TAG@)
You need to run ./configure which will produce the osdp_config.h which you need to include in your project. Looks like you are including osdp_config.h.in
vk2tds
I am attempting to use LibOSDP with an InnerRange Exception alarm system. I have compiled the library, with some changes onto the STM32 using the Arduino ecosystem.
The exact code I am running lives in the following repositories:
The PD is configured in Install Mode (PD is in INSTALL_MODE)
The PD that I am creating has the ID number of 1. There is an existing device that has the ID number of 0. The full debug log can be found at the following link: (https://pastebin.com/6FgGWAar). Looking at the appropriate lines, it appears that a SC session is created, and then things stop working. Alas, I am not familiar enough with the internal workings of the protocol to know what should be going on.
The pastebin was created using the following PD_CAP
NOTE: I also tried with compliance_level=1. The capture can be found at https://pastebin.com/0guBD9zy
Any hints in getting this working would be appreciated. Thanks.