-
Posts
541 -
Joined
-
Last visited
-
Days Won
23
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by crossrulz
-
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
-
Poll on Architecture and Frameworks
crossrulz replied to drjdpowell's topic in Application Design & Architecture
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. -
-
You get that with any error. What I found is I had to make sure the installer was "Run As Administrator".
-
deleting a portion of a string not an array
crossrulz replied to rscott9399's topic in LabVIEW General
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.
-
You will likely need a write (to request the data) and a read (to get the data) for each slave.
-
Style Tips for Spaghetti Block Diagram
crossrulz replied to TUzzell's topic in Application Design & Architecture
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. -
LabVIEW NXG - when will we start using it
crossrulz replied to 0_o's topic in Development Environment (IDE)
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. -
LabVIEW NXG - when will we start using it
crossrulz replied to 0_o's topic in Development Environment (IDE)
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
-
converting the timer indicator in hours minutes and seconds
crossrulz replied to qwerty3321's topic in LabVIEW General
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.
-
DVR Read and Write Malleable VIs - Simplify Your Block Diagram
crossrulz replied to the_mitten's topic in Code In-Development
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. -
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.