I was hoping for something like git (where I could create branches, merge, rebase, etc) but so far Iâve only be able to use it for maintaining a linear main branch for methods.
2022-11-09 17:29:39> HSLLabwrAccess : _Method::HSLLabwrAccess::SortSequenceByProbeHeadWithPresort - start; i_intProbeHeadConfiguration = 1
2022-11-09 17:29:39> SYSTEM : Execute method - error; An error occurred while running Vector. The error description is: C:\Program Files (x86)\HAMILTON\Library\HSLLabwrAccess\HSLLabwrAccess.hsl(1042) : Invalid class string (0x23 - 0x2 - 0x39) ,
2022-11-09 17:29:39> HSLLabwrAccess : _Method::HSLLabwrAccess::SortSequenceByProbeHeadWithPresort - complete with error; Error while creating the COM object Hamilton.ASW.SequenceSorting. Is this component installed and registered?
Seems like I need to run an additional install but Iâve already run ASW standard. Is there a separate installer for HSLLabwrAccess?
For the Vantage platform, can you use the span-8 channels with tips on the 96-core head? I vaguely remember this couldnât be done on the STAR platform. Always curious as to why Venus wouldnât let you perform this operation.
@chips-a-hoai - So I can confirm that on VANTAGE I have used MPH commands (tip pickup, aspirate, dispense, tip eject) while the channels had the QCG loaded without issue, though this was on older MPH and 1mL channel firmware.
That is not to say that all combinations of tip/CO-RE accessories and their associated commands would necessarily be allowed while tips are loaded on the MPH, or vice versa. The various scenarios would need to be tested. At the moment, I cannot remember the specific scenarios I have attempted in the past - same with STAR - so I would need to test to confirm.
I doubt VENUS software cares one way or the other, it is likely low level rules programmed into the firmware various modules, which in turn would trigger an error reported by VENUS.
Is there a particular scenario you are after? I will have access to equipment next week and can run a few quick tests, as now my curiosity is piqued.
yup, I am trying to basically use the span-8 to aspirate/dispense while i have tips loaded on the 96 core head.
It helps when you are trying to do multi-task, as I do not want to unload dirty tips on the 96 core head.
I am just having my fingers crossed that itâs no longer a limitation on the Vantage platform. But I never understood why Venus wouldnât let you perform that command since the core-96 and span-8 never cross paths (a crash isnât possible).
@chips-a-hoai - With current VANTAGE firmware, you are good to go. I ran a variety of tests this morning testing different commands while both the MPH96 and the 1mL channels had tips or CO-RE accessories loaded and did not encounter any issues. These included:
Pipette with the 1mL channels while the MPH96 had tips loaded
Pipette with the MPH96 while the 1mL channels had tips loaded
Pipette with the MPH96 while the QCG was holding a rack
Get/place a rack while the MPH96 had tips loaded
I cannot guarantee that future VANTAGE firmware module revisions will not include checks preventing any of the above scenarios, but they are currently allowed.
@Stefan - This is likely due to the grip mode you have set. Complex grip orientation 1 will have the iSWAP grip the labware from the rear of the rack.
If your labware is landscape orientation, then you would want your grip mode set to 1 (grip labware on large side) so your grip mode (and resultant labware orientation) matches the grip orientation.
If the labware you are gripping is portrait, then youâll need to set grip mode to 0 (grip on small side).
Is there a way to modify liquid class properties programmatically? I am interested in creating a placeholder liquid class that I can write any values I want to and have this used to dynamically apply liquid handling parameters at runtime.
Yes, you should be able to use the Liquid Class library that is posted to the Libraries folder. It has commands to set parameters for the aspirate and dispense.
Working on putting together a deck loading prompt for folks and was wondering if thereâs a way to pull the file path for the preview image of the labware from a labware on the deck
