Jordan Kuehn

Does this work for cRIO and RT targets? Raspberry Pi running LV?

Fair enough. Good luck and please keep us up to date as you progress or need beta testers!

I assume you are familiar with these already? https://github.com/LabVIEW-Open-Source/LV-MQTT-Broker https://www.wireflow.com/products/software/wf-wirequeue-mqtt-toolkit/ I use the latter extensively, both in Windows and Linux RT. I have some curiosity regarding the first one, both the client and the broker, but have yet to try it out. I do not know how many of us there are, but I do use MQTT heavily and would welcome an additional (paid or OSS) toolkit. One feature of a native broker that I would love to see is the ability to cluster brokers like EQMX or other.

If still active I would appreciate the link as well.

https://www.ni.com/en-us/shop/software/products/embedded-control-and-monitoring-software-suite.html

That is working to measure loop iteration time. Stores the initial time in a shift register. Then each iteration takes the current time and subtracts the previous, while also storing the current time in the register for use in the next iteration.

Is your HMI a PC running LabVIEW or is it something else? If the former, you can certainly use Network Shared Variables and get quite a lot accomplished. Especially if you just intend to expose the data to the host code and let it handle the logic and controls directly. You can also look at network streams if you want lossless communication, and/or to pass command/responses. If not LabVIEW then you'll need to look at the protocols it supports and make a determination regarding where you want the logic parts to live. I typically find myself wanting to put as much in the cRIO as possible and keep the UI pretty thin/lightweight, especially if I want to have multiple UIs for the same device.

done

perfect. I think you can swap LVOOP in there too

One big upside to the Enterprise version that I can see would be the High Availability feature as a result of the Kubernetes clusters. I'm no IT expert, but with what I know about this it seems like a very good choice to break the various components into individual clusters and allow for individually scaling them out as well as redundancy.

I would augment that with "...without community presentations OR (many) R&D presentations...". I went to several and almost all were of the Marketing variety of NI presentations, while I think there was just the one from AQ on Interfaces that I felt was really valuable. I do like the exposure to new products, but I get the most value from the advanced software presentations that R&D brings as well as the community presentations.

At risk of derailing this thread, where is the documentation for these methods? I'm aware of local windows users and LDAP. Further, you do rightly point out the difference between systemlink and webvis. My conflation is due to wanting to utilize systemlink *and* webvis to serve data and dashboards to customers utilizing the same authentication method. As noted above the workspaces have issues with filtering properly using the system filter. I am only aware of workspaces as the ability to segment out accessibility of systems to users and even then I may want to limit data views via certain dates (system is on rent with different customers at different times), but that is another can of worms.

I may have misheard/misspoken here, but I thought they mentioned more open authentication methods/user management. Agreed strongly with this. With the price tag SL commands I shouldn't be making my own user management. Which is partially why I haven't implemented the method in the video I linked.

I too would like something native like this. We have dashboards that we use internally that customers would also use, but there is no built in method to segment that out best I can tell. The system filter doesn't respect workspaces either (shameless idea exchange plug) which would be one potential workaround. I do recall seeing some OAuth options on a slide (ETA: see the last slide I posted above) for the enterprise version which would be a step in the right direction. I had that presentation in my recent memory because I have it somewhere in the queue of items to try when implementing a customer facing dashboard.

I think this presentation from NIWeek 2019 may be on point here:

Enterprise version of SystemLink with containers sounds fantastic. Hopefully they will include it with the already expensive license cost.

Job Details Description Software Engineer What is a Software Engineer? The Software Engineer is responsible for maintenance and development of software that is core to our Freedom Series Completion System. The ideal candidate will have demonstrable software programming capability (specifically in LabVIEW), control systems experience, mechanical aptitude, ability to direct others, and an ability to operate in a fast-paced environment. This position can be located anywhere in the United States but will require some travel to Oklahoma City at the beginning of the position, and then as needed potentially for a few days to a week each month. Job Listing Here

This is brilliant. I imagine it could even become a standalone toolkit/extension of JSONtext.

We have gotten "media" recently. It took a few weeks and they mailed a piece of paper with a serial number on it.

I think Mads method will work. I think it's frowned on, but probably the most straightforward. Alternatively you could figure out what permissions are set on the script file and required for the operations it calls, then make all of those executable by the lvuser. All of this is annoying enough in linux, but then Linux RT user permissions and file permissions are even more complicated than usual as some permissions are reset on boot. This pdf is a good reference and I think is still valid despite its age. https://www.ni.com/pdf/support/us/ni_linux_real-time_security_user_guide.pdf

Two weeks away! I assume no LAVA BBQ?

With packages you can include files (e.g. an installer), and put them where you want them. You can also call post-install scripts. I think if there is a way to call the installer silently from the CLI you could script this. You are starting to tread on IT's world though, but sometimes you need to get it done and for it to work so perhaps you are best off doing it yourself this way Seriously though if they have the systems in a domain or something they might be able to handle the environment setup independently of your NI packages.

Isn't this the case with many acquisitions by NI? Buy it up and let it languish instead of developing or integrating it?

You can call opkg install from the CLI and manually install a package you have copied over. Some discussion here where I built such a package. We use SystemLink which makes it easy to add the custom feeds and such, but hopefully this could help some?

Cross posted to the dark side. Hello, I'm attempting to work with the launch remote actor function utilizing two cRIOs. I have a working AF application on one cRIO and I would like to spawn a few Actors to run on another one beneath my original top level actor, hoping that the top level actor will be able to interact with them as if they exist locally. I have watched this presentation from JustACS and have considered using the nested endpoints, but this approach seems more "AF-ish" and doesn't require extra communication actors mid-tree, or mid -> top of tree. My question at this point is that I don't think I have the dependency injection correct for a built exe. The example doesn't seem to address applications outside the IDE either. I believe I have gotten the VI Server settings working and can launch the actor from the Server side without errors now. I encountered some errors while working on the dependency injection. Note: these are built and deployed startup exes. I first started with something like in the webcast: And here is mine: However, I encountered errors on the Server side in the upper proxy vi until I added this loop: Now the Server side launches, but I don't see any activity from my remote actors. I expect at the very least to have some of the initial logging that happens at the beginning of their Actor Cores happen, even if there are other errors, but I see nothing on the Client side. Am I missing something simple here on the dependency injection? I attempted to include just a few actors at first, and then added all the actors that could possibly be linked in some way, added subvis to the always include in the build spec, etc. Any help or pointers here would be greatly appreciated. Thank you!