From RTE 34.24.9.
ASCII-type file containing the configuration of axioline modules connected via Ethernet (Modbus/TCP) through the AXL_F_BK_ETH module. Remote axioline modules should not be included in the hardware configuration.
The file must be in the alias folder MODBUS_DIR.
Currently, the following RTE entity types can be associated with the device process data of each individual device connected to the coupler:
•Input/output word (16 bits)
•Internal management (safety modules)
NOTE: R registers (32 bits) can no longer be associated since RTE 34.28.3.
Refer to the PhoenixContact manual db_en_axl_f_bk_eth_8515_en_xx to know which holding registers to use.
Communication with the AXL_F_BK_ETH module is already handled with holding registers starting from 0.
Currently, access to the parameterization data of the various modules must be done through modbus client commands. AXIO_ROBJ and AXIO_WOBJ commands/instructions cannot be used.
When communication with the coupler starts, it is checked that the module composition matches the configured one. In case of mismatch, an error is indicated in the report and the check is repeated every 1.5 seconds (by default).
In case of communication failure, management restarts from the coupler configuration check phase.
The SYS_CFG_2.6 bit allows to enable the generation in the report of the failed connection diagnostic only the first time and not at every occurrence (for Modbus Client).
The SYS_CFG_2.23 bit allows the input and output areas of AXL_F_BK_ETH (PCMBC) to no longer be updated when in loading mode. The values of the physical outputs set when the control is in loading mode depend on the configuration of the various devices.
NOTE: Since RTE 34.29.0, PCMBC handling has been changed, improving diagnostics and allowing support for AXL_F_BK_ETH device watchdog.
The file can contain the following commands:
Name |
Parameters |
Description |
|---|---|---|
AXL_F_BK_ETH rid "ipaddr" [-UDP] [-P port] [-COMT timeout] |
•rid: unique identifier. Must be in the range 2000-:-2099 •ipaddr: IP address of the AXL_F_BK_ETH module •UDP: optional. If omitted TCP communication is used, otherwise UDP is used. •P: optional. port is the port number to be used. By default it is 502 for TCP and 7502 for UDP •COMT: optional. timeout is the time in seconds to wait for a response. If omitted, the value of 2.0 seconds is used |
This command opens the connected devices definition block. The block must be closed with the CLOSE_AXL_F_BK_ETH command. There may be more than one definition in the file |
DEVICE "moduleName" "mode" idx |
•moduleName: device name (see list of available modules below) •mode: resource of RTE where to map process data: o"IO" input/output word (16Bits) o"INT" internal use, only for Safety modules •idx: index of RTE entities. Should be set to 0 if INT is specified on "mode" |
This command specifies the axioline modules connected to the coupler (the order of definition represents the physical order of how they are connected) as well as the mode of connection to the RTE entities. Each device needs a certain number of input/output words in order to map all process data (see list of available modules below). The areas of two devices must not overlap |
DIAGNO_REG n [-R c] |
•n: number of the starting R register to be used for diagnostics (see meaning of diagnostic registers below) •R: optional. c number of registers to be used starting with idx inclusive. The maximum accepted value is 8. Default is 1 |
This command specifies the address of the R register and the number of registers used for diagnostics of the axioline bus, the AXL_F_BK_ETH coupler device, and the management of communications made by RTE. The command is valid only in the device definition block |
COMMAND_REG n |
•n: R register index to be used for sending commands to the coupler (see accepted commands below) |
This command allows you to specify an R register that contains the command to be sent to the AXL_F_BK_ETH device. Allowed values are those valid for command register (2006) in the AXL_F_BK_ETH device manual |
AUTO_RESET_WD |
- |
This command is used to enable automatic reset of the error condition "A Net Fail occurred" on the coupler. If it is not entered in the file, the user must do so via command register (see command 0x0020). Before resetting the error, the control will send the current state of the outputs to the coupler, which will update the state only when the reset is complete |
RETRY_TO waitSec |
•waitSec: waiting time in seconds before retrying to communicate with the coupler after a communication alarm |
This command specifies the waiting time, once an error is received, before retrying the connection. The command is valid only in the device definition block. If omitted, the time is 1.5 seconds |
COMM_ALARM_DELAY time |
•time: time in seconds from control startup after which communication alarms are generated |
It is used to delay the output of communication alarms in case there are delays from control switch on to network availability (connection with wifi, delayed switch on of other devices, ...) |
DISABLE_COMM_ALARM |
- |
It is used to disable the generation of communication alarms. It remains the user's responsibility to check the status of communications with the coupler |
COMM_ERR_FORCE_INP_OFF |
- |
It is used to force the input status (INP_W) to 0 in case of Modbus communication errors. If enabled, forcing the inputs to the state of FALSE is active even if communication alarms are not generated |
CLOSE_AXL_F_BK_ETH |
- |
This command closes the definition block, and a series of checks are performed on the correctness of the definitions. An alarm on this line can also mean an error in a previous definition |
T_PCMBC_FREQ frq |
•frq: frequency of the Phoenix Contact Modbus client task manager. Values between 5 and 500Hz are accepted |
Command used to change the frequency of the Phoenix Contact client Modbus task. The update of process data occurs at half of the communication manager frequency. This parameter is global for all configured nodes. By default it is 100Hz NOTE: Must be set after at least one block has been defined. |
ADD_SAFETY "safetyDevice" isle sat rid pos |
•safetyDevice: safety modules accepted: oSSDI8 oSSDO8 oSE_SSDI8 oSE_SSDO4 •isle: number of island safety •sat: number of satellite safety •rid: number of the device they are connected to, must match the one used in the AXL_F_BK_ETH command •pos: module position (1 to 63) relative to the coupler |
See ADD_SAFETY command. The island and satellite numbers refer to the configuration set in the Phoenix safety PLC program for this module. The corresponding abbreviations are: •SSDI8: AXL_F_SSDI8_4_1F •SSDO8: AXL_F_SSDO8_3_1F •IF_SSDI8: AXL_SE_SSDI8_3 •IF_SSDO4: AXL_SE_SSDO4_2 |
NOTE: You can also use these commands in the RTE.CFG file. In this case, any PCMBC.CFG file present in flash is ignored.
Example
; configuration example
AXL_F_BK_ETH 2001 "192.168.0.5" -UDP -COMT 0.1 DEVICE "AXL_SE_AO4_I_4_20" "IO" 501 DEVICE "AXL_SE_AI4_U_0_10" "IO" 551 DEVICE "AXL_SE_SSDI8_3" "INT" 0 DEVICE "AXL_SE_SSDO4_2" "INT" 0
DIAGNO_REG 1000 -R 8 COMMAND_REG 1100
AUTO_RESET_WD RETRY_TO 0.2 COMM_ALARM_DELAY 60 CLOSE_AXL_F_BK_ETH
ADD_SAFETY "SE_SSDI8" 1 1 2001 3 ADD_SAFETY "SE_SSDO4" 1 2 2001 4
NOTE: In case of configuration errors, a diagnostic message is inserted into the report. Using the PCMBC.CFG file, alarm 9220 is also generated and the bit (11) of BAD_CONFIG is set. |
Meaning of the diagnostic registers
The meaning of the registers is:
For more information, see the AXL_F_BX_ETH device manual and the AXL_F_SYS_DIAG manual. |
List of accepted commands register
The accepted commands are:
|
Available modules list
Permitted modules are:
WARNING: The number of input/output words is the maximum between input and output words used by the modules (see chapter "Process data" in the module reference manual), not the sum of the two. NOTE: See the complete list of modules for more details. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
