3/27/2023 12:21 PM | |
Joined: 12/14/2020 Last visit: 11/29/2023 Posts: 10 Rating:
|
Hello, I was working with NodeRED and specifically the preinstalled OPCUA package. Found a couple of bugs there which they fixed. Now I need to update the package to test it. When I've updated the package, I did receive an error saying that I require version of "node>=15". So I installed version 16.19.1 using npm and NodeRED server does not start anymore. Could you, please, walk me though the process of "node" package update or provide me with a link describing said thing? Cheers, Jiri |
3/28/2023 6:35 AM | |
Joined: 10/22/2020 Last visit: 10/1/2024 Posts: 169 Rating:
|
Hi kubesji, I guess that the versions of your components like NodeRED and the OPCUA package you updated and Node are no longer compatible with each other. In order to be able to help you, we need the following additional information:
We look forward to solving your problems together. BR |
3/28/2023 9:01 AM | |
Joined: 12/14/2020 Last visit: 11/29/2023 Posts: 10 Rating:
|
Hello, cheers for fast reply. Currently, node-red commands return segmentation fault. I'm using Example Image v1.2.2 and node-red shipped with this image. The newly installed version of node is 14.21.3. Jiri |
Last edited by: kubesji at: 03/28/2023 09:05:01 |
|
3/28/2023 10:41 AM | |
Joined: 10/22/2020 Last visit: 10/1/2024 Posts: 169 Rating:
|
Hey, as you mentioned in the first post, your updated blocks require a node version > 15. I assume that you currently have these blocks active in one of your flows and that this is causing NodeRED to fail on startup. So please try to start Node-RED without starting the flows. This allows you to open the faulty flow in the editor and make changes without running anything. When you deploy your changes, the flows are then started:
Following these instructions, it is possible to update Node and NodeRED. Please note that newer versions of Node and NodeRED can have a significant impact on all packages you have installed so far, and you may encounter difficulties elsewhere in favour of the more recent OCPUA modules. BR |
3/28/2023 11:27 AM | |
Joined: 12/14/2020 Last visit: 11/29/2023 Posts: 10 Rating:
|
Still getting segmantation fault even with --safe. I do not mind reflashing my sd card with a clean image v1.2.2 to restore. What I need help with is how to update "node" without breaking anything. JK |
3/28/2023 1:31 PM | |
Joined: 10/22/2020 Last visit: 10/1/2024 Posts: 169 Rating:
|
Hi Kubesji, we'll need to test it on our side before providing a solution. Can you please confirm which version of the OPCUA package you're planning to use? Is it the latest 0.2.303 version? Thanks and regards |
3/29/2023 10:37 AM | |
Joined: 12/14/2020 Last visit: 11/29/2023 Posts: 10 Rating:
|
Hi apastore, yes, the latest one. It was 0.2.302 when I check last time but if a new increment is available, I'll go with that one. Cheers. |
3/29/2023 11:46 AM | |
Joined: 6/8/2018 Last visit: 2/3/2025 Posts: 113 Rating:
|
Hi, I update nodejs + node red with cmd : make a backup before node js:
node red:
|
Last edited by: rfond at: 03/29/2023 11:49:49 |
|
This contribution was helpful to
1 thankful Users |
4/3/2023 1:39 PM | |
Joined: 12/14/2020 Last visit: 11/29/2023 Posts: 10 Rating:
|
Cheers, it works now. The only tiny downside is that NodeRED does not start on startup but that should be an easy fix. Cheers again, Jiri |
This contribution was helpful to
1 thankful Users |
4/4/2023 2:15 PM | |
Joined: 4/28/2015 Last visit: 2/26/2025 Posts: 57 Rating:
|
Please see the next post. |
Last edited by: libsch79 at: 04/04/2023 17:57:40Last edited by: libsch79 at: 04/04/2023 17:58:37 |
|
We are working on a new user interface with better overview and more relevance.
To explore the new Forum, you can follow the textbox in the right column, which will lead you to the corresponding page in the new Forum. Alternatively, you can start from the main page by following this link:
https://sieportal.siemens.com/en-ww/support/forum
In the coming days, we will update the configuration step by step, so that you are directed to the new Forum by default. The “classic Forum” will remain available for all known functionalities alongside the new one.
We are thrilled to finally share the future of our Forum with you. Thank you for your commitment!
Kind regards,
the Forum Support Team
Follow us on