Pixsys ECO-CNV510-PNET-RTU-A User manual

pag. 1
ECO-CNV510-PNET-RTU-A
Software version SW67602
PROFINET Slave / Modb s Master Converter
User Manual

pag. 2
WARNING:
Pixsys srl reserves the right to change information in this manual about our product without warning.
Pixsys srl is not responsible for any error this manual may contain.
TRADEMARKS:
All trademarks mentioned in this document belong to their respective owners.
SECURITY ALERT:
GENERAL IN ORMATION
To ensure safe operation, the device must be operated according to the instructions in the manual. When using the device, legal and safety regulation are required for
each individual application. The same applies also when using accessories.
INTENDED USE
achines and systems must be designed so the faulty conditions do not lead to a dangerous situation for the operator (i.e. independent limit switches, mechanical
interlocks, etc.).
QUALI IED PERSONNEL
The device can be used only by qualified personnel, strictly in accordance with the specifications.
Qualified personnel are persons who are familiar with the installation, assembly, commissioning and operation of this equipment and who have appropriate
qualifications for their job.
RESIDUAL RISKS
The device is state-of-the-art and is safe. The instruments can represent a potential hazard if they are inappropriately installed and operated by untrained personnel.
These instructions refer to residual risks with the following symbol:
This symbol indicates that non-observance of the safety instructions is a danger for people that could lead to serious injury or death and / or the possibility of
damage.
CE CON ORMITY
The declaration is made by our company. You can send an email to [email protected]t or give us a call if you need it.

pag. 3
CHARACTERISTICS:
The CNV510-PNET-RTU-A is a PROFINET Slave  odbus aster Converter.
It allows the following characteristics:
Up to 512 bytes in reading and 512 bytes in writing;
Triple isolation between odbus - Power Supply, odbus - Ethernet, Power Supply – Ethernet;
Two-directional information between odbus bus and PROFINET bus;
ountable on 35mm Rail DIN;
Wide power supply input range: 8..24V AC or 12..35V DC ( aximum consumption at 24V: 3 W / VA);
Wide environment conditions: 0..45°C, humidity 35..95 uR%.
CON IGURATION:
You need Software SW67602 on your PC in order to perform the following:
Define the parameter of the PROFINET line;
Define the parameter of the odbus line;
Define the data to Read in odbus and where to map these information in the PROFINET array;
Define the data to Write in odbus and where to take the information in the PROFINET array;
Update the device.

pag. 4
MECHANICAL DIMENSIONS:

pag. 5
EXAMPLE O CONNECTION:

pag. 6
CONNECTION SCHEME:

pag. 7
POWER SUPPLY:

pag. 8
UNCTION MODES:
The device has got two functions mode depending of the position of the ‘Dip2 of Dip-Switch A’:
The first, with ‘Dip2 of Dip-Switch A’ at “OFF” position, is used for the normal working of the device.
The second, with ‘Dip2 of Dip-Switch A’ at “ON” position, is used for upload the Project and/or Firmware.
For the operations to follow for the updating, see ‘UPDATE DEVICE’ section.
According to the functioning mode, the LEDs will have specifics functions, see ‘LEDS’ section.
Warning:
Dip1 of ‘Dip-Switch A’ must be always at ON position!

pag. 9
LEDS:
LEDs that are used to give information of the functioning status.
The various meanings of the LEDs are described in the table below.
LED Normal Mode Boot Mode
1: ON [supply voltage] (green) ON: Device powered
O : Device not powered
ON: Device powered
O : Device not powered
2: PT [PROFINET state] (yellow) ON: PROFINET transmissions present
LASHING: No PROFINET transmissions present
3: T [ odbus state] (yellow) ON: ODBUS-RTU transmissions present
LASHING: No ODBUS-RTU transmissions present
4: Ethernet1 Tx (green) Blinks when is transmitting Ethernet frames Blinks quickly: Boot state
Blinks very slowly (~0.5Hz): Update in progress
Internal LED (green) Blinks very slowly (~0.5Hz): Device is working in normal mode

pag. 10
PRO INET:
The PROFINET connection must be made using Connector3 with at least a Category 5E cable. The maximum length of the cable should not exceed 100m. The cable must conform
to the T568 norms relative to connections in cat.5 up to 100 bps. To connect the device to an Hub/Switch is recommended the use of a straight cable, to connect the device to
a PC/PLC/other is recommended the use of a cross cable.

pag. 11
RS485:
For terminate the RS485 line with a 120Ω resistor it is necessary to put ON dip 1, like in figure.
The maximum length of the cable should be 1200m (4000 feet).
Here some codes of cables:
Belden: p/n 8132 - 2x 28AWG stranded twisted pairs conductor + foil shield + braid shield;
Belden p/n 82842 - 2x 24AWG stranded twisted pairs conductor + foil shield + braid shield;
Tasker: p/n C521 - 1x 24AWG twisted pair conductor + foil shield + braid shield;
Tasker: p/n C522 - 2x 24AWG twisted pairs conductor + foil shield + braid shield.

pag. 12
USE O CON IGURATION SO TWARE SW67602:
To configure the Converter, use the available software that runs with Windows called SW67602. It is downloadable on the Pixsys download are ( https://cloud.pixsys.net/ ) and its
operation is described in this document. (This manual is referenced to the last version of the software present on our web site). The software works only on icrosoft Windows (XP,
Vista, Seven, 8, 10; 32/64bit architectures).
When launching the SW67602, the window below appears (Fig. 2).
Note:
It is necessary to have installed .Net Framework 4.
Figure 2: Main window for SW67602

pag. 13
NEW CON IGURATION / OPEN CON IGURATION:
The “New Configuration” button creates the folder which contains the entire device’s configuration.
A device’s configuration can also be imported or exported:
To clone the configurations of a Programmable “PROFINET Slave / odbus aster - Converter” in order to
configure another device in the same manner, it is necessary to maintain the folder and all its contents;
To clone a project in order to obtain a different version of the project, it is sufficient to duplicate the project
folder with another name and open the new folder with the button “Open Configuration”.

pag. 14
SO TWARE OPTIONS:
By pressing the “Settings” ( ) button there is the possibility to change the language of the software and check the updatings for the compositor.
In the section “Language” it is possible to change the language of the software.
In the section “Connection Options”, it is possible to check if there are some updatings of the
software compositor in Pixsys srl website.
Checking the option “Check Software Update at Start of Program”, the SW67602 check
automatically if there are updatings when it is launched.

pag. 15
SET COMMUNICATION:
This section defines the fundamental communication parameters of two buses, PROFINET and odbus.
By Pressing the “Set Communication” button from the main window for SW67602 (Fig. 2) the window “Set Communication”
appears (Fig. 3).
The window is divided in two sections, one for the PROFINET and the other for the odbus aster.
The means of the fields for “PROFINET” are:
In the fields “IP ADDRESS” insert the IP address that you want to give to the Converter;
In the fields “SUBNET Mask” insert the Subnet ask;
In the fields “GATEWAY” insert the default gateway that you want to use. This feature can be enabled or disabled pressing
the Check Box field. This feature is used for going out of the net;
In the field “Port” is possible to define the port to use for the “Tunneling mode” (see “Advanced functions” section for
more details);
In the field "PRO INET Name of Station" is possible to assign a name to the PROFINET node;
In the fields “Number Byte IN” insert the number of input byte of the slave station;
In the fields “Number Byte Out” insert the number of output byte of the slave station;
In the field “Diagnostic” insert the starting byte of the PROFINET array where you will save the diagnostic of odbus. It is
possible to enable/disable this function using the checkbox.
For more information about the diagnostic, see “Diagnostic” section.
The means of the fields for the “ odbus aster” section are:
In the field “Serial” the serial to use is defined (select RS485);
In the field “Baudrate” the baudrate for the serial line is defined;
In the field “Parity” the parity of the serial line is defined;
In the field “TimeOut (ms)” there is the maximum time that the device attends for the answer from the Slave
interrogated;
In the field “Communication Idle Time (ms)” the minimun delay between two polls is defined.
Figure 3: “Set Communication” window

pag. 16
SET ACCESS:
By pressing the “Set Access” button from the main window for SW67602 (Fig. 2) the window “Set Access” appears.
This window is divided in two parts, the "Modb s Read" (Fig. 4) and the "Modb s Write" (Fig. 5).
The first part " odbus Read" is used to read the data from the odbus slaves, and make them available to read from the aster PROFINET.
The second part " odbus Write " is used to write the data that arrives from the aster PROFINET into the slaves odbus.
MODBUS READ:
The means of the fields are:
In the field “Slave ID” is defined the address of the
odbus device you have to read;
In the field “Type” insert the data type of the
register you would like to read. You can choose
between the following:
oCoil Status;
oInput Status
oHolding Register;
oInput Register.
In the field “Address” is defined the start address
of the register to be read;
In the field “NPoint” insert the number of consecutive registers to be read;
In the field “Poll Time” insert the time to make this request;
In the field “Max Error” is the number of errors continues that the gateway waits before suspending the poll until the next reboot. If is set to zero, this function is disabled;
In the field “Position” insert the address of the PROFINET array where place the information;
In the field “Start Bit” insert the start bit of the first byte of the field “Position” where start to insert the data read. Valid only for the “Coil Status” and “Input Status”.
In the field “Mnemonic” the description for the request is defined.
Figure 4: “Set Access  Mod us Read” window

pag. 17
MODBUS WRITE:
The means of the fields are:
In the field “Slave ID” is defined the address of the
odbus device that you have to write;
In the field “Type” insert the data type of the
register you would like to read. You can choose
between the following:
oCoil Status;
oHolding Register;
In the field “Address” is defined the start address
of the register to be written;
In the field “NPoint” insert the number of
consecutive registers to be written;
In the field “Poll Time” insert the time to make this request;
If the field “On Change” is checked, the gateway send the Write request in odbus when the data change the value.
In the field “Max Error” is the number of errors continues that the gateway waits before suspending the poll until the next reboot. If is set to zero this function is disabled;
In the field “Position” insert the address of the PROFINET array where read the information;
In the field “Start Bit” insert the start bit of the first byte of the field “Position” where start to read the data to write. Valid only for the “Coil Status”;
In the field “Mnemonic” the description for the request is defined.
Note:
If you want that the converter sends the data only “On change” the “Poll Time” must be at 0.
Note:
If the field “On change” is checked and the “Poll Time” is different from 0, the converter sends the Write request cyclically and also when the data is changed.
Figure 5: “Set Access --> Serial Write” window
Figure 5: “Set Access  Mod us Write” window

pag. 18
UPDATE DEVICE:
By pressing the “Update Device” button it is possible to load the created configuration into the device; and also the Firmware, if is necessary.
If you don’t know the actual IP address of the device you have to use this procedure:
Turn off the Device;
Put Dip2 of ‘Dip-Switch A’ at ON position;
Turn on the device
Connect the Ethernet cable;
Insert the IP “192.168.2.205”;
Press the “Ping” button, must appear “Device Found!”;
Press the “Next” button;
Select which operations you want to do;
Press the “Execute update firmware” button to start the upload;
When all the operations are “OK” turn off the Device;
Put Dip2 of ‘Dip-Switch A’ at OFF position;
Turn on the device.
At this point the configuration/firmware on the device is correctly updated.
Figure 6: “Update device” windows

pag. 19
If you know the actual IP address of the device, you must use this procedure:
Turn on the Device with the Ethernet cable inserted;
Insert the actual IP of the Converter;
Press the “Ping” button, must appear “Device Found!”;
Press the “Next” button;
Select which operations you want to do;
Press the “Execute update firmware” button to start the upload;
When all the operations are “OK” the device automatically goes at Normal ode.
At this point the configuration/firmware on the device is correctly update.
Note:
When you install a new version of the software it is better if the first time you do the update of the Firmware in the CNV510-PNET-RTU-A device.
Note:
When you receive the device, for the first time, you must update also the Firmware in the CNV510-PNET-RTU-A device.
Warning:
If the Fig. 7 appears when you try to do the Update before require assistance try these points:
Try to repeat the operations for the updating;
Try with another PC;
Try to restart the PC;
If you are using the program inside a Virtual achine, try to use in the main Operating System;
If you are using Windows Seven or Vista or 8/10, make sure that you have the administrator privileges;
Take attention at Firewall lock;
Check the LAN settings.
Figure 7: “Protection” window

pag. 20
MODBUS DIAGNOSTIC OVER PRO INET:
During the normal functioning of the device, if all the programmed odbus requests have received a valid reply (not an exception error), every PROFINET frame has the "Data
Status" byte at the value of 0x35.
Otherwise, if at least one odbus reply is not valid, the "Data Status" byte assumes the value 0x15; that means "Problem Indicator".
If this happens, using the port 5000 there is a UDP message that is possible to send in order to understand which odbus modules have generated that error.
This command is described in the section "Advanced Functions" under the “B2 command”.
oreover, it is possible to save the odbus Diagnostic on Output PROFINET array using the field “Diagnostic” of the section “Set Communication”.
In this case, the status of each odbus request defined in the section “Set Access” is saved starting from the byte of the PROFINET array defined in the section “Set
Communication”.
Each bit will represent the status of a odbus request:
If for a request the converter receives a correct response, the status bit is put to ‘0’;
If for a request the converter receives a wrong response or it doesn’t receive any response, the status bit is put to ‘1’.
Example:
In the section “Set Access” are defined 8 odbus reading requests (“ odbus Read” table) and 8 odbus writing requests (“ odbus Write” table). The odbus reading requests
are working and the odbus writing request are not working.
The status bits of the odbus Diagnostic on PROFINET will be:
Byte x Byte x+1
bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0
0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1
where ‘x’ is the starting byte of the PROFINET array where the odbus diagnostic is saved.