Siddharth Chandrasekaran

@schmida2 I turned #113 into a [discussion](https://github.com/goToMain/libosdp/discussions/171). ~~Do you mind updating that thread with the most recent version of your proposal? (I think the current link points to the one...

@dhopsonlb, What use case are you targeting? Is it the same as @jason155392? If not, the solution I had in mind (relatively simpler approach) would not work for the general...

One part of the issue is that the PD didn't respond to the file transfer command in time (2 lines above the red arrow in your image). You have to...

@rsgmodelworks, Thanks for your clarification. This seems like an odd design; I expect the main firmware to download the firmware file, verify integrity and put it to some place where...

@rsgmodelworks Thanks again. Will take a look at this issue when I get some free time.

@boobika Did you investigate why the PD took that long to respond to those commands? I will fix the CP to go a bit more easy on slow PDs but...

@boobika Sorry I missed those attachments; but the files seem to be corrupted. Can you check and re-upload the files? ``` tshark: The file "osdp-trace-cp-pd-1-2024-06-27T14_22_10Z.pcap.txt" appears to be damaged or...

After looking at your capture file (with SC), here is what happened (numbers in [] below correspond to the annotations in screenshot above): The CP first received a Card Read...

@boobika I have fixed the PD timeout issue. Now LibOSDP will keep a PD online for up to 8 seconds (see #189 for more info). Closing this ticket as I...

It’s WireShark. See https://libosdp.sidcha.dev/libosdp/debugging#wireshark-payload-dissector to know more.