Use the System Error Struct to find the source of an error.
The parameter Code contains the value indicating the error, while the Error tag contains the message. The next table suggests the actions you can take.
Note that in Data Tables, you can select a system error struct to help you log errors.
|
Value |
Module |
Fault |
Symptom |
Action |
|
1 |
MQTT |
Too many MQTT requests. Queue size: 16 |
Related Ladder request will not be applied. |
Check Related Ladder request logic, are there a lot of parallel requests?
|
|
2 |
Load .INI |
Too many Load Config - .ini from SD requests. Queue size: 2 |
Related Ladder request will not be applied.
|
Check Related Ladder request logic, are there a lot of parallel requests?
|
|
3 |
OPC-UA |
Too many OPC UA requests |
Internal
|
Internal
|
|
4 |
SQL |
Too many SQL requests. Queue size: 16 |
Related Ladder request will not be applied. |
Check Related Ladder request logic, are there a lot of parallel requests? |
|
5 |
Ping/DNS |
Too many PING/DNS requests. Queue size: 16 |
Related Ladder request will not be applied. |
Check Related Ladder request logic, are there a lot of parallel requests? |
|
6 |
BufferToFile |
Too many Append Buffer to File requests. Queue size: 16 |
Related Ladder request will not be applied.
|
Check Related Ladder request logic, are there a lot of parallel requests? |
|
7 |
FTP |
Too many FTP Send/ Receive/ Compare requests. Queue size: 16 |
Related Ladder request will not be applied.
Ladder utilities: |
Check Related Ladder request logic, are there a lot of parallel requests? |
|
8 |
Serial |
Too many COM Tx/Rx Serial requests. Queue size: 16 |
Related Ladder request will not be applied.
|
Check Related Ladder request logic, are there a lot of parallel requests? |
|
9 |
Modem/SMS |
Too many Init Modem/ Send SMS requests. Queue size: 16 |
Related Ladder request will not be applied. |
Check Related Ladder request logic, are there a lot of parallel requests? |
|
10 |
|
Too many Send Email requests. Queue size: 16 |
Related Ladder request will not be applied.
|
Check Related Ladder request logic, are there a lot of parallel requests? |
|
11 |
Sampler |
Too many Data Sampler requests. 64 messages |
Sampler will not run: Data Sampler events: Log SAMPLE, START, STOP, PAUSE. |
Check Related Ladder request logic, are there a lot of parallel requests? |
|
12 |
Inner Data Blocks |
RC’s TFTP queue is full |
Modules using TFTP (Data Tables, SQL...) may not work as expected. |
Nothing. If this continues to happen send logs to Unitronics |
|
13 |
Resolution |
Resolution changed unexpectedly |
Default resolution (800x480) will be applied and not the configured one. |
Reboot If this continues to happen send logs to Unitronics |
|
14 |
Sync to Cloud |
Too many Sync to Cloud Ladder requests |
Related Ladder request will not be applied. |
Check Related Ladder request logic, are there a lot of parallel requests? |
|
15 |
REST |
Too many REST Ladder requests. Queue size: 16 |
Rest-Related Ladder requests will not be applied.
|
User should: Check Related Ladder request logic. Are there a lot of parallel requests?
|
|
17 |
Process crash and recover |
The {PROCESS} module experienced an unexpected event but has recovered |
{PROCESS} module will be reset (certain structs data) |
Nothing. If this continues to happen send logs to Unitronics |
|
18 |
Alarms |
The rate at which Alarms occur is more than what the system can register |
Memory overload (will cause panel processes to crash). Alarm module will not work properly (Alarms data will be missed). |
Check Alarm logic. Decrease the rate of alarms triggers.
|
|
19 |
WAL DB FILE SIZE |
WAL DB file size exceeds 4.5MB |
|
|
|
20 |
HMI SOFT RESET |
HMI unexpected event - Refresh |
Screen will reset without any refresh screen |
If this continues to happen send logs to Unitronics |
|
21 |
HMI HARD RESET |
HMI unexpected event - Reset |
HMI module will be reset (refresh screen before) |
If this continues to happen send logs to Unitronics |
|
23 |
SD/USB |
SD is worn out |
Unexpected behavior on SD related modules (DT will not save, Trends will not respond...) |
User should Format/Replace the SD (can try to read content from PC before. Verify the SD quality (Ex. type 10) |
|
25 |
Internal SD |
Only to internal log (in external SD) |
Some features may not work, slow response time to certain operations. |
Contact Support |
|
26 |
Task Server |
Too many certain operations triggered by Ladder requests. Queue size: 50
|
CsvSampleTask CsvDTTask SyncTask FileOperationTask CsvToUdtfTask UdtfCountTask ResetMouseTask ResetKeyboardTask ImportApplicationTask SetTimeDateTask GetLineFromFileTask |
|
|
27 |
Flash more than 90% |
Flash more than 90%
|
Some features may not work |
Contact Support |
|
28 |
Alarms |
Alarm History widget cannot load history, DB corrupted |
Alarm History widget cannot load history, DB corrupted
|
Contact support |
|
29 |
HW watchdog |
CPU HW watchdog expired |
CPU will stop working |
Reset and extract logs |
|
30 |
SD/USB |
Too many files on SD card |
Unexpected behavior on SD/USB related modules (DT will not save, Trends will not respond...) |
Use SD management to reduce the number of files on SD |
|
31 |
OCPP |
Too many TASK_SERVER requests. Queue size: 16 |
Related File operations Ladder request will not be applied. |
Check Related Ladder request logic, are there a lot of parallel requests? |
|
32 |
Burn CPU IOs failed |
RC failed to burn IOs on startup due to IO upgrade part |
HMI will start as expected, but will skip IO upgrade part |
Contact support |
|
33 |
RC packets level is low |
The number of available packets in RC is low |
Some features may not work, slow response time to certain operations. |
Contact Support |
|
34 |
DIGITAL_SIGNATURE |
Failed to create a digital signature to a file |
File was not signed |
Try to sign the file again |
|
35 |
SD/USB |
SD is almost full |
If you ignore the message, and the SD is filled, SD-related modules may not function correctly (DT will not save, Trends will not respond...) |
Use: |
|
36 |
SD/USB |
SD is locked or Read only |
Unexpected behavior on SD related modules (DT will not save, Trends will not respond...) |
- Format/Replace the SD (can try to read content from PC before. |
|
37 |
Rapid CPU Inner Events |
RC logs, indicates RC user/System problem |
CPU task (CANbus, I/O) malfunctions |
Reset and extract logs – may be due to Ladder logic |
|
38 |
SD/USB |
USB is almost full |
If you ignore the message, and the USB is filled, USB-related modules may not function correctly (DT will not save, Trends will not respond...) |
Use: |
|
39 |
SD/USB |
USB is locked or Read only |
Unexpected behavior on USB related modules (DT will not save, Trends will not respond...) |
- Format/Replace the USB (can try to read content from PC before. |
|
40 |
SD/USB |
USB is worn out |
Unexpected behavior on USB related modules (DT will not save, Trends will not respond...) |
User should Format/Replace the USB (can try to read content from PC before. Verify the SD quality (Ex. type 10) |
|
41 |
PLC Clock |
PLC Clock is not automatically set |
Clock does not sync automatically |
Nothing. If this continues to happen send logs to Unitronics |
|
1000 |
Ethernet |
UDP packet of unexpected size (too long) |
Incoming traffic in dropped. Network disturbance in different modules that rely on ethernet |
Extract logs and send to support |
|
1001 |
Ethernet |
TCP packet of unexpected size (too long) |
Incoming traffic in dropped. Network disturbance in different modules that rely on ethernet |
Extract logs and send to support |