PROTON CMB

PROTON CMBUser Manual

Warranty : All products by IZI Technology are underwarranty against defective materials for a period of one yearfrom the date of shipment to the original purchaser.

Atention : IZI Technology is not responsible for dam-age resulting from the use of its products. IZI Technologyreserves the right to change this manual at any time with-out notice. The information provided by IZI Technology isbelieved to be accurate and reliable. However, no respon-sibility is assumed by IZI Technology for its use or for anyinfringement of patents or rights of third parties resultingfrom the use of the products.

Copyright :All material in this manual is protected bycopyright in 2016.

Trademarks : The names are used for the sole purposeof identification and trademarks are the property of their re-spective companies.

IZI Technology Inc.3651 Pegasus Dr. Ste. 117 Bakersfield, CA 93308 USA.

Tel: (661) 412-3494 – email: [email protected]://www.izitechnology.com

[email protected]

http://www.izitechnology.com

Contents1 Product Capabilities 7

2 Hardware Installation 82.1 Power Supply Connector . . . . . . . . . . . . . . . . . . . . . . . . 92.2 Serial Ports Connector . . . . . . . . . . . . . . . . . . . . . . . . . 92.3 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.4 Status Led Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5 Reset Push Button . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.6 Digital Output Connections . . . . . . . . . . . . . . . . . . . . . . . 132.7 Digital Input Connections . . . . . . . . . . . . . . . . . . . . . . . . 132.8 Analog Output Connection . . . . . . . . . . . . . . . . . . . . . . . 152.9 Analog Inputs Connection . . . . . . . . . . . . . . . . . . . . . . . 16

3 Setting up the PROTON for the first time 17

4 Operation and Configuration of the PROTON 214.1 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2 Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.2.1 Gateway Name and Description . . . . . . . . . . . . . . . . 234.2.2 Gateway Security Configuration . . . . . . . . . . . . . . . . 234.2.3 Ethernet (LAN) and WiFi (WLAN) Configuration . . . . . . 254.2.4 DHCP Server Settings: . . . . . . . . . . . . . . . . . . . . 254.2.5 Wireless Settings . . . . . . . . . . . . . . . . . . . . . . . . 274.2.6 MAC Address Whitelist . . . . . . . . . . . . . . . . . . . . 29

4.3 I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.4 IZI-NET Protocol Configuration . . . . . . . . . . . . . . . . . . . . 304.5 Network Protocols Configuration . . . . . . . . . . . . . . . . . . . . 32

4.5.1 Modbus TCP/IP Client Protocol . . . . . . . . . . . . . . . . 324.5.2 Modbus TCP/IP Server Protocol . . . . . . . . . . . . . . . . 354.5.3 EtherNet/IP Tag Client . . . . . . . . . . . . . . . . . . . . . 364.5.4 NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.6 Serial Protocol configuration . . . . . . . . . . . . . . . . . . . . . . 404.6.1 Modbus RTU MASTER . . . . . . . . . . . . . . . . . . . . 404.6.2 Modbus RTU Slave . . . . . . . . . . . . . . . . . . . . . . . 42

4.7 Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.7.1 Adding and Removing Charts . . . . . . . . . . . . . . . . . 434.7.2 General Settings . . . . . . . . . . . . . . . . . . . . . . . . 444.7.3 Adding and configuring variables . . . . . . . . . . . . . . . 464.7.4 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.7.5 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.7.6 Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49



[email protected]


5 Scripting 515.1 Scripts example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.1.1 Timing in seconds . . . . . . . . . . . . . . . . . . . . . . . 515.2 Read/write values in the database . . . . . . . . . . . . . . . . . . . . 525.3 Mathematical operations of values . . . . . . . . . . . . . . . . . . . 525.4 Description of objects available in PROTON . . . . . . . . . . . . . . 53

5.4.1 Functions for the manipulation of the database from the Script. 53

6 IZINET 556.1 IZINET 2.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

6.1.1 Network Settings . . . . . . . . . . . . . . . . . . . . . . . . 556.2 IZINET 900 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

6.2.1 Network Settings . . . . . . . . . . . . . . . . . . . . . . . . 566.3 IZINET 2.4 e IZINET 900 Transfer configuration . . . . . . . . . . . 57

6.3.1 Types of transfers (Enable) . . . . . . . . . . . . . . . . . . . 586.3.2 Run Interval (Poll Interval) . . . . . . . . . . . . . . . . . . . 586.3.3 Node Address . . . . . . . . . . . . . . . . . . . . . . . . . . 586.3.4 Source DB Address Initial Address . . . . . . . . . . . . . . 596.3.5 Number of bytes transmitted (Byte Count) . . . . . . . . . . . 596.3.6 Destination DB Address . . . . . . . . . . . . . . . . . . . . 59

7 Mapping analog and digital inputs and outputs 597.1 Entradas Digitales(Digital Inputs) . . . . . . . . . . . . . . . . . . . 607.2 Salidas Digitales (Digital Outputs) . . . . . . . . . . . . . . . . . . . 607.3 Entradas Analógicas (Analog Inputs) . . . . . . . . . . . . . . . . . . 607.4 Salida Analógica (Analog Output . . . . . . . . . . . . . . . . . . . . 61

8 HMI 62

9 LUA Objects and Functions Available in PROTON Script Language 66

10 Internal Diagnostic Data 7810.1 ModBus RTU Maestro . . . . . . . . . . . . . . . . . . . . . . . . . 7910.2 Modbus TCP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 8110.3 Modbus TCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 8310.4 IZINET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8310.5 MODULE INFORMATION . . . . . . . . . . . . . . . . . . . . . . 8510.6 Ethernet/IP Tag Client . . . . . . . . . . . . . . . . . . . . . . . . . 86

List of Figures1 Proton Dimentions . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Distribución de terminales del conector de alimentación . . . . . . . . 93 Serial Network Connector showing RS485 connections . . . . . . . . 94 Status Led Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . 105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11



[email protected]


6 Reset Push Button Location. . . . . . . . . . . . . . . . . . . . . . . 127 Digital Output Diagram Connection . . . . . . . . . . . . . . . . . . 138 Digital Input Diagram Connection. . . . . . . . . . . . . . . . . . . . 149 Analog Output Diagram Connection. . . . . . . . . . . . . . . . . . . 1510 Analog Input Diagram Connection. . . . . . . . . . . . . . . . . . . . 1611 Connecting the PROTON . . . . . . . . . . . . . . . . . . . . . . . . 1712 PROTON Browser windows. . . . . . . . . . . . . . . . . . . . . . . 1813 Firmware upgrade: Select the configuration page. . . . . . . . . . . . 1914 Firmware upgrade: Select the Firmware Upgrade . . . . . . . . . . . 1915 Firmware upgrade: Select the .prtn file and press Send. . . . . . . . . 1916 PROTON Home Page. . . . . . . . . . . . . . . . . . . . . . . . . . 2017 Base de datos de la unidad Proton. . . . . . . . . . . . . . . . . . . . 2218 PROTON Configuration Screen . . . . . . . . . . . . . . . . . . . . . 2419 PROTON Security Configuration Screen. . . . . . . . . . . . . . . . 2520 LAN Interface Configuration . . . . . . . . . . . . . . . . . . . . . . 2621 WLAN IP Settings configuration . . . . . . . . . . . . . . . . . . . . 2622 DHCP Server Configuration . . . . . . . . . . . . . . . . . . . . . . 2723 Wireless Lan Configuration Sections . . . . . . . . . . . . . . . . . . 2824 Setting Address at Digital Input and Digital Output . . . . . . . . . . 2925 Setting Address on Analog Inputs and Analog Output . . . . . . . . . 3026 IZI Net Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 3127 IZI Net Commands Configuration . . . . . . . . . . . . . . . . . . . 3228 Protocol Configuration Screen. . . . . . . . . . . . . . . . . . . . . . 3329 Modbus TCP/IP Configuration. Protocol Settings Section. . . . . . . 3330 Configuración Protocolo Modbus TCP Cliente . . . . . . . . . . . . . 3431 Data Swap Usage Example . . . . . . . . . . . . . . . . . . . . . . . 3532 Modbus TCP/IP Configuration Window . . . . . . . . . . . . . . . . 3533 Mapping of Modbus registers to PROTON database registers. . . . . . 3634 Ethernet IP Tag Client Configuration . . . . . . . . . . . . . . . . . . 3735 Example of setting the reading of a TAG from an AB PLC . . . . . . 3836 Example of setting the reading of a TAG from an AB PLC . . . . . . 3937 NTP Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . 3938 Serial Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . 4039 Serial command Configuration . . . . . . . . . . . . . . . . . . . . . 4140 Add a new chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4341 Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4442 Display window time interval . . . . . . . . . . . . . . . . . . . . . . 4543 Creating and Configuring Variables . . . . . . . . . . . . . . . . . . . 4644 Variable Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4645 View on status page . . . . . . . . . . . . . . . . . . . . . . . . . . . 4846 Independent Page View . . . . . . . . . . . . . . . . . . . . . . . . . 4847 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4948 overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4949 Configuración del Tag Qtot para PLC de AB . . . . . . . . . . . . . . 5350 HMI Initial Configuration Window . . . . . . . . . . . . . . . . . . . 6251 Image Management Tab . . . . . . . . . . . . . . . . . . . . . . . . . 63



[email protected]


52 Label Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 6353 Pestaña de configuración de los Multiestados. . . . . . . . . . . . . . 64



[email protected]


1 Product CapabilitiesThe PROTON is and Industrial Wireless Communications Gateway that allows trans-ferring data to and from the internal memory to other devices via all the supportedindustrial protocols. It also allows wireless communications using the WiFi standard.

By using the friendly WEB based configuration tool, the user can configure readsand writes using all the available industrial communication protocols. The PROTONcan also be programmed using a simple scripting language called LUA, allowing dataconversion as well as execute event based actions upon communication exceptions ordata value based.

Values retrieved trough the communication protocols can be displayed in a WEBbased HMI (Human Machine Interface) that allows monitoring the industrial processusing Personal Computers and Mobile Devices like tablets or smartphones.



[email protected]


2 Hardware Installation

(a) Top and Bottom View (b) View from behind

(c) Right side view

Figure 1: Proton Dimentions



[email protected]


2.1 Power Supply ConnectorThe PROTON can be powered with a 9 to 48 Volts DC power supply and the maximumpower consumption is 5 Watts. The power supply connector is located on the top sideof the gateway and the terminals are shown of Figure 2. The FG terminal must beconnected to the field ground to avoid electromagnetic interference and allow all theover voltage protections to operate properly.

Figure 2: Distribución de terminales del conector de alimentación

2.2 Serial Ports ConnectorTo connect the PROTON to serial networks, for connecting the unit to a serial networkusing the diagram in Figure 3. The port only allows “half duplex" communication, inwhich only one node transmits at a time. Only terminals D + and D- terminal togetherwith the reference, are available.

Figure 3: Serial Network Connector showing RS485 connections



[email protected]


2.3 EthernetThe PROTON has a 10/100/1000 Mb/s capable Ethernet Port. This port supports alltype of network communications like EtherNet/IP and Modbus TCP/IP. This port isalso used for configuring the PROTON using our WEB based configuration tool.

Indication LEDs for the Ethernet Port

LED Status Description

Data(Green) Off No Ethernet connection detected.PROTON is not communicating troughthe Ethernet Port.

Blinking Active data Communication trough theEthernet Port

Speed(Amber) Off No activity

On Connected at 10Mbps

Blinking Connected at 100Mbps

(a) Puerto Ethernet de PROTON (b) Vista frontal Proton

Figure 4: Status Led Indicators



[email protected]


2.4 Status Led IndicatorLa unidad cuenta con un conjunto de leds de estado. Estos indican el estado tantogeneral de la unidad, como el estado especifico de cada interfaz de comunicaciones.De izquierda a derecha la figura 5 presenta la disposición frontal de estos indicadoresluminosos.

Figure 5:

1. RS-485 Error condition: if an error condition exist through RS-485 port, thenturn on the red led.

2. RS-485 Traffic condition: the led blinking if exist a data transfer.

3. WiFi Traffic and Error condition:

(a) Green: the led blinking if exist a data transfer through WiFi interface

(b) Red: If an error condition exist through WiFi interface, the led turn on.

4. Link wireless transmission and reception indicators

(a) Green: Transmission

(b) Red: Reception



[email protected]


5. Network Status

(a) Rojo: Network fail

(b) Verde: Network OK

6. Module Status

(a) Rojo: Module fail

(b) Verde: Module OK

2.5 Reset Push Button

Figure 6: Reset Push Button Location.

In figure 6, the reset push button is shown. This button is to reset the PROTONsecurity and to restore factory default settings. If the button is pressed and hold for 5seconds, all security settings (passwords), will be reset to a disabled security. This maybe necessary if the user forgets the administration password that is required to makeconfiguration changes. After the security is disabled the unit will play two tones using



[email protected]


the internal speaker.

To restart the unit to factory defaults, the reset button must be pressed for 10 sec-onds. At this point the internal configuration will be replaced with the factory defaultsettings. The user may need to do this if an invalid configuration is loaded into themodule.

2.6 Digital Output ConnectionsThe unit has two normally open type relay outputs, which are available on the firstconnector block of 8 terminals. When the output is active, there is confirmation in therespective indicator the wiring diagram is shown in Figure 7 The maximum current thatthe contacts can handle is 2 Amps and the maximum voltage is 250VAC or 220 VADC.

Figure 7: Digital Output Diagram Connection

2.7 Digital Input ConnectionsProton has two sets of two digital inputs with independent references and opticallyisolated. The permissible voltage range for these entries is between 12[VDC] and



[email protected]


30[VDC]. The input impedance is greater than 5[kΩ] so the input current is always be-low 10[mA]. When the respective terminals are energized, warning lights are activatedand indicate the high status of input.

In the first connector terminal block 8 there is a connection point to the land of fieldF.G. The shielding of the conductors can be attached to this node in order to improvenoise immunity of these inputs. In Figure 8 the wiring diagram shown.

Figure 8: Digital Input Diagram Connection.



[email protected]


2.8 Analog Output ConnectionProton has an analog current output in the format of 4 to 20mA. You can use a differentpower supply that is used to energize the Proton or can be bypassed to the terminals24V and 0V. The current in the range 4 to 20mA flows from the AO terminal, throughthe load must have a value less than 300Ω and returned by the RET terminal. In Figure9 the wiring diagram shown.

Figure 9: Analog Output Diagram Connection.



[email protected]


2.9 Analog Inputs ConnectionA set of 6 analog inputs, referenced to IRET can be read by IZI - Proton. The mea-suring range is between 4 and 20mA. In Figure 10 the wiring diagram shown. In thefirst terminal connector block is the connection point of the common signal. The lastterminal is a connection to the land of F.G field and that node must connect the shieldsof instrumentation cables used to connect the transmitters.

Figure 10: Analog Input Diagram Connection.



[email protected]


3 Setting up the PROTON for the first timeTo start working with the PROTON, it must be powered by a 9V to 36V power supplyand the Ethernet port must be connected to the configuration personal computer.

From the IZI Technology web site download and install the PROTON Browser.This application is only supported in Microsoft Windows Operating System.

http://www.izitechnology.com/support/Proton/

UWhen the application is installed and run for the first time, it will show all con-nected PROTON on the network.

Figure 11: Connecting the PROTON

The use of the Browser program, which is presented in the figure 12, is reallysimple. Firstly with this program you can update the firmware version of the system oridentify the IZI products that are connected to the red interface. The IP address of thered port of the computer is presented in numeral 2 of the figure and allows to identifythe segment of red where the IP address of the Proton is addressed. In section 3 theMAC address of the network interface through which the communication is establishedis presented.



http://www.izitechnology.com/support/Proton/

[email protected]


Figure 12: PROTON Browser windows.

It can be the MAC address of the Ethernet port or the WiFi port according to the in-terface through which the communication was made. In the number 4 is the IP addressthat has been assigned to Proton and in the general case it is not part of the networksegment where the device has been connected. In section 5 you can see the versionof firmware installed on the computer. Right click on the Proton icon and select "SetTemporary IP" opens the window that is designated by 6. In this you can specify anIP address that should be in the same network segment to which the computer belongsIs used to configure the product. Once this step is completed, in the position that isindicated by numeral 7 will appear the IP address that previously has been specified.



[email protected]


Figure 13: Firmware upgrade: Select the configuration page.

After you have changed the Proton IP address so that it is part of the network seg-ment of the computer where the configuration is done, double clicking on the Protonicon will open a new window in the browser of your computer (It is recommended Usethe latest version of Google Chrome) and you can see the page of Figure 16. From nowon it is possible to configure the Proton.

Figure 14: Firmware upgrade: Select the Firmware Upgrade

Figure 15: Firmware upgrade: Select the .prtn file and press Send.



[email protected]


Firmware updates are distributed as * .prtn extension files that can be downloadedfrom the IZI Technology website and downloaded to the unit using the Ethernet port.The process of updating the firmware is carried out from the web page of the unit.Pressing the Firmware Download button starts the process that requires selecting thedevice to be updated, defining the path where the * .dld extension file is located andperforming a couple of confirmations shown in Figure ?? with the numerals (8) and(9). The sequence of figures 13, 14, 15, indicate the steps from the home page to thedownload of a .prtn file

A very important aspect about the firmware update process that must be kept inmind is that for no reason should it be interrupted while it is running. If power orcommunication is interrupted the Proton will enter a state that does not allow firmwarereprogramming and must be returned to the factory for repair. Logistics and trans-portation expenses will not be assumed by IZI Technology and will be borne by thecustomer.

Figure 16: PROTON Home Page.



[email protected]


4 Operation and Configuration of the PROTONThe PROTON is an industrial communication gateway that allows transferring value toand from its internal database. Using any of the supported protocols, the informationis read from a device and copied in the internal memory of the PROTON. Then usinganother protocol that same information is transferred to a different device.

The PROTON also supports writing simple user scripts that allow conversion ofdata values or executing logic upon communication events. There are three types ofscripts available on the PROTON: Startup, Continuous, and Fault. The Startup scriptis executed on startup (every time the gateway cycles power or after configurationchanges). The Continuous script executes constantly during operation, for this reasonis important to make this script in an efficient way, to avoid interrupting communica-tions. The Fault Script is executed if an error is found on the Continuous Script.

4.1 DatabaseThe PROTON contains an internal Real Time Database. This database is used to holdvalues retrieved using the different available protocols. This data can also be accessedby the protocols to be transferred to a different device.

The Status web page of the PROTON allows viewing the Database for troubleshoot-ing or just to view the values retrieved by the different protocols. The Status web page(shown in Figure 12) shows the database as an array of values with a user selectableData Format and Byte Swapping. Table 1 shows all the possible data types



[email protected]


Figure 17: Base de datos de la unidad Proton.

Name Range Description

INT16(DEC) (-32.768 to 32.768) 16-bit integer with decimal display.

UINT16(DEC) 0 to 65.535 Unsigned 16-bit integer in decimal dis-play.

UINT16(HEX) 0 to 65.535 Unsigned 16-bit integer in hexadecimaldisplay.

INT32(DEC) -2.147.483.648 to2.147.483.648

32-bit integer with decimal display.

UINT32(DEC) 0 to 4.294.967.295 Unsigned 32-bit integer in decimal dis-play.

UINT32(HEX) 0 to 4.294.967.295 Unsigned 32-bit integer in hexadecimaldisplay.

FLOAT32 2−128 to 2128 Representation in 32 bits where MSB issign, 8 bits of exponent and 23 of man-tissa.

BIN Uses the 16 memorylocations

Binary representation of the data.



[email protected]


The database can be accessed from two instances; From the protocols and from thescripts. In the case of protocols, addressing is done with 16-bit words whereas in thecase of scripts, addressing is done with bytes (8 bits). For the protocols, the value writ-ten in the PROTON Database Address field corresponds to the address of the databaseof the unit.

In the case of scripts, which are presented in Chapter 5 of this manual, the addressesof the read and write functions are entered via 8-bit addresses, which means that to ac-cess a particular address of the database Of PROTON, the value written in the field ofthe functions of the scripts corresponding to addresses must be multiplied by two.

4.2 Module ConfigurationTo access the configuration of the module, select the corresponding tab on the Protonwebsite. In the figure 18 the configuration tab is displayed; On the left side there is amenu with all the options available on the computer. With this menu it is possible to:

• (1) Define the name and description of the gate

• (2) Configure module security

• (3) Configure LAN and WAN interfaces

• (4) Configure inputs and outputs

• (5) Configure The protocols that use the Ethernet, WiFi and IZI Net networkinterfaces

• (6) Configure the Serial port

• (7) Edit the Start, Continuous and Fault scripts of the PROTON

• (8) Edit the human-based web-based machine interface.

4.2.1 Gateway Name and Description

This option allows setting a name and a description of this specific PROTON gateway.This information is available in the status tab and the PROTON Browser and allows theuser to identify individual PROTON as well as quickly determining what its functionis.

4.2.2 Gateway Security Configuration

In PROTON there are three levels of security, Administrator (Full Access), Hmiview(Allows monitoring of HMI), Hmicontrol. All passwords must be greater than eightcharacters. Passwords are not stored in the configuration file and can not be read.Whenever passwords are defined or modified it is necessary to restart the unit by press-ing the "Reboot Module" button in the "Status" tab. Passwords can only be written



[email protected]


and it is impossible to read them; If they are forgotten, the procedure described in thesection describing the operation of Configuration Reset Button must be executed. Inthe figure ?? you can see the configuration screen of the module.

Figure 18: PROTON Configuration Screen



[email protected]


Figure 19: PROTON Security Configuration Screen.

4.2.3 Ethernet (LAN) and WiFi (WLAN) Configuration

The LAN interface (Wired Ethernet) is always enabled. The user must configure theIP Address, network mask and default gateway. The user must carefully choose thesevalues to allow the PROTON gateway to communicate trough the hardwired Ethernetinterface.

The Gateway setting is required if the PROTON will be accessing networks outsidethe wireless (WLAN) and wired (LAN) sub networks. In that case, the IP of a routerconnected to the LAN interface must be specified in the Gateway setting.

The Wireless network can be enabled or disabled depending on the user require-ments. The user must specify the IP settings: IP Address, Network Mask and Gateway.It’s very important that the settings for LAN and WLAN are in different subnets. Al-though a Gateway setting is present for the WLAN, this is reserved for the future. Atthis point in time the network can be rerouted to other subnets only trough the LANinterface.

4.2.4 DHCP Server Settings:

The WLAN interface supports a DHCP Server, useful to automatically set IP Addressesof mobile devices attached trough the WLAN Interface. It is important to se the rangeof IP Addresses on the same subnet as the WLAN Interface.



[email protected]


Figure 20: LAN Interface Configuration

Figure 21: WLAN IP Settings configuration



[email protected]


4.2.5 Wireless Settings

The "Scan Network" button allows you to identify the SSIDs within the Proton WIFIrange provided that the WLAN interface is enabled. - If you enable it and pretend touse the "Scan Network" button, remember to save the configuration previously - Thewindow associated with this button provides MAC address information, the topology,the channel used, the type of authentication and encryption as well as the quality ofthe link. With this information the user can select the least used channel to establishcommunication with other devices or accept the configuration parameters of the linkestablished in another device as the case may be.

Figure 22: DHCP Server Configuration



[email protected]


Figure 23: Wireless Lan Configuration Sections

The Topology button allows you to select between Ad-Hoc and AP-Infrastructure.The first is recommended when it is intended to make a link where all nodes have thesame status within the network and will be free to associate with other devices that arein the range of the link.

The Access Point-Infrastructure topology requires that there be a device configuredas an Access Point that may well be a PROTON, which must be configured in thismode, or another network device. The other devices that need to be connected to thistype of network, which can be other PROTON, smart phones or tablets, must be con-figured in infrastructure mode. Note that only the vast majority of phones and tabletsby default are configured in default infrastructure mode.

In the Passphrase field a password must be included, at least nine alphanumericcharacters to set the password.



[email protected]


4.2.6 MAC Address Whitelist

It is possible to enable a set of MAC addresses so that only they can connect to theSSID enabled on the device. It is possible to define a friendly name to identify thedevice quickly.

4.3 I/O ConfigurationIt is possible to configure the address in the Proton database the addresses where thedata associated with the inputs and outputs will be. The status of the bits of the digitalinputs, as well as that of the digital outputs can be configured in the tab shown in thefigure 24 The address specified in each field corresponds to a bit.

Figure 24: Setting Address at Digital Input and Digital Output



[email protected]


In the figure 25 the configuration tabs of the analog inputs and outputs are dis-played. All addresses correspond to 16-bit extension words. For analog inputs, thesewill be displayed in µA (1x 10-6 A). For example, if a current of 4mA flows in thecorresponding input, the present value in the Database will be 4000 which correspondsto 4000 µA.

In the case of analog output, the value must be written in the respective memorylocation should be the amount multiplied by one hundred mA; that is, if it is to generatea signal of 12mA, in the field of the database will be written the value 1200.

Figure 25: Setting Address on Analog Inputs and Analog Output

4.4 IZI-NET Protocol ConfigurationThe purpose of the IZI Net protocols is to communicate IZI products efficiently andsimply, but wirelessly, by accessing their databases. To establish the communicationbetween the teams it is only necessary to define three parameters, the Node Identifier,the Network Identifier and the respective Channel.

IZI Net has three tools that allow: Restart the link to its factory configuration,Remove the set of commands that were previously written and IZINet Mangaer thatallows to observe the status of the IZI equipment that are in the vicinity of the radiolinks Eur-lex.europa.eu eur-lex.europa.eu

The configuration window for the IZI Net protocols is shown in the figure ref fig:izinet1. The Node Identifier, Channel, Network ID and Cluster ID fields are used togroup the computers that are configured to work together. The Power Level field allows



[email protected]


you to define the level of RF power that the respective equipment must handle. TheRety Count and Back off (ms) fields allow you to configure the number of attemptsto make a communication as well as the time during which communication will beavoided once it has not been successful. The Application Ack field allows each timea communication between a pair of devices exists, there is a response that confirmsthe success of the process; When it has been confirmed that the process is successfulin a suitable time interval, it is possible to disable this option in order to improve thebandwidth of the channel.

Figure 26: IZI Net Configuration

In order to configure the Write and Read commands, it is necessary to define the ad-dress of the operation (Continuous Write, Write Before Changing Data or ContinuousWriting - Before Changing Data - Reading or Reception).

When writing is configured, you must specify the Node Address, the address in theSource DB Address where the information and the amount of Bytes that are intendedto be sent. You must also specify the address of the database of the device where theDestination DB Address must be stored.

In the case of configuring a read, it is very important to keep the same informationthat was defined in the corresponding write command in the fields Source DB Address



[email protected]


Figure 27: IZI Net Commands Configuration

and Byte Count for the link to be successful.

4.5 Network Protocols ConfigurationThere are four types of network protocols that can be configured in the PROTON, Mod-bus TCP Client, Modbus TCP Server, EtherNet / IP Tag Client and NTP. IZI productshave a set of protocols that allow the communication of a wide variety of industrialsystems. It is important to note that it is possible to configure several of these protocolssimultaneously and the equipment can operate correctly; It is possible for example tosimultaneously configure three Modbus TCP Client protocols to read data from threemodbus devices efficiently. From the standpoint of servers, it is only possible to add aninstance, it is also possible to add multiple clients that could be configured and controltraffic between the various clients. All protocol configuration windows have a commonarea, called "General Settings" where it is possible to include a name and comments ofthe configuration that has been established in each command.

4.5.1 Modbus TCP/IP Client Protocol

For the correct configuration of this client, data transfer blocks or commands mustbe specified, indicating which information must be requested from a Modbus TCP/IPdevice and where the information will be copied to the PROTON database. The com-mands will run periodically according to the specified interrogation time.



[email protected]


Figure 28: Protocol Configuration Screen.

In Figure 29, in particular in the section of "Protocol Settings" three values can beconfigured. (1). Time Out, (2). Retray Count and (3). Back Off. When the client beingconfigured communicates with a Modbus TCP server, after making a request, it waitsfor the time set in Time Out by the response. If this response does not arrive duringthe set time, it performs the number of attempts specified in Retray Count and if thecommunication still is not successful, PROTON stops performing this process duringthe time set in Back Off.

Figure 29: Modbus TCP/IP Configuration. Protocol Settings Section.

If, however, communication is performed successfully, the time set in "(5) PollInterval" shown now in Figure 30, will be the minimum set time to execute each com-mand . When a continuous enable is selected, PROTON will attempt to execute thiscommand each time the specified time expires. For example, a command with 100ms



[email protected]


of "Poll Interval" will run every 100 ms.

Figure 30: Configuración Protocolo Modbus TCP Cliente

In the field (4.) Enable, each command can be disabled, enabled continuously orthat can be executed when there is a change in the data being addressed when it is tobe written only.

In (6.) Device IP Address and Device Node Address, you must specify the IPaddress where the Modbus TCP Server and the node address are configured respec-tively. PROTON automatically detects if the specified address is on the Ethernet orWIFI subnet and directs messages to that interface. If it is not a message for any of theconfigured subnets, the message is sent via Ethernet to the Default Gateway. Usuallythe Device Node Address parameter is ignored by the Modbus TCP/IP server, howeversome devices such as TCP/IP to serial routers may require this parameter to specify theserial slave address.

In the (7.) Modbus Function field, you can select from the eight available func-tions.

In the field (8.) Device Modbus Address specifies the address of the modbus table,of the device configured as server, where the value with which it is desired to operateis specified. This address must be the offset offset of the record based on zero. Forexample, to read the 40001 register, use 0.

In the field (9.) PROTON Database Addres specifies the address of the PROTONdatabase where the information with which it is to be found is located; This address



[email protected]


can point to either a source or a destination. It is important to note that this address canbe a word address when in the selected command records intervene or it can be a bitaddress when the command intervenes bit information.

In the field (10.) Register Count specifies the number of forward registers fromthe source address that will be modified by the executed command. If, for example, itis being read from the server, the amount specified in 10 will be read from the nodeand its contents will be written to the SXP5 database from the address written in field 9.

The options available in the (11.) Data Swap field allow data modified with thecommand in question to have byte, word and byte-byte manipulation as the case maybe. An example of the use of the Data Swap feature is presented in Table 3.

Figure 31: Data Swap Usage Example

4.5.2 Modbus TCP/IP Server Protocol

Figure 32: Modbus TCP/IP Configuration Window

The default Modbus TCP Server protocol is configured on port 502. You can select



[email protected]


the maximum number of connections in "Concurrent Connections" and the value of"Connection Timeout" in your configuration window.

All the information found in the PROTON database is available to modbus clientsthat interact with the configured server. In the figure ?? is the memory map of PRO-TON and allows to find the equivalences of addresses between a native modbus deviceand the addresses of the PROTON database.

For example, in word 0 of the PROTON database, the information correspondingto the "Holding Register" 40001 or the content of "Coils" can be written between ad-dresses 1 to 16. In word 1 of the database Of PROTON, you can read information fromthe "Input Register" 30002 or the "Input Status" 101017 to 10032

Figure 33: Mapping of Modbus registers to PROTON database registers.

4.5.3 EtherNet/IP Tag Client

As in the other protocols, it is necessary to specify data transfer blocks or commandsthat will indicate that Tags of an Allen Bradley PLC must be transferred to or from thePROTON database.

In the protocol settings area, the four fields marked by the number 1 in the figure34 allow you to specify the address of the PLC, the chasis slot where the Allen Bradleyprocessor is connected and the maximum values of the connection times to the PLCand the message to be sent.

In the Tag Settings area, marked by the number 2, the information regarding theTag with which it is intended to work is specified. In the Enable tab it is possible toenable, disable or update only in case of change, during writing, the command that is



[email protected]


being configured. In the Data Direction section you can configure the process of read-ing or writing data. In the Tagname field you must specify the name of the Tag thatis defined in the Controller Tags section of the Allen Bradley PLC. The format for thetags can be: tag, tag.elemento, tag [index], tag.elemento [index] .elemento. The typeof data that you want to work with must be selected in the Data Type menu

Figure 34: Ethernet IP Tag Client Configuration

The Register Count field is used to work with PLC Tags that are fixes. For allnon-Boolean data is addressed as follows. If the tag is specified without square brack-ets "Tag", the value specified in Register Count will allow the reading or writing ofthat number of elements of the array. If, on the other hand, a Tag with square brack-ets and an index inside it is specified, "Tag [Index]", the read or write process willbe performed on the elements of the array that are indicated by the "Index + Register



[email protected]


Count "For example, if an array called EXA is constructed in the PLC, it consists of100 elements of the real type and you want to read the contents of the last 20 elementsfrom PROTON and store it in position 1000 of the PROTON database, repeating thisProcess at least every 100ms it is possible to do it as shown in figure 35.

Figure 35: Example of setting the reading of a TAG from an AB PLC

If the array consists of Boolean data, addressing is done in 32-bit words and theRegister Count value points to 32-bit quantities. If for example in the PLC there is atag called EXABOOL of type bool array, which has 128 elements and you want to readelement 33 and place it in the position of BIT 1153 of the PROTON database, you mustconfigure PROTON as it appears in Figure 26. The section on the use and interpretationof the information provided by the PROTON database addresses the topic of locationof information in depth.

4.5.4 NTP

PROTON has the possibility of using an NTP server to configure the working dateand time. Figure 37 shows the fields that must be specified in order to configure theprotocol. In the NTP Server Address and Backup NTP Server Address fields, the IPaddresses of the server and the backup server must be specified. If the backup serveris not available, the same IP address must be used in both fields. The offset valuesmust be specified in both hours and minutes with respect to the time of the Greenwichmeridian in the Time Zone Hour Offset and Time Zone Minute Offset fields. You canconfigure the refresh interval by specifying the value in minutes in the Request Intervalfield.



[email protected]


Figure 36: Example of setting the reading of a TAG from an AB PLC

Figure 37: NTP Protocol Configuration



[email protected]


4.6 Serial Protocol configuration4.6.1 Modbus RTU MASTER

To configure the protocol it is necessary to specify data transfer blocks or commandsthat will indicate what information is to be requested from a Modbus RTU device andwhere in the PROTON database the information will be copied. The execution of thecommands is performed periodically according to the specified interrogation time.

Figure 28 shows the serial port configuration window. In the Port Settings sectionit is possible to select the interface type between RS-485 and RS 422, the Baud Rateto which the communication is to be executed, the parity, the data bit number and thenumber of stop bits

In the Protocol Settings section, in the Command Delay field, the delay time be-tween commands is specified, in the Intercharacter Timeout field the maximum waittime for a message is answered, in the Retray Count field the number of failed messageretries and In the Back Off field specifies the time that a device is kept out of the sweepafter it has presented a communication error.

in the ocnfiguration of the protocol it is possible to select the values of command de-lay, message timeout, intercharacter timeout, retry count and back off. That should beselected according to the type of application being programmed in the unit. In GeneralSettings tab, as is normal with the commands programmed in PROTON it is possible todefine the command name and enter private comments. In command settings tab youcan specify the command and keep a structure very similar to the one used in ModBusClient Command present before.

Figure 38: Serial Port Configuration



[email protected]


Figure 39: Serial command Configuration

In the General Setings field it is possible to define a Name and specify CommentsOf the command. On the Command Settings tab it is possible to Enable Continueor On Data Change or Disable the command. Can be specified Poll Interval, se-lect from one of the eight Functions Modbus. In the Device Modbus Address fieldthe address of the record is specified Modbus with which you intend to work. In theSPX5 Database Address field, Specifies the address of the Proton database where theinformation is to be read or written. The Register Count field allows me to specify thenumber of records that are involved in the operation. The Data Swap field allows meto select the type of ordering (Byte, Word and Byte-Word) that you want to apply tothe value being operated. Finally in the Device Node Address field corresponds to thenode address in the Modbus RTU network. An address from 0 to 255 should be used,where 0 represents a broadcast command (it is received by all devices connected to thenetwork). It is possible to use an addressing directive in this field indirect. The indirect



[email protected]


addressing directives available are:

• @UINT8(Address in Byte)

• @UINT16(Address in Word[,swap code])

• @INT16(Address in Word[,swap code])

• @UINT32(Address in Word[,swap code])

• @INT32(Address in Word[,swap code])

• @REAL32(Address in Word[,swap code])

• @BIT(Address in Bits)

The purpose of indirect addressing directives is to replace a real-time database valuein the configuration. This allows for example enabling or disabling commands basedon existing values in the database or changing the destination node of a command.

For example, in the case of placing in the Device Node Address field as @ INT16(100), the proton will proceed to take the value (in 16-bit integer format) of the word100 from the database and use this value as Address of the Modbus node. If the valueis invalid, for example -1, the command is automatically disabled. In this way, it ispossible to have a query with a different Modbus slave address than the configuredModbus slave when modifying the word 100 of the database.

4.6.2 Modbus RTU Slave

When configuring the Modbus RTU slave protocol in the General Settings tab it ispossible to include a comment describing the intent of the communication.

In the Port Settings part, it is possible to select the interface (RS 485), BaudRate (300-115200), Parity, Data Bits and Stop Bit. In the Protocol Settings tab it ispossible to define the Slave Address, which must be a value between 1 and 255 as wellas the corresponding timing. It is possible to specify the magnitude of the ResponseDelay as well as the Time Interval between Characters.



[email protected]


4.7 ChartsThe process of configuring the variable storage and visualization module is explainedbelow. It also specifies the limitations thereof.

4.7.1 Adding and Removing Charts

Figure 40: Add a new chart

The previous image shows the steps to add a new chart or remove an existing chart.



[email protected]


4.7.2 General Settings

Figure 41: Initial Setup

The previous figure shows the fields related to the general configuration, the configu-ration of the display window and the period of reading of the graph or variables.

Enable Enables or disables the read, store, and display process globally.

Comments Comments of the user

_View Period SetUp Sets the maximum tiem interval of the display window, once inthe display window, the set of values that the associated variables have had during thistime, the new data set read, will be displayed for the first time, thay will displace the



[email protected]


same amount of the oldest readings that are being displayed. with this and accordingto the specified time interval, only the most recent data is displayed.

Figure 42: Display window time interval

Before acquiring the number of readings required for a complete display period,the time interval displayed will always be less than specified.

Since the accumulation of readings is done on the browser side of the user, oncethe user closes the web page associated with a particular chart, all accumulated samplesare deleted. When the web page of the chart in question is opened again, the maximumset of displayed data will be given by the size of the buffer of visualization housed inthe unit, and of the amount of samples stored in this one, until that moment. This alsoapplies when the page associated with a chart is opened for the first time. Once the unitis powered up, or the main program is restarted, the above-mentioned display bufferwill be empty. The size of this buffer is 365 readings per variable.

Finally, the maximum time interval of the display window can be specified in termsof days, hours, minutes and seconds.

_Data Collection Rate SetUp Sets the time interval for reading the variables (records)associated with a chart. This interval can be specified in terms of days, hours, minutesand seconds. This parameter specifies the minimum time between readings stored forlater reference.

Finally it should be clarified that it is convenient that the display interval is greaterthan the reading range.



[email protected]


4.7.3 Adding and configuring variables

Figure 43: Creating and Configuring Variables

At the bottom of the Chart’s general configuration form is the addition, edit, and re-moval control of the variables (records) that are to be plotted and stored.

Figure 44: Variable Record

The previous image shows the different parameters of configuration and registra-



[email protected]


tion of a variable that is visualized and whose history will be stored. Each parameter isexplained below.

DB Index Index of the record that stores the value of interest.

Data Format Value Format: UINT8, UINT16, INT16, UINT32, INT32, FLOAT32,and BIT

Swap Code Byte sort options, to get the correct value of the variable: None, SwapByte, Word Swap, Byte and Word Swap

Min Minimum value that the variable of interest can take

Max Maximum value that the variable of interest can take.

Deadband Magnitude of the difference that the current reading should have over theimmediately previous one, so that the current reading is recorded (persistent storage).

Unit Prefix Represents the units of the physical variable in question. It is part of theinformation displayed in the display window. Example: C

Color Color with which the variable in question will be graphed.

Label It is part of the information shown on the display sale.



[email protected]


4.7.4 Display

Figure 45: View on status page

Figure 46: Independent Page View



[email protected]


The previous images show the methods of access to the display page. The 46 imagehighlights some graphics scanning utilities as well as shows the queries section of thestored information.

4.7.5 Queries

Figure 47: Queries

This section allows you to retrieve and display data stored in a past time interval. Oncethe initial date and time, and the end date and time of the query are entered, you mustpress the "MAKE REQUEST" button, this will start the process of retrieving the re-quested data. The "MAKE REQUEST" button will be enabled again, once all availableinformation has been displayed. The "Export to CSV" button allows the user to exportthe recovered data to a CSV file.

Figure 48: overview

Overview

4.7.6 Cautions

Real Time Clock In order to maintain the chronological consistency of the storeddata it is vitally important to keep the system’s real-time clock updated. A loss of timesynchronization can lead to data loss and erroneous data viewing.

Particiones de almacenamiento Each reading of each variable belonging to thesame Chart is stored in a table with a maximum of 4000 records. Once this valueis exceeded, proceed to create another table. A maximum of 250 tables are created,once this value is exceeded, a process of reuse of the tables that store the oldest databegins. This is within the database of each chart created by the user.



[email protected]


Arreglo de trazabilidad Each time the computer or the main program is restarted,a structure called "Traceability Arrangement" is created. This structure contains thenumber of tables that exist per variable, how many records each table contains and whatis the time stamp of the oldest stored data In each table. This process is performed byrunning queries against the underlying database, and can take several minutes depend-ing on the number of existing tables. Reason why, initially the web interfaces relatedto this functionality, may not respond to the actions of the user. It is clear that only theweb interfaces related to this functionality will present this anomaly.

BackUp Finally it is recommended periodically to make a backup of the stored in-formation. This through the option of queries and export in SCV format.



[email protected]


5 ScriptingLua is an extensible programming language designed for general procedural program-ming with utilities for data description. It also provides good support for object-oriented programming, functional programming, and data-driven programming. It isintended that Lua be used as a powerful and lightweight scripting language for anyprogram that needs it. Lua is implemented as a clean C written library (that is, in thecommon subset of ANSI C and C ++).

Being an extension language, Lua has no concept of main program (main): it onlyworks embedded in a host client, called container program or simply host. It can invokefunctions to execute a piece of Lua code, can write and read Lua variables and canregister C functions to be called by the Lua code. Through the use of C functions,Lua can be augmented to cover a wide range of different domains, creating customprogrmaing languages that share the same syntax. The Lua distribution includes asample host program called lua, which uses the Lua library to provide a complete andindepedent Lua interpreter.

5.1 Scripts example5.1.1 Timing in seconds

When it is necessary to introduce a delay, greater than 1 second and in whole numbersof seconds, the following script can be used:

Startup

1 TiempoInicial = os.time()

Continuous

1 i f os.difftime(os.time(),TiempoIncial)>1 then2

3 TiempoInicial = os.time()4 -- Escriba su codigo aca --5

6 end

In the Startup defines a variable "Initial Time" that stores an amount that providesthe function os.time ()

In Continous, the if conditional evaluates the current "os.difftime" difference be-tween os.time () and the value stored earlier in StartTime; If this difference is greaterthan 1, an instruction is executed that updates the value of the variable StartTime andthen executes the code to be timed. If it is required to timer quantities greater than1 second, the difference with respect to the quantity in seconds that is required to betimed must be evaluated.



[email protected]


5.2 Read/write values in the databaseIn this example it is required to read an unsigned integer from position 80 of thedatabase and place it in position 90 of the database. The functions used for this opera-tion are mainDatabase: getUINT16 (index, swapCode) and mainDatabase: setUINT16(index, value). In both functions the value of the index corresponds to the indicateddirection, multiplied by two. In section 4.1 of this manual the ways of addressing thevalues in the database are presented and the reason for the multiplication by two e theaddress included in the "index" parameter can be evidenced.

Startup

1 Entrada = 0

Continuous

1 Entrada=mainDatabase:getUINT16(2*10,0)2 mainDatabase:setUINT16(2*100,Entrada)

5.3 Mathematical operations of valuesIn this case, a data coming from a Modbus device reaches the PROTON database ataddress 100 and has a value range between 0 and 4096. In the AB PLC it is requiredto write to a tag called Qtot , Corresponding to the value of the square root of the valuesent by the modbus device and located at position 105 of the PROTON database.

Startup

1 Entrada = 02 Salida = 03 TiempoInicial = os.time()



[email protected]


Continuous

1 i f os.difftime(os.time(),TiempoIncial)>1 then2

3 TiempoInicial = os.time()4 Entrada =mainDatabase:getUINT16(2*100,0)5 Salida= math.sqrt (Entrada)6 mainDatabase:setFLOAT(2*105,Salida,0)7

8 end

Figure 49: Configuración del Tag Qtot para PLC de AB

5.4 Description of objects available in PROTONThe version of LUA available in PROTON has a set of objects that allow, among otherthings, to check the status of the programmed commands.

5.4.1 Functions for the manipulation of the database from the Script.

Table 4 presents a set of functions that allows the read or write values of the databasewithin the scripts. The value of the indexes that must be included in the functions isspecified in bytes, unless they are bit oriented operations. It is important to note thatthe addresses of the PROTON database are specified in words (16 bits) then if it is in-tended to point to address 10 of the database from a function, the index to be included



[email protected]


should be 2 * 10 .

mainDatabase:setUINT8(index,value)

mainDatabase:setUINT16(index,value)

mainDatabase:setINT16(index,value)

mainDatabase:setINT32(index,value,swapCode)

mainDatabase:setUINT32(index,value,swapCode)

mainDatabase:setFLOAT(index,value,swapCode)

mainDatabase:setBit(index,value,swapCode)

mainDatabase:getUINT8(indice)

mainDatabase:getUINT16(index,swapCode)

mainDatabase:getINT16(index,swapCode)

mainDatabase:getINT32(index,swapCode)

mainDatabase:getUINT32(index,swapCode)

mainDatabase:getFLOAT(index,swapCode)

mainDatabase:getBit(index)



[email protected]


6 IZINET

6.1 IZINET 2.4

IZINET is a simple record transfer protocol between the IZI Technology family ofgateways. IZINET 2.4 is the wireless implementation of this protocol on a 2.4GHzradio link oriented to the construction of mesh networks.

6.1.1 Network Settings

This set of parameters allows the interaction of units with the same configuration. Theassociated parameters are described below:

• Node Identifier: String of maximum 20 characters that identifies the bound.

• Channel: Value between 12 and 23 that selects the channel used during datatransfer. Default value 12.

• Network ID: Value between 0 and 32767 that identifies the network, in whichthe units exchange data. Default value 32767.

• Power Level: Power level delivered during each transmission. The options arelimited to: + 10dBm, + 12dBm, + 14dBm, + 16dBm and +18dBm. The defaultoption is + 10dBm.



[email protected]


• Cluster ID: Value between 0 and 65535 that identifies or discriminates group ofunits within the same network. Default value 17.

• Retry Count: Field that defines the number of retries before a failed transferbefore removing the command from the execution stack. Default value 3.

• Backoff [ms]: Value in milliseconds, during which a failed command remainsoutside the execution stack.

• Application Ack: Enables or disables the protocol-level acknowledgment mes-sage. By default it is disabled.

6.2 IZINET 900

IZINET is a simple record transfer protocol between the IZI Technology family ofgateways. IZINET 900 is the wireless implementation of this protocol over a 900MHzradio link oriented to point-to-point communication.

6.2.1 Network Settings

This set of parameters allows the interaction of units with the same configuration. Theassociated parameters are described below:

• Node Identifier: String of 20 characters maximum that identifies the unit

• Preamble ID: Value between 0 and 7 that is placed before each transmitted packetin order to identify the context of the information transferred. It is analogous tothe IZINET 2.4 channel



[email protected]


• Network ID: Value between 0 and 32767 that identifies the network, in whichthe units exchange data. Default value 32767

• Power Level: Power level delivered during each transmission. The options arelimited to: + 7dBm, + 15dBm, + 18dBm, + 21dBm and + 24dBm. The defaultoption is + 24dBm.

• Cluster ID: Value between 0 and 65535 that identifies or discriminates group ofunits within the same network. Default value 17.

• Retry Count: Field that defines the number of retries before a failed transferbefore removing the command from the execution stack. Default value 3.

• Backoff [ms]: Value in milliseconds, during which a failed command remainsoutside the execution stack.

• Application Ack: Enables or disables the protocol-level acknowledgment mes-sage. By default it is disabled.

6.3 IZINET 2.4 e IZINET 900 Transfer configuration



[email protected]


Both IZINET 2.4 and IZINET 900 share the same transfer configuration structureas a general rule, any transmission command must have a "Receive" command on thereceiving node side. In both cases both the source address of the initial transfer registerand the number of bytes transmitted must match.

6.3.1 Types of transfers (Enable)

• Disabled: The command is not executed.

• Continuous: The command is executed periodically based on the Poll Intervalparameter.

• On Data Change: The command is executed only if any record within the sectionto be transmitted changes its value, with respect to its last transmitted content,or if the transfer has not been executed within the time interval defined by theparameter Poll Interval.

• Receive: This command creates the counterpart on the receiving side. It isstrictly necessary for the received data to be written in the section defined inthe database of the receiving equipment.

6.3.2 Run Interval (Poll Interval)

This parameter specifies the run interval for the Continuous and On Data Change /Continuous transfer types. It has no interpretation for the On Data Change type. Fi-nally, it defines the maximum waiting time of receiving a transfer type Receive, afterwhich the associated Receive command will be bounded by a Time Out error.

6.3.3 Node Address

8 bytes that uniquely identify the object that is the object of the transfer (unit that re-ceives the information). If the transfer type is Receive, the address identifies the nodetransmitting the information.



[email protected]


6.3.4 Source DB Address Initial Address

Defines the address within the transmitting unit’s database, the initial record of therecords section that will be transmitted, or received if the transfer type is Receive.

6.3.5 Number of bytes transmitted (Byte Count)

Defines the amount of Bytes that will be transmitted, or received if the transfer type isReceive. The number of bytes is equal to twice the number of MODBUS registers.

6.3.6 Destination DB Address

Defines the address within the database of the receiving unit, of the initial register ofthe section of registers where the received data will be written. It is only effective ifthe transfer type is Receive.

7 Mapping analog and digital inputs and outputsThe input and output information of the I / O block is mapped to the unit’s database viaits respective section on the unit’s web interface.

Each section of the I / O block has a mapping form.



[email protected]


7.1 Entradas Digitales(Digital Inputs)

7.2 Salidas Digitales (Digital Outputs)

7.3 Entradas Analógicas (Analog Inputs)



[email protected]


7.4 Salida Analógica (Analog Output



[email protected]


8 HMIProton has the possibility of building an HMI when using the WEB-based configura-tion software that the unit has. There are six basic types of components that you canuse to build an interface. You can include labels, images, values, multi-stacks, levelbars and value writing.

To build a display screen you must select the option to add a new screen in the"Screens" menu. In the properties section it is possible to define the name of the screen,the color of the background, the width and height. In the figure the windows and sec-tions of initial configuration of the HMI are shown.

Figure 50: HMI Initial Configuration Window

Once the working surface of the HMI is defined it is possible to add any of the avail-able components. The relative position of any component can be changed by specifyingthe X coordinates Y or by the cursor arrows. If an image is added, for example, thegreen box named Image must be selected and dragged to the work surface. A rectangle,with dimensions of 100 x 50 pixels, will appear by default, with dashed lines with anX in its upper left corner. This rectangle can be located anywhere on the work surface.

In the section of Properties it will be possible to change the dimension of the im-age, its position X Y, change its scale within the area previously defined and specifya link that will allow navigation control of the application. With this it is possibleto return to the previous screen or move to another screen. The figure shows the im-age management window where it is possible to add, change or delete the images withwhich the HMI is being performed. The formats and types of images that can be loadedare the same as a normal browser, however, it is important to note that if your size isimportant, so will the PROTON configuration file.

Figura XX shows a configuration screen where a label called "Label Exmaple" hasbeen added. Int the properties section it is possible to change the color of the back-ground and the text, the area of the label, the size of the letter and thickness of theletter. It it als possible, as in the case of the image, to add a link.



[email protected]


The Value, Multi-state, and level bar components share the dimensional propertiesassociated with the way the texts are displayed with the labels; All these also have afield that allows you to specify the source of the database from which the values arefetched.

Figure 51: Image Management Tab

Figure 52: Label Configuration

Table 2 presents a set of functions that allow you to fetch information from the



[email protected]


PROTON database and use it as an information source for the Value, Multi-state andLevel bar components.

@UINT8(Direction in Byte)

@UINT16(Direction in Word,[swap code])

@INT16(Direction in Word,[swap code])

@UINT32(Direction in Word,[swap code])

@INT32(Direction in Word,[swap code])

@REAL32(Direction in Word,[swap code])

@BIT(Direction in Bits)

In the case of values it is possible to add prefixes and suffixes to the amount shownon the screen. This option is particularly useful when engineering units are required tobe added or a particular Tag modified.

The Multi-state component allows a particular image to be associated with a setof states. According to the value taken by the data source, the related image will bedisplayed in the HMI. The configuration tab of the Multi-state component is shown inFigure xx.

Figure 53: Pestaña de configuración de los Multiestados.

In the level bar component you can change the geometry (Width or Height) ofthe bar according to the value specified in Data Source. You can define the range ofvariation by specifying the Maximum and Minimum values. According to the optionselected in direction it is possible that the bar grows or reduces upwards, downwards,



[email protected]


left or right.



[email protected]


9 LUA Objects and Functions Available in PROTONScript Language

Multiple Functions:

Function: SaveDatabaseData

Function SaveDatabaseData(startByte, byteCount, fileIndex)

Description Write the contents of a section of the database to non-volatile mem-ory.NOTE: This function limits writing to once per minute. If you callit more frequently than this, do not proceed to write anything until atleast one minute has passed since the module was restarted or sincethe last write was made.

Parameters startByte Start in Bytes of the region of the database to be storedin non-volatile memory.

byteCount Number of bytes of the database to be stored in non-volatile memory.

fileIndex Index of the file to store. Up to 10 memory regionsidentified with a number from 0 to 9 can be stored.

Returns BOOLReturns if the data storage was successful:False: Could not store data.True: Data stored successfully.

Examples -- Uses the first bit of the database-- like flag to proceed to write-- the database to non-volatile memory-- that same flag is repositioned-- at 0 when writing is successful-- This example should be in the scriptContinuousLocal writeBit = NUMERIC _DATABASE: getBit(0) If writeBit == true then

-- stores 180 bytes starting at-- byte 20 in file number 1local result = SaveDatabaseData

(20,180,1);if (result) then

NUMERIC_DATABASE: setBit (0)end

end



[email protected]


Function: LoadDatabaseData

Function LoadDatabaseData(startByte, byteCount, fileIndex)

Description Reads the contents of a section of the nonvolatile memorydatabase and copies it to the specified position in the numericdatabase.

Parameters startByte Start in Bytes of the region of the database to be storedin non-volatile memory.

byteCount Number of bytes of the database to be stored in non-volatile memory.

fileIndex Index of the file to store. Up to 10 memory regionsidentified with a number from 0 to 9 can be stored.

Returns BOOLReturns if the data storage was successful:False: Could not store data.True: Data stored successfully.

Examples - This example should be in the script- from startup- load 180 bytes starting at- byte 20 from file number 1Local result = LoadDatabaseData (20,180,1);



[email protected]


Function: deadBandValue

Function deadBandValue (sourceValue,destAddr,destType,deadBand)

Descripción Transfer a numeric value (sourceValue) to the database, takinginto account that the value in the database is written if and onlyif the value is changed to at least the value indicated in dead-Band. For example, if the deadBand value is 100, no value ofsourceValue will be written to memory address 1000 unless thevalue of sourceValue is greater than or equal to 1100 or less thanor equal to 900.This function is mainly used To limit the bandwidth of valueswhen they are transmitted wirelessly. For example certain valuesread in a protocol can move to another direction with some dead-band, to avoid that tiny changes begin transmissions in wirelessprotocols.

Parameters sourceValue Value to be written to the database.

destAddr

Destination address in the database. This address is inbytes. This should be remembered when configuringthe function since in other configuration parametersthe address is usually given in words.

destType

It is the data type in the destination address. This pa-rameter in a string y can have any of the followingvalues:’UINT8’’UINT16’’INT16’’INT32’’UINT32’’FLOAT’

deadBandDead band value. The source value must change atleast this amount so that its value is propagated to thedatabase.

Returns This function does not return values

Example -- The first line will write 5000-- in INT16 format in the byte position-- 2000 (Word 1000) from the databaseNewline -- (assuming that the initial valueof this-- position is 0).



[email protected]


- The second line will not write anything- Since the change (99) is smaller than the- deadband (100).- The third line will make the value- 5100 is written in the database- The fourth line will not write anything- since change (5100 - 5001 = 99)Is smaller- than the deadband(100).- in the fifth line re-copies 5000 in- the database.

deadBandValue(5000, 2000, ’INT16’, 100)deadBandValue(5099, 2000, ’INT16’, 100)deadBandValue(5100, 2000, ’INT16’, 100)deadBandValue(5001, 2000, ’INT16’, 100)deadBandValue(5000, 2000, ’INT16’, 100)



[email protected]


Function: deadBandDb

Function deadBandDb (sourceAddr,sourceType,destAddr,destType,deadBand)

Description Transfer a numerical value from one database address to an-other database address, taking into account that the value in thedatabase is written if and only if the value has changed by at leastthe value indicated in deadBand . For example if the memoryvalue in the destAddr address is 1000 and the deadBand valueis 100, no database value in the source address will be writtento the memory address 1000 unless the read value is greater orEqual to 1100 or less or equal to 900.This function is mainly used to limit the bandwidth of valueswhen they are transmitted wirelessly. For example certain valuesread in a protocol can move to another direction with some dead-band, to avoid that tiny changes begin transmissions in wirelessprotocols.

Parameters sourceAddr

Source address in the database. This address is inbytes. This should be remembered when configuringthe function since in other configuration parametersthe address is usually given in words.

sourceType

:’UINT8’’UINT16’’INT16’’INT32’’UINT32’’FLOAT’

destAddr

Destination address in the database. This address is inbytes. This should be remembered when configuringthe function since in other configuration parametersthe address is usually given in words.



[email protected]


destType

It is the data type in the destination address. This pa-rameter in a string y can have any of the followingvalues:’UINT8’’UINT16’’INT16’’INT32’’UINT32’’FLOAT’

deadBandDead band value. The source value must change atleast this amount so that its value is propagated to thedatabase.

Returns this function does not returns values

Example -- The first deadBand will write 5000-- in INT16 format in the byte position-- 2000 (Word 1000) from the database-- (assuming that the initial value of this-- position is 0).-- The second deadBand will not write anything--That the change (99) is smaller than the-- deadband (100).-- The third deadBand is going to make thevalue-- 5100 is written in the database-- The fourth deadBand will not write anythinganymore-- that the change (5100 - 5001 = 99) issmaller-- than the dead band (100).-- The fifth deadBand re-copies 5000 in-- the database.

mainDatabase:setINT16(1000,5000)deadBandDb(1000,’INT16’, 2000,’INT16’,100)mainDatabase:setINT16(1000,5099)deadBandDb(1000,’INT16’, 2000,’INT16’,100)mainDatabase:setINT16(1000,5100)deadBandDb(1000,’INT16’, 2000,’INT16’,100)mainDatabase:setINT16(1000,5001)deadBandDb(1000,’INT16’, 2000,’INT16’,100)mainDatabase:setINT16(1000,5000)deadBandDb(1000,’INT16’, 2000,’INT16’,100)



[email protected]


Numeric Database ObjectNUMERIC_DATABASEAlias:mainDatabase

Both NUMERIC_DATABASE and main database can be used indistinctly, how-ever in future versions of firmware, mainDatabase, could disappear, so it is advisableto start new developments using NUMERIC_DATABASE.

Object NUMERIC_DATABASE

Function: setUINT8(índex,value)

Description: Write an 8-bit unsigned integer in the numeric database.

Parameters: Index Index in bytes of the database to write.

Value Numeric value to be written to the database. Itmust be in the range of 0 to 255.

Returns: Nothing

Example: -- Write 123 In the first byte of the-- databaseNUMERIC_DATABASE:setUINT(0,123)-- Forma AlternativamainDatabase:setUINT(0,123)

Objeto NUMERIC_DATABASE

Función: setUINT16(Index, value, [Exchange code])

Description: Write a 16-bit unsigned integer in the numeric database.


Value Numeric value to be written to the database. Mustbe in the range of 0 to 65535.

Exchangecode

Optional. Form in which the bytes must be or-dered as they are written in the database:0: Do not swap bytes.1: Exchanging bytes.

Returns: nothing

Example: -- Write 12345 in the first byte of the-- Database without exchanging bytesNUMERIC_DATABASE:setUINT16(0,12345,0)



[email protected]



Function: getUINT8(Index)

Description Reads from the numeric database an 8-bit unsigned integer.

Parameters Index Index in bytes to read from the database.

Returns Number Result of reading the database as a number in therange of 0 to 255.

Example -- Gets the value of the first byte of the-- databaselocal value = NUMERIC_DATABASE:getUINT8(0)-- alternative Form local value =mainDatabase:getUINT8(0)


Function: getUINT16(Index, Exchange code)

Description Reads from the numeric database an unsigned 16-bit integer.


Exchangecode

Form in which the bytes must be ordered as theyare written in the database:0: Do not swap bytes1: swap bytes.

Returns Number Result of reading the database as a number in therange of 0 to 65535.

Example -- Gets the value of the first word of-- the databaselocal value = NUMERIC_DATABASE:getUINT16(0)-- alternative form local value =mainDatabase:getUINT16(0)



[email protected]



Function: getINT16(Index, Exchange code)

Description Reads from the numeric database a 16-bit integer.


Exchangecode

Form in which the bytes must be ordered as theyare written in the database:0: Do not swap bytes1: swap bytes.

Returns Number Result of reading the database as a number in therange of -32.768 to 32.767

Example -- Gets the value of the first word of-- the databaselocal value = NUMERIC_DATABASE:getINT16(0)-- alternative form local value =mainDatabase:getINT16(0)


Función: setINT16(Index, value, [Exchange code])

Description: Write a 16-bit integer in the numeric database.


Value Numeric value to be written to the database. Mustbe in the range of -32.768 to 32.767.

Exchangecode

Optional. Form in which the bytes must be or-dered as they are written in the database:0: Do not swap bytes.1: Exchanging bytes.

Returns: nothing

Example: -- Write 12345 in the first byte of the-- Database without exchanging bytesNUMERIC_DATABASE:setINT16(0,12345,0)



[email protected]



Function: getINT32(Index, Exchange code)

Description Reads from the numeric database a 32-bit integer.


Exchangecode

Form in which the bytes must be ordered as theyare written in the database:0: Do not swap bytes1: swap bytes.2: swap words.3: swap word and bytes.

Returns Number Result of reading the database as a number in therange of -2.147.483.648 a 2.147.483.647.

Example -- Gets the value of the first word of-- the databaselocal value = NUMERIC_DATABASE:getINT32(0)-- alternative form local value =mainDatabase:getINT32(0)


Función: setINT32(Index, value, [Exchange code])

Description: Write a 32-bit integer in the numeric database.


Value Numeric value to be written to the database. Mustbe in the range of -2.147.483.648 a 2.147.483.647.

Exchangecode

Optional. Form in which the bytes must be or-dered as they are written in the database:0: Do not swap bytes1: swap bytes.2: swap words.3: swap word and bytes.

Returns: nothing

Example: -- Write 1234567 in the first byte of the-- Database without exchanging bytesNUMERIC_DATABASE:setINT32(0,1234567,0)



[email protected]



Function: getUINT32(Index, Exchange code)

Description Reads from the numeric database a 32-bit unsigned integer.


Exchangecode


Returns Number Result of reading the database as a number in therange of 0 a 4.294.967.294.

Example -- Gets the value of the first word of-- the databaselocal value = NUMERIC_DATABASE:getUINT32(0)-- alternative form local value =mainDatabase:getUINT32(0)


Función: setUINT32(Index, value, [Exchange code])

Description: Write a 32-bit unsigned integer in the numeric database.


Value Numeric value to be written to the database. Mustbe in the range of 0 a 4.294.967.294.

Exchangecode

Optional. Form in which the bytes must be or-dered as they are written in the database:0: Do not swap bytes1: swap bytes.2: swap words.3: swap word and bytes.

Returns: nothing

Example: -- Write 1234567 in the first byte of the-- Database without exchanging bytesNUMERIC_DATABASE:setUINT32(0,1234567,0)-- alternative form local value =mainDatabase:setUINT32(0,1234567,0)



[email protected]



Function: getFLOAT(Index, Exchande code)Description Read from the numeric database in IEEE 754-2008 32-bit

floating point format


Exchandecode


Returns Number Result of reading the database as a floating pointnumber.

Example -- Get the value of the first number-- in floating point format-- from the database-- without exchanging words and byteslocal value = NUMERIC_DATABASE:getFLOAT(0)-- Alternative Formlocal value = mainDatabase:getFLOAT(0)


Function: setFLOAT(Index, Value, Exchange code)

Description Write a number in the IEEE 754-2008 32-bit floating-pointformat in the numerical database.


Value Numeric value to be written to the database.

Exchangecode


Returns Nothing

Example -- Write 1,234 in the first word-- floating point of the database-- without exchanging bytesNUMERIC_DATABASE:setFLOAT(0,1,234,0)-- Alternative FormmainDatabase:setFLOAT(0,1,234,0)



[email protected]



Function: getBit(Index)

Description Reads from the numeric database a bit in Boolean format.


Returns Bit Returns true or false depending on the state of thespecified bit.

Example -- Gets the value of the first bit-- in boolean format-- from the database-- without exchanging words and byteslocal value = NUMERIC_DATABASE:getBit(0)-- Alternative Formlocal value = mainDatabase:getBit(0)


Función: setBit(Index, Value)

Descripción Write a bit in the numerical database.


Value Numeric value to be written to the database.

Returns Nothing

Example -- Write bit in one first bit-- from the databaseNUMERIC_DATABASE:setBit(0,true)-- Write bit in zero in first bit of-- the second word in the databasemainDatabase:setBit(16,0)

10 Internal Diagnostic DataThe internal diagnostic data is obtained by consulting the STATUS _DATA table.



[email protected]


Element Content

STATUS_DATA.SerialPortsStatus.COM1 Internal Diagnostic Data SerialPort 1

STATUS_DATA.SerialPortsStatus.COM2 Internal Diagnostic Data SerialPort 2

STATUS_DATA.NetProtocols[Index] Network Diagnostics Drivers byIndex Data

STATUS_DATA.NamedNetProtocols[nombre]Diagnostics Data of NetworkCommunication Drivers byName

Within each of these elements the status information is determined by the commu-nications driver that is configured for that port.

10.1 ModBus RTU Maestro

MODBUS RTU MASTER: Elements of the diagnostic table

STAT_CmdsExecuted Number of Executed Commands

STAT_CmdsOK Number of commands successfully ex-ecuted

STAT_CmdsERR Number of commands executed witherror

STAT_CmdsERR_TO Number of commands executed withTime Out

STAT_CmdsERR_ITO Number of commands executed withTime Out between characters

STAT_CmdsERR_CRC Number of commands with CRC error

STAT_CmdsERR_INV Number of commands invalidly re-ceived

STAT_CmdsERR_MB Number of commands with Modbus er-rors

STAT_CmdsERR_OTHERS Number of commands with other errors

CmdLastError[index] List of errors per command indexed nu-merically

NamedCmdLastError[name] List of errors per command indexed byname



[email protected]


MODBUS RTU MASTER: Meaning of command errors

0 OK

-1 Timeout

-2 Timeout between characters

-3 CRC invalid

-4 Function Invalid

-5 Node Address Invalid

-6 Indirect Node Address Invalid

-1000 Function Invalid

-10000 Command not executed

1 Function Invalid

2 Address Invalid

3 Invalid Value

4 Slave Failure

MODBUS RTU Master: Status Query Examples

-- Obtain the number of commands with Modbus error-- RTU Master configured on COM1 portlocal errCount = STATUS_DATA.SerialPortsStatus.COM1.STAT_CmdsERR-- Copy number into the database in word 100mainDatabase:setUINT32(200,errCount)-- If the command number 5 is in error, put a-- error code in the databaselocal errStatus = STATUS_DATA.SerialPortsStatus.COM1. CmdLastError[5]if errStatus ~= 0 then

NUMERIC_DATABASE:setUINT16(1000, -10000)NUMERIC_DATABASE:setUINT16(1002, -10000)NUMERIC_DATABASE:setUINT16(1004, -10000)

End



[email protected]


10.2 Modbus TCP Client

MODBUS TCP Client: Elements of the Diagnostic Table


STAT_CmdsOK Number of commands successfully ex-ecuted

STAT_CmdsERR Number of commands executed witherror

STAT_CmdsERR_TO Number of commands executed withTime Out

STAT_CmdsERR_ITO Number of commands executed withTime Out between characters

STAT_CmdsERR_CRC Number of commands with CRC error

STAT_CmdsERR_INV Number of commands invalidly re-ceived

STAT_CmdsERR_MB Number of commands with Modbus er-rors

STAT_CmdsERR_INV_IP Number of commands with IP addressInvalid

STAT_CmdsERR_UNABLE_TO_CONNECTNumber of commands for which it wasnot possible to connect



NamedCmdLastError[name] List of errors per command indexed byname



[email protected]


MODBUS TCP CLIENT: Meaning of command errors

0 OK

-1 Timeout

-2 Timeout between characters

-3 CRC invalid

-4 Function Invalid

-5 IP Address Invalid

-6 Could not connect

-7 Function Invalid




1 Function Invalid

2 Address Invalid

3 Invalid Value

4 Slave Failure

MODBUS TCP Client: Status Query Examples

-- Obtain the number of commands with Modbus error-- TCP Client configured as "Modbus TCP Client"local errCount = STATUS_DATA.NamedNetProtocols["ModbusTCP Client"].STAT_CmdsERR-- Copy number into the database in word 100mainDatabase:setUINT32(200,errCount)-- If the command number 5 is in error, put a-- error code in the databaselocal errStatus = STATUS_DATA.NamedNetProtocols["Modbus TCPClient"].CmdLastError[5]if errStatus ~= 0 then

NUMERIC_DATABASE:setUINT16(1000, -10000)NUMERIC_DATABASE:setUINT16(1002, -10000)NUMERIC_DATABASE:setUINT16(1004, -10000)

End



[email protected]


10.3 Modbus TCP Server

MODBUS TCP SERVER: Items in the diagnostic table

TCPConnAccepted Number of TCP Connections Accepted

TCPConnRejected Number of Rejected TCP Connections

MODBUS TCP Server: Status Query Examples

-- Get the number of connections acceptedlocal connAccepted = STATUS_DATA.NamedNetProtocols["ModbusTCP Server"].TCPConnAccepted-- Copy number into the database in word 100mainDatabase:setUINT32(200,connAcepted)

10.4 IZINET

IZINET: Interfaces name

LINK_10k_900MHz

IZINET: Elements of the diagnostic table

STAT_WrRqTxExeOK Number of Writing Requests Transmittedand Exected Successfully

STAT_WrRqTxExe Number of Written Transmission Requests

STAT_WrRqTxExeERR_Refused Number of Transmitted Write RequestsRejected by Remote Node

STAT_WrRqRxExeOK Number of Written Requests Received

STAT_WrRqRxExeERR_Refused Number of Write Requests Received andRejected by Local Node

STAT_WrRqTxExeERR_TimeOutNumber of Written Requests Transmittedwithout execution confirmation from theremote node

STAT_WrRqTxExeERR Number of transmitted write requests exe-cuted with error



[email protected]


LnkPayloadToolarge Number of commands with very long pay-load error

LnkDirectMsgUrq Number of commands with direct messageerror Unsolicited

LnkRouteNotFound Number of commands with path error notfound

LnkMACACKFailure Number of commands with error for con-firmation failure at MAC level

LnkNetworkACKFailure Number of commands with network-levelerror confirmation error

PtlRfsdOverallMmatch Number of commands rejected by incom-patible format

INFO_LinkDriverSs Text indicating driver status


IZINET: Meaning of command errors

0 OK

1 Confirmation failure at MAC level

33 Network-level acknowledgment failure

37 Route Not Found

116 Very long payload

117 Unsolicited Direct Message

200 Protocol: Waiting for remote ACK

201 Protocol: Remote ACK TimeOut

100 Protocol: Refused Physical Address mismatch

101 Protocol: Refused Source Db Start Word mismatch

102 Protocol: Refused Source Db Byte Count mismatch

103 Protocol: Refused Command Type mismatch

104 Protocol: Refused Db Out of Range

105 Protocol: Refused Overall mismatch

106 Protocol: Receive TimeOut


-10000 Command Not Executed



[email protected]


IZINET: Status Query Examples

- Obtain the number of transmitted Scripture requests- and successfully executedlocal errCount =STATUS_DATA.IziNet900Protocols.LINK2_10K_900MHz.STAT_WrRqTxExeOK- Copy number into the database in word 100mainDatabase:setUINT32(200,errCount)-- Of being in error in command 1 put a code-- error in the databaselocal errStatus =STATUS_DATA.IziNet900Protocols["LINK2_10K_900MHz"].CmdLastError[1]NUMERIC_DATABASE:setINT16(1000*2,errStatus,0)

10.5 MODULE INFORMATION

MODULE: Name of Interfaces

MODULE

MODULE: Elements of the diagnostic table

runtimeinfo.date Date

runtimeinfo.time Time

osinfo.uptime Number of commands executed with error

osinfo.memtotal Total RAM available

osinfo.memfree Total free RAM

osinfo.luamem Total RAM used by the application

versioninfo.DEVICE_TYPE Product Name

versioninfo.FIRMWARE_VER Firmware

versioninfo.HARDWARE_CODE Hardware Name

configinfo.DBSize Size in 16-bit words from the database

configinfo.Name User-defined name

configinfo.Comment Comment defined by user

configinfo.version Configuration file version



[email protected]


10.6 Ethernet/IP Tag Client

Ethernet/IP Tag Client: Elements of the diagnostic table


STAT_CmdsOK Number of successfully executed com-mands

STAT_CmdsERR Number of commands executed with error

STAT_CmdsERR_CIP Number of commands executed with CIPError

STAT_CmdsERR_UNABLE_TO_CONNECT

Number of commands with non-connection error

STAT_CmdsERR_CIP_INV Number of invalid commands



Ethernet/IP Tag Cliente: Meaning of command errors

0 OK

-1000 Invalid Command

-1001 Invalid Tag Name

-1003 Invalid number of records

-10000 Command not yet executed



[email protected]


Ethernet/IP Tag Client: Status Query Examples

-- Obtain the number of commands with Ethernet / IPerror-- Tag Client-- Configured with name "Ethernet/IP Tag Client" localerrCount =STATUS_DATA.NamedNetProtocols[“EtherNet/IP Tag Client”].STAT_CmdsERR-- Copy number into the database in word 100mainDatabase:setUINT32(200,errCount)-- Of being in error in command 5 putting a code-- error in the databaselocal errStatus =STATUS_DATA.NamedNetProtocols[“EtherNet/IP TagClient”].CmdLastError[5]-- if errStatus ∼= 0 then-- NUMERIC_DATABASE:setUINT16(1000, -10000)-- NUMERIC_DATABASE:setUINT16(1002, -10000)-- NUMERIC_DATABASE:setUINT16(1004, -10000)-- End



[email protected]


PROTON CMB

Documents

Transcript of PROTON CMB