crossrulz

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.

Well, I'd say you've been lied to on the protocol.

Interestingly, all of the bytes (except for the initial byte) are alpha-numeric.  If I convert your hex values to ASCII I get:

Write: 00P004SOL1

Read: 00D0010

This still means nothing to me.  Just thought I would go through the exercise in case it sparks someone's thought process.

That manual also mentions "included cables".  You might want to ohm out that cable to see where pins are actually going.

7 minutes ago, rharmon@sandia.gov said:

Crossrulz,

What do you mean by "Then you need to read using the protocol of the device" The read buffer is always empty.

When I send this polling command the response from the UPS should be 7E05 0318 B004 52 the data being 1200 or 120.0V

1. Make sure you are actually following the protocol of the UPS.  What is the model?  Do you have a link to the programming manual (might also be in the User Manual)?

2. If you send a binary string to the UPS, I almost guarantee it will not spit back "120.0V".  It has a protocol defining the message format.

Since you are getting no data back, I am left to assume you are sending an invalid command.  Though, it is also possible the UPS is using a different pinout than you expect for the RS-232 connection.

Since it look like you are sending binary data, you really should turn off the termination character at the VISA Configure Serial Port (Boolean input on the top).  Then you need to read using the protocol of the device.  This should involve reading a start byte, message ID, data, a checksum of some type.

I'm also a TI guy.  The TI-83 was the recommended calculated in high school, but I already had a TI-82.  The only real difference was the handling of unreal numbers.  I had to do some special programing to handle i in my Pythagorean Equation program.  In college, it was the TI-89.  I used to have all kinds of programs I wrote/distributed, including one I wrote that was to handle an entire exam for one class.  I think they are long gone now.  I still have both calculators, but I usually end up using the TI-89 emulator on my phone.

No.  It is more like they just use the same library on the back end.  But a Map is not going through a conversion to a variant first.

On 5/2/2020 at 8:21 AM, Neil Pate said:

Speaking of quickdrop... "esseqz" really just flows out of the fingertips does it not? (Thankfully just by typing "Less" in the quickdrop you get want you want). I think the machine learning algorithm that was used to generate these "shortcuts" might need a bit more training data. Pity the algorithm did not at some point put their hand up and say, hang on, this is a bit crazy. Just look at the others,

"ess" for Less...

"erg" for Retain First Error

Those are the same as what is default in LabVIEW 20XX.  They were chosen by Darren specifically to only have to type with the left hand.

On 5/2/2020 at 3:47 PM, Neil Pate said:

And I had totally forgotten Run Continuously has been removed.

I remember being part of the discussion to remove it.  I thought it was supposed to turn into a right-click option on the run arrow.

My understanding is that the Linx Toolkit will be available in the professional LabVIEW 2020.  But that hasn't been released yet (hopefully mid-May).

Will this be recorded?  I will attempt to attend, but have appointment that will likely cover the first half.

39 minutes ago, Aristos Queue said:

You know how all LV objects are represented as cubes? What do you call just the surface of a cube? 🙂

To be a little more obvious: LVOOP Interfaces