BK7500 (SERCOS interface)
The BK7500 Bus Coupler is used for controllers with SERCOS interface. Those specific properties which distinguish them from other Bus Couplers are described below.
The coupler has been designed according to the SERCOS I/O specification and generates corresponding I/O data channels that can be addressed via IDNs. It should therefore be possible to use it with any controller that conforms to the SERCOS interface. For an Overview of all currently supported SERCOS Bus Couplers BK75x0, please see...
”BK75x0” tab
Address: This is used to set the Sercos address with which the coupler announces its presence on the bus.
K-Bus Update: Knowing the attached terminals, the estimated K-Bus run-time is calculated and given.
Strict Mode: The manufacturer-specific parameter P-0-0001 can be used to specify whether the I/O data channels are to be allocated in strict accordance with the Sercos I/O specification, or whether a variation that saves IDNs should be used, since some controllers can only handle a limited number of IDNs in the Master Data Telegram (MDT) or Drive Telegram (AT). The checkbox on this tab only displays the selected mode. It can be modified on the next tab, under Startup, because this parameter is communicated at each start-up (change from phase 2 to phase 3), and the I/O data channels are then assigned accordingly.
Firmware Update...: The coupler's firmware can be updated by means of what is known as a KS2000 cable.
"Startup" tab
Any IDNs can be given (2 and 4 byte values) on the "Startup" file tab, and these are sent to the coupler at the change from phase 2 to phase 3. Further values can be added or deleted here.
"Actual-/Nominal Channel" tab
Both the coupler and the TwinCAT System Manager calculate the assignment of the I/O data channels in the light of the connected terminals. The value in P-0-0001, which should normally always be included in the start-up parameters, is considered here, so that both the coupler and the System Manager calculate according to the same rules. The calculated I/O data channels are included in the AT's list of IDNs (S-0-0016, actual channel), or that of the MDT (S-0-0024, nominal channel). In addition to the automatically generated entries, further IDNs can be included in the AT and MDT (as shown in the diagram of the IDN S-0-0364).
"Online" tab
Read and write access to all the coupler's IDNs is possible through the Online tab at run-time from phase 2 onwards.