C-IPC 171
C-DIAS IPC WITH AMD FUSION G-T56N
Page 36
04.11.2019
-
Reload the application into the
control.
47
APPL-SAVE-ERROR
An error has occurred while attempting
to save the application.
50
ACCESS-
EXCEPTION-ERROR
Read or write access of a restricted
memory area. (I.e. writing to the NULL
pointer).
Solution:
-
Correct application errors
51
BOUND EXCEEDED
An exception error has occurred when
accessing arrays. The memory area was
overwritten through accessing an invalid
element.
Solution:
-
Correct application errors
52
PRIVILEDGED
INSTRUCTION
An unauthorized instruction for the
current CPU level was given. For exam-
ple, setting the segment register.
Cause:
-
The application has overwritten
the application program code.
Solution:
-
Correct application errors
53
FLOATING POINT
ERROR
An error has occurred during a floating-
point operation.
60
DIAS-RISC-ERROR
Error from the Intelligent DIAS Master.
Restart; report error to SIGMATEK.
64
INTERNAL ERROR
An internal error has occurred; all appli-
cations are stopped.
Restart; report error to SIGMATEK.
65
FILE ERROR
An error has occurred during a file
operation.
66
DEBUG ASSERTION
FAILED
Internal error.
Restart; report error to SIGMATEK.
67
REALTIME RUNTIME
The total duration of all real-time objects
exceeds the maximum time; the time
cannot be configured.
2 ms for 386 CPUs
1 ms for all other CPUs
Solution:
-
Optimize the application's real-
time task (RtWork).
-
Reduce the clock time for the
real-time task of all objects.
-
Correct application errors
-
CPU is overloaded in real-time
=> use a higher capacity CPU.
68
BACKGROUND
RUNTIME
The total time for all background objects
exceed the maximum time; the time can
be configured using two system varia-
bles:
-BTRuntime: Remaining time
-SWBTRuntime: Preset value for runtime
counter
Solution:
-
Optimize the application's back-
ground task (background)
-
Use higher capacity CPU
-
Set SWBTRuntime correctly
70
C-DIAS ERROR
A connection error with a C-DIAS mod-
ule has occurred.
Cause:
-
The cause of the error is docu-
mented in the log file