R45C-2K-MQ

## IO-Link Master for Modbus Converter Device Register Map 

**==> picture [464 x 368] intentionally omitted <==**

Original Instructions p/n: 221399 Rev. E 25-Sep-24 © Banner Engineering Corp. All rights reserved. 

## Contents 

**Chapter 1 Important Information** Supported Function Codes............................................................................................................................................................................ 3 Modbus Configuration ................................................................................................................................................................................... 3 Identification Information ............................................................................................................................................................................... 3 Device Information......................................................................................................................................................................................... 4 **Chapter 2 Multi-Port Support ................................................................................................. 6 Chapter 3 Port Status.............................................................................................................. 7 Chapter 4 Process Data Input ................................................................................................ 9 Chapter 5 Process Data Output ........................................................................................... 10 Chapter 6 ISDU (Index/Subindex) Data** ISDU Request Register Block ......................................................................................................................................................................11 ISDU Response Register Block....................................................................................................................................................................11 ISDU Read/Write in Single Register Write................................................................................................................................................... 12 ISDU Read/Write in Multiple Register Writes .............................................................................................................................................. 13 **Chapter 7 Port Configuration** PortCycleTime Value Calculation ................................................................................................................................................................ 15 **Chapter 8 IO-Link Port/Operating Modes............................................................................ 16 Chapter 9 Replacing an IO-Link Device During Operation (Backup/Restore Mode) ...... 17 Chapter 10 IO-Link Events** IO-Link Event Processing............................................................................................................................................................................ 19 **Chapter 11 Data Storage** Data Storage Content.................................................................................................................................................................................. 20 Reading from Data Storage Content .................................................................................................................................................... 21 Writing from Data Storage Content....................................................................................................................................................... 21 **Chapter 12 Alias Registers** Read-Only Alias Registers........................................................................................................................................................................... 22 Example....................................................................................................................................................................................................... 22 Read-Write Alias Registers.......................................................................................................................................................................... 23 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

Supported Function Codes................................................................................................................................................................................... 3 Modbus Configuration .......................................................................................................................................................................................... 3 Identification Information ...................................................................................................................................................................................... 3 Device Information ............................................................................................................................................................................................... 4 

## Chapter 1 

## Important Information 

The device register map supports the Compact 2-port IO-Link Master for Modbus (R45C-2K-MQ) and the Compact 4-port IOLink Master for Modbus (R90C-4K-MQ). 

## Supported Function Codes 

**==> picture [500 x 331] intentionally omitted <==**

**----- Start of picture text -----**<br>
Function Code Name Max Message Size<br>3 (0x03) Read Holding Register 250 bytes<br>6 (0x06) Write Single Register 2 bytes<br>16 (0x10) Write Multiple Registers 246 bytes<br>23 (0x17) Read and Write Registers 246 bytes<br>Modbus Configuration<br>Modbus configuration is used for changing communications settings on converter.<br>Registers Parameter Access Default<br>Baud Rate:<br>40601 9600 = 0 r/w 19200<br>19200 = 1<br>38400 = 2<br>Parity:<br>40602 None = 0 r/w None<br>Odd = 1<br>Even = 2<br>40603 Address r/w 1<br>40604 Reserved (cannot be read or  None —<br>written)<br>Restore Factory Configuration:<br>40605 No Operation = 0 w/o —<br>Restore Factory Configuration = 1<br>**----- End of picture text -----**<br>


## Identification Information 

**==> picture [500 x 78] intentionally omitted <==**

**----- Start of picture text -----**<br>
Register Parameter Access<br>40001 Vendor ID r/o<br>40002-40003 Master ID r/o<br>40004 Master Type (see IO-Link Specification V1.1.3  r/o<br>table 29 for enumeration)<br>Continued on page 4<br>**----- End of picture text -----**<br>


25-Sep-24 

page 3 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master for Modbus Converter Device Register Map 

Important Information 

**==> picture [500 x 310] intentionally omitted <==**

**----- Start of picture text -----**<br>
Continued from page 3<br>Register Parameter Access<br>Features_1:<br>40005 Bit 0: DeviceParBatch (SMI_ParamWriteBatch) r/o<br>Bit 1: DeviceParBatch (SMI_ParamReadBatch)<br>Bit 2: PortPowerOffOn (SMI_PortPowerOffOn)<br>40006 Number of Supported Channels r/o<br>Port Type [n] [(1)]  (see Table E.2 - MasterIDent from<br>40007-40014 IO-Link Interface Specification V1.1.3 for  r/o<br>enumerations)<br>40015 Total Max Power Supply (in units of 0.1 A) r/o<br>40016-40023 Max Power Supply (in units of 0.1 A) r/o<br>40024 Revision r/o<br>40025-40040 Vendor Name r/o<br>40041-40056 Product Name r/o<br>40057-40088 Vendor URL r/o<br>40089-40120 Manual URL r/o<br>40121-40122 Firmware P/N [(1)] r/o<br>40123 Firmware Version [(1)] r/o<br>40124 Firmware Build Number [(1)] r/o<br>40125-40140 Application Specific Tag r/w<br>40141-40156 Function Tag r/w<br>40157-40172 Location Tag r/w<br>**----- End of picture text -----**<br>


## Device Information 

## R45C-2K-MQ Device Information 

**==> picture [500 x 177] intentionally omitted <==**

**----- Start of picture text -----**<br>
Modbus Register Address Description I/O Range Comments Default Access Notes<br>40606-40615 Banner Name 0..65535 Banner Engineering RO (9 words/18 Characters)<br>40616-40631 Product Name 0..65535 R45C-2K-MQ RO (16 words/32 Characters)<br>40632 Item H 0..65535 810974 split into two  12 RO Banner Item Number<br>16-bit registers<br>40633 Item L 0..65535 24542 RO<br>40634 Serial Number H 0..65535 RO Serial Number is<br>40635 Serial Number 0..65535 RO split into (4) 16-bit registers<br>40636 Serial Number 0..65535 RO<br>40637 Serial Number L 0..65535 RO<br>More Sensors. More<br>40644-40659 User Define Tag 0..65535 User writable space Solutions. RW (16 words/32 Characters)<br>**----- End of picture text -----**<br>


## R90C-4K-MQ Device Information 

**==> picture [500 x 49] intentionally omitted <==**

**----- Start of picture text -----**<br>
Modbus Register Address Description I/O Range Comments Default Access Notes<br>40606-40615 Banner Name 0..65535 Banner Engineering RO (9 words/18 Characters)<br>Continued on page 5<br>**----- End of picture text -----**<br>


(1) Normally available as an input register. Added to holding registers so it can be accessed if input registers are not supported. 

page 4 of 24 

25-Sep-24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master for Modbus Converter Device Register Map 

Important Information 

**==> picture [500 x 168] intentionally omitted <==**

**----- Start of picture text -----**<br>
Continued from page 4<br>Modbus Register Address Description I/O Range Comments Default Access Notes<br>40616-40631 Product Name 0..65535 R90C-4K-MQ RO (16 words/32 Characters)<br>40632 Item H 0..65535 811445 split into two  12 RO Banner Item Number<br>16-bit registers<br>40633 Item L 0..65535 25013 RO<br>40634 Serial Number H 0..65535 RO Serial Number is<br>40635 Serial Number 0..65535 RO split into (4) 16-bit registers<br>40636 Serial Number 0..65535 RO<br>40637 Serial Number L 0..65535 RO<br>More Sensors. More<br>40644-40659 User Define Tag 0..65535 User writable space Solutions. RW (16 words/32 Characters)<br>**----- End of picture text -----**<br>


25-Sep-24 

page 5 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

## Chapter 2 

## Multi-Port Support 

All register maps shown below are specific to port 1. For multi-port adapters, each port is given its own register range within the holding register space. 

**==> picture [500 x 138] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Port<br>41001-41999 Port 1<br>42001-42999 Port 2<br>43001-43999 Port 3<br>44001-44999 Port 4<br>45001-45999 Port 5<br>46001-46999 Port 6<br>47001-47999 Port 7<br>48001-48999 Port 8<br>**----- End of picture text -----**<br>


For a given register, the starting address of the port can be applied to determine the register address for the new port. For example, the calculation below demonstrates how to find the address of the process data output for port 8. 

**==> picture [500 x 47] intentionally omitted <==**

**----- Start of picture text -----**<br>
Equivalent Port 1 Register Port Port Starting Register Offset New Register<br>41051 1 41001 50 41051<br>41051 8 48001 50 48051<br>**----- End of picture text -----**<br>


25-Sep-24 

page 6 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

## Chapter 3 

## Port Status 

Information regarding the connected device is provided by the following holding registers. When a new device is connected, all data attempts to be read from the device. Unsupported commands read as an empty string. 

Register endian swapping is not performed on the string values. The byte order of the data payload matches the byte-order from the device. 

Writing to these registers results in an error. 

**==> picture [500 x 390] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>41501 Port Mode [(1)] r/o<br>PortQualityInfo:<br>41502 r/o<br>Bit0: Process Data In Valid<br>Bit1: Process Data Out Valid<br>41503 IO-Link Revision r/o<br>Com Mode:<br>41504 COM1 = 0 r/o<br>COM2 = 1<br>COM3 = 2<br>41505 Master Cycle Time r/o<br>41506 Process Data Input Size (bytes) r/o<br>41507 Process Data Output Size (bytes) r/o<br>41508 Vendor ID (for pre 1.1 devices) r/o<br>41509-41510 Device ID (for pre 1.1 devices) r/o<br>41511 Min Cycle Time r/o<br>41512-41543 Vendor Name r/o<br>41544-41575 Vendor Text r/o<br>41576-41607 Product Name r/o<br>41608-41639 Product ID r/o<br>41640-41671 Product Text r/o<br>41672-41679 Serial Number r/o<br>41680-41711 Hardware Revision r/o<br>41712-41743 Firmware Revision r/o<br>41744-41759 Application Specific Tag r/o<br>41760-41775 Function Tag r/o<br>41776-41791 Location Tag r/o<br>**----- End of picture text -----**<br>


Continued on page 8 

- (1) Enumerations (from IO-Link Interface Spec V1.1.3, Table E.4): 

   - 0: NO_DEVICE 

   - 1: DEACTIVATED 

   - 2: PORT_DIAG 

   - 3: PREOPERATE 

   - 4: OPERATE 

   - 5: DI_C/Q 

   - 6: DO_C/Q 

25-Sep-24 

page 7 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master for Modbus Converter Device Register Map 

Port Status 

**==> picture [500 x 38] intentionally omitted <==**

**----- Start of picture text -----**<br>
Continued from page 7<br>Registers Parameter Access<br>41792-41823 Profile Characteristic r/o<br>**----- End of picture text -----**<br>


page 8 of 24 

25-Sep-24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

## Chapter 4 

## Process Data Input 

If no device is connected, all registers read as 0. Unused process data bytes also read as 0. 

Data bytes are not register endian swapped. The byte order of the data payload matches the byte-order from the device. Writing to these registers results in an error. 

**==> picture [500 x 171] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>Port Status:<br>Bit0  = Connected? Bit1  = Process Data Valid? Bit2  = Event Pending? Bit3  = Ready for ISDU?<br>Bit4  = Pin4 SIO State Bit5  = Pin2 SIO State<br>Bit6-7 = Pin4 Mode:<br>SDCI Mode = 0<br>41001 SIO Input Mode = 1 r/o<br>SIO Output Mode = 2<br>Bit8-10 = Pin2 Mode:<br>Disabled = 0<br>Input Normal = 1<br>Output = 2<br>Diagnostic Input = 3<br>Inverted Input = 4<br>41002-41017 Data r/o<br>**----- End of picture text -----**<br>


Discrete modes can be added as input process data so that a reset of the master can be detected when discrete output mode is being used. After reset, the master returns to SDCI Mode on Pin4 and Disabled on Pin2. 

25-Sep-24 

page 9 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

## Chapter 5 

## Process Data Output 

Data bytes are not register-endian swapped. The byte order of the data payload matches the byte order written to the device. A read of this parameter returns the most recent process data output written to the adapter. 

The process data out behavior if a sensor is disconnected and reconnected is undefined. 

**==> picture [500 x 103] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>Bit0 = IsValid<br>Bit1 = Pin4 Output State<br>41051 Bit2 = Pin2 Output State r/w<br>If Pin4<br>and Pin2 are not configured in SIO output mode, writes are ignored and reads are returned as 0 .<br>41052-41067 Data r/w<br>**----- End of picture text -----**<br>


25-Sep-24 

page 10 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

ISDU Request Register Block .............................................................................................................................................................................11 ISDU Response Register Block ..........................................................................................................................................................................11 ISDU Read/Write in Single Register Write ......................................................................................................................................................... 12 ISDU Read/Write in Multiple Register Writes ..................................................................................................................................................... 13 

## Chapter 6 ISDU (Index/Subindex) Data 

ISDU data operations are based on a request/response model. First the request is written to the adapter, and then the response is read. The request is non-blocking, so the status register of the response must be polled to determine when the request has been completed. 

Any write to any of the request registers triggers the request. If the write is to be broken up into multiple write operations, a NOP opcode should first be written to prevent the request from being handled until all data has been written to the adaptor. 

The result register contains an indication of whether the requested operation succeeded or failed. In the case of a failure, the error code returned by the device is not available. 

Data bytes are not register endian swapped. The byte order of the data payload matches the byte-order read from/written to the device. 

## ISDU Request Register Block 

For a write, the data length must match the required data length being written to the device. For a read, the length is a don't care; that is, the returned length of the read is not checked by the adapter. 

For a write, the data contains the data to be written to the sensor. For a read, the data is a don't care. 

**==> picture [500 x 125] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>Operation:<br>41301 NOP = 0 r/w<br>Read = 1<br>Write = 2<br>41302 Index r/w<br>41303 Subindex (max = 255) r/w<br>41304 Data Length (max = 238) r/w<br>41305-41423 Data r/w<br>**----- End of picture text -----**<br>


## ISDU Response Register Block 

The Operation, Index, and Subindex match the value from the most recent request. 

For a write, the length matches the length of data written. For a read, the length contains the number of bytes returned from the device. 

For a write, the data contains the data written to the device. For a read, the data contains the data read from the device. 

If a failure has occurred (Status == Failure), then the Data Length is set to 2. Data[0] contains the Error Code while Data[1] contains the Additional Code. An Error Code of 0 represents an internal error within the master module, while other Error Codes are defined in Annex C of the IO-Link Interface Specification. 

|Registers|Parameter|Access|
|---|---|---|
|41101<br>Operation (see Request for opcodes)<br>r/o<br>Continued on page 12|||



25-Sep-24 

page 11 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master for Modbus Converter Device Register Map 

ISDU (Index/Subindex) Data 

**==> picture [500 x 140] intentionally omitted <==**

**----- Start of picture text -----**<br>
Continued from page 11<br>Registers Parameter Access<br>Status:<br>NOP = 0<br>41102 r/o<br>In Progress = 1<br>Success = 2<br>Failure = 3<br>41103 Index r/o<br>41104 Subindex (max = 255) r/o<br>41105 Data Length (max = 238) r/o<br>41106-41224 Data r/o<br>**----- End of picture text -----**<br>


## ISDU Read/Write in Single Register Write 

The flowchart documents how to perform an ISDU read/write operation using a single Write Multiple Registers Modbus command of the ISDU Request register block. 

**==> picture [76 x 379] intentionally omitted <==**

**----- Start of picture text -----**<br>
Start<br>Read Input False<br>Process Data<br>Ready for ISDU<br>Flag?<br>True<br>Write All Request<br>Registers<br>(Opcode = Read or<br>Write)<br>Yes<br>Read Response<br>Status ==<br>InProgress?<br>No<br>End<br>**----- End of picture text -----**<br>


The request is dispatched to the connected device after the request is written. For a read operation, at the end of the sequence, the response data contains the data returned from the device. 

page 12 of 24 

25-Sep-24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master for Modbus Converter Device Register Map 

ISDU (Index/Subindex) Data 

## ISDU Read/Write in Multiple Register Writes 

The flowchart documents how to perform an ISDU read/write operation using multiple Write Multiple Registers or Write Single Register Modbus commands of the ISDU Request register block. 

**==> picture [76 x 504] intentionally omitted <==**

**----- Start of picture text -----**<br>
Start<br>Read Input False<br>Process Data<br>Ready for ISDU<br>Flag?<br>True<br>Write Request<br>Operation Register<br>to NOP<br>Write Other Request<br>Registers<br>Write Request<br>Operation Register<br>to Read or Write<br>Yes<br>Read Response<br>Status ==<br>InProgress?<br>No<br>End<br>**----- End of picture text -----**<br>


The request is not dispatched to the connected device until the opcode is written to read/write. For a read operation, at the end of the sequence, the response data contains the data returned from the device. 

25-Sep-24 

page 13 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

PortCycleTime Value Calculation ....................................................................................................................................................................... 15 

## Chapter 7 Port Configuration 

**==> picture [500 x 333] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>41851 Port Mode [(1)] r/w<br>41852 Validation&Backup [(2)] r/w<br>41853 I/Q behavior [(3)] r/w<br>41854 PortCycleTime (reserved): 0 = As Fast As Possible. r/w<br>See PortCycleTime Value Calculation"PortCycleTime Value Calculation" on page 15 below.<br>41855 Vendor ID r/w<br>41856-41857 Device ID r/w<br>Pin4 Extra Configuration<br>Bit0-1: Output Type:<br>Push-Pull = 0<br>41858 r/w<br>PNP = 1<br>NPN = 2<br>Bit2:<br>If configured as a diagnostic input, then the LED turns red when the input is in the inactive state. This<br>can be used to indicate a failure of the connected device.<br>Normal Input = 0<br>Diagnostic Input = 1<br>Bit3:  (Don't care if not in SIO Input mode.)<br>Non-inverted Input = 0<br>Inverted Input = 1<br>Bit4: [(4)]<br>Input Type 1 = 0<br>Input Type 2 = 1<br>Continued on page 15<br>**----- End of picture text -----**<br>


- (1) Enumerations (from IO-Link Interface Spec V1.1.3, Table E.3): 

   - 0: DEACTIVATED (SM: INACTIVE - Port is deactivated; input and output Process Data are 0; Master shall not perform activities at this port) 

   - 1: IOL_MANUAL (SM: CFGCOM - Target Mode based on user defined configuration including validation of RID, VID, DID) 

   - 2: IOL_AUTOSTART (SM: AUTOCOM - Target Mode w/o configuration and w/o validation of VID/DID; RID gets highest revision the Master is supporting; Validations: NO_CHECK) 

   - 3: DI_C/Q (Pin 4 at M12) (SM: DI - Port in input mode SIO) 

   - 4: DO_C/Q (Pin 4 at M12) (SM: DO - Port in output mode SIO) 

- (2) Enumerations (from IO-Link Interface Spec V1.1.3, Table E.3): 

   - 0: No Device check 

   - 1: Type compatible Device V1.0 

   - 2: Type compatible Device V1.1 

   - 3: Type compatible Device V1.1, Backup + Restore 

   - 4: Type compatible Device V1.1, Restore 

- (3) Enumerations (from IO-Link Interface Spec V1.1.3, Table E.3): 

   - 0: Not supported 

   - 1: Digital Input 

   - 2: Digital Output 

- (4) Type 1 supports IEC 61131-2 Type 1 input voltage levels. Type 2 supports IEC 61131-2 Type 2 and Type 3 input voltage levels. 

25-Sep-24 

page 14 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master for Modbus Converter Device Register Map 

Port Configuration 

**==> picture [500 x 101] intentionally omitted <==**

**----- Start of picture text -----**<br>
Continued from page 14<br>Registers Parameter Access<br>Pin2 Extra Configuration:<br>Normal = 0<br>Diagnostic Input = 1<br>41859 r/w<br>Inverted Input = 2<br>If configured as a diagnostic input, then the LED turns red when the input is in the<br>inactive state. This can be used to indicate a failure of the connected device.<br>**----- End of picture text -----**<br>


If Port Mode is set to IOL_AUTOSTART (default), the master ignores the Vendor ID and Device ID of the connected device. 

If Port Mode is set to IOL_MANUAL, the master will attempt to write the Device ID into the device at connection. If the Vendor ID and Device ID are not supported by the device, the master will not connect. 

This value is non-volatile and is stored to EEPROM and persisted across adapter power cycles. After a write to any register in this block, the port is reset to apply the new configuration settings. 

## PortCycleTime Value Calculation 

Bits 6 to 7: Time Base. These bits specify the time base for PortCycleTime calculation. 

Bits 0 to 5: Multiplier. These bits contain the 6-bit multiplier for PortCycleTime calculation. 

**==> picture [500 x 134] intentionally omitted <==**

**----- Start of picture text -----**<br>
Time Base Multiplier<br>Bit 7 Bit 0<br>Time Base Time Base Value Calculation PortCycleTime<br>00 0.1 ms Multiplier × Time Base 0.4 ms to 6.3 ms<br>01 0.4 ms 6.4 ms + (Multiplier × Time Base) 6.4 ms to 31.6 ms<br>10 1.6 ms 32 ms + (Multiplier × Time Base) 32 ms to 132.8 ms<br>11 Reserved Reserved Reserved<br>**----- End of picture text -----**<br>


NOTE: 0.4 ms is the minimum possible PortCycleTime. 

25-Sep-24 

page 15 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

## Chapter 8 

## IO-Link Port/Operating Modes 

The operating mode can be configured for any port on the IO-Link master. The following modes can be used: 

## Deactivated 

Use deactivated mode for any unused IO-link master ports if a device is not connected. 

## IO-Link Manual 

The IO-Link master only connects IO-Link devices that have a certain vendor ID and device ID (1: IOL_MANUAL). This mode is also required to for the Backup and Restore or Restore function. 

## IO-Link Autostart 

The IO-Link master connects to every connected IO-Link device (2: IOL_AUTOSTART). 

Digital Input 

The IO-Link port functions as a standard digital input (3: DI_C/ Q). 

Digital Output 

The IO-Link port functions as a standard digital output (4: DO_C/Q). 

25-Sep-24 

page 16 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

## Chapter 9 

## Replacing an IO-Link Device During Operation (Backup/Restore Mode) 

Replacing an IO-Link device during operation is common, and inadvertent changes to device settings can cause operational problems and down-times. Operating personnel without special knowledge or tools can replace IO-Link devices quickly and without errors. 

When the backup function of the IO-Link master is used, the IO-Link master automatically provides the saved parameters to the new device after replacement. This makes IO-Link device replacement seamless in IO-Link applications. Another common industry term for this function is data storage mode. 

## . Backup+Restore Mode 

If a port on the IO-Link master is set to Backup+Restore, then the new device added to the IO-Link port takes in the same device configuration as the device that was just replaced, as the IO-Link master had stored the last configuration change by a backup (3: Type compatible Device V1.1, Backup + Restore). 

## . Restore 

If the port on the IO-Link master port is set to Restore, then the new device takes in the configuration according the settings saved in the master at the time of the last backup. Because possible configuration changes were not saved in the master, a different behavior from the previous one before the replacement may occur (4: Type compatible Device V1.1, Restore). 

25-Sep-24 

page 17 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

IO-Link Event Processing................................................................................................................................................................................... 19 

## Chapter 10 IO-Link Events 

If an event is pending, the Event Pending flag is set in the process data input register block. If a user is not concerned with IO-Link events, they can ignore the state of this flag. 

Events are read via the Event status register block: 

**==> picture [500 x 205] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>41901 Count (max = 10) r/o<br>Mode[0]:<br>None = 0<br>41902 r/o<br>SingleShot = 1<br>Disappears = 2<br>Appears = 3<br>Type[0]:<br>None = 0<br>41903 r/o<br>Notification = 1<br>Warning = 2<br>Error = 3<br>41904 Code[0] r/o<br>41905 Mode[1] (Repeats for 10 total supported events) r/o<br>41906 Type[1] (Repeats for 10 total supported events) r/o<br>41907 Code[1] (Repeats for 10 total supported events) r/o<br>**----- End of picture text -----**<br>


Events are stored in a FIFO buffer, where Mode[0] is the oldest event in the queue. If a new event is received when the queue is full, the oldest event in the queue is shifted out. 

After an event has been read, it can be cleared by writing its event code to the Clear Event Register: 

**==> picture [500 x 32] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>41951 Event Code w/o<br>**----- End of picture text -----**<br>


25-Sep-24 

page 18 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Events 

IO-Link Master for Modbus Converter Device Register Map 

## IO-Link Event Processing 

**==> picture [78 x 339] intentionally omitted <==**

**----- Start of picture text -----**<br>
Start<br>Read Process Data<br>Input<br>Event Pending<br>Flag Set?<br>Yes<br>Read Event Status<br>No<br>Write Event Code to<br>Clear Event Register<br>Done<br>**----- End of picture text -----**<br>


25-Sep-24 

page 19 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

Data Storage Content......................................................................................................................................................................................... 20 

## Chapter 11 Data Storage 

The data storage configuration is set as part of the Port Configuration object. The operations can also be triggered manually using the Data Storage Command register: 

**==> picture [500 x 73] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>Data Storage Command:<br>NOP = 0<br>41981 w/o<br>Upload = 1<br>Download = 2<br>Clear = 3<br>**----- End of picture text -----**<br>


The command is executed immediately upon writing the command. 

The status of the requested data storage command can be accessed via the Data Storage Command Status register: 

**==> picture [500 x 73] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>Data Storage Command Status:<br>NOP = 0<br>41991 r/o<br>In Progress = 1<br>Success = 2<br>Failure = 3<br>**----- End of picture text -----**<br>


## Data Storage Content 

The following registers are outside the normal 40000-49999 range of holding registers. They are only available through direct addressing, and not through Modicon. 

**==> picture [500 x 103] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Register Description<br>50000 Port Selection —<br>0 = NOP<br>50001 Operation 1 = Read<br>2 = Write<br>0 = NOP<br>50002 Status [(1)] 1 = In Progress<br>2 = Success<br>3 = Failure<br>**----- End of picture text -----**<br>


Reading/writing the data storage contents does not trigger an upload/download to/from the connected device. To do so, write the desired operation to the appropriate port's Data Storage Command register. 

Registers Parameter 50100-51123 Data Storage Content 

The data storage content is unpopulated (read as 0) prior to performing a data storage read operation. 

While the master supports storing separate data storage contents per port, a single buffer is shared for all ports for communications purposes. To support data storage content over multiple ports, the port must be specified in the Data Storage Request registers prior to reading/writing the contents. 

> (1) Writes to this register are ignored. 

25-Sep-24 

page 20 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master for Modbus Converter Device Register Map 

Data Storage 

Reading from Data Storage Content 

**==> picture [491 x 104] intentionally omitted <==**

**----- Start of picture text -----**<br>
In Progress<br>In Progress<br>Start Command = UploadData StorageWrite Read Data StorageCommand Status Success Port = Port NumberWrite Data StorageOperation = ReadRequest Storage RequestRead DataStatus Storage ContentRead All DataRegisters Done<br>Failure Failure<br>Error<br>Optional: Read current data storage<br>parameter out of device<br>**----- End of picture text -----**<br>


Writing from Data Storage Content 

**==> picture [491 x 129] intentionally omitted <==**

**----- Start of picture text -----**<br>
In Progress<br>In Progress<br>Start Storage ContentWrite all Data Port = Port NumberWrite Data StorageRequest Storage RequestRead Data Data StorageCommand =Write Read Data StorageCommand Status Done<br>Registers Operation = Write Status Download<br>Failure<br>Optional: Write current data storage<br>Failure parameter to device<br>Error<br>**----- End of picture text -----**<br>


25-Sep-24 

page 21 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master For Modbus Converter Device Register Map 

## Chapter Contents 

|Read-Only Alias Registers ................................................................................................................................................................................. 22|
|---|
|Example ............................................................................................................................................................................................................. 22|
|Read-Write Alias Registers ................................................................................................................................................................................ 23|
|Alias Registers<br>Chapter 12|



There are two register sets that are part of the holding registers. 

## Read-Only Alias Registers 

This set is the user-configurable alias configuration registers: 

Registers Parameter Access 40701-40768 Read/Only Alias Register Address r/w 

Each register in this section contains the 16-bit register address for the corresponding alias holding register, which is readable in the alias register space: 

Registers Parameter Access 40501-40568 Read/Only Alias Register r/o 

When reading an alias register, the data in the register is filled with the contents of the address that are present in the corresponding alias configuration register. The address can be stored in either direct or modicon addressing. Note that all aliased registers are read-only, and it is not possible to write to an alias register. 

Any alias registers that are configured to an unsupported register address, or where the read operation fails for some other reason, returns as a zero when read. 

## Example 

Consider reading the process data state registers for all four ports in a single read operation. In this example, the holding registers are configured with the data below: 

**==> picture [500 x 77] intentionally omitted <==**

**----- Start of picture text -----**<br>
Register Value Register Description<br>40701 41001 Port 1 input process data state<br>40702 42001 Port 2 input process data state<br>40703 43001 Port 3 input process data state<br>40704 44001 Port 4 input process data state<br>**----- End of picture text -----**<br>


If the alias registers are read, then they will contain the following register contents: 

**==> picture [500 x 77] intentionally omitted <==**

**----- Start of picture text -----**<br>
Register Value Register Description<br>40501 41001 Port 1 input process data state<br>40502 42001 Port 2 input process data state<br>40503 43001 Port 3 input process data state<br>40504 44001 Port 4 input process data state<br>**----- End of picture text -----**<br>


By default, the alias register is set-up to alias process data for all available ports into a consecutive register map. The alias configuration can always be restored to its factory default value by writing to the Restore Factory Configuration holding register (40605). The alias register space is sized to allow reading all input process data from a 4-port device. 

25-Sep-24 

page 22 of 24 

© Banner Engineering Corp. All rights reserved. 

IO-Link Master for Modbus Converter Device Register Map 

Alias Registers 

## Read-Write Alias Registers 

This set is a series of alias registers with read-write access allowed: 

**==> picture [500 x 32] intentionally omitted <==**

**----- Start of picture text -----**<br>
Registers Parameter Access<br>40901-40968 Read/Write Alias Register Address r/w<br>**----- End of picture text -----**<br>


Each register in this section contains the 16-bit register address for the corresponding alias holding register, which is readable in the alias register space: 

Registers Parameter Access 40801-40868 Read/Write Alias Register r/w 

By default, the read-write alias registers are configured to point to the output process data for each port. The register space is sized to allow for aliasing all output process data for a 4-port device. 

If writing to an alias register fails (for example, if the aliased register is not writeable), then the write operation of the alias registers will NACK. 

A register value that is set to 65535 is always read as 0, and no write operation will be attempted. 

25-Sep-24 

page 23 of 24 

© Banner Engineering Corp. All rights reserved. 

## LinkedIn 

X (formerly Twitter) 

## Facebook 

© 2024. All rights reserved. www.bannerengineering.com