which Modbus Driver ? - Sungrow Logger 1000A

Alan 3 days ago

i have a Sungrow (Brand) - model 1000A Logger for a solar energy system.

i can easily communicate (using Modbus CAS Scanner - freeware tool) to the unit and it returns valid data in correct format as i expect.

however, when i use plant SCADA 2023R2 comms with same settings i cannot connect to it?

does anyone have any experience with comms to these loggers? currently i am using MODNET (which has been successful with about 20 other Modbus TCP devices i have) i was going to try the others, but it looks like there is a vast amount of differing Modbus drivers.

0 Alan 3 days ago

i forgot to mention i am using the Modbus CAS Scanner tool on the same machine as my SCADA server so that eliminates any issue with networking or connectivity on the physical side.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Kelvin 2 days ago

2 reasons i could think of.

1. The register to initialize comms with Sungrow 1000A is not the default (eg. 40001) i cant recall what. but for you can try look at [MODNET] IntiVar parameter to set the register for MODNET driver to have a successful read to intiialize comms.

2. Sungrow 1000A rejects comms with attempt to read out of range registers. as MODNET reads in block (of 16 registers. You maybe have 40001, 40002 valid. but then 40003 to 40015 is not valid. Device returns error.

One way to try out is prefix G to variable tag address.

Why Vijeo Citect shows #BAD variables while communicating to OTB1E0DM9LP over modnet Protocol? | Schneider Electric Egypt and North East Africa
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel