VIDAS AND MINIVIDAS - SCANNER ERRORS

Scanner Codes < 100 are ADVISORY or INFORMATIONAL and will appear only on a Diagnostic Terminal.

ID# Description

0 Scanner OK No errors
During barcode reading, the tray did not move to the home position when
1
commanded
During barcode reading, the tray did not move to the out position when
2
commanded
3 During barcode reading, the tray did not toggle its position when commanded

7 The Scanner head will not leave the home position

8 The Scanner head will not move to the home position

9 A barcode was read which contained too few characters

10 A DEL character was received
11 Packet (data) buffer overrun on receive
12 Bad checksum received for a packet

miniVIDAS: A SYNC message was received from the VIC Board (computer)
13
VIDAS: A SYNC error was received from the HOST (computer)

miniVIDAS: A command was received from the VIC Board which contained an
illegal character
14
VIDAS: A command was received from the HOST which contained an illegal
character
15 A barcode was read which contained too many characters
16 The number-of-packets count was invalid
17 The end packet was received and some data packets were still expected
18 Bad parameter in packet
19 The end packet was expected, but not what was received
Too much time elapsed between receipt of the first character of a message and
20
a subsequent character
Too much time elapsed between receipt of the first packet of a message and a
21
subsequent packet
22 A packet being transmitted to the Host was NAKed
23 A packet being transmitted to the Host was neither ACKed or NAKed
24 A packet being transmitted to the Host failed to be sent due to too many NAKs
25 A packet being transmitted to the Host failed to be sent due to too many NAKs
26 Error trying to read an incubator's temperatures
27 A retry was done on an incubator poll
28 A retry was done for a tray scan

29 A reduction in motor speed was done

30 Unable to find the tray (with the tray edge sensor)

Attempt to verify that no steps have been lost by re-finding the tray edge, has
31
failed

32 Attempt to verify that no steps have been lost by verifying home, has failed

Too many error messages were generated while not logged in Some have been
33
dropped

34 Odd internal error

35 Starter task running too soon/late
36 Starter task running too soon/late
Starter task failed due to the Section being in a state other than RESERVED
37
when start time arrived

40 Error moving tray in while trying to establish tray origin

41 Error moving tray out while trying to establish tray origin

42 Attempt to read an incubator's version has failed

43 Attempt to log into the Host Computer (VIC) has failed
45 An air reading was equal to zero
46 A tray origin was reset due to minor drift
47 Non-volatile RAM checksum failed
48 Optics were recalibrated
61 A protocol was reloaded
A packet being transmitted to the Host (computer) was apparently interrupted by
62
the start of a message from the Host
63 A call to transmit ( ) was deferred due to it not being okay to transmit
64 Attempt to send a sync packet
65 An attempt to send a sync packet failed
67 An incubator communications error resulted in us calling the inc_sync ( ) routine
68 A barcode was unreadable

A barcode did not read on the first try This is set when it starts the retry phase,
69 and will be set once per strip that it retries, regardless of how many retries are
done

70 A CV for a reading was out-of- range

Scheduling slop error A contig J- reading was seen by the checkinc( ) loop
71
Should not have been Would have secfailed if not a contig reading
72 Scheduling slop error
73 Scheduling slop error
74 A temperature error occurred in one of the Sections
75 The motor fix task was called
76 The motor fix task did not find a problem with the motor

100 VIDAS: Receive failed due to lack of memory

101 MINI VIDAS: Receive failed due to lack of memory

102 Command "PROTO" failed due to full memory

MINI VIDAS: Unknown command received from Host (VIC Board)

103 VIDAS: Unknown command
received from Host computer

104 Command "vidasep" parameters were invalid

105 Command "stinc" (Start Section) parameters were invalid

106 Command "retran" (Retransmit) parameters were invalid.

107 Command "rsinc" (Reset) parameters were invalid.

108 Command "proto" (Protocol) parameters were invalid

109 Incubator did not respond to the reset command (Section Reset Error)

An Incubator whose start time had been reached, failed to start (Section Start
110
Error)

111 Incubator failed to re-start after a tray reading (Section Restart Error).

Command "stinc" failed while attempting to download the protocol to the

112
Incubator (Protocol Error).

Incubator error occurred while an assay was/is in progress (Section Failure - an

114
Incubator error should have preceded this error).

115 Command "bcread" parameters were invalid (Invalid Bar Code parameters).

117 A stored Protocol is corrupt (Scanner board failure)

119 Command "RESET" parameters were invalid (Invalid Section Reset parameters).

Command "INTERP" (Interpret) parameters were invalid. (Illegal Interpret

120
parameters).

A "READBC" command could not be done due to thecurrent instrument status.

121
(Unable to perform a Barcode reading)
 A "STINC" command could not be done due to the current instrument status
122
(Scanner unable to start a Section).

A "RETRAN" command could not be done due to current instrument status

123
(Scanner Board unable to retransmit data).

124 Optics self-test failed. Air reading too high (Air reading> 20 RFU)

125 Optics self-test failed (VSH Extended range hardware failure).

Optics self-test failed. Air readings have climbed to a level at which Field Service
126
should be notified

127 Optics self-test failed

128 Computer self-test failed (Scanner board failure)

129 Computer self-test failed (Scanner board failure)
130 Computer self-test failed (Scanner board failure)
131 Used for errors related to the NVRAM and HW version (Scanner board failure)

132 Command "SLIPTIME" parameters were invalid

133 Started looking for Jx status too late. Protocol time glitch (Assay failed)

Section status while in fast pool loop was not the correct Jx, nor was it a working
134
status (Assay failed)

135 Timed out in fastpool routine while waiting for Jx status (Assay failed)
 A tray scan failed (Scanner head unable to find tray edge)
Tray edge not found where expected
136 The tray is not in the correct position.
The scanner head is not able to see the tray
With NSH, notify when the tray origin offset is missing (not calibrated)

A Jx status was detected by the checkinc( ) loop on a non- contig scheduled

137
mode J- reading (Protocol ReadError)

138 The parameters in the "SECTEMP" command were invalid.

Used in a secfail message, this indicates that the Section aborted due to a
139
manualreset command from the host(VIC Board or VIDAS PC)

141 A bad state occured when trying to scan the tray. Section state is not RUNNING.

142 A bad state occured when trying to scan the tray. Section state is not RUNNING.

143 Unable to home theScanner head (Scan head motor failure)

144 Checking home position failed in the self- test (Scan head motor failure)

The motor speed has fallen to a level at which field service should be notified
145
(Scan head motor movement becoming restricted)

146 Instrument memory almost full.

147 Extended range optics failure (VSH). Jumper set wrong or bad hardware

148 The internal stack usage has reached a level to be concerned about.

149 The external stack usage has reached a level to be concerned about.

More errors have occurred than would fit in the error queue. Some have been
150
lost

151 Command "DELPROTO" parameters were invalid

152 Command "SETVAR" parameters were invalid
153 Command "BCTEXT" parameters were invalid

154 A "BCTEXT" command could not be done due to the current instrument status

The non-volatile RAM checksum failed (Memory corrupt or incorrect checksum

155
value is found)
The non-volatile RAM checksum failed (Memory corrupt or incorrect checksum
156
value is found)
 Auto-calibration data not present in non-volatile RAM, but a Solid Standard
Bracket was found in the instrument (it will occur the first time a Solid Standard is
157
installed in an instrument until the optics are recalibrated and a standard value is
stored)

Auto-calibration data present in non-volatile RAM, but Solid Standard Bracket not
158
found

159 Solid Standard Bracket can no longer be found

160 Calibration Drift is excessive between (see identified anomalies)

Calibration Drift: the Digipot is too close to the end of its range (see identified
161
anomalies)

162 Auto-calibration not performed recently.

ly on a Diagnostic Terminal.

Action

All is normal

Check for error 40 or 41

Check for error 40 or 41

Check tray movement

Check for error 144
Check scanner head movement

Check for error 144

Check scanner head movement

Information only
Information only
Information only
Information only

Information only

Information only

Information only
Information only
Information only
Information only
Information only

Information only

Information only

Information only
Information only
Information only
Check routing of serial cables (noise could be induced on the serial line)
Information only
Information only
Information only
Check for Scanner head binding
VIDAS: Check for error 145
Tray edge not found, check for code 136, 114
Verify tray pulls into instrument correctly, check for code 40
See actions for Code 31
Possible problem with reflective surface on back of tray
See actions for code 32
Check for intermittent ribbon cable on Scanner head (cable modification)
Warning that the Scanner motor is loosing steps, check for code 75
Check Scanner head mechanical movement (binding) and alignment
Check for excessive drive screw end play
Check for loose barcode cable catching bottom of pump arm
Check for code 143

mini VIDAS: Allow module to log in to VIC (computer)

VIDAS:
Allow module to log in to computer
Correct cause of other errors
Information only
Information only
Information only

Check for error code 105

Could be caused by possible missing motor steps

Perform Tray Test

Could be caused by possible missing motor steps

Perform Tray Test
Bad firmware
Information only
Check the zero adjustment on Scanner Board
Clean Tray edge reflective surface
See errors 157 and 158
Auto calibration of optics was performed
Information only

Information only

Information only
Information only
Information only
Information only
Will generate a Bad Barcode error (BCERR)
Check condition of barcode being read
Check barcode reader alignment (see Alignments)

Information only

Check for electrically noisy Scanner head

Verify Optics Calibration

Information only

Information only
Information only
Check Temperatures
Check for error 76. If 75 = 76 (number of errors equal) Scanner Motor OK
Check for error 76. If 75 = 76 (number of errors equal) ScannerMotor OK
Allow current assay(s) to finish, then cycle power to the VIDAS
If the error persists, replace Scanner Board
Allow current assay(s) to finish, then cycle power to the MINI VIDAS
If the error persists, replace Scanner Board

Allow current assay(s) to finish, then cycle power to the VIDAS / mini VIDAS
If development system, check number and size of protocols - may have too many
If the error persists, replace Scanner Board

If error occurred while entering a command on keypad, try entering the command
again
Possible corrupt software on VIC Board or on Host Computer
If the error persists, replace Scanner Board
Power OFF/ON the VIDAS or mini VIDAS
Check that Software and Firmware are compatible
If the error persists, replace Scanner Board
Power OFF/ON the VIDAS or mini VIDAS
Check that Software and Firmware are compatible
If the error persists, replace Scanner Board
Power OFF/ON the VIDAS or mini VIDAS
Check that Software and Firmware are compatible
If the error persists, replace Scanner Board
Power OFF/ON the VIDAS or mini VIDAS
Check that Software and Firmware are compatible
If the error persists, replace Scanner Board
Power OFF/ON the VIDAS or mini VIDAS
Check that Software and Firmware are compatible
If the error persists, replace Scanner Board
Power OFF/ON the VIDAS or mini VIDAS.
Check the ribbon cable from the Scanner board to the Incubator board
Verify Address/Reset jumpers and voltages on the Incubator board
Use the "rsinc x" command (x = the Section letter) on the PuTTY Terminal to
reset the failing section
If the error persists, replace the Incubator board concerned
Use the "rsinc x" command (x = the Section letter) on the PuTTY Terminal to
reset the failing section
If the error persists, replace the Incubator board concerned
Use the "rsinc x" command (x = the Section letter) on the PuTTY Terminal to
reset the failing section
If the error persists, replace the Incubator board concerned
Use the "rsinc x" command (x = the Section letter) on the PuTTY Terminal to
reset the failing section
If the error persists, replace the Incubator board concerned

Verify all voltages on the Incubator board

Use the "rsinc x" command (x = the Section letter) on the PuTTY Terminal to
reset the Section.
Use "dinc x" (x = Section letter) on the PuTTY Terminal to look for errors; check /
repair if errors found
Rerun the assay.
If the error persists, replace the Incubator board concerned

Verify the label of the strip.

Verify Barcode Reader alignment
Use the PuTTY Terminal to perform "bc_x" (x = Section letter) for the section
concerned
If the error persists, change the barcode reader
If the error persists, perform an optics calibration (if air reading > 10 RFU, the
system concludes that strips are present even if it is not the case. The barcode
reader will look for a barcode in vain).

Power OFF/ON the VIDAS or mini VIDAS

Try to run the assay again
If the error persists, change the Incubator board
If the error persists change the Scanner board
Power OFF/ON the VIDAS or mini VIDAS.
Verify that Software and Firmware are compatible
If the error persists, change the Scanner board
Power OFF/ON the VIDAS or mini VIDAS.
Verify that Software and Firmware are compatible
If the error persists, change the Scanner board

Verify SPR Door Sensor alignment and operation (can be due to an open door)
Check quality of reflective surface
Check instrument status (use the "stat" command on the PuTTY Terminal)
Check the checkinc status line on the PuTTY Terminal to determine the error
Verify SPR Door Sensor alignment and operation (can be due to an open door)
Check quality of reflective surface
Check instrument status (use the "stat" command on the PuTTY Terminal)
Check the checkinc status line on the PuTTY Terminal to determine the error

MINI VIDAS:
Check the ribbon cable between the VIC board and the Scanner board
If the error persists, replace the scanner board
If the error persists, replace the VIC board
VIDAS:
Check the cable between the computer and the Scanner board
If the error persists, replace the scanner board

Clean the optics

If the error persists, verify / perform Optics calibration
If the error persists, replace the Scanner board
If the error persists, replace the Scanner cable E-chain
If the error persists, replace the Trigger Board (VSH)
If the error persists, replace the High Voltage Power Supply (VSH)
If the error persists, replace the Scanner Head

Use the "EXTR" command (on PuTTY Terminal) to verify that the BR average
minus the SR average is less than 50 counts
If the error persists, verify / perform Optics calibration
If the error persists, replace the Scanner board

Clean the optics

If the error persists, verify / perform Optics calibration
If the error persists, replace the Scanner board
If the error persists, replace the Scanner cable E-chain
If the error persists, replace the Trigger Board (VSH)
If the error persists, replace the High Voltage Power Supply (VSH)
If the error persists, replace the Scanner Head

Clean the optics

If the error persists, verify / perform Optics calibration
If the error persists, replace the Scanner board
If the error persists, replace the Scanner cable E-chain
If the error persists, replace the Trigger Board (VSH)
If the error persists, replace the High Voltage Power Supply (VSH)
If the error persists, replace the Scanner Head
Replace the scanner board
Replace the scanner board
Replace the scanner board
Error 131 at boot (Incorrect or loose cable connection by the FSE): Check the
cable connections on the DSP and NSB boards according to the procedure.
Detail of Error 131 (with NSH):
The error conditions related to the NSB non-volatile memory corruption and
version mismatching are sent to the host within the error 131. In particular, error
131 is generated when:
• the Magic number or checksum of a region in the NSB non-volatile memory is
not correct
• the NSB HW version is not compatible with the NSB FW running in the
microcontroller.
• the FPGA FW version is not compatible with the NSB FW running in the
microcontroller.
Error 131 is a blocking error without NSB inhibition, which means that the
instrument stops operating, but the NSH responds normally.
Actions to perform in case of error 131:
• Check the NSB/NSH voltage (±12 and +5 V).
• Check cable connection on the NSH/NSB.
• Clean the error history by repeating the command "OPTRST", reinitialize the
instrument and check if the error still appears. If yes, continue with the procedure
below.
• Perform the "TRAYCAL" and "BCA" alignment procedure.
• Perform optical calibration with "SHCAL" (in order to also align the S/N between
NSH and NSB), reinitialize the instrument and check if the error still appears. If
yes, continue with the procedure below.
• Update NSB FW and reinitialize the instrument.

Replace the Firmware on the Scanner board

If the error persists, replace the Scanner board
If the error persists, replace the Incubator board of the section concerned
If the error persists, save the log file using the PuTTY terminal
Replace the Firmware on the Scanner board
If the error persists, replace the Scanner board
If the error persists, replace the Incubator board of the section concerned
If the error persists, save the log file using the PuTTY terminal
Replace the Firmware on the Scanner board
If the error persists, replace the Scanner board
If the error persists, replace the Incubator board of the section concerned
If the error persists, save the log file using the PuTTY terminal
Replace the Firmware on the Scanner board
If the error persists, replace the Scanner board
If the error persists, replace the Incubator board of the section concerned
If the error persists, save the log file using the PuTTY terminal
Reset the section because it may be caused by the customer pushing the tray
too hard when inserting the strips
Check for other errors. If there are other movement errors (1013, 1016, 1091)
check for the tray motor and sensor. Then check if the metal gear is unscrewed
If there are other scanner head errors (143, 144, 145), check for the scanner
head motor and home sensor
If error persists, check the tray edge sensor. Type "loop k sensors" on the PuTTY
terminal to check the tray edge sensor,

Detail of Error 136 (with NSH):

In the past it was used to notify a strip optical scanning failure in the current
section, requested by the host.
In the NSB FW, error 136 is also used to notify when the tray origin offset is
missing (not calibrated).
Actions to perform in case of error 136:
• Check that the Tray Edge sensor functions properly (check the flat cable
between the DSP and the Tray Edge Sensor board).
• Check cable connection on the NSH/NSB.
• Check LED D13 (ON when nothing is detected, and OFF when something is
detected)
• Check the NSB/NSH voltage (±12 and +5 V).
• Perform the TRAYCAL and BCA alignment procedures.
• Reinitialize the instrument.

Reset the section with the "rsinc x" command

Re-run the assay
Check the firmware version
Replace the incubator board

Instruct the operator not to reset sections that are running

Perform the "dinc x" (x = Section letter) command on the PuTTY Terminal, and
check for any section problems (correct any problems found)
If the error persists, replace the incubator board concerned
Perform the "dinc x" (x = Section letter) command on the PuTTY Terminal, and
check for any section problems (correct any problems found)
If the error persists, replace the incubator board concerned

Check the Scanner/Carriage assy for mechanical binding

Check the voltages of the power supply board, replace fuses or Board if
necessary
Check for loose cables or wires interfering with scanner head movement (such
as barcode cable)
If the error persists, verify scanner home sensor operation and adjustment
If the error persists, verify scanner motor operation by typing the command
"checkmotor" command on the PuTTY Terminal, and watch for step errors. In
case of step errors, replace the scanner motor
If the error persists, replace the scanner board
Check the Scanner/Carriage assy for mechanical binding
Check the voltages of the power supply board, replace fuses or Board if
necessary
Check for loose cables or wires interfering with scanner head movement (such
as barcode cable)
If the error persists, verify scanner home sensor operation and adjustment
If the error persists, verify scanner motor operation by typing the command
"checkmotor" command on the PuTTY Terminal, and watch for step errors. In
case of step errors, replace the scanner motor
If the error persists, replace the scanner board

Check the Scanner/Carriage assy for mechanical binding

Check the voltages of the power supply board, replace fuses or Board if
necessary
Check for loose cables or wires interfering with scanner head movement (such
as barcode cable)
If the error persists, verify scanner home sensor operation and adjustment
If the error persists, verify scanner motor operation by typing the command
"checkmotor" command on the PuTTY Terminal, and watch for step errors. In
case of step errors, replace the scanner motor
If the error persists, replace the scanner board

Check instrument status using the "stat" command on the PuTTY Terminal,
maximum Istack = 160 or Xstack = 1500
Power OFF/ON the VIDAS or mini VIDAS
If the error persists, replace the scanner board
Clean optics.
If the error ocurred during a run, instruct the customer to reject the results and to
re-run again. If the error presists, replace the scanner board
If the error persists, verify / perform optics calibration/adjustment
If the error persists, replace the scanner board
Check instrument status using the "stat" command on the PuTTYTerminal, and
note the Istack information (Maximum Istack = 160).
Power OFF/ON the VIDAS or mini VIDAS
If the error persists, replace the scanner board
Check instrument status using the "stat" command on the PuTTY Terminal, and
note the Xstack information (Maximum Xstack = 1500)
Power OFF/ON the VIDAS or mini VIDAS
If the error persists, replace the scanner board
Perform an "errs" command on the PuTTY Terminal to check for errors
Correct the cause of errors referring to the specific error code described in this
section
If the error persists, power OFF/ON the VIDAS or mini VIDAS
Power OFF/ON the VIDAS or mini VIDAS
Power OFF/ON the VIDAS or mini VIDAS
Power OFF/ON the VIDAS or mini VIDAS

Power OFF/ON the VIDAS or mini VIDAS

Perform optics calibration/adjustment

If the error persists, replace the scanner board
Perform optics calibration/adjustment
If the error persists, replace the scanner board
Perform optics calibration/adjustment
If the error persists, replace the scanner board

verify operation of the scanner head tray edge sensor on the Solid Standard
bracket
If the error persists, change the tray edge sensor
If the error persists, change the scanner cable E-chain
If the error persists, change the scanner board
If the error persists, change the scanner head

verify operation of the scanner head tray edge sensor on the Solid Standard
bracket
If the error persists, change the tray edge sensor
If the error persists, change the scanner cable E-chain
If the error persists, change the scanner board
If the error persists, change the scanner head
See Service manual in the Troubleshooting chapter.

In case of error 161 with the NSH, refer to “NSH Troubleshooting” in the Service
Manual.
Note: Auto-calibration frequency (times when errors 160 and 161 can occur):
- at startup
- Every 12 hours

Instrument has been too busy for auto calibration to occur:

Allow the VIDAS or mini VIDAS to remain idle for a while (>1 hour)
VIDAS AND MINIVIDAS - INCUBATOR ERRORS
Scanner board can add "1000" to the incubator error code. For example, error 53 will appear as error 1053 in mi

vidas MINIvidas Message

Description
ID# ID# displayed
Unknown section
10 1010 Door open.
error
Unknown section
11 1011 Temperature Error.
error

Tower mechanism
12 1012 Did not see Tower sensor transition.
failure

Tray mechanism
13 1013 Did not see Tray sensor transition.
failure

Pump mechanism
14 1014 Did not see Pump sensor transition
failure

Tower mechanism
15 1015 Found sensor, tower motor lost steps
failure
 Tray mechanism
16 1016 Found sensor, tray motor lost steps.
failure

Pump mechanism
17 1017 Found sensor, pump motor lost steps
failure

Unknown section
18 1018 Door was opened while assay was in progress.
error

Tray temperature
50 1050 out of allowed Tray temperature too high
range

Tray temperature
51 1051 out of allowed Tray temperature too low
range

SPR temperature
52 1052 out of allowed SPR block temperature too high.
range

SPR temperature
53 1053 out of allowed SPR block temperature too low.
range

Tray temperature
54 1054 out of allowed Tray temperature higher than average tray limit
range

Tray temperature
55 1055 out of allowed Tray temperature lower than average tray limit.
range

SPR temperature
56 1056 out of allowed SPR block temperature higher than average limit
range
 SPR temperature
57 1057 out of allowed SPR block temperature lower than average limit
range

Temperature
58 1058 Cannot read temperatures.
monitoring failed

Temperature Temperature reference on Incubator Board

59 1059
monitoring failed invalid.

Some section
90 1090 errors lost due to Too many Incubator errors, some errors dropped.
overflow

Unable to initialize
91 1091 Scanner could not find edge of tray.
section

Section hardware
97 1097 Unable to contact Incubator upon hardware reset
failure

Section
98 1098 communication Incubator communication error
error

Section
99 1099 communication Incubator communication error
error
will appear as error 1053 in mini VIDAS and error 53 in VIDAS PC.

Action

Close section SPR Door. Rerun work list

If closed, check door sensor

Check if temperature errors 50 to 59 are present. Refer to error 50 and 59 actions.

Reset the section to check if the tower is still stuck or has difficulty moving
Check cables
Check the tower sensor alignment
Run Assay code TP5 (see Test Protocols) and observe the Tower LED on the Incubator board to
verify sensor operation.
If the error persists, check for mechanical movement problems (belt, lead screw, bearings) and
change the tower motor if necessary.
If the error persists, change the incubator board concerned

Reset the section to check if the tray is still stuck or has difficulty moving
Check cables
Check the tray sensor alignment
Run Assay code TP6 (see Test Protocols) and observe the Tray LED on the Incubator board to
verify sensor operation
Check if the tray metal drive gear is unscrewed
If the error persists, check for mechanical movement problems (Nylon gear, bearings) and
change the tray motor if necessary
If the error persists, change the incubator board concerned

Reset the section to check if the pump is still stuck or has difficulty moving
Check cables
Check the pump sensor alignment
Run Assay code TP4 (see Test Protocols) and observe the Pump LED on the Incubator board to
verify sensor operation
If the error persists, check for mechanical movement problems (motor ball joint) and change the
pump motor if necessary
If the error persists, change the incubator board concerned

Reset the section to check if the tower is still stuck or has difficulty moving
Check cables
Check the tower sensor alignment
Run Assay code TP5 (see Test Protocols) and observe the Tower LED on the Incubator board to
verify sensor operation
If the error persists, check for mechanical movement problems (belt, lead screw, bearings) and
change the tower motor if necessary
If the error persists, change the incubator board concerned
Reset the section to check if the tray is still stuck or has difficulty moving
Check cables
Check the tray sensor alignment
Run Assay code TP6 (see Test Protocols) and observe the Tray LED on the Incubator board to
verify sensor operation
Check if the tray metal drive gear is unscrewed
If the error persists, check for mechanical movement problems (Nylon gear, bearings) and
change the tray motor if necessary
If the error persists, change the incubator board concerned

Reset the section to check if the pump is still stuck or has difficulty moving
Check cables
Check the pump sensor alignment
Run Assay code TP4 (see Test Protocols) and observe the Pump LED on the Incubator board to
verify sensor operation
If the error persists, check for mechanical movement problems (motor ball joint) and change the
pump motor if necessary
If the error persists, change the incubator board concerned

Check door sensor and alignment

External root causes (environmental conditions, installation specifications)

Power supply/fan.
Strips coming from Heat & Go
defective Incubator board
Defective tray

Instrument warm up
Cold strips
Cut wire
Defective incubator board
Defective tray
External root causes (environmental conditions, installation specifications)
Power supply/fan
Defective Incubator board
Defective SPR block
Instrument warm up
Cut wire.
Defective Incubator board
Defective SPR block
On mini VIDAS, can be caused by the tray of the other section which is too cold (for example cut
tray wire).
Insertion of cold/hot strips in the section
Defective Incubator board
Defective tray
Cut Tray wire
Insertion of cold/hot strips in the section
Defective Incubator board
Defective tray
On mini VIDAS, can be caused by the SPR block of the other section which is too cold (for
example cut SPR block wire)
Defective Incubator board
Defective SPR block
Cut SPR block wire
Defective Incubator board
Defective SPR block
Check that the correct / compatible version(s) of the Firmware have been installed in the
Incubator and Scanner Boards.
Replace the Incubator Board
Verify power supply voltages on the incubator board concerned
Replace the Incubator Board
If error 59 is present on all sections,check power supply voltages

Power OFF/ ON the instrument

Correct cause of other errors

Clean back edge of tray and type "tfx" (x = section letter) on the PuTTY Terminal, to see if the
Scanner head can find the tray edge
Verify Tray alignments and correct movement
Verify Scanner Tray Edge Sensor alignment
Check for defective sensor or ribbon cable on Scanner head
Power OFF/ON the instrument
Use "rsinc x" (x = the section letter) on the PuTTY Terminal to reset the section
Verify Incubator cable connections, jumpers, and voltages
Power OFF/ON the instrument
Use "rsinc x" (x = the section letter) on the PuTTY Terminal to reset the section
Verify Incubator cable connections, jumpers, and voltages
Replace the Incubator Board
Replace the Scanner Board

Power OFF/ON the instrument

Use "rsinc x" (x = the section letter) on the PuTTY Terminal to reset the section
Verify Incubator cable connections, jumpers, and voltages
Replace the Incubator Board
Replace the Scanner Board
VIDAS AND MINIVIDAS - NSH ERRORS
NSH errors generating Error 161

Error
Error code
code Description
(HEX)
(DEC)

1 1 Wrong stream length

2 2 Unknown command

3 3 Bad command parameters

4 4 Wrong stream format

5 5 Checksum Error

6 6 DRDY not in the status “high” (FPGA)

7 7 Transmission timeout (FPGA)

8 8 Reception timeout (FPGA)

11 00B ADC Conversion timeout

12 00C Led feedback signal out of range

13 00D Reference signal out of range

14 00E Fluorescence signal out of range

Data from NSH cannot be converted to

16 10
decimal numbers
Data from NSH not compatible to the
17 11 format expected respect the NSH
Status
Data received from NSH is not the
18 12
expected string (DNE)

The barcode returned by the NSH is

19 13
not delimited by the characters ‘<’ e ‘>’
25 19 Int SSolid Autocalibration Warning

26 01A Int SSolid Autocalibration Error

Int SSolid Autocalibration Error and

27 01B
EEprom Read/Write Error

71 47 EEprom data read/write Error

NSH not ready to receive commands

256 100
(synchronization failed)

257 101 NSH status of irrecoverable error

258 102 NSH in upload status

259 103 NSH in erroneous boot status

260 104 NSH in erroneous init status

Error code returned by the NSH not

261 105
consistent to the sent command
Calibration coefficient read by the NSH
264 108
not allowed (different from 0/1)
The instrument type read by the NSH
265 109
not allowed (different from 0/1)

NSH FW version not compatible with

272 110 the current version of the FW running
in the NSB microcontroller 8051.

S/N stored respectively by NSB and

512 200
NSH not equal

513 201 Int SSolid Autocalibration Warning

514 202 Int SSolid Autocalibration Error

Int SSolid Autocalibration Error and

515 203
EEprom Read/Write Error
Error or data not present in the EEprom
516 204
of the NSH
 Action

Check the NSB and NSH voltage (±12 & +5 V)

Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5V)
Check the NSH-PreAmp Board cable
Check the NSB and NSH voltage (±12 & +5V)
Check NSH-LED Driver board cable
Check the NSB and NSH voltage (±12 & +5V)
Check the beam splitter (dirty or scratched)
Check NSH-LED Driver board cable
Repeat the optical calibration
Check the NSB and NSH voltage (±12 & +5V)
Check the beam splitter (dirty or scratched)
Check the NSH-PreAmp Board cable
Check NSH-LED Driver board cable
Repeat the optical calibration/adjustment
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB

Check the NSB and NSH voltage (±12 & +5 V)

Check cable connection on the NSH-NSB

Check the NSB and NSH voltage (±12 & +5 V)

Check cable connection on the NSH-NSB

Check the NSB and NSH voltage (±12 & +5 V)

Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5V)
Check the beam splitter (dirty or scratched)
Check the solid standard mechanical position
Check tray offset on tray A
Repeat the optical calibration/adjustment

Check the NSB and NSH voltage (±12 & +5V)

Check the beam splitter (dirty or scratched)
Check the solid standard mechanical position
Check tray offset on tray A
Repeat the optical calibration/adjustment
Check the NSB & NSH voltage (±12 & +5V)
Update DSP Firware and try to reinitialize
Check the NSB & NSH voltage (±12 & +5V)
Update DSP Firware and try to reinitialize
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Retry DSP FW update
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB
Check the NSB and NSH voltage (±12 & +5 V)
Check cable connection on the NSH-NSB

Check the NSB and NSH voltage (±12 & +5 V)

Check cable connection on the NSH-NSB
Update DSP/NSB Firmware

Complete optical calibration/adjustment and save the solid standard value

Check the NSB and NSH voltage (±12 & +5 V)

Check the beam splitter (dirty or scratched)
Check the solid standard mechanical position
Check tray offset on tray A
Repeat the optical calibration/adjustment

Check the NSB and NSH voltage (±12 & +5 V)

Check the beam splitter (dirty or scratched)
Check the solid standard mechanical position
Check tray offset on tray A
Repeat the optical calibration/adjustment
Check the NSB and NSH voltage (±12 & +5 V)
Update DSP FW and try to reinitialize
Check the NSB and NSH voltage (±12 & +5 V)
Update DSP FW and try to reinitialize
MINIVIDAS - Errors > 2000

ID# Message displayed Description

2001 Software failure Heap out of space

2002 Software failure Heap corrupted

2003 Software failure Invalid Heap block freed

2004 Boot EPROM obsolete Boot EPROM wrong table size

2005 Boot EPROM obsolete Boot EPROM old version

2006 Software failure Proto too big

2007 Software failure RUNWL msg but no protocol
2008 Communications error Bogus RC from receive of %d
2009 Communications error Bogus T_ status %d
ask %d exited code %d, system
2010 Software failure
compromised

2011 Software failure Task %d aborted, system compromised

2012 Communications error @ Invalid section '@sec@' in bcinfo msg

2014 Assay data load failed Protocol not found

2015 No assay data No protocols found!

2016 Assay data load failed Protocol file corrupt

2017 Warning: SRAM card battery low Warning: SRAM Card battery low

2018 Warning: replace SRAM card battery! Warning: Replace SRAM Card battery!

2019 No assay data No assay data found

2020 Internal printer paper empty Internal printer paper empty

2021 Internal printer error Internal printer general error

2022 Internal printer error Internal printer busy

2023 Internal printer error Internal printer Ack timeout

2024 External printer paper empty

External printer error
2025 External printer error External printer general error
2026 External printer error External printer busy
2027 External printer error External printer ack timeout
2028 Communications error Invalid msg from scanner

2029 Communications error @ Invalid section '@sec@' in incst msg

2030 Communications error Invalid section id @id@ in incst msg

2031 Communications error @ Invalid section '@sec@' in flinfo msg

Item \"@item@\" on menu \"@menu@\"

2032 Software failure
doesn't have a submenu or an action

2033 No assay data No assays found!

2034 Communications error Invalid section wlid @id@ in secfail msg

2035 Assay data load failed No Protocols

2036 Software failure Invalid language string ID @id@

2037 Communications error Invalid section in resip

2038 Section reset failed @ Section @s@ failed to reset

@ Invalid section '@sec@' in bcodest

2039 Communications error
msg
@ Invalid section wlid @id@ in bcodest
2040 Communications error
msg

2041 Communications error Inconsistent data in flinfo - section name

2042 Communications error Inconsistent data in flinfo - run ID

2043 Communications error Invalid section in secfail
Inconsistent data in bcinfo - section
2044 Communications error
name
2045 Communications error Inconsistent data in bcinfo - bad ID

2046 Communications error @ Invalid section '@sec@' in bctext msg

2047 Communications error Invalid field count in bctext

2048 Assay data load failed Too many assays

2049 Assay data load failed Assay corrupt

2050 Assay data load failed Assay load error
2051 Lab function failed Corrupt fake flinfo file - file too short

2052 Software failure DML Startup file execution error

2053 Software failure Strip index out of range

2054 Unknown software error No protocol order list found

2055 Communications error Secfail on non-running section
Secfail on section @sec@, Error code
2056 Unknown software error
@err@

2057 Assay data load failed Assay load error

2058 Communications error @ Invalid section id @id@ in bcinfo msg

Cannot begin barcode read - check @ Section @sec@ failed to start BC,
2059
door bcodest failcode @err@
@ Section @sec@ failed to start, incst
2060 Cannot begin assay - check door
failcode @err@
PartitionBitMap fault need: %d got: %d
2061 Unknown software error
map: %d
2062 Assay startup error Problem with starting a section
2065 Communications error Bad arg count in VIDASep
2066 Unknown software error Analysis routine unhappy
2067 Lab function failed Corrupt fake barcode file

2068 Lab function failed Corrupt fake time file - missing number

2070 Unknown software error Semaphore mismatch

2071 Software failure Data storage failure

2072 Standard save failed Std save failed

2073 MLE Card data bad MLE Card data bad

2074 Master lot save failed Master Lot Data save failed

2075 Configuration data not found No config data found

2076 Software failure Main heap full, adding reserve heap
2077 Unknown software error Bad UCI size
2078 Assay data load failed Bad UCI read
2079 Unknown software error Semaphore mismatch
2080 Hardware failure Idata compaction failed
2081 Lab function failed Corrupt fake flinfo file
2082 Lab function failed Corrupt fake barcode file
2083 Software failure DML Startup file load error
2088 Software failure Unknown Heap error
2089 Hardware failure Data store failure
Warning: Standard @name@ is
2091 Standard @name@ is expired
expired
2092 Software Patch @name@ failed @ Setvar @name@ failed
2093 Software Patch @name@ failed DML Patch @name@ load error
2094 Software Patch @name@ failed DML Patch @name@ load error
2095 Software Patch @name@ failed DML Patch @name@ execution error
2096 Software failure Assay used ainfo that wasn't created
2097 Software failure Error in assay data

2098 Software failure Assay not found

2099 Copy failed, aborting Copy failed during backup

2100 Copy failed, aborting Copy failed during restore
2101 Copy failed, aborting RT config restore failed

2102 Data card is missing, empty, or corrupt Data card is missing, empty, or corrupt.

Card is not a valid backup set.

2103 Card is not a valid backup set.
Aborting.
2104 Software failure Internal BAP software error

2105 BAP Card data save failed BAP Protocol hunk save failed

2106 BAP Card data save failed BAP Assay hunk failed
2107 BAP Card data save failed BAP Patch hunk save failed
2108 BAP Card data save failed BAP Kill hunk save failed
2109 BAP Card data save failed BAP Hunk is unknown data type
2110 Unable to change language Unable to change language
2111 Unable to load helpfile Unable to load helpfile
2112 Assay data load failed Assay data missing
2113 Error saving dose unit selection Error saving dose unit selection

2114 Master lot save failed Master Lot info save failed

2115 Master lot save failed Master Lot info save failed

Cannot start section @sec@ - System

2116 Cannot start section - System Problem
Problem @err@

Cannot start section @sec@ -

2117 Cannot start section - Scanner Problem
Scanner Problem @err@

2118 Warning - LIS Validation Queue Full Warning – LIS Validation Queue Full

2119 Warning - LIS Upload Queue Full Warning – LIS Upload Queue Full
 Data card is missing, empty, or Interference from the barcode reader
2120
corrupt. during the software update.

2121 Error, wrong type of card Wrong card

Data card is missing, empty, or

2122 Bad card
corrupt.

2123 Error, wrong type of card Wrong card

Interference from the barcode reader

2124 Error, update failed [@err@]
during the software update.

2125 Software failure No room in std pool

2126 Software failure No room in std pool
2127 Normal Range load failed Failed reading NR file
2128 Normal Range save failed Failed saving NR file
New LIS Results have been discarded
2129 LIS results punted
due to full queues
Unable to complete LIS upload of
2130 Unable to send message
results
Unable to complete LIS / Gateway
2131 Unable to communicate with LIS host
upload of results
2132 Standard load failed Standard file open failed
2133 Standard load failed Standard CTOR failed
2134 Software failure Too many Standards
2135 Assay load failed Protocol not found at assay startup
2136 Software failure Out of range control point requested

2147 MLE Card read failed MLE Card read failed

2148 general MLE data entry error - call bMx TOS Sheet Error

2149 TOS Sheet data bad TOS Sheet Error

2150 general TOS sheet data entry error Code not used

2151 Master Lot Data curve data bad Master Lot Data curve data bad

2152 Master Lot obsolete Master lot without CRC characters

Error on scenario removing data in PTC
2153 Internal error : delete data
support
Error in compressing assay for PTC
2154 Internal error : compress assay
support
2155 Internal error : save assay Error in saving assay for PTC support
Error in saving assay for PTC support :
2156 Internal error : save assay
specific case of saving “T_UAC” file

2157 Internal error : save protocol Error in saving protocol for PTC support

Error in compressing protocol for PTC

2158 Internal error : compress protocol
support
2159 Unknown type of data Type of data bad for PTC support
Non valid parameter data for Assay Error on scenario check missing protocol
2160
@san@ (@uac@) in PTC support
Error on scenarios Check assay sharing
Non valid parameter data for Assay
2161 calibration, Check main assay – sub
@san@ (@uac@)
assay
PTC update not successful. The Error on scenario Check PTC support
2162
system has to be restored flag in PTC support
2164 Unexpected MLE scan error Unexpected MLE scan error
2165 Out of memory Out of memory
2166 Invalid MLE format Invalid MLE format
MLE does not match any registered MLE does not match any registered
2167
assay assay
New Quality control results have been New Quality control results have been
2168
discarded due to full queues discarded due to full queues
 Action

Replace VIC

Verify compatibility of VIC software and Boot EPROMs

Call bioMérieux
Verify compatibility of VIC software and Boot EPROMs
Replace Printer Board. Verify compatibility of VIC software
and Boot EPROMs
Call bioMérieux
Call bioMérieux
Call bioMérieux
Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux
Call bioMérieux
• Reload Assay and Protocol Software
• Try a different Software Card
• Replace VIC Board
Replace SRAM Card battery (SRAM Card not currently
used)
Replace SRAM Card battery (SRAM Card not currently
used)
• Reload Assay and Protocol Software
• Try a different Software Card
• Replace VIC Board
Install Thermal printer paper
• Enter 6263 on the Keypad and run Int. Print Test
• Verify +24 VDC Printer voltage
• Replace Printer Board or Replace VIC board
• Cycle power (data will be lost)
• Verify +24 VDC Printer voltage
• Replace Printer board
Replace Printer Board

Install printer paper

• Check cable connections to external Printer

• Check Printer
• Replace Printer
• Check cable connections to external Printer
• Check Printer
• Replace Printer
Retry

Retry

Retry

Retry

Retry

• Reload Assay and Protocol Software

• Try different Software Card
• Check cable connections

Retry

• Reload Protocol Software

• Try a different Software Card
• Replace VIC Board
Retry
Retry
• Retry
• Check for Scanner Error 119
• Retry
• Check for Scanner Error 121

Retry

Retry

Retry
Retry

Retry

Retry

Retry

Retry

• Reload Assay and Protocol Software

• Try a different Assay Card
• Replace VIC Board

Call bioMérieux
• Reload Assay and Protocol Software
• Try a different Assay Card
• Replace VIC Board
Call bioMérieux
• Reload Protocol Software
• Try a different Assay Card
• Replace VIC Board
Call bioMérieux

Check for Section (Incubator) error

• Reload Assay and Protocol Software

• Try a different Assay Card
• Replace VIC Board

Retry

Check for Section (Incubator) error

Check for Section (Incubator) error

Call bioMérieux

Check for Section (Incubator) error

Retry
Call bioMérieux
Call bioMérieux

Call bioMérieux

Call bioMérieux
Replace the VIC Board
• Delete oldest Standard
• Re-run Standard
• Replace the VIC Board
• Manually enter Master Lot Data
• Re-enter Master Lot Data
• Replace barcode Reader
• Call bioMérieux
• Delete oldest Master Lot Data
• Re-enter Master Lot Data
• Manually enter Master Lot Data
• Replace barcode Reader
• Call bioMérieux
Replace U26 on VIC Board
Cycle power at first opportunity
Call bioMérieux
Call bioMérieux
Call bioMérieux
Replace the VIC borad
Call bioMérieux
Call bioMérieux
Call bioMérieux
Call bioMérieux
Backup all idata and replace VIC Board
Warning: Standard for assay has expired
Rerun Standard for assay
Call bioMérieux
Call bioMérieux
Call bioMérieux
Call bioMérieux
Call bioMérieux
Call bioMérieux
• PTC (Protocol) out of date
• Load latest version of Protocol
Hardware Problem. Replace VIC Board
Hardware Problem. Replace VIC Board
Hardware Problem. Replace VIC Board

Replace Data card

Call bioMérieux

Hardware Problem. Replace VIC Board

Hardware Problem. Replace VIC Board
Hardware Problem. Replace VIC Board
Hardware Problem. Replace VIC Board
Hardware Problem. Replace VIC Board
Hardware Problem. Replace VIC Board
Hardware Problem. Replace VIC Board
Call bioMérieux
Call bioMérieux
PTC (Protocol) out of date
Hardware Problem. Replace VIC Board.

• Delete oldest Master Lot entry

• Re-enter Master Lot Data
• Manually enter Master Lot Data
• Load latest Software Update
• Replace barcode Reader
• Call bioMérieux Engineering

• Check for Scanner Error Codes

• Check for Section Error Codes
• Call bioMérieux
• Check for Scanner Error Codes
• Check for Section Error Codes
• Call bioMérieux
Validate LIS Results! - Results Menu
• Problem with LIS connection!
• Check cabling
• Never connect or disconnect the barcode reader when
MINI VIDAS is switched ON, as this could damage the
instrument.
- Turn OFF the MINI VIDAS
- Disconnect the barcode reader
- Insert software card
- Switch ON MINI VIDAS
- Start the software and update again (see chapter
"Update the Software")
- Turn OFF the MINI VIDAS
- Remove the software card
- Reconnect the barcode reader to the Diagnostic port
- Switch ON MINI VIDAS
Note: For further information on barcode reader
installation, refer to the User's Manual

• Check Card - Not S/W or Protocol update

• Insert correct card and retry
• Replace VIC Board
• Check Card - Card is bad
• Replace card
• Retry update
• Replace VIC Board
• Check Card - Not S/W or Protocol update
• Insert correct card and retry
• Replace VIC Board

• Never connect or disconnect the barcode reader when

MINI VIDAS is switched ON, as this could damage the
instrument.
- Turn OFF the MINI VIDAS
- Disconnect the barcode reader
- Insert software card
- Switch ON MINI VIDAS
- Start the software and update again (see chapter
"Update the Software")
- Turn OFF the MINI VIDAS
- Remove the software card
- Reconnect the barcode reader to the Diagnostic port
- Switch ON MINI VIDAS
Note: For further information on barcode reader
installation, refer to the User's Manual

Call bioMérieux
Call bioMérieux
Call bioMérieux
Call bioMérieux
• Problem with LIS connection!
• Check cabling
• Problem with LIS connection!
• Check cabling

Check cabling, restart host

Call bioMérieux
Call bioMérieux
Delete some Standards
PTC out of date. Load latest PTC Card.
Call bioMérieux
• Check MLE card
• Card loose in holder
• Enter MLE Data manually
• Check Barcode Reader alignment

Call bioMérieux

Customer should not use TOS Entry Screen

Customer should not use TOS Entry Screen
• Check MLE card
• Card loose in holder
• Enter MLE Data Manually
• Check Barcode Reader alignment
Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux

Call bioMérieux
Call bioMérieux
Call bioMérieux

Call bioMérieux

Call bioMérieux
 WINDOWS 10
Login Password Windows Group remarks
Dynamic password expiring on
bmx_admin Administrator FSE account
the following month
db2bmx Db2_Bmx Administrator FSE account
Lab_Admin -
To be changed at first login and Customer account
LabAdmin Administrator
then periodically

bmx_remote NA NA Does not exist anymore

temp_admin NA NA Does not exist anymore
LabSuper NA NA Does not exist anymore
LabTech NA NA Does not exist anymore

WINDOWS 7
Login Password Windows Group remarks
Dynamic password expiring on
bmx_admin Administrator FSE account
the following month
db2bmx Db2_Bmx Administrator FSE account
Dynamic password expiring on
bmx_remote Administrator FSE/FAS account
the following month
Dynamic password expiring on
temp_admin Administrator FSE account
the following hour
LabAdmin Lab_Admin Administrator Customer account
LabSuper Lab_Super User Customer account
LabTech Lab_Tech User Customer account

VIDAS Software
Remark
Same login and password to log in Windows and to log in VIDAS Software. Auto log is used to log in
VIDAS Software

BCI link
Refer to users and groups set in bioMérieux User Management software

Router checkpoint 1000

IP address Login Password remarks

GCSPortal ►
Homepage►Resources
►
192.168.168.254 admin BMX_ROUTER_PWD Password Generator
►CHECK POINT
ROUTER 500&1000n
Passwords.pdf
 Check Point 730 Appliance
IP address Login Password remarks

GCSPortal ►
Homepage►Resources
►
https://my.firewall:4434 or
bmx_admin BMX_ROUTER_PWD Password Generator
192.168.168.254:4434
►bioMérieux Standard
Devices Default
Password Version 1.7

RP5810 Bios & Boot Order Access

Password remarks

For RP5810 in Windows 7 or in

Windows 10
For RP5800 only in Windows 10
b1oMerieux
This password is used when
entering the Bios to change the
boot order, for example to boot
on USB drive.
CURRENT VERSIONS - SW and Documents

MINIVIDAS VIDAS Industry

MAR 4206 MAR 4143
Rev.A Rev. 2
Service Manual Ref.161150-1382 Ref.4501-2229
User SW V.5.6.1 V.4.10
version
Versions

Master DVD Ref. 423258

(RP5810), 423256
Master or Flashcard ref. 423117 (RP5800), 423296
update (standalone), 423349
(VRC Kit)

PC/Operating RP5810/W10
N/A
System RP5800/W10
 Vidas Clinical
MAR 2407
Rev. 2
Ref.4501-2229

V.4.7.1

Master DVD ref. 421408

(RP5810)

RP5810/W7
RP5800/W7
Revisions Table - Vidas-miniVIDAS Troubleshooting file

Revision Date Tabs Reason of the modification

1 2-Apr-19 ALL Creation