Field application update
How to make updates to your live systems
Program download with PD 688If you require new features or program changes in a project, and you want to use a PD 688 as a device for download, then you can do the following steps.
STEP 1:Make the updates you want to your project.
STEP 2: Prepare the downloader PD 688
- Add a new device as PD 688 to your project assembly and give it a proper name.
- Connect the new PD 688 to your chosen network, for example 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 shows on the PD 688.
- Copy the ‘Output’ folder from the project folder in your VIGO6 library to a SD card. You have to place the ‘Output’ folder in the root of the SD card with the name ‘Output’.
- Insert the SD card in the PD 688.
STEP 3: Use the PD 688 for download
Tips on the COPP hardware modules and peripherals
- support USB
- support ESC/POS command format
IT and Support
When something does not work, look here
- Minimum 3,6 GHz CPU
- Minimum 6 GB RAM
- A SSD-disk
- Find the Hardware interface of the component.
- Right click and then select “Assign hardware interface to channel”.
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).
Overall designIn general PD recommends to create components for “logical functions”. As an example , please see the below component structure for a milk tanker system. By following this method, you can use a broad range of physical components such as pumps and valves. You can even use a combinations of them, without having to change any program code. We have made a demo-project PD_17604-02 that implement the described component structure.
Using methods to reduce number of program linesSometimes you find that a method becomes so large that you find it difficult to read. In that case, you have the option to create methods within the component, that you can call from your “too large” method. An example is functionality used in many places. Another example is to make a method for each state in a state machine. In the end, remember that you can make a supervisor/servant-connection from one component to another. As a result, you can get access to the methods and data in another component.
- Add the relay output component(PD-2825) and your control component.
- Connect the two
- Locate the relay and contorl component in PD850 (or in another suitable device)
- In VIGO6 you build and test functionality one time, and then you can use it again. No copy paste - you just add the component to your assembly.
- In VIGO6 you have a lot of premade components that you can use in your project. It can be a pump valve or flow meter components.
- In VIGO6, you tie the visualisation to a component or assembly, and you can reuse it.
- In VIGO6, you have better options for maintenance of existing systems. There are no settings done directly on the modules - as was the case in VIGO5. As a result, when you locate your project for the system, you know what is running, can make the updates you want, and then build and download the new program.
- In VIGO6 you can replace a faulty module 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)
How does it work?You can find servant proxys in the subcomponents. They have an X as its icon. They create a communication channel between a supervisor and servant component. In the model, one supervisor can control many servants. But a servant can only have one supervisor. If you need more than one component to control another component, then you can add a connector. It is important to notice that inputs and outputs in VIGO6 are components too. You can create a connector in the section “connection to external components”. The connector is a different way of communicating between two components. You have no “automatic notification” - as you have in the SUP/SERV model.
AdvantagesThe data from the servant in your supervisor is validated by VIGO6. This means that you will get “invalid” if your servant component is not able to communicate. Another advantage is that the supervisor is automatically notified by the notification model, whenever there is a change in the data of the servant. In practice, the model updates the "actual" register and calls the method “calculate actual” in the supervisor. So you don't need to ask the servants all the time about their status and data, as they will tell you themselves.
More informationTo learn more about the notification model, see tutorial 4. For further information and inspiration of what the model can do for you, please check out tutorial 8. In that tutorial a servant exposes its error state and control condition of its servant. Its state is the sum of its own state and the state of its servants. This is a way to create an simple monitoring system that guides you to where the problem is. To learn more about connectors, see tutorial 1, step 5.
Tips and tricks on building awesome visualisations for your components and assemblies
For control components:First create a “basic view” based on PD_11813 - Comp_view that has the size you want and that contains the elements you want on all views. Examples are headers and buttons, but do not bother with the forward or back arrow – they will come automatically. Build each individual frame for the swipe using your “basic view” as your template. Build your swipe by using this view as your base: PD_15398 Basic_swipe_view_for_component. Afterwards, place all the individual frames in the view list of this view. Remember to set the size of this view to the same size as you selected for your “basic view”.
For assemblies:Same as control components, but create a “basic view” based on PD_13556 - Asm_view and build your swipe by using this view as your base: PD_15452 Basic_swipe_for_assembly. The first two elements in the view list for the PD_15398 and PD_15452 are buttons to swipe left or right and they work automatically. The first frame in the view list will be shown first, and then the second etc. 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 tutorial 7 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.
1:If you don't want to restrict any user access, or use any translations, the default setting is Language = 1. If you haven't defined language 1 in the project, the system will show texts as you wrote it in the program. Furthermore, set user access rights to all rights. There are no restrictions in what you can show, edit, or print.
2:If you must set the language and user access rights to specific values, then you must locate PD_17553-xx - Display_interface_control in the device. Furthermore, you must locate one for each kind of presentation interface, which can be a screen or printer. This is the default setting when you use the PD_13619-xx - PD688_complete assembly. For other devices, you must add and locate the Display_interface_control component. Now you can set the power-on Language and User access rights through the instance constants in the figure below: Automatic_Logout_at_StartUp must be True. Set Logout_language_index to your prefered language. Set Logout_operator_rights 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 a variable. As always, remember to connect the connector in your control component.
3:When you add the PD_17553-xx - Display_interface_control to a device, then 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. You can cover the login view by the drawing “PD_18207-xx ca_Cover_login_logout_button”. Remember to disable the hit-test: The Instance constant Operator_array defines the rights, language, name, password and ID for a group of operators. If you want more information, see the documentation for PD_17553-xx - Display_interface_control. If you use 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. They are individual swipe frames, where you can see the operator access rights and select a Language. In 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 logs in with an NFC card. The specific language to set is stored on the NFC card. This is the default setting when you are 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. You select it through the Instance constant NFC_login_actions in the PD_15627-xx - PD688_NFC_component. Default setting is that the system sends NCF login information 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.
- If a view is set as “non closeable” it makes no sense to have a close button on it.
- PD_18158-01 - Close_all_windows_button (closing all windows EXCEPT guest views that youhave marked “Non closeable” in the project/assembly) – a button with a red circle
- PD_18157-01 - Close_window_button (closes only the window it is located on- as long as you haven't marked the window as “Non closeable”) – a button with a red X.