[bbailey]

Hello all!
Found a USB port on the device and connected as a Modbus RTU service and used @kumajaya ‘s advice and got a Modbus tester application, specifically Modbus Doctor v2.9.
Modbus Test Result

I was polling the same register 0x19 for the battery voltage register value of: 240 (0xEF) [divided by 10 for 24V]

Sadly it indicates that the PLC is not communicating via the the USB port nor the RS485 port at all.

Contacting my distributer to see why this is happening but there shouldn’t be a reason why it is not communicating at all.

Seems that the advice given by @manjey73 changing to RTU is best as it is still RTU and the frames given as examples by the manufacturer match the request made by RapidSCADA

2020-12-21 13:05:49 Establish a TCP connection with 172.16.15.150:23

2020-12-21 13:05:49 Communication session with the Device 4 “RealModbus”, type: KpModbus, address: 5
Request element group “Battery Level Level Test”
Send (8): 05 04 00 19 00 01 E1 89
Receive (0/5):
Communication error!
Request element group “Battery Level Level Test”
Send (8): 05 04 00 19 00 01 E1 89
Receive (0/5):
Communication error!
Request element group “Battery Level Level Test”
Send (8): 05 04 00 19 00 01 E1 89
Receive (0/5):
Communication error!

2020-12-21 13:05:53 Disconnect from 172.16.15.150

I am connected via Port 23 as seen below:

WaveShare Serial Setting

Hopefully the distributor will give answers, maybe the unit is defective.

Anyways I appreciate the help so far, this will be resolved soon!

Much respect!

[bbailey]

No as to get it to the country I am in, especially during Christmas time, the package would take take more than a week to two weeks.

My work needs this to work asap, so lots of pressure haha.

But do you think improper cables are to blame?
(Greetings from Jamaica)

[bbailey]

Greetings @Mikhail, thanks for the response!

The Device ID by default is 5 and so that is my Dev Address in RapidSCADA, along with no call number as recommended for RTU slave devices using this Ethernet-to-RS485 converter.

Regarding the wires used for the RS-485, I am currently using:

three normal (slightly large) power wires to run the short distance of 6 inches during tests. Do you think this will affect its performance?

and not twisted pair as I am in testing. With the terminals: A, B, COM.

Do you think this would cause a problem in communication?

All help is appreciated!

[bbailey]

Hello @manjey73
Changed the Remote Port to 502, because in the tutorial had Port 502 and my team entered it to see if it would make a difference (it did not sadly). Changed it to Port 23 and no difference.

I changed the test to look at only one register (Battery Level, as seen in the request frame example given by the manufacturer
.

I am getting the following result, which matches the above:
2020-12-20 08:30:44 Establish a TCP connection with 172.16.15.150:23

2020-12-20 08:30:44 Communication session with the Device 1 “ActualModbus”, type: KpModbus, address: 5
Request element group “Battery Level Level Test”
Send (8): 05 04 00 19 00 01 E1 89
Receive (0/5):
Communication error!
Request element group “Battery Level Level Test”
Send (8): 05 04 00 19 00 01 E1 89
Receive (0/5):
Communication error!
Request element group “Battery Level Level Test”
Send (8): 05 04 00 19 00 01 E1 89
Receive (0/5):
Communication error!

2020-12-20 08:30:48 Disconnect from 172.16.15.150

I feel it is either the request is somehow incorrect and thus does not get the a response from the slave.

OR

The RS-485 itself is not working as there is no transmission.

In your expertise what do you think is the best solution?

[NOTE: I am not using a shielded twisted pair, but rather three normal (slightly large) power wires to run the short distance of 6 inches during tests. Do you think this will affect its performance?]

[bbailey]

Hello @manjey73 , thanks for the reply!

OK I have done all the changes you recommended and still having errors (but we are on the right path)

Here is the line log:
2020-12-19 11:14:57 Establish a TCP connection with 172.16.15.150:502

2020-12-19 11:14:57 Communication session with the Device 1 “ActualModbus”, type: KpModbus, address: 5
Request element group “Analog Levels”
Send (8): 05 04 00 00 00 28 F1 90
Receive (0/5):
Communication error!
Request element group “Analog Levels”
Send (8): 05 04 00 00 00 28 F1 90
Receive (0/5):
Communication error!
Request element group “Analog Levels”
Send (8): 05 04 00 00 00 28 F1 90
Receive (0/5):
Communication error!

2020-12-19 11:15:00 Disconnect from 172.16.15.150

2020-12-19 11:15:00 Establish a TCP connection with 172.16.15.150:502

2020-12-19 11:15:00 Communication session with the Device 1 “ActualModbus”, type: KpModbus, address: 5
Request element group “Analog Levels”
Send (8): 05 04 00 00 00 28 F1 90
Receive (0/5):
Communication error!
Request element group “Analog Levels”
Send (8): 05 04 00 00 00 28 F1 90
Receive (0/5):
Communication error!
Request element group “Analog Levels”
Send (8): 05 04 00 00 00 28 F1 90
Receive (0/5):
Communication error!

2020-12-19 11:15:04 Disconnect from 172.16.15.150

AND here is are Configuration settings as per recommendation.

The line state is giving this result:
Line 1 “Actual Line”
——————–
State : running
Action : 19/12/2020 11:18:46 Communication with Device 1 “ActualModbus”

Connection Channel
——————
Type: TcpClient
Connection: not established
Custom Parameters
—————–
TransMode = RTU

Common Properties
—————–
Modbus.Templates = Dictionary of 1 templates

Active Devices
————–
1. Device 1 “ActualModbus” : error

It looks much closer to what it should be reading as seen in this link

Looking forward to your response!

[bbailey]

LINK FOR PICS ABOVE (if not available)

[bbailey]

Hello!
I am struggling to install this image pack onto my server. I am using this page to help, however I do not know if it is a server or a webstation plugin.
Where do I put the manosphere.sch?
What is the step-by-step if it is different?
Any help is appreciated!

[Author]

Posts