hooovahh

So does that mean that this deprecated function is still semi-supported? I assume it was deprecated for a reason, is it unstable under any known circumstance?

I think multiple sessions to the same running VI has been supported for a long time. It is really giving different sessions to different users that is the tricky part which I tried doing with reentrant main VIs. What I'm saying is if you want 2 or 3 people to see the same page, I don't think any thing extra needs to be done but they all will see the same view.

I don't remember that being an issue. That being said it might not be a bad idea to append the instance ID to all UIDs just to ensure that it is going to the right place. Still I did experimentations a while ago and I'm not sure what I did but I clearly had something working (or seemingly working) a while ago on an internal version. I'm working on other projects at the moment so I haven't had time to support this, and with NXG seemingly getting better all the time it makes me want to look to using that for things like manual panel.

And referenced in that post is my work around. It isn't so much that the PNGs are having meta data stripped, it is that they have a custom image viewer which adds a scaling size. Viewing the raw image still allows snippets. Also downloading the snippet might work too. https://forums.ni.com/t5/Feedback-on-NI-Community/How-do-I-get-a-snippet-from-the-board-into-my-block-diagram/m-p/3763571#M15575 So Michael here is a working snippet from NI's site: https://forums.ni.com/t5/image/serverpage/image-id/214063iB57FB649CBEA2ED8

EXE - I don't remember all that is involved in making this work, but I did have it working. I think the main thing is getting the paths right to the various external files needed for HTML generation. Multi User - I did some preliminary testing with this by using reentrant VIs. The idea was that each request to a page would create a new clone of a VI and that close is that that user would see. It worked okay, but was a bit of a hack. So it is possible but wasn't pretty. Pop-Up - Never looked into this sorry. I bet something could be done since there is a dialog on the HTML page for configuring the refresh rate (click the gear in the lower right). I'm not good on the HTML side of things, just the LabVIEW side so I don't know what it would take to come up with dialogs and make them work. It would be possible for something but my suggestion might be to try to put the configuration on the same single HTML page rather than a separate dialog if getting that to work is too hard.

One of the reasons I heard that NI is making this a separate add-on is that the bundle also comes with some NI cloud hosting functionality. I'm not sure what it is, and I'm currently not interested in it. But there is probably some additional overhead for every user that takes advantage of that part of the toolkit. It wouldn't be as profitable but NI should have made the WebVI part of NXG, and had the cloud hosting be a separate toolkit on its own.

Oh that is an interesting request. In debugging I would do something like that where I would run the VI, it would generate the HTML and open it, and then from there I could CTRL+Shift+I (inspect source) and then look at all kinds of things like network traffic and UID values. I can see why it might be valuable to edit the HTML code generated. I'd suggest some kind of post processing VI which edits the already generated HTML, rather than forcing your HTML to be used. This is because things with the HTML could be changed on a run of the VI, like UID values, labels, adding/removing controls, etc. Starting with something that works, and then running something to post process seems like a better design in my mind, but that is without knowing the kinds of edits you make to the HTML.

Oh man how I hate it when I don't check LAVA for some amount of time and interesting discussions take place. Maybe interesting discussions take place because I take a break?... Anyway the killer feature in my eyes is WebVIs. Be able to run G code in a browser! On paper that is awesome. But NI choosing to make this an add-on at an additional cost makes it less accessible. But to answer the first question I do use NXG on a current project...but it is just for the web stuff. The large part of the application runs in a current gen LabVIEW EXE which publishes data where the NXG web VI can perform requests and show formatted data. Pretty minor of a project and several work arounds for things that were missing. As for when do I think I will have a real full application in NXG? Maybe 2021, but it will all depend on feature set. And honestly with 2018 now being stable, and having all the features I want I don't see wanting to upgrade. I don't know of any new feature planned for the future that would make me have to upgrade. I do like the flat UI look, and NXG is decent with that. Having NXG style in 2018 is nice, and my UI's lately are a mix of system, NXG style, JKI Flat, and Flatline. NXG is quite limiting at UI design still which is just another reason to stay in current gen.

Wow I never knew about that and the fact that it can handle dotted properties is awesome. Darren is there a reason we shouldn't be using this thing that does exactly what we might want when the proper method lacks this functionality?

Here is an article to wipe Linux RT controllers using SSH. https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019LfbSAE&l=en-US

Someone from NI can chime in, but I think this is not possible and is one of those limitations of LabVIEW Scripting. QuickDrop has a CTRL+Shift+B that operates on a property node and it has a limitation of not working with "dotted properties". I assume that's due to a limitation with LabVIEW's scripting otherwise NI would have supported it.

Yeah but I wonder how much of a format this really does. I was experimenting with reading/writing NTFS drives from within Linux RT. All that was needed was a few commands to install the appropriate package through opkg. After that it could read and write NTFS USB drives just fine. At some point I wanted to start fresh so I formatted it through MAX. But after the MAX format I was still able to read and write NTFS drives. So I suspect this isn't so much as a format as a "Remove all NI software and config, and copy over the base image". All OS level things might just be left alone. I never really followed up on this, and I do have several controllers so I could have mixed one up and formatted the wrong one, I'll try to reproduce this test later today to see if it is reproducible. See edit, I thought MAX format didn't wipe everything, now it seems it does wipe more than just NI software as OPKG installed packages are removed. EDIT: Okay a few other things for anyone that cares (just me then?). If you are using the Legacy FTP, you can read NTFS drives but cannot write to them. Running LabVIEW VIs, and the web interface to look at the U drive returns errors, and empty drives, but FTP can read and transfer files. This is where my confusion came from. I formatted the controller and FTP could still read the drive. But since I couldn't write to it or transfer data to it without extra packages being installed, this means a MAX format does uninstall OPKG installed packages, so it probably does wipe everything and start from a fresh image.

I downloaded the web install last week and speeds were as slow as I expected due to our infrastructure issues. By that I mean it didn't seem any slower than usual, maybe the developer suite's are cached differently. Also geographic location can be a factor since NI has several data hosting locations and it is supposed to pick the one closest to you. Since all my internet traffic is routed half way around the world while at work I have no idea where my download came from, but I'm in the Detroit area.

I'm still searching but I had a similar issues. Someone mistakenly ordered the Windows version of the 9132 when we wanted the Linux RT. I asked NI what it would take to change it over and they said we would have to send it back getting a refund (probably minus stacking fee I can't remember) and then buy the new one. The reason was that the part numbers of the product were different and one example was that if we ever needed support it would be directed to the wrong place, and a replacement would give us the wrong one. I can't remember if I had this conversation in an email or online, or a private message I'll post it if I find it online.

Okay I'm in the process of downloading the fall bundle but I can say that I am thrilled to find that the F1 patch fixes a major crashing issue with access violation, and illegal operations I've been having. The cause is unknown but I suspect it has something to do with subpanels, splitters, and call asynchronous nodes, but to be honest it could be anything I couldn't nail down the issue. And if patches are like the ones in the past, the 2018 SP1 F1 patch must be installed over top 2018 SP1. I suspect this was a patch discovered after going gold with 2018 SP1 and being sent through the validation, and DVD pressing process. A pain for sure to have to download a huge thing install it, and then realize there is more to download and install, but if it finally means being able to get LabVIEW working again I'm happy. EDIT: Seems my issue was likely CAR 715018

I ran into this several times in the past and haven't experienced it lately. I'm guessing NI has fixed it in future versions. It is still annoying and so I'd update to the latest patch level you can in the hopes it is resolved there. Like I said if you know where there is an issue just add an Always Copy, but the problem is when VIs are behaving that way and you aren't aware of the issue.

So a while ago I wrote a XNode that would add functionality to the traverse for GObjects. One thing it would do is order the references based on their positioning on the front panel or block diagram. The most common use for me was for something like a grid of buttons. I would want them ordered from left to right and top to bottom so I made an enum input to the XNode that orders them after finding them. It would also return the reference as a boolean so no casting was needed after. Of course this goes with the normal "XNodes are experimental" statement but you could look at the code and see how I did it if you wanted to not use it.

Your usb2RS232 device is likely a counterfeit Prolific, or FTDI chipset. The official makers of Prolific and FTDI have pushed out driver updates which disable counterfeit hardware which previously worked with the official drivers. At one point an FTDI driver disabled the counterfeit hardware making it not work in any computer once it had be used with the official driver. These updated drivers have been published as Windows Updates, and as a result they have stopped working unless you manually roll back drivers and force uninstall the newer ones. Not saying this is your situation but it has been mine. You often have no way of knowing if counterfeit chips are being used. An update will come through and they suddenly stop working. As for the LabVIEW thing yeah that is on NI. But to be fair they can't support every operating system with every version of LabVIEW and the more they cut out the more resources they have for other support issues.

Throw in an always copy liberally and I'm guessing things will work start working. If you can isolate it well enough send it to NI for them to investigate. What version of LabVIEW and patch level?

I don't share your opinion of Windows 10. I haven't had hardware access issues, and as others have said current gen LabVIEW is supported on several operating systems. 2015 SP1 is supported on 6 different Windows OSs according to this table, that seems pretty extensive to me. That means Virtual Bench 15.0 should work fine on XP. Expecting Virtual Bench drivers to support 8.5 seems like a stretch since it came out 8 years before the first release of Virtual Bench (correct me if 15.0 isn't the first release of Virtual Bench) There are things I hate about Windows 10, but the start and tile really doesn't bother me. In the past I have installed Classic Shell to get a basic looking start experience, with a skin that looks like Windows 10. But even on systems that I don't do this on it doesn't bother me. Windows 8.0 with the full screen tiles did bother me, but even then most of the time I just started typing what I wanted, or pinned important programs to the task bar, or used desktop shortcuts on systems I'd deploy to. Most users of my systems don't open the start at all, they just use the software I write anyway. And on systems I develop on I'm free to customize it however I want.

The real death of an API isn't when development stops, but instead the last time someone uses it as a dependency. (loosely quoting several people about existentialism)

VIPM years ago did have an Enterprise version (I think they called it) which was more or less what you described. It didn't have all the features of Pro but could subscribe to feeds. At the time it seemed like it was too confusing. There was free, pro, enterprise, and I think a 4th option. In the early days of package management, people (myself included) were confused about what features were good for what and it was hard to know what was needed. VIPM was the first package manager I ever used and several concepts about feeds, dependencies, and use cases just weren't well understood. JKI simplified this with a Free, and Pro making it clear when you would want one over the other.

I've never used VirtualBench but if the drivers aren't supported, then they aren't supported. The only thing that might help you is that sometimes in the past NI has done things like just used DAQmx for some features, and NI-DMM for others. So if you must use LabVIEW 8.5, I'd suggest trying to find the newest version of DAQmx, and NI-DMM, and NI-Power, that work with 8.5 and install it, and see if MAX recognizes the VirtualBench at least for those features.

So if it wasn't clear, this release had issues. It wasn't intended to be the final LabVIEW 2018 SP1 and was an version between SP0 and SP1 for testing. It was unintentionally released to the public and wasn't intended for the general public to use, and likely won't activate. The release was pulled and if you did download it you are better off not using it until the actual SP1 release. On top of not being intended for an actual release, and not activating, it also has a bug with upgrading from 2018 f2 to 2018 SP1 which is being addressed for the actual SP1 release.

Well I mean...it can be. ?