Microtronics myDatalogEASY IoTmini User Manual page 162

Log entry
Code Plain text
3000 SCRIPT_ERR
3001 AMX_ERR_EXIT
3002 AMX_ERR_
ASSERT
3003 AMX_ERR_
STACKERR
3004 AMX_ERR_
BOUNDS
3005 AMX_ERR_
MEMACCESS
162
Parameter
Code Plain text
0 NO SCRIPT
1 SCRIPT UPDATE
2 SCRIPT EXCEPT
LOOP
3 SCRIPT SOFT
ERROR 1
4 SCRIPT SOFT
ERROR 2
5 SCRIPT SOFT
ERROR 3
6 SCRIPT UPDATE
ERROR
## ---
## ---
## ---
## ---
## ---
Description
No valid Device Logic available
New Device Logic received
Exception loop detected (4 system starts due to
exception within 10 min.)
The Device Logic is deactivated and error
handling is activated (see "Error handling" on
page 32). The file system is also reformatted.
This means that all of the data and log entries
recorded to date are deleted. This is indicated by
the additional "LOG REFORMATFILE" log entry.
First time a runtime error has occurred within
24 hours. Device Logic was restarted.
Second time a runtime error has occurred within
24 hours. Device Logic was restarted.
Third time a runtime error has occurred within
24 hours. Device Logic was restarted.
The Device Logic is deactivated and error
handling is activated if another runtime error
should occur within 24 hours (see "Error
handling" on page 32).
Connection abort during the Device Logic
download
As the existing Device Logic is located in the
RAM, it can continue to be executed until the
next PowerOn. It can no longer be executed
following a PowerOn and the "SCRIPT_ERR,
NO SCRIPT" error is entered in the device log.
Abortion
e.g. max. number of PAWN commands
(100,000) per run reached
Assertion failed
Stack/heap collision (insufficient stack size)
Array index outside the valid range
Invalid memory access
e.g. mix-up between cell (32-bit element) access
[] and byte access {}
Rev. 01