hooovahh

Glad it eventually worked for you. After several spammers took over LAVA extra restrictions were put on account creation. I suspect this is part of the issue you had.

I never thought about it because of muscle memory. But logically it should be there.

I did do something similar years ago and posted the code here. With a youtube link demoing the graph functions. I never actually used it on a real project but put some decent time into the UX. It also allows for dragging out the graph into a new semi transparent window. It is not a generic framework, and mostly a proof of concept that could be used in an application, if you don't mind the various limitations, and restrictions.

I don't have anything to contribute to the development here. Only to say that I really like this type of function, and looking at your source it sure looks efficient. Thanks for sharing.

This is pretty accurate. I know one ex-coworker in particular had an RSS feed push to his Outlook every post on LAVA. When LAVA had a major crash his Outlook was used to restore as much content as was possible. As for the content moderation, we try to self police our selves, enough to not get on NI's bad side. I have very rarely ever needed to intervein. One time I had to ask one user, to tread carefully on the topic they were sharing, but I did not delete any content or post. Thanks for the additional history. Jim has mentioned this story to me in the past but I didn't remember the details. I believe there was a meeting with NI where they were insisting that the scripting code wouldn't be made public, and someone called their bluff basically stating the tools for scripting are already being made by the community, and that if these were good enough for NI to use, we should also have access to them.

You shouldn't need to delete and reinsert for the icon to be updated. Just close and reopen the builder if it is open to have it refresh.

That's because you didn't add it. The Palette does not show all VIs. It is a place where you can add your VIs, or directories that you want it to show. If you added a VI, and the package builder already has it open, then click File >> Close, then pick your project in the new window. Then go to Palette, then Right Click >> Insert >> Control or VI and pick your new VI. This video shows some of the process even if it is older.

Why would you repeat steps 1 and 2 every time? Just open the the VIPB you made from the last build you made, then click Build Package. The Palette you made previously will only have items removed if the file it references no longer exists. You may also want to update the Release Notes or Change Log with every release but realistically that's all you should have to do. Is your Source Directory and palette getting wiped away after each build?

VIPM has an package builder that is free, and has some really nice features. One of them is the ability to make a palette laying out items how you want. Then installing this package will give the user the API you want them to see. You don't need to create the MNU files your self manually, but if you do use the Palette API built into LabVIEW which lets you read and write MNU files.

Probably. Again NI-CAN drivers, which you need to use your 8473, only work on LabVIEW 32 bit. Do you have LabVIEW 32 bit installed? Do you have the NI-CAN drivers installed? Do you see the "CAN" palette under Measurement IO? If not then you need to resolve this. Sorry.

No you can't. This lets you use XNet hardware (which I don't think you have) but use the older NI-CAN drivers. This was intended to help developers transition to the newer XNet hardware but use their old software. You cannot use any XNet sessions on the 8473 hardware.

I can't open it at the moment it is new too of a version. But based on the name it looks like it is again using the XNet drivers not the NI-CAN. You need these drivers for the USB-8473.

I'd need to see some code. For NI-CAN I usually start with the example provided by NI. Get that working first.

Oh I'm sorry I did a quick google search and of course the first search result shows a picture of an XNet device but when you click on it it shows the correct one. Well in that case you need to use the NI-CAN drivers which also appear on the Measurement IO palette. Note that you can't do the Signal API in NI-CAN with that hardware and can only use Frame API. But that's okay my conversion library returns frames. Part 3 of the CAN blog also goes over NI-CAN hardware. And again there are examples in the Help >> Find Examples. NI-CAN hardware is old and not getting updates. It also is only 32 bit binaries so it only works in LabVIEW 32 bit, but can run on 64 bit OSs.

With the XNet drivers installed there will be a new palette under the Measurement I/O for XNet functions. Also in the Help >> Find Examples there are several thing showing how to read and write frames on the hardware. Additionally I have two CAN blogs that might help out with Part 3 talking about XNet code for doing basic frame functions, and Part 6 which talks about the different XNet session types. But also if you are just dealing with CAN signals, and not frames you don't need my conversion library to work with XNet hardware. You can create the signal sessions and do the writing as single point session types which the hardware will then retransmit at the rate defined in the database. My conversion library is primarily used for situations when you don't have a Signal API and just have the raw frames.