Jump to content

SUNSPEC protocol over MODBUS TCP - PV Plant sensors - SCADA


Recommended Posts

Hello,

i have a solar project with modbus RTU on the field, and also modbus TCP using SUNSPEC protocol. This is a standardized protocol to the Solar vendors (specific values to specific registers for inverters , voltage, current etc).  At the same time we have the SCADA from the grid operator to make the inverter control on power curve and power facor. Grid operator also needs some values to pass from modbus RTU and also from Modbus TCP. to him. So we are talking for a modbus TCP Server ? or client ?

Main functionalities:

----------------------------

1. SCADA operation -  (sim card machine to machine system provided by grid operator)

2. Data acquisition from enviromental sensors on modbus RTU

3. ability to pass those values to modbus TCP

4. ability to rephrase values to SUNSPEC over modbus TCP for portals

5. Ability to export to third party energy management portal

6. inverters control

 

What hardware i need to make all this work out ? Thank you.

Link to comment
Share on other sites

  • MVP 2023

Any of the Unitronics Vision or UniStream PLCs can be a blank slate capable of both Modbus RTU and Modbus TCP communication in both Master and Slave mode at the same time.  Whether a unit is a server or client depends on the point of view of data flow, but generally the "Server" is the slave and the "Client" is the master.  

Your requests #1 and #5 are kind of ambiguous and need more details. 

As to what hardware you need, I would lean toward the UniStream family as it has much more powerful networking capabilities and the Modbus is easier on it.  All you have to decide is how big the display needs to be and a list of I/O connected to it.

Joe T. 

Link to comment
Share on other sites

3 hours ago, Joe Tauser said:

Any of the Unitronics Vision or UniStream PLCs can be a blank slate capable of both Modbus RTU and Modbus TCP communication in both Master and Slave mode at the same time.  Whether a unit is a server or client depends on the point of view of data flow, but generally the "Server" is the slave and the "Client" is the master.  

Your requests #1 and #5 are kind of ambiguous and need more details. 

As to what hardware you need, I would lean toward the UniStream family as it has much more powerful networking capabilities and the Modbus is easier on it.  All you have to decide is how big the display needs to be and a list of I/O connected to it.

Joe T. 

Hello and thanks for the support.

#1 SCADA communication with the grid operator might be stand alone to the inverters from this system (machine to machine sim card operated already provided from grid operator). They are going to provide the values of power factor , power limitation , power offset etc.. this values we have to pass to inverters through modbus RTU over RS485. (for control). I'm waiting from inverters provider to confirm that, but the idea would be like that.  What you recommend for that ?

#5 Ability to export on third party energy management portal - can be done in 2 basic ways.

1. send CSV file to FTP and the platform will do the handling to the database

2. have another one modbus TCP  "Server" available (for the third party portal) with all the values available !!  In that case, how we are going to pass values from one modbus TCP Server to another?  What if we have irradiation sensor sitting on the MODBUS RTU site somewhere in the field, and this value must be passed to everyone !! grid operator, inverter portal through SUNSPEC and third party portal.  This is as complicated might be. nothing more.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

This site uses cookies. By clicking I accept, you agree to their use.