Register settings, Table 100
The registers can be set through a dialog using the KS2000 configuration software, or it is possible to write into the registers directly.
Register | Description | Default | Bus Terminal Controller | |
|---|---|---|---|---|
0…1 | IP address | 0xAC, 0x10, 0x11, 0x00 | BC9000, BC9100, BK9000, BK9050, BK9100 | |
2…3 | IP mask | 0xFF, 0xFF, 0x00, 0x00 | BC9000, BC9100, BK9000, BK9050, BK9100 | |
4…13 | Device Name | BC9000 | BC9000, BC9100, BK9000, BK9050, BK9100 | |
14 | Watchdog AMS/ADS | 1000 ms | BC9000, BC9100, BK9000, BK9050, BK9100 | |
15.0 | 0bin | enable ModbusTCP | 0bin | BC9000, BC9100, BK9000, BK9050, BK9100 |
1bin | disable ModbusTCP | |||
15.1 | 0bin | enable AMS/ADS | 0bin | |
1bin | disable AMS/ADS | |||
16.8 | 0bin | Ethernet mode half duplex | 1bin | BC9000, BC9100, BK9000, BK9050, BK9100 |
1bin | Ethernet mode full duplex | |||
16.12 | 0bin | Autobaud off | 1bin | |
1bin | Autobaud on | |||
16.13 | 0bin | 10 Mbaud | 1bin | |
1bin | 100 Mbaud | |||
17…18 | Default Gateway | 0x00, 0x00, 0x00, 0x00 | BC9000, BC9100, BK9000, BK9050, BK9100 | |
24 | Watchdog ModbusTCP | 1000 ms | BC9000, BC9100, BK9000, BK9050, BK9100 | |
25.0 | Entry of a fieldbus error (connection to switch interrupted) in the flags area diagnosis | 0bin | BC9000, BC9100 | |
0bin | Error was not entered | |||
1bin | Error was entered | |||
26 | ModbusTCP port no. | 502 | BC9000, BC9100, BK9000, BK9050, BK9100 | |
27 | ADS connection service life | 10 s | BC9000, BC9100, BK9000, BK9050, BK9100 | |
28 | Modbus connection service life | 10 s | BC9000, BC9100, BK9000, BK9050, BK9100 | |
29.0 | ModbusTCP mode | 0bin | BC9000, BC9100, BK9000, BK9050, BK9100 | |
1bin | Fast ModbusTCP | |||
 | ModbusTCP Connections A maximum of three ModbusTCP connections are permitted! Only the first connection gets the read/write access, further connections get only read access. The Modbus client should only send a further request to the bus coupler after the bus coupler has responded to the last request or after a timeout period (> 1 s) has elapsed (recommended 5 seconds). It is also recommended that a certain idle time (> 100 ms) be observed between request and response. |
| Increased network load Increased network load due to e.g. incorrectly configured networks may cause the bus coupler to stop responding. Once the network load problem has been eliminated, it may be necessary to reboot the Bus Coupler. |