How to Automate FlexLogger Features

[fazekasc]

Hello,

I'd like to use FlexLogger to record thermocouple data with a FieldDAQ device, but I'd like to automate certain things.

I'll be running a typical test program from a TestStand sequence that will run steps to setup a temperature chamber, power on the UUT, etc.

I'd also like to have steps that can tell the FlexLogger project to begin recording automatically without someone manually having to press a button on a GUI.  I'd need automation hooks for stopping the recording, saving the log file, re-naming that log file, etc.

I've read through some of the plugin content and flag content, but it's not clear if I can start, stop and save a FlexLogger recording session automatically.

I use TestStand, but would be ok writing some LabVIEW VI's to automate this, then call those VI's from TestStand. 

[CyGa]

Hi Fazekasc,

To start/stop a FlexLogger recording from TestStand, we can develop a plugin to do so. Let me know if you are interested (send me a PM), but it is definitely feasible.

To change the recorded filename I don't know how to do it. But this could be done from TestStand, once the file is ready on disk after the acquisition is stopped.

[fazekasc]

Thanks for the quick response.

I don't mind developing the plugin, just wanted to know if it was feasible with existing NI software.

[Jarrod_S.]

This won't solve all the items you listed, but you can start and stop a test from another application by reading and writing to specially-named Skyline/SystemLink tags. See this LabVIEW example: <Program Files>\National Instruments\FlexLogger 2020 R1\Examples\SystemLink Integration\Start and Stop Test Example.vi.

Also, I believe TestStand has the ability to read and write SystemLink tag values, so you should be able to incorporate this directly into your test sequence.

Also, you can publish output values configured by FlexLogger (such as Analog Outputs or CAN output signals) as SystemLink Tags, which will allow you to control other parts of your test system, although you should not expect to be able to do fast or deterministic control via tags.

All that said, more comprehensive application automation is a notable area for future investment for FlexLogger.

[fazekasc]

Understood,

I'd also need to be able to open and close the FlexLogger software because we want to avoid having any manual steps to open something like FlexLogger manually, for the plugins or SystemLink Tags to work.

I suppose a simple batch file could open the software, or a command line TestStand step, but in our experience that's not as robust as needed for long term use without the occasional issue.

[Tommy_G]

Hi fazekasc,

As Jarrod mentioned above there are a few ways today to automate FlexLogger from an external application using SystemLink Tags, but it seems like there is more functionality that you would like to see added to make it work in your current workflow such as opening and closing FlexLogger. I would love to talk with you more about your application and desired automation functionality. Please feel free to reach me at Tommy.glicker@ni.com and we can set up some time to chat.

Thanks,

Tommy