Closed gfcittolin closed 5 years ago
OK I will do a release on npm with the hotfix, I agree it would be nice to fix it properly and join the packets and process the reply as a valid one, but that may not be practical right now.
Thanks once again for merging and publishing it!
Just a side node: if you check the published node, there are some other files there... nothing harmful, only something to cleanup on your checkout there before publishing it ;)
This issue refers to the thread at https://github.com/netsmarttech/node-red-contrib-s7/issues/30#issuecomment-494420638
There's an odd issue when communicating with LOGO! devices, where the last byte is missing in the response telegram, and this last byte arrives later at another telegram. The big issue happens when we try to check if the second packet is valid by checking its header fields, but this second telegram is only one byte length, and a range index error is thrown.
From the previous mentioned issue:
I propose a fix in two steps:
onResponse
, just preventing that we crash the whole process