are you sure that the usb / rs485 converter you are using supports the ModbusRTU protocol?
I found in the old document say that the controller we're using is: Powertran PI9130A 004G3. But I'm not able to test or simulate them yet.
@rromele Yes, I'm very sure that the USB converter supports the Modbus RTU.
Just so we are clear
USB to RS485 is an Electrical conversion
From Universal Serial Bus to RS485
Modbus RTU is a protocol than can even run it over an medium.
After many attempts using different methods. I still can not read the status of the controller.
The following data shows what the setting in the Modbus RTU should be:
Thank you for all the help so far but I cannot really talk to the controller using NodeRed at the moment. Can anyone tell me where to start with?
This is the python code that used to work for the controller: Code
I'm trying to adapt this code to nodered.
@Bond This can be frustrating, just some comments
Does the python code still work? If it does (or even partially) this would give you some clues. I notice in the python code there is a setting for connection to an MQTT broker, if this code works you could setup a broker in Node Red and communicate through MQTT using the working python code.
The python code uses the minimalmodbus python library and only sets the baud rate so the remaining serial settings should be default based on the minimalmodbus docs which is 8N1 so in the modbus config you should try serial expert and set the config to 8 data bits none parity and 1 stop bit.
I used a modbus scanner to initially get the communications working and then scanned the likely registers to read some parameters. This enabled me to fault find towards a solution. The scanner is here
@mtoko thank you for your comments
I have checked out the Modbus scanner. Unfortunately, it cannot be installed on Raspberry PI (or just because i don't know how to).
The python code should be working. However the project requirement stated that we do not need to use MQTT, and need to adapt everything from that python code to a browser-based editor, which is Nodered.
I have a lot of experience with using the FTDI rs485 cables to talk to yaskawa ac drives. I like the node-red-contrib-modbus package myself. It's very simple and has a lot of tweakables.
In your case, it looks like you should have everything you need in your python file to make this work. The biggest thing that messes people up with serial connections is the wiring. Does this controller have separate rs232 and rs485 ports? Most don't. On yaskawa drives, one must jumper the S+ to R+ and S- to R- for rs485, since it uses a differential signal. Also, don't forget the commond wire, which should bond both the Pi and the controller to the same ground potential.
I used the Modbus scanner on a windows computer to get all the communications settings correct (9600, N81) and to ensure that communications with the controller were working including the USB to RS485 converter and confirming modbus registers. With all this working and confirmed it was only necessary to work with Node Red configuration knowing that all else was working
Thank you @gemini86 for your response. I think the wiring is correct now because the python can actually run the fans.
I think the problem now is just trying to get that python file to work in Nodered.
I'm trying to read the status of a working fan (i turned it on physically so it's spinning), but have an error of reading ('sequential dequeue command not possible') as shown in the picture:
This is my setting of the Modbus Read node from node-red-contrib-modbus"
can anyone please help?
What do you have in the 'optionals' tab?
link a Modbus response node to the bottom output and set quantity to less than 100 (it is requesting 100 registers)
The datasheet of your controller shows that the status word is at 1001H (hex), so in the modbus node, that would be 4097 decimal. It also shows the status being 5 words in length. I do not know what the data formatting is, if they're using ieee 754 floating point data words, integers divided by some factor to represent floats, individual bit flags, etc. That's going to be deeper in the drive's actual modbus spec.
optional tab just to show errors and activities. I think for debugging
it does not work, show me the same error. Should i write some command into the register before reading?
Hey Bond, this could likely be a simple issue, but we need the device manual (the full manual) to be able to help out. What did you change the modbus read node to now?
Try reading (function 3) word address 3000, quantity 3.
how did you work out the quantity to be 3?
From the manual you linked. Can't cite the PDF right now, I'm on mobile. Any luck?