Register pages for IO-Link parameters
The parameters of the KL6224 can be accessed via register communication or via the KS2000 configuration software. The register model of the terminals is used as a basis. The KL6224 has 64 registers (words). Registers 0 to 31 always have the same meaning. The contents of registers 32 to 63 are specified via the register page selection register (R4).
A register page has 32 registers (64 bytes). The following register pages are used:
- Register page 4: Parameter(s) for channel 1 (IO-Link device 1)
- Register page 5: Parameter(s) for channel 2 (IO-Link device 2)
- Register page 6: Parameter(s) for channel 3 (IO-Link device 4)
- Register page 7: Parameter(s) for channel 4 (IO-Link device 4)
- Register page 8: CMD/status interface and acyclic data for IO-Link devices
- Register page 9: acyclic data
Assignment of the IO-Link parameters to the register page and the terminal register
Register page 4 (RP4): Parameter(s) for channel 1 (IO-Link device 1)
KL6224 registers | Description | Name | Comment | ||||
---|---|---|---|---|---|---|---|
RP4.R32 | IO-Link master configuration: | IO-Link DeviceID LowWord | Device ID of the IO-Link device | ||||
RP4.R33 | IO-Link DeviceID HighWord | ||||||
RP4.R34 | IO-Link VendorID LowWord | Vendor ID of the IO-Link device | |||||
RP4.R35 | IO-Link VendorID HighWord | ||||||
RP4.R36 | LowByte | IO-Link revision: | ID of the specification version based on which the IO-Link device communicates. | ||||
HighByte | FrameCapability: | The Frame Capability indicates certain functionalities of the IO-Link device (e.g. SPDU supported). | |||||
RP4.R37 | LowByte | minCycleTime: | See table below (time base) | ||||
HighByte | OffsetTime | reserved | |||||
RP4.R38 | LowByte | ProcDataLenght Input | Bit 7 | Byte | 0bin | Length is counted in bits | |
1bin | Length is counted in bytes | ||||||
Bit 6 | SIO | 1bin | The device supports the standard IO mode | ||||
Bit 0...4 | Length |
| Length of the process data | ||||
HighByte | ProcDataLenght Output | see LowByte | |||||
RP4.R39 | CompatibleId | Currently not used | |||||
RP4.R40 | - | reserved | |||||
RP4.R41 | MasterControl | 0 | Channel 1 is inactive | ||||
1 | Channel 1 is digital input | ||||||
2 | Channel 1 is digital output | ||||||
3 | Channel 1 is IO-Link port and communicates via the IO-Link protocol | ||||||
4 | reserved | ||||||
5 | Channel 1 is IO-Link port and communicates via the IO-Link protocol with compressed mode. |
Time Base
Time Base | Time base meaning | Calculation | Min. Cycle Time |
---|---|---|---|
00bin | 0.1 ms | Multiplier x Time Base | 0.0...6.3 ms |
01bin | 0.4 ms | 6.4 ms + Multiplier x Time Base | 6.4...31.6 ms |
10bin | 1.6 ms | 32.0 ms + Multiplier x Time Base | 32.0...132.8 ms |
11bin | 6.4 ms | 134.4 ms + Multiplier x Time Base | 134.4...537.6 ms |
KL6224 registers | Description | Name | Comment | ||||
---|---|---|---|---|---|---|---|
RP4.R42 | IO-Link actual data: | IO-Link DeviceID LowWord | Device ID of the IO-Link device | ||||
RP4.R43 | IO-Link DeviceID HiWord | ||||||
RP4.R44 | IO-Link VendorID LowWord | Vendor ID of the IO-Link device | |||||
RP4.R45 | IO-Link VendorID HiWord | ||||||
RP4.R46 | LowByte | IO-Link revision | ID of the specification version based on which the IO-Link device communicates. | ||||
HighByte | FrameCapability: | The Frame Capability indicates certain functionalities of the IO-Link device (e.g. SPDU supported). | |||||
RP4.R47 | LowByte | minCycleTime: | See table below (time base) | ||||
HighByte | OffsetTime | reserved | |||||
RP4.R48 | LowByte | ProcDataLenght Input | Bit 7 | Byte | 0bin | Length is counted in bits | |
1bin | Length is counted in bytes | ||||||
Bit 6 | SIO | 1bin | The device supports the standard IO mode | ||||
Bit 0...4 | Length |
| Length of the process data | ||||
HighByte | ProcDataLenght Output | see LowByte | |||||
RP4.R49 | - | reserved | |||||
RP4.R50 | - | reserved | |||||
RP4.R51 | - | reserved |
Time Base | Time base meaning | Calculation | Min. Cycle Time |
---|---|---|---|
00bin | 0.1 ms | Multiplier x Time Base | 0.0...6.3 ms |
01bin | 0.4 ms | 6.4 ms + Multiplier x Time Base | 6.4...31.6 ms |
10bin | 1.6 ms | 32.0 ms + Multiplier x Time Base | 32.0...132.8 ms |
11bin | 6.4 ms | 134.4 ms + Multiplier x Time Base | 134.4...537.6 ms |
KL6224 registers | Description | Name | Comment | ||
---|---|---|---|---|---|
RP4.R52 | IO-Link diagnostics | LowByte | IO-Link state similar to object 0xA000 of the EL6224). | 0 | Inactive |
1 | DigInput | ||||
2 | DigOutput | ||||
3 | EstablishComm | ||||
4 | InitMaster | ||||
5 | InitDevice | ||||
6 | reserved | ||||
7 | reserved | ||||
8 | Operate | ||||
9 | Stop | ||||
HighByte | LostFrames | This parameter counts the number of lost IO-Link telegrams. This value is deleted whenever IO-Link starts up, otherwise it is incremented continuously. |
Register page 8 (RP8): CMD/status interface and acyclic data for IO-Link device
KL6224 | Description |
| Comment | |
---|---|---|---|---|
RP8.R32 | Cmd | TACYCLICKBUSCMD_CMD_START | 0x00000001 | |
TACYCLICKBUSCMD_CMD_ACK | 0x00000002 | |||
TACYCLICKBUSCMD_CMD_READ_CH1 | 0x00000010 | |||
TACYCLICKBUSCMD_CMD_READ_CH2 | 0x00000020 | |||
TACYCLICKBUSCMD_CMD_READ_CH3 | 0x00000030 | |||
TACYCLICKBUSCMD_CMD_READ_CH4 | 0x00000040 | |||
TACYCLICKBUSCMD_CMD_WRITE_CH1 | 0x00000100 | |||
TACYCLICKBUSCMD_CMD_WRITE_CH2 | 0x00000200 | |||
TACYCLICKBUSCMD_CMD_WRITE_CH3 | 0x00000300 | |||
TACYCLICKBUSCMD_CMD_WRITE_CH4 | 0x00000400 | |||
TACYCLICKBUSCMD_CMD_SCAN_CH1 | 0x00001000 | |||
TACYCLICKBUSCMD_CMD_SCAN_CH2 | 0x00002000 | |||
TACYCLICKBUSCMD_CMD_SCAN_CH3 | 0x00003000 | |||
TACYCLICKBUSCMD_CMD_SCAN_CH4 | 0x00004000 | |||
RP8.R33 | Status | TACYCLICKBUSCMD_STATUS_IDLE | 0x00000000 | |
TACYCLICKBUSCMD_STATUS_BUSY | 0x00000001 | |||
TACYCLICKBUSCMD_STATUS_DATAREADY | 0x00000002 | |||
TACYCLICKBUSCMD_STATUS_DATAERROR | 0x00000003 | |||
RP8.R34 |
| SPDU / ISDU SubIdx | SPDU / ISDN index | |
RP8.R35 |
| LowByte | Length | Length of the data |
HighByte | SPDU / ISDU SubIdx | SPDU / ISDN subindex | ||
RP8.R36 | Acyclic data for the IO-Link device |
|
| |
... |
|
| ||
RP8.R61 |
|
|
Register page 9 (RP9): Further acyclic data for the IO-Link device
KL6224 registers | Description | Value | Comment |
---|---|---|---|
RP9.R0 | Further acyclic data for the IO-Link device |
|
|
... |
|
| |
RP9.R61 |
|
|
Process of an acyclic query
The process of an acyclic query to an IO-Link device is as follows:
- Reading of register page 8 R33 (status) to ascertain whether status is Idle
- If status = Idle, write TACYCLICKBUSCMD_CMD_START to register page 8 R32 (Cmd)
- Write acyclic data into the buffer from register page 8, R36, as required
- Start the service by writing the corresponding services in register page 8 R32 (Cmd)
- Read register page 8 R33 (status) until no longer busy
- Read acyclic data from the buffer from register page 8, R36, as required
- Conclude the service by writing TACYCLICKBUSCMD_CMD_ACK to register page 8 R32 (Cmd)