Field application update
How to make updates to your live systems
- Add a new device as PD 688 to your project assembly and give it a proper name
- Connect the new PD 688 to the desired network, e.g. IP
- Add a visualization for the Configurator (PD_3184-nn - View_for_Configurator) as a Guest view for the new PD 688
- Insert the right serial number for the new PD 688 in your VIGO6 project
- Build the project
- Download the Customware to the PD 688 and see that the download screen appears on the PD 688
- Copy the ‘Output’ folder from the project folder in your VIGO6 library to a SD card. The ‘Output’ folder must be placed in the root of the SD card and the name shall be ‘Output’.
- Insert the SD card in the PD 688
Tips on the COPP hardware modules and peripherals
- be connected via USB
- understand ESC/POS command format
CITIZEN model CT-P293
Special note for the CITIZEN printer. The switches must be set as in the attached pictures in order to function correctly.
IT and Support
When something does not work, look here
- Minimum 3,6 GHz CPU
- Minimum 6 GB RAM
- A SSD-disk
If you want to interface to this component in your overall control component, then do it as a “supervisor-servant”-connenction. Below you see how to access the “level in metres”
The final step is then to select this new “quantity <-> local units relation table” in your project(right click on the project name and select “quantity <-> local units relation table”). You should also add it in your editor (set on the setup screen).
- In VIGO6 you build (and test) a functionality (a component) one time and can use it over and over. No copy paste - you just add the component to your assembly.
- In VIGO6 you have a lot of ready-made components that you can use to construct your project. Eg pump- valve and flow-meter components.
- In VIGO6, the visualisation is tied to a component or assembly, and can be reused over and over.
- In VIGO6, you have better options for maintenance of exsting systems. There are no configurations done directly on the modules (as was the case in VIGO5), so when you locate your project for the system, you know what is running, can make the required updates and then build and download the new program and you are up-and running.
- In VIGO6 a faulty module can be replaced on-the-fly. You simply remove the faulty module and plug in a new one, type in the Serial Number of the new module and you are back in business.
Tip: To add the visualization, you need to find the get/set method of the “Operator_log_in” (see the attached screendump)
Tips and tricks on building awesome visualisations for your components and assemblies
FYI: Process components have a predefined set of frames with pre-programmed “swipe-logic”. They are based on “PD_15399-17 - Swipe_View_for_Process_component_100_x_75”. See https://www.vigo6.com/tutorial-7-control-mode-error-states-conditions/ for examples on how they work. Process assemblies (as e.g. valve or pump) have a special swipe-control which give an “assembly process component” the same swipe-logic as a process component. They are based on “PD_15453-15 - Process_swipe_for_assembly”.
- Fixed in the program to default
- Fixed in the program via Instance constants or set via program
- Login via a visualization where the operator enters his credentials
- Login by using NFC
2: If the language and user access rights must be set to specific values, then PD_17553-xx - Display_interface_control components must be located in the device for each kind of presentation interface (Screen, Printer). This is the predefined configuration when using the PD_13619-xx - PD688_complete assembly. For other devices you must add and locate this Display_interface_control component. Now the power-on Language and User access rights can be set through the instance constants shown here:
Automatic_Logout_at_StartUp must be True. Logout_language_index is set to the required language. Logout_operator_rights must be set for the presentation interface. Or, you can set the Language in your program: Create a connector to the Display_interface_control component and write the following line: Display_interface_control.Display_interface_Language_index.Language_index:= 3 (1 to 4) The value you assign may be a constant (3, in this example) or it may be a variable depending on e.g. a customer record information. As always, remember to connect the connector in your control component. 3: By adding the PD_17553-xx - Display_interface_control to a device you can add a visualization for this component: PD_18202-xx - View for operator define. Through this visualization, the operator can enter his credentials and setup the rights and language as defined in the operator array.
The login view can be covered by the drawing “PD_18207-xx ca_Cover_login_logout_button”, and this must have the hit-test disabled:
The Instance constant Operator_array defines the rights, language, name, password and ID for a group of operators, see more details in the documentation for PD_17553-xx - Display_interface_control. If you are using the PD_13619-xx - PD688_complete assembly, visualizations for Logged-in user and Printer setup are already included in the PD_17616-xx - Setup_PD_688_pushbutton visualization as individual swipe frames, where you can see the operator access rights and select a Language. This way you can have individual Language settings for visualization and printouts. PD_17552-xx - View_for_PD_688_active_operator_data:
PD_20658-xx - View_for_PD_688_printer:
4: Using NFC login is possible for a PD 688. The default setup for setting the language is that both the Display (visualization) and the Printer (printouts via USB) are set to the same language when a user is logging in with an NFC card. The specific language to set is stored on the NFC card. This is the predefined configuration when using the PD_13619-xx - PD688_complete assembly. However, you may wish that any login via NFC will only affect the visualization and the printouts should always have the same language. This is selected by the Instance constant NFC_login_actions in the PD_15627-xx - PD688_NFC_component. Default setting is that the NCF login information is sent to both Screen and Printer. You can now select that the Printer presentation interface is not informed, NFC_login_actions[Printer] = False, and then you can configure your settings for the Printer presentation interface as described in section ‘2’ above.
This can be done in VIGO6 via a pre-built component.
- they take up space, and some visualizations will need to utilize every available pixel for other purposes J
- if a view is set as “non closeable” it makes no sense to have a close button on it.