Questions regarding development of pks430 and beyond
Thread Content
This post was last edited by yzdatou on 2016-5-19 at 11:23. It’s my first time working with PKS; the system architecture doesn’t mention anything regarding engineer stations. It seems that everything is based on the severe version, so any operation station should be able to function as an engineer station, as long as it’s connected to the server in order to update the so-called real-time database So, in a project where two people are involved in the development – one responsible for the Control Builder and the other for the HMI Builder – can the former work on the server while the latter uses an operator station (with the screen files then being sent to each machine)?
In PKS, there is no distinction between engineer stations and operation stations; only C stations and F stations exist. C station (console station) data is collected directly from the controller, while F (flex) data is collected from the server. Regardless of the type of station, it is possible to open the Control Builder for configuration and the HMI for drawing. However, the number of Control Builder instances that can be opened is limited by the license, and the diagrams created must be saved in a specific folder on the main server in order to be shared with others. Typically, station F is used as the engineer’s station, while station C serves as the operator’s station; this way, even if the server fails, it does not affect operations at the operator’s station. Keep the software patches on C Station or F Station in sync with those on the server, and configuration can also be carried out on these stations. You can also choose to log in remotely to the server for configuration.
Thank you for the advice. So do all software licenses need to be stored on the server?
Authorization is handled on the server; during the server installation process, there are steps that require you to add the authorization
thank you very much