Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

node-red-contrib-modbus on armv6 platform not loading (unsupported?)

See original GitHub issue

Problem

I can’t install the module on a RPiZeroW which is an ARMv6 architecture

Current behavior

npm install works correctly (also compiles correctly from source), but node-red crashes trying to load the module saying that “armv6” is not supported (not very verbose)

Expected behavior

actually I would expect that the module works fine if compiled from source

Minimal reproduction of the problem with instructions

get a dietpi (or whatever) install on a PiZeroW (armv6 platform)
install node-red
run npm install node-red-contrib-modbus (optionally build it from source)
restart node-red

Your Environment

Please tell us about your environment:

(X ) I am using just the Node-RED package and got modbus-serial package
( X) I have installed modbus-serial package global from source (using git clone)

Yes, modbus-serial is the name but it does all, TCP and Serial. The node-modbus package is just for the Modbus Server node.

Device :
- (X) Raspbian: v
  - Name: Dietpi (a Debian/Raspbian derivate)
  - Version: v8.6.1
node-red-contrib-modbus version: v5.21.2
node-red: v2.1.4
npm:
npm -v= 8.3.0
Node: node --version = v17.3.0

Issue Analytics

State:
Created a year ago
Comments:9 (4 by maintainers)

Top GitHub Comments

1reaction

belveder79commented, Jul 29, 2022

You are totally right; v12 or v14 certainly suffice;

the origin of the issue comes from the fact that distros usually move forward with versions for frameworks regardless of incompatibilities of applications like node-red arising from that.

Still the real problem is that at this point just everything fails for the non-expert in Linux; for the rest of us, it is just tedious to get a particular install of node outside the distro system and fix a few startup scripts, but that’s doable and no pain…

1reaction

belveder79commented, Jul 25, 2022

Thx for the hints… I finally figured out that it seems to be an incompatibility with node v16/v17 particularely on armv6. I now start node-red with --no-expose-wasm and it works as expected. I found out through this post that it seems to be connected to the dropped WASM support?

Top Results From Across the Web

WASM usage causes Node 16.1+ crash on ARMv6 #41402

I understand WASM support for ARMv6 has been removed in Node 16.1+ which is fine. But unfortunately the above code causes a hard...

Failed to install: node-red-contrib-modbus - #13 by santos - General ...

I think I know where the problems are. I uninstalled node-red. But then I have realized that ubuntu has it integrated. With node-red...

ARMv6-M Architecture Reference Manual - Arm Developer

This manual documents a substantially reduced version of the ARMv7 Microcontroller profile. This architecture variant aligns strongly with the ARMv6 Thumb ...

How to automate the setup of a UC-3100 Moxa gateway device

The public ssh key is not sensitive so we can just copy this in here in ... The new qbee.io platform offers another...

node-red-contrib-modbus - bytemeta

Modbus RTU connection not working ... node-red-contrib-modbus on armv6 platform not loading (unsupported?) JorgeAlberto91MS. JorgeAlberto91MS CLOSED.