Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Catalog
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
🛈
Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

OPC UA Client error in V3.1.1

Created by: Keele at: 12/30/2021 10:51 AM (12 Replies)

Rating (0)

Thanks 3

Result pages:: |; 1 | 2; |

13 Entries

Entries per page: 10 | all

12/30/2021 10:51 AM	Rate (0)
Keele Advanced Member Joined: 6/14/2019 Last visit: 1/31/2023 Posts: 15 Rating: (0)	Hi, I have fully clean format and installed the latest version v3.1.1 into Simatic IOT 2040. However, when i deploy the OPC UA item & OPC UA client node, it having the error "Error: get-installed-path: module not found" May i know what is the issue causing this and how to solve it. Thanks. Attachment Error.JPG (444 Downloads)

Suggestion To thank Quote Answer

12/30/2021 3:01 PM	Rate (0)
bergmanu Platinum Expert Joined: 4/28/2015 Last visit: 2/1/2023 Posts: 3087 Rating: (362)	Hi, I don't know why this happens, but the nodes are installed in another path than displayed here. I have the same behavior and wasn't really able to solve it on the image itself. I tried installing the nodes again with npm install -g node-red-contrib-opcua which solved the issue for OPC UA Client and Item, but not for Server. I need to open an issue on the github page of the Example Image, maybe the R&D knows more about that. Best regards!
	Last edited by: bergmanu at: 02/22/2022 14:49:29
Suggestion To thank Quote Answer

12/31/2021 2:04 AM	Rate (0)
Keele Advanced Member Joined: 6/14/2019 Last visit: 1/31/2023 Posts: 15 Rating: (0)	May i know which location do you install the node? Should i need to remove the original OPC node? npm install node-red-contrib-opcua Meantime, i have check the version of node-red-contrib-opcua in palette, it was version 0.2.88. should i need to update to specific version that can able to use in json v8.17. Why i'm asking this because of 0.2.88 OPCUA node has endpoint error and browse node error in OPCUA client. Thanks.
	Last edited by: Keele at: 12/31/2021 02:05:32 Last edited by: Keele at: 12/31/2021 04:33:20
Suggestion To thank Quote Answer

1/3/2022 8:31 AM	Rate (0)
bergmanu Platinum Expert Joined: 4/28/2015 Last visit: 2/1/2023 Posts: 3087 Rating: (362)	Hi, I did not re-install the installed nodes and ran the command in root directory. But the directory does not really matter, because the -g flag installs it globally. Why do you get errors using the pre-installed nodes? I thought they are not working because of the path error? How do the endpoint and browse errors look like? Do you have a screenshot? Best regards!

Suggestion To thank Quote Answer

2/22/2022 9:10 AM	Rate (0)
DVBHUZ Regular Member Joined: 6/26/2019 Last visit: 2/24/2022 Posts: 18 Rating: (0)	I have the same problem with 3.1.1 image. Is there any way to solve it? Thanks!

Suggestion To thank Quote Answer

2/22/2022 2:58 PM	Rate (0)
bergmanu Platinum Expert Joined: 4/28/2015 Last visit: 2/1/2023 Posts: 3087 Rating: (362)	Hi, did you already try to install the node again. as stated in my first post? Best regards!

Suggestion To thank Quote Answer

2/22/2022 8:17 PM	Rate (0)
DVBHUZ Regular Member Joined: 6/26/2019 Last visit: 2/24/2022 Posts: 18 Rating: (0)	But with what command: a) npm i -g node-red-contrib-opcua@0.2.88 b) npm i -g node-red-contrib-opcua c) npm i -g node-red-contrib-opcua@0.2.xxx The version of node-red-contrib-opcua in the 3.1.1 image is 0.2.88. node version is v8.17.0. npm version is v6.13.4 What version 0.2.xxx of node-red-contrib-opcua should I install? I don't think the latest 0.2.258 is supported. Is there a way to check nodes versions with node and npm version?
	Last edited by: Jen_Moderator at: 02/23/2022 07:09:09 Edited text for better reading.
Suggestion To thank Quote Answer

2/23/2022 7:41 AM	Rate (0)
bergmanu Platinum Expert Joined: 4/28/2015 Last visit: 2/1/2023 Posts: 3087 Rating: (362)	Hi, back in December the latest version was working with the command npm install -g node-red-contrib-opcua But I don't know which version that was, probably something from 0.2.294 to 0.2.254. I can't find any information whether something has changed fron those versions to the current version 0.2.258. If possible, please try to install the current version. Best regards!

Suggestion To thank Quote Answer

2/23/2022 11:19 AM	Rate (0)
DVBHUZ Regular Member Joined: 6/26/2019 Last visit: 2/24/2022 Posts: 18 Rating: (0)	I have proceed with this command: npm install -g node-red-contrib-opcua the result is below: npm WARN notsup Unsupported engine for chalk@4.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: chalk@4.1.2 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 hexy@0.3.4: wanted: {"node":">=10.4"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: hexy@0.3.4 npm WARN notsup Unsupported engine for ltx@3.0.0: wanted: {"node":">= 12.4.0"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: ltx@3.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 yargs@17.2.1: wanted: {"node":">=12"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: yargs@17.2.1 npm WARN notsup Unsupported engine for update-notifier@5.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: update-notifier@5.1.0 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/node-red-contrib-opcua/node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"ia32"}) npm WARN notsup Unsupported engine for is-installed-globally@0.4.0: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: is-installed-globally@0.4.0 npm WARN notsup Unsupported engine for boxen@5.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: boxen@5.1.2 npm WARN notsup Unsupported engine for is-npm@5.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: is-npm@5.0.0 npm WARN notsup Unsupported engine for wrap-ansi@7.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: wrap-ansi@7.0.0 npm WARN notsup Unsupported engine for camelcase@6.3.0: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: camelcase@6.3.0 npm WARN notsup Unsupported engine for type-fest@0.20.2: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: type-fest@0.20.2 npm WARN notsup Unsupported engine for global-dirs@3.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: global-dirs@3.0.0 npm WARN notsup Unsupported engine for ini@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: ini@2.0.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 yargs-parser@20.2.9: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: yargs-parser@20.2.9 npm WARN notsup Unsupported engine for y18n@5.0.8: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your version of node/npm: y18n@5.0.8 After reboot the node opcua version is the same 0.2.88. Is any way to check node & npm versions with nodes version before installing it? Attachment 20220223 Same Version node-red-contrib-opcua.zip (261 Downloads)

Suggestion To thank Quote Answer

2/23/2022 12:08 PM	Rate (0)
bergmanu Platinum Expert Joined: 4/28/2015 Last visit: 2/1/2023 Posts: 3087 Rating: (362)	Hi, I was able to install the version 0.2.254 via npm install -g node-red-contrib-opcua@0.2.254 Sometimes you can find the supported NodeJS versions of the nodes on flows.nodered.org or on the github page of the nodes. Best regards!

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

SIMATIC IOT2000 Programing

Follow us on