Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

modbus issue image v3.1.1

Created by: joshuatreenl at: 6/29/2021 8:08 PM (6 Replies)

Rating (0)

Thanks 0

7 Entries

6/29/2021 8:08 PM	Rate (0)
joshuatreenl Experienced Member Joined: 4/11/2013 Last visit: 8/12/2024 Posts: 56 Rating: (3)	Hi All, Anyone tried the IOT as Modbus-client with the new image v3.1.1 and Modbus version node-red-contrib-modbus v5.13.3? 1. Node Modbus Read used. See attachment: 1_Modbus Read.txt Result: 29 Jun 17:55:21 - [red] Uncaught Exception: 29 Jun 17:55:21 - TypeError: u.pushToQueueByUnitId(...).then(...).catch(...).finally is not a function at Object.<anonymous> (/home/root/.node-red/node_modules/node-red-contrib-modbus/modbus/maps/modbus-client.js:436:7) at emitThree (events.js:136:13) at Object.emit (events.js:217:7) at Object.showStatusActivities [as emit] (/usr/lib/node/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:181:20) at Timeout.a.modbusPollingRead [as _onTimeout] (/home/root/.node-red/node_modules/node-red-contrib-modbus/modbus/maps/modbus-read.js:165:16) at ontimeout (timers.js:498:11) at tryOnTimeout (timers.js:323:5) at Timer.listOnTimeout (timers.js:290:5) 2. Node Modbus Read used, except that the 'Queue commands' are not checked/used. Result: There is communication but every second the message appears: (node:450) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:450) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. Regards, Rene Attachment 1_Modbus Read.txt (924 Downloads)

Suggestion To thank Quote Answer

6/30/2021 5:55 PM	Rate (0)
Fe_lipe Silver Member Joined: 12/12/2016 Last visit: 4/8/2024 Posts: 640 Rating: (60)	Hello Rene, I have not tested the Modbus Nodes in this version yet, but im supposing some incompatibilities as the npm repository mentions following: Node-RED v1.x versions: Node.JS 14.x is supported with v5.14.+ Node.JS 12.x is supported with v5.x Node.JS 10.x is supported with v5.x Node-RED v0.x versions: Node.JS 10.x is supported with v4.x Node.JS 8.x is supported with v3.x Node.JS 6.x is supported with v2.x Node.JS 4.x is supported with v1.x And we are using Node-Red V1.2 together with NodeJS 8. Could you possibly try installing an older version of the modbus nodes (e.g V3) and trying with the same flow? Alternatively you can also share your flow and I can give it a try. BR

Suggestion To thank Quote Answer

6/30/2021 9:42 PM	Rate (0)
joshuatreenl Experienced Member Joined: 4/11/2013 Last visit: 8/12/2024 Posts: 56 Rating: (3)	Hi Fe_lipe, Thanks for your response. The flow is inside the text-file (see previous message). It's a simple flow, ModbusRead + 2 Debug messages at the output. You're right about the versions you mentioned. I had a flashback... I encountered more or less the same issues at the image v2.6.0 See link: modbus issue image v2.6.0 I indeed downgrade to an earlier version of Modbus. I gave it a try: 1. Installing node-gyp --target=v8.17.0 Result: root@iot2000:~# npm -g install node-gyp --target=v8.17.0 node: WARN: Check failed in ../deps/v8/src/deoptimizer.cc:1981 - ignoring /usr/bin/node-gyp -> /usr/lib/node_modules/node-gyp/bin/node-gyp.js npm WARN notsup Unsupported engine for node-gyp@8.1.0: wanted: {"node":">= 10.12.0"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: node-gyp@8.1.0 npm WARN notsup Unsupported engine for semver@7.3.5: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: semver@7.3.5 npm WARN notsup Unsupported engine for make-fetch-happen@8.0.14: wanted: {"node":">= 10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: make-fetch-happen@8.0.14 npm WARN notsup Unsupported engine for tar@6.1.0: wanted: {"node":">= 10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: tar@6.1.0 npm WARN notsup Unsupported engine for lru-cache@6.0.0: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: lru-cache@6.0.0 npm WARN notsup Unsupported engine for cacache@15.2.0: wanted: {"node":">= 10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: cacache@15.2.0 npm WARN notsup Unsupported engine for promise-retry@2.0.1: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: promise-retry@2.0.1 npm WARN notsup Unsupported engine for @npmcli/move-file@1.1.2: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: @npmcli/move-file@1.1.2 npm WARN notsup Unsupported engine for chownr@2.0.0: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: chownr@2.0.0 npm WARN notsup Unsupported engine for mkdirp@1.0.4: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: mkdirp@1.0.4 npm WARN notsup Unsupported engine for p-map@4.0.0: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: p-map@4.0.0 npm WARN notsup Unsupported engine for socks@2.6.1: wanted: {"node":">= 10.13.0","npm":">= 3.0.0"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: socks@2.6.1 + node-gyp@8.1.0 updated 1 package in 155.174s 2 Installing modbus: root@iot2000:~# npm install -g node-red-contrib-modbus@3.1.6 npm ERR! code ETARGET npm ERR! notarget No matching version found for node-red-contrib-modbus@3.1.6. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist. npm ERR! A complete log of this run can be found in: npm ERR! /home/root/.npm/_logs/2021-06-30T18_29_33_220Z-debug.log root@iot2000:~# npm install -g node-red-contrib-modbus@3.6.1 npm WARN deprecated node-modbus@4.3.0: please, use modbus-serial (has tcp and serial) or jsmodbus - contact me to get the package access npm WARN deprecated bson@1.0.4: Fixed a critical issue with BSON serialization documented in CVE-2019-2391, see https://bit.ly/2KcpXdo for more details node: WARN: Check failed in ../deps/v8/src/deoptimizer.cc:1981 - ignoring insta > serialport@6.1.1 install /usr/lib/node_modules/node-red-contrib-modbus/node_modules/serialport > prebuild-install \|\| node-gyp rebuild prebuild-install WARN install EACCES: permission denied, access '/home/root/.npm' gyp WARN EACCES current user ("nobody") does not have permission to access the dev dir "/home/root/.cache/node-gyp/8.17.0" gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/node-red-contrib-modbus/node_modules/serialport/.node-gyp" gyp WARN install got an error, rolling back install gyp WARN install got an error, rolling back install gyp ERR! configure error gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/node-red-contrib-modbus/node_modules/serialport/.node-gyp' gyp ERR! System Linux 4.4.238-cip50 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /usr/lib/node_modules/node-red-contrib-modbus/node_modules/serialport gyp ERR! node -v v8.17.0 gyp ERR! node-gyp -v v5.0.5 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! serialport@6.1.1 install: `prebuild-install \|\| node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the serialport@6.1.1 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/root/.npm/_logs/2021-06-30T18_48_55_195Z-debug.log Next try: root@iot2000:~# npm install -g node-red-contrib-modbus@3.6.1 --unsafe-perm --build-from-source Several message, see attachment for log output. But version v3.6.1 is installed 3. Delete installed version Modbus v5.13.3, e.g. delete the directory... 4. Start node-red It works, no issues/messages (for now of course), even with trace function on. Q: 1. Is this the right way to de-install and install modbus package? I am little bit concerned about the many warning and errors during installation and building the package. 2. Is it possible to upgrade node.js to at least > v10? Rene Remark: There are several issues with Modbus, node-red and node versions. See: Modbus issues Attachment logfile_ModbusBuild.txt (828 Downloads)

Suggestion To thank Quote Answer

7/6/2021 9:26 AM	Rate (0)
bergmanu Platinum Member Joined: 4/28/2015 Last visit: 11/12/2024 Posts: 3345 Rating: (379)	Hi, did you update the modbus node on your own? Because we have version 4.1.3 pre-installed. So I would rather stick to this version than up- or downgrading. For removing nodes you could also use Manage Palette in the node-red menu, but I do not kn ow how it behaves when two version are installed in parallel. Removing the directory should also do the job, but I guess then some dependencies are not deleted, what does not really matter. Installing the modbus node this way is the right one. It is kind of usual, that you get many error during this, but in the end it does work. I don't think that we will patch nodejs 10 to run on the IOT2040 but stick to version 8. Best regards!
	Last edited by: bergmanu at: 07/06/2021 09:27:49 Not working for IOT2050 support anymore from March 1st, 2024. I really enjoyed the time supporting you! :)
Suggestion To thank Quote Answer

7/6/2021 10:44 PM	Rate (0)
joshuatreenl Experienced Member Joined: 4/11/2013 Last visit: 8/12/2024 Posts: 56 Rating: (3)	Hi 'bergmanu', Thanks for your response. 1. I removed the node which I don't use. Simply 'uninstall' didn't worked for me. I removed the nodes by deleting them (/home/root/.node-red/node_modules/). I update the package.json (/home/root/.node-red), removing the deleted nodes. I encountered that during startup of node red, node red 'says' the modules are missing. 2. Next I installed the modbus version (npm install node-red-contrib-modbus@3.6.1). This is the version tested with version v8.x of nodeJS (Fe_lipe mentioned that in the previous discussion). This version is now under test, to see if there are errors Next step: 1. I will install contrib-s7. I read that the beta version is not working, so I will install v2.0.2. and do the final tests to see if it's stable. (I'll hope the problem with ECONNRESET is solved) Although I am very grateful with this forum and new images are launched now and then, for me it would help that in the future no extra node-red modules are installed when a new image is launched OR simply launch two versions, one empty and one with extra modules. Of course I could 'bake' an image myself, I didn't try that. Regards, Rene

Suggestion To thank Quote Answer

4/27/2022 3:07 AM	Rate (0)
JohnCaipa Member Joined: 4/26/2022 Last visit: 4/27/2022 Posts: 1 Rating: (0)	Hi I have the same error, I tried to do what you did but I can't install the library with: npm install node-red-contrib-modbus@3.6.1 --unsafe-perm --build-from-source, the process reaches a point and freezes and it doesn't advance, maybe someone has some other way to use this library in nodered?

Suggestion To thank Quote Answer

4/28/2022 10:03 AM	Rate (0)
bergmanu Platinum Member Joined: 4/28/2015 Last visit: 11/12/2024 Posts: 3345 Rating: (379)	Hi, last week that command did the job for me (see here). Did not encounter a freeze... Either it worked or ended with errors. Best regards!
	Not working for IOT2050 support anymore from March 1st, 2024. I really enjoyed the time supporting you! :)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

SIMATIC IOT2000 Software

Follow us on