crossrulz

1 hour ago, Antoine Chalons said:

I think when NIWeek was moved to may instead of august they said the release cycle might change, I think AQ posted something about that on LAVA, can't find it though.

The release cycle was changed so that the main release remained with NI Week.  So there was no LabVIEW 2016 SP1 since NI Week was moved from August to May in 2017.  AQ has told me that NI has a "quarterly" release cycle, so who knows when LabVIEW 2021 would be released (April?  July? October?  Never?)

16 minutes ago, mabe said:

Maybe it's just me, but I find it very difficult to work with the new color scheme of NI TestStand. My eyes are burning after few minutes... Am I the only one?

No, you are not the only one.  Unfortunately, this is the color scheme all NI products are going with.  Have you seen the LabVIEW 2020 SP1 Getting Started Window?

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.

8 hours ago, LogMAN said:

For the second part "and in worse case puts the entire project at risk by making random decisions" imagine somebody without any prior knowledge about OOP being brought into a project that is heavily based on OOP (i.e. using Actor Framework). They are brought in by management to evaluate the situation and get the product ready for market. Of course management will listen to the CLA as an expert (as they should).

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.

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

18 hours ago, MarkCG said:

I would love to see NI do this. It would open up a huge new field of application for LabVIEW. I thought NI couldn't do this because of their agreement with Xilinx, to prevent NI from taking over Xilinx programming tools' share of the market. It would be a real chance for LabVIEW to survive and thrive.

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.

1 hour ago, bmoyer said:

I was wondering how you make the front panel display update lossy.  Currently, when I want to do this, I check the Time of the event, and if the event is, let's say >1s old, I don't bother updating the display/indicator.  If that how you go about it, or is there another way?  Is there a way to only get the latest event and ignore the rest?  I'm asking this mainly from the perspective of using your Messenger Library toolkit.

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.

50 minutes ago, Arka Dipta Das said:

1. to create a stream of historical data points (say values generated in the last 1000 iterations of the loop) and then find the highest value in that array. Data points older than 1000 iterations are not required and I would want them to get overwritten.

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

20 minutes ago, Mads said:

I would not be surprised if NI now (wrongly) thinks that they do not need LabVIEW to make their hardware unique (spending so much time and money on NXG might make it all look like waste...). I hope I am dead wrong though, and that they consider themselves just as much a software company ("the software is the instrument" after all!).   If not, I hope they at least spin off a separate company soon enough that will. The latter would be riskier for the future of LabVIEW/G than the former (having to establish a different sustainable business model), but might also leave us developers with a higher reward. Especially if the alternative is a dwindling LabVIEW / NXG that is geared towards configuration only.

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.

On 6/19/2020 at 3:11 PM, Michael Aivaliotis said:

I discussed with @Mark Balla and we figured out a way to get all the old videos that used to be on the Tecnova site up to Youtube. It will take a few days but this is in progress. Probably within a week all the videos should be up. I will update this thread with progress.

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

10 hours ago, mcduff said:

It appears that NI is a hardware company rather than a software company. LabVIEW is developed to drive sales of hardware. This is similar to Apple, OS X, iOS, etc, are all developed to drive sales of hardware.

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.

29 minutes ago, Mads said:

(The hardware ties might unfortunately be one of the things that prevents LabVIEW from becoming all it could and deserves to be though; the graphical champion of all kinds of programming. )

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.

2 hours ago, shoneill said:

In a way, the new announcement is a bit like "this isn't designed for you, do you hear us loud and clear?"

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.