Closed mikaelj closed 2 years ago
Not sure how you were able to exceed the capacity of a collection while receiving reply data. What kind of device is the OSDP.Net running?
Are you able to run the library using a debugger? If so, when the error occurs check the size of the replyBuffer collection in the WaitForRestOfMessage method in the Bus class. Double checking the logic, I don't see how it can exceed the max size of a ushort (65,535)
I agree it sounds strange - it shouldn't overflow. According to my OSDP library (ARM Cortex-M3 device) message lengths are between 64 and 110 bytes, and the library I'm using on my end has been in production use for many years. The only new thing is USB CDC ACM...
I'd be happy to try to debug it.
However, I'm a bit of a newbie in Windows development - is there a way i can install a debuggable version of OSDP.Net using the package manager? If not, what's the recommended way?
Not sure if this is the best way...
I switch the reference in the project from the Nuget package to a compiled version of the source code.
Also, are you using the latest version of the Nuget package?
nuget package version 3.0.1.
I'll add the project source code to my own temporarily then. Thanks.
Can no longer reproduce. I think the error is on my part. Closing.
Polling one device over virtual USB-serial. Not using a secure channel. What other information do you need?