Michael Aivaliotis

The keys can be any type. A for loop will do it easily: Watch this presentation by @altenbach :

I've been able to connect and deploy code over wifi. However, I can't use the DNS name over wifi so I use the IP address. I'm sure there's a way to get that working but haven't needed to figure it out yet.

Curious, does this change your choice in using them or is it purely academic?

My understanding is that Maps are the same as variant attributes. Except with maps, obviously you don't have the overhead of VariantToData or DataToVariant, when inserting data or looking up data. That can be a huge overhead in some cases. Plus you need support code to prevent variant conversion errors when using the wrong typecast. Variant attributes are slightly more powerful than Maps because you can insert any type. However, one could argue that this is a characteristic that leads to messy designs. The same variant wire could contain mixed values types within it. Each with its' own type conversion VIs. I think if you've been using variant attributes and it works for you, I don't think you need to rewrite everything. But they definitely need to be considered in new designs. Because you don't have the overhead of creating all the glue VIs for the data conversion, they are frictionless to use and start using out of the box.

Lack of NIWeek content has prompted @Steve Watts, to start VIWeek. See his post here: https://forums.ni.com/t5/Random-Ramblings-on-LabVIEW/VIWeek-Making-Trouble-Again/ba-p/4044162 LabVIEWWiki Page.

@Rolf Kalbermatter, PM me your address and I will send some your way.

i watched the video. Yikes, ya, that's pure garbage.

Inconsistent to a post i made 10 years ago? Besides, that was related to CG. I'm not advocating for removing an engrained CG feature. I thought we were discussing NXG. My assumption is this feature hasn't even beed implemented in NXG. There is a lot more work required in NXG to make it even barely usable. Lack of continuous run is not a problem in NXG. Lack of everything, is a problem.

I can live without it. On the level of priorities for NXG, this has to be the least important. Just drop the vi on the diagram and wrap a while loop.

I can't live without them.

Oh, so it selectively only works for clusters then. Well at least NXG is consistently inconsistent.

So I guess NXG doesn't support dot notation unbundling.

So I took a look at the code that pulls the device info and ya, my assumption was correct. Actually, not sure why they are even reporting on the model type. It should just return the generic type. Like Raspberry Pi. No need to report the exact model, since you will always be wrong and really, it doesn't matter.

I have the same board. This is what I did. Download the RaspBerry Pi Imager v1.2 and used that to format a microSD card used for the Raspi. Select the first recommended OS: Raspbian Boot up the Pi with keyboard and mouse. Walk through the startup config (installing updates, etc) and wifi setup. When asked to enter a new password, ignore this and just click next. Reboot as suggested. Go to RaspBerry Pi configuration and on the Interfaces tab, enable SSH Open a command prompt on raspi and type: sudo raspi-config Select 7: Advanced Select A1: Expand file system. (this will expand the file system if it's not already expanded) Reboot In LabVIEW select from the Tools > MakerHub > LINX > LINX Target Configuration Click the connection button and it should connect. Hostname: raspberrypi, username: pi, password: raspberrypi. These are all the defaults. Click the Installation button. Click the Update button on the installation page. it should go through the process of doing the update. At some point the raspi will reboot. this is part of the process. When the raspi reboots, the LINX target configuration dialog will lose connection and give an error. This is normal. it will take a while to reconnect. Eventually, it should come back. If not then click the Connection button and try to connect. The Installation panel should now show the installed version: Click on Launch Example. In LabVIEW, right-click on the Raspberry Pi Target and select connect. This should should show the deployment progress dialog and after connection a small green indicator will appear in the target tree You should be able to execute (run) the VI now. Everything should be good to go now. Sometimes you will try to connect, in the project, and then you will get an error not connecting. If that happens, just wait and try again. I find that the connection is more reliable if you use the IP address of the raspi instead of the DNS name. To specify an IP address, right-click on the Raspberry Pi target and select Disconnect. Then right-click again and select properties. In General, enter the IP address of the raspi. Then click OK. To find the IP address of the raspi, type: hostname -I in a raspi command prompt. I think the reason why the log message states Raspberry Pi 2 B, is because the LINX toolkit is old and that message was probably not updated to handle all the new boards that have come out since release? Not sure. i'm getting the same message on my system even though the board is Pi3.

Considering development was started years before even the CABs were a thing. i'd say too much money. For a product that is not used by the majority of veteran developers, this is a problem. This is similar to the Star Wars franchise that was taken over by Disney. They decided to move forward with new characters and stories and burn the past. I'm hopeful that this will still evolve and improve over time. ...while I'm still alive.

That works. Ya, I get it. But a new view wouldn't hurt for those passionate OOP users. Similar to the Files tab, you could have a Class tab.

As a side-note. In 2020, NI changed the "change inheritance" dialog to "change parent class". Most likely due to interface nomenclature. But this triggered a thought in my head. Why can't we get this class relationship view inside the project tree? It seems useful.

Maybe a fly-out menu.

Checkout @ElijahKerry's home automation project I also featured on my VI Shots livestream. It's a great demonstration of how to interface to NXG webVIs to get a nice interface into your hardware:

It would be great to have a project menu item, goto parent interface:

Well considering NI owns MCCDAQ... It could be a good thing or a bad thing.

I'm investigating this hardware which might fit your requirement: https://www.mccdaq.com/DAQ-HAT.aspx

I'll be putting out videos on testing all the hardware out there and compatibility with LVCE, over time. As I do, I'll be populating this page: https://labviewwiki.org/wiki/Linx_Toolkit_Hardware_Compatibility_List If others confirm compatibility, then please update that page.

Ya, you're kinda in a gray area, between release dates. However, you can still download it and play with it. That's what VMs are for right?

The LabVIEW community edition, community is tiny right now and it's up to all of us to build it up and help others. We are the pioneers so to speak. Don't forget we have the LabVIEW Wiki to use as a place to create compatibility tables and information. Creating a LabVIEW compatibility table should be the first thing on there, actually.