Forum Replies Created
-
Posts
-
Glad I could help you.
Don’t hesitate if you need more info.
Now you’re in the fun part, adapting register configuration to your needs, testing and UI implementation…
Took me two weeks because their documentation often mentions registers that are not readable depending on your configuration or system.
The sad part is that not everything is available in the MODBUS Interface of the Logger, you’re short of a lot of detailed variables that you get from directly using Inverter Modbus Interface. If I had a choice, I would’ve used another generic gateway such as Moxa branded ones (they’re fantastic) for each inverter to get all the variables.I did not configure the logger myself but from what is configured in my interface in Wired Network is :
—
— Wired Network
WAN/LAN port working mode : WAN+LAN— WAN & SFP Port Parameters
DHCP : Disable
All static IP fields and dns are set with the IP I’m using to connect to the logger.— LAN Port parameters
Static IP set to some unknown IP that I’m not using and the cable is not pugged in.As for Modbus TCP settings, I already mentionned it before :
—
Link setting : Enable (limited)
Client 1 Ip Address : Your SCADA PC or Server IP
Address mode : Communication address
Logger address : 10
—As for settings in rapid scada communicator, you have it all in github screenshots folder.
Also be aware that Smart Logger has a dynamic mapping by inverter that needs to be calculated from the inverter modbus starting address.
It’s in the documentation.
I had 3 inverters starting from 12 so my config file is based on this.
@oley Oh and also, pay attention to Smart Logger ACL Security.
In Smart Logger Modbus TCP settings, you either need to disable ACLs or add your IP adresses to Client list (limited to 5 in Smart Logger 3000).
—
Link setting : Enable (limited)
Client 1 Ip Address : Your SCADA PC or Server IP
Address mode : Communication address
Logger address : 10
—
At least these settings work for me.Sorry, had a little bit too much things going on so I forgot to provide examples and I forgot to whitelist rapid scada mails last time, so I did not get notifications.
Not sure if there are rules for file sharing links on this forum (I did not find a policy), but you can find the documentation I found online, some screenshots and my Modbus xml config file here on github : https://github.com/odobrev/rapid-scada-examples
It’s a public repository I made just for sharing, think it will be better than a link to my self hosted cloud server.
Hope you find it somehow usefull.
Let me know if you need some more explanations.
The difficult part of “Fault Codes” is that it’s HEX CODED so you need some processing to decode error codes.
That’s what I had to do in Node RED directly, then aggregate to custom fault variables.Good to know.
I didn’t think of this since no one mentionned it when I created this post.Might use this if I have a new Modbus source to implement that requires publishing.
MQTT did not pick my interrest since it’s a paid plugin in my ALERTING software and I already had everything built on OPC UA included in the base licence. Also, MQTT a new protocol for me that I still need to learn.
We were already using Node RED anyway for bacnet compatibility so it was the easy solution for us.
We could’ve actually used Node RED to directly connect to the Modbus Gateway but since we’ve already implemented everything in Rapid SCADA, we did not bother to rewrite everything.
As for data looping, we’re not doing it since it goes like this : Modbus Gateway > Rapid SCADA > Postresql > Node RED > Alerting sotfware (we don’t need the calculated variables in Rapid SCADA itself) but I agree it makes a complicated path.
The way you describe your solution seems about the same complexity for me. You just keep everything in the same software which I agree is better than my solution.Hi,
Sorry, I have missed mail notifications because it got to quarantine.
I’m on holidays right now, but I will come back with the example of how I configured Modbus Next Week.
We are not writing to Modbus since we are only using data for monitoring purposes so I won’t be able to help with this but I did test writing over Modbus TCP/IP to a Moxa E1212 for testing purposes when I was evaluating Rapid SCADA so it does work. You might want to get one since it’s pretty “cheap” compared to an automate and will allow you to test SNMP and Modbus/TCP pretty easily. As for Rapid SCADA, well, it’s free and pretty easy to install…Can’t do better than that !
For implementation, the documentation from Huawei was actually pretty bad. Finding the right documentation for Modbus registers and inverters and getting it right is always a pain in the neck. But it’s not because of Rapid SCADA, it’s always like this with Modbus and actually I did find Rapid SCADA to be the only good tool for this protocol. What I recommend doing is to always use the same model of hardware (same gateway, same inverters, etc.) since you will be able to reuse your template and it will make your life so much easy. You also want to get some float or integer values such as Active Power, Voltages, etc. to be sure that the way you’re reading registers is good. (Especially when you don’t know if the manufacturer is using a base 0 or 1 for adresses)
When possible, I always prefer OPC UA or better SNMP. You always get an MIB file from your manufacturer and with MIB Browser, it’s just a walk in the park to make it right in the SCADA.As for my “calculated variables exporter problem”, what I remember doing for my calculated variables :
– Configure Postgresql server (installed on the same server as Rapid SCADA) and create Postgresql exporter as written in documentation. I tweaked it a little to export only on COV (Change of Value).
– Install Node RED.
– Poll reading Postgresql Database with Node RED.
– Calculate my logic for alarms and aggregates inside Node RED.
– Create an OPC UA Compact Server in Node RED.
– Export my calculated variables to OPC UA server in Node RED.
– Connect my external Software to OPC UA server in Node RED directly.If you need to use these variables in Rapid SCADA, you can just connect to your Node RED OPC UA Compact server and read from it. It will become also available in your Rapid SCADA OPC UA server.
Best regards
