# Modbus sendet "Read -\> startIntervalReading node" nach Neuinstallation NodeRed
**URL:** https://discourse.nodered.org/t/modbus-sendet-read-startintervalreading-node-nach-neuinstallation-nodered/91300
**Category:** General
**Created:** [27 September 2024 10:38 UTC](https://discourse.nodered.org/t/modbus-sendet-read-startintervalreading-node-nach-neuinstallation-nodered/91300 "2024-09-27T10:38:12Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@volvog](https://discourse.nodered.org/u/volvog)
#### Post date: [27 September 2024 10:38 UTC](https://discourse.nodered.org/t/modbus-sendet-read-startintervalreading-node-nach-neuinstallation-nodered/91300/1 "2024-09-27T10:38:12Z")
Due to some issues in virtualization I had to re-setup my NodeRed VM. Now the basis is Ubuntu 24.04.1 (before 22.04.5) and Nodered is 4.0.3.
I copied the whole .node-red folder and restarted Nodered. Everything available again.
BUT: Now I often get messages like
"Read -\> resetIntervalToRead node 8eb943eafa5f7625 address: 0X484"
"Read -\> resetIntervalToRead node 5956e716afe1d287 address: 0x584"
"Read -\> startIntervalReading node 8eb943eafa5f7625 address: 0X484"
"Read -\> startIntervalReading node 5956e716afe1d287 address: 0x584"
I haven't had this before?!? What's the reason?
In the modbus server-configuration I deselected already all Logs and Warnings...
Any ideas?
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [27 September 2024 11:08 UTC](https://discourse.nodered.org/t/modbus-sendet-read-startintervalreading-node-nach-neuinstallation-nodered/91300/2 "2024-09-27T11:08:06Z")
> [@volvog](#):
>
> I copied the whole .node-red folder
You should not copy `node_modules`
in fact, you should stop node-red, delete `.node-red/node_modules`, run `npm install` inside `.node-red`
Some nodes have compiled parts and may need rebuilding.
Also, check/ensure all installed nodes are up-to-date.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [27 September 2024 11:20 UTC](https://discourse.nodered.org/t/modbus-sendet-read-startintervalreading-node-nach-neuinstallation-nodered/91300/3 "2024-09-27T11:20:38Z")
Also make sure all your installed nodes are using the latest versions. Check in Manage Palette.
---
### Author:  [@volvog](https://discourse.nodered.org/u/volvog)
#### Post date: [27 September 2024 11:38 UTC](https://discourse.nodered.org/t/modbus-sendet-read-startintervalreading-node-nach-neuinstallation-nodered/91300/4 "2024-09-27T11:38:18Z")
All nodes have been updated...
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [27 September 2024 13:21 UTC](https://discourse.nodered.org/t/modbus-sendet-read-startintervalreading-node-nach-neuinstallation-nodered/91300/5 "2024-09-27T13:21:24Z")
Assuming that you have already followed Steve's advice then you might be best to ask on the [node's github page](https://github.com/BiancoRoyal/node-red-contrib-modbus/issues).
I can see where the message is generated in the code but it is not clear what the significance is.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [26 December 2024 13:21 UTC](https://discourse.nodered.org/t/modbus-sendet-read-startintervalreading-node-nach-neuinstallation-nodered/91300/6 "2024-12-26T13:21:36Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.