Why does EZChrom miss the start of run signal?

There could be a number of reasons why this could happen.  Below is a list of the most common reasons.

1. Hard wiring problem
Check trigger line in the "terminal panel" (inside the black box that lies between the Biochrom 20 and PC).  Check that the Yellow lead is attached properly to the IN1+ (It could be IN2+, IN3+ or IN4+) connector.
2. Problem with trigger signal on actual EZChrom board.
In some instances it has been found that the trigger line fails to see the Biochrom 20 start of run signal.  It is possible to move the trigger line in the "terminal panel" (inside the black box that lies between the Biochrom 20 and PC) to another trigger line.  Identify the yellow lead and which connector it is attached to normally IN1+ (It could be IN2+, IN3+ or IN4+) connector.  Move it to one of the other connectors e.g. IN2+ and then go into EZChrom and choose configuration, the instrument and set Trigger Signal Line #: (Input) to 2 (if using IN2+).  Now test the system with the new trigger line.
3. New faster PC's.
This is an intermittent problem which can occur with the newer, faster computers - 100 MHz Pentiums and faster - when using EZChrom version 6.6 or 6.7. The problem stems from the processor speed versus the bus speed.

To prevent this from happening, a statement can be added to the EZCHROM.INI to slow down the bus speed.  Exit EZChrom if it is running and then open the file EZCHROM.INI (found in the EZChrom directory) in any text editor (Notepad, Wordpad, etc.).  In the first section - [EZChrom] add the statement SS420DELAY as below:

[EZChrom]
.
.
.
DEMO=0
RF=1
Integration=SSI
MULTIPORT=0
SS420DELAY=5000

Save the INI file and restart EZChrom.

This additional statement will not work with any EZChrom versions before 6.6.  So check what EZChrom version you are running first.

 

If this does not answer your question or solve your problem, then please contact us at support@biochrom.co.uk detailing your question or the problem you are experiencing.  Please list if relevant the instrument, software and version numbers you are running, and enclose any relevant data files, etc.