The DeviceNet status data from a node can be read by any TwinCAT program via ADS and/or signalled to any TwinCAT program.
”Parameter” tab
The parameters are read from the EDS when creating the box. If the system has not started up yet, the EDS default value is always displayed under the value input.
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 Overviewof all currently supported SERCOS Bus Couplers BK75x0, please see...
”BK75x0” tab
TwinCAT System Manager: Reference
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.
BK9000 (Ethernet Interface)
The Beckhoff BK9000Bus Coupler can be configured in TwinCAT below a "Virtual Ethernet Interface"or Ethernet Miniport (real-time)I/O device. In reference to the last which is available since TwinCAT v 2.9 is released, an introduction can be found under: Introduction of TwinCAT Real-Time Ethernet.
The following description explains the differences between a BK9000 and other Beckhoff Bus Couplers. The Ethernet coupler communicates in non-real-time applications via TCP/IP or UDP (and ADSas the Application Layer on top of it) with TwinCAT. For an Overviewof all currently supported Bus Couplers BK90x0 for Virtual Ethernet Interface, please see...
For an Overviewof all currently supported Bus Couplers BK90x0 for Ethernet Miniport (real-time), please see...
Hint: If Real-Time Ethernet and "normal" Ethernet are both used on the same system with two different network adapters, the subnet addresses of these TwinCAT System Manager: Reference
adapters (NICs) must differ! The BK9000 has to be configured with the same subnet address as the Ethernet Miniport adapter, of course (first two quadruples).
"BK9000" Tab
Diagnosis: This checkbox is deactivated for the BK9000.
2 Byte PLC Interface: This checkbox is deactivated for the BK9000.
No Real time Flag: If unchecked, the BK9000 bypasses at all incoming Ethernet frames its internal TCP/IP stack (default if used with Beckhoff TwinCAT Real-Time Ethernet in Run Mode). If, i.e. for configuration purposes in Config Modesessions the TCP/IP part has to be enabled, this flag may be activated.
K-Bus Update: According to the attached Bus Terminals, the estimated K-Bus update time is calculated and displayed here.
Firmware Update: The firmware update dialog is called by pushing this button. With this function, the most recent firmware version for the BK9000 can be loaded to this device (via LAN or COM port).
Data Exchange: The data exchange with devices can be adapted to their local K-Bus update time and related application. The following description is based on the fact, that the I/O driver resolves an internal cycle counter which is always present.
Scenario: A network contains two Bus Couplers. One Coupler (A) has only a few digital Bus Terminals attached and needs to be updated fast. Another Coupler (B) has analog Bus Terminals and doesn't need to get updated that fast. In that case, at Bus Coupler (B) the
- Divider: would be set e.g. to '4' to force the I/O system to only exchange data with this device in every 4th I/O cycle and the
- Modulo: factor takes care (in the above case it can be set to value between 0..3) that (B) doesn't get an update in the same cycle (A) gets it.
VLAN Support:
- Enable: Activates the VLAN support (see: IEEE 802.1Q, RFC3518) for the communication with this device. If enabled, the Ethernet frame is getting extended by 4 byte. These extension is called VLAN tag and contains informations about ID and priority for instance
- Priority: A 3 bit VLAN priority value as defined by IEEE 802.1D. Most switches contain two queues, a high and a low priority one. Therefore priorities between 0..3 are assigned to the high priority queue and 4..7 are assigned to the low priority queue at those switch types.
- Id: 12 bit VLAN identifier number as defined by IEEE 802.1Q.
"IP Address" Tab
For further informations about this tab, see -> "IP Address" Tab.
"ADS Commands" Tab
For further informations about this tab, see -> "ADS Command Window".