You can find answers to common questions here.
What if you can't find what you are looking for? Then, please send a mail to
How to make updates to your live systems
Make the updates you want to your project.
Tips on the COPP hardware modules and peripherals
The hardware-interface PD_16494-06 - Power_state_notification_interface is a subcomponent. You can add it to all the components where you want to handle changes in the power state.
When the power state changes, you get a notification. Further, you get the current power state in the local variable “events”. One of these states is “External_power_lost”. In other words, you get this event, when you lose the main supply, and your device runs on a battery.
See the small basic example below.
Nb. Once you add the interface you can only locate your component in devices with batteries (i.e. PD 688, PD 803, and PD 802).
You use the reset button to reset a module or change its mode. The module's diode will show its mode. When you press the button, the diode will turn off for 100 ms as a response. You can make the diode blink through a method call.
If a customware program on a module causes an error, you can start the module in "firmware only" mode. The module will never call the guest component, only the firmware. Now, you can download new customware and activate that instead.
You change to “firmware only” mode with a press on the reset button for five to ten seconds. The color of the diode will be yellow.
This mode is for when you have a major problem where you can't even connect to the module in "firmware only" mode. In that case, you force the module to run its factory firmware. As a result, the module will lose its non-volatile data, including the P-NET settings. The factory firmware is the firmware it had when the module left PROCES-DATA.
You change to "factory only" mode with a long press on the reset button for ten to fifteen seconds. The diode will be blue.
The diode is a constant red, and you can't change its mode. The module needs service.
It will activate the "factory only" mode. You can use it to mount a module that you have already used for another purpose. You install the module in a plant with a power supply, while you press and hold the reset button down. Afterward, it will not interfere with the communication in your system, because you reset its P-NET settings.
The table has an overview of the different presses and the colors.
|You need a PD688 or a PD803 to be able to print from VIGO6.
The printer must:
We have tested two printers:
EPSON TM-T88V-042 model M244A
|CITIZEN model CT-P293|
|Special note for the CITIZEN printer. The switches must be set as in the pictures below in order to function correctly.|
The modules PD688/802/803 currently only support SDHC cards with the FAT32 filesystem.
This means that the card needs to be 4GB..32GB. As a result, cards smaller than 4GB or larger than 34GB will not work.
The card should have an A1, A2, or similar rating. Cards with these ratings have good random write performance (like the workload found in a mobile phone), rather than only good streaming write performance (like the workload found in a video camera).
Lastly, the card should have a temperature rating suitable for the environment in which the PD688/802/803 will be operating. For example, the Sandisk 16GB A1 card we ship as standard is rated for -25 to +85 degrees celsius.
When something does not work, look here
Your PD-contact person can help you sort out what kind of support you need, and what is appropriate for your specific problem.
If we need our VIGO6-experts to have a look at your problem, they will typically ask for a support file.
Instructions on how to generate a support file:
You can continue working offline on all the content in your local archive. Once you are back online, you can then push your work to the company's archive (signer archive) for safekeeping. You can find the content of your local and company archive in the editor by selecting "open"-> "All types".
In addition, the section "Draft types" contains a subset of the local archive. It holds all the types you are the writer of, and that you have not yet pushed to the company archive. It means that anything in the "Draft types"-section only exists on your local PC.
PROCES-DATA hosts your VIGO6 server. It communicates with TCP on port 35349. In short, change the company's firewall settings to allow communication on that port, and you are ok.
We have the following minimum recommendations for the workstation used to run the VIGO6-editor:
Especially the SSD disk is important for speed. We have seen 50-60 times speed improvements between using a non-SSD-disk and an SSD-disk.
|While PROCES-DATA has designed the modules for 4-20mA inputs and outputs, it is still possible to use a 0-10V input.
Below is an example of a 0-10V level input transforming the 0-10V input signal to a length.
We have implemented basic error handling, which means that it will signal to its supervisor if it has an error. You can operate it in "manual feedback", "auto" and "disabled". For more info on the built-in functionality of the process component see tutorial 7.
The component is PD-18096 and in the documentation section, you can see what it does. Basically, it reads a voltage and converts it to meters.
If you do not add any operator control, you will likely not see any fields on the views we have made. That is why we have added component PD-17553 Display interface control to the assembly. In effect, we can add the login or logout button to our assembly view. This enables us to play around with operator rights.
|If you want to interface to this component in your overall control component, then do it as a “supervisor-servant”-connection. Below you see how to access the “level in meters”|
|First, locate your components into devices – which will give you the automatic configuration. The method is that the first output you add gets the first output channel. The first input you add gets the first input channel etc. The system only allocates to an I/O channel, when all I-channels are full.
You can change the allocation:
If you have “filled” all channels in the device, you can start by clearing the channel number on a few of the components, so you have space to move around.
Using one of the predefined "Quantity <-> local units relation table"
All units in VIGO6 are stored as SI-units but can be displayed as any derived unit you want.
Volume in Litres and flow rate in liters per second are already defined and are e.g. used in the “quantity <-> local units relation table” PD_12849 Europe_metric_system_MID. So if you select that one in both the project and editor, you will work in liters instead of m3.
Creating your own derived quantity
If you want eg liters per minute, you first need to create your own local unit.
Open PD_13598 Volume_flowrate_l/s. Rightclick and select “create new type” now rename this new type to “Volume_flowrate_l/minute” and adjust the symbol to “l/m” and the scale to 60000 (1000 to go from M3/s to l/s and another 60 to go from l/s to l/m)
You then need to create your own “quantity <-> local units relation table”.
Open PD_12849 Europe_metric_system_MID. Right-click and press “create new type”. Rename to eg” MYCOMPANYNAME_europe_metric_system”
Then you right-click on “VolumeFlowRate” and select “Add local unit type” and choose the “volume_flowrate_l/minute” you just created. And then you press on the radio button next to your own unit.
You should also add it in your editor (set on the setup screen).
In general, PD recommends creating 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 combination of them, without having to change any program code. We have made a demo-project PD_17604-02 that implements the described component structure.
Sometimes 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 a 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.
You need to share all the types with the people working on the project. They can see and use them, but there is still only one owner. You create a project. Different people can work on different types that you use in the project. As a rule of thumb, split the project into as small pieces as you can. In that way, you don’t have to wait too long for other participants to implement changes.
If you find an error or want to add functionality to one of the types, the type owner can make the changes. Afterward, the type owner should push the types to the shared draft again. You can then go to the specific type and restore type and documentation, and thereby you implement the changes in the project.
There is no notification system in the editor that gives you an update when there are changes to one of the types in the project. As a result, you need to be in a close dialog with your colleagues.
Everyone who contributes to the projects needs to have the same editor version.
In VIGO6, you do not need to know the specific final design of your outputs or inputs for that matter. You can develop all your control code without deciding which type of digital output to use.
In your control component, you add a connector or servant proxy to ” PD_2824-xx - Digital_output_base”. Now your control code can interface to any of the descendants of the digital output_base. This is illustrated in green color in the inheritance diagram below.
Now you can write your control code that controls the (generic) output.
You can also see tutorial 1:
Once you have made the decision about the type of output, you can proceed. Let us assume that you have selected a relay output.
In your assembly you simply:
You can also see tutorial 2:
And the VIGO6 platform contains many improvements that will make development easier, including:
See also advantages in VIGO6.
While we suggest using the NFC-reader in the PD688 display unit for easy login, you can also predefine users.
We have created a control component (PD_17553) and visualization (PD_18202) that allow you to create six default users for every display unit in a project. These are instance constants in the control component, so once you have added the component to your project you simply define the default users you want. And of course, remember to locate the component into the display unit.
The user logs in with username + password OR with userID + password.
The password and username are a (text)string. The string value is entered as plain text in the “AdaptString” cell.
See the example for Operator .
NoOfElements is the string length, 0,1,2,3 … is the elements of the string. So since NoOfElements is 20, the password can be up to 20 characters long.
Tips and tricks on building awesome visualisations for your components and assemblies
Yes, you can. Please see this tutorial, where you will get detailed instructions on how to create your own keyboard.
Check this tutorial upon language and operator access rights!
Yes, this is “as designed”.
But of course, you have several options to change the default behavior of the screens. Just refer to this tutorial!