50 likes | 169 Views
Test done: results and findings Next steps. Test done: result and findings. Objectives: monitor the exchange of information between the HP and the PLC during the execution of different commands Analyze this flow of information, to be able to replicate it in the new supervisor
E N D
Test done: results and findings • Next steps
Test done: result and findings Objectives: • monitor the exchange of information between the HP and the PLC during the execution of different commands • Analyze this flow of information, to be able to replicate it in the new supervisor To this purpose, more than 150 files of data were acquired, and software to analyze them was developed (see online demo)
In order to understand what is going on, the analysis cannot neglect the examination of the PLC code • We now start to understand the mechanism for sending commands • We also start to understand the mechanism through which the HP is constantly asking the PLC for information • We still need to study and understand all the details of the PLC-> HP information flow
Next steps • Final Target: The PC replaces the HP • The new supervisor needs to implement the complete functionality • The PLC needs to be able to communicate with the PVSS application through the S7 driver • Intermediate Target: The HP and the PC coexist • In the PLC we must develop the simple code to support the new PC<->PLC communication. This modification will be small but unavoidable (see Jeronimo’s slides), because of the different nature of the HP communication (synchronous) with respect to the PVSS communication (asynchronous) • We should also implement a “flag” mechanism, through which it will be straightforward to switch from HP to PC and vice versa.
Additional tests required • What happens when the supervisor is disconnected? • Once the PC<->PLC communication mechanism is implemented, try to send some commands from the PC