| |
This site contains a range of movies, programs and descriptions for self-instructional learning the programming of TECOMAT |
|
| |
|
TECOMAT - PC Connection Setup |
 Konfiguracja.avi
 Ethernet connection settings.jpg
IP_address.png
|
Instructional video showing the configuration steps to connect a PC to the TECOMAT Foxtrot controller with Ethernet to work on the LAN.
Explanation of terms:
LAN IP Address - The address of the controller on the local Ethernet network which allows direct connection among the participants of this network.
"MODE" button - on the CPU of TECOMAT controller, which when pressed, cyclical displays on the dispaly the IP number given to the central unit /for ex. IP=192_168_001_104/.
Network card - Ethernet communication port on the computer connected to the CPU. Required to set the IP address, subnet mask and default gateway for TCP/IPv4.
IMPORTANT NOTE!
Each Ethernet channel has its IP address and IP mask. Their values depend on the setting of the off-side participant in communication. A general rule applies here that the IP addresses of both participants of communication must be identical within positions wherethe IP mask has a non-zero value. The IP mask should be identical for both participants, however, this is not conditioned.
Example:
PC-PLC
IP address: 192.168.1.1 IP address: 192.168.1.2
IP mask: 255.255.255.0 IP mask: 255.255.255.0
or:
PC-PLC
IP address: 192.168.12.1 IP address: 192.168.25.8
IP mask: 255.255.0.0 IP mask: 255.255.0.0
Attention:The first IP address number must not be 0, the last IP address number must not be 0 or 255! The last IP mask number must not be 255! If& not correct IP address and IP mask values are entered, CPU sets these parameters to default values preset by the producer. The IP address and the IP mask are valid for all modes used within one Ethernet channel. |
|
|
|
| |
|
New project in Mosaic |
Tworzenie projektu.avi
 Getting_Started_pl.pdf
Getting_Started_en.pdf
|
|
Instructional video showing the steps of creating new project in TECOMAT Mosaic.
Explanation of terms:
Projet Group - "Project Group", a collection of all the files that describe the complete automation system for any number of cooperating PLC /default name "ProjectGroup1"/. In the folder with the default name MosaicApp /Mosaic Applications/ is generated the file *.mpr and a folder named the same as adopted for the Project Group, including all files, folders and complete documentation of the automation system.
Project - a collection of all the files for one PLC in the whole automation system /Project Group/ default name "Plc1"/. All files describing the complete scope of documents for the PLC can be found in a folder default called MosaicApp/ProjectGroup1/Plc1.
POU - "Program Organization Unit" any block of the interface program presented in one of the forms according to IEC 61131-3 /IL, ST, LD, FBD, CFC, SFC*/.
Program name - the name of the interface program block /default "progMain"/
Program Instance - all or part of a software block called in the controller by its name. Instances are the elements of a program introduced to the PLC which are enforceable in the PLC cycle.
Program Instance name - the additional, distinguished name of the interface program block, which is many times called at various places the complete PLC software. To the data supported by a block is given an additional label, a name that allows for easy identification of a block in the structure of the same interface program. If the program block will be executed only once in the entire circulation of controller, there is no need for granting additional label /default "Main"/.
Function - block called by the other POU program. Is not directly related to the implemented technological tasks, is universal in nature and for the same data will always return the same result. Features include a set of parameters /variables and constants/, which are defined when the function call. Function returns only the one result being a declared value of the function in the format of the function /eg such as trigonometric functions/.
Function Block - block called by the other POU program. Is not directly related to the implemented technological task, is universal in itself does not take any value, exchanges data with other POU blocks only by a set of formal parameters and may return different results. Examples of standard function blocks in the Mosaic are: S-Set, R-Reset, CLK - Clock Synchronization, PDT-Preset Date and Time ...
Function, Function Block - subroutines that belong to the group of the POU programs. Functions and function blocks can use but can not call other POU programs, while POU programs can call Functions and Function Blocks.
TASK - name of technological tasks carried out by a group of program units. The task can be called a periodicaly or after the event in the modes defined by the number of process P /default name of "FreeWheeling" of the default process P0 for tasks done in each circulation loop of the PLC software. There are calls to process tasks from P0-P64 in either hardware interrupts, time interrupts, restarts "Warm" /P62/ and "Cold" /P63/ or phased calling to avoid the hazards /P1-P4/, or for executing the last calculations while ending the loop of software /P64/, or other events defined by the user/
*. mpr - "MOSAIC program name extension for Design Group.
*. plc - Project name extension.
*. mcf - "Main configuration file "- expansion of the name which is automatically created and presents configuration of files in the PLC.
RESOURCE CPM - the contents of the controller CPU Central Processing Module. The list contains tasks and form of their implementation and names of called program blocks. |
|
|
|
| |
|
Assigning symbolic names /aliases/ |
Alias.avi
|
Instructional video showing how to describe inputs and outputs using aliases /own names of signals instead of formal addresses/
Explanation of terms:
I/O Setting - Table to assign physical inputs and outputs of the modules and modules-oriented information to the controller registers and symbolic names.
Data Structure - a list of information generated by the module /states of the inputs, outputs, information on exceedances ranges, data of the module ... etc./.
Full notation - a real address signal in accordance with the principles of module location /r0_p3_DI - means the cassette (rack) number 0, the position of the cassette in position No. 3, DI module, bit DI0/ following the TECOMAT system structure /see also the example of "Addressing the CIB modules in TECOMAT controllers/.
Alias - An alternate name used to identify the signals /other designation assigned to facilitate a meaningful symbolic object identification of signals used in the project/.
Terminal - terminal designation for the selected module terminal block
Abs./len. - Name of memory cell /Bit, Byte ... /, where the adequate data is stored and the length of the data.
Value - the value or state /input/output or data/
Fixed - the field for manual forcing by entering a value to be used in the program instead of the actual /useful, for example during the commissioning of the control system/.
Note - additional remarks and comments that do not affect the control process |
|
|
|
| |
|
Simulated controller |
Sterownik symulowany.avi
|
Instructional video showing the work with a simulated TECOMAT controller /Soft PLC/.
Mosaic environment allows to test programs in a virtual PLC and periphery assigned by the user. This gives an easy and free way to validate the developed solution of the automation system.
Explanation of terms:
Simulated controller - software emulated particular type of CPU from the TECOMAT family which can perform the interface program prepared from customer. The simulator allows to force states of inputs, outputs, variables, and the insertion of data representing the object to verify the correctness of the structure of developed automation system. It is possible to complete the verification of complex solutions based on any number of cooperating controllers connected by any communication networks. The simulation results are presented graphically and the numerical values of the actual assignment of variables are supported. /see also an example of PID Control showing the possibility of simulation a regulated facility/. |
|
|
|
| |
|
Archiving |
Archiwum.avi
|
Instructional video showing how to back up Project Groups.
With *. piz archives (compression system with additional protection against hackers) which is special form of *.zip (a widely used compression software) can be made easy and safe storage of created programs.
Explanation of terms:
Archiving - save all files included in Project Group into computer memory - the command available with the path File/Archiving /Archive current project group." The new folder is created in a compressed version /extension *. piz /
Downloading the archived file - download from PC memory of all the files stored in a compressed format *. piz to the Mosaic environment - "the command available with the path File/Archiving /Restore archived project group." / See also an example of the "Program with the user Function Block" / |
|
|
|
| |
|
|
| |
|
|
| |
|
Addressing the CIB modules in PLC TECOMAT |
Adresowanie Foxtrot.jpg
Adresowanie CIB_1.jpg
Adresowanie CIB_2.jpg
Przykład programu z CIB.jpg
|
The accompanying drawings illustrate the principles of addressing the CIB object modules in TECOMAT family.
Explanation:
- Each CIB object module has its own unique hardware address. In addition, the Mosaic program gives each module the ID when adding a module to the system configuration /see Annex Adresowanie CIB_1/
- Designated ID number is part of the name (1) and serves to identify the symbolic name of an alias (2) /see Annex Adresowanie CIB_2. Symbolic names are assigned by the user./
- Addressing the TECOMAT Foxtrot and addressing the TECOMAT TC700 based on locating modules in racks. Foxtrot TECOMAT addresses virtual rack, due to its physical absence.
- CPU modules, CIB bus Master modules, operator panels occupied rack number r0 /rack0 marked additionally as a RM0 - Rack Module 0/
- The individual modules are addressed in the rack as they occupied the position /p/ in order of their installation, the CPU takes the position of p0, the integrated display on the CPU module has a position p1, the integrated CIB Master has a position p2, the integrated I/O module available CPU occupies a position p3, p4-p7 positions remain unused, positions p8-p11 are used to address additional operator panels attached to the TCL2 bus.
- Object modules extending the scope of the I/O's CPU occupied the rack1 with positions r1 p0-p9 settable with hardware switches
- Another CIB bus Master modules /Is possible to attach additional 8 sections each 500m long/ take a virtual rack RM3and positions p0, p2, p4, p6
- There is no need to use physical addresses in the program, just enter symbolic addresses /for example see Annex Przykład programu z CIB/. |
|
|
|
| |
|
Communication with SMS |
_PG_ExampleSMS1_2010-06-04.piz
|
The Annex presents an example program implementing SMS communication via modem connected to the TECOMAT Foxtrot controller. Presented are two main versions of the program in the form of a list of commands /ST/ and functional blocks /FBD/.
The structure of the main program /SMSMain/:
- Network 1 controls the SMS gateway readiness signal /iSMS.Ready / and calls the program block RemoveSMSfromQueqe, which reduces the queue of served SMS messages
- Network 2 Library program block SMS_HANDLER/library SmsLib/ supports the transmission channel for sending and receiving SMS messages through the gateway. Is required to parameterize theSMS_HANDLER block with the data of subscriber, SIM card and network, through which the call is made. GSM modem is connected to a communication channel /ex. RS232/ operating in UNI mode /details see the description of the library block in chapter 1.2.1 SMS_HANDLER SMS_Handler documentation available in a Help tab in the Mosaic program. Program block SMS_HANDLER supports transmission in both directions set by the signals Send to dispatch and NewMess for the incoming message. Received message is passed to the function block GSM_PARSER, which analyzes the content of the message received in accordance with the requirements of the user program. At the same time function CTU assignes a serial number to message received and sets information on receiving new SMS message at the iSMS output.
- Network 3 StoreSMS calls a function, which enters the data into PLC and adds a timestamp mark /TimeStamp/
- Network 4 supports SMSAlarm function, which prepares the content of SMS to dispatch in the event of alarm. |
|
|
|
| |
|
Communication with Modbus protocol |
TecoLibSrc_Modbus_RTU.piz
Test_ModbusRTUlib.piz
_PG_ModbusRTU.piz
_PG_Modbus_CP1015_ACU.piz
|
Appendix presents two examples of implementing the program to communicate with the ModbusRTU protocol for reading the power meter and collection of measurement data from the Adam module.
The structure of the main program / prgMain / (example 1):
Network 1 marks the beginning of the variables, which store data read from power meter
Network 2 ModbusCmd calls a library function for reading data
Network 3 calls function block arranging the transfer over the selected communication channel /CH1 ... CHN/ in ModbusRTU mode /PLC as Master and power meter as Slave/.
The structure of the main program /Foxtrot_vs_Adam/ (example 2)
Networks perform duties similar to example 1, wherein is included more external modules, which are read from the controller. |
|
|
|
| |
|
PID controller |
_PG_ExamplePIDs_2010-05-21.piz
|
The attached file shows an example of application the PID controller serving the heating and mixing installation with a table of setting parameters and oscilloscope presentation of the work. To illustrate the proper selection of waveforms and parameters, software simulates working conditions of PID block. Controller uses an incremental structure /PID11 function block - MORE output /Więcej/ and LESS /Mniej/ with a short list of parameters and another one with direct output OUT also with limited parameters. WebMaker tab window shows the setting data for both controllers and simulators. GraphMaker tab shows the flows of process parameters.
Note:
Attachement in compressed form. Support - see the examples "Archiving" and "Program containing the user's Function Block"
Program structure:
- In the main loop two program blocks _PID1_Example _PID2_Example are called
- Network 1 of each called program blocks serves adequate library function block PID11 or PID21 and respectively function blocks fbSIM1 and fbSIM2 to simulate the actual parameters of the controlled installation. |
|
|
|
| |
|
Training set |
|
|
Educational kit for beginners to rent for self-study and testing
- Plastic case consists of TECOMAT Foxtrot CP-1005 controller, expansion module TCL2, CIB modules, ID-18 touch panel and manipulative elements to perform the tasks in the design and testing of digital circuits and PID control. For details, see here |
|
|
|
| |
|
|
| |
|
Connection Setup TECOMAT - PC on the Internet |
Komunikacja przez Internet.pdf
|
The attached document describes the steps for configuring the PC - Foxtrot Tecomat connection realized by using a WAN router TP-Link TL-WR1043ND equipped with DD-WRT software.
Explanation of terms:
LAN IP Address - The address of the PLC controller on the local Ethernet network which allows direct communication among participants of the network
Internet / WAN IP Address - The address of the router that connects a local area network /LAN/ to Internet |
|
|
|
| |
|
Communication with VPN channel |
VPN.pdf
|
This tutorial describes a step-by-step actions to launch virtual server VPN network connection on a router equipped with alternative software OpenWrt.
VPN (Virtual Private Network) described as a tunnel through which traffic flows within the private network between the client terminal over a public network such as the Internet. This network exists merely as a logical structure, in fact, acting in the public network. Although such a mechanism of end stations can use the VPN just as if there were physical link between private individuals. |
|
|
|
| |
|
Upload of user visualization files |
Wizualizacje.avi
|
Instructional video featuring steps of usage the WebMaker tool in Mosaic. Presented is the principle of building visual screens using animation showing the dynamic states of devices supported by the TECOMAT PLC controllers.
Explanation:
- The first part of the film shows the visualization of a simple task, symbolizing the engine in movement and in rest state with animation in GIF format /file used in the example of graphic animation comes from the Wikipedia portal http://pl.wikipedia.org/wiki/Plik:Schemat_pracy_silnika_elektryczne_pr% C4% 85du_sta% C5% 82ego.gif /
- The second part of the film shows the ability to view certain web pages associated with the current state of supported devices - such as direct access to the manual service instructions adequate to the machine operator needs
Note
TECOMAT system and the software Mosaic allow you to insert your own animation developed in Javascript and Flash. Access to the implementation of this type of animation is not described on-screen messages of Mosaic to avoid ambiguity interpretation by different browsers. For information on how to get access to such functionality of the Mosaic tool, please contact the EMEA Gateway company. |
|
|
|
| |
|
Real-time clock synchronization over the Internet |
_PG_SNTP_2012-04-25.piz
|
Attached program presents synchronization of the internal real-time clock of TECOMAT controllers with the signal form SNTP server / Simple Network Time Protocol / available on the Internet. SNTP servers are a source whose accuracy is ensured by the standard time taken directly from the atomic clocks or via satellite navigation systems GPS, GLONASS, EGNOS, WAAS. The signal is sent from servers to the Internet customer with an accuracy better than 10 ms, which is sufficient for the realization practically of all tasks that require of time synchronisation.
The structure of the main program / PrgMain /:
- Circuit 1 / Network1 / shows the use of the Library fbSntp
- Synchronization follows at intervals of one hour / trigged with system variable System_S.R_EDGE_1HOUR / or at any time "on demand" by activating the GET variable. In both cases, the command is executed by the occurrence the rising edge of trigger variables.
The meaning of basic parameters:
- Channel-mode Ethernet UNI with UDP protocol,
- SNTPaccept - confirmation of the realized communication
- SNTP server default port = 123,
- Utcoff - time offset relative to GMT in minutes
- SNTP server IP address,
- Done - rising edge confirming synchronisation of internal clock / state =1, when not synchronized state=0 /,
- Busy = 1 if lasts process of synchronization,
- TimeSet = 1 to confirm that the correction of the internal clock was made. |
|
|
|
| |
|
Graphmaker - edition of charts in Mosaic |
Graphmaker.pdf
|
|
Description of the steps for configuration the Graph Maker tool which is used to draw diagrams and charts in the Mosaic software. |
|
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
SMART Home
Ethernet connection settings.jpg
IP_address.png
icon to make the compilation of the loaded program to verify its correctness 
icon ro establish the communication between the Mosaic tool and simulated PLC 
icon 
icon 
Adresowanie Foxtrot.jpg
Adresowanie CIB_1.jpg
Adresowanie CIB_2.jpg
Przykład programu z CIB.jpg
