NPS Troubleshooting

7/25/2019 NPS Troubleshooting

1/28

TROUBLESHOOTING

NPS 25 -50 SYSTEMS

Nov 2009


2/28

NPS TroubleshootingManual Version 1109

Table of Contents I

1

Log Reporter (LogRep)..................................................................................1

2 Error Codes and Messages...........................................................................2

2.1

Error messages...............................................................................3

2.2 Module errors..................................................................................3

2.3 Communication errors.....................................................................4

3 Observed Errors and Corrective Action .........................................................5

3.1 Liquid handling...............................................................................5

3.2 Robotic handling ............................................................................6

4

Firmware................................................................................................... ....7

4.1 Validating firmware parameters ......................................................7

4.2 Firmware and parameters.............................................................10

4.3 Troubleshooting corrupted firmware configuration........................10

4.3.1 Examples of module name window...........................11

4.3.2 Other module names.................................................12

4.3.3 File device.dat ...........................................................12

4.4 Procedure to restore a correct FW parameter configuration..........15

4.4.1 Software procedure....................................................15

Table of Contents

4.4.2 Emergency procedure.................................................15

4.5 Communication error while reading X-Util FW parameters............16

5 Z-motor and Controller Board .........................................................................17

5.1

Motor does not initialize ..............................................................

....

17

5.2 Motor moves in negative direction with positive values ...................18

5.3 Motor check .....................................................................................18

5.4 Controller board check.....................................................................19

6 PipettingArm ................................................................................................19

6.1 Blocking unused valve port ..............................................................19

6.2 Running pumps after accidentally drying out..................................20


3/28

NPS Troubleshooting Manual Version 1109

Table of Contents I I

7 Handler Arm.................................................................................................21

8

Liquid Detection ...........................................................................................21

8.1 Z-index move special setting in X-Util.........................................21

8.2 Faulty flat band cable can cause motor failure ..............................22

9 USB / CAN-bus.................................................................................. ..........22

10 Special Service Equipment..........................................................................24

11 How to change a needle................................................... .....................25


4/28


Troubleshooting

1 Log Reporter (LogRep)

When NPSruns under X-Util or X-AP, log files are automatically generated andstored in the X-AP\log directory. The last 99 logs are stored, numbered sequentially

n the system loops and overwrites the files,

tedious withouthaving an adequate tool.

ogRep.exe" which is automatically

en with" displays the following window:

from "SIAS_IO01" to "SIAS_IO99". Thestarting with "SIAS_IO01".

The size of the log file depends on the length of the run and may be severalmegabytes! Opening such a file to investigate module errors or flags is

X-AP 1.1 and newer versions include a tool called "L

installed in the main X-AP directory.LogRep is a file viewer containing different filters to sort selectively and display loggedinformation. To configure LogRep as the default viewer, a right click on a log file opensa context menu where "Op

Figure 1 Choosing "Log Reporter Application"as the default application for log files

Note: If the procedure described above fails, it may help to also press the shift key while right clicking the log file name.

The following examples show a display of selected logged errors. It is possible tosearch for a specific string, print or compare log files.

Troubleshooting 1


5/28


Figure 2 Warnings in the "LogReporter" window

Troubleshooting 2

Reporter" windowFigure 3 Errors in the "Log

This tool generates use r systematic support. A shot of summarizederrors, or even the complete log file can be mailed for further analysis.

2 Error Codes and Messages

aredescribe hapter.

When reporting a malfunction or asking NOVACYTfor assistance, a precise description of theproblem should already be available, including the exact error code, module

corrective action.

Error codes and messages are displayed in the run list and during run time.

The following sections describe the errors and give some assistance locating the cause

list every ror. In this case, we rely on the

judgment and professionalism of the trained service engineer.

ful information fo

The causes of many operating problems can be identified and corrected by the user.Failures are displayed on the computer screen as error codes and messages which

d in this c

information and the attempted

and possible remedy. Although this information is comprehensive , it is impossible topotential cause and remedy for each er


6/28


2.1 Error messages

If an error occurs during the run time of the instru nalert box on the monitor. Errors origin

theNPS

are displayed with the name of the module that generated the error.

ment, error codes are displayed in aating from malfunction of individual modules of

Figure 4 "Module Error" window

Line / button Explanation

First Type of error and the related module ID

Second Action:State: State information (same as in module

Error numbes

Error: rcreen)

Abort Aborts the run

Retry Retries the last action

Ignore Ignores the error

Help Displays help information

Note: For the complete error list please refer to the X-AP "error.ini" file located inc:\XAP.

2.2 Module errors

Note: For specific information relating to your NPSconfiguration, please refer to"error.ini" located in the XAP directory.

Type of error Value Explanation Causes

Syntax error at module The telegram is not correct Software error

Wrong configuration

Module error at module 0100 Initialization failed (no block found).

The module has not been initialized.

Mechanical problem

Sensor not found

Electronics error

0200 Movement blocked Mechanical obstruction

Troubleshooting 3


7/28


Troubleshooting 4

2.3 Communication errors

Type of error Explanation Causes

Unknown module error An unknown error has occurred Error not defined on "error.ini"

Error addressing module The module can not be addressed Faulty electronics

Module firmware error

Wrong configuration in "siascfg.ini"

Cables not properly connected

Error sending to module

Module firmware error

y connected

The telegram can not be sent to themodule

Faulty electronics

Cables not properl

Illegal message from module The module sends incorrect telegram Firmware error

Active timeout at module dule does not complete the Timeout time too short

d of the module too slow

Wrong configuration in "siascfg.ini"

The moaction in a given time

Spee

Software error

Electronics error

CAN error CAN dongle not installed properly

Software error reboot computer

CAN-bus does not work properly

Driver for the CAN-bus faulty

Unable to create CAN thread re errorSoftware can not create a CAN thread Softwa

Message answer timeout at module Faulty electronics

e PC

e configuration

The module does not answer in thegiven time

Firmware error

Instrument disconnected from th

Wrong connection cabl


8/28


Troubleshooting 5

3 Observed Errors and Corrective Action

3.1 Liquid handling

Observation Explanation, remedy, actions

Needlemisses target (Novastick,etc.)

s on the worktable and rack configuration in MachineCheck rack positionsetup.

Run X/Y/Z-random test to see if the drive is losing steps.

Drops form on end of tip Tighten the liquid system connections.

Clean the needlewith an alcohol impregnated lint free tissue.

Needledoes not detect liquid

here is good contact between the bottom of the sampledeck.

flushed.

Run the liquid detection test using Sias racks.

Check for air/liquid leakage at tips or tubing.

Check that distilled or de-ionized water is used as system liquid.

Check that the needleis correctly installed.

Check to see that tcontainer and the surface of the

Check that system is properly

Needledetects "air" as if it were liquid Liquid detection is too sensitive. Run liquid detection test.

Check connection between needleand LLD block.

Check liquid detection flat band cable.

Erroneous CV (Coefficient ofvariation) or poor precision; the CVof a previously optimized protocol

becomes unreliable

manually remove the

d verify that the liquid volumes are at least 10%

ck that all liquid connections are tight and leak-free.

y the acceptable performance of equipment other than the Xantus, e.g.,scale, particle counter or photometer and reagent involved in the test.

tection test. If the results are acceptable, check the precision

rs in X-AP software.

If foaming is observed in the sample or reagent liquid,foam or increase the number of submerge steps in the test setup.

Check for tip damage or air bubbles in the liquid system.

If syringe pumps are usesyringe volume.

Che

Verif

Run the liquid deparameters of the assay with poor CV.

If the problem persists adjust the liquid paramete

Air bubbles build up in tubing

.

Line filters are not correctly si tting on the bottom of the system liquid container

Check spacers are correctly positioned and that the l iquid container is full

Carry-over of samples or reagents Check for tip damage or insufficient tip wash.

Check the submerge steps value.

The system fluid can be 0,2% Decon solution to make the tip wash moreefficient, however this may affect results when using coated plates.


9/28


Troubleshooting 6

3.2 Robotic handling

Obs tierva on Explanation, remedy, actions

Problem w

G- o

rotating due to the hold currentns, there is an angular acceleration

g. a deep well plate (DWP)., just due to the combination

Corrective action:

Start X-Util and decrease the Y-ramp from 500 to 300 and the R-ramp from600 to 400. Find the correct parameters and change the corresponding values

r and Y-motor.

e first the current parameters in a"AllPar_ddmmyy.dat.dat" file where mm stands for month, dd for day, yy foryear.

Change reserved parameters 1 - 2 - 3 and 4 to "0 - 0 - 0 - 200"

Change precision to -2 units, Change error limit to 10.

ith G- or R-motor R-motor: The plate may be offset whenparameters in the firmware. When it tur

r R-motor overheats that may alter positioning if the plate is heavy e.This might also occur with DWP without rotatingof X- and Y-movements.

in the siascfg.ini for handler X-moto

Before changing values, always sav

G-motor can not be initialized with atime out error

G-motor turns unnecessarily longuntil a mechanical block occurs

The problem disappears when G-motor is cool

The normal gripping movement isusually not affected

High friction warms the motor/pulley and softens the glue (Loctite638). Theinner assembly is composed of 2 pulleys, one mounted on the Motor axis andthe other mounted on a gear, which moves the 2-toothed racks.

Corrective action:

Replace the handler module.


10/28


Troubleshooting 7

Caution

An incorrect sequence of action while updating or changing firmwareparameters might result in an unstable firmware configuration and in theworst case it can lead to an unusable instrument.

ters are vital information for the instrument. Only NOVACYTineers are authorized to modify these values and

even then only when instructed to do so by NOVACYT.

Unauthorized changes will invalidate warranty and releases NOVACYTfromany responsibility.

4.1 Validating firmware parameters

The valid firmware parameter set for each instrument is produced at the time theinstrument was built and is burned on the CD delivered with the instrument.

The "AllPar.dat" file containing all parameter settings is located in the FW subdirectoryby default. Sias suggests renaming this file to "AllPar_Original.dat". Whenever a

backup of the instrument parameters is necessary, e.g. in case of a modulereplacement, the default name "AllPar.dat" should be used. This file will always be thecurrent one.

llPar_ddmmyy.dat.

Firmware parametrained and certified eng

4 Firmware

Note: Screenshots in this section refer to "sias_io.dll" version 0.1.7.7; X-Util version0.1.7.5 and older, firmware version 0.21b2.

A pdf file containing screenshots of firmware parameters is usually handed out duringhardware training courses. This file should never be used as reference but it can be

hen used as example!helpful wIf in doubt, always contact Sias for the latest valid parameters.

Example of "Modul_Info" screen in X-Util, each module is listed with the standardth


11/28


Correct configuration/display

information.Check that all modules are listed and that the 9 column contains the"Module type info".

Troubleshooting 8

Figure 7 "Modul_Info" window

No Explanation

1 Start ad dress

2 Module name

3 Module status flag:initialized; P = prepared; A = active; W = warning; E = error; odes = module specificD = detected; I = other c

4 C, 0.1 l)Module position in 1/10 of units (i.e.: 0.1 mm, 0.1 degree, 0.1

5 Module type info (first 4 digits)

6 re type (last 2 digits): 04 = DC motor; 10 = pump; (BB1 V1.0, BB2 V1.0, .0 )05 = DC motor; 11 = pump; (MCB BB1 V2 X-board V 2.11 )

Firmwa

X-board V 1.0, MCB BB2 V2.0,

7 F are versionirmw

8 Build

9 serial num 2 digits)Module ber for CAN-bus (first 1

10 PCB channel number for sub m 2 digits): 01 - 04odules (last

1 27

43 6 8 9105


12/28


Troubleshooting 9

Figure 8 "Move Modul [YMotor1]" window

Incorrect configuration/display

If t hile X Util is starting up, corrupted informationmight be displayed with incomplete module list and missing module type info.

In o for address 31 is missing, resulting in aco

he instrument is switched off and on w

the example below, the module type infrrupted "Modul_Info" list!

Figure 9 "Modul_Info" window

Figure 10 "Move Modul [YMotor1]" window

n

Motor steps to perform singlemovements in relative orabsolute mode.

Parameter setup scree

Missing information


13/28


Troubleshooting 10

Note: Some firmware parameter windows pop up also, if the corresponding ocx-fileis missing or not registeredExecute the batch file "RegAll" in C:/XAP/ocx.

4.2 Firmware and parameters

Note: This section describes firmware parameters, not firmware versions. Do notconfuse firmware download and parameter setup!

Firmware download

ersion withoutchanging the firmware parameters. As the same firmware goes in different modules,i.e. DC motors, it makes sense to use the multi-download option of the firmware menu.

Firmware parameter setup

fthe specific

,

Note: The parameter "MultiSend" button should never be used in the field, as it

A firmware download allows you to upgrade the current firmware v

A firmware parameter setup changes the current setting of a module independently othe firmware version. The setup contains the address of the modules andvalues, which make the difference between a Z- and a Y-motor; i.e. liquiddetectiondefault direction of the motor, error limits, home offsets.

would send the complete content of the current window to all other selectedias production but not for service!modules! This is used in S

4.3 Troubleshooting corrupted firmware configuration

Please refer to the following list as a reference for the correct address and modulenames for NPS Systems.

ase refer to the following list asmes for NPSsystems.

Address #

HEX DEC Module name Arm #

11 - 18 17 - 24 Micro-pump devices

21 - 28 33 - 40 Z-motor Pipetting arm #1

31 - 38 49 - 56 Y-motor Pipetting arm #1

51 81 X-motor Pipetting arm #1

52 82 X-motor Pipetting arm #2

53 - 5A 83 - 90 Handler Handler arm

5B 91 Density Housing


14/28


Note: In X-Util, the addresses are displayed in hexadecimal; in X-AP in decimal

The "Module type" info listed in the 9 column of the "Modul_Info" window comes fromthe "Xutil.ini" file. You can refer to it to identify the right module type.

th

Figure 11 "Edit Modul Names connected Modules" window

Troubleshooting 11

[ModulTypeData]

0005=2DC-Motor (new name)0010=2DCPump (old name)

yringe pump)

4. e window

Th :C:\ it Module Names/Addresses

0003=2DC-Motor

0004=2DC-Motor (old name)

0011=2DCPump (new name)

0018=StepPump

001C=StratecPump (Stratec s

0020=2StepMotor

0030=BCRack

0040=

3.1 Examples of module nam

ese windows are displayed fromXAP\XUTIL and /Command/Ed


15/28


4.3.2 Other module names

When the box "Only connected Modules" is not checked, additional modules notlayed.present on the instrument, can be disp

Figure 12 "Edit Modul Names all modules" window

case of a second shaker.Note: Address 73 should be used in

4.3.3 File device.dat

This file is located in the X_AP\Data sub-directory, and contains the module names,

The following "device.dat" file can be used as a reference, but of course the serialnumber of the modules will be different. Y- and Z-motors have nearly identical serialnumbers

evice.dat basic file:

000001BEA06A01,013,Pump3

0 0

0 0

000006FAD75F00,,

000001A6027001,,

0 0000006FB13C801,021,ZMotor1

0 0

0 0

0 0

0 0

0 0

000006FAD76B01,,

000006FB13C800,031,YMotor1

0 0

00 0

00000

000001A64AC100,,

000001BEA06800,,

000006FAD76B00,,

000001A64AAF00,051,XMotor1

000001A64ABE00,052,XMotor2

serial numbers and addresses of the hardware detected by the system.

, only the last digit is different.

D

000001BEA06A00,011,Pump1

000006FB18DA00,012,Pump2

000 6FB18DA01,014,Pump4

000 1A6027000,,

000 6FAD75F01,,

000 6FAC65E01,022,ZMotor2

000 1A5E45F01,023,ZMotor3

000 6FACC1401,024,ZMotor4

000 1A64AC101,,

000 1BEA06801,,

000 6FAC65E00,032,YMotor2

00 1A5E45F00,033,YMotor3

6FACC1400,034,YMotor4

Troubleshooting 12


16/28


Troubleshooting 13

0

000006FACC2800,05A,GripperR

0

00000

000001A6565C01,,

0

Not

00006FACC2801,055,GripperG

00001BEA06901,054,GripperZ

1BEA06900,053,GripperY

00001A6565C00,,

e: For each serial number there are 2 sub modules, the extension "0" stands forY-motor while the extension "1" stands for Z-motor. For a pump assemthere is a micro-pump and a valve per serial number.

bly

Extra lines

ve everd by the corresponding instrument.

The found in a working configuration in addition to the first oneliste that boards were exchanged on that instrument.

Not a R&D instrument where many modules have been

It is likely that the "device.dat" contains extra lines and it seems that some info isduplicated. In fact the file is setup as a log file displaying all the modules that habeen identifie

following lines wered before. It means

e: This file originates fromexchanged!

000001A64AE500,011,Pump1

000006FAF73600,,

000006FAFC8600,,

000001A5E46E01,021,ZMotor1

000001A6026701,022,ZMotor2

000001A5DE1401,023,ZMotor3

6E001,,

0 0

0 0

000001BEA06600,034,YMotor4

000001A606E000,,

0 0

0 0

1,XMotor1

000001A5DE3200,053,GripperY

000001A5DE3201,054,GripperZ

D01,,

000001A6026D00,,

Note: The order of the modules is not important as the software only checks if a

000006FAF22400,012,Pump2

000001A64AE501,013,Pump3

000006FAF22401,014,Pump4

000006FAF73601,,

000006FAFC8601,,

000001BEA06601,024,ZMotor4

000001A60

000001A606E301,,

000006FAD20601,,

000001A5E46E00,031,YMotor1

000 1A6026700,032,YMotor2

000 1A5DE1400,033,YMotor3

000 1A606E300,,

000 6FAD20600,,

000006FACBF300,05

000006FAC06400,052,XMotor2

000001A64AEE00,05A,GripperR

000001A606F200,,

000001A606F201,,

000001A6026

detected serial number is listed in this file or not.


17/28


Example of correct info window for channel #1

Module name originating frommodule assignment

Both level sensor modes arechecked for sensing info

Pipetting channel #1

Figure 13 "Modul Setup General" window

Troubleshooting 14

Figure 14 "Modul Setup YMotor1" window

Figure 15 ""Modul Setup ZMotor1" window

Y Module #1

Module type

Module address

Module scaling factor

Z Module #1

Special setting:

Liquid detection Inverted motor direction


18/28


4.4 Procedure to restore a correct FW parameter configuration

Caution

Restoring FW parameters should be done by NOVACYTtrained engineers only.

X-Util.

3. Select one of the displayed modules.

itialize it to get a visual confirmation of the selection.

Name" list.

eter window.

7. Click "Send".

parameters if necessary.

ck "Send".

12. Switch the instrument off.

eat these steps for all listed modules. In case some modules are not listed.

15. Save the parameters with "Save" button of the setup parameter window.

Save the file as "AllPar_ddmmyy_hhmm.dat" in the FW subdirectory.

4.4.2 Emergency procedure

. Then

19. Click "Exit".

4.4.1 Software procedure

1. Switch the instrument on.

2. Start

4. In

5. Compare the address with the one in the "Module

6. Correct the address if necessary in the param

8. Compare the other parameters with the one provided by Sias. Modify

9. Cli

10. Click "Close".

11. Exit X-Util.

13. Repinitially, they will be displayed after the first ones have been properly setup

14. Make a final check to be sure that each module (including pumps) can beaddressed (init, move ).

16.

17. Exit X-Util.

If you still have problems, you can physically disconnect all modules except oneidentify the only connected module by init/move and set the right address andparameters.

18. Click "Send".


2. Connect next module.

3. Switch the instrument on.

4. Repeat the procedure until all modules are setup correctly.

Troubleshooting 15


19/28


4.5 Communication error while reading X-Util FW parameters

Note: The following error does not indicate defective hardware.

Symptoms

The following error windows might appear after the instrument has been switched offwhile NPSand X-Util were still running.

First erro

Switch the instrument on again.

Start X-Util

Select the module by double clicking in the "Modul_Info" window.

r message:

Figure 16 "Communication Error" window

Click "Abort".

"Modul Setup ZMotor2" windowFigure 18

Troubleshooting 16

Figure 17

Acc age as many times as you have installed modules on theXan

X-Util window

ept this error messtus.


20/28


Diag

The soft om the module. Allfield lues of the "ini" file are set to "FFFF"(hex

Solution

The following window appears.

nosis

ware couldn't read the firmware parameter configuration frs which could not be filled in by the vaadecimal value "65535" decimal).

Click "Close".

Figure 19 X-Util "Save module parameter" window

Click "No".

Caution

It is extremely important to notsend the changes to the module yet!

Normal window appearance will come back as soon as you exit X-Util.

Mak u start X-Util again to scan the present modules.

5 d

5.1 t initialize

Symptom

The motor is not responding to initialization and there is no resistance when manuallymoving the pipetting head up and down. The cables and connectors are correctlyinstalled. The software settings ("siascfg.ini"), firmware, addresses and parameters arealso correct.

Solution

Does a swap of the controller board affect another motor?No Go to section 5.3 "Motor check"Yes Go to section 5.4 "Controller board check"

e s re Xantus is turned on and

Z-motor and Controller Boar

Motor does no

Troubleshooting 17


21/28


5.2 Motor moves in negative direction with positive values

Symptom

According to the firmware reverse flag status, the motor moves in the correct directionwhile initializing. But other movements are executed in the opposite direction!

Diagnosis

As the initializing has been executed properly, the controller board and motors areworking well. The problem is related to the parameters although the reverse flag hasn'tbeen set and the initializing move was carried out in the correct direction.

Cause

If the motor range is set too high, the firmware can not process the calculated data

prop

Solution

The motor range must be set according to the value provided in ini files on theinstallati

5.3 Motor

If a controllethe o

To detect a possible short circuit, the inner resistance of the motor must be tested:

f and unplug the power cable.

2. Disconnect the motor from the controller board and measure the resistancewith an ohmmeter as follows:

erly, which results in a negative value for the move direction.

on CD.

check

r board exchange does not bring any improvements, the fault must be inmot r.

1. Switch the instrument of

Troubleshooting 18

Figure 20 Z-motor connector and 6-pin header

the red wire of the Flat ribbon cable

3. Plug a 6-pin header into the motor connector.

4. Check the coil resistance of the motor (10 - 15 ) between pin 1 and 6. Referto motor table for details in section 11.6.3 "Reference motor and valve tables".

5. Check the resistance of the encoder (3 - 4 M) between pin 2 and pin 5.

Mark indicates pin 1 connected to

6-pin header

Pin 2

Pin 1

Pin 5Pin 6


22/28


Troubleshooting 19

5.4 Controller board check

If a motor exchange does not bring any improvements, the fault must be on the

2. Start X-Util.

3. Check the LED on the controller board. At power on and during operation it

cated in"X-AP\Data" subdirectory.

tart a text editor and open the "device.dat" file located in "X-AP\Data"

d to the appropriate modules; i.e.:3, address 33.

ox to identify new hardware.

otor3) and address (e.g. 23) from the

ame (ZMotor3) and address (23) will automatically be displayed.This means that the controller board has been recognized and that

14. Ensure the corresponding motor is connected and click "Identify": The motor

controller

6 Pipetting

6.1 Blocking unused valve port

NPS uses valves with three ports. One of them is not used and is blocked with a redcap. On Instruments with serial numbers below SN 1041 the red cap on the unusedport might be missed.

Instruments and spare valves should be checked within the next service. If blocking isnecessary, it must be done on the port nozzle which is neither labeled "IN" nor "NC".Gel-glue "Loctite Cyanocrilate Gel" must be used.

controller board. XSPB is a useful tool to check and to configure boards.

Controller board troubleshooting

1. Switch the instrument off and then on again.

flashes slowly (1Hz).

4. Check if the board is listed with its name during the module scan.

5. Exit X-Util.

6. Open Windowsexplorer and backup the "device.dat" file lo

7. Ssubdirectory.

8. Delete those line(s) which are relateZMotor3, address 23 and YMotor

9. Save the file and exit text editor.

10. Start X-Util.

11. Enter X-Util/Module Info. This displays a dialog b

12. Select the correct module name (e.g. ZMpop down menu in the "user defined field".

13. The module n

communication is established.

will move to and fro a few steps, like a shake movement.

15. Check the "Set on Module" box.

16. Repeat this procedure for the Y-motor 3 which is driven by the same

board.

Arm


23/28


Apply a little glue on the nozzle athe nozzle and wait a few second

s well as on the red cap. Put the cap completely overs until the glue is dry.

Unlabeled nozzle

Inlet port "IN"

Outlet port "NC"

Figure 21

6

Sealed nozzle

.2 Running pumps after accidentally drying out


2. Move the tips carefully over the waste position and refill the system liquidcontainer with distilled or de-ionized water.

3. Switch the instrument on. Start X-Util, select a micro-pump and enter:

a) Dispense 1000

b) Speed 2000

c) Ramp 1000

Figure 22 "Move Modul [PipPump]" window

4. Click "Init".

5. Click "Dispense" several times was the pump is priming, increase "Dispense" to 10000 and dispense a fewtimes.

hile checking if the pump is priming. As soon

Troubleshooting 20


24/28


Note: A dry system liquid filter might need one or two dispense sequencesbefore liquid comes through again. If the liquid system tubing remainsdry, inspect tubing connections and check for leaks.

6. Repeat the procedure for all other channels. When all pumps are primed,return to X-AP and flush normally.

7 Handler Arm

Actions on the handler

Adjusting the handler requires special skill and knowledge. Therefore actions on thehandler at the customer's site are limited to the following actions:

Tilt adjustments Exchange

e done at NOVACYTby authorized serviceengineers.

intenance actions on the handler may lead to

All other adjustments and actions must b

Note: Inappropriate adjustment and mathe loss of warranty!

8 Liquid Detection

8.1

In the "M nt to any module scannedby X-Util.

e

Z-index move special setting in X-Util

ove_Modul" window a low level command can be se

To move a module after initialization, at least one value must be entered into the movfield.

Figure 23 "Move Modul [ZMotor]" window

Troubleshooting 21


25/28


Troubleshooting 22

If "Speed" and "Ramp" fields are set to "0", the system uses the default values from thefirmware.

r, a selected "Index Move" for liquid detection uses the"Acceleratio t the submerge step!

Exa l

ove" option.

00 and "Acceleration" to 0.

4. Place the tip over a trough filled with tap water.

5. Click "Init" to initialize the Z-motor

6. Click "Move" until the tip detects liquid.

The system stops at meniscus level. If "Acceleration" is set to 20, the tip will be

submerged by 2 mm.

8.2 Faulty flat band cable can cause motor failure

B ) insulation is damaged, the motor controllermay report errors and the Z-axis may

loose steps.

at the FBC is fully inserted in the corresponding sockets.

ar k the FBC for any damage (susceptible points are protectedit.

USB / CAN-bus

9.1 Communication problems linked to USB-devices

Note: After a PC reboot the Peak CAN USB dongle flashes its red LED once,

Regarding the Z-moton" field to se

mp e

1. Enter a "Rel. move" of 150

2. Check the "Index m

3. Set "Speed" to 5

If the liquid detection flat band cable (Fboard, driving the corresponding motor channel,

C

1. Ensure th

2. C efully checw tape). If any stress marks are found, replaced

9

indicating that the dongle has been recognized by the PC BIOS.

Some PCs may encounter communication problems linked to Universal Serial Bus(USB) devices. Microsoftsupport provides the following information:

USB devices are not detected when you restart the computer.

USB devices are not detected after you resume the computer from hibernationor standby.

The computer uses 100% of the CPU time when you move the USB mouse.

The computer hangs when you resume from standby mode when a USBmouse is connected.

The computer takes a long time to start or resume when a USB device is

connected.


26/28


Troubleshooting 23

A yellow exclamation point with code 28 or 31 is displayed on a USB device indevice manager.

s USB 1.1 devices when yourcomputer resumes from hibernation, even though they are plugged into a USB2.0 capable port.

it may not indicate that the Peak CAN USB dongle isfaulty. But some settings and versions must be checked first.

ed in

inimal configuration:

SP 4

Checkin

If Peak C roblems occurmore freq d port than to anUSB 1.1

rt version can be checked in"Start/Settings/Control Panel/System/Hardware/Device Manager/USB Bus Controllers".

2.

If each USB output provide a current of 500 mA (minimum 350 mA) it is an USB V2.0 Hi-speed port,

USB 2.0 Hi-speed devices are detected a

If any of these problems occurs,

Checking the OS and the SP version

Operating system (OS) and service pack (SP) version can be check"Start/Settings/Configuration Panel/System/General.

M

MS Windows 2000 with

MS Windows XP with SP 2

g the USB port version

AN USB dongle firmware version 7.0 is used, communication puently when the dongle is connected to an USB 2.0 Hi-spee

port.

The USB po

1. Right click "USB Root Hub".

Click "Properties".

otherwise it is an USB 1.1 port.

"USB Root Hub Properties" windowFigure 24


27/28


Troubleshooting 24

Checking the dongle firmware version

o an USB 2.0 Hi-speed port, it is mandatory to use a donglen 2.8.

On request previous versions are updated free of charge.

can be checked in "Start/Settings/Control Panel/PcanHardware".

If the dongle is connected twith firmware versio

The firmware version

1. Right click "PcanHardware icon".

2. Click "Properties".

10 Special Service Equipment

10.1 Xantus(NPS)Service Programming Box XSPB

The Xantus (NPS) Service Programming Box XSPB is a small and easy to use programmingtool. It is used under X-Util together with a dongle to program Xantus boards.

For a detailed function description please contact NOVACYTSupport.

XSPB Specification

24 VDC input

CAN dongle connector

Long CAN-bus cable with board connector Green status LED

On/off switch

Figure 26 Xantus (NPS) Service Programming Box

Ordering details

Part # Description

150100 Xantus (NPS) Service Programming Box XSPB, including power supply unit (24 VDC/1 A)

Xantus (NPS) Service Programming Box

Power supply unit PSU

CAN dongle connector

CAN-bus cable with

board connector


28/28


This action could be realized directly by the Distributor following his formation.

To be made, follow the step hereafter, automate switch OFF:

Unscrew the screw maintaining slightly the needle (Screwdriver Torx 8)

11 How to change a needle

Lower the needle to clear the zone of the tubing positioned initially in theliquid detector box.

Documents

NPS Troubleshooting