One unit consists of one Bus Coupler, any number from 1 to 64 terminals and one end terminal. With the K-bus extension, up to Bus Terminals can be connected. The Bus Couplers recognize the terminals to which they are connected, and perform the assignment of the inputs and outputs to the words of the process image automatically. Connection is through normal RJ 45 connectors. As far as the user is concerned, the inputs and outputs are not handled any differently from the way they are with other coupler series. The information is made available for use as a byte array in the process image of the automation device.
|Published (Last):||3 January 2016|
|PDF File Size:||19.70 Mb|
|ePub File Size:||13.51 Mb|
|Price:||Free* [*Free Regsitration Required]|
After switching on, the Bus Coupler immediately checks the connected configuration. The error code can be determined from the frequency and number of blinks. This permits rapid rectification of the error.
The upper group with four LEDs indicates the status of the respective fieldbus. The significance of the fieldbus status LEDs is explained in the appropriate sections of this manual. It corresponds to the usual fieldbus display. On the upper right hand side of the Bus Couplers are two more green LEDs that indicate the supply voltage.
The right hand LED indicates the presence of the supply to the power contacts. Diagnostic LEDs. Left LED off. Bus Coupler has no power.
Right LED off. Physical connection present. No physical connection present. Flashing: Bus traffic present. No bus traffic bus idle. Flashing: data received at the controller. No error. PLC program is in stop mode. WDG BK only. Watchdog is triggered. Watchdog expired or not triggered. Error code. Error code argument.
Persistent, continuous flashing. EMC problems. Set manufacturer's setting with the KS configuration software. Code buffer overflow. Insert fewer Bus Terminals. Too many entries in the table for the programmed configuration. Unknown data type. Software update required for the Bus Coupler. Programmed configuration has an incorrect table entry. Check programmed configuration for correctness.
Table comparison Bus Terminal n. Incorrect table entry. K-bus command error. Repeat until the defective Bus Terminal is located. K-bus data error, break behind the Bus Coupler. Break behind Bus Terminal n. Check whether the bus end terminal is connected.
K-bus error in register communication with Bus Terminal n. Exchange the n th bus terminal. Error at initialization. Exchange Bus Coupler. Internal data error. Perform a hardware reset on the Bus Coupler switch off and on again. DIP switch incorrect for BootP. Set to on or off , see BootP. Error in IP socket. Note: cycle time was exceeded see Table 1, Register Warning: the set cycle time was exceeded. Remedy: increase the cycle time. Checksum error in Flash program. Transmit program to the BC again.
Incorrect or faulty library implemented. Remove the faulty library. Bus Terminal n is not consistent with the configuration that existed when the boot project was created. Check the n th Bus Terminal.
The boot project must be deleted if the insertion of an n th Bus Terminal is intentional. Start the Bus Coupler again, and if the error occurs again then exchange the Bus Terminal. Number of Bus Terminals is no longer correct. Start the Bus Coupler again. If the error occurs again, restore the manufacturers setting using the KS configuration software. Length of the K-bus data is no longer correct. Communication available.
BK9000 | Ethernet TCP/IP Bus Coupler
The BC is an intelligent slave and can be used as a non-central intelligence in the Ethernet system. One unit consists of the Bus Terminal Controller, any number of terminals between 1 and 64, and a bus end terminal. Each Bus Terminal can be configured in such a way that it exchanges data directly through the fieldbus with the higher-level automation device. Similarly, pre-processed data can be exchanged between the Bus Terminal Controller and the higher-level controller via the fieldbus.
BK9000 (Ethernet Interface)
In reference to the last which is available since TwinCAT v 2. The BK has to be configured with the same subnet address as the Ethernet Miniport adapter, of course first two quadruples. If, i. Firmware Update : The firmware update dialog is called by pushing this button.
BC9100 | Ethernet TCP/IP Bus Terminal Controller