crossrulz

My understanding is that NXG is a full platform effort, not just LabVIEW. The LabVIEW part was scrapped, not everything else. I suspect the devs for LabVIEW NXG have already been moved on to work on Instrument Studio, TestStand (2020 has the NXG look), VeriStand, Flex Logger, etc.

Now imagine a "Senior Engineer" being brought in on a project and being told to redo everything because you used an Event Structure. No, I am not exaggerating. He had issues with the Event Structure in LabVIEW 6 and swore them off forever. Good thing I didn't listen to him, managed to get him to leave me alone, and the project was successful. My point here is that titles should be taken with a grain of salt.

Coming from my personal experience, I still lean towards no. I had a discussion with Nancy Hanson about this and we came the the conclusion that the CLA was not a destination, but the opening of doors to learn (yes, this was alluding to the CLA Summits). Personally, I had 0 experience using OOP when I got my CLA. But after my second CLA Summit, I found an application that deserved a very basic OOP architecture. The CLA Summit opened that door for me. Now I would say ~50% of what I do is OOP. There is still A LOT you can do effectively without OOP. And keep in mind that part of a CLA is to make architectures that your less experienced developers can use and understand. If they can't use OOP, then your OOP architectures will not be effective. So should it be REQUIRED? No. Highly recommended? Absolutely.

Sounds like you should be handling your serial communications with a Queued Message Handler. Use queues to send message to other loops (the QMH) telling it to send, query, or just read the port. Your message could include a queue reference for returning the data. I covered this at my VI Week presentation: Proper way to communicate over serial

Not quite what you are asking for, but...LabVIEW FPGA IP Export Utility

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.

You can use the Flush Event Queue function to clear out old events.

Sorry, but you can't state you have the "best" training when you don't even know how to spell LabVIEW.

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 termination character.

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.

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.

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.

Bryan's suggestion is by far the simplest method. The other route would be to have the two applications communicate over TCP/IP.

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.

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.

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.

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).

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 was still only in CABs). I don't think LabVIEW 20xx is attached in the same way. So I think there is an argument that LabVIEW 20xx could be spun off into an open-source project. But NXG is too ingrained into the MCP to be broken off without taking everything else with it.

I'm seeing a lot of activity on the LabVIEW Wiki Youtube channel. So it does look like things are progressing!

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.

It really depends on your point of view. I deal with a lot of people who see the hardware integration as the strongest thing about LabVIEW. But then I run into a bunch of people who just expect LabVIEW to do everything for you, which is just completely unreasonable. Perhaps that is where FlexLogger, DAQExpress, and the like come into play.

Mind elaborating on this?

And on a mobile, that splash screen takes up more than my screen, making it so I can't even close the dialog.

But isn't every logo?

NI Week keynote. Pure marketing BS. Exactly what I expected from it.