Runtime Errors

The KTx card reports processing problems by putting a fault code into status word 15. Your ladder logic should monitor this word, copy it when not zero, and reset S15 to zero, since the driver never resets the word. The meaning of fault and error codes stored in S15 is documented in the table below and this information supersedes the similar information in the TOPDOC for SoftPLC help system.

Some of these errors occur only during driver initialization discussed above, and this subset of errors will prevent you from placing the system into REM/RUN mode. In order to enter RUN mode, ALL needed adapters must have been powered up and communicating during driver initialization, and S15 should reflect a value of 0 at that time. Otherwise the next attempted transition to RUN mode will fail, even if that is months later. The only way to catch these errors is to either have a monitor hooked up to SoftPLC so you see them on the console, or you can use TOPDOC or your MMI to read from SoftPLC while it is in FAULT mode. SoftPLC will not enter RUN mode under these circumstances.

Other errors can occur while in RUN mode, and these fall into two subsets: those that will fault the CPU and those that will not. When the CPU faults, it turns off all OUTPUTS to the best of its ability and enters FAULT mode.

The one error that you should pay most attention to is number 5324. This can happen in RUN mode and indicates that at least one I/O rack adapter is not communicating properly. (Remember that in order to enter RUN mode, ALL needed adapters had to have been communicating during driver initialization. So this means that an adapter that once was working is now not working.) Error 5324 will not FAULT the CPU. If you want it to, then you will need to add logic to EQU word S15 for 5324 and then set bit S11/6, setting bit S11/6 should fault the CPU. Test this logic to verify it actually faults the CPU as you desire. To determine which I/O rack adapters are faulted, use the TOPDOC Loadable Instruction (TLI) named KTXGETFAULTMAP described in the TLI section.

All block transfer errors are stored in the 3rd word of the respective block transfer "control block". When using BTW or BTR instructions, it is recommended that you use the BTxxx:yyy datatable elements to store the control block information rather than the N (integer) blocks. The advantage of BT elements for control blocks, is that TOPDOC can present a more discernable view of the control block, and will name the 3rd word DLEN. In either case, N or BT control block, upon a successful block transfer the 3rd control block word contains the number of 16 bit words actually transferred and the DN bit comes on. Upon a failed block transfer, this 3rd word instead gets a negative error code, and the ER bit is also set in the control block.

The .NR and .TO bits in the block transfer control block are not used in this driver and therefore have no meaning. If an adapter does not respond to a block transfer command within 4 seconds, the corresponding control block will timeout with an error code of -36 in the 3rd word.