Ethernet-ip crash node-red

Industrial
1

Hi Folks,

Have the cip-ethernet-ip driver setup with a ControlLogix CPU to write some data to a couple of tags. For the most part it was very easy to setup. After the flow runs for some time it crashes the node-red instance in docker.....wondering if anyone has seen this before?

Thanks.

21 Jul 03:14:39 - [error] [eth-ip endpoint:PLC_80] Error communicating with the PLC: Error: <SCAN_GROUP>

Unrecognized Type Passed Read from Controller: 0

``

21 Jul 03:14:39 - [red] Uncaught Exception:

21 Jul 03:14:39 - RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4

at boundsError (internal/buffer.js:49:9)

at Uint8Array.readUInt32LE (internal/buffer.js:181:5)

at Object.header.parse.buf [as parse] (/data/node_modules/ethernet-ip/src/enip/encapsulation/index.js:230:22)

at Controller._handleDataEvent (/data/node_modules/ethernet-ip/src/enip/index.js:240:41)

at Controller.emit (events.js:198:13)

at addChunk (_stream_readable.js:288:12)

at readableAddChunk (_stream_readable.js:269:11)

at Controller.Readable.push (_stream_readable.js:224:10)

at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

npm ERR! code ELIFECYCLE

npm ERR! errno 1

``

npm ERR! node-red-docker@1.3.5 start: node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"``

npm ERR! Exit status 1

2

That sounds like the sort of error that should be raised as an issue with the author of that node.

3

Also sounds like an invalid assumption by the author. Have you recently updated the node or a dependency? Or some other software. It is the kind of error that creeps in with a new version of some dependency.

4

Is that a datatype mismatch?

5

No, it is what it says. The number 4 was sent which is larger than the max allowed (3).

6

Did you open an issue in the repository of the node?

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.