To mix using a Smart Command in FluentControl, create a custom liquid class that includes a mix as part of the dispense by editing the Dispense Microscript for a liquid class. Tecan Expertline can help if needed.
I missed that this was already mentioned above:
What version release was this originally included in? Honestly it’s a great feature that didn’t make the jump from EVOware–>FluentControl and I miss it. It takes away a lot of the dynamic mixing potential that is harder to reproduce inside of microscript. Don’t get me wrong, I love my microscript-heavy LC’s, but it’s not beginner friendly at all and takes a lot of troubleshooting.
I had a “source” that told me that this feature was making a comeback but I haven’t found it as of FCv3.3. A lot of my old Tecan friends have since moved on and I’m learning less and less about new features outside of this forum!
Believe it or not, it’s in the current Dilution smart command. With that said, they’re going to deprecate this command (per the manual) so they recommend not using it but they’ve been saying that for a few versions of FC and it’s still there so…
And yeah I believe (and rightfully so) that there will be a greater emphasis on smart commands. In my meetings with some of their leadership members, I’ve emphasized that this is a missing piece for more plug & play LH automation adoption. It gets old to re-do asp/disp commands over and over, and I’ve found that even basic eng principles fly over the head of a lot of scientists.
Not to my knowledge but you can comment them to the AuditTrail to reveal them. You can also check them through the API (both versions of it.)
I don’t really use the Variable Viewer because it has been easier for me to send any parameter to the AuditTrail than it is to run over to the Fluent and navigate a buggy FC interface. What’s your use Variable Viewer case?
I use the Variable View for troubleshooting when a run aborts. My team also writes values for some variables to custom logfiles that we generate using the Export Variable command. Creating these logfiles requires a fair amount of work, and their creation also needs to be debugged…
I should mention that Variable View is of limited use when a run aborts, because while the abort window is present, FluentControl will not allow the user to click anywhere other than on the abort window. And after clicking abort, some user defined variables disappear from the Variable View, which is a maddening bug, in my opinion.
I prefer to disable all comments in scripts so that they do not appear in Tecan Connect and on MissionControl.Tecan.com, where comments take up valuable slots in the ephemeral rolling logs. Those logs can be great when providing user support remotely, but if they fill with comments, then the error and warning messages are lost and can only be found by remoting into the controller computer and opening the LogViewer, which is not practical using a smartphone.
How do you “comment to the AuditTrail”? The scripts that I inherited don’t appear to write anything useful there — just hundreds and hundreds of copies of the same input file with a different timestamp for each.
I was thinking that a lot of functionality could be added by just having a set of macros kept in something like a simple AHK gui. Track variables, preconfigured steps, even a simple version history likely could be handled by this. Might be a little easier than large blocks of code - but depends on what familiarity you have with it.