Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Bryan last won the day on January 24

Bryan had the most liked content!

Community Reputation


About Bryan

  • Rank
    Very Active

Profile Information

  • Gender

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since

Recent Profile Visitors

1,479 profile views
  1. Okay... I'll bite just because I'm curious. While I was reading your post on how you fixed it, I was thinking of all of the times that I've reviewed code and shook my head when I see that type of programming.
  2. How specifically are you trying to create the folder? I'm using LabVIEW 2016 on Windows 7 and just tried creating a folder named "Blah 1.1" on my desktop. I did it using the "Create Folder" node located in the "File I/O" >> "Adv File Funcs" palette and it worked for me. If you're using Windows 10 and LV 2017, I'm not sure if one of those could be the culprit.
  3. With good reason! We "y's" are pretty sketchy.
  4. I think he'll be cool with it.
  5. I tried to log into the Wiki using my LAVA username/password and it wouldn't let me. So then, I tried to reset my password by specifying my username and email address. It said that there was no email address recorded for my username. Next, I tried creating an account with my username, and of course it won't let me since "Bryan" already exists. So, I gave up and went with "SouthPaw". But, I would still like to access the Wiki under my LAVA username. Would it be possible for a Wiki admin to make that happen? If it's too much of a pain, I can just stick with "SouthPaw".
  6. Loving this central location of organized and searchable LabVIEW knowledge! (Just like LAVA.😁) I've made a couple of small contributions to this so far. Mostly clicking on "Random Article" and reviewing it for typos and broken links. I set somewhat of a personal goal of trying to do this at least once per workday. Every little bit helps, right? Granted, they're not contributions on a grand scale yet, (i.e I'm not creating articles, etc.) but maybe I'll get there. This is my first time contributing to a Wiki of any kind, so I'm a n00b at it.
  7. Judging by the poll results thus far, it looks like there is a LOT of interest in having a LAVA code repository for those that are not using VIPM Pro. That's to be expected though. If a public repository were to be set up somewhere, I'm assuming that JKI would have the option of adding it to the list of canned repositories for the Pro and Free versions if they so choose.
  8. From my experiences, TS seemed to be overkill for a lot of applications with which I have been involved, like trying to swat a fly with a Buick. Add to that the additional cost of deployment/debug licenses for multiple test stations, the bill goes up quickly. Learning curve also comes into play as TS has seemed to become its own programming language and is not as easy to learn as LabVIEW for those without the budget or time to take the training classes. With a "roll your own", after the initial time investment of creating a test sequencer in LabVIEW, you can deploy to as many stations as you want without the cost of additional deployment licenses by just building EXEs. Where I'm currently working, TestStand is just starting to gain a foothold, but ease of deployment and cost of deployment licensing has been a source of contention. Now, my opinions are based solely on my experience with using TS on and off for several years without formal TS training. Ironically, a couple of my coworkers and myself are going to be taking a TestStand classes within the coming weeks, and I'm interested in whether my personal opinion (and those of my coworkers) will change. At my previous employer, we still had a system running the precursor to TS: Test Executive. We had kept updating it until we ran into an incompatible version of LabVIEW, then just "froze it in time". Nobody there was very familiar with TestStand and how much it would take to do a migration as the station tested a large variety of boards. Because there was only one operating station, the risk of downtime for migration was considered too great, so it was never done. Test Executive seemed so much simpler and a better match for the needs at the time. A second station was created to do the same as the one running Test Executive. Test Executive wasn't compatible with the newer version of Windows, and they still didn't want to go the TS route, so we ended up going with a LabVIEW-based test sequencer from CalBay (now Averna) called "iVVivi". I became very well versed in iVVivi and it was definitely simpler than TS. It also had an integrated LabVIEW OOP-based HAL, which was very attractive. However, in some respects it was TOO simple and required some creative LabVIEW routines to mimic some functionality available with Test Executive. I don't believe iVVivi is even supported anymore, so they may eventually be forced to go the route of TS. Or, beg NI for the password to access/update the protected VIs to recompile in later LV versions.
  9. Here's another quick and dirty example just using local variables and two separate while loops. I don't like using sequences and local vars in practice myself, but this is just a way to show you a simple way to control parallel loops. It's quirky, but I hope it gives you an idea. There are much better ways to implement parallel loop control and communication, but I just wanted to provide a quick example for you. The "Stop" button is set up to use latch functionality, which isn't compatible with having it used as a local var, so I had to create a separate indicator for "Stop All" to "hold" the value to be used by the second loop. Please don't use this as the best example as it doesn't really show good LabVIEW programming practice, but will at least show you what's needed for parallel loops. Again, I hope I've helped you out! Untitled 2.vi
  10. You're probably going to have to implement a producer/consumer design pattern if you want truly parallel processes. There are many examples of them in the LabVIEW examples. I wasn't sure whether going into producer/consumers was going to be overkill for what you wanted, but you may want to look into going that route based on your description. For simplicity's sake (and my lack of time), and to illustrate what I was talking about in my first paragraph using a timeout case, I've attached a VI (in LabVIEW 2016) that uses the timeout case. The default timeout is -1, which means that the event will wait forever or until an event occurs. In my attached, it waits for 100ms. You can have the timeout be as long or short as you want as long as it's greater than -1. To keep the value in your shift register, you'll have to wire your shift register value straight through your timeout case. If you don't, it will be overwritten by a default value (normally "0"). This method is a quick and dirty way of allowing the event structure to complete alongside your case structure and not be dependent on it while being in the same loop and not have the while loop hanging. I hope this helps! Untitled 1.vi
  11. A while loop will not iterate until all nodes within have completed execution. First thing: do you have a "Timeout" event case defined? If not, your loop is going to "hang" and only loop when your "Numeric" value changes. The wire you have currently running to the "timeout" terminal of your event structure is not going to do anything as this defines the amount of time that the event structure "waits' for an event before proceeding via the "Timeout" event case. You'll need to wire a separate constant for your iteration delay (i.e. Timeout value), say: 1000ms. If you wanted these two cases to be independent, you'd have to set up a second while loop and pass data between them. I don't know what the end product is for what you're working on, so just for simplicity's sake, I'd say to set up your timeout event case. Note: when this is running and your timeout case is set up, there will be up to a 1000ms (1s) delay from the time you press "Stop" until the VI stops execution. This is unless you have a "Value Change" event set up for your "Stop" button.
  12. I agree with you, but I still have to run it by them before plugging in anything not provided by the company. You know how large companies can be. Knee-jerk reactions become long term policy and then convincing them otherwise is like talking to a tree unless you have serious pull within the organization, (which I do not). I've sent a request asking if there is an accepted process or if I can get a waiver. If there's no way, then I have to wait for our company-wide VLA to come up to speed... which could be a while. Currently, they are only providing up to LabVIEW 2015 through our engineering software "store". As I said in another post, we're normally two to three versions behind (which is why I let my CLD expire). The only way I'm able to get anything newer has been via the DVDs/CDs and my "pseudo" administrative rights on my computer. I would definitely be able to contribute as well!
  13. I just received the "disks" for our SSP today with LabVIEW 2017 and NXT. I was eager to install and play with it. But, instead of disks, I received a 32GB USB stick. While It's a neat concept by NI, it's a BIG no-no at my company to use USB media sticks that are not explicitly provided by my company for information security reasons. (Anyone remember Stuxnet?) I'm friends with someone in information security, and I can ask if there are acceptable processes/procedures to use the disk, but I'm pretty sure I already know the answer. These are the times when working for the type of company I do is a pain.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.