ShaunR

Is this really what we are up in arms about? Sounds like the sort of thing the LabVIEW haters group would be whinging over. I don't have this problem in 2009 

12 minutes ago, codcoder said:

But this isn't LabVIEW specific. There are a lot of situations in corporate environments where you simply don't upgrade to the latest version all time of a software. It's simply too risky.

On 10/14/2017 at 6:07 PM, ShaunR said:

Changing versions is a huge project risk. You may get your old bug fixed (not guaranteed, though) but there will be other new ones and anyone who converts mid-project is insane. In fact. I would argue that anyone who upgrades before SP1 is out is also insane.

1 hour ago, Antoine Chalons said:

Any chance the Encryption Compendium ever supports Linux (Ubuntu)?

Back at around version 2 Linux and Mac were supported but only Windows was distributed (see licensing below). Linux was a real pain to maintain so I dropped that. No one was interested in Mac so I dropped that too.

There are several reasons why Linux support is unlikely in the future:

1. The NI licencing scheme only works on Windows.
2. There is quite a lot of Windows specific stuff now like the use of the Windows Certificate Store and Windows Messaging for ICMP (off the top of my head-but there's more).
3. Linux is a real pain to maintain for. (50% chance of any one distribution of any software working out-of-the-box).
4. LabVIEW may be synonymous with the Dodo in the next year or two.

1. Has a solution but I'm tentative. 2. Is doable with a quite some of effort. 3 just isn't worth the aggro and 4. Well. Interesting times.

There are lots of reasons why *not*. Very few of why it should.

Tada!

Just released 4.3.0 with MQTT support (and, of course, examples). Have fun!

Eric Starkloff horse trades NI shares. The ones we are really interested in are the 50+% owned by the creators and their families.

I still have a feeling all these "Over by March/April" are a kind of propaganda.  NI's behaviour doesn't seem to be of a company about to throw in the towel-quite the contrary. I'm still quietly hopeful it will all fall through but hey! I'm a programmer! What do I know about this stuff anyway? 

5 hours ago, Mahbod Morshedi said:

Any good material you can suggest for me to start with GOOP would be appreciated in the meantime.

Just mention GOOP 3 times and it will summon MikaelH - who can tell you everything about it.

40 minutes ago, Jordan Kuehn said:

*ahem*

Not that I'm suggesting that you do bother haha.

Aha! Yes. Apologies.

12 minutes ago, Rolf Kalbermatter said:

Well. It's more likely a very resounding "I have no idea if I'm ever going to need that. For now I just refrain from commenting on the matter!" 😎

As you are the only one that has commented on it al all (indirectly). I think that's a resounding "don't bother".

Also means I don't have to look too closely at DTLS just yet 

So. that's a resounding "don't bother" on the CoAP then 

1 hour ago, X___ said:

I am looking forward to reading "Undo doesn't work anymore" in 2024Q3 and "colors are all gone" in 2027Q5...

🍿🍹

If Emerson buy NI, you can look forward to no LabVIEW at all.

11 hours ago, Mahbod Morshedi said:

I totally Agree and in fact i had that format originally. However, arrays gets rid of the cluster names and replace them wit the first item's name and for me keeping track was becoming difficult even with documentation. it was just easier to have the clusters that can have different name. I know that i could also use a simple enum for indexing but that would add an extra data that needed to add to my system.
I also have a duplicate of BG and HRS as an original data and manipulated data. This way when want i can revert back by replacing the data with the original.

I am very new to programming and do not have experience in data organisation and almost nothing about labVIEW classes and the NI documentation is just too simple and is not covering any real life application.
That is why I was asking for help.

Cheers,

Here is a List API. Seems complicated but it's a "managed" list with lots of features. Overkill for what you need but it demonstrates a point. You could use it for your data but then you'd have a dependency. I'm guessing you don't want dependencies at this point.

You'll notice it has two items in the cluster - Name and Variant (variant is a general type and think of it as your Cluster). The important part is that it has a "Name". This is a poor replacement for the Cluster Name (functionally) but it does enable lookups, even by regular expressions. It serves a very similar purpose but operates at run-time instead of design time

The name is just a string label. It can be anything. Granted it's not as simple as an enum but it does give much more flexibility and doesn't require design time editing of the control to make changes. The tradeoff is complexity. Now you have a way of making a list behave like a database but you need specific functions to look up and return data.

This, from one of the list examples, returns all items with a numerical label:

Intuitively you will realise that having duplicate data is not very useful unless you can distinguish between the original and manipulated. Up until now you have used the Cluster with an unbundle which has served you well but are now finding that you need to edit the cluster every time you add new variant of your data. The label gives you that ability at run-time instead of design time with a small increase in complexity.

However. Your biggest issue is compartmentalization - separating config from data. Now. What if only the List (aka data array) wasn't tied to a particular data type? Then, by thinking carefully about the labels you use, you would be able to differentiate between the different data types, different devices and different configs

There are other ways to approach this. But from where you are at present I would suggest this way - at least until you are more confident with your abilities. The database I suggested earlier requires a different mind-set and classes are a huge learning curve. This is a modest step from where you are to where you want to be.

25 minutes ago, Mahbod Morshedi said:

That is why I wanted to use a class to help me with ubn and bbn of the cluster data.

If you are going they way I think you are, all you will do is swap [un]bundles for VI's and add a lot of boiler plate. To be fair. You monster cluster isn't really that much of a monster-more like a tribble.

My advice (if you're not going to re-architect) would be just to split out the data from the config. Your All Scan data BG and HRS is actually an identical format so you could rationalise that into a single array which will make adding more of the same format easier (just add and index into the array-no need to modify the cluster to add more data). Everything else seems to be config data.

20 hours ago, LogMAN said:

break down your complex and complicated data types into simple and uncomplicated ones.

Break down your complex and complicated data types into a complex and complicated architecture.  FTFY

10 hours ago, Mahbod Morshedi said:

I have heard that converting everything to a class is the best approach

I expect you have.

Have you also thought about using an SQLite database ?

2 hours ago, Rolf Kalbermatter said:

Most likely because of its use of DTLS. 😁 OpenSSL's support of this was fairly "flaky" back when I did my Network library. Many problems were surrounding it, some of them were actually kind of unfixable with the DTLS standard at that time. Now this was around OpenSSL 0.9.6 or so, so I would assume that a lot has changed since.

And yes I got it to work, but only had done minimum testing with it. It was clear that more extended use of it would sooner or later bring out troubles with it. Some for sure in my interpretation of the OpenSSL API at that time, but some also unfixable for me without changing OpenSSL itself.

Last time I looked it was about 1.1.1e. I don't think it was much better. I bypassed it in the end because it needed callbacks for cookies-wasn't prepared to do that at the time. I'm hoping they've moved on from there with full blown certificate verification but if they haven't, I now have a place for callbacks in the API.

Quote

 

In LabVIEW 2014 and later, the PID and Fuzzy Logic Toolkit is included natively within LabVIEW Full and Professional Development Systems and does not require a separate license, installation, or activation.

 

source

I guess you don't have the Full or Professional LabVIEW?

14 hours ago, Jordan Kuehn said:

I have had a passing interest. I think you were extoling its virtues some time ago. But when I saw I'd be needing to build the LV implementation of the protocol from scratch I lost interest. I also didn't see a lot of wide adoption at the time in areas where I was working, but that is probably worth a fresh look.

Building the protocol from scratch isn't a barrier for me - I'm on a roll  The difficulty is that it requires DTLS (the UDP version of TLS). DTLS is something I've played with in the past and it was somewhat awkward to integrate into what I have currently so I moved past it and on to other features that I desperately wanted. CoAP would force me to look at DTLS again as it is something I've wanted, but never had a need for.

IMO CoAP is a far superior protocol to MQTT. I don't really understand why MQTT gets so much love.

Anyone interested in CoAP?

I think you need to do some LabVIEW courses and/or tutorials.

You're clearly are out of your depth here with even the concept of what LabVIEW is and how it operates at the most basic level - you have bitten off more than you can chew.

Go and ask ChatGPT how to make a LabVIEW program to add two numbers and you will see the difficulties you face. 

37 minutes ago, dadreamer said:

They introduced a token for smooth lines:

SmoothLineDrawing=False

That works. Thanks.

8 hours ago, X___ said:

https://finance.yahoo.com/news/ni-acquires-set-gmbh-accelerate-140000459.html

Interesting. Not the sort of behaviour of a company that's about to roll over.

20 hours ago, codcoder said:

Yes, of course. I can't argue with that (and since English isn't my first language and all my experience comes from my small part of the world, it's hard for me to argue in general 😁).

English *is* my first language and I'm not as eloquent as you are. There is no real argument here, though.

21 hours ago, codcoder said:

But that shouldn't mean LabVIEW development is stagnating or dying. It's just that those areas where NI excel in general aren't as big and thriving compared to other.

I still use LabVIEW 2009 for development because there is little that the later versions offered of significance. It's also robust, stable and fast. That cannot always be said for some of the later versions (looking at you 2011/2012). Some features that actually got us excited weren't even on the roadmap (VIM's anyone?). NI have been so far behind the curve for features that we want that we have all created our own solutions so if one of them actually gets implemented, it's a moot feature. TLS/SSL, for example was only released in LV2020 but I (and Rolf) had created solutions a decade before that. The one thing we have been yelling at NI about for about 15 years is Unicode which we cannot really make a native solution for. This is why I laughed when it was mentioned in this talk. I moved to HTML UI's and relegated LabVIEW to a back-end service through Websockets which solved the problem but it's a sledgehammer to crack a nut.

2 hours ago, codcoder said:

Idk, why should the failure of NXG mark the failue of NI?

I don't think anyone is saying that, so much, with respect to NI as a whole. But the effort and investment in NXG made LabVIEW (Classic?) the withered limb of NI, Now they have lots of C# devs who can't do jack with LabVIEW. From this seminar, it looks like this is a solution (lots of C# devs) looking for a problem (Cloudy stuff) and they see LabVIEW as a stagnant technology instead of the axiomatic driver behind their hardware it actually is.

Don't get me wrong. They can very easily move into this space and do all the cloudy stuff. But their view of how this will fit together is flawed (IMO). They are viewing it purely like an IT system rolling out images (think AWS Compute-IAAS) when, in fact, those images will be highly specialised LabVIEW installations for very specific and usually custom hardware configurations. 

2 hours ago, codcoder said:

But it never as been and that shouldn't mean it can't be thriving in the world it was originally conceived for.

They lost Test and Measurement to Python a while ago-arguably the mainstay for LabVIEW.

37 minutes ago, Elbek Keskinoglu said:

represent different experimental setups

I've really no idea what this means.

If you are just looking for a volume of any code then VIPM has hundreds of libraries (with source) that you can train on. You will have 10's of thousand of VI's with source to point your algorithm at. Apart from that, you will have to be more specific.

Artificial Insemination is coming for us, boys and girls.

You'll need to define exactly what "experimental setups" means - I've no idea