- Posts: 8
- Thank you received: 2
Scalability / I/O
5 days 1 hour ago #232
by Benito
Scalability / I/O was created by Benito
Hello everyone
I have a question about the scalability of ProView, how much input and output can ProView manage? On this point, is it as efficient as Yokogawa?
I have a question about the scalability of ProView, how much input and output can ProView manage? On this point, is it as efficient as Yokogawa?
Please Log in or Create an account to join the conversation.
21 hours 20 minutes ago #236
by Foxman
Replied by Foxman on topic Scalability / I/O
Hi Benito,
Yokogawa's most powerful controller, the CENTUM VP, is designed to handle up to 15360 data points. It remains unclear how much control logic can still be processed and what cycle times can be used. So the question is not so easy to answer in general terms. BUT:
I am sure that ProviewR can easily exceed this performance – even with one runtime/controller. My largest project to date (building automation) has 4279 data points (Wago remote I/O), all of which are connected via Modbus TCP and processed with a cycle time of 500 ms. The entire system, including 16 operator stations that are accessed remotely and are always active, and including database recording in MySQL (approx. 2500), runs on an Advantec Uno 137 with an Intel® Atom® E3940 processor. The system's idle time is between 90–95%, with the ProviewR-Plc process occupying 10% on one core.
So there is a lot of unused capacity left here, and the performance of the hardware could easily be increased further.
/Martin
Yokogawa's most powerful controller, the CENTUM VP, is designed to handle up to 15360 data points. It remains unclear how much control logic can still be processed and what cycle times can be used. So the question is not so easy to answer in general terms. BUT:
I am sure that ProviewR can easily exceed this performance – even with one runtime/controller. My largest project to date (building automation) has 4279 data points (Wago remote I/O), all of which are connected via Modbus TCP and processed with a cycle time of 500 ms. The entire system, including 16 operator stations that are accessed remotely and are always active, and including database recording in MySQL (approx. 2500), runs on an Advantec Uno 137 with an Intel® Atom® E3940 processor. The system's idle time is between 90–95%, with the ProviewR-Plc process occupying 10% on one core.
So there is a lot of unused capacity left here, and the performance of the hardware could easily be increased further.
/Martin
Please Log in or Create an account to join the conversation.
Time to create page: 0.429 seconds