When sending the command OSDP_CMD_FILE_TX after previously had registered a file transfer operation with osdp_file_register_ops the frame sent to the PD is larger than the max capacity of the buffer indicated by PDCAP.
For a reader with the following reported capability:
osdp: CP: DEBUG: Reports capability 'ReceiveBufferSize' (194/1)
Expected behavior:
The expected behavior is to send a FILETRANSFER frame with size of fragment field value <= (194 - frame header), something like
FF 53 00 F2 00 05 7C 01 B4 AF 03 00 00 00 00 00 AF 00 0E 83 03
Observed behavior:
A command frame of size 0xF2 (242) and fragment size of DF (223) is sent which is bigger than the reader's receive buffer size
FF 53 00 F2 00 05 7C 01 B4 AF 03 00 00 00 00 00 DF 00 0E 83 03
After sending this frame the reader does not reply and a timeout happens, most probably because the frame is received incomplete by the reader and discarded
The issue is reproducible 100% of the times
Here is a log with additional prints intended for debugging
When sending the command
OSDP_CMD_FILE_TX
after previously had registered a file transfer operation withosdp_file_register_ops
the frame sent to the PD is larger than the max capacity of the buffer indicated by PDCAP.For a reader with the following reported capability: osdp: CP: DEBUG: Reports capability 'ReceiveBufferSize' (194/1)
Expected behavior: The expected behavior is to send a FILETRANSFER frame with size of fragment field value <= (194 - frame header), something like FF 53 00 F2 00 05 7C 01 B4 AF 03 00 00 00 00 00 AF 00 0E 83 03
Observed behavior: A command frame of size 0xF2 (242) and fragment size of DF (223) is sent which is bigger than the reader's receive buffer size FF 53 00 F2 00 05 7C 01 B4 AF 03 00 00 00 00 00 DF 00 0E 83 03
After sending this frame the reader does not reply and a timeout happens, most probably because the frame is received incomplete by the reader and discarded
The issue is reproducible 100% of the times
Here is a log with additional prints intended for debugging