« Close

Datasheets and User Guides

App Notes

Software & Driver

 
Table of Contents

5.3 - Errorcodes [U6 Datasheet]

Table 5.3-1. low-level function errorcodes.

Error Code (HEX) Code (DEC)
SCRATCH_WRT_FAIL 0x01 1
SCRATCH_ERASE_FAIL 0x02 2
DATA_BUFFER_OVERFLOW 0x03 3
ADC0_BUFFER_OVERFLOW 0x04 4
FUNCTION_INVALID 0x05 5
SWDT_TIME_INVALID 0x06 6
XBR_CONFIG_ERROR 0x07 7
     
FLASH_WRITE_FAIL 0x10 16
FLASH_ERASE_FAIL 0x11 17
FLASH_JMP_FAIL 0x12 18
FLASH_PSP_TIMEOUT 0x13 19
FLASH_ABORT_RECIEVED 0x14 20
FLASH_PAGE_MISMATCH 0x15 21
FLASH_BLOCK_MISMATCH 0x16 22
FLASH_PAGE_NOT_IN_CODE_AREA 0x17 23
MEM_ILLEGAL_ADDRESS 0x18 24
FLASH_LOCKED 0x19 25
INVALID_BLOCK 0x1A 26
FLASH_ILLEGAL_PAGE 0x1B 27
FLASH_TOO_MANY_BYTES 0x1C 28
FLASH_INVALID_STRING_NUM 0x1D 29
     
SMBUS_INQ_OVERFLOW 0x20 32
SMBUS_OUTQ_UNDERFLOW 0x21 33
SMBUS_CRC_FAILED 0x22 34
     
SHT1x_COMM_TIME_OUT 0x28 40
SHT1x_NO_ACK 0x29 41
SHT1x_CRC_FAILED 0x2A 42
SHT1X_TOO_MANY_W_BYTES 0x2B 43
SHT1X_TOO_MANY_R_BYTES 0x2C 44
SHT1X_INVALID_MODE 0x2D 45
SHT1X_INVALID_LINE 0x2E 46
     
STREAM_IS_ACTIVE 0x30 48
STREAM_TABLE_INVALID 0x31 49
STREAM_CONFIG_INVALID 0x32 50
STREAM_BAD_TRIGGER_SOURCE 0x33 51
STREAM_NOT_RUNNING 0x34 52
STREAM_INVALID_TRIGGER 0x35 53
STREAM_ADC0_BUFFER_OVERFLOW 0x36 54
STREAM_SCAN_OVERLAP 0x37 55
STREAM_SAMPLE_NUM_INVALID 0x38 56
STREAM_BIPOLAR_GAIN_INVALID 0x39 57
STREAM_SCAN_RATE_INVALID 0x3A 58
STREAM_AUTORECOVER_ACTIVE 0x3B 59
STREAM_AUTORECOVER_REPORT 0x3C 60
STREAM_SOFTPWM_ON 0x3D 61
STREAM_INVALID_RESOLUTION 0x3F 63
     
PCA_INVALID_MODE 0x40 64
PCA_QUADRATURE_AB_ERROR 0x41 65
PCA_QUAD_PULSE_SEQUENCE 0x42 66
PCA_BAD_CLOCK_SOURCE 0x43 67
PCA_STREAM_ACTIVE 0x44 68
PCA_PWMSTOP_MODULE_ERROR 0x45 69
PCA_SEQUENCE_ERROR 0x46 70
PCA_LINE_SEQUENCE_ERROR 0x47 71
TMR_SHARING_ERROR 0x48 72
     
EXT_OSC_NOT_STABLE 0x50 80
INVALID_POWER_SETTING 0x51 81
PLL_NOT_LOCKED 0x52 82
     
INVALID_PIN 0x60 96
PIN_CONFIGURED_FOR_ANALOG 0x61 97
PIN_CONFIGURED_FOR_DIGITAL 0x62 98
IOTYPE_SYNCH_ERROR 0x63 99
INVALID_OFFSET 0x64 100
IOTYPE_NOT_VALID 0x65 101
INVALID_CODE 0x66 102
     
UART_TIMEOUT 0x70 112
UART_NOTCONNECTED 0x71 113
UART_NOTENALBED 0x72 114
I2C_BUS_BUSY 0x74 116
TOO_MANY_BYTES 0x76 118
TOO_FEW_BYTES 0x77 119
DSP_PERIOD_DETECTION_ERROR 0x80 128
DSP_SIGNAL_OUT_OF_RANGE 0x81 129
MODBUS_RSP_OVERFLOW 0x90 144
MODBUS_CMD_OVERFLOW 0x91 145

6 comments

Submitted by Matthias (not verified) on Mon, 12/19/2011 - 00:32

Hello, 

I'm getting sporadically Error 105 (Delphi). What does it mean?

regards

 

 

Submitted by LabJack Support (not verified) on Mon, 12/19/2011 - 08:49

What firmware version are you using?

What function is returning the error?

Submitted by Starfire on Sat, 04/16/2016 - 07:31
Starfire's picture

Hello,

I am using the exodriver(version 2.0503f) under GNU/Linux.

When I try to reset the counter 0 using the Feedback()-command, I get an error "XBR_CONFIG_ERROR ". What does this error mean in general?

No stream should be running at the moment, when I get this error. Stream is configured and started after this command.

Two timers are enabled for use in quadrature-encoder-mode. The software is running fine except that command.

As the counter wraps around(forward pulses I get are less than the reverse pulses), I need to reset the counter.

Thanks in advance for your help.

Regards,

Starfire

Submitted by LabJack Support on Mon, 04/18/2016 - 11:37
LabJack Support's picture

XBR_CONFIG_ERROR means crossbar configuration error. In most cases, that error occurs when trying to use a counter or timer that is not enabled. When you enabled the timers, did you enable Counter0 as well? Also, when using a timer clock base with a divisor, Counter0 is unavailable and cannot be enabled. Use Counter1 instead in this case.

Submitted by Starfire on Mon, 04/18/2016 - 23:11
Starfire's picture

Thanks for the fast reply.

Resetting the counter 0 was not the right thing to do in this case. I had to reset the timer 0, because this is counting the quadrature pulses. This worked as expected. Sorry for that. This happens when you work in several projects in parallel and the working day was long.;-)

But now a further question arose: Is it also possible to set the timer to a defined value - let's say to 32768 - when in quadrature mode?

Submitted by LabJack Support on Tue, 04/19/2016 - 12:13
LabJack Support's picture

No, you cannot start the quadrature input timers with a defined value, and the value passed is ignored. For quadrature input functionality, refer to this section of the datasheet:

https://labjack.com/support/datasheets/u6/hardware-description/timers-co...

Copyright © 2001-2099 LabJack Corporation. All rights reserved.