Hey all! My lab wants a CSV file to be output from each method that has the firmware versions of the instrument, along with other information. I recognize that the firmware versions are output in the Trace file, but I want to see if there is a way to get the firmware versions in-method and then automatically log them to a CSV. Does anyone have any suggestions?
1 Like
Hi @spazianim,
I wrote a code snippet below that is a fairly simple way of extracting the firmware versions directly from the Trace file:
Outlined:
-
Use the default library HSLUtilLibâs âGetUniqueRunIdâ function to get the Run GUID which is generated as part of the Trace file name. Concatenate this with the LogFiles directory, method name, and suffix/extension to generate the current runâs Trace File Path.
-
Use a File: Open command to open the Trace file as an âASCII Fileâ, loop over said file and check if the given line contains the substring âFirmware versionâ. If so, add to an array.
The method and trace will pick up from this point and continue normally.
Thank you,
Dan
1 Like
Hi @spazianim
If you like to use firmware commands, I can hook you up with a few commands
Basically you can use one command to retrieve the modules (C0, r0, i0, p1, p2 etc) and then query each module with command RF to retrieve this value.
I use it for the same purpose. Full tracing into a csv file. Happy to share with you.
1 Like
Hey Pascal! That sounds great! Could you please send it my way? If you have any additional firmware command documentation, Iâd love that too!
Excellent! I have created a package for you.
Iâll just tag @EricSindelar_Hamilton here if he has some space to share this with because itâs quite a handy thing.
3 Likes
Thank you so much! I really appreciate you creating a package for me. Please let me know if you need my email address or anything to send it my way.
Hi @spazianim
Created the package for you (and others). Uploaded it to the drive that I got from Eric, should be in the repo soon.
pH
1 Like
Uploaded to the Methods folder here. It looks like the export is a hampackage which would require VENUS 6 or above to import, fyi.
1 Like
@Pascal @EricSindelar_Hamilton Thank you both so much. Unfortunately, I only have access to VENUS 4 and am unable to import this package. Is there a VENUS 4 package you could provide? If not, is there any documentation you could send my way that has the firmware commands on it or something similar?
