Intellicenter rs485 communication stopped suddenly

[lockeandev]

My njs-pc has been running fine for over a year. One day last week the connection between my OCP and njs-pc went down. The tx/rx lights were not flashing on my USB serial adapter so I thought I'd replace it. Just replaced it and no change. I didn't make any changes to my system in the last year let alone the last week.
I'm using this adapter: https://a.co/d/d130jbJ

I have not migrated the intellicenter to the pentair home app, and I'm still on firmware version 1.064.

my dash panel looks like this:

Any suggestions on how to get back up and running?

[rstrouse]

Go to the configuration and double check the port settings. Is the serial port opening and data is just not being sent?

[lockeandev]

Sorry, where do I check that? I don't see any port settings in dash panel.

[rstrouse]

Click on the gears menu then open the Controller -> Comms tab. There you should see the primary port. Your settings should be to the USB port but I am using the serial adapter on a Sequent card.

[lockeandev]

I don't see any tabs on the configuration screen.

[rstrouse]

This looks like njsPC is not running. Click on the hamburger menu and make sure you have dashPanel pointing to a valid njsPC server under the connections tab.

[lockeandev]

It is pointed to a valid server. But logging on to the pi that runs it, and looking at pm2 monitor. It is not able to start. But I don't understand what's wrong.

[rstrouse]

Lets first start with any changes you have made. Did you install a new version of anything on the pi?

[lockeandev]

No, no changes before I lost connection. I did just pull changes for njsPC and dashPanel but then I can't remember what to do to update with the changes.

…

On Sat, Jan 20, 2024, 11:55 AM rstrouse ***@***.***> wrote: Lets first start with any changes you have made. Did you install a new version of anything on the pi? — Reply to this email directly, view it on GitHub <#886 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVWJ2U6I2SOCZMAGYMT7HTYPQHLZAVCNFSM6AAAAABCC4C3KKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCOJSGU4DK> . You are receiving this because you authored the thread.Message ID: <tagyoureit/nodejs-poolController/repo-discussions/886/comments/8192585@ github.com>

[rstrouse]

First lets get you updated on nodejs. v14 is too old.

Type the following command in a console.
nvm ls

[lockeandev]

Command not found

…

On Sat, Jan 20, 2024, 12:01 PM rstrouse ***@***.***> wrote: First lets get you updated on nodejs. v14 is too old. Type the following command in a console. nvm ls — Reply to this email directly, view it on GitHub <#886 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVWJ2RSN7NBQGVC3L7GDK3YPQH65AVCNFSM6AAAAABCC4C3KKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCOJSGY2DO> . You are receiving this because you authored the thread.Message ID: <tagyoureit/nodejs-poolController/repo-discussions/886/comments/8192647@ github.com>

[rstrouse]

Did you get any errors when running the previous commands?

[lockeandev]

nothing other than warnings to run "npm audit fix"
This is the out put from nvm ls now:

pi@poolraspi:~/relayEquipmentManager $ nvm ls
-> v18.19.0
system
default -> 18 (-> v18.19.0)
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v18.19.0) (default)
stable -> 18.19 (-> v18.19.0) (default)
lts/* -> lts/iron (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.12 (-> N/A)
lts/fermium -> v14.21.3 (-> N/A)
lts/gallium -> v16.20.2 (-> N/A)
lts/hydrogen -> v18.19.0
lts/iron -> v20.11.0 (-> N/A)

[rstrouse]

Run the following commands

pm2 stop all
cd ~/nodejs-poolController
npm start

[lockeandev]

`pi@poolraspi:~/nodejs-poolController $ npm start

[email protected] start
npm run build && node dist/app.js

[email protected] build
tsc

Init state for Pool Controller
[1/20/2024, 1:41:27 PM] info: The current git branch output is master
[1/20/2024, 1:41:27 PM] info: The current git commit output is aa0ec31
[1/20/2024, 1:41:27 PM] info: Starting up SSDP server
[1/20/2024, 1:41:27 PM] info: Init mqtt interface: MQTT
[1/20/2024, 1:41:27 PM] info: Initializing MQTT client MQTT
[1/20/2024, 1:41:27 PM] info: Init rem interface: Relay Equipment Manager
[1/20/2024, 1:41:27 PM] info: Opening Relay Equipment Manager socket on http://192.168.0.82:8080
[1/20/2024, 1:41:27 PM] info: Server is now listening on 0.0.0.0:4200 - 192.168.0.82:4200
[1/20/2024, 1:41:27 PM] info: Serial port: /dev/ttyUSB0 request to open successful 9600b 8-none-1
[1/20/2024, 1:41:27 PM] info: Checking njsPC versions...
[1/20/2024, 1:41:27 PM] info: Starting Pool System intellicenter
[1/20/2024, 1:41:27 PM] error: Relay Equipment Manager socket connection error: Error: websocket error
[1/20/2024, 1:41:27 PM] info: Auto-backup initialized Last Backup: 2024-01-07T15:14:32.812-0700 Next Backup: 2024-01-14T15:14:32.812-0700
[1/20/2024, 1:41:28 PM] info: MQTT connected to mqtt://192.168.0.91:1883
[1/20/2024, 1:41:28 PM] info: MQTT: TOPIC IGNORED, SYSTEM NOT READY Inbound intellicenter-i8ps/state/chlorinator: {"id":1,"poolSetpoint":8}
[1/20/2024, 1:41:29 PM] info: Found Controller Board IntelliCenter i8PS, awaiting installed modules.
[1/20/2024, 1:41:29 PM] error: Relay Equipment Manager socket connection error: Error: websocket error
[1/20/2024, 1:41:29 PM] info: Checking njsPC versions...
[1/20/2024, 1:41:29 PM] info: Checking njsPC versions...
INTELLICENTER MODULES DETECTED, REQUESTING STATUS!
[1/20/2024, 1:41:30 PM] info: Initializing Nixie Controller
Checking IntelliCenter configuration...
[1/20/2024, 1:41:30 PM] info: Initializing chemController REM Chem1
[1/20/2024, 1:41:30 PM] info: Nixie Chemical orp object created
[1/20/2024, 1:41:30 PM] info: Nixie Chemical ph object created
[1/20/2024, 1:41:30 PM] warn: REM Server not Connected
[1/20/2024, 1:41:30 PM] info: Nixie Controller Initialized
[1/20/2024, 1:41:30 PM] info: Requesting IntelliCenter configuration
[1/20/2024, 1:41:30 PM] info: Queued 33 configuration items
RS485 Stats:{ "bytesReceived": 478 "success": 24, "failed": 1, "bytesSent": 25, "collisions": 2, "failureRate": 4.00% }
[1/20/2024, 1:41:32 PM] info: Checking REM Connection njsPC - automatic 192.168.0.82:4200
[1/20/2024, 1:41:32 PM] error: Error getting hostnames for njsPC REM connection
[1/20/2024, 1:41:32 PM] error: Error sending Request: PUT /config/checkconnection/ connect ECONNREFUSED 192.168.0.82:8080
[1/20/2024, 1:41:32 PM] error: Error Sending REM Request: PUT /config/checkconnection/ Error sending Request: PUT /config/checkconnection/ connect ECONNREFUSED 192.168.0.82:8080
[1/20/2024, 1:41:32 PM] error: Error establishing bi-directional Nixie/REM connection: Error: initConnection: Error sending Request: PUT /config/checkconnection/ connect ECONNREFUSED 192.168.0.82:8080
RS485 Stats:{ "bytesReceived": 1292 "success": 45, "failed": 2, "bytesSent": 207, "collisions": 2, "failureRate": 4.26% }
RS485 Stats:{ "bytesReceived": 1437 "success": 52, "failed": 3, "bytesSent": 233, "collisions": 2, "failureRate": 5.45% }
[1/20/2024, 1:41:35 PM] error: Relay Equipment Manager socket connection error: Error: websocket error
RS485 Stats:{ "bytesReceived": 1664 "success": 61, "failed": 4, "bytesSent": 259, "collisions": 2, "failureRate": 6.15% }
RS485 Stats:{ "bytesReceived": 1813 "success": 67, "failed": 5, "bytesSent": 285, "collisions": 2, "failureRate": 6.94% }
RS485 Stats:{ "bytesReceived": 2029 "success": 75, "failed": 6, "bytesSent": 311, "collisions": 2, "failureRate": 7.41% }
RS485 Stats:{ "bytesReceived": 2141 "success": 79, "failed": 7, "bytesSent": 324, "collisions": 2, "failureRate": 8.14% }
[1/20/2024, 1:41:40 PM] warn: REM Server not Connected
RS485 Stats:{ "bytesReceived": 2901 "success": 96, "failed": 8, "bytesSent": 493, "collisions": 2, "failureRate": 7.69% }
[1/20/2024, 1:41:42 PM] error: Relay Equipment Manager socket connection error: Error: websocket error
RS485 Stats:{ "bytesReceived": 3106 "success": 105, "failed": 9, "bytesSent": 519, "collisions": 2, "failureRate": 7.89% }
RS485 Stats:{ "bytesReceived": 3293 "success": 111, "failed": 10, "bytesSent": 545, "collisions": 2, "failureRate": 8.26% }
RS485 Stats:{ "bytesReceived": 3479 "success": 119, "failed": 11, "bytesSent": 571, "collisions": 2, "failureRate": 8.46% }
RS485 Stats:{ "bytesReceived": 3552 "success": 121, "failed": 12, "bytesSent": 584, "collisions": 2, "failureRate": 9.02% }
RS485 Stats:{ "bytesReceived": 3722 "success": 128, "failed": 13, "bytesSent": 610, "collisions": 2, "failureRate": 9.22% }
[1/20/2024, 1:41:48 PM] info: Pruning auto-backup file: /home/pi/nodejs-poolController/backups/2023-12-10_15-13-32.zip
[1/20/2024, 1:41:48 PM] info: Last auto-backup 2024-01-20T13:41:47.954-0700 Next auto - backup 2024-01-27T13:41:47.954-0700
[1/20/2024, 1:41:50 PM] info: Configuration Complete
[1/20/2024, 1:41:50 PM] warn: REM Server not Connected
^CShutting down open processes
[1/20/2024, 1:41:58 PM] info: Shut down sys (config) object timers
Stopping sys
[1/20/2024, 1:41:58 PM] info: Closing chemController 50
[1/20/2024, 1:41:58 PM] warn: Cannot send PUT /state/device/i2c:1:4:1 to Relay Equipment Manager server is not connected.
[1/20/2024, 1:41:58 PM] info: State process shut down
[1/20/2024, 1:41:58 PM] info: Serial Port 0 - /dev/ttyUSB0 has been closed.
[1/20/2024, 1:41:58 PM] info: Successfully closed portId 0 for serial port /dev/ttyUSB0
[1/20/2024, 1:41:58 PM] info: Closed all serial communications connection.
[1/20/2024, 1:41:58 PM] info: Shut down MDNS Server mdns
[1/20/2024, 1:41:58 PM] info: Stopped SSDP server: ssdp
[1/20/2024, 1:41:58 PM] info: Successfully shut down MQTT Client
[1/20/2024, 1:41:58 PM] info: Stopped REM Interface Server Relay Equipment Manager
[1/20/2024, 1:42:00 PM] info: Stopping logger Process.
Logger Process Stopped
`

[rstrouse]

You need to reinstall pm2 so that it uses node 18. We already installed node 18 so pm2 needs to be reinstalled.

npm install pm2 -g
pm2 update
pm2 unstartup
pm2 start ecosystem.config.js
pm2 save
pm2 startup

Then copy the command that pm2 shows in the console and run it.

[lockeandev]

Done. Still getting the same error.

Updated with screenshot.

[lockeandev]

ok, so now dashPanel and njsPC are back to normal, but now it looks like REM has a problem with the new NODE version:

[lockeandev]

ok, I rebuilt and installed REM, and it launches and connects to njsPC but now everything I have configured on REM is gone. I had atlas ph orp and temp sensors, a sequent smart fan card and sequent relay card all properly configured before, but they are gone. I have file system backups of the pi, and I think some backups from dashPanel maybe, but is there any way to recover my previous setup from those files?

[rstrouse]

All the configuration for REM is in the data directory. Simply restore the files from your backup.

Shut down REM before you restore it though.

[lockeandev]

perfect. Thank you I am back up and running again!

[rstrouse]

The major version node transitions are sometimes painful. Especially v14 to v18. Glad we got it all worked out.