Page 1 of 1
Getting EZChrom Elite to respond
Posted: Thu Dec 29, 2016 12:08 am
by Andy Alpert
We have a legacy machine running EZChrom Elite ver. 3.1.7. Somebody must have inadvertantly changed a setting. Now, any attempt to start a run results in an error message saying "division by zero". We cannot start or end a run and can't load a new method. Help!
Re: Getting EZChrom Elite to respond
Posted: Fri Dec 30, 2016 5:47 pm
by M F Wahab
We have a legacy machine running EZChrom Elite ver. 3.1.7. Somebody must have inadvertantly changed a setting. Now, any attempt to start a run results in an error message saying "division by zero". We cannot start or end a run and can't load a new method. Help!
Hello Dr. Alpert, It seems like a fatal error as per the following link, indicating a board error.
http://www.ecs.umass.edu/eve/facilities ... ssages.pdf.
Please see page 4 of this link. "Divide by zero". Not sure if Agilent still supports EZChrom.
Regards,
Farooq
Re: Getting EZChrom Elite to respond
Posted: Fri Dec 30, 2016 5:54 pm
by Andy Alpert
Hi, Farooq!
Thanks for this information, which is helpful. While Agilent no longer supports EZChrom, an Agilent tech did call us in response to an e-mailed "SOS". He's talking us through a clean reinstallation of the program, which he said might or might not solve the problem. He also didn't seem to think that this error message necessarily implied a fatal motherboard problem.
Re: Getting EZChrom Elite to respond
Posted: Tue Jan 03, 2017 7:49 pm
by Mike H.
Open all fields in the sequence table and see if there are any 0s in any multiplier or divisor in there. Also sometime when copy and pasting you can get non-numeric data in these fields that will screw it up.
Re: Getting EZChrom Elite to respond
Posted: Thu Jan 05, 2017 9:40 pm
by Andy Alpert
Here's how the problem was resolved. It turned out that the program had stopped recognizing the license key in the dongle (a USB thumbdrive). Even though Agilent no longer supports EZChrom, some technical people there wrote us a software patch that provided a software-based license key (in place of the hardware-based key). We then deleted the program from the root directory and performed a clean reinstallation. Now we're reinstalling the drivers for each component of our system, but EZChrom itself is working fine. All hail Agilent!
Thanks to Mike H. and Farooq for your suggestions.