I’m trying to do a simple aspirate and dispense on a Hamilton Vantage. I’ve heard Venus on Vantage is the easiest way to do this, so that’s what I am using, but if people have been able to do this using Instinct / something else, I’d be happy to use that instead.
My current Venus method is just a super simple single variable assignment, so no actual hardware operations. It runs fine in simulation. Unfortunately, when trying to run this on the robot I get an error saying Firmware check failed at modul C0-RE 96 Head, version on instrument S.1.00.06.01 2022-10-06 (XRP H0) (0x29 - 0x1 - 0x9).
What can I do to resolve / work around this error?
When VENUS Run Control is launched for a live (non simulated) run, there is a ‘run analysis’ phase executed prior to any method execution, in which Run Control connects to the VANTAGE and quickly runs a series of configuration checks. One of the checks is to scan which firmware rev is downloaded on each component.
You are running a recent version of MPH 96 version, which may not have existed upon release of the version of VoV you are running. I can help you out via DM.
There isn’t a cut and dry solution I can easily post to cover all scenarios.
This issue typically occurs in the following scenarios:
A firmware upgrade is run without updating the accompanying version of VENUS/VoV for that firmware version, or without updating the firmware compatibility list (typically performed by Hamilton service at the time of firmware upgrade).
VENUS/VoV reinstall occurs on a system that has had a firmware upgrade (updated firmware compatibility list is reset to default).
Software downgrade occurs without firmware downgrade.
Do any of these situations apply? I would need to see traces of the failed run analysis to provide further consult, but generally this type of issue is best handled via your local Hamilton service support group.
If you need any assistance getting pointed in the right direction, let me know!
Hi @NickHealy_Hamilton thank you! We acquired these instruments used so it is hard to say which of these is the root cause. The trace file does not really say much more than that. We have a second star in which we are getting the following error on a simple initialize step : The instrument configuration descrived in the instrument configuration file does not match the configuration reported by the instrument. (Wrong setting oof instrument eject position; expected 0, received 13400.). Do you have any ideas about this one?
@rickwierenga awesome, that worked. Finally got the instrument to initialize, unfortunately I’m getting another error towards the end of the initialize step. H0:Main, Cannot reach the defined position. Check if the position reachable for each channel. On transport check if the labware is gfripped in the right direction or plate is fgripped with correct channels.]
We are running into a similar issue. We had to switch the computer that our Hamilton was running on, and re-install VENUS software. This was after upgrading to CORE II which I believe included a firmware update. Simulation works, but we get the following error when not in simulation:
Microlab® STAR : Main - error; An error occurred while running Vector. The error description is: Firmware check failed at modul Main module, version on instrument 7.6S 25 2021_11_05 (GRU C0) (0x29 - 0x1 - 0x9)
Do you have access to the original PC, and does it still have its VENUS/VoV install intact? If not, was a backup of the Hamilton folder made?
If the answer to either question is yes, the easiest way to restore run control compatibility with your instrument would be to restore the VStar.cfg file from backup.
Locate from the original installation:
Hamilton\Config\VStar.cfg
and overwrite the existing file in your newer install.
If a backup isn’t accessible then it will need to be manually restored, which requires alternative recourse.
Hi U,
I got the same error with “Firmware check failed at Modul Main” when switch tha PC with Venus 3 version to PC with Venus 4 version. I needed to copy some folder from old PC to run a method i simulation mode. It did not work in Run Control I got the same error. Do you have any suggestion what to do?