Jump to content

crossrulz

Members
  • Content Count

    451
  • Joined

  • Last visited

  • Days Won

    16

crossrulz last won the day on July 22

crossrulz had the most liked content!

Community Reputation

78

About crossrulz

  • Rank
    Extremely Active
  • Birthday 04/22/1982

Profile Information

  • Gender
    Male
  • Location
    Cincinnati, OH

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since
    2005

Recent Profile Visitors

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

  1. It'll be amazing crossing 2 time zones (Central to Western US time zones) just by going to the other side of the couch. Our sincerest hope is you learn more of our perspective as developers and take it back to R&D.
  2. You can use the Flush Event Queue function to clear out old events.
  3. Sorry, but you can't state you have the "best" training when you don't even know how to spell LabVIEW.
  4. I recommend you make a new VI to use the data block protocol. Here's the code I use for this. In short, you send your query command and read the # and the first number. This tells you how many bytes are in the "size" section. So you read that many bytes and convert that to a number. This will now tell you how many bytes are in the actual data. So read that many bytes and then 2 more to act as the termination character. Now a key here is you need to turn off the termination character so that you don't have to keep trying to read more data due to a data value just happening to match the t
  5. Just use the Array Max & Min PtByPt.vi. It does all of this for you. There is also the Data Queue PtByPt.vi that you might find useful.
  6. This change happened in 2019. My suggestion is to start getting used to using Ctrl+U to clean up the wires (make sure the wires are selected first). I am pretty sure there is a LabVIEW.ini token to turn this off, I'm just having problems finding it.
  7. Well, the developers of the two applications will have to agree to a protocol to communicating with each other. Once you have that figured out, go into the LabVIEW Example Finder and there is an example project for TCP/IP communications.
  8. Bryan's suggestion is by far the simplest method. The other route would be to have the two applications communicate over TCP/IP.
  9. CSV is a text file. So why are you stuck with Excel? It will not do what you want. What's wrong with making another viewer? Push back on this requirement to figure out what the real goal is.
  10. UltraEdit is just a text editor (a REALLY good one, in my opinion). So I have had test results being saved to a text file and had the result file open in UE. I can look all I want and then reload the file whenever I want to see the updates.
  11. Excel actually locks the file so only it can edit it. So if you close the file in LabVIEW, you will not be able to reopen it to add more data. Yes, I have personal experience with this. Since you are using a CSV, I would recommend something like UltraEdit. UE edits backup files and it will let you reload files that have changed while you have it open. I'm not sure if Notepad++ does the same.
  12. VIPM is showing 1.2.09. I thought I saw a notice on LinkedIn about Hooovahh Array VIMs being released. I don't have access to check vipm.io at the moment (blocked by work firewalls).
  13. I would say NI is becoming more and more software oriented. Just look at their latest acquisition (Optimal+). But all of the software I have seen are still geared toward hardware sales (FlexLogger to DAQ hardware, Instrument Studio to PXI instruments, InsightCM to cRIO, SystemLink to PXI test systems and cRIO, DAQExpress to DAQ, a lot of tools to the VST). And I don't see a spin off happening that would work well. All of the NI software tools are using a core stack now (reuse!). I saw evidence of this when I got a demo of VeriStand and it looked just like NXG (this was when NXG
  14. I'm seeing a lot of activity on the LabVIEW Wiki Youtube channel. So it does look like things are progressing!
  15. NI has always been quite open with me about that over my entire 15 years of using LabVIEW: LabVIEW was developed to drive hardware sales.
×
×
  • Create New...

Important Information

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