ProSoft Technology 5104-DNPS-PDPM - Manual (Page 52)

Diagnostics and Troubleshooting PDPM ♦ ProLinx Gateway
Protocol Manual PROFIBUS DP Master
Page 52 of 70 ProSoft Technology, Inc.
June 24, 2013
Error
Number Description
-26 DRIVER: Could not create write event
-27 DRIVER: Could not create timer event
-28 DRIVER: Error by writing data
-29 DRIVER: Wrong COM state
-30 DRIVER: Set COM state error
-31 DRIVER: COM buffer setup failed
-32 DRIVER: COM set timeout failed
-33 DRIVER: RX buffer overrun
-34 DRIVER: RX buffer full
-35 DRIVER: TX busy
-36 DRIVER: Error during close driver
-40 USER: COM port not opened
-41 USER: Invalid handle value
-42 USER: Invalid COM number
-43 USER: Size parameter invalid
-44 USER: Size parameter zero
-45 USER: Buffer pointer is NULL
-46 USER: Buffer too short
-47 USER: Setup error
-50 USER: Send message, timeout error
-51 USER: Could not send a message
-52 USER: Send message, no device connected
-53 USER: Error by send message, message receiving
-54 USER: Telegram collision
-55 USER: Telegram, no acknowledgement received
-56 USER: Telegram, noise
-57 USER: Telegram, data overrun
-58 USER: Telegram, parity error
-59 USER: Telegram, framing error
-60 USER: Telegram, unknown error
-70 USER: Timeout by receive a message
-71 USER: No message received
5.4.2 RCS Error Numbers (4 to 93)
This is the list of error numbers returned by the RCS (Real-time Communication
System), that is the operating system. The error number is returned in an answer
message. Command messages and answer messages communicate between
the application (for example, the system configuration) and the master device.
An example of this communication is the download of a configuration.