Jump to content

hooovahh

Moderators
  • Content Count

    2,932
  • Joined

  • Last visited

  • Days Won

    199

Everything posted by hooovahh

  1. If your front panel is broken up into panes (which I think would help you if it was) then you can also set the color of the pane programatically with the Pane Color property.
  2. So I wasn't there but there was a public announcement at GDevCon about a new edition of LabVIEW called Community Edition which is the LabVIEW Professional version (I read that as application builder included), and completely free with no watermarks for non-commercial use. NI hasn't made any post about timelines, or other details yet but I hear those are in the works. This is obviously a huge thing for LabVIEW as any monetary barrier to entry will discourage new developers from experimenting with LabVIEW. And then there is the fact that those that are familiar with LabVIEW, can keep up with the newest version outside of their company, or when they are between jobs.
  3. I sent Michael an email. Not sure where that Contact Us goes but I don't see it.
  4. There is several efforts on getting the Linux RT virtual machine working with a few methods of success. I don't have the spare hardware or time to see if it is possible but I too suspect you can get the Linux RT OS on a desktop. My own concern is there is no support, and potentially the licensing issue.
  5. No you can't do what you are asking. There are a few things you might want to know, but none will totally fix your situation. Starting in LabVIEW 2017 there is a forward compatible runtime engine. Meaning binaries build in LabVIEW 2017 can be ran in the 2018 or newer runtime engine. When you build a EXE there is an option to force it to run in that one version of LabVIEW, or the newest one installed. Then if you wanted to run a new version all you'd need to do is install the new RTE and it would run in that. Obviously that is a relatively new feature and not going to be useful for you now. Also there is the fact that LabVIEW 2009 while not official supported in Windows 10 will most likely run just fine. I've installed LabVIEW 7.1 in Windows 7 and had no issues, other than tracking down old drivers to support it. So you might be able to convince your IT team that the 2009 RTE should be used. Without the source that really is the only way to run that EXE. The binary is compiled for that RTE and can't be recompiled for another target or platform unless you have the source.
  6. So most of my interactions with NI in that capacity are documented somewhere. If I presented at NI Week, it is available online. If I attended NI Week then I have expense reports on it (and I know I attended), if I present at a user group I post my slides after the presentation, if I participate in a beta I'll remember, or even have the beta VM still on my computer. So what I did was when my certification was about a year from expiring I just started adding up all the events and presentations I did. Once I reached 50 points I sent an email to NI saying what I did and when and how I was up to 50. They emailed back within a couple days saying I was then certified for another 4 years. The one thing you might have a hard time with is remembering what user groups you attended if you aren't always a regular.
  7. It might also be possible to load a GIF into a .Net PictureBox. I have some demo code for this but for some reason I get a .Net exception but others online have said it is possible.
  8. I had some issue with a bad stick of RAM in my computer that made the installer not work in unexpected ways and I got a similar error too.
  9. Wonderful suggestion. Most LAVA members that are older than some date have a wiki account and are welcome to update it.
  10. Maybe it has something to do with the fact that we have a more graphical mindset and don't care as much as long as we can convey a thought. Maybe because we are primarily engineers? Or this is a wiki with a relatively small support base? In any case thank you for your wiki contributions.
  11. All very good points and good concerns. Personally I would capitalize Boolean, but I may forget occasionally. I would also prefer subVI as I've gotten used to the NI standard. I can see the confusion with LabVIEW and G, and often I go back to what the community at large uses. If I say "My programming language of choice is G" some may confuse this with GCode, or something else. If I say LabVIEW I think that conveys what I mean to the general public more. For this reason I default to "LabVIEW" but at times will say G. Public opinion may change, and that may mean updating the wiki. And if there are specifics I'd prefer separate pages for 20xx and NXG, but whatever. One thing you might not be aware of is that there is a place for page specific discussions on the Wiki Talk Page. You could make an edit, but leave a comment asking for direction or leave it open to preference. That being said I think the opinion of most moderators on the Wiki is more that getting something which is non-perfect, is better than having nothing. I'd encourage others to make pages and fill in what they can, even if they are unsure of how to handle some of these differences. Things can always be cleaned up and refined later.
  12. Here is an answer by NI about why DIadem and Excel add-in do weird things with spaces. https://forums.ni.com/t5/DIAdem/Spaces-In-Property-Names/td-p/2831180 Basically its due to how it is indexed and put into a database. The standard LabVIEW TDMS API does allow writing and reading properties with spaces in them.
  13. Does the Get Properties return an error? If so what is the error? Show your VI that does the reading and writing. Oh and what is the property names there are a few that NI reserves.
  14. Not really. I mean it might be possible but an easier way to handle this would be to setup your VI to run on open, and then just ask your users to double click on the VI from a shortcut somewhere like the desktop. Then it will open that VI in LabVIEW (because that's what happens when you double click a VI file) and on open it will start running it. You can even configure the VI to quit LabVIEW when the VI stops running or the user closes the window. Then they wouldn't even know it is running in the IDE. This does however go against some standard programming practices and the better answer would involve still turning the code into an application, and figuring out what features you are trying to use that isn't available in the run-time engine. And try to code around them.
  15. Sorry no idea, I didn't even know this was possible. I'd contact NI support if you don't get any other suggestions.
  16. The linked article specifically states that it is for Windows and has you go through the process of creating drivers and installing them in Windows so that process isn't possible on RT. Also NI sells PCI and USB based FPGA's that can be programmed with LabVIEW, but I assume you went with a custom chip for a reason.
  17. Pulling the VIs out of an EXE isn't the hard part. In relatively recent versions of LabVIEW you can pull out VIs from an EXE. I think the last version I did this on was 2015. But the VIs are a binary blob with no block diagram, generally no front panel, but can be called as a subVI in the IDE. And with the forward compatible run-time engine that means any LabVIEW 2017 EXE can have its VIs pulled out and ran in 2017 or newer. I haven't tested this but I think it should work. But as others have said, getting the source code out of an EXE is considered impossible.
  18. I don't think making an XControl transparent is difficult. NI recommends setting the Facade VI to be "Window Runs Transparent". Then you can color the 2D picture control to be transparent. If the user chooses a background color other than transparent, then set the background color of the front panel, and set the Facade to not run transparent. If that doesn't work you should be able to draw a rectangle behind the chart the color the user wants. In any case congratulations, it looks like you put a lot of work into this, and I hope the market finds this valuable. I've never tried to sell any LabVIEW toolkits but I get the impression it is a difficult market.
  19. Wow yeah whole crap congratulations. Everything appears to be native G. It always feels like cheating when I see stuff like this that just is some .Net wrapper under the hood but this is an XControl which I would guess is a 2D picture control. I also like that you can see the settings update as you change them. That being said there are a few things I wish worked better. XControl resizing is one that would be nice so things like Fit to Pane worked. That Circular Chart Designer dialog can't be resized and it is actually too tall for my main monitor. Even the Circular Chart Example VI is too large and I had to change the settings to allow to make it fit on my monitor. Background color allowing for transparent would be nice but in most cases can be colored the same as the pane and you won't notice. I also don't see any XControl Properties or Methods to change the UI programatically. One easier solution for this would just be to allow to load premade CCS files with an invoke node. Then if you want to switch to other settings like changing the description, color, style, etc. Just load one made earlier. That can help you avoid having to make so many properties and methods. I really only played around with it for a few minutes but whole crap is there a lot of settings. I'd often try to do something to change one part of the chart and go down a rabbit hole of playing with every control to just see what it would do and how it would change it. The help is helpful but there just was things I had a hard time trying to figure out how to adjust.
  20. Okay for the heck of it here is my interpretation. I read that as OP trying to remove the last few characters from each string in an array. (also I read "few" as 3). Also snippets might not be working so attached is a VI in 2018. Remove Strings Test.vi
  21. Yeah these controllers are quite limited on space. I have a 9132 running wes7 and I was able to install LabVIEW 2018 SP1 development, XNet, DAQmx, and VISA support. After that the drive has very little space left, like 1GB. If possible a better option is like what JKSH said and to create an EXE and an installer, then just install that on the device instead of the full IDE. However debugging things wrong with your application is harder when you don't have a VI to just open and debug. So either option should be possible for you. If you are generating large logs you can put in an SD card, or a USB drive and log to that. It is also a full featured OS so logging to a network is also pretty simple.
  22. There doesn't appear to be a native way to do this, but if you write a VIM for this then you should be able to reuse that on any map type.
  23. LAVA has been known to strip out that meta data in the past. I remember one instance where it was seen when the image wouldn't fully fit on the post and it would do some scaling on the server side. I'll ping Michael but until then I'd recommend attaching the VI.
  24. I'm not a HID device expert (Rolfk maybe?), but there seems to be several DLL wrappers to talk to HID devices, but the best solution is to use NI-VISA and talk to it over USB Raw. For this you'll need to make your own INF driver using the NI-VISA Driver Wizard (should be installed with NI-VISA). Then install that driver for your device instead of the one from Microsoft (Device Manager). For this in Windows 8 and newer you'll need to disable driver verification. Then the device shows up in MAX, and the Help >> Find Examples and searching VISA Raw will show some examples. http://www.ni.com/tutorial/4478/en/ https://forums.ni.com/t5/LabVIEW/Nugget-1-of-n-GEtting-started-with-USB-communication-via-VISA/td-p/743518 https://forums.ni.com/t5/LabVIEW/Nugget-2-of-n-USB-Control-transfers-using-VISA/td-p/757011 If you can't or won't use VISA then there are lots of other DLL wrappers but I haven't found one that works as well as VISA with custom driver. http://ahidlib.com/pages/programming_labview.php?lang=en (license needed for full?) https://forums.ni.com/t5/Example-Programs/Windows-API-HID-Functions-Enumeration/ta-p/3513868 https://forums.ni.com/t5/LabVIEW/Confusion-between-HID-and-VISA-communication/m-p/1741390#M610130 https://forums.ni.com/t5/LabVIEW/Need-Example-Code-to-Interface-with-a-USB-HID-compliant-Device/m-p/2763516#M814451 https://forums.ni.com/t5/LabVIEW/How-to-configure-the-call-library-function-using-a-dll-for-HID/m-p/2757194#M813218 https://www-user.tu-chemnitz.de/~heha/mb-iwp/Durchflussmesser/
  25. It is open source. It is licensed under BSD, which in layman's terms means you can use it for personal or commercial use, and various attributes must remain in the source, and you can't sue the author (I am not a lawyer). I think the installed location is <user.lib>\_LAVA\VariantProbe
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.