crossrulz

I just set the display for my controls to something like "%#pHz". The %p sets the display mode to SI Notation, which uses the prefix.

So what I am gathering here is that the Assert Floating-Point Numeric Type.vim does not work with units. Otherwise, it does look like the timestamp case for the Scaler To String.vim is the first one that would work with a numeric, even with units (just feeds into a Format Into String). I'm so glad I gave up on using units ~13 years ago... EDIT: Daren posted right when I was about to hit "Submit".

Crosspost on the dark side: https://forums.ni.com/t5/LabVIEW/How-to-solve-this-kindly-help/m-p/4004765#M1144354

I often just use "x". Curious where that puts me...

When not doing TestStand, I tend to use something similar to a Queued Message Handler. Possible commands to a module/actor are the public interfaces in a library while the queue/event/etc are stored in a private Action Engine.

So you just want the missing elements?

You get that with any error. What I found is I had to make sure the installer was "Run As Administrator".

That's too complicated. Just wire the 3 to the Length and leave the Index unwired. Delete From Array will default to deleting from the end.

You are mixing definitions of "Hex String". It appears you need a raw/binary/flat data string. So replace the Number To Hexidecimal String with a Flatten Into String. The Number To Hex String converts into an ASCII text, which you do not want. Further, since you only want 4 hex character (ie 2 bytes), you need to add a U16 conversion bullet after the multiplication.

There also appears to be A LOT of interaction between things. If I disable the Value Property Node, the User Event gets into the same realm as the Notifier and Queue. Removing the channels makes it even more the similar. Maybe the Queue Status in every single VI is doing something?

You will likely need a write (to request the data) and a read (to get the data) for each slave.

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.