crossrulz

State Machines are your friends here. You can easily make a state for each of your steps. You can maintain your state list with a queue or you can have a good study of the JKI State Machine.

I did have word that NI was working on something for SSH in LabVIEW 2019. I have not seen anything mention of it in the beta forum (have not gotten it installed yet), so it probably got delayed.

Scripting is a work in progress last I heard. OO is now a feature and NI is working on Traits. I think llbs are gone. lvlib I think got transformed into something else. I do not know of any replacement currently available for the PPLs. Benefits? "Programming Optional"! For me, I will consider NXG when packages (ie PPL replacement) are more fleshed out. Otherwise, I think all of the features I would need in my current position are implemented.

I downloaded the DS disks last week and the speeds seemed good to me, considering the corporate IT mess I have to get through.

1. Help->Find Examples. Do a search for XML 2. Go look at packages in VIPM. NI has a Simple XML library that I used to figure some things out. Then JKI and MGI have their own XML packages you can have a look at.

Yes, I still heavily use ini files. Admittedly, I am starting to transition my code to use XML.

Here are your VIs saved in 2015. 2015.zip

Right-click on the timer indicator and choose Display Format. Choose the Relative Time type and then the HH:MM:SS radio button. The indicator will now show your hours, minutes, and seconds.

I still maintain that using parallel loops is greatly beneficial to you here. But if you insist on LVOOP, you should have a nice long look at the Actor Framework.

I can't say I support the use of the Write DVR Value. The point of using a DVR is to protect critical sections of code (ie avoid race conditions). If you are just randomly writing a value to a DVR without doing the Read-Modify-Write protection, you might as well use a Global Variable and get better performance.

You might want to monitor the communications with something like Wire Shark. You might find the instrument sent a command code and is waiting for you to confirm it.

As long as you don't need the command codes, just look to the TCP Client and TCP Server examples already built into LabVIEW. Telnet only gets complicated (at all) when the command codes are used.

I would stick with 32-bit. I have yet to see a reason to go 64-bit unless you are doing massive amounts of memory intensive processing (Vision immediately comes to mind).

You could probably get away with a simple Arduino or Raspberry Pi or even an office level PC.

My only TestStand roadblock so far (and has not been nearly as big of one as I expected) is the deployment license cost. Though, put that cost against a VST and it is a small drop in the bucket. (The VST is literally half of the cost of my current project's entire test rack.) As far as going away from TestStand, I have ran into a couple situations where I was told to use TestStand and I convinced the customer/management that the project really just needed a decent State Machine with a few other loops for logging and instrumentation. Sorry, no real ammo coming from me. But I am very curious about other people's reasons.