Skip to content
  • There are no suggestions because the search field is empty.

Lucullus Online Tool: Error and Status Codes

How Lucullus Devices Communicate System State, Errors, and Warnings

Overview

In Lucullus, ports are not only used for actuator commands and measured values but also play a critical role in communicating device status and error conditions. To ensure a consistent and standardized approach, every Lucullus device is required to expose dedicated ERROR and STATUS ports.

These ports are typically provided via predefined subdevices, such as StatusSubDevA or StatusSubDevB. Because all Lucullus devices must include one of these status subdevices, the Online Tool can reliably display the operational state of any device in a uniform way.

 

The ERROR Port

The ERROR port is used to report system-level and communication-related problems.

  • A value of 0 indicates that no error is present.
  • Any non-zero value indicates an error condition.

When an error is detected:

  • The Lucullus Online Tool displays a “Communication Error” warning.
  • A red status bar appears in the footer of the Online Tool to highlight the issue.


Process-Specific Errors (System Device)

Each Lucullus process automatically includes a system device called syssystem, which is displayed in the Online Tool as “System Device.”

The ERROR port of this system device reflects the current state of the process logger. Internally, this value is a direct copy of the LoggerError variable.

The following error codes may be reported by the system device:

Error Code

Name

 

1002

FORMAT_ERROR

 

1003

DB_ACCESS_ERROR

 

1004

DB_WRITE_ERROR

 

1005

IPC_ERROR

 

Detailed explanations of these logger-related error codes will be documented separately.

 

Device-Specific Errors

For all other devices, communication-related errors are reported via the ERROR port of StatusSubDevB.

The following standard error codes are used:

Error Code

Description

0

No error 

2

Protocol error 

3

Timeout error 

4

No results returned; the device or OPC server is likely offline or stopped

6

OPC “quality bad” status. At least one OPC item has reported a bad quality state. Additional details can be found in the Lucullus log file.

As with system errors, more detailed explanations and troubleshooting guidance for these codes will be added in a future update.

 

Summary

By enforcing dedicated ERROR and STATUS ports across all devices, Lucullus provides a consistent and transparent mechanism for communicating system health and communication issues. The Online Tool leverages this standardized structure to clearly inform users of error conditions, enabling faster diagnosis and resolution.