MaintenanceCenter:Error code

From OROS Wiki
Jump to navigation Jump to search


Any error message:

Flash the server by running the "UpdateHardware.bat" program with the hardware in the maintenance mode.

It is the first thing to do when any OR3x hardware is showing an error during the boot.


OR3XTW

// IDS des messages d'erreur de boot du hardware
#define IDS_BASE_BOOT_ERR0x60000000
#define IDS_BOOT_LOADCONFIG0x60000101
#define IDS_BOOT_ILLEGALCONFIG0x60000102
#define IDS_BOOT_FPGAINPUT0x60000103
#define IDS_BOOT_FGPAOUTPUT0x60000104
#define IDS_BOOT_FGPATRIGGER0x60000105
#define IDS_BOOT_FGPAMULTILEXEUR0x60000106
#define IDS_BOOT_BOARDINPUT0x60000107
#define IDS_BOOT_BOARDOUTPUT0x60000108
#define IDS_BOOT_NB_PASS_TEST0x60000110
#define IDS_BOOT_DSP_MASTER0x60000200
#define IDS_BOOT_DSP_CALCUL10x60000201
#define IDS_BOOT_DSP_CALCUL20x60000202
#define IDS_BOOT_DSP_CALCUL30x60000203
#define IDS_BOOT_DSP_CALCUL40x60000204
#define IDS_BOOT_DSP_CALCUL50x60000205
#define IDS_BOOT_DSP_CALCUL60x60000206
#define IDS_BOOT_DSP_CALCUL70x60000207
#define IDS_BOOT_DSP_CALCUL80x60000208
#define IDS_BOOT_DSP_DISK0x60000209
#define IDS_BOOT_LOAD_DSP_MASTER0x60000210
#define IDS_BOOT_LOAD_DSP_CALCUL10x60000211
#define IDS_BOOT_LOAD_DSP_CALCUL20x60000212
#define IDS_BOOT_LOAD_DSP_CALCUL30x60000213
#define IDS_BOOT_LOAD_DSP_CALCUL40x60000214
#define IDS_BOOT_LOAD_DSP_CALCUL50x60000215
#define IDS_BOOT_LOAD_DSP_CALCUL60x60000216
#define IDS_BOOT_LOAD_DSP_CALCUL70x60000217
#define IDS_BOOT_LOAD_DSP_CALCUL80x60000218
#define IDS_BOOT_LOAD_DSP_DISK0x60000219
#define IDS_BOOT_ERR_LOADCONFIG0x60000300
#define IDS_BOOT_ERR_ILLEGALCONFG0x60000301
#define IDS_BOOT_ERR_LOAD_MASTER0x60000302
#define IDS_BOOT_ERR_LOAD_DISK0x60000303
#define IDS_BOOT_ERR_LOAD_CALCUL0x60000304
#define IDS_BOOT_ERR_LOAD_SERVEUR0x60000305
#define IDS_BOOT_SRV_MIN0x61000000

#define ERR_LOAD_HARD_CONFIG0x101
#define ERR_ILLEGAL_CONFIG0x102
#define ERR_FPGA_INPUT 0x103
#define ERR_FPGA_AUX_AND_OUTPUT0x104
#define ERR_FPGA_TRIGGER 0x105
#define ERR_FPGA_MULTIPLEXEUR0x106
#define ERR_BOARD_NB_INPUT 0x107
#define ERR_BOARD_NB_AUX_AND_OUTPUT 0x108
#define ERR_BOARD_NB_TRIGGER 0x109
#define ERR_PASS_ERROR 0x110
#define ERR_BOARD_INPUT_TYPE 0x111
#define ERR_BOARD_AUX_TYPE0x112
#define ERR_FPGA_CLRINPUT0x113
#define ERR_FPGA_CLR_AUX_AND_OUTPUT 0x114
#define ERR_FPGA_CLRTRIGGER 0x115
#define ERR_FPGA_CLRMULTIPLEXEUR0x116
#define ERR_BOARD_EXTSYNC_TYPE0x117
#define ERR_NB_DETECTED_BOARD 0x118

#define ERR_UNABLE_READ_FLASH_DESC0x400
#define ERR_READ_FLASH_MAGIC_NUMBER0x401
#define ERR_INVALID_SECTOR_NUMBER0x402
#define ERR_INVALID_PROG_NUM0x403
#define ERR_INVALID_NUM_ARG0x404
#define ERR_RESET_ALL_DSP0x405

#define ERR_UNABLE_READ_PROG_DESC0x500

#define ERR_BOOT_TIME_OUT0x600
#define ERR_BOOT_TIME_OUT_V10x620
#define ERR_READ_BOOT_LOADER0x640
#define ERR_READ_DSP_PROG0x660

#define ERR_UNABLE_READ_HARD_CFG0x700
#define ERR_ALLOC_LOCAL_MEM0x800
#define ERR_UNABLE_TO_READ_FLASH0x900

#define ERR_UNABLE_TO_EXEC_PROG0x980

OR3XV2

#define ERR_LOAD_HARD_CONFIG 0x101

#define ERR_ILLEGAL_CONFIG 0x102

#define ERR_FPGA_INPUT 0x103

#define ERR_FPGA_AUX_AND_OUTPUT 0x104

#define ERR_FPGA_TRIGGER 0x105

#define ERR_FPGA_MULTIPLEXEUR 0x106

#define ERR_BOARD_NB_INPUT 0x107

#define ERR_BOARD_NB_AUX_AND_OUTPUT 0x108

#define ERR_BOARD_NB_TRIGGER 0x109

#define ERR_PASS_ERROR 0x110

#define ERR_BOARD_INPUT_TYPE 0x111

#define ERR_FPGA_CLRINPUT 0x113

#define ERR_FPGA_CLR_AUX_AND_OUTPUT 0x114

#define ERR_FPGA_CLRTRIGGER 0x115

#define ERR_FPGA_CLRMULTIPLEXEUR 0x116

#define ERR_UNABLE_READ_FLASH_DESC 0x400

#define ERR_READ_FLASH_MAGIC_NUMBER 0x401

#define ERR_INVALID_SECTOR_NUMBER 0x402

#define ERR_INVALID_PROG_NUM 0x403

#define ERR_INVALID_NUM_ARG 0x404

#define ERR_RESET_ALL_DSP 0x405

#define ERR_UNABLE_READ_PROG_DESC 0x500

#define ERR_BOOT_TIME_OUT 0x600

#define ERR_BOOT_TIME_OUT_V1 0x620

#define ERR_READ_BOOT_LOADER 0x640

#define ERR_READ_DSP_PROG 0x660

#define ERR_UNABLE_READ_HARD_CFG 0x700

#define ERR_ALLOC_LOCAL_MEM 0x800

#define ERR_UNABLE_TO_READ_FLASH 0x900

#define ERR_UNABLE_TO_EXEC_PROG 0x980

OR36-38 V1

Tests on the analogical part

0x101

  • Change the Ethernet DSP board

0x102

  • Check the configuration programmed in the analyzer (inputs number, DSP number, boards as DC or generators…)

0x103

  • Change the input board for the inputs identified by the leds during the boot

0x104

  • Change the output board

0x105

  • Change the link board

0x106

  • Change the link board

0x107

  • Check the configuration programmed in the analyzer (inputs number, DSP number, boards as DC or generators…)
  • Change the input board

0x108

  • Check the configuration programmed in the analyzer (inputs number, DSP number, boards as DC or generators…)
  • Change the output board

Tests on the digital part

0x200

  • Change the Master DSP board

0x201 to 0x208

  • Change the Calculation DSP board 1 to 8

0x209

  • Change the Disk DSP board

0x210 to 0x218

  • Change the Ethernet DSP board
  • Change the Calculation DSP board 1 to 8

Tests when loading DSP programs on OR36/OR38

0x300

  • Change the Ethernet DSP board
  • Change the global memory board

0x301

  • Check the configuration programmed in the analyzer (inputs number, DSP number, boards as DC or generators…)
  • Change the global memory board

0x302

  • Change the Master DSP board

0x303

  • Change the Disk DSP board

0x304

  • Change the faulty Calculation DSP board: it is the one whose led is off

0x305

  • Change the Ethernet DSP board

invalid licence error

The error "Invalid license number! "Is followed by a number in square brackets: [i] This number identifies the type of error precisely: [1]: No rainbow dongle connected and no OR38 connected [2]: Expiration date reached (only for demo versions) [3]: The PC has been backdated, that is to say that the last date of use of the software contained in the rainbow dongle or in the OR38 is more recent than the current date of the PC (only for the demo versions)


Cases studies for analyser maintenance operation

All

-No communication

  • Check Ethernet cable connection (cable ok, Ethernet connector clean and not broken)
  • Check IP address (though Cfg environment, or in PC ethernet board property and analyser IP address through LCD button)
  • Ping analyser IP address (if both analyser and PC has the same first IP address: exple: 223.255.253.50 – 223.255.253.51): command prompt windows, ping 223.255.253.50
  • In maintenance mode (long power LCD push button for V2-V3 and OR34-35, last and first power LCD push button for V1), check comm with Cfg environment or ping

-Any error message

  • Try to flash hard (update hardware through NVGate Cfg environment)
  • Try to flash Bios server hard (update hardware through NVGate Cfg environment). You should have added before " –updateserver –forceupdate" to property target name of your NVGate environment shortcut (exple : target ; C:\OROS\Programs\NVGate\NVGateCfg.exe –updateserver –forceupdate) (–forceupdate allow to flash hard even if it already is in this version)

-Analogical error on measures or maintenance center

  • Take a look at boards for burnt components (smoke) specially GND/Flt resistor
  • First measure outputs coherency (because we use it for all analogical tests)
  • Check switchbox response
  • Check BNC cable connections (cable ok, BNC center tightened and clean)
  • Change the corresponding board

-Mobidisk in USB-connected is not recognize/seen en NVGate OFFICE mode

  • Start NVGate as administrator mode (right click- start as administrator)

-Verification

  • Run time error (exple: 2147024156 (800702e4) + automation error)
  • Right click on program NVGate and Microsoft office WORD and OROS verification, => compatibility =>execute as administrator
  • Call argument '5' or execution error '5' on the very beginning verification process. => Remove then reinstall "constant.ini" in "verification" program folder . (basically 'List the different OR38 software' Soft1=NVGATE V10.00 and not only V10)

OR36-38 V1 :

-Stay in « rebooting »

  • Old unresolvable bug. Reboot doesn'twork always. => Force Shutdown/powerON.

-Stay in « powering up »

  • Check digital voltages: 5V num, 3V3 num
  • Unplug/Plug Digital board
  • Change Ethernet DSP board or memory board

-Error 2xx or 3xx: digital issue

  • Please refer to S015-070-1 document for error code
  • Unplug/Plug and clean Digital board
  • Most of the time : change the DSP corresponding to the last error number (exple: error 206 change DSP6)
  • Change one by one all digital board
  • Ask for a minimal configuration (1 DSP, 4 channel) can help the diagnostic

-Digital issues: crash or error message on NVGate start

  • Unplug/Plug and clean Digital board
  • Change one by one all digital board (start with: Ethernet DSP, Master DSP, Memory)and use a macro that use lots of SPU between each replacement (ask for us if you need it : Macro "Run")
  • Try without Mobidisk

-Error 1xx: analogical issue

  • Please refer to S015-070-1 document for error code
  • Unplug/Plug and clean analogical board
  • Take a look at boards for burnt components (smoke)
  • Change one by one all analogical board

OR34-35V1

OR36-38 V2

OR36-38 TW (V3)

-output noise S/N (=-110dB VS -114dB) in verification

  • Plug to the ground (or ground) all instruments (including analyser)
  • Change 21226A (+21225A) link board

-Impossible to test V29-30 or V31-32 (or DSP computation errors or incoherent phase errors) in OR3Xtest_V3 input boards test

  • Change 21226A (+21225A) link board

-Error 0x0000117

  • replug or change 21226A (+21225A) link board
  • replug or change 21230A ARM board (DSP server) (pay ATTENTION to procedure)

-Error 0x0000112 (randomly or/and when hardware is "warm")

  • replug or change 21223A (+21225A) auxiliary board
  • replug or change 21226A (+21225A) link board

OR35TW

-Error 0x0000112 (randomly or/and when hardware is "warm")

  • replug or change 21264A Generator board (plug under 21266A motherboard)
  • folded pin on J1 or J2 motherboard connectors when replacing power supply board
  • Replace 21266A motherboard (on last resort)

-Error 0x0000111 (once after a powersupply replacement or replug)

  • Bad first initialization => not critical