Hi,
I want to edit the Daily Maintenance HSL protocol so that we do not have to click through the prompts and just allow them to timeout after a few seconds. Is there anything I should be worried about or consider regarding editing this protocol?
Thanks!
@partyparrot I remember asking the Hamilton programmer to do this for us, and was sternly informed this was a bad idea, we shouldn’t do it … Since I have to change gloves everytime I use computer mouse/keyboard, I really wish it was a walk away method. Currently, we have to stand there throughout this step in order to click through prompts, even though we give the same response every time. If you do change it, and it works ok, i’d love to know!
We’ve got 9 Hamiltons and spend a bit of time walking back and forth between them all to hit enter. This is a great idea!
@cdm @colin.cox I’ve edited it via the HSL editor and it works!
The only thing is that it is suggested to power cycle after running daily maintenance, so that part is still manual. @NickHealy_Hamilton Is this step actually needed? Is there a way to programmatically restart the instrument?
Power cycling after running maintenance is only required for VANTAGE platforms being run by VoV (any version prior to VENUS 6). This is not required for STAR.
Thanks.
-Nick
If you’re able… Sharing is caring
This is a smart idea, and you have to change the timeout setting for MessageBox from infinite to timeout seconds in maintenance hsl.
MessageBox(StringTable::Load(IDS::dlgCannotRunWithSimulator),
StringTable::Load(IDS::dlgWarningTitle), hslOKOnly | hslExclamation, hslInfinite);
but maintenance hsl file is readonly, that you can modify it with hsl editor. The possible way is saving that file to another name, deleting that file with stp file, and then saving it back.
or just go to file properties and untick read only…
The readonly of hsl file was set in .stp file, so you can not change it with file properties.
I did exactly this!
Hey Nick,
Is there a way to programmatically power cycle the instrument?
Have light automation in the home, some via smart plugs, and wondering if something like that could be utilized to remotely/programmatically turn on/off the instrument?
Thanks!
There is no way to do this through VENUS. Unfortunately, there is no guidance I can provide for alternative options.
If powercycling after running daily maintenance is an issue, I would consider upgrading software to VENUS 6.2. This comes with an updated VANTAGE daily maintenance routine which does not require powercycling after running, and also includes an additional channel alignment check, in addition to the existing pressure leak and cLLD checks.
Thanks.
-Nick
Long ago I added the email library to email you on failures of daily maintenance
Is it possible to generate the Report.xls file in a directory other than LogFiles? We manage 15+ systems, and for audit compliance we’d like to save all maintenance files in a single cloud drive location.
Unfortunately I cannot provide guidance on making modifications to the daily maintenance HSL code for customizations. The method and libraries install as Hamilton read only in order to prevent inconsistencies between maintenance runs on various instruments and sites, as any outcome that results in an error free run is often used to trigger an on-site service visit from a FSE.
That said, there is no reason you couldn’t generate an internal script/application outside of VENUS to scrape the LogFiles folder of each installation to identify any .xls files whose name indicate that the file is a maintenance results file, and subsequently copy it to your networked cloud drive destination.
If you are running VENUS 6 or more recent, another option would be to use the automatic log cleanup feature supported by the UI to move all contents of the log files into your networked drive location:
This provides the additional advantage of consistently ensuring the default LogFiles folder for the VENUS installation is of a reasonable size. Given that this folder is actively used by software during runs, extremely large LogFile folder sizes will slow down run time performace.
Thanks.
-Nick
