Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
Apparently, this was a permission issue; it doesn't apply to administrators, so I didn't even know it was there...
Anyway, I've adjusted the file upload permissions for registered users; please try again.
@vladimir Sorry for the delay. Upload symbol is there but I get an error that file is too big. The log is 1Mbyte in size. Is there a way to reduce the size once the log is loaded into IO Ninja?
Thanks.
[0_1709752179535_BACnet_38400_heavery_traffic_error_v4.njlog](Uploading 100%)
No prob, I've increased the upload file size limit to 8MB.
Also, you could have archived it with 7z
7z
@vladimir Here is a log that is working very well until time stamp 9:55:07 +00:46.470 and then the decode stops.
Thanks again for all the help.
BACnet_38400_heavery_traffic_error_v4.7z
Try the updated analyzer:
BacNetMsTp.7z
It checks CRCs now and discards frames with broken headers (in the previous log, the decoder didn't actually stop, but because a broken header specified a very long payload size, it kept buffering data assuming it still was a payload).
Also, when you upload the log, please detach the Analyzer before saving the log. This way, we can access the original raw & unprocessed data (instead of the already decoded frames).
@vladimir Looks really good. I'm going to send this log over to our BACnet stack supplier to see if he has any extra feedback. To me this looks much better than running a 485 to USB connection into WireShark.
Thanks again for all the help. Any chance you could release this into your standard layer plugins?
BACnet_38400_heavery_traffic_error_v5.7z