Start-up: iX TxA SoftControl, FnIO-S NA-9173 / NA-9473 Modbus RTU (KI00327)

​With the HMI soft controllers in the iX TxA SoftControl series, any HMI application can have an intuitive graphic iX interface with total CODESYS control. The operator terminal iX TxA SoftControl communicates with a remote I/O (Crevis FnIO-S Serie) in a Modbus RTU (serial) network.

Attached ProgExample_TxA_SC_ModbusRTU_KI00327.zip includes program example for CODESYS and iX Developer.

The folder in “zip-file" contains:
KI00327: Start-up document for iX TxB SoftControl and NA-9173/NA-9473 Modbus RTU
Project_TxA_Modbus_NA9173: CODESYS and iX Developer project

Programming software needed for the attached example:
 - iX Developer 2.0 SP1 (b 2.0.463.0) or later, programming the HMI in iX TxA SoftControl
 - CODESYS v3.5 SP1 Patch 4 or later, programming the soft control

Note!
Start-up document KI00326 and KI00327 replace KI00302

• ProgExample_TxA_SC_ModbusRTU_KI00327.zip

CoDeSys in TxA SoftControl, ST-3702 change Pt100 to Pt1000

• CoDeSys_TxA_SoftControl_ParamSet_NA9173.pdf
• T4A_SoftControl_NA9173_ST3702.zip

Start-up: IPsec VPN tunnel to iX panel (KI00333)

• KI00333.pdf

Start-up: iX TxA SoftControl, Basic setting (KI00326)

With the HMI soft controller in the iX TxA SoftControl series, any HMI application can have an intuitive graphic iX interface with total CODESYS control. The soft controller communicates with an external device, for example a remote I/O.

Attached StartKit_TxA_SoftControl_KI00326_.zip includes files for CODESYS and iX Developer.
The folder in the “zip-file" contains:
KI00326A: Start-up document iX TxA SoftControl Basic setting.
Diagnostic Tag: Import of “Diagnostic Tag” to your iX project.

Programming software needed for the attached example:
- iX Developer 2.0 SP1 (b 2.0.463.0) or later, programming the HMI in iX TxA SoftControl
- CODESYS s v3.5 SP1 Patch 4 or later, programming the soft control

See related links to download:
- Recommended version of CODESYS 3.5
- Manuals for Crevis and iX Developer

Note!
Start-up document KI00326 and KI00327 replace KI00302

• StartKit_TxA_SoftControl_KI00326B.zip

Start-up: iX TxB SoftControl, NA-9286 EtherCAT (KI00329) (Codesys runtime 3.5.1.40)

This start-up document applies for TxB SoftControl using Codesys runtime 3.5.1.40.

With the iX HMI soft controllers in the iX TxB SoftControl series, any HMI application can have an intuitive graphic iX interface with total CODESYS control. The operator terminal iX TxB SoftControl communicates with a remote I/O (Crevis FnIO-S Serie) in a EtherCAT network.

Attached ProgExample_TxB_SC_EtherCAT_KI00329x.zip includes program example for CODESYS and iX Developer.

The folder in “zip-file" contains:
KI00329x: Start-up document iX TxB SoftControl Basic setting.
Device Description Crevis NA9286: The files enable NA-9186 in CoDeSys.
Project_TxB_EtherCAT_NA9286: CODESYS and iX Developer project

Programming software needed for the attached example:
 - iX Developer 2.10 SP2 or later, programming the HMI in iX TxA SoftControl
 - CODESYS v3.5 SP1 Patch 4 or later, programming the Soft Control

NOTE!
NA-9286 is a replacement for NA-9186.

• ProgExample_TxB_SC_EtherCAT_KI00329B.zip

Start-up: iX TxB SoftControl, FnIO-S Serie ModbusTCP (KI00330) (Codesys runtime 3.5.1.40)

This start-up document applies for TxB SoftControl using Codesys runtime 3.5.1.40.

With the HMI soft controllers in the iX TxB SoftControl series, any HMI application can have an intuitive graphic iX interface with total CODESYS control.
The operator panell iX TxB SoftControl communicates with a remote I/O (Crevis FnIO-S Serie) in a Modbus TCP network.

Attached ProgExample_TxB_SC_ModbusTCP_KI00330x.zip includes program example for CODESYS and iX Developer.

The folder in “zip-file" contains:
KI00330x: Start-up document for iX TxB SoftControl and NA-9189 / NA-9289 ModbusTCP
Project_TxB_Modbus_NA9_89: CODESYS and iX Developer project

Programming software needed for the attached example:
 - iX Developer 2.10 SP2 or later, programming the HMI in iX TxA SoftControl
 - CODESYS v3.5 SP1 Patch 4 or later, programming the Soft Control

• ProgExample_TxB_SC_ModbusTCP_KI00330B.zip

Start-up: iX TxB SoftControl, Basic Settings (KI00375) (Codesys runtime 3.5.7.10)

• KI00375.pdf
• StartUp_iX_T7B_SoftControl_BasicSettings_v001.zip

Start-up: iX TxB SoftControl, Basic Setting (KI00328) (Codesys runtime 3.5.1.40)

• StartKit_TxB_SoftControl_KI00328D.zip

Start-up: iX TxB SoftControl, NA-9286 EtherCAT (KI00376) (Codesys runtime 3.5.7.10)

• KI00376A.pdf
• StartUp_iX_T7B_SoftControl_EtherCAT_v002.zip

Start-up: iX TxB SoftControl, NA-9173/NA-9473 Modbus RTU (KI00378) (Codesys runtime 3.5.7.10)

• KI00378.pdf
• StartUp_iX_T7B_SoftControl_ModbusRTU_v001.zip

Start-up: iX TxB SoftControl, FnIO-S Serie ModbusTCP (KI00377) (Codesys runtime 3.5.7.10)

• KI00377.pdf
• StartUp_iX_T7B_SoftControl_ModbusTCP_v001.zip

iX TxB-SC, NA-9289, ST-5101, ST-5111, ST-5112, ST-5114, Program example

​

Crevis FnIO S-Series, Manuals

• TxB_SC_NA9289_ST5111_35SP7P10_20170228.zip
• TxB_SC_NA9289_ST5112_35SP7P10_20170228.zip
• TxB_SC_NA9289_ST5114_35SP7P10_20170228.zip

iX TxB-SC, NA-9286, ST-5101, ST-5111, ST-5112, ST-5114, Program example

In zip file you find:
- Codesys project (x.projectarchive)
- Picture from codesys (jpg)
- Print file (pdf) at PLC-code

Crevis FnIO S-Series, Manuals

​

• TxB_SC_NA9286_ST5111_35SP7P10_20170228.zip
• TxB_SC_NA9286_ST5112_35SP7P10_20170228.zip
• TxB_SC_NA9286_ST5114_35SP7P10_20170228.zip

Program example CODESYS, Modbus TCP Master (TxB-SC ) and Memory Register Map in ST-5111

More information in pdf and example

• FnIO_HSC_UserManual_REV106.pdf
• na-9289_txb_st5111.CIO
• SET_MemoryRegisterMap_ST5111_TxB-SC_to_NA9289.pdf
• T7B-SC_NA9289_Set_MemoryRegisterMap_ST5111_35sp8.projectarchive

NA-9286, Change parameter for I/O module (Codesys)

Example: change Pt100 to Pt1000 in ST-3702

Result!

NOTE!
- Write value to all parameter byte for the I/O module!

The Parameters for the I/O module can be found in the manual "FnIO_Configuration_Parameter_Memory_Register_rev107_BE"

• T7B_SC_NA9286_ST3702_Param.projectarchive
• T7B_SC_NA9286_ST4424_Param_35SP6.projectarchive

Quick start guide, Upgrade instructions TxB Softmotion to BoX2 pro motion, SUEN00413

• Upgrade instructions TxB Softmotion to BoX2 pro motion - SUEN00413.pdf

CAB111 Cable Drawing for X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B operator panel

​CAB111/3M Straight RS232 cable to CREVIS I/O node for X2 control iX Panel TxA/B SoftControl

Length: 3m

• CAB111 3m.PDF

CAB105 Cable Drawing for X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C operator panel

Cable between Allen Bradley Micrologix and X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C

Cable length: 3 meters.

• CAB105_3m.pdf

CAB106 Cable Drawing for X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C operator panel

Cable between OMRON Host Link and X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C

Cable length: 3 meters.

• CAB106_3m.pdf

CAB107, 25-pol to 9-pol adapter, Cable Drawing for X2 base, X2 pro, X2 marine, X2 control, iX Panel TxA/B/C operator panel

CAB107  9pin Dsub to 25pin Dsub, for using EXTER/E1000 422/485 cables on X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C

Cable length: 0,2 meters.

• CAB107.pdf

CAB109 Cable Drawing for X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C iX operator panel

CAB109 Y-split cable to utilize more than two COM ports on X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C

Cable length: 2 x 0,1 meters.

• CAB109.pdf

iX Panel T7A Outline Drawing/Panel Cut-Out

• EZHMI-Z1141-001B.dwg
• EZHMI-Z1141-001B.dxf
• EZHMI-Z1141-001B.pdf
• T7A_Cutout.pdf
• T7A_outline.eps
• T7A_outline.pdf

iX Panel T7A 3D Drawing

• iX_Panel_T7A-col.stp

iX Panel T4A Outline Drawing/Panel Cut-Out

• T4A_Cutout.pdf
• T4A_outline.eps
• T4A_outline.pdf

iX Panel T4A 3D Drawing

• iX_Panel_T4A-col.stp

iX Panel T10A Outline Drawing/Panel Cut-Out

• T10A_Cutout.pdf
• T10A_outline.eps
• T10A_outline.pdf

iX Panel T10A 3D Drawing

• iX_Panel_T10A-col.stp

CAB104 Cable Drawing forX2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C operator panel

Cable between PC standard RS232 and X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C 

Cable length: 3 meters.

• CAB104_3m.pdf

CAB103 Cable Drawing for X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C

 Cable between MELSEC FX1/2/3-series and X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C

Cable length: 3 meters in drawing CAB103_3m.pdf.

Cable length: 10 meters in drawing CAB103_10m.pdf.

Cable length: 15 meters in drawing CAB103_15.pdf.

• CAB103_10m.pdf
• CAB103_15m.pdf
• CAB103_3m.pdf

CAB102 Cable Drawing for TxA / TxB / TxC iX operator panel

CAB102 cable drawing for T4A / T7A / T10A

TxB / TxC MPI Direct are not supported.

Cable length: 3 meters.

Can be used with following systems:

SIMATIC 300/400 MPI Direct Driver

SIMATIC 200 PPI Driver

SIMATIC 1200 N/A only ethernet use ISO-on-TCP driver. 

• CAB102_3m.pdf

CAB101 Cable Drawing for X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C operator panel

CAB101 Cable between MELSEC Q and  X2 base, X2 pro, X2 marine, X2 control, X2 motion, iX Panel TxA/B/C

Cable length: 3 meters.

• CAB101_3m.pdf

Beijer Electronics - Device Runtime and Compiler versions in CODESYS

Attached documents describes following;

• What versions of project compiler and runtime you should use when programming our codesys related products.

- TxA SoftControl
- TxB SoftControl
- TxB SoftMotion
- "PIO" Programmable I/O
- X2 Control

• What versions of communication drivers you should use in Codesys when communicating out from our Codesys related products, based on what CODESYS runtime currently installed in the device.

- Serial Modbus RTU
- Ethernet Modbus TCP
- EtherCAT

• Codesys communication driver versions_20181129.pdf
• Codesys Runtime and compiler versions_20181129.pdf

Number of ARTI connections to one TxA-SC, TxB-SC/SM

TxA-SC, Max 3 Cyclic Task

Max. number of Cyclic task is limited to 3 according to the Device description of iX TxA-SoftControl.

Note, the amount of task can only be increased by changing the device file and this may affect the performance of the panel. 

Instead we propose to use the program to control the various program components.
- The following illustration shows how a POU can be used as "Task" and call other POU (PRG)

A possible extension of the number of "task" to the device file will be discussed at the next update of TxA-SC.

• CallPrograms.projectarchive

CODESYS - Declare persistent variables in GVL

Question:
Is it possible to declare persistent variables in GVL?

Answer:
Yes, for Beijer Electronics devices, normally by using PersistentVars and making a "double declaration".
Please ensure that this works on your device since behaviour might be different on hardware and runtime.
Note: This adds and extra step manual step in the process but can be very convenient in some circumstances.

1. Change Flags on the GVL variables you want to be treated as Persistent or Retain accordingly, e.g. Persistent include flags Retain and Persistent:

2. Add PersistentVars GVL and Build your project.
3. Right click inside of PersisentVars and select "Add all instance paths":

iX TxA/TxB SoftControl, How to set up ARTI controller in iX Developer to communicate with TxA/B SoftControl.

This removes the need to download iX Developer project to panel and instead use PC to simulate panel (faster testing).
The ARTI driver uses the Codesys Gateway on PC to connect to panel.

• Connecting ARTI in iX Runtime with iX SoftControl panel.pdf

TxA-SC - Modbus RTU/TCP slave error handling

How can I check if my Modbus slave in iX TxA SoftControl is running or not?

ANSWER
After configurating the communication to the slave(s) like we recommend, you use these variables in the PLC program:
<ModbusSlaveDeviceName>.xError ; to check if is there is a communication error.
<ModbusSlaveDeviceName>.xReset ; to reset the error and start communication again.
<ModbusSlaveDeviceName>.byModbusError ; gives you information about the error.
In the Modbus library (found in the Library Manager) is also a Struct called "MB_ErrorCodes" which gives you the information about the errors.

For advanced users:
Via the menu " Tools=> Options =>Feature sets ", you can specify that you don't want to hide System Libraries.

CoDeSys - TxA-SC, Trigger to start communication with a slave, Modbus RTU

The communication to a modbus slave starts from the plc-project.
Communication to the slave are ON as long as the "trigger" is ON.

Select Trigger in Modbus slave.

Programming the function

Connect the "Trigger" to I/O Mapping

I / O can be used as a trigger signal

From help in CoDeSys:

Configuration of the Modbus slave

• Perf_T7A_SC_NA9173_Nod5_5_trigger.projectarchive

CoDeSys - TxA-SC timeout example (Modbus RTU)

1 pcs T7A-SoftControl
1 pcs Crevis NA-9473
3 pcs BFI-H2 (HVAC)

Disconnecting one of the BFI inverters will generate a timeout in the network, depending of the Response Timeout setting (ms).

"Response Timeout" needs to be adjusted when more than one slave is connected! Because when there is a communication failure with one of the slaves, the communication will stop 1000 ms (default value) to this slave. According to response timeout setting the CoDeSys Modbus RTU driver will communicate with the other slaves and try to connect to the faulty slave again. If there still are problem it will take another 1000 ms before the master communication with the other slaves.
 

Solution:
- Change Response Timeout to a lower value, for example 100 or 50 ms on each node.

CoDeSys - TxA-SC, Modbus Com status

Example showing Modbus diagnostics to Crevis I/O nodes using Function Block FB_ModbusStatus in CFC editor:

• Modbus Slave Status.projectarchive

CoDeSys - TxA-SC and NA-9173 / NA-9473, Timeout when more then 1 slave

"Response Timeout" needs to be adjusted when more than one slave is connected!

When there is a communication failure with one of the slaves, the communication stop 1000 ms (default value) to this slave.
After the timeout the CoDeSys communicates with the other slaves and then try to connect to the "error" slave again.
If there still are problem it´s take 1000 ms before the will communication with the other slaves.

Solution:
- Change Response Timeout to 20 ms* for each slave. (*Example for application with Baud Rate 115 200).
Which means that there will only be a communication stopped at 20 ms.

Codesys - iX TxA-SC, TxB-SC - Used Persistent Memory

Used size can be read after rebuild of project.

Used persistent data is displayed.
In this example, there is free space at 15358 (93%) of the total area 16360 bytes. 

Example from T7A-SoftControl   

Codesys - Improvements in 3.5 SP2

Some of the good improvements you will get after upgrade from 3.5 SP1 to SP2:

• Important, the crash message "Unhandled exception has occurred..." are corrected.

• More easy to close each tab with the cross mark inside the tab instead of outside to the right of the pane of CoDeSys editor.

• Improved information when using Instancename of Function Blocks in ST-editor.

• Compiling errors are now shown more graphical directly in the statusbar (before it was discovered at download).

CODESYS - How to backup variable values (Recipe Manager)

Procedure how to make backup of variable values from the Soft PLC (CoDeSys) to a file in a computer.

Attached example show the iX TxA-SoftControl device (Recipe_Backup.zip including):
 - RecepieManagerExample.projectarchive  (CoDeSys project of T4A SoftControl)
 - ValueBackup1.txtrecipe  (Example of backup text file)
 - iX_T4A_SC_RecValues  (iX Developer project of T4A SoftControl)

We have some global variables declared in the GVL list of a CoDeSys project:

And some values are set in the soft PLC (T4A SoftControl):

Add an object "Recipe Manager" to the CoDeSys application:

Storage Type, File Extension and Selected Columns can be defined for the recipe file:

Add Recipe Definition:

Add a new recipe column:

Select a name for the first Recipe column (ValuesBkp1):

The column "ValuesBkp1" are created:

Import the global varialbes into the Recipe:

The variables of the GVL was included in the Recipe list, and when Login to the PLC we can monitor the Current Values:

Now read values from PLC to Recipe:

Values are read to the Recipe tool of CoDeSys:

Save values to file:

By using the function "Load and Write Recipe" the backup can be restored to the TxA SoftControl device.

The values in the file ValueBackup1.txtrecipe, can be edited with a normal text editor:

Note!
Some important steps that need to be done according KI00326, see related link for details.

Export Variables to iX HMI
In Codesys we have to make a “XML” file for import to iX Developer. In order to be able to export application variables from CoDeSys to iX HMI a “Symbol configuration” is needed. The XML file for iX Developer is created when you transfer the project to the TxA SoftControl or “Generate code” in menu “Build”. The file is saved in same library as the “CoDesys” project.
 - Highlight the “Application” entry in “Devices”
 - Right click and select “Add Object”
 - Choose “Symbol configuration”
 - Enter chosen name in the “Name” option and click “Open”

Transfer CoDeSys project to TxA SoftControl
A gateway needs to be created in order to communicate between the PC and the HMI.
 - Double click the “TxA SoftControl” option under “Devices”
 - Select the “Communication setting” options
 - If no gateway present, create one by selecting “Add Gateway” (choose default value)
 - Highlight the gateway 
 - Press “Scan network” and wait until scanning is done
 - All CoDeSys devices on the network will be listed below the gateway

Import of variables into iX Developer project
 - Setup an iX application (TxA SoftControl)
 - At this stage, it is time to import the variables that were exported from CoDeSys
 - In “Functions”, double click the “Tags” option
 - In the window, choose the “Import tags to” option
 - Select the “CoDeSys V3 import format” (Import Modules) and browse to the location where the CoDeSys project is saved
 - Choose the xml file with the same name as the CoDeSys project and press “Open”. Mark “Connect selected import file to project”.
 - Select “Import”
 - Select “All items” and press OK
 - Press “OK” in the “Import Completed” dialog

• Codesys_How ToBackupVariableValues_RecipeManager.pdf
• Recipe_Backup.zip

CoDeSys - Modbus RTU time setting, Bus Task and Application Task

Background
The purpose of this document is to give some pointers on how the different time settings in the CoDeSys Modbus tree should be set to achieve accurate and data consistent Modbus communication. This document only covers the serial Modbus communication.
Inputs to this documents are the CoDeSys Online Help, questions to 3S developers and support as well as internal discussions between Beijer employees.
Modbus time settings
In the CoDeSys serial Modbus configuration, the different timing settings are as follows:

Additionally, there are a few time settings on the “Task” level which are relevant for this issue:

• Bus task cycle time

• Application task cycle time

More info in "CoDeSys_ModbusRTU_BusTask.pdf"

• CoDeSys_ModbusRTU_BusTask.pdf

IX softcontrol \ softmotion project loading trough USB \ SD memory

22.10.2013
Information found here is exctracted from KI00326 \ KI00353

It is possible to load both IX project and codesys project via USB \ SD memory.

Export project from CODESYS programming tool:
In the menu “Online” select “Create boot application” and save the project files (.app/.crc) in the root of the USB memory

Copy CODESYS project from USB to iX TxB SoftControl \ SoftMotion:
- Restart the iX TxB SoftMotion panel with USB memory
- You will be asked if you wish to load the CODESYS project “Copy PLC project from USB memory?”

Important note!
- When download a CODESYS project the SoftControl \ SoftMotion memory will be cleared! Also the “Persistent” area (the battery powered memory cells and register)
- Tip! It’s also possible to download the iX Developer project in same way, on the same USB memory!

Use the Export funktion in the project ribbon to eksport the project, either directly to the rootlevel of an USB, or to a folder to e.g. send trough email.

- When rebooting the terminal with the IX project on the USB \ SD memory, the user will be promted to create a backup of existing project (if exist), then one are asked if one wish to load the project on the memory unit.

- After the Codesys project are downloaded and the terminal are rebooted the "PLC" go to RUN.

iX SoftControl/SoftMotion - Error message Read Timeout and Add Timeout

Using Direct Access driver in iX HMI can sometimes give Error message "[Controller name]Read: Timeout" and "Add: timeout" when running the application.

1. Reason could be tag missmatch between iX Tag list and Codesys Symbol Configuration.
Make sure that the Symbol Configuration in Codesys have been downloaded to the PLC.
Import the symbol configuration *.xml file again and delete unused tags see picture how to setup the import.

It's important to note that even if a tag isn't used in the iX project (i.e screens, alarms etc), it can't be addressed to a Codesys variable that doesn't exist in the Symbol Configuration.

2. Another possibility is that the access rights in the Codesys Symbol configuration has been changed, this will also give error and can be hard to notice (Direct Acces driver version 4.02.01) :

iX - Transparent Mode Qnn serial through an iX panel with Serial/IP

The following settings worked when I tested Serial/IP->iX Panel T7A -> Mitsubishi Q03 CPU (serial).

iX driver setup:

Serial/IP was set up as follows:

Knowledge: CODESYS 3.5 SP2 and released version of iX TxA SoftControl

Note, the device description of TxA-SoftControl defines that specific libraries of CoDeSys SP1 Patch4 are used, for example IoStandard 3.5.1.0, see screenshot from TxA-SoftControl_V3_5_1_40.devdesc.xml.

If the PC never had this version installed, for example that you only installed CoDeSys 3.5 SP2, you will get many errors duing compilation in a new project using device TxA-SoftControl... "Fail to insert library IoStandard, 3.5.1.0 (System)" and error codes like C0077 , C0032 , C0229 , C0046 and C0018.

Solution
The most easy way to get all libraries from 3.5 SP1 (3.5.1.0) is to install this old version to the computer as well. After this is done the CoDeSys 3.5 SP1 Patch4 version can be uninstalled again and the libraries will still be present in the Library repository.

TxA-SoftControl

iX - How to enter the Service Menu to set a new IP address, calibrate touch etc

Please see the attached document.

• TxA Service Menu.pdf

CoDeSys and iX TxA SoftControl - Modbus status signals

Example of some interesting status of the Modbus slaves ...

Modbus status of slaves that can be used for status display

 xAllSlavesOk = Indicates whether all slaves communicating

xError = Shows the error on that particular slave
byModbusError = Displays the error code (161 is a communication error with slave)

xReset = Can be used to remove the fault indication

Explanation of error codes can be found at the following location (see picture):

How to check what battery type your TxA is equipeed with

Part number that ends with 01 is equipped with a rechargeable battery.

Part number that ends with 02 is equipped with a non rechargeable battery.

EtherCAT installation guideline (cables, wiring, earth etc.)

EtherCAT Installation Guideline

The ETG.1600 EtherCAT Installation Guideline describes the main aspects which should be considered when implementing an EtherCAT network infrastructure in order to optimize the communication performances.

It consists of four main chapters:

• Chapter "EtherCAT Basics" describes few theoretical aspects of the EtherCAT technology which could be relevant for a proper dimensioning of the network infrastructure.
• Chapter "Planning" is intended to support engineers which plan an industrial communication network based on the EtherCAT technology, with specific reference to international standards. 
• Chapter "Assembling" wants to support technicians which realize the EtherCAT communication network based on a previous plan. 
• Chapter "Commissioning" is intended to support technicians, as well as end users, which check the correctness of an installation, or monitor the operation of an industrial communication network based on the EtherCAT technology.

Link to the document ETG.1600 EtherCAT Installation Guide below:
https://www.ethercat.org/en/downloads/downloads_0BB3377CCA0740E7A7EE2405D71FA308.htm

NA-9286, NA-9289, Change parameter in I/O moduls with IO Guide Pro

The configuration software “IO Guide Pro” can be used to change I/O-moduls parameter.
Modbus RTU (serial, RS-232) is used to connect the computer to the EtherCAT node (NA-9186).

• Config_IO_ModbusRS232_20150608.pdf
• NA_9186_Config_IO_20130920.pdf
• Test_NA9186_ParameterChangeST3702.CIO

TxB Softcontrol - Check communication status against ModbusTCP (NA-9289)

Simple Codesys-logic to check that ModbusTCP communication is running OK towards I/O node.

Tested with T7B SC (3.5.7.10) and NA-9289 (FW 1.008).

• TxB_NA9289_ComStat.projectarchive

Restart of Codesys EtherCAT slave using code

Sometimes Codesys fails to get slaves up and running again after a hot connect or they've been powered down.

A typical example of this is the Beckhoff special slice modules, digital modules work fine but most special modules (analogue, high speed counter etc.) will become stuck in PreOperational mode.

The code below shows how slaves can be handled manually to auto-repair such a situation and become operational again.
In the example we have two Beckhoff slaves named EL5101 and EL4032 (typically slices within an EK1100 node).

PROGRAM prgAutoRestartSlaves
VAR
 aiRestart: ARRAY[1..2] OF 
INT;
 atmrRestart: ARRAY[1..2] OF TON;
 iSlaveIndex: 
INT;
 pSlave: POINTER TO ETCSlave;
END_VAR

FOR iSlaveIndex:=1 TO 2 DO
 //Define here which slaves are to be 
monitored and auto-restarted
 CASE iSlaveIndex OF
  1: 
pSlave:=ADR(EL5101);
  2: pSlave:=ADR(EL4032);
 END_CASE
 //Get updated slave status
 pSlave^();
 IF pSlave^.wState=ETC_SLAVE_STATE.ETC_SLAVE_OPERATIONAL THEN
  //Slave is operational, reset timer and restart sequence
  aiRestart[iSlaveIndex]:=0;
  atmrRestart[iSlaveIndex](IN:=FALSE);
 ELSE
  //Slave has trouble
  IF aiRestart[iSlaveIndex] = 
0 THEN
   //Restart sequence not busy, wait until there has 
been trouble for x s
   atmrRestart[iSlaveIndex](IN:=TRUE, 
PT:=T#10S);
   IF atmrRestart[iSlaveIndex].Q THEN
    //x s elapsed, reset timer and start the sequence
    atmrRestart[iSlaveIndex](IN:=FALSE);
    aiRestart[iSlaveIndex]:=10;
   END_IF
  ELSE
   //Restart sequence busy, timeout after x s
   atmrRestart[iSlaveIndex](IN:=TRUE, PT:=T#10S);
   IF atmrRestart[iSlaveIndex].Q THEN
    //Restart failed, start over and wait for trouble 
again
    atmrRestart[iSlaveIndex](IN:=FALSE);
    aiRestart[iSlaveIndex]:=0;
   END_IF
  END_IF
 END_IF
 //Restart sequence
 CASE aiRestart[iSlaveIndex] OF
  10: //Command INIT
   pSlave^.SetOpMode(ETC_SLAVE_STATE.ETC_SLAVE_INIT);
   aiRestart[iSlaveIndex]:=20;
  20: //Command 
PREOP as soon as we reach INIT
   IF 
pSlave^.wState=ETC_SLAVE_STATE.ETC_SLAVE_INIT THEN
    pSlave^.SetOpMode(ETC_SLAVE_STATE.ETC_SLAVE_PREOPERATI
ONAL);
    aiRestart[iSlaveIndex]:=30;
   END_IF
  30: //Command SAVEOP as soon as we 
reach PREOP
   IF 
pSlave^.wState=ETC_SLAVE_STATE.ETC_SLAVE_PREOPERATIONAL THEN
    pSlave^.SetOpMode(ETC_SLAVE_STATE.ETC_SLAVE_SAVEOPERAT
IONAL);
    aiRestart[iSlaveIndex]:=40;
   END_IF
  40: //Command OP as soon as we 
reach SAVEOP
   IF 
pSlave^.wState=ETC_SLAVE_STATE.ETC_SLAVE_SAVEOPERATIONAL THEN
    pSlave^.SetOpMode(ETC_SLAVE_STATE.ETC_SLAVE_OPERATIONA
L);
    aiRestart[iSlaveIndex]:=99;
   END_IF
 END_CASE
END_FOR   

IP setting on NA-9289

If BOOTP is used to set the IP of the NA-9289 do that on a LAN without a DHCP-server, DIP-switch 9 on the NA-9289 is for both BOOTP and DHCP.
After setting the IP via BOOTP set the DIP-switch to OFF or otherwise the NA-9289 will get a new IP from a DHCP-server if it´s later connected to a network like that.

NOTE!
Depends on value in register 0x1045

Using Crevis ST5111 high speed counter as source to a Codesys FreeEncoder object

• Crevis_ST5111_FreeEncoder.projectarchive

Upgrading an existing SoftMotion project from v3.5.3.30 to v3.5.7.10 (TxB build 198)

Beijer Electronics always recommend using the latest startup project and copy your own code into this.
In some cases, the customer insists on keeping their existing Codesys project and simply wants to upgrade it to be compatible with v3.5.7.10.

If so, the following steps are needed in order to reach compatibility:

1.   Use Codesys Developer v3.5.7.10 or later.

2.   Download and open the latest startup project (currently v3.10) to ensure you have the correct versions of needed libraries. After opening the project, restart Codesys to ensure device/library repository is updated.

3.   Open the project to be upgraded.

4.   Update the TxB SoftMotion device to 3.5.7.10

5.   Change project compiler settings to 3.5.7.10. Please note that persistance storage need to be rebuilt so if you use Persistent Variables make sure you have a fresh backup of these values.

6.   Update the EtherCAT_Master and make sure to select EtherCAT Master SoftMotion 3.5.7.30 (it's not a typo, very important to use this version, contains bug fixes an is fully compatible with the runtime in build 198)

7.   Update all servo axis to SM_Drive_ETC_GenericDSP402 3.5.7.0

8.   Update all devices in SoftMotion General Axis Pool (virtual axis and free encoders) to 3.5.5.0 (there are no later versions).

9.   Open the library manager and update the Standard library (using right click, Properties) to v3.5.7.0.

10. Finally, open the POU prgGeneralEtherCATHandling (or similar) and remove the line that sets FrameAtTaskStart to TRUE as the driver handles this internally and it's no longer allowed to change it via code.

In case of problems, please don't hesitate to contact the Beijer Electronics support.

DNV Certificate iX T7AM +CiX-CAN

DNV Certificate iX T7AM, +CiX-CAN

Apply to:
630002502 iX T7AM
630003112 iX T7AM-CAN

• DNV Certificate-13497.pdf

iX TxA-SC DoC DNV (PROD CERT - 1033774 - 1 - A1) - 1

• iX TxA-SC DoC DNV (PROD CERT - 1033774 - 1 - A1) - 1.pdf

Declaration of conformity iX Panel TxA

• Declaration of conformity iX Panel TxA PIEN292.pdf

iX Panel T7A Declaration of Conformity EMC

• EG_Confirmation_iX_Panel_T7A.pdf

iX Panel T4A Declaration of Conformity EMC

• EG_Confirmation_iX_Panel_T4A.pdf

iX Panel T10A Declaration of Conformity EMC

• EG_Confirmation_iX_Panel_T10A.pdf

iX TxA SoftControl, Device Description

Current version 3.5.1.40

• TxA-SoftControl_V3_5_1_40.devdesc.zip

TxA-SC - Install Device description file in CoDeSys

Example :
 - Choose this menu: Tools > Device Repository > Install
 - Select the latest Device description file, TxA-SoftControl_V3_5_X_X.devdesc.xml

Now the TxA SoftControl can be selected from the Add Device dialog:

• TxA-SoftControl_V3_5_1_40.devdesc.zip

iX TxA-SC Image 1.11

iX TxA-SC
Image Release 1.11, Build 1238

Image file
Release notes
Last minutes notes

• IML_TxA_b1238.exe
• Last_Minutes_Notes_iX_TxA_SoftControl_PIEN296C.pdf
• Release_Notes_iX_TxA_SoftControl_PIEN295C.pdf

TxB-SC/ SM image 1.3 b202

​New image for TxB-SoftControl, TxB-SoftMotion version 1.3 b202

• IML_TxB_build202.zip
• TxB SoftControl_Motion LastMinutesNotes PIEN309C.pdf
• TxB SoftControl_Motion ReleaseNotes PIEN310C.pdf

iX T7A Installation manuals

Installations manuals for operator panel iX T7A with preinstalled iX Runtime software.

Installation manuals exist in following language:
Chinese simplified
Chinese traditional
English
French
German
Italian
Portuguese
Spanish

Fold up exist in English language

• iX_T7A_MABP016F.pdf
• iX_T7A_MACN016F.pdf
• iX_T7A_MADE016F.pdf
• iX_T7A_MAEN016F.pdf
• iX_T7A_MAEN016F_Foldup.pdf
• iX_T7A_MAES016F.pdf
• iX_T7A_MAFR016F.pdf
• iX_T7A_MAIT016F.pdf
• iX_T7A_MATW016F.pdf

iX T10A Installation manuals

Installations manuals for operator panel iX T10A with preinstalled iX Runtime software.

Installation manuals exist in following language:
Chinese simplified
Chinese traditional
English
French
German
Italian
Portuguese
Spanish

Fold up exist in English language

• iX_T10A_MABP017F.pdf
• iX_T10A_MACN017F.pdf
• iX_T10A_MADE017F.pdf
• iX_T10A_MAEN017F.pdf
• iX_T10A_MAEN017F_Foldup.pdf
• iX_T10A_MAES017F.pdf
• iX_T10A_MAFR017F.pdf
• iX_T10A_MAIT017F.pdf
• iX_T10A_MATW017F.pdf

iX T4A Installation manuals

Installations manuals for operator panel iX T4A with preinstalled iX Runtime software.

Installation manuals exist in following language:
Chinese simplified
Chinese traditional
English
French
German
Italian
Portuguese
Spanish

Fold up exist in English language

• iX_T4A_MABP015F.pdf
• iX_T4A_MACN015F.pdf
• iX_T4A_MADE015F.pdf
• iX_T4A_MAEN015F.pdf
• iX_T4A_MAEN015F_Foldup.pdf
• iX_T4A_MAES015F.pdf
• iX_T4A_MAFR015F.pdf
• iX_T4A_MAIT015F.pdf
• iX_T4A_MATW015F.pdf

iX T7B Installation manuals

Installations manuals for operator panel iX T7B with preinstalled iX Runtime software.

Installation manuals exist in following language:
Chinese simplified
Chinese traditional
English
French
German
Italian
Portuguese
Spanish

Fold up exist in English language.

• iX_T7B_MABP095C.pdf
• iX_T7B_MACN095C.pdf
• iX_T7B_MADE095C.pdf
• iX_T7B_MAEN095C.pdf
• iX_T7B_MAEN095C_Foldup.pdf
• iX_T7B_MAES095C.pdf
• iX_T7B_MAFR095C.pdf
• iX_T7B_MAIT095C.pdf
• iX_T7B_MATW095C.pdf

iX T15B Installation manuals

Installations manuals for operator panel iX T15B with preinstalled iX Runtime software.

Installation manuals exist in following language:
Chinese simplified
Chinese traditional
English
French
German
Italian
Portuguese
Spanish

Fold up exist in English language.

• iX_T15B_MABP097C.pdf
• iX_T15B_MACN097C.pdf
• iX_T15B_MADE097C.pdf
• iX_T15B_MAEN097C.pdf
• iX_T15B_MAEN097C_Foldup.pdf
• iX_T15B_MAES097C.pdf
• iX_T15B_MAFR097C.pdf
• iX_T15B_MAIT097C.pdf
• iX_T15B_MATW097C.pdf

iX T12B Installation manuals

• iX_T12B_MABP096C.pdf
• iX_T12B_MACN096C.pdf
• iX_T12B_MADE096C.pdf
• iX_T12B_MAEN096C.pdf
• iX_T12B_MAEN096C_Foldup.pdf
• iX_T12B_MAES096C.pdf
• iX_T12B_MAFR096C.pdf
• iX_T12B_MAIT096C.pdf
• iX_T12B_MATW096C.pdf

BSD-L7NH and iX SoftControl Startup Manual KI00381

• BSD and iX SoftControl Startup Manual KI00381.pdf

BSD-L7NH and iX SoftMotion Startup Manual KI00374D

• BSD and iX SoftMotion Startup Manual KI00374D.pdf

CoDeSys V3.5 SP1 Patch 4 (required for TxA-/TxB-SoftControl)

Note! This is the officially tested CODESYS version by Beijer Electronics, it's required for TxA-SoftContol and TxB-SoftControl.

• Features and Changes_Addressed Defects CODESYS v35 SP1 Patch 4.xls
• ReleaseInformation V3.5 SP1 Patch 4.pdf
• Setup_CoDeSysV35SP1Patch4.exe

CODESYS 3.5 SP3 Patch 3 (required for TxB-SoftMotion)

Note! This is the officially tested CODESYS version by Beijer Electronics, it's required for TxB-SoftMotion.

Setup_CODESYSV35SP3Patch3.exe
EXE: Full self-extracting setup - including CODESYS HMI, CODESYS Soft Motion Win V3, CODESYS Control Win V3, CODESYS Gateway, CODESYS OPC Server, CODESYS Licensing Manager

• Features and Changes_Addressed Defects CODESYS v35 SP3 Patch 3.xls
• ReleaseInformation V3.5 SP3 Patch 3.pdf
• Setup_CODESYSV35SP3Patch3.exe

Remote Access Viewer v1.5.4, for Exter/E1000 - TxA/TxB/TAxx - X2 panels

Remote Access Viewer is a program for remote access and control Exter/E1000 - TxA/TxB/TAxx - X2 panels.

It is possible to access, reflect and control panels from a PC by using the VNC client program, Remote Access Viewer (freeware), together with the built-in VNC server (Remote Access function) in the iX Panels.

NB: Even though the help file suggests another key combination, please note that Ctrl-Alt-Shift-F toggles Full screen mode on / off best, so you Restore from Fullscreen mode with this key combination! vncviewer.exe_patch.zip contains a patched vncviewer.exe

• MA00756.pdf
• RemoteAccessViewerSetup 1.5.4_iX.exe
• vncviewer.exe_patch.zip

TxB SoftControl LastMinutesNotes

• TxB SoftControl LastMinutesNotes PIEN307A.pdf

TxB SoftControl ReleaseNotes

• TxB SoftControl ReleaseNotes PIEN308A.pdf

iX - TxB SoftControl - Solution to the problem with Persistent Variables - EN

Document explaning how to download new system image and how to backup existing Codesys project. Regarding the solution for Persistent Variables for TxB SoftControl.

• TxB SoftControl - Solution to the problem with Persistent Variables_1A_EN.pdf