Patrick José Pereira

> How did you do the install? I installed the extension via the web interface. > Did you restart after doing the install to get that log output? The docker...

> /data/node_modules/@serialport/bindings-cpp Thanks, that did work!

btw this issue is still happening when installing from scratch using node-red 3.1.9 and node-red with node-red-node-serialport 2.0.2

> Workaround for now, while we raise this with the upstream project. > > In `/data/node_modules/@serialport/bindings-cpp` run `npm run rebuild` ~This is not working anymore~

Hi @hardillb, I just run `npm run rebuild` and it fixed the problem! Do you know why is this still necessary ? ``` 6e27a50136db:/usr/src/node-red# cd /data/node_modules/@serialport/bindings-cpp 6e27a50136db:/data/node_modules/@serialport/bindings-cpp# npm run rebuild...

Thanks for the explanation! That makes total sense! Can you link the issue here where you contacted the developer to make it easier for us to track the status ?...

are we there yet ?

Hi Shepherd, sorry for not updating this repository and helping others. This repository was an initial step to create a good BlueROV2 ROS package. But since ROS, Ardupilot and Gazebo...

Try to run the xacro command manually and check the output, it may have something useful.

check the error message: ``` /opt/ros/noetic/share/xacro/xacro.py --inorder /catkin_ws/src/bluerov_ros_playground-master/model/BlueRov2.urdf.xacro ```