Fault codes

Top  Previous  Next

A fault occurs when the RTCU device is not able to continue because of a severe error either in the VPL program or in some other condition detected by the firmware.

An example is if the VPL application tries to make a divide by zero operation. That will be caught by the firmware, and the device will enter a fault state where the LEDs of the device flash rapidly. The fault code will also be saved in the fault log of the device with timestamp. The fault log can be retrieved by using the Device: Data: Fault Log dialog.

 

It is possible to instruct the firmware to automatically reset the device after a certain time when a fault has occurred by using the boardSetFaultReset() function.

 

 

The table below describes the possible fault codes.

 

Fault code#

Description

-1

Low-level TCP/IP failure.
This fault code is followed by another internal failure code. Please report this fault to Logic IO.

1

Unspecified error.

This should not occur.

2

Not a valid VSX image.

The program image in the device is invalid - probably because of an interruption in the programming of the device.

3

Out of memory.

The program in the device requires more memory than available to execute.

4

Index error.

The program in the device has made an illegal index into an array.

5

Illegal op-code.

Most likely an attempt to use a feature that is not available in the firmware.

6

Illegal string-ID referenced.

Can be caused by misuse of string assignments from multiple threads. See the section on STRING.

7

Dynamic string reference illegal (not owner of string).

8

Dynamic string-allocation failed due to illegal size request.

Most likely the program has attempted to create a STRING larger than 254 characters.

9

Dynamic string allocation failed.

Maximum number/size of the dynamic strings has been exceeded. See also STRING.

10

Reference-decrement on no-reference dynamic string detected.

11

Divide by zero.

A division by zero operation has occurred.

12

Stack overflow.

13

String memory arena has been destroyed.

14

X32 enhanced memory not available.

17

Timers used has exceeded the maximally allowed.

18

The callback function stack was too small.

19

Call is not allowed from a high priority callback function.

20

I/O update is not allowed from a callback function.

128

Flash write error.

The write to Flash has failed - probably because of too many write cycles to either the Flash persistent memory or the data loggger.

129

GSM: Invalid PIN code.

Pin code set from the RTCU IDE or gsmSetPIN() is not correct.

130

GSM: SIM PUK required.

Too many attempts with the wrong PIN code. The PUK code must be entered by using a normal mobile phone.

131

GSM: SIM PIN2 required.

The PUK2 code must be entered by using a normal mobile phone.

132

GSM: SIM PUK2 required.

The PUK2 code must be entered by using a normal mobile phone.

135

Memory allocation error.

The allocated dynamic strings in the program use too much memory, or the allocated CHANNEL data in the program use too much memory.

136

GSM: Missing PIN code.

The SIM card is expecting a PIN code, but no PIN code has been set.

A PIN code can be set either from the RTCU IDE or by using the gsmSetPIN() function.

137

GSM: Module power-off failed.

138

GSM: Low-level recovery reset.

139

GPRS: Recovery boot #1. Permanent problems establishing the cellular connection.

140

GPRS: Recovery boot #2. Permanent problems with establishing the RTCU Communication Hub session.

141

GPRS: Recovery boot #3. Prolonged time to establish connection to the RTCU Communication Hub.

142

Battery charger failed. Charger permanently stopped.

143

User Watchdog timeout. Device resetting.

144

GSM: SIM-card has been reinserted.

145

Drive A: has been repaired due to an unexpected shutdown.

146

Drive B: has been repaired due to an unexpected shutdown.

147

Unsupported SDHC SD-CARD inserted.

148

Generic 1-wire lock timeout.

149

Temperature too high.

151

GPS/GNSS initialization failure.

152

factory.vsx is not found on the project drive.

154

Failed to connect to the RTCU Communication Hub. Switching to fallback configuration.

169

Incompatible firmware.

The firmware programmed into the device is not compatible. Please upgrade to a newer version.

199

Unexpected reset by firmware watchdog.
The device has been reset by the firmware watchdog during upgrade.

200

Unexpected runtime reset.

201

Hardware watchdog timeout. Device resetting.