Error code list
This section provides a list of error identifiers that are displayed in the Status Timeline, including the following items for each identifier.
| Item | Description |
|---|---|
| Message | Message assigned to the error identifier |
| Content | Details of the error |
| Action | How to resolve the error |
Component default#
NO_MEMORY#
| Item | Description |
|---|---|
| Message | Low memory |
| Content | Not enough memory on the machine running SpeeDBee Synapse. |
| Action | Stop components not in use. In addition, make sure that unnecessary data collection and other wasteful settings are not configured. If the error still persists, consult your System Administrator and add more memory or to adjust with other applications. |
PARAMETER_PARSE_ERROR#
| Item | Description |
|---|---|
| Message | Parameter parsing error |
| Content | The configuration file has not been saved in the correct format. The settings may be corrupted. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
PARAMETER_FORMAT_ERROR#
| Item | Description |
|---|---|
| Message | Parameter error |
| Content | The configuration file contains incorrect parameters. |
| Action | In the Compute Collector, this error occurs if no variable or expression is set. In other components, it may also occur due to poor configurations, such as an incorrect Azure connection string. Check the configuration of the relevant component. If the error persists, consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
FRAMEWORK_ERROR#
| Item | Description |
|---|---|
| Message | Framework api error |
| Content | An error occurred in the internal framework used by the relevant component. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
DISK_FULL#
| Item | Description |
|---|---|
| Message | Disk full |
| Content | Not enough storage space on the machine running SpeeDBee Synapse. |
| Action | You need to take some action, such as deleting unnecessary files. Consult your System Administrator and free up storage space. |
IO_ERROR#
| Item | Description |
|---|---|
| Message | IO error |
| Content | Failed in I/O processing on the machine running SpeeDBee Synapse. (E.g., storage read/write failure) |
| Action | Consult your System Administrator and make confirmation on the storage status and the like. (E.g., possibility of failure) |
NETWORK_ACCESS_ERROR#
| Item | Description |
|---|---|
| Message | Network access error |
| Content | A communication error occurred in the relevant component. |
| Action | (Action 1) Make sure that the machine running SpeeDBee Synapse is connected to the network. (Action 2) Make sure that the device or service to which the relevant component communicates is enabled for communication. |
PROCESSING_DELAY#
| Item | Description |
|---|---|
| Message | Processing delay |
| Content | Processing is delayed on the relevant component. |
| Action | (Action 1) Reduce the count of data items sent and received by the relevant component. (Action 2) Stop or remove unnecessary components that are running on SpeeDBee Synapse. (Action 3) Check whether no delay has occurred in the network of the machine running SpeeDBee Synapse. |
INVALID_REGEX#
| Item | Description |
|---|---|
| Message | Regex error |
| Content | A setting of the relevant component has the input of a regular expression in an incorrect format. |
| Action | 1. Open the configuration screen of the relevant component. 2. Check the settings to identify the one with the input of a regular expression in an incorrect format. 3. For the setting confirmed in step 2, enter a regular expression in the correct format, and save it. 4. Restart the relevant component. |
COMPONENT_DATA_MISMATCH#
| Item | Description |
|---|---|
| Message | No data for the component matching the specified parameters Note: This message includes the following information. ▪ Component ▪ Data |
| Content | No data corresponds to the contents specified in the settings. In this state, no action is taken according to the relevant configuration. |
| Action | 1. Confirm the component and data included in the message. 2. Right-click the IN Port of the relevant component. 3. Specify "Receive and set data definitions" for the "Setting option" setting, and check the data list. 4. Open the configuration screen of the relevant component. 5. For the setting with the data confirmed in step 1 specified, enter the data confirmed in step 3, and save it. Note: If you use a regular expression to specify data, enter the regular expression that contains at least one item of data confirmed in step 3. 6. Restart the relevant component. |
STATISTICS_INIT_ERROR#
| Item | Description |
|---|---|
| Message | Statistical processing Initialization error |
| Content | Failed to initialize statistical processing. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
STATISTICS_INSERT_ERROR#
| Item | Description |
|---|---|
| Message | Statistics registration error |
| Content | Failed to register a statistic value. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
UNAVAILABLE_DATA_TYPE#
| Item | Description |
|---|---|
| Message | An invalid type was specified in the conditional expression Note: This message includes the following information. ▪ Component ▪ Data |
| Content | The specified type cannot be used for data in a conditional expression. For example, strings and arrays cannot be used in conditional expressions. |
| Action | 1. Confirm the component and data included in the message. 2. Open the configuration screen of the relevant component. 3. For the setting with the data type confirmed in step 1 specified, specify the appropriate data type, and save it. 4. Restart the relevant component. |
UNKNOWN_ERROR#
| Item | Description |
|---|---|
| Message | Unknown error |
| Content | An unknown error occurred. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
INTERNAL_ERROR#
| Item | Description |
|---|---|
| Message | Unexpected Error |
| Content | An error occurred that does not correspond to other error identifiers. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
Resource Collector#
CPUUSAGE_OPENREAD_ERROR#
| Item | Description |
|---|---|
| Message | CPU usage open error |
| Content | Unable to access the following file containing CPU usage information. /proc/stat |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
CPUUSAGE_FORMAT_ERROR#
| Item | Description |
|---|---|
| Message | CPU usage acquisition error |
| Content | Failed to retrieve CPU usage information from the following file. /proc/stat |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
CPUFREQ_OPENREAD_ERROR#
| Item | Description |
|---|---|
| Message | CPU frequency open error |
| Content | Unable to access the following file containing CPU frequency information. /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq |
| Action | The CPU frequency is not acquirable depending on your machine or platform. If the above file exists and this error occurs, consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
CPUFREQ_FORMAT_ERROR#
| Item | Description |
|---|---|
| Message | CPU frequency acquisition error |
| Content | Failed to retrieve CPU frequency information from the following file. /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq |
| Action | The CPU frequency is not acquirable depending on your machine or platform. If the above file exists and this error occurs, consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
CPUTEMP_OPENREAD_ERROR#
| Item | Description |
|---|---|
| Message | CPU temperature open error |
| Content | Unable to access the following file containing CPU temperature information. /sys/class/thermal/thermal_zone0/temp |
| Action | The CPU temperature is not acquirable depending on your machine or platform. If the above file exists and this error occurs, consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
CPUTEMP_FORMAT_ERROR#
| Item | Description |
|---|---|
| Message | CPU temperature acquisition error |
| Content | Failed to retrieve CPU temperature information from the following file. /sys/class/thermal/thermal_zone0/temp |
| Action | The CPU temperature is not acquirable depending on your machine or platform. If the above file exists and this error occurs, consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
IOSTAT_NOT_FOUND#
| Item | Description |
|---|---|
| Message | IO device error |
| Content | The following file containing IO information does not exist. /dev/{"I/O device" setting} |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
IOSTAT_OPENREAD_ERROR#
| Item | Description |
|---|---|
| Message | IO open error |
| Content | Unable to access the following file containing IO information. /dev/{"I/O device" setting} |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
IOSTAT_FORMAT_ERROR#
| Item | Description |
|---|---|
| Message | IO acquisition error |
| Content | Failed to retrieve IO information from the following file. /dev/{"I/O device" setting} |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
IOSTAT_STORAGE_MOUNT_POINT_ERROR#
| Item | Description |
|---|---|
| Message | IO unacquirable (unable to get mount point) Note: This message includes the following information. ▪ Device name |
| Content | Mount point information is not defined correctly in the configuration file. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
IOSTAT_STORAGE_INFO_ERROR#
| Item | Description |
|---|---|
| Message | IO unacquirable (unable to get information with statvfs) Note: This message includes the following information. ▪ Device name ▪ Mount point ▪ Status |
| Content | Failed to get IO information using the statvfs command for the mount point defined in the configuration file. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
MEM_OPENREAD_ERROR#
| Item | Description |
|---|---|
| Message | Memory open error |
| Content | Unable to access the following file containing memory information. /proc/meminfo |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
MEM_FORMAT_ERROR#
| Item | Description |
|---|---|
| Message | Memory acquisition error |
| Content | Failed to retrieve memory information from the following file. /proc/meminfo |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
NETWORK_OPENREAD_ERROR#
| Item | Description |
|---|---|
| Message | Network open error |
| Content | Unable to access the following file containing network information. /proc/net/dev |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
NETWORK_FORMAT_ERROR#
| Item | Description |
|---|---|
| Message | Network acquisition error |
| Content | Failed to retrieve network information from the following file. /proc/net/dev |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
PLC Collector#
CONNECTION_REFUSED#
| Item | Description |
|---|---|
| Message | Disconnected |
| Content | The PLC has been disconnected. |
| Action | (Action 1) Restart the component. (Action 2) 1. Check the configuration on the PLC side for the host and port capable of communication. 2. Open the configuration screen of the relevant component. 3. For the "Host" and "Port" settings, enter the host and port confirmed in step 1, and save them. 4. Restart the relevant component. |
NETWORK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Timeout Note: This message includes the following information. ▪ Address ▪ Port number ▪ Setting timeout value ▪ Operation type |
| Content | (When the operation type is connect or close) Failed to connect the PLC within the time specified for the "Connect timeout" setting. (When the operation type is receive or send) Failed to receive data from the PLC within the time specified for the "Read timeout" setting. |
| Action | 1. Confirm the operation type included in the message. 2. Open the configuration screen of the relevant component. 3. (When the operation type confirmed in step 1 is connect or close) Increase the "Connect timeout" setting. (When the operation type confirmed in step 1 is receive or send) Increase the "Read timeout" setting. 4. Restart the relevant component. |
SERIAL_CONNECTION_REFUSED#
| Item | Description |
|---|---|
| Message | Disconnected (Serial Communication) |
| Content | The PLC has been disconnected. |
| Action | (Action 1) Restart the component. (Action 2) 1. Check the PLC settings for the correct "Device", "Baud rate", "Data bit", "Stop bit", and "Parity bit". 2. Open the configuration screen of the relevant component. 3. Enter and save the values confirmed in step 1 for the "Device", "Baud rate", "Data bit", "Stop bit", and "Parity bit" settings. 4. Restart the relevant component. |
SERIAL_NETWORK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Timeout (Serial Communication) Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Configured timeout value ▪ Operation type |
| Content | Failed to receive data from the PLC within the time specified for the "Read timeout" setting. |
| Action | 1. Open the configuration screen of the relevant component. 2. Increase the "Read timeout" setting. 3. Restart the relevant component. |
SERIAL_NETWORK_ACCESS_ERROR#
| Item | Description |
|---|---|
| Message | Communication error Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Error number ▪ Operation type |
| Content | (When the operation type is connect) Failed to connect to the PLC. (When the operation type is receive or send) Failed to send or receive data to/from the PLC. |
| Action | 1. Confirm the operation type included in the message. (If the operation type confirmed in step 1 is connect) 2. Open the configuration screen of the relevant component. 3. Check the PLC settings for the correct "Device", "Baud rate", "Data bit", "Stop bit", and "Parity bit", and enter and save the confirmed settings. 4. Restart the relevant component. (If the operation type confirmed in step 1 is receive or send) 2. Check for any connection issues with the PLC. |
SERIAL_LOCK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Connection exclusive control timeout (Serial Communication) Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Configured timeout value ▪ Operation type |
| Content | Could not connect to the PLC within the time specified for the "Connect timeout" setting because another component using the same device is currently connected. |
| Action | 1. Open the configuration screen of the relevant component. 2. Increase the value of the "Connect timeout" setting. 3. Restart the relevant component. |
REGISTER_ADDRESS_ERROR#
| Item | Description |
|---|---|
| Message | Specified register is invalid Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A register address not supporting bit specification has been entered in the "Address" setting with bit specification. |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Address" setting of the register confirmed in step 1, enter the register address that supports bit specification, and save it. 4. Restart the relevant component. |
REGISTER_ADDRESS_RANGE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect register address Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A register address that cannot be handled by the PLC protocol has been entered in the "Address" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Address" setting of the register confirmed in step 1, enter the register address that can be handled by the PLC protocol, and save it. 4. Restart the relevant component. Note: Refer to the manual of the relevant device and others for usable addresses and their range. |
REGISTER_ADDRESS_DATA_TYPE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect data type Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A data type different from the configuration on the PLC side has been specified for the "Data type" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Check the PLC configuration for the data type of the register confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Data type" setting of the register confirmed in step 1, specify the data type confirmed in step 2, and save it. 5. Restart the relevant component. |
REGISTER_ADDRESS_SIZE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect number of contiguous regions Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | The number of contiguous regions different from the configuration on the PLC side has been entered for the "Num array" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Check the PLC configuration for the number of contiguous regions confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Num array" setting of the register confirmed in step 1, enter the number of contiguous regions confirmed in step 2, and save it. 5. Restart the relevant component. |
REGISTER_READ_ERROR#
| Item | Description |
|---|---|
| Message | Register acquisition error Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Protocol error number |
| Content | Failed to get the register. |
| Action | 1. Confirm the register name, register address, and protocol error number included in the message. 2. Check the communication specifications manual of the device to see if a workaround is available for the protocol error number confirmed in step 1. 3. (If a workaround is available) Implement the workaround. (If no workaround is available, or if you are not familiar with the workaround instructions) Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
GROUP_REGISTER_READ_ERROR#
| Item | Description |
|---|---|
| Message | Register batch acquisition error Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Protocol error number |
| Content | Failed in register batch acquisition. |
| Action | 1. Confirm the register name, register address, and protocol error number included in the message. 2. Check the communication specifications manual of the device to see if a workaround is available for the protocol error number confirmed in step 1. 3. (If a workaround is available) Implement the workaround. (If no workaround is available, or if you are not familiar with the workaround instructions) Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
Modbus Collector#
CONNECTION_REFUSED#
| Item | Description |
|---|---|
| Message | Disconnected |
| Content | The device has been disconnected. |
| Action | (Action 1) Restart the component. (Action 2) 1. Check the configuration on the device side for the host and port capable of communication. 2. Open the configuration screen of the relevant component. 3. For the "Host" and "Port" settings, enter the host and port confirmed in step 1, and save them. 4. Restart the relevant component. |
NETWORK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Timeout Note: This message includes the following information. ▪ Address ▪ Port number ▪ Setting timeout value ▪ Operation type |
| Content | (When the operation type is connect or close) Failed to connect to the device within the time specified for the "Connect timeout" setting. (When the operation type is receive or send) Failed to receive data from the device within the time specified for the "Read timeout" setting. |
| Action | 1. Confirm the operation type included in the message. 2. Open the configuration screen of the relevant component. 3. (When the operation type confirmed in step 1 is connect or close) Increase the "Connect timeout" setting. (When the operation type confirmed in step 1 is receive or send) Increase the "Read timeout" setting. 4. Restart the relevant component. |
SERIAL_CONNECTION_REFUSED#
| Item | Description |
|---|---|
| Message | Disconnected (Serial Communication) |
| Content | The device has been disconnected. |
| Action | (Action 1) Restart the component. (Action 2) 1. Check the device settings for the correct "Device", "Baud rate", "Communication protocol", "Data bits", "Stop bits", and "Parity bits". 2. Open the configuration screen of the relevant component. 3. Enter and save the values confirmed in step 1 for the "Device", "Baud rate", "Communication protocol", "Data bits", "Stop bits", and "Parity bits" settings. 4. Restart the relevant component. |
SERIAL_NETWORK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Timeout (Serial Communication) Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Configured timeout value ▪ Operation type |
| Content | Failed to receive data from the device within the time specified for the "Read timeout" setting. |
| Action | 1. Open the configuration screen of the relevant component. 2. Increase the "Read timeout" setting. 3. Restart the relevant component. |
SERIAL_NETWORK_ACCESS_ERROR#
| Item | Description |
|---|---|
| Message | Communication error Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Error number ▪ Operation type |
| Content | (When the operation type is connect) Failed to connect to the device. (When the operation type is receive or send) Failed to send or receive data to/from the device. |
| Action | 1. Confirm the operation type included in the message. (If the operation type confirmed in step 1 is connect) 2. Open the configuration screen of the relevant component. 3. Check the device settings for the correct "Device", "Baud rate", "Communication protocol", "Data bits", "Stop bits", and "Parity bits", and enter and save the confirmed settings. 4. Restart the relevant component. (If the operation type confirmed in step 1 is receive or send) 2. Check for any connection issues with the device. |
SERIAL_LOCK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Connection exclusive control timeout (Serial Communication) Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Configured timeout value ▪ Operation type |
| Content | Could not connect to the device within the time specified for the "Connect timeout" setting because another component using the same device is currently connected. |
| Action | 1. Open the configuration screen of the relevant component. 2. Increase the value of the "Connect timeout" setting. 3. Restart the relevant component. |
REGISTER_ADDRESS_ERROR#
| Item | Description |
|---|---|
| Message | Specified register is invalid Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A register address not supporting bit specification has been entered in the "Address" setting with bit specification. |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Address" setting of the register confirmed in step 1, enter the register address that supports bit specification, and save it. 4. Restart the relevant component. |
REGISTER_ADDRESS_RANGE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect register address Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A register address that cannot be handled by the device protocol has been entered for the "Address" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Address" setting of the register confirmed in step 1, enter the register address that can be handled by the device protocol, and save it. 4. Restart the relevant component. Note: Refer to the manual of the relevant device and others for usable addresses and their range. |
REGISTER_ADDRESS_DATA_TYPE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect data type Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A data type different from the configuration on the device side has been specified for the "Data type" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Check the configuration on the device side for the data type of the register confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Data type" setting of the register confirmed in step 1, specify the data type confirmed in step 2, and save it. 5. Restart the relevant component. |
REGISTER_ADDRESS_SIZE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect number of contiguous regions Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | The number of contiguous regions different from the configuration on the device side has been entered for the "Num array" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Check the configuration on the device side for the number of contiguous regions confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Num array" setting of the register confirmed in step 1, enter the number of contiguous regions confirmed in step 2, and save it. 5. Restart the relevant component. |
REGISTER_READ_ERROR#
| Item | Description |
|---|---|
| Message | Register acquisition error Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Protocol error number |
| Content | Failed to get the register. |
| Action | 1. Confirm the register name, register address, and protocol error number included in the message. 2. Check the communication specifications manual of the device to see if a workaround is available for the protocol error number confirmed in step 1. 3. (If a workaround is available) Implement the workaround. (If no workaround is available, or if you are not familiar with the workaround instructions) Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
GROUP_REGISTER_READ_ERROR#
| Item | Description |
|---|---|
| Message | Register batch acquisition error Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Protocol error number |
| Content | Failed in register batch acquisition. |
| Action | 1. Confirm the register name, register address, and protocol error number included in the message. 2. Check the communication specifications manual of the device to see if a workaround is available for the protocol error number confirmed in step 1. 3. (If a workaround is available) Implement the workaround. (If no workaround is available, or if you are not familiar with the workaround instructions) Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
EtherNet/IP Collector#
TYPE_MISMATCH#
| Item | Description |
|---|---|
| Message | Type mismatch Note: This message includes the following information. ▪ Tag name ▪ Setting type ▪ Read type |
| Content | A data type different from the configuration on the device side has been specified for the "Data type" setting. |
| Action | 1. Confirm the tag name, the setting type, and the read type included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Data type" setting of the tag confirmed in step 1, specify the read tag type confirmed in step 1, and save it. 4. Restart the relevant component. |
UNKNOWN_TAG#
| Item | Description |
|---|---|
| Message | Specified tag unreadable Note: This message includes the following information. ▪ Tag name |
| Content | Data for the specified tag is unavailable. Note: This error occurs when the "Setting option" setting is "Variable". |
| Action | 1. Confirm the tag name included in the message. 2. Check the configuration on the device side for the correct tag name. 3. Open the configuration screen of the relevant component. 4. For the "Variable name" setting of the tag confirmed in step 1, enter the tag name confirmed in step 2, and save it. 5. Restart the relevant component. |
CIP_SETTING_ERROR#
| Item | Description |
|---|---|
| Message | CIP object setting error Note: This message includes the following information. ▪ Class ID ▪ Instance ID ▪ Attribute ID |
| Content | Data for the specified CIP object unavailable. Note: This error occurs when the "Setting option" setting is "CIP object". |
| Action | 1. Confirm the class ID, instance ID, and attribute ID included in the message. 2. Check the configuration on the device side for the correct class ID, instance ID, and attribute ID. 3. Open the configuration screen of the relevant component. 4. For the "Class ID", "Instance ID", and "Attribute ID" settings of the CIP object confirmed in step 1, enter the information confirmed in step 2, and save them. 5. Restart the relevant component. Note: Refer to the manual of the relevant device and others for accessible CIP objects. |
ARRAYSIZE_MISMATCH#
| Item | Description |
|---|---|
| Message | Array size error Note: This message includes the following information. ▪ Column name |
| Content | The received data array size is less than the number of arrays specified for the "Array size" setting. |
| Action | 1. Confirm the column name included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Array size" setting of the column confirmed in step 1, enter a smaller number, and save it. 4. Restart the relevant component. |
READ_TIME_OVER#
| Item | Description |
|---|---|
| Message | Read time over Note: This message includes the following information. ▪ Time taken to load |
| Content | Reading data is taking longer than the interval specified for the "Get Interval" setting. |
| Action | 1. Confirm the time taken to read data included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Get Interval" setting, enter a time longer than the time confirmed in step 1, and save it. 4. Restart the relevant component. |
Compute Collector#
EXPRESSION_FORMAT_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect formatting of formulas Note: This message includes the following information. ▪ Output name |
| Content | An expression in an incorrect format has been entered in the "Expression" setting. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
SOME_VARIABLE_NOT_SPECIFIED#
| Item | Description |
|---|---|
| Message | Some variables in the formula are not specified Note: This message includes the following information. ▪ Output name ▪ Variable name |
| Content | The "Expression" setting contains undefined variables. |
| Action | (Workaround 1) 1. Confirm the output name and variable name included in the message. 2. Open the configuration screen of the relevant component. 3. Add input data whose setting "Variable name" is the same as the variable name confirmed in step 1. 4. For the "Trigger variable" setting of the output data confirmed in step 1, specify the variable added in step 3, and save it. 5. Restart the relevant component. (Workaround 2) 1. Confirm the output name and variable name included in the message. 2. Open the configuration screen of the relevant component. 3. From the "Expression" setting of the output data confirmed in step 1, remove the variable confirmed in step 1, and save it. 4. Restart the relevant component. |
NO_TRIGGER_SPECIFIED#
| Item | Description |
|---|---|
| Message | No trigger is set on any of the variables Note: This message includes the following information. ▪ Output name |
| Content | The "Trigger variable" setting has no variable entries. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
EVALUATION_ERROR#
| Item | Description |
|---|---|
| Message | Formula Evaluation Error Note: This message includes the following information. ▪ Output name ▪ Error status |
| Content | Failed to evaluate the "Expression" setting. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
NO_VARIABLE_SPECIFIED#
| Item | Description |
|---|---|
| Message | Not a single variable is specified in the formula. Note: This message includes the following information. ▪ Output name |
| Content | The "Expression" setting does not contain the variable specified in the "Trigger variable" setting. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
COMPUTE_ERROR#
| Item | Description |
|---|---|
| Message | Error in arithmetic operation Note: This message includes the following information. ▪ Output name |
| Content | An error occurred during execution of the "Expression" setting. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
OUTCOLUMN_CREATE_ERROR#
| Item | Description |
|---|---|
| Message | Failed to create output column Note: This message includes the following information. ▪ Output name |
| Content | Failed to generate an output column for registering the execution result of the "Expression" setting. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
OUTCOLUMN_INSERT_ERROR#
| Item | Description |
|---|---|
| Message | Failed to register data in output column Note: This message includes the following information. ▪ Output name |
| Content | Failed to register the execution result of the "Expression" setting in the output column. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
VARIABLE_NOT_UNIQUE_ERROR#
| Item | Description |
|---|---|
| Message | Variable settings are duplicated and variable names cannot be identified Note: This message includes the following information. ▪ Component name ▪ Data name ▪ Statistics type |
| Content | The "Input Data" setting contains variables with duplicated definitions. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
MQTT Collector#
AUTHENTICATION_FAILURE#
| Item | Description |
|---|---|
| Message | Authentication error |
| Content | Failed in authentication to MQTT Broker. |
| Action | (When turning OFF the "Anonymous access" setting) 1. Check the configuration on the MQTT Broker side for the correct user information (user name and password). 2. Open the configuration screen of the relevant component. 3. Set the "Anonymous access" setting to OFF. 4. For the "User name" and "Password" settings, enter the user name and password confirmed in step 1, and save them. 5. Restart the relevant component. (When turning ON the "Anonymous access" setting) 1. Check the configuration on the MQTT Broker side to make sure that anonymous access is allowed. 2. Open the configuration screen of the relevant component. 3. Set the "Anonymous access" setting to ON, and save it. 4. Restart the relevant component. |
MESSAGE_PARSE_ERROR#
| Item | Description |
|---|---|
| Message | Incoming message parsing error |
| Content | Data in a different format than expected was received. |
| Action | Configure the setting on the publishing device side to send data in the following format. { 'records' : [{ 'timestamp': 'Timestamp (ISO 8601 format)' }, { 'Data name': 'Value' }]} Note 1: Define data as an array in JSON format for the records key. Note 2: The array should contain {'data name': 'Value' } as a data definition. Note 3: The Timestamp setting is optional. If setting it, use {'timestamp': 'Timestamp (ISO 8601 format)' } to define the timestamp. If not set, timestamp is automatically assigned. In this event, the system time of the machine running SpeeDBee Synapse is used. |
UNSUPPORTED_DATA_TYPE#
| Item | Description |
|---|---|
| Message | Unsupported data type |
| Content | The data received contained a value of a type that the MQTT collector does not support. |
| Action | Configure the setting on the publishing device side to send data of the following types. ▪ Integer value ▪ Decimal value ▪ Character ▪ True/false value |
TIMESTAMP_ERROR#
| Item | Description |
|---|---|
| Message | Timestamp error Note: This message includes the following information. ▪ Last registration time ▪ Error registration time |
| Content | The currently received data timestamp is older than the previously received data timestamp. |
| Action | 1. Confirm the last registration time included in the message. 2. Configure the setting on the publishing device side to send data with a timestamp that is newer than the last registration time confirmed in step 1. |
TIMESTAMP_RANGE_ERROR#
| Item | Description |
|---|---|
| Message | Timestamp tolerance error Note: This message includes the following information. ▪ Timestamp ▪ Minimum time allowed ▪ Maximum time allowed included |
| Content | The difference between the timestamp defined in the received data and the actual timestamp is larger than the value set in the "Timestamp error tolerance" setting. |
| Action | (Action 1) Configure the setting on the publishing device side to send data including no timestamp. (Action 2) 1. Open the configuration screen of the relevant component. 2. Check the "Timestamp error tolerance" setting. 3. Configure the setting on the publishing device side to send data that has a timestamp within the tolerance confirmed in step 2. (Action 3) 1. Open the configuration screen of the relevant component. 2. For the "Timestamp error tolerance" setting, enter a larger value, and save it. 3. Restart the relevant component. |
TIMESTAMP_PARSE_ERROR#
| Item | Description |
|---|---|
| Message | Timestamp parse error |
| Content | The timestamp defined in the received data was not in the expected format. |
| Action | Configure the setting on the publishing device side to send data that has a timestamp in ISO 8601 format. |
| Remarks | An example of a timestamp in ISO 8601 format is: 2023-10-30T10:00:00.012345678Z |
RECEIVED_PARAMETER_ERROR#
| Item | Description |
|---|---|
| Message | Received data error Note: This message includes the following information. ▪ Column name (or key name) ▪ Error cause |
| Content | There was a problem with a parameter defined in the received data. The types of error causes are as follows. ▪ data_type: Different in the type of the created column and the received data ▪ array_size: Different in the array size of the created column and the received data ▪ value: Value of the received data outside the range of the column type ▪ key_name: Keys not usable as column names when the "Dynamic column" setting is ON and the collector generates a column based on the received JSON data (e.g., incorrect character, exceeded maximum number of characters) |
| Action | (When the cause of the error is data_ type) 1. Confirm the column name included in the message. 2. Check the configuration on the publishing device side for the column data type confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Data type" setting of the column confirmed in step 1, specify the data type confirmed in step 2, and save it. 5. Restart the relevant component. (When the cause of the error is array_size) 1. Confirm the column name included in the message. 2. Check the configuration on the publishing device side for the array size of the column confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Number of data" setting of the column confirmed in step 1, specify the array size confirmed in step 2, and save it. 5. Restart the relevant component. (When the cause of the error is value) 1. Confirm the column name included in the message. 2. Configure the setting on the publishing device side so that the value of the data confirmed in step 1 falls within the range of the data type. (When the cause of the error is key_name) 1. Confirm the key name included in the message. 2. Open the configuration screen of the relevant component. 3. Check the names that can be entered for the "Data name" setting. 4. Configure the setting on the publishing device side to change the column name confirmed in step 1 to the name confirmed in step 3. |
CA_FILE_ERROR#
| Item | Description |
|---|---|
| Message | Certificate file error |
| Content | The certificate uploaded to the "CA certificate" setting is invalid. |
| Action | 1. Obtain the correct CA certificate in the MQTT Broker settings. 2. Open the configuration screen of the relevant component. 3. Upload the certificate gotten in step 1 to the "CA certificate" setting, and save it. 4. Restart the relevant component. |
MQTT Emitter#
AUTHENTICATION_FAILURE#
| Item | Description |
|---|---|
| Message | Authentication error |
| Content | Failed in authentication to MQTT Broker. |
| Action | (When turning OFF the "Anonymous access" setting) 1. Check the configuration on the MQTT Broker side for the correct user information (user name and password). 2. Open the configuration screen of the relevant component. 3. Set the "Anonymous access" setting to OFF. 4. For the "User name" and "Password" settings, enter the user name and password confirmed in step 1, and save them. 5. Restart the relevant component. (When turning ON the "Anonymous access" setting) 1. Check the configuration on the MQTT Broker side to make sure that anonymous access is allowed. 2. Open the configuration screen of the relevant component. 3. Set the "Anonymous access" setting to ON, and save it. 4. Restart the relevant component. |
UNSUPPORTED_DATA_TYPE#
| Item | Description |
|---|---|
| Message | Unsupported data type |
| Content | Some of the data to be sent is of an unsupported data type. |
| Action | 1. Right-click the IN Port of the relevant component. 2. Specify "Receive and set data definitions" for the "Setting option" setting, and check the data list. 3. In the data list, check the data type that the MQTT Emitter does not support. 4. Take one of the following actions on the component sending the data confirmed in step 3. ▪ Delete the flowlink ▪ Configure the flowlink filter function to prevent the data confirmed in step 3 from passing ▪ Stop or remove the component ▪ Configure the component not to send the data confirmed in step 3 |
| Remarks | The MQTT Emitter supports the following data types. ・BOOLEAN ・INT8 ・INT16 ・INT32 ・INT64 ・UINT8 ・UINT16 ・UINT32 ・UINT64 ・FLOAT ・DOUBLE ・STRING ・BINARY ・FILE |
PUBLISH_ERROR#
| Item | Description |
|---|---|
| Message | Publish error |
| Content | Failed to send data. |
| Action | (Workaround 1) Make sure that the machine running SpeeDBee Synapse is connected to the network. (Workaround 2) 1. Check the configuration on the MQTT Broker side for the host and port capable of communication. 2. Open the configuration screen of the relevant component. 3. For the "Host" and "Port" settings, enter the host and port confirmed in step 1, and save them. 4. Restart the relevant component. (Workaround 3) Consult your System Administrator and make sure that the configuration on the MQTT Broker side is correct. |
File Emitter#
UNSUPPORTED_DATA_TYPE#
| Item | Description |
|---|---|
| Message | Unsupported data type |
| Content | Some of the data to be sent is of an unsupported data type. |
| Action | 1. Check the IN Port of the relevant component. 2. If it is connected with a flowlink to a component other than the following ones, delete the flowlink. ▪ CSV Serializer ▪ JSON Serializer |
Cloud Emitter for AWS#
AUTHENTICATION_FAILURE#
| Item | Description |
|---|---|
| Message | Authentication error |
| Content | Failed in authentication to AWS IoT Core. |
| Action | 1. Check the AWS IoT Core configuration for the correct host port, and obtain the correct CA certificate, SSL certificate, and private key. 2. Open the configuration screen of the relevant component. 3. Enter the information confirmed in step 1 for the following settings, and upload and save the obtained file. ▪ Host ▪ Port ▪ CA certificate ▪ SSL certificate ▪ Private key 4. Restart the relevant component. |
PUBLISH_ERROR#
| Item | Description |
|---|---|
| Message | Publish error |
| Content | Failed to send data to AWS IoT Core. |
| Action | (Workaround 1) Make sure that the machine running SpeeDBee Synapse is connected to the network. (Workaround 2) 1. Check the AWS IoT Core configuration for the correct host port, and obtain the correct CA certificate, SSL certificate, and private key. 2. Open the configuration screen of the relevant component. 3. Enter the information confirmed in step 1 for the following settings, and upload and save the obtained file. ▪ Host ▪ Port ▪ CA certificate ▪ SSL certificate ▪ Private key 4. Restart the relevant component. (Workaround 3) Consult your System Administrator and make sure that the configuration on the AWS Iot Core side is correct. |
UNSUPPORTED_DATA_TYPE#
| Item | Description |
|---|---|
| Message | Unsupported data type |
| Content | Some of the data to be sent is of an unsupported data type. |
| Action | 1. Check the IN Port of the relevant component. 2. If it is connected with a flowlink to a component other than the following ones, delete the flowlink. ▪ CSV Serializer ▪ JSON Serializer |
Cloud Emitter for Azure#
AUTHENTICATION_FAILURE#
| Item | Description |
|---|---|
| Message | Authentication error |
| Content | Failed in authentication to Azure IoT Hub. |
| Action | 1. Check the configuration on the Azure IoT Hub side for the correct connection string. 2. Open the configuration screen of the relevant component. 3. For the "Connection string" setting, enter the connection string confirmed in step 1, and save it. 4. Restart the relevant component. |
PUBLISH_ERROR#
| Item | Description |
|---|---|
| Message | Publish error |
| Content | Failed to send data. |
| Action | (Workaround 1) Make sure that the machine running SpeeDBee Synapse is connected to the network. (Workaround 2) 1. Check the configuration on the Azure IoT Hub side for the correct connection string. 2. Open the configuration screen of the relevant component. 3. For the "Connection string" setting, enter the connection string confirmed in step 1, and save it. 4. Restart the relevant component. (Workaround 3) Consult your System Administrator and make sure that the configuration on the Azure IoT Hub side is correct. |
UNSUPPORTED_DATA_TYPE#
| Item | Description |
|---|---|
| Message | Unsupported data type |
| Content | Some of the data to be sent is of an unsupported data type. |
| Action | 1. Check the IN Port of the relevant component. 2. If it is connected with a flowlink to a component other than the following ones, delete the flowlink. ▪ CSV Serializer ▪ JSON Serializer |
FTP/FTPS/SFTP Emitter#
AUTHENTICATION_FAILURE#
| Item | Description |
|---|---|
| Message | Authentication error |
| Content | Failed in authentication to FTP/FTPS/SFTP Server. |
| Action | (When turning OFF the "Anonymous access" setting) 1. Check the configuration on the FTP/FTPS/SFTP Server side for the correct user information (user name and password). 2. Open the configuration screen of the relevant component. 3. Set the "Anonymous access" setting to OFF. 4. For the "User name" and "Password" settings, enter the user name and password confirmed in step 1, and save them. 5. Restart the relevant component. (When turning ON the "Anonymous access" setting) 1. Check the configuration on the FTP/FTPS/SFTP Server side to make sure that anonymous access is allowed. 2. Open the configuration screen of the relevant component. 3. Set the "Anonymous access" setting to ON, and save it. 4. Restart the relevant component. |
SEND_ERROR#
| Item | Description |
|---|---|
| Message | Publish error |
| Content | Failed to send data. |
| Action | (Workaround 1) Make sure that the machine running SpeeDBee Synapse is connected to the network. (Workaround 2) 1. Check the configuration on the FTP/FTPS/SFTP Server side for the hosts and ports capable of communication. 2. Open the configuration screen of the relevant component. 3. For the "Host" and "Port" settings, enter the host and port confirmed in step 1, and save them. 4. Restart the relevant component. (Workaround 3) Consult your System Administrator and make sure that the configuration on the FTP/FTPS/SFTP Server is correct. |
PERMISSION_ERROR#
| Item | Description |
|---|---|
| Message | Directory operation error |
| Content | Failed to perform a directory operation on the FTP/FTPS/SFTP Server. (E.g., permission error) |
| Action | 1. Open the configuration screen of the relevant component. 2. Check the "Output directory" setting for the directory entered. 3. Consult your System Administrator, and on the FTP/FTPS/SFTP Server, grant write permission to the directory confirmed in step 3. |
JSON Serializer#
MAX_SIZE_ERROR#
| Item | Description |
|---|---|
| Message | Max size error |
| Content | Unable to create the file because the file size exceeds the "Max size" setting. |
| Action | 1. Open the configuration screen of the relevant component. 3. For the "Max size" setting, enter a larger value, and save it. 3. Restart the relevant component. |
CSV Serializer#
MAX_SIZE_ERROR#
| Item | Description |
|---|---|
| Message | Max size error |
| Content | Unable to create the file because the file size exceeds the "Max size" setting. |
| Action | 1. Open the configuration screen of the relevant component. 3. For the "Max size" setting, enter a larger value, and save it. 3. Restart the relevant component. |
JSON Deserializer#
JSON_FORMAT_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect formatting of JSON |
| Content | The received file is not in the correct JSON format. |
| Action | Connect the flowlink so that it can receive a file in the correct JSON format. |
ARRAY_VALUES_NOT_SUPPORTED#
| Item | Description |
|---|---|
| Message | Array values are not supported Note: This message includes the following information. Pattern Data name |
| Content | The pattern matched an array values, which is not supported. |
| Action | 1. Confirm the component and data included in the message. 2. Right-click the IN Port of the relevant component. 3. Enter a pattern that does not result in an array value and save it. 4. Restart the relevant component. |
DATA_TYPE_MISMATCH#
| Item | Description |
|---|---|
| Message | Data type mismatch Note: This message includes the following information. Pattern Data name |
| Content | A data type different from the configuration on the result of matching the pattern has been specified for the "Data type" setting. |
| Action | 1. Confirm the component and data included in the message. 2. Right-click the IN Port of the relevant component. 3. Select the data type that matches the match result and save. 4. Restart the relevant component. |
STRING_TRUNCATED#
| Item | Description |
|---|---|
| Message | String truncated Note: This message includes the following information. Pattern Data name |
| Content | The string value matched by the pattern exceeds the maximum size, so the output string is truncated. |
| Action | No special action is required. However, some data is lost. |
| Remarks | The maximum string size is 511 bytes. |
Event Trigger#
IGNORE_INVALID_TIMESTAMP_DETECT#
| Item | Description |
|---|---|
| Message | Event detection ignored due to invalid timestamp data |
| Content | This error indicates that after the detection of a start or end event, another trigger occurred from data with an invalid timestamp, and the detection by that trigger was ignored. An invalid timestamp indicates data with the same timestamp as or earlier than the first encountered timestamp. The event trigger ignores detection from data with these timestamps. |
| Action | Revise the conditional expression that allows start and end events to be satisfied at the same time. This error does not occur if the start and end events occur at different times. |
Shell Command#
COMMAND_EXEC_ERROR#
| Item | Description |
|---|---|
| Message | Command execution error |
| Content | Failed to execute the command entered for the "Command" setting. |
| Action | 1. Open the configuration screen of the relevant component. 2. For the "Command" setting, enter an executable command, and save it. 3. Restart the relevant component. |
PLC Writing#
CONNECTION_REFUSED#
| Item | Description |
|---|---|
| Message | Disconnected |
| Content | The PLC has been disconnected. |
| Action | (Action 1) Restart the component. (Action 2) 1. Check the configuration on the PLC side for the host and port capable of communication. 2. Open the configuration screen of the relevant component. 3. For the "Host" and "Port" settings, enter the host and port confirmed in step 1, and save them. 4. Restart the relevant component. |
NETWORK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Timeout Note: This message includes the following information. ▪ Address ▪ Port number ▪ Setting timeout value ▪ Operation type |
| Content | (When the operation type is connect or close) Failed to connect the PLC within the time specified for the "Connect timeout" setting. (When the operation type is receive or send) Failed to receive data from the PLC within the time specified for the "Read timeout" setting. |
| Action | 1. Confirm the operation type included in the message. 2. Open the configuration screen of the relevant component. 3. (When the operation type confirmed in step 1 is connect or close) Increase the "Connect timeout" setting. (When the operation type confirmed in step 1 is receive or send) Increase the "Read timeout" setting. 4. Restart the relevant component. |
SERIAL_CONNECTION_REFUSED#
| Item | Description |
|---|---|
| Message | Disconnected (Serial Communication) |
| Content | The PLC has been disconnected. |
| Action | (Action 1) Restart the component. (Action 2) 1. Check the PLC settings for the correct "Device", "Baud rate", "Data bit", "Stop bit", and "Parity bit". 2. Open the configuration screen of the relevant component. 3. Enter and save the values confirmed in step 1 for the "Device", "Baud rate", "Data bit", "Stop bit", and "Parity bit" settings. 4. Restart the relevant component. |
SERIAL_NETWORK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Timeout (Serial Communication) Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Configured timeout value ▪ Operation type |
| Content | Failed to receive data from the PLC within the time specified for the "Read timeout" setting. |
| Action | 1. Open the configuration screen of the relevant component. 2. Increase the "Read timeout" setting. 3. Restart the relevant component. |
SERIAL_NETWORK_ACCESS_ERROR#
| Item | Description |
|---|---|
| Message | Communication error Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Error number ▪ Operation type |
| Content | (When the operation type is connect) Failed to connect to the PLC. (When the operation type is receive or send) Failed to send or receive data to/from the PLC. |
| Action | 1. Confirm the operation type included in the message. (If the operation type confirmed in step 1 is connect) 2. Open the configuration screen of the relevant component. 3. Check the PLC settings for the correct "Device", "Baud rate", "Data bit", "Stop bit", and "Parity bit", and enter and save the confirmed settings. 4. Restart the relevant component. (If the operation type confirmed in step 1 is receive or send) 2. Check for any connection issues with the PLC. |
SERIAL_LOCK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Connection exclusive control timeout (Serial Communication) Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Configured timeout value ▪ Operation type |
| Content | Could not connect to the PLC within the time specified for the "Connect timeout" setting because another component using the same device is currently connected. |
| Action | 1. Open the configuration screen of the relevant component. 2. Increase the value of the "Connect timeout" setting. 3. Restart the relevant component. |
REGISTER_ADDRESS_ERROR#
| Item | Description |
|---|---|
| Message | Specified register is invalid Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A register address not supporting bit specification has been entered in the "Address" setting with bit specification. |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Address" setting of the register confirmed in step 1, enter the register address without bit specification, and save it. 4. Restart the relevant component. |
REGISTER_ADDRESS_RANGE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect register address Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A register address that cannot be handled by the PLC protocol has been entered in the "Address" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Address" setting of the register confirmed in step 1, enter the register address that can be handled by the PLC protocol, and save it. 4. Restart the relevant component. Note: Refer to the manual of the relevant device and others for usable addresses and their range. |
REGISTER_ADDRESS_DATA_TYPE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect data type Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A data type different from the configuration on the PLC side has been specified for the "Data type" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Check the PLC configuration for the data type of the register confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Data type" setting of the register confirmed in step 1, specify the data type confirmed in step 2, and save it. 5. Restart the relevant component. |
REGISTER_ADDRESS_SIZE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect number of contiguous regions Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | The number of contiguous regions different from the configuration on the PLC side has been entered for the "Num array" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Check the PLC configuration for the number of contiguous regions confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Num array" setting of the register confirmed in step 1, enter the number of contiguous regions confirmed in step 2, and save it. 5. Restart the relevant component. |
REGISTER_WRITE_FIX_VALUE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect fixed value Note: This message includes the following information. ▪ Register name ▪ Register address |
| Content | The "Write value" setting is invalid. Note: This error occurs when the "Value type" setting is "Fix value." |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. Make sure that the "Write value" setting confirmed in step 1 satisfies the following conditions, and save it. ▪ Write value type matching the "Data type" setting ▪ Number of characters less than or equal to the "Num array" setting, if the write value is a string 5. Restart the relevant component. |
REGISTER_WRITE_NO_VALUE_ERROR#
| Item | Description |
|---|---|
| Message | Register write value acquisition error Note: This message includes the following information. ▪ Register name ▪ Register address |
| Content | Failed to get the data specified for the "Write value" setting. Note: This error occurs when the "Value type" setting is "Component." |
| Action | 1. Confirm the register name and register address included in the message. 2. Click the IN Port of the relevant component, and open the data monitor. 3. Confirm the column in which at least one data item is registered. 4. Open the configuration screen of the relevant component. 5. For the "Write value" setting of the register confirmed in step 1, specify the column confirmed in step 3, and save it. 6. Restart the relevant component. |
REGISTER_WRITE_ERROR#
| Item | Description |
|---|---|
| Message | Register write error Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Protocol error number |
| Content | Failed in write access to the register. |
| Action | 1. Confirm the register name, register address, and protocol error number included in the message. 2. Check the communication specifications manual of the device to see if a workaround is available for the protocol error number confirmed in step 1. 3. (If a workaround is available) Implement the workaround. (If no workaround is available, or if you are not familiar with the workaround instructions) Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
Modbus Writing#
CONNECTION_REFUSED#
| Item | Description |
|---|---|
| Message | Disconnected |
| Content | The device has been disconnected. |
| Action | (Action 1) Restart the component. (Action 2) 1. Check the configuration on the device side for the host and port capable of communication. 2. Open the configuration screen of the relevant component. 3. For the "Host" and "Port" settings, enter the host and port confirmed in step 1, and save them. 4. Restart the relevant component. |
NETWORK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Timeout Note: This message includes the following information. ▪ Address ▪ Port number ▪ Setting timeout value ▪ Operation type |
| Content | (When the operation type is connect or close) Failed to connect to the device within the time specified for the "Connect timeout" setting. (When the operation type is receive or send) Failed to receive data from the device within the time specified for the "Read timeout" setting. |
| Action | 1. Confirm the operation type included in the message. 2. Open the configuration screen of the relevant component. 3. (When the operation type confirmed in step 1 is connect or close) Increase the "Connect timeout" setting. (When the operation type confirmed in step 1 is receive or send) Increase the "Read timeout" setting. 4. Restart the relevant component. |
SERIAL_CONNECTION_REFUSED#
| Item | Description |
|---|---|
| Message | Disconnected (Serial Communication) |
| Content | The device has been disconnected. |
| Action | (Action 1) Restart the component. (Action 2) 1. Check the device settings for the correct "Device", "Baud rate", "Communication protocol", "Data bits", "Stop bits", and "Parity bits". 2. Open the configuration screen of the relevant component. 3. Enter and save the values confirmed in step 1 for the "Device", "Baud rate", "Communication protocol", "Data bits", "Stop bits", and "Parity bits" settings. 4. Restart the relevant component. |
SERIAL_NETWORK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Timeout (Serial Communication) Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Configured timeout value ▪ Operation type |
| Content | Failed to receive data from the device within the time specified for the "Read timeout" setting. |
| Action | 1. Open the configuration screen of the relevant component. 2. Increase the "Read timeout" setting. 3. Restart the relevant component. |
SERIAL_NETWORK_ACCESS_ERROR#
| Item | Description |
|---|---|
| Message | Communication error Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Error number ▪ Operation type |
| Content | (When the operation type is connect) Failed to connect to the device. (When the operation type is receive or send) Failed to send or receive data to/from the device. |
| Action | 1. Confirm the operation type included in the message. (If the operation type confirmed in step 1 is connect) 2. Open the configuration screen of the relevant component. 3. Check the device settings for the correct "Device", "Baud rate", "Communication protocol", "Data bits", "Stop bits", and "Parity bits", and enter and save the confirmed settings. 4. Restart the relevant component. (If the operation type confirmed in step 1 is receive or send) 2. Check for any connection issues with the device. |
SERIAL_LOCK_TIMEOUT#
| Item | Description |
|---|---|
| Message | Connection exclusive control timeout (Serial Communication) Note: This message includes the following information. ▪ Device ▪ Baud rate ▪ Configured timeout value ▪ Operation type |
| Content | Could not connect to the device within the time specified for the "Connect timeout" setting because another component using the same device is currently connected. |
| Action | 1. Open the configuration screen of the relevant component. 2. Increase the value of the "Connect timeout" setting. 3. Restart the relevant component. |
REGISTER_ADDRESS_ERROR#
| Item | Description |
|---|---|
| Message | Specified register is invalid Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A register address not supporting bit specification has been entered in the "Address" setting with bit specification. |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Address" setting of the register confirmed in step 1, enter the register address without bit specification, and save it. 4. Restart the relevant component. |
REGISTER_ADDRESS_RANGE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect register address Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A register address that cannot be handled by the device protocol has been entered for the "Address" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. For the "Address" setting of the register confirmed in step 1, enter the register address that can be handled by the device protocol, and save it. 4. Restart the relevant component. Note: Refer to the manual of the relevant device and others for usable addresses and their range. |
REGISTER_ADDRESS_DATA_TYPE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect data type Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | A data type different from the configuration on the device side has been specified for the "Data type" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Check the configuration on the device side for the data type of the register confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Data type" setting of the register confirmed in step 1, specify the data type confirmed in step 2, and save it. 5. Restart the relevant component. |
REGISTER_ADDRESS_SIZE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect number of contiguous regions Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Operation type |
| Content | The number of contiguous regions different from the configuration on the device side has been entered for the "Num array" setting. |
| Action | 1. Confirm the register name and register address included in the message. 2. Check the configuration on the device side for the number of contiguous regions confirmed in step 1. 3. Open the configuration screen of the relevant component. 4. For the "Num array" setting of the register confirmed in step 1, enter the number of contiguous regions confirmed in step 2, and save it. 5. Restart the relevant component. |
REGISTER_WRITE_FIX_VALUE_ERROR#
| Item | Description |
|---|---|
| Message | Incorrect fixed value Note: This message includes the following information. ▪ Register name ▪ Register address |
| Content | The "Write value" setting is invalid. Note: This error occurs when the "Value type" setting is "Fix value." |
| Action | 1. Confirm the register name and register address included in the message. 2. Open the configuration screen of the relevant component. 3. Make sure that the "Write value" setting confirmed in step 1 satisfies the following conditions, and save it. ▪ Write value type matching the "Data type" setting ▪ Number of characters less than or equal to the "Num array" setting, if the write value is a string 5. Restart the relevant component. |
REGISTER_WRITE_NO_VALUE_ERROR#
| Item | Description |
|---|---|
| Message | Register write value acquisition error Note: This message includes the following information. ▪ Register name ▪ Register address |
| Content | Failed to get the data specified for the "Write value" setting. Note: This error occurs when the "Value type" setting is "Component." |
| Action | 1. Confirm the register name and register address included in the message. 2. Click the IN Port of the relevant component, and open the data monitor. 3. Confirm the column in which at least one data item is registered. 4. Open the configuration screen of the relevant component. 5. For the "Write value" setting of the register confirmed in step 1, specify the column confirmed in step 3, and save it. 6. Restart the relevant component. |
REGISTER_WRITE_ERROR#
| Item | Description |
|---|---|
| Message | Register write error Note: This message includes the following information. ▪ Register name ▪ Register address ▪ Protocol error number |
| Content | Failed in write access to the register. |
| Action | 1. Confirm the register name, register address, and protocol error number included in the message. 2. Check the communication specifications manual of the device to see if a workaround is available for the protocol error number confirmed in step 1. 3. (If a workaround is available) Implement the workaround. (If no workaround is available, or if you are not familiar with the workaround instructions) Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
EtherNet/IP Writing#
WRITE_ERROR#
| Item | Description |
|---|---|
| Message | Write error Note: This message includes the following information. ▪ Error cause ▪ Variable name or class ID ▪ Instance ID ▪ Attribute ID |
| Content | Failed in writing. |
| Action | 1. Confirm the error cause, variable name, class ID, instance ID, and attribute ID included in the message. 2. Check the communication specifications manual of the device to see if a workaround is available for the cause of the error confirmed in step 1. 3. (If a workaround is available) Implement the workaround. (If no workaround is available, or if you are not familiar with the workaround instructions) Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
UNSUPPORTED_FUNCTION_ERROR#
| Item | Description |
|---|---|
| Message | Unsupport function |
| Content | This function is not currently supported. Writing with CIPObject is not supported. |
| Action | 1. Open the configuration screen of the relevant component. 2. Make sure that the "Setting option" setting of the variable satisfies the following condition, and save it. ▪ To be "Variable name" (Writing with "CIPObject" is not supported.) 3. Restart the relevant component. |
FIX_DATA_TYPE_INCOLLECT#
| Item | Description |
|---|---|
| Message | Fixed value write data type mismatch Note: This message includes the following information. ▪ Data type ▪ Write value |
| Content | The fixed write value does not match the destination data type. Note: This error occurs when the "Value type" setting is "Fix value." |
| Action | 1. Confirm the data type and write value included in the message. 2. Open the configuration screen of the relevant component. 3. Make sure that the "Write value" setting of the variable confirmed in step 1 satisfies the following condition, and then save it. ▪ Write value type matching the "Data type" setting 4. Restart the relevant component. |
STRUCT_ERROR#
| Item | Description |
|---|---|
| Message | Specified structure does not exist Note: This message includes the following information. ▪ Variable name |
| Content | The specified structure does not exist. |
| Action | 1. Confirm the variable name included in the message. 2. Open the configuration screen of the relevant component. 3. Make sure that the "Variable name" setting of the variable confirmed in step 1 satisfies the following conditions, and then save it. ▪ Specified variable name is correct ▪ Specified variable is a structure 4. Restart the relevant component. |
Send mail#
SMTP_AUTHENTICATION_ERROR#
| Item | Description |
|---|---|
| Message | SMTP authentication error Note: This message includes the following information. ▪ Username ▪ Password |
| Content | Failed in authentication to SMTP Server. |
| Action | 1. Check the configuration on the SMTP Server side for the correct SMTP user information (user name and password). 2. Open the configuration screen of the relevant component. 3. For the "SMTP user" and "SMTP password" settings, enter the user name and password confirmed in step 1, and save them. 4. Restart the relevant component. |
Core Internal#
DELETE_STORAGE_GROUPS_ERROR#
| Item | Description |
|---|---|
| Message | Past data deletion error |
| Content | Failed to delete old data in the persistent column. A storage error is one of the possible causes. |
| Action | Consult your System Administrator and make confirmation on the storage status and the like. (E.g., possibility of failure) |
DELETE_FILE_TYPE_OLD_DATA_ERROR#
| Item | Description |
|---|---|
| Message | File type column data deletion error |
| Content | Failed to delete old data in the file type column. A storage error is one of the possible causes. (The file type column refers to a file saved by the serializer.) |
| Action | Consult your System Administrator and make confirmation on the storage status and the like. (E.g., possibility of failure) |
ACCESS_FILE_TYPE_DATA_DIR_ERROR#
| Item | Description |
|---|---|
| Message | File type column data deletion error Note: This message includes the following information. ▪ Number of files |
| Content | Failed to delete old data in the file type column because the directory was inaccessible. |
| Action | Consult your System Administrator and make confirmation on the storage status and the like. (E.g., possibility of failure) |
SYNC_COLUMNS_TO_STORAGE_ERROR#
| Item | Description |
|---|---|
| Message | Persistent data write error |
| Content | Failed to write the persisted column to storage. A storage error is one of the possible causes. |
| Action | Consult your System Administrator and make confirmation on the storage status and the like. (E.g., possibility of failure) |
CORE_INTERRUPT#
| Item | Description |
|---|---|
| Message | Detection of abnormal end of previous run Note: This message includes the following information. ▪ Core start time ▪ Final state ▪ Last state transition time |
| Content | Due to a cause such as a power failure of the machine running SpeeDBee Synapse, the core stopped without a graceful termination procedure. |
| Action | Make sure that the components registered in SpeeDBee Synapse operate normally. |
SPEEDBEE_ERROR_ACCESS#
| Item | Description |
|---|---|
| Message | DB access error detected |
| Content | Failed to access the time series database file for SpeeDBee Synapse. |
| Action | (Workaround 1) If this occurs frequently, initialize the database as described in "Server Settings." (Workaround 2) If the error persists even after Workaround 1 is implemented, consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
SPEEDBEE_ERROR_CORRUPT#
| Item | Description |
|---|---|
| Message | DB file corruption detected |
| Content | The time series database file for SpeeDBee Synapse is corrupt. |
| Action | (Workaround 1) If this occurs frequently, initialize the database as described in "Server Settings." (Workaround 2) If the error persists even after Workaround 1 is implemented, consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
SPEEDBEE_ERROR_INTR#
| Item | Description |
|---|---|
| Message | DB power failure detection section |
| Content | Due to a cause such as a power failure of the machine running SpeeDBee Synapse, the time series database operation was interrupted. |
| Action | Make sure that the components registered in SpeeDBee Synapse operate normally. |
SPEEDBEE_ERROR_NO_REPORTS#
| Item | Description |
|---|---|
| Message | DB missing log acquisition error |
| Content | Failed to obtain the missing detection log of the time series database file for SpeeDBee Synapse. |
| Action | (Workaround 1) If this occurs frequently, initialize the database as described in "Server Settings." (Workaround 2) If the error persists even after Workaround 1 is implemented, consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
DB query service#
PARAMETER_ERROR_IPADDRESS#
| Item | Description |
|---|---|
| Message | IP address setting error |
| Content | The "Address" setting is blank. |
| Action | 1. Open the configuration screen of the relevant component. 2. For the "Address" setting, enter the IP address, and save it. 3. Restart the relevant component. |
PARAMETER_ERROR_PORT_NUMBER#
| Item | Description |
|---|---|
| Message | Port number setting error |
| Content | The "Port" setting is blank. |
| Action | 1. Open the configuration screen of the relevant component. 2. For the "Port" setting, enter the port number, and save it. 3. Restart the relevant component. |
PARAMETER_ERROR_HTTPS_CERTIFICATION#
| Item | Description |
|---|---|
| Message | HTTPS certificate error |
| Content | No HTTPS certificate file has been uploaded to the "SSL/TLS certificate" setting in the "HTTP/HTTPS communication" Setting Menu. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
PARAMETER_ERROR_HTTPS_SECRETKEY#
| Item | Description |
|---|---|
| Message | HTTPS private key error |
| Content | No HTTPS key file has been uploaded to the "Private key" setting in the "HTTP/HTTPS communication" Setting Menu. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
PARAMETER_ERROR_JWS_SETTING#
| Item | Description |
|---|---|
| Message | Enable/disable JWS verification setting error |
| Content | The "Token authentication" setting is unspecified. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
PARAMETER_ERROR_JWS_VERIFICATION#
| Item | Description |
|---|---|
| Message | JWS validation file error |
| Content | The JWS validation file is incomplete. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
DB_QUERY_HTTP_SERVER_START_ERROR#
| Item | Description |
|---|---|
| Message | DB query service startup error |
| Content | Failed to start HTTP Server. |
| Action | 1. Open the configuration screen of the relevant component. 2. Check the "Host" and "Port" settings. 3. Consult your System Administrator and confirm if the host and port checked in step 2 conflicts with other services. |
Error manager#
PARAMETER_ERROR_INTERVAL#
| Item | Description |
|---|---|
| Message | Processing interval setting error |
| Content | The "Processing interval" setting value is incorrect. |
| Action | 1. Open the configuration screen of the relevant component. 2. For the "Processing interval" setting, enter a value in the range of 5 to 180, and save it. 3. Restart the relevant component. |
PARAMETER_ERROR_CORE_PORT#
| Item | Description |
|---|---|
| Message | Core port number setting error |
| Content | The core port number is set to an incorrect value. |
| Action | This error should not normally occur. Consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
NETWORK_TIMEOUT_ERROR#
| Item | Description |
|---|---|
| Message | Communication timeout error |
| Content | Communication timed out. |
| Action | 1. Open the configuration screen of the relevant component. 2. For the "Timeout" setting, enter a larger value, and save it. 3. Restart the relevant component. |
Event data manager#
RESTORE_DB#
| Item | Description |
|---|---|
| Message | Restoring data from backup due to database corruption |
| Content | This is a warning to let you know that during access to the internal database of i-Trigger, corruption was detected and data was restored from a backed-up database. |
| Action | No special action is required. However, some data is lost. |
VIDEO Collector (i-Trigger Extension package)#
READ_FRAME_ERROR#
| Item | Description |
|---|---|
| Message | Failed to load frame |
| Content | Failed to load streaming data received from a network camera. |
| Action | Usually, no special action is required. However, if this error persists, check the following points. 1. Check to see if the connected camera supports i-Trigger. (Reference) 2. Revise the camera settings. Try a lower resolution or lower frame rate. |
MAKE_CONTAINER_ERROR#
| Item | Description |
|---|---|
| Message | Error occurred while creating mp4 |
| Content | An internal error occurred while creating the mp4 file. |
| Action | This error should not normally occur. If the symptom persists, consult your System Administrator, and contact manufacturer following the steps described in Contact manufacturer. |
Event Recorder (i-Trigger Extension package)#
All errors generated by this component are "Component default" errors.