hooovahh

My go to site for this kind of thing was Flaticon but man this place is even better.  Any idea what the licensing restrictions are?  I couldn't find anything about that other than it is open source with no specifics.

I don't have a solution to this but am interested in the topic.  Darren also recently mentioned that this should work in 2020 for VIMs without the hacky work arounds found here.

I think searching is limited to 4 characters or more.  I'd also suggest Google is a better search tool than...well anything.

Just an FYI Pi4 isn't officially supported by LINX yet, but several people performed some manual steps to get it working.

So the Pi3 can be deployed to with Linx 3.0 as you may have found.  This is an official toolkit from NI that adds the target in the project and you deploy to it like any other device, and is free.  There is no front panel or UI when running on the Pi so keep that in mind.  But the code can be deployed and set to run on startup so that it runs headless.  There is some licensing to be aware of, specifically it can't be used on any commercial applications.  NI has said that in collaboration with the LabVIEW Community Edition (free as in beer expected release in May) that the Linx toolkit is to also have some kind of new release.  The same people that make the Arduino Compiler also make a Pi Compiler which can be used for commercial applications and has the front panel running on the Pi so you can plug in a monitor and see it.

Other than the Pi, the MyRIO is really the intended platform for students.  NI has partnered with Universities to offer a discount bringing the price of one I believe to $500.  I'm not a student so I can't see it.  But used ones on ebay pop up all the time from students who bought one for a class and no longer need it.  I picked one up for under $200.  The price of a raw Pi ($30-60) compared to the MyRIO ($500 retail) is a huge jump.  But NI justifies the price with all the stuff you get.  I mean the raw Pi doesn't even come with a case.  But the MyRIO has a real-time embedded Linus OS, an FPGA, built in Wifi, USB network, USB host, a bunch of IO, and the support of NI.  If your project needs an FPGA, and you want to program it in LabVIEW it is by far the cheapest option.  If you don't need an FPGA then it can be seen as over priced.  I'd start with the Pi3 and Linx and see what is possible.  There are lots of online videos and tutorials and the upfront cost is pretty low.

What is your use case that you need to turn it on and off?  I suspect you already know but there is an INI key that turns it on and off but is only read on LabVIEW start.

Okay I'm done guessing without actual testing in the environment.  In Windows -1 on the Read From Text File, and Read From Binary File both read the whole file.  I feel like there is a bug or two found in this thread.

2 hours ago, ShaunR said:

OK. Got hold of my Linux Box with LabVIEW. Wire a number of bytes to the "Count" (1024?). Ignore the error 4 if you demand too many.

Oh yeah, just wire a -1 and you get the whole file.  I always forget that.

Thanks, added up through 2020.  Even though it isn't actually released, lets just assume it does get released someday and that we won't need another reminder to update it until at least 2021 is out.

Permissions might prevent the reading of the file.  If you do a Open File maybe even set to read only then read the file you might have better luck.  Also calling a system exec and reading the standard output might work as well.

Neat idea editing the control itself.  But that solution is only going to work if you don't mind having no control over the GIF and don't mind looping, and if you don't need to update the GIF at runtime based on an existing file.  The demo I showed saved the GIF as a constant in the block diagram because it is faster, but I have some disabled diagram code that will instead read the GIF from a file.  It then will play the first half of the GIF, then wait for the saving to finish (random number) then play the second half.  Is there a site where simple animations like this can be used for free?  Also back saved to 2016.

2016 Save Demo.zip

I get your point of the multi menu setting isn't very quick to change.  That being said I sometimes mess around with conditional outputs, and with arrays I might be concatenating, or conditionally concatenating, or indexing, or last value, or conditionally last value.  And I just think cycling through all 6 possible combinations would be more annoying than a couple right clicks.

On 1/9/2020 at 12:42 PM, X___ said:

Not that I could care less, but VIM, which were introduced in ODG (old gen) are challenged by them 

You can call the non-NXG LabVIEW IDE what you'd like since NI just refers to it as "LabVIEW" but the designator I've seen most commonly used is Current Gen (CG).  But maybe ODG would be better since, well some day it won't be current gen...unless NXG is always going to be coming next.

Anyway I hate units too and have left them behind.  I feel bad for those that do use them as it is an official real documented feature of LabVIEW, but just has too many places it doesn't work as expected.  It's a feature I feel like the majority of NI and LabVIEW users have forgotten about.

Over the years I've been using a portable version of Gimp for ICO file editing.  In Windows 10 I've found that having 256x256, 48x48, 32,32, and 16x16 work well.  I mean you can have 128x128, 96x96, and any others but it becomes a support problem having to make all those for every application.

Over on reddit someone asked for suggestions on how to make a sliding UI like you might find on your phone.  I thought it was a fun challenge so here is my very rough draft that could probably be turned into a QControl.  And a video.  At the moment you can only change the settings of booleans and of a selection like the days of the week I show.  I planned on putting code for handling string and numeric value changes but probably spent too much time on this already.

Android Sliding UI Demo.zip

Okay I edited the spec file to start with the following:

[Package Name]
Name=oglib_lvzip
Version=4.2.0
Release=1
Display Name="OpenG LabVIEW ZIP Library"

Then I zipped the source back up and renamed the zip to oglib_lvzip-4.2.0-1.ogp.  I then installed the package and it didn't say "Upgrade" but instead said "Install".  But after installing there was only one entry and the result was the upgrade was successful.

Thanks, good to know.  I took your 4.1.0 release (maybe it was b2?) and edited it to make a package that was considered an upgrade.  I thought the changes I made were to the displayed name and version.  But now that I try to do the same with the 4.2 release in this thread I can't make it work.  I keep copying more stuff from the existing spec to the new one and it isn't working...I'll keep playing around and let you know if I get anything conclusive.

As always, thank you very much for this continuation.  Inflate/Deflate on Linux RT is important for a side project I have lately so this is awesome.  I did notice that in VIPM if I open your package and already have the previous OpenG zip package installed, it doesn't do an upgrade but instead performs a new install.  It appears that the internal name of the package, or versioning changed in a way that VIPM doesn't recognize it as a new version and will install it along side the last official release of OpenG which I think was 4.0.  I was able to edit the OGP spec file and create a package that convinced VIPM that it was an upgrade.  I was curious if this was intentional to distinguish it from the official releases.

Oh it seems the old package name was "OpenG LabVIEW ZIP Library", while the new one is "OpenG ZIP Library", I think this combined with some version changing is what I needed to edit.

13 hours ago, bjustice said:

Thanks Hooovahh, I've used your TDMS concatenate VIs in a few places.  Really convenient to see this wrapped in a VIPM with a few other tools.  Will install this right alongside Hooovahh arrays

The VIM Array package is a dependency, and actually included in this VIPC release.  It was just easier for me as a developer than trying to remove the dependency, and easier for you guys if everything is in one file.

I haven't tested everything in there on NI Linux RT but a few of them I have.  The only thing that uses any thing questionable is the Circular buffer has a compression option where it zips the circular buffer before logging it to disk.  I used the native LabVIEW zip API so I suspect it works on Linux RT...but I forgot to test it before posting it.  Everything else is just pure G and I see no reason it wouldn't work.

On 12/5/2019 at 4:14 PM, TomOrr0W said:

Brian's original attachment is also listed as unavailable.

I also can redownload it, you likely need an account.

Now we are digressing a bit but I also have an old piece of marketing I like to show off inconspicuously.  At NI Week the last few years NI has various buttons that say phrases for that years' theme.  Usually people grab a handful of buttons and put them on the lanyard you wear with your badge on it.  I won't go too over board but I'll grab a few and put them on, but mixed in with them is a LabVIEW 7 Express pin I was given years ago by someone that was at NI Week the year LabVIEW 7.0 Express was released.  It is old enough that it is starting to rust on the back a bit but LabVIEW 7 (and 7.1) were my favorite versions for a long time so I wear them.  Last year someone was looking at my various buttons and saw that and asked where they could get the retro NI Week pins and I had to explain where it came from.

I don't have anything to add other than I've seen this but not in any recent projects I've worked on.  It always frustrated me when I'd drill into some VI that was taking forever and it would be some property node or Read/Write/Open that was supposed to have a small timeout.