Digital inputs 10 x KL1xx4, i. Example for entering individual bytes and Fig. Example for entering contiguous bytes. Byte-oriented modules are the first to be mapped into the process image, and for this reason all the complex modules must first be entered in the sequence in which they are plugged into the Bus Coupler.
|Published (Last):||24 July 2006|
|PDF File Size:||16.92 Mb|
|ePub File Size:||8.98 Mb|
|Price:||Free* [*Free Regsitration Required]|
The upper group BK3xx0 or left hand group LC indicates the state of the fieldbus. The right hand LED indicates the presence of the supply to the power contacts. These indicate the operational state of the Bus Terminals and the connection to these Bus Terminals.
The errors are displayed in the blink code in the following way:. The number of pulses indicates the position of the last Bus Terminal before the fault.
Passive Bus Terminals, such as a power feed terminal, are not included in the count. Operating state: RUN, inputs are read and outputs are set. Everything is operating correctly. Bus activity, but slave is already parameterized.
Start master. Check parameters, configuration possible error in DP start-up. Data exchange with the master is not started. PLC start. No bus activity. Start the master, check the bus cable. Start master, check parameters, configuration possible error in DP start-up.
Start of the error code. First slow sequence. Error code. Second slow sequence. Error argument error location. Error code argument. Persistent, continuous flashing. Check the Bus Terminal strip. Inline code buffer overflow. Connect fewer Bus Terminals; too many entries in the table for the programmed configuration. Unknown data type. Software update required for the coupler. Programmed configuration incorrect. Check programmed configuration for correctness.
K-bus command error. No Bus Terminal connected; attach Bus Terminals. One of the Bus Terminals is defective; halve the number of Bus Terminals attached and check whether the error is still present with the remaining Bus Terminals. Repeat until the defective Bus Terminal is located. K-bus data error, break behind Bus Coupler n. Check whether the End Terminal is connected. K-bus error in register communication with Bus Terminal n. Replace Bus Terminal n. Checksum error in program flash memory.
Set manufacturer's setting with the KS Runtime K-bus command error. Bus Terminal n has the wrong format. Start the coupler again, and if the error occurs again then exchange the Bus Terminal.
Number of Bus Terminals is no longer correct. Length of the K-bus data bit length is no longer correct. K-bus outputs become 0 or b.
K-bus outputs are retained.
BK3100 | PROFIBUS Bus Coupler
BK3120 | PROFIBUS “Economy plus” Bus Coupler
BK3150 | PROFIBUS “Compact” Bus Coupler