#Citect scada 2020 how to

You could still do it with three M340 PLCs, one for each device, each PLC with all 20,000 registers, but the customer will have to accept a change order for an additional 2 PLC CPUs, power supplies, backplanes, and NOE modules. The citect devs can't be bothered to look at the data that is available from the devices, understand what is actually useful to the application, design their screens that will use that information, and provide a list of the tags that would even potentially be useful on the HMI, so they have just defaulted to telling you to read 'everything'. The Citect devs were not happy about this and claims I'm trying to push my workload onto them The SCADA developers will be made to provide a proper list with all data they need and we will only handle that. What PLC hardware are you using as the slaves and master exactly ?Дon't forget that Modbus is limited to 125 words in one read so it's going to take some time to get all this back to one central point. Is there a better way to do this? Also, will having the data types in the arrays as INT mess anything up? Is it feasible to just store the ~10000 registers from each device into three huge arrays starting at %MW0-%MW20000 so the SCADA has complete access to all registers?

#Citect scada 2020 how to

The part I'm stuck on right now is how to store the data in the PLC memory to make it available to the SCADA. In testing I've managed to connect and read/write to a Modbus simulator running on PC, I unfortunately do not have access to the devices in the office. I am failry new to Schneider PLCs and am using Unity Pro XL. There is no writing necessary, only writing. Also connected to the PLC is a Citect server that will read all this data and handle it in the SCADA. I am currently working on a project where I need to gather data from 3 separate devices via Modbus TCP.