Programming examples for Movicon LogicLab and SCADA. These examples are for HMI series and PL500.
Before downloading the examples, we suggest to login to the website http://www.pixsys.net and to read the instructions for the HMI series, available at the following link:
https://www.pixsys.net/download_file.ph ... 8_RevD.pdf
EXAMPLE NO. 1: Read/Write Digital Outputs
This example shows sequential reading/writing or single activation of digital outputs on MCM260-1AD or MCM260X-1AD.
EXAMPLE NO. 2: Read/Write Digital Outputs
This example shows sequential reading/writing or single activation of digital outputs on MCM260-1AD or MCM260X-1AD.
EXAMPLE NO. 3: PID and Data Logger
This example shows the PID regulation with history records and graphic display of the data through I/O ETD-1644.
The PID function will be executed by the LogicLab PLC, while the data-logging is done by Movicon functionality.
EXAMPLE NO. 4: Dynamic Objects and Movicon Screens
This example shows how to handle dynamic objects within the screen according to the value of a variable. Also the example shows how to group several screens within a single screen using TAB.
EXAMPLE NO. 5: Internal Movicon Report
This example shows how to handle an internal Movicon report and to save it in the project folder \DLOGGERS\.
EXAMPLE NO. 6: LogicLab Mapping Modbus Slave Registers
This example shows how to make Modbus registers available on Ethernet using a PL500 as a MODBUS TCP-IP slave.
EXAMPLE NO. 7: How to change the system time
This example shows how to change the system time of windows CE using a Movicon screen.
EXAMPLE NO. 8: Movicon Trend Graphics
This example shows how to manage an XY trend (abscissa and ordinate variables sampled) and usual trends (abscissas on time base and ordinates with variables sampled).
EXAMPLE NO. 9: How to force page change from PLC
This example shows how to enable forcing a new page on Movicon using the PLC variables. Movicon cyclically performs a script to check if the forcing of the page change is enabled by the PLC. If the page changeover can be forced on the PLC, the screen changes in accordance with the value of a variable.
EXAMPLE NO. 10: Numerical and Alphanumeric Keyboard customization on Movicon
This example shows how to use an existing screen as "Numeric " or "Alphanumeric" Pad within a Movicon project. The screen has been optimized for use on TD410 and TD710, but it may also be used on other targets.
EXAMPLE NO. 11: Pixsys GSM Module
This Function Block interfaces with the Pixsys GSM module (2200.20.002) and allows to send text messages (SMS) on events. The Function Block (see file attached SMS_ALERT.pll) must be imported into LogicLab using a special function of the "Project" menu -> "Import Objects".
For wiring and connection please refer to the enclosed user guide of the GSM module.
N.B.: In case of use with the serial port COM1 RS232, it is very important to use a standard RS232 cable with all signals RTS, CTS etc. (we suggest to use standard Belden cables).
EXAMPLE NO. 12: How to format SD Memory Expansion
Formatting an SD memory expansion. This guide shows how to handle an SD or microSD card to use it as data storing memory.
EXAMPLE NO. 13: Internet Explorer and Movicon
This example shows how to make your Movicon project available from remote for the Internet Explorer browser.
EXAMPLE NO. 14: Configuration of MCM260X-9AD
This example shows how to configure I/O and probe reading of an MCM260X-9AD using Movicon on a TD710.
EXAMPLE NO. 15: Movicon Scheduler
This example shows how to use the object Movicon scheduler to activate a Boolean variable on weekly time bands.
EXAMPLE NO. 16: How to update or restore HMI and PL500
This guide shows how to use the DeviceFinder utility in order to upgrade or restore the default image of the device.
EXAMPLE NO. 17: Graphic Interface Movicon HMI on remote PLC/HMI
This guide shows how to use the graphic Movicon interface of an HMI with another HMI or PLC of the same class of IP network addresses.
EXAMPLE NO. 18: How to setting the Siemens S7 driver using a Pixsys HMI
This guide shows how to parameterize the S7TCP driver for the Siemens S7 PLC series, using only the Movicon graphical interface on the Pixsys HMI.
EXAMPLE NO. 19: Users Management
This example shows how to request logins and passwords for objects within a screen accessible only to higher level users.
EXAMPLE NO. 20: Send a mail by active alarm
Attention: For the correct functioning of this application it is required a MoviconCE FULL license that allows you to run the Movicon Alarm Dispatcher.
Pixsys code MoviconCE FULL license 2400.35.003
(contact your Pixsys sales or write to info@pixsys.net)
This example shows how to automatically start the Movicon Alarm Dispatcher and associate an alarm notification email.
The example contains the SMTP.STG file to download and edit according to the following procedure :
1.Edit the SMTP.STG file with any text editor and enter the data of your email account used.
2.Save the file.
3.Copy the file into the /NandFlash/MovXCE folder of the HMI or PL500. Overwrite the old STG file if any.
4.Download the Movicon application and start the project on the HMI.
SMTP.STG file
Movicon Application
EXAMPLE21: Recipe management on LogicLab
This example shows how to manage the backup/restore of the values of some PLC variables, through the recipe features of LogicLab. The variables to be saved/restored must be of type "RETAIN", i.e. retentive.
Procedure:
1.Create a "recipe container", from the Resources tab, by right-clicking on "Recipes" and choosing "Add recipe", for example "SystemRecipe":
2.Add, using the "Add" button and then "Assign", the desired retention variables to the newly created container. You can automatically add all existing retention variables in your project using the "Add/Refresh all retain variables" button.
3.Save the project.
4.Add a program and assign it to the "background" task.
5.Insert the function blocks "Save_Recipe" and "Load_Recipe" (from the library "Pixsys\Recipe Functions")" connect the variables as shown below:
NB: function blocks must be in a program assigned to the background task to work!
The variable "SaveCommand" executes the function block "Save_Recipe" that creates a snapshot of the value of all the variables assigned to the container "SystemRecipe" and saves it in the recipe indicated by "RecipeName" (editable as desired). This is automatically set to FALSE once the procedure is finished.
The variable "LoadCommand" executes the function block "Load_Recipe" that creates loads the recipe indicated by "RecipeName" (editable as desired) and assigns the value to the variables assigned to the container "SystemRecipe". This is then automatically set to FALSE once the procedure is finished.
LogicLab project:
[TD410][TD710][TD810][TD820][PL500]Programming examples
-
- Moderatore
- Posts: 1201
- Joined: 12/09/2016, 14:49
[TD410][TD710][TD810][TD820][PL500]Programming examples
You do not have the required permissions to view the files attached to this post.