Jump to content

hooovahh

Moderators
  • Content Count

    3,061
  • Joined

  • Last visited

  • Days Won

    218

hooovahh last won the day on February 23

hooovahh had the most liked content!

Community Reputation

768

9 Followers

About hooovahh

  • Rank
    Im no supervising technician Im a technical supervisor

Profile Information

  • Gender
    Male
  • Location
    Detroit MI

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    2004

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I think combining that what PiDi gave, with a single column listbox, and an event structure that gets triggered on the Double Click, event would get you most of the way there. You can also try to capture a <CTRL> + G on the OS to go to the next. I think the Initialize Keyboard an Acquire input would work.
  2. Okay this is possible, but it may need extra work when making the file. TDMS data in channels by themselves are just 1D data. They have no way of knowing how much time is between each sample, or the start time. But you can write to the properties of a TDMS channel, and put in extra information like the start time, and time between samples. This works great for things like the Waveform data type, and when you write this data type to a channel, these properties are already written. So you can read the start time property, the dT (time between samples), and the number of samples in a channel
  3. I like TestStand but it is the one size fits all type of software. NI can't know what you'll prioritize in features in a sequencer and so it either has too few features and only can satisfy the simplest of projects, or it has everything thrown at it, in which case there are parts almost no one will use, and it might have a steep learning curve. That's why one of the justifications I agree with when it comes to a home grown sequencer, is that you know the types of features you need, and the types you don't. Now obviously requirements change, and you need to change with them, but high lev
  4. Good discussions are timeless. There's lots of great content on LAVA that goes dormant, but its still there. I would almost put XControls in the best features, and worst features list personally. I still stand by my debugging comment from almost 11 years ago.
  5. A seemly highly specialized piece of equipment can usually justify the price. But not meeting your needs and costing that much seems crazy. It gets me wondering if there are products NI offers that over the life of the product never sell a single unit. Years ago I was in a hands on session with some PXI card NI was selling that allowed for taking many temperature readings, by using fiber optics. Something like the fiber optic had microscopic cuts in it that allowed for taking many channels of temperature reading, like on the order of 100s. I looked up the card and I can't remember th
  6. Not that I know of. I'm not sure if this is an option for you or not, but you could completely shutdown the LinuxRT device, then have power removed, then reapply power. I believe the bios of these controllers allow for wake on power being provided, and your app can be ran on startup. So maybe have some kind of external device work like a watch dog. While your program is running keep hitting the watchdog, then when your program shuts down the timer starts counting down, removes power, waits a second, then applies power again. Just a thought and probably not a great solution, and someone wi
  7. I have seen bad DBCs in the past. But in those cases I would just load it up in XNet Database Editor, re-export it, and then it was fine. I haven't seen it not load in XNet before.
  8. Oh man and I was just touting NI support as being one of the few "fine" parts of NI.com. Never mind. I'm really confused and I think the report a bug feature is worst than you made it sound. So I got there and it says "In which product did you encounter the bug". It asks for a Serial Number. I enter "LabVIEW" or "LabVIEW 2020" and it didn't work. So I tried entering the serial number of my hardware or model number and that didn't work. I think I'm supposed to put in the serial number of my LabVIEW license, but I'm on a disconnected license from a VLM so I have no serial. Am I not a
  9. Very neat thanks for the background on a toolkit I didn't know existed. I'm sure NI was in a "damned if you do/damned if you don't" situation, but this can be seen as another example of NI's first party solution, stifling 3rd party toolkits. Also I generally don't mind bundling in stand alone binaries in cases like this if it means an easier experience for users, similar to bundling in the SQLite DLL in the build.
  10. You have to create a free NI account, and login with that. Once logged in and connected to the internet it should activate. If you have any problems with activation you can try contacting NI, or post on their forums.
  11. The LabVIEW Wiki has lots of content. I usually recommend new developers checkout the Getting Started or the Online Training sections.
  12. The problem is sometimes the compiler gets a bit too aggressive and does something that it thinks won't functionally change the code, but does. Like what if the compiler mistakenly thinks the close reference function can't be called? Well it will think that node can safely be removed and nothing will change. But if the close was actually being called in the IDE, and now it isn't in the RTE that could be a problem. The Always Copy function has been known as a band-aid because it forces the compiler in some cases to leave things alone instead of trying to optimize code. This would then
  13. I'm also a fan of SVN. For multideveloper work we use VisualSVN Server. The free version does a great job, but the paid version has domain integration among other enterprise features. I'm not sure what can be used to make a local repo. Jim had an old blog post years ago that I can't seem to find. The client side I just use the explorer integration that comes with Tortoise SVN. There are LabVIEW toolkits that add quick drop, or tools menu, and project integration, but none of them worked with our work flow enough. Here is the first package I found made by JKI that does some of this.
  14. Adding to crossrulz suggestion. If you do want simple I2C or SPI, using an Arduino is a great solution in LabVIEW. NI has their LINX toolkit, which downloads a known set of firmware to the Arduino, and then in LabVIEW you have the LINX palette which basically tells the microcontroller to execute some set of steps. These commands are just serial commands, and when plugged into USB should appear as a normal VISA device in LabVIEW. I don't have a pharlap system to test with but with other remote devices I've used they just get enumerated when they are plugged in. I personally have not us
×
×
  • Create New...

Important Information

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