Neil Pate

Uninstalled 2020 when my computer fan was spinning up for no apparent reason and then I seem some VIPM Browser stuff chewing at my CPU. That is odd, I thought I disabled it.... oh wow the tickboxes cannot be unselected so last time I thought I was turning it off I was actually doing nothing. Installing 2019, thanks for the link @Michael Aivaliotis. By the way got any hacks to allow VIPM 2019 to manage LV2020 packages? This sucks 😞

@Rolf Kalbermatter when is your kickstarter launching? You know the one where you write all this useless but interesting crap down in a nice coffee table book. I would back this project...

Yeah I was quite surprised to see the new VIPM hidden away even when I thought it was turned off. Run with Windows start? Hmmm, no there is enough other crap starting then. Run with LabVIEW start? What??? Are you joking? LOL never.

I used something like this about 5 years ago in a lab test. Interfacing with it over VISA was really easy it pretty much performed flawlessly.

Is this what you want? I still don't really understand the subtleties of all the different scientific vs floating point formats and normally just play around until I get what I want. I find going into the Advanced numeric formatting is a huge help as it basically tells you the exact formatting string to use. Especially useful for timestamps!

Yes but that is no longer Engineering formatting which is where the confusion is coming in. Format into string should be able to give you what you want, I will put an example shortly.

Aren't engineering strings always multiples of 3 digits? You cannot have an engineering string 1.2x10E10,it will be 12x10E9 Maybe I misunderstood the question. if you want advanced string formatting you can use the format to string function, it allows a very flexible formatting string. Sorry on mobile now or would put some pics.

Thanks AQ, you are the first to actually spell this out in words that make sense to engineers. Not sure too many here are going to like it though! ps: I liked your post due to its honesty and absence of marketing weasel words, not because I think this is a particularly good strategy for NI. Maybe I have just had a weird career but in the 20 years or so I have been developing LabVIEW based solutions virtually never would a custom off-the-shelf piece of software like Signal Express or similar come anywhere close to doing what I needed it to and it would require so much customisation that the benefit would be so low. To me LabVIEW is a programming language or RAD tool and the responsibility of NI is to deliver first class hardware with amazing software to help me bring the two together and that is it.

The new colour scheme is growing on me, I quite like the green. The logo I think is entirely forgettable but this is really not important to me. Regarding the name change, were we not already referring to them as NI anyway? I think what we are forgetting is that none of this guff is for us... we are already customers and need no reminding of the benefits of spending your whole instrumentation budget on a cRIO! This stuff is to get the next million customers, the young engineers who might have never heard of National Instruments. The slogan is meant to ignite passion in young people, not to excite the already battle hardened. I do think the event was completely overhyped, but this is what marketing is about. In the short to medium term absolutely nothing is going change just because it cannot. A behemoth such as NI has so much momentum (or is it inertia... always get that wrong) that things will take time to change. NI was stagnating anyway, so this is probably a good thing.

please post again so I can double laugh...

I did look at your Github page but did not try your code as I though it was the broker only. However upon closer examination I see it does include a client also. Would it be of interest to you to see if I can get it connecting to my Azue IoT hub? Edit: there seems to be an error in the project, the two Destroy.vi are not there. Removing them manually seems to fix the Test Server e I did try make the TLS changes and connect with sensible parameters but it did not seem to work. I can try again tomorrow if you like, otherwise I am probably going to park this here for now as I have a working solution with the other MQTT library.

cannot unsee this now!

Mixed messages here... I was poking around tonight trying to bring a cRIO VM up to speed and realised just how many places on disk or in MAX and other applications they use the name National Instruments. Changing all those over to NI is going to be a job even bigger than developing NXG! This is going to get pretty confusing to the next generation of ambitious engineers using the products.

WOOT! Just tested this MQQT library running on a simulated cRIO in a VM and it also works and can talk to my Azure IoT hub 🤩

Wow that does look pretty similar! I guess the missing square in the top right corner makes all the difference though, there is no way anyone could get confused. I am not sure sure about the colour appearing in NXG though. new-NI has collected lots of data which conclusively proves that engineers and scientists are actually put off by colour and so are sticking to light grey, dull grey and washed out grey.

This is the only change I made to the MQTT library. Simples 🙂

@mads Awesome, it works! Thank you for your suggestion. I did not realise TLS could be done "simply", I was messing around with certificates and stuff and getting nowhere!

Thanks, I did actually search but did not press enter and just bailed when the Keywords list was empty!

Yes I am more than happy to pay for a commercial toolkit, but I did try this out also and it did not connect either. I will get in touch with them I think 🙂

Wow, 2020 could really do with an example of how to use TLS!

Thank Francois. I believe Azure does support 3.1 but I cannot recall where I saw this info. I think the problem is the missing TLS which I am now digging into. Now I am down a rabbit hole of security concepts and terminology that I have only ever had a passing interest in. TLS, X.509, primary thumbprints 🤯

Thanks, I am actually already about half-way through the 2020 installation so I can check out the TLS stuff. That library you mentioned is what I am using, I did try modifying all the settings that seem sensible (for example Azure IoT hub uses port 8883) but it still does not work. Actually the connect seems to work, and the publish does not give any errors but no data appears in my hub. I am still very much a newbie in Azure IoT so there is a lot to learn for me.

Hi, I am trying to send a simple message to an Azure IoT hub. I am pretty new to all this, but have followed a few tutorials and Pluralsight courses and can successfully send a message from VS Code to my hub. What I have not been able to do yet is send a message using LabVIEW. I have tried several different MQTT libraries, without any success. Has anyone done this kind of thing before and can offer guidance on which toolkit they used? I am using VSCode to generate the SAS token and using that as the password. Edit: I have been able to send some messages using simple C# code, this code works fine.

The whole IDE is unacceptably sluggish. Doing any kind of block diagram create/remove space feels terrible. Everything just takes a few hundred ms to a second longer than it ought to. Tearing out tabs into new windows feels so heavy. When I start NXG now from fresh I get a total system freeze where I cannot even interact with the OS for about 30 s. It does not happen on subsequent openings but is still quite disconcerting.

You guys lost me days ago, but I love reading this. Please continue to share 🙂