Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Last week
  3. Not a lawyer but I suspect it's a bit of a good faith kind of thing similar to Visual Studio Community Edition or Visual Studio Code. I also imagine the licensing cost might be cheaper than the potential of getting caught and NI wanting to do something about it.
  4. It would also allow open source developers to maintain their projects after they have changed jobs. I'm glad to hear that NI is moving in this direction. How are they going to prevent companies from just using the community version though?
  5. Is this what you are trying to do? My Script.vi My Template.vi Setup Static VI Ref.vi
  6. NI offfers an electrical power toolkit : http://zone.ni.com/reference/en-XX/help/373375G-01/
  7. It depends what you try to do. As long as you don't try to access a particular zip or unzip sessions from multiple places in parallel, the zlib zip library has always been safe for reentrant execution as it does not contain global state that spans across sessions. The underlaying zlib library (pure compression/decompression algorithms) itself is even less of a problem as it does not have the complex archive maintenance that is needed for a ZIP archive but only works on immediate memory streams. If you try to open a zip (or unzip) session somewhere and then branch this to two different locations and try to write streams to them from both locations you are going to crash sooner or later. Each session stores state that is used across method invocations and even if I would protect the individual function calls with a per session mutex (or make the functions all execute in the UI thread) you would still potentially corrupt the zip archive stream or in the case of unzip operation retrieve a different stream than what you think you do in a particular location. As long as you don't access a specific session (zip or unzip refnum) from multiple places in parallel you were always fine though and that will remain like this in the future. This pretty much is the same as trying to read or write to a specific file from multiple places (through he same refnum or a separately opened). You can do that but expecting the read and writes to work properly and have a proper data content in the file afterwards will be pretty much impossible. There is however no problem in writing (and/or reading) in parallel to two (or more) different files on disk. So setting the VIs to shared clone should work (all the state is stored in the session behind the refnum) but I'm not going to do that for now.
  8. It appears that the shared libraries are fully threadsafe, given the calls are all set to run in any thread, and I don't think the zlib library is multithreaded. Would there be any issues with setting the VIs to "Shared clone reentrant" to allow multiple simultaneous calls?
  9. 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.
  10. I probably can't test the VxWorks targets for now but can create at least the RT image to be installed for them. No guarantee that it can even load though without having tested it before myself.
  11. Vision doesn't require realtime at all. What are you really trying to do here?
  12. Great. I would be glad to test it. I mainly work on ARM-based Linux RT targets myself, and the occational old VxWorks cFP-target.
  13. It most definitely does with some caveats such as what hardware your computer may use. As to licensing, NI has so far mostly avoided the answer, but from the reaction so far it is clear that they don't feel compelled to create a standalone version of NI Linux for PCs. As far as licensing is concerned, the NI Linux part itself is a no brainer, it is Linux after all and you are always allowed to rebuild that for whatever hardware you want. The more interesting part is the NI-VISA, NI-this and NI-that software and of course the LabVIEW real-time engine that you also need to have installed on such a system to be useful for targeting with LabVIEW Realtime. This clearly is NI owned software and unless you have an explicitly spelled out license that allows you to use it on such a system, you are simply violating NI copyrights if you copy any of these files to a NI Linux operated platform of your own (aside that there are technical issues such as ABI compatibility and CPU architecture/family, for instance not every ARM CPU core is able to execute the LabVIEW ARM compiled modules, you need a Cortex A or compatible CPU core, this is the more powerful type compared to Cortex M or R which are meant for deeply embedded devices or reliable security platforms, or pre Cortex era cores).
  14. I did work on that mainly end of last year but found some time to resume testing recently. The code and VIs are more or less ready but I do need to do a bit more testing on Linux, Mac and the different real-time targets. Especially Mac and the real-time targets proof to be quite a hassle. Mac because I don't work often on it nowadays and the real-time targets because debugging shared libraries on them is always quite some hassle and each flavor is again different. I could however use some extra eyes for testing and I don't mean the shared library part itself but simply the general operation of it. I might be able to create a preliminary OGP package for installation through VIPM within a week or so if you want to test it. Let me know which platforms you would want to test it on and how and I will check what I can do.
  15. Is it possible to make Windows 10 realtime capable, so that i can use Vision?
  16. Thanks for the advice. Unfortunately it doesn't work with this dialog box. Maybe I have to resort to some mouse click simulation tool.
  17. I could imagine that RT Linux from a PXI system also works on a PC. This will certainly not be allowed by licensing law.
  18. You're right, running VIPM as admin works but I'd still like to know how to fix the problem rather than work around it.
  19. There is a brown/private property node that can suppress all dialogs. If you don't have access to this property node, you can find a sub VI that does this for you here.
  20. Its easiest to use VI Package manager. Just search for Modbus, select the package and install.
  21. Try running VIPM as an administrator. I have had similar issues happen when trying to install packages that were cached from the tools network by another user. Cached packages (and some other VIPM settings, I would assume) are stored in %ProgramData%, and Windows 10 seems to think that you shouldn't be able to access files in program data created by (in this case downloaded by) another user.
  22. Dear Poster, Thank you for your recommendation. How do I install Labview modbus API?
  23. I sent Michael an email. Not sure where that Contact Us goes but I don't see it.
  24. 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.
  25. In what format do you have these signals? Array? Waveform? Dynamic Data Type? If the latter two, there are some fairly straightforward ways to re-sample and interpolate in the Signal Processing -> Signal Operation palette or the Express -> Signal Manipulation palette (Align and resample plus append signals perhaps).
  26. Hi, I want to unit test methods in my classes using JKI's VI Tester. Some methods are private or protected, which means, the TestCase class can't access it. (Yeah, I know, testing private methods is controversial for some people, but I want to do it anyway 😛.) My approach is, to save the access scope of every vi in the class that I want to test. Then set all members to 'public' in the test setup and finally restore to the original setting in tear down. The problem is: Everytime the 'Set Source Scope' or 'Set Source Scope And Propagate' library method is called with a dynamic dispatch method, a warning pops up. This requires me to click a button, which I wanted to avoid in the first place by programmatically changing the access scope 😬. My question: Is this dialog suppressable or automatable somehow? At least 'Set Source Scope And Propagate' should not result in a popup. Its sole purpose is change the scope and propagate that change. (Generally, calling invoke nodes shouldn't popup anything, IMHO.) I could also set the access scope to 'community' and add the test classes as friends, but that seems like an ugly workaround... Edit: By the way: I'm using LV 2018 SP1, if that makes a difference.
  27. This means that RT Linux for Desktop PC is theoretically possible. Can I buy a Linzens from RT Linux for Desktop PC´s? And how long will Pharlab ETS be available?
  1. Load more activity
  • Create New...

Important Information

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