Hey all, I’m an experienced liquid handler technician and I’ve been running into more and more Fluents with issues that can’t always be solved without access to the setup software, which seems to need a certificate to use. My conversations with Tecan on the subject haven’t gotten me anywhere when asking for training. Some reps have told me it’s available but are unable to point me in the right direction. They seem more to want to charge me ridiculous amounts to just come and check my work. Does anyone have advice on how to acquire one? Or if it is allowed, to share one that they already have? I’m mainly looking to be able to change configurations since a lot of the instruments I see have been scavenged from and don’t have the components on the original configuration. Tecan helped me a couple times but has been getting slower and dodgy in their responses.
Alternatively, I don’t think it was necessary to have one for older Fluent control installs since the manuals reference you using it frequently. Does anyone have an older version (pre 2.6) and can confirm this and possibly share the install folders?
Thank you for any help and/or advice that you can provide.
I’ve done the hardware training. They give you a certificate that you can then use to access Fluent Setup. After X amount of time, you can apply to have it re-certified. I used it with Fluent Setup versions for 1.6 and 2.2 so it definitely has been true that pre-2.6 that you also needed a certificate.
I’ve personally always been reticent to share certificates but I’m sure that consultant networks have their ways. They’re your best bet or befriend an FAE.
I am an ex Tecan Apps Specialist (25 years and counting in the industry),
We offer full service/support coverage for Tecan Fluents and can help you
please email me and we can discuss (daniel.leach@optimizyourlab.com)
You can patch the certificate verification methods in Tecan.FluentSetup.Actions.dll by modifying the IL instructions so they always return true. This involves removing the original instructions, loading the constant integer 1 onto the stack with ldc.i4.1, and then ending the method with a ret instruction.
As a result, any time these methods are called within the application, they will consistently return true. The patched method body would look like this:
IL_0000: ldc.i4.1
IL_0001: ret
I don’t want to spell out every detail, but I ran into the same issue while doing some contract work. The client had paid an exorbitant amount for a device they didn’t fully own, since parts of its functionality were deliberately restricted. Which is something that annoys me to my core.