TROUBLESHOOTING

NPS 25 -50

SYSTEMS

Nov 2009

NPS Troubleshooting Ma n ual

Versi on 1109

Table of Contents

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

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

2.1

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

2.2

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

2.3

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

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

3.1

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

3.2

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

Firmware .......................................................................................................7
4.1

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

4.2

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

4.3

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

4.4

4.5
5

4.3.1

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

4.3.2

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

4.3.3

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

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

4.4.1

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

4.4.2

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

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

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

Pipetting Arm ................................................................................................19

6.1

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

6.2

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

Table of Con tents

NPS Troubleshooting Manual

Versi on 1109

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

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

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

10

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

11

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

Table of Con tents

II

NPS Troubleshooting Manual

Versi on 1109

Troubleshooting
1

Log Reporter (LogRep)

When NPS runs under X-Util or X-AP, log files are automatically generated and
stored in the X-AP\log directory. The last 99 logs are stored, numbered sequentially
from "SIAS_IO01" to "SIAS_IO99". Then the system loops and overwrites the files,
starting with "SIAS_IO01".
The size of the log file depends on the length of the run and may be several
megabytes! Opening such a file to investigate module errors or flags is tedious without
having an adequate tool.
X-AP 1.1 and newer versions include a tool called "LogRep.exe" which is automatically
installed in the main X-AP directory.
LogRep is a file viewer containing different filters to sort selectively and display logged
information. To configure LogRep as the default viewer, a right click on a log file opens
a context menu where "Open with" displays the following window:

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 to

search for a specific string, print or compare log files.

Trou blesh ooting

NPS Troubleshooting Manual

Versi on 1109

Figure 2 Warnings in the "LogReporter" window

Figure 3 Errors in the "Log Reporter" window

This tool generates useful information for systematic support. A shot of summarized
errors, or even the complete log file can be mailed for further analysis.

Error Codes and Messages

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 are
described in this chapter.
When reporting a malfunction or asking NOVACYT for assistance, a precise description of the
problem should already be available, including the exact error code, module
information and the attempted 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
and possible remedy. Although this information is comprehensive , it is impossible to
list every potential cause and remedy for each error. In this case, we rely on the
judgment and professionalism of the trained service engineer.

Trou blesh ooting

NPS Troubleshooting Manual

2.1

Versi on 1109

Error messages

If an error occurs during the run time of the instrument, error codes are displayed in an
alert box on the monitor. Errors originating from malfunction of individual modules of
the NPS are displayed with the name of the module that generated the error.

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 screen)
Error: Error number

Abort

Aborts the run

Retry

Retries the last action

Ignore

Ignores the error

Help

Displays help information

Note:

2.2

Note:

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

Module errors

For specific information relating to your NPS configuration, please refer to

"error.ini" located in the XAP directory.

Type of error

Value Explanation

Syntax error at module

The telegram is not correct

Causes
Software error
Wrong configuration

Module error at module

0100

Initialization failed (no block found).

Mechanical problem

The module has not been initialized.

Sensor not found

Electronics error

0200

Trou blesh ooting

Movement blocked

Mechanical obstruction

NPS Troubleshooting Manual

2.3

Versi on 1109

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

The telegram can not be sent to the

module

Faulty electronics
Module firmware error
Cables not properly connected

Illegal message from module

The module sends incorrect telegram

Firmware error

Active timeout at module

The module does not complete the

action in a given time

Timeout time too short

Speed of the module too slow
Software error
Wrong configuration in "siascfg.ini"
Electronics error

CAN error

CAN-bus does not work properly

CAN dongle not installed properly

Driver for the CAN-bus faulty
Software error reboot computer

Unable to create CAN thread

Software can not create a CAN thread Software error

Message answer timeout at module

The module does not answer in the

given time

Faulty electronics
Firmware error
Instrument disconnected from the PC
Wrong connection cable configuration

Trou blesh ooting

NPS Troubleshooting Manual

3
3.1

Versi on 1109

Observed Errors and Corrective Action

Liquid handling

Observation

Explanation, remedy, actions

Needle misses target (Novastick,

etc.)

Check rack positions on the worktable and rack configuration in Machine

setup.
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 needle with an alcohol impregnated lint free tissue.

Needle does not detect liquid

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 needle is correctly installed.
Check to see that there is good contact between the bottom of the sample
container and the surface of the deck.
Check that system is properly flushed.

Needle detects "air" as if it were liquid Liquid detection is too sensitive. Run liquid detection test
.
Check connection between needle and LLD block.
Check liquid detection flat band cable.
Erroneous CV (Coefficient of
variation) or poor precision; the CV
of a previously optimized protocol
becomes unreliable

If foaming is observed in the sample or reagent liquid, manually remove the

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 used verify that the liquid volumes are at least 10%
syringe volume.
Check that all liquid connections are tight and leak-free.
Verify the acceptable performance of equipment other than the Xantus, e.g.,
scale, particle counter or photometer and reagent involved in the test.
Run the liquid detection test. If the results are acceptable, check the precision
parameters of the assay with poor CV.
If the problem persists adjust the liquid parameters in X-AP software.

Air bubbles build up in tubing

Line filters are not correctly sitting on the bottom of the system liquid container
Check spacers are correctly positioned and that the liquid 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 more
efficient, however this may affect results when using coated plates.

Trou blesh ooting

NPS Troubleshooting Manual

3.2

Versi on 1109

Robotic handling

Observation

Explanation, remedy, actions

Problem with G- or R-motor

R-motor: The plate may be offset when rotating due to the hold current
parameters in the firmware. When it turns, there is an angular acceleration
that may alter positioning if the plate is heavy e.g. a deep well plate (DWP).
This might also occur with DWP without rotating, just due to the combination
of X- and Y-movements.

G- or R-motor overheats

Corrective action:
Start X-Util and decrease the Y-ramp from 500 to 300 and the R-ramp from
600 to 400. Find the correct parameters and change the corresponding values
in the siascfg.ini for handler X-motor and Y-motor.
Before changing values, always save first the current parameters in a
"AllPar_ddmmyy.dat.dat" file where mm stands for month, dd for day, yy for
year.
Change reserved parameters 1 - 2 - 3 and 4 to "0 - 0 - 0 - 200"
Change precision to -2 units, Change error limit to 10.
G-motor can not be initialized with a
time out error
G-motor turns unnecessarily long
until a mechanical block occurs
The problem disappears when Gmotor is cool

High friction warms the motor/pulley and softens the glue (Loctite 638). The
inner assembly is composed of 2 pulleys, one mounted on the Motor axis and
the other mounted on a gear, which moves the 2-toothed racks.
Corrective action:
Replace the handler module.

The normal gripping movement is

usually not affected

Trou blesh ooting

NPS Troubleshooting Manual

Versi on 1109

Firmware

Note:

Screenshots in this section refer to "sias_io.dll" version 0.1.7.7; X-Util version

0.1.7.5 and older, firmware version 0.21b2.

Caution
An incorrect sequence of action while updating or changing firmware
parameters might result in an unstable firmware configuration and in the
worst case it can lead to an unusable instrument.
Firmware parameters are vital information for the instrument. Only NOVACYT
trained and certified engineers are authorized to modify these values and
even then only when instructed to do so by NOVACYT.
Unauthorized changes will invalidate warranty and releases NOVACYT from
any responsibility.

4.1

Validating firmware parameters

The valid firmware parameter set for each instrument is produced at the time the
instrument 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 subdirectory
by 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 module
replacement, the default name "AllPar.dat" should be used. This file will always be the
current one.
llPar_ddmmyy.dat.

A pdf file containing screenshots of firmware parameters is usually handed out during
hardware training courses. This file should never be used as reference but it can be
helpful when used as example!
If in doubt, always contact Sias for the latest valid parameters.

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

Trou blesh ooting

NPS Troubleshooting Manual

Versi on 1109

Correct configuration/display
information. Check that all modules are listed and that the 9 column contains the
"Module type info".
1

10

Figure 7 "Modul_Info" window

No

Explanation

Start ad dress

Module name

Module status flag:

D = detected; I = initialized; P = prepared; A = active; W = warning; E = error; other codes = module specific

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

Module type info (first 4 digits)

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

Firmware version

Build

Module serial number for CAN-bus (first 12 digits)

10

PCB channel number for sub modules (last 2 digits): 01 - 04

Trou blesh ooting

NPS Troubleshooting Manual

Versi on 1109

Parameter setup screen

Motor steps to perform single

movements in relative or
absolute mode.

Figure 8 "Move Modul [YMotor1]" window

Incorrect configuration/display
If the instrument is switched off and on while X Util is starting up, corrupted information
might be displayed with incomplete module list and missing module type info.
In the example below, the module type info for address 31 is missing, resulting in a
corrupted "Modul_Info" list!

Figure 9 "Modul_Info" window

Missing information

Figure 10 "Move Modul [YMotor1]" window

Trou blesh ooting

NPS Troubleshooting Manual

Note:

4.2

Versi on 1109

Some firmware parameter windows pop up also, if the corresponding ocx-file

is missing or not registered Execute the batch file "RegAll" in C:/XAP/ocx.

Firmware and parameters

Note:

This section describes firmware parameters, not firmware versions. Do not

confuse firmware download and parameter setup!

Firmware download
A firmware download allows you to upgrade the current firmware version without
changing 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
A firmware parameter setup changes the current setting of a module independently of
the firmware version. The setup contains the address of the modules and the specific
values, which make the difference between a Z- and a Y-motor; i.e. liquid detection,
default direction of the motor, error limits, home offsets.
Note:

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

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

4.3 Troubleshooting corrupted firmware configuration

Please refer to the following list as a reference for the correct address and module
names for NPS Systems.
Address #

ase refer to the following list as

Module name
HEX
DEC
mes for
NPS systems.

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

Trou blesh ooting

Density Housing

10

NPS Troubleshooting Manual

Note:

Versi on 1109

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

The "Module type" info listed in the 9th column of the "Modul_Info" window comes from
the "Xutil.ini" file. You can refer to it to identify the right module type.
[ModulTypeData]
0003=2DC-Motor
0004=2DC-Motor
0005=2DC-Motor
0010=2DCPump
0011=2DCPump
0018=StepPump
001C=StratecPump
0020=2StepMotor
0030=BCRack
0040=

(old
(new
(old
(new

name)
name)
name)
name)

(Stratec syringe pump)

4. 3.1 Examples of module nam e window

These windows are displayed from:
C:\XAP\XUTIL and /Command/Edit Module Names/Addresses

Figure 11 "Edit Modul Names connected Modules" window

Trou blesh ooting

11

NPS Troubleshooting Manual

Versi on 1109

4.3.2 Other module names

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

Figure 12 "Edit Modul Names all modules" window

Note:

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

4.3.3 File device.dat

This file is located in the X_AP\Data sub-directory, and contains the module names,
serial numbers and addresses of the hardware detected by the system.
The following "device.dat" file can be used as a reference, but of course the serial
number of the modules will be different. Y- and Z-motors have nearly identical serial
numbers, only the last digit is different.
Device.dat basic file:
000001BEA06A00,011,Pump1
000006FB18DA00,012,Pump2
000001BEA06A01,013,Pump3
000006FB18DA01,014,Pump4
000001A6027000,,
000006FAD75F00,,
000001A6027001,,
000006FAD75F01,,
000006FB13C801,021,ZMotor1
000006FAC65E01,022,ZMotor2
000001A5E45F01,023,ZMotor3
000006FACC1401,024,ZMotor4
000001A64AC101,,
000001BEA06801,,
000006FAD76B01,,
000006FB13C800,031,YMotor1
000006FAC65E00,032,YMotor2
000001A5E45F00,033,YMotor3
000006FACC1400,034,YMotor4
000001A64AC100,,
000001BEA06800,,
000006FAD76B00,,
000001A64AAF00,051,XMotor1
000001A64ABE00,052,XMotor2

Trou blesh ooting

12

NPS Troubleshooting Manual

Versi on 1109

000006FACC2801,055,GripperG
000006FACC2800,05A,GripperR
000001BEA06901,054,GripperZ
000001BEA06900,053,GripperY
000001A6565C01,,
000001A6565C00,,

Note:

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

Extra lines
It is likely that the "device.dat" contains extra lines and it seems that some info is
duplicated. In fact the file is setup as a log file displaying all the modules that have ever
been identified by the corresponding instrument.
The following lines were found in a working configuration in addition to the first one
listed before. It means that boards were exchanged on that instrument.
Note:

This file originates from a R&D instrument where many modules have been
exchanged!

000001A64AE500,011,Pump1
000006FAF22400,012,Pump2
000001A64AE501,013,Pump3
000006FAF22401,014,Pump4
000006FAF73600,,
000006FAFC8600,,
000006FAF73601,,
000006FAFC8601,,
000001A5E46E01,021,ZMotor1
000001A6026701,022,ZMotor2
000001A5DE1401,023,ZMotor3
000001BEA06601,024,ZMotor4
000001A606E001,,
000001A606E301,,
000006FAD20601,,
000001A5E46E00,031,YMotor1
000001A6026700,032,YMotor2
000001A5DE1400,033,YMotor3
000001BEA06600,034,YMotor4
000001A606E000,,
000001A606E300,,
000006FAD20600,,
000006FACBF300,051,XMotor1
000006FAC06400,052,XMotor2
000001A5DE3200,053,GripperY
000001A5DE3201,054,GripperZ
000001A64AEE00,05A,GripperR
000001A606F200,,
000001A606F201,,
000001A6026D01,,
000001A6026D00,,

Note:

The order of the modules is not important as the software only checks if a
detected serial number is listed in this file or not.

Trou blesh ooting

13

NPS Troubleshooting Manual

Versi on 1109

Example of correct info window for channel #1

Pipetting channel #1

Module name originating from

module assignment

Both level sensor modes are

checked for sensing info

Figure 13 "Modul Setup General" window

Y Module #1
Module type
Module address

Module scaling factor

Figure 14 "Modul Setup YMotor1" window

Z Module #1

Special setting:
Liquid detection
Inverted motor direction

Figure 15 ""Modul Setup ZMotor1" window

Trou blesh ooting

14

NPS Troubleshooting Manual

4.4

Versi on 1109

Procedure to restore a correct FW parameter configuration

Caution
Restoring FW parameters should be done by NOVACYT trained engineers only.

4.4.1 Software procedure

1.

Switch the instrument on.

2.

Start X-Util.

3.

Select one of the displayed modules.

4.

Initialize it to get a visual confirmation of the selection.

5.

Compare the address with the one in the "Module Name" list.

6.

Correct the address if necessary in the parameter window.

7.

Click "Send".

8.

Compare the other parameters with the one provided by Sias. Modify
parameters if necessary.

9.

Click "Send".

10. Click "Close".

11. Exit X-Util.
12. Switch the instrument off.
13. Repeat these steps for all listed modules. In case some modules are not listed
initially, 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 be
addressed (init, move ).
15. Save the parameters with "Save" button of the setup parameter window.
16. Save the file as "AllPar_ddmmyy_hhmm.dat" in the FW subdirectory.
17. Exit X-Util.
4.4.2 Emergency procedure
If you still have problems, you can physically disconnect all modules except one. Then
identify the only connected module by init/move and set the right address and
parameters.
18. Click "Send".
19. Click "Exit".
1.

Switch the instrument off.

2.

Connect next module.

3.

Switch the instrument on.

4.

Repeat the procedure until all modules are setup correctly.

Trou blesh ooting

15

NPS Troubleshooting Manual

4.5

Versi on 1109

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 off
while NPS and X-Util were still running.

Switch the instrument on again.

Start X-Util

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

First error message:

Figure 16 "Communication Error" window

Click "Abort".

Figure 17 X-Util window

Accept this error message as many times as you have installed modules on the
Xantus.

Figure 18

"Modul Setup ZMotor2" window

Trou blesh ooting

16

NPS Troubleshooting Manual

Versi on 1109

Diagnosis
The software couldn't read the firmware parameter configuration from the module. All
fields which could not be filled in by the values of the "ini" file are set to "FFFF"
(hexadecimal value "65535" decimal).
Solution
Click "Close".
The following window appears.

Figure 19 X-Util "Save module parameter" window

Click "No".
Caution
It is extremely important to not send the changes to the module yet!

Normal window appearance will come back as soon as you exit X-Util.
Make sure Xantus is turned on and start X-Util again to scan the present modules.

Z-motor and Controller Board

5.1

Motor does not initialize

Symptom
The motor is not responding to initialization and there is no resistance when manually
moving the pipetting head up and down. The cables and connectors are correctly
installed. The software settings ("siascfg.ini"), firmware, addresses and parameters are
also correct.
Solution
Does a swap of the controller board affect another motor?
Go to section 5.3 "Motor check"
No
Yes
Go to section 5.4 "Controller board check"

Trou blesh ooting

17

NPS Troubleshooting Manual

5.2

Versi on 1109

Motor moves in negative direction with positive values

Symptom
According to the firmware reverse flag status, the motor moves in the correct direction
while initializing. But other movements are executed in the opposite direction!
Diagnosis
As the initializing has been executed properly, the controller board and motors are
working well. The problem is related to the parameters although the reverse flag hasn't
been 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
properly, which results in a negative value for the move direction.
Solution
The motor range must be set according to the value provided in ini files on the
installation CD.

5.3

Motor

check

If a controller board exchange does not bring any improvements, the fault must be in
the motor.
To detect a possible short circuit, the inner resistance of the motor must be tested:
1.

Switch the instrument off and unplug the power cable.

2.

Disconnect the motor from the controller board and measure the resistance
with an ohmmeter as follows:
Mark indicates pin 1 connected to
the red wire of the Flat ribbon cable
Pin 1
Pin 5
Pin 6
Pin 2

6-pin header
Figure 20 Z-motor connector and 6-pin header

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. Refer
to 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.

Trou blesh ooting

18

NPS Troubleshooting Manual

5.4

Versi on 1109

Controller board check

If a motor exchange does not bring any improvements, the fault must be on the
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.

2.

Start X-Util.

3.

Check the LED on the controller board. At power on and during operation it
flashes slowly (1Hz).

4.

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

5.

Exit X-Util.

6.

Open Windows explorer and backup the "device.dat" file located in

"X-AP\Data" subdirectory.

7.

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

8.

Delete those line(s) which are related to the appropriate modules; i.e.:
ZMotor3, address 23 and YMotor3, address 33.

9.

Save the file and exit text editor.

10. Start X-Util.

11. Enter X-Util/Module Info. This displays a dialog box to identify new hardware.
12. Select the correct module name (e.g. ZMotor3) and address (e.g. 23) from the
pop down menu in the "user defined field".
13. The module name (ZMotor3) and address (23) will automatically be displayed.
This means that the controller board has been recognized and that
communication is established.
14. Ensure the corresponding motor is connected and click "Identify": The motor
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 controller
board.

Pipetting

Arm

6.1

Blocking unused valve port

NPS uses valves with three ports. One of them is not used and is blocked with a red
cap. On Instruments with serial numbers below SN 1041 the red cap on the unused
port might be missed.
Instruments and spare valves should be checked within the next service. If blocking is
necessary, it must be done on the port nozzle which is neither labeled "IN" nor "NC".
Gel-glue "Loctite Cyanocrilate Gel" must be used.
Trou blesh ooting

19

NPS Troubleshooting Manual

Versi on 1109

Apply a little glue on the nozzle as well as on the red cap. Put the cap completely over
the nozzle and wait a few seconds until the glue is dry.

Outlet port "NC"

Inlet port "IN"

Unlabeled nozzle

Figure 21

6 .2

Sealed nozzle

Running pumps after accidentally drying out

1.

Switch the instrument off.

2.

Move the tips carefully over the waste position and refill the system liquid
container 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 while checking if the pump is priming. As soon
as the pump is priming, increase "Dispense" to 10000 and dispense a few
times.

Trou blesh ooting

20

NPS Troubleshooting Manual

Note:

6.

Versi on 1109

A dry system liquid filter might need one or two dispense sequences
before liquid comes through again. If the liquid system tubing remains
dry, inspect tubing connections and check for leaks.

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

Handler Arm

Actions on the handler

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

Tilt adjustments

Exchange

All other adjustments and actions must be done at NOVACYT by authorized service
engineers.
Note:

8
8.1

Inappropriate adjustment and maintenance actions on the handler may lead to

the loss of warranty!

Liquid Detection
Z-index move special setting in X-Util

In the "Move_Modul" window a low level command can be sent to any module scanned
by X-Util.
To move a module after initialization, at least one value must be entered into the move
field.

Figure 23 "Move Modul [ZMotor]" window

Trou blesh ooting

21

NPS Troubleshooting Manual

Versi on 1109

If "Speed" and "Ramp" fields are set to "0", the system uses the default values from the
firmware.
Regarding the Z-motor, a selected "Index Move" for liquid detection uses the
"Acceleration" field to set the submerge step!
Example
1.

Enter a "Rel. move" of 150

2.

Check the "Index move" option.

3.

Set "Speed" to 500 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

If the liquid detection flat band cable (FBC) insulation is damaged, the motor controller
board, driving the corresponding motor channel, may report errors and the Z-axis may
loose steps.
1.

Ensure that the FBC is fully inserted in the corresponding sockets.

2.

Carefully check the FBC for any damage (susceptible points are protected
wit. tape). If any stress marks are found, replaced

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,
indicating that the dongle has been recognized by the PC BIOS.

Some PCs may encounter communication problems linked to Universal Serial Bus
(USB) devices. Microsoft support 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 hibernation
or 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 USB
mouse is connected.

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

Trou blesh ooting

22

NPS Troubleshooting Manual

Versi on 1109

A yellow exclamation point with code 28 or 31 is displayed on a USB device in

device manager.

USB 2.0 Hi-speed devices are detected as USB 1.1 devices when your
computer resumes from hibernation, even though they are plugged into a USB
2.0 capable port.

If any of these problems occurs, it may not indicate that the Peak CAN USB dongle is
faulty. But some settings and versions must be checked first.
Checking the OS and the SP version
Operating system (OS) and service pack (SP) version can be checked in
"Start/Settings/Configuration Panel/System/General.
Minimal configuration:

MS Windows 2000 with SP 4

MS Windows XP with SP 2

Checking the USB port version

If Peak CAN USB dongle firmware version 7.0 is used, communication problems occur
more frequently when the dongle is connected to an USB 2.0 Hi-speed port than to an
USB 1.1 port.
The USB port version can be checked in
"Start/Settings/Control Panel/System/Hardware/Device Manager/USB Bus Controllers".
1.

Right click "USB Root Hub".

2.

Click "Properties".

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

Figure 24

"USB Root Hub Properties" window

Trou blesh ooting

23

NPS Troubleshooting Manual

Versi on 1109

Checking the dongle firmware version

If the dongle is connected to an USB 2.0 Hi-speed port, it is mandatory to use a dongle
with firmware version 2.8.
On request previous versions are updated free of charge.
The firmware version can be checked in "Start/Settings/Control Panel/PcanHardware".
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 programming
tool. It is used under X-Util together with a dongle to program Xantus boards.
For a detailed function description please contact NOVACYT Support.
XSPB Specification

24 VDC input

CAN dongle connector

Long CAN-bus cable with board connector

Green status LED

On/off switch

Power supply unit PSU

CAN-bus cable with

board connector
CAN dongle connector
Figure 26 Xantus (NPS) Service Programming Box

Xantus (NPS) Service Programming Box

Ordering details
Part #

Description

150100

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

Trou blesh ooting

24

NPS Troubleshooting Manual

11

Versi on 1109

How to change a needle

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)

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

Trou blesh ooting

25