Jump to content

Michael Aivaliotis

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Michael Aivaliotis

  1. Checkout @ElijahKerry's home automation project I also featured on my VI Shots livestream. It's a great demonstration of how to interface to NXG webVIs to get a nice interface into your hardware:
  2. It would be great to have a project menu item, goto parent interface:
  3. Well considering NI owns MCCDAQ... It could be a good thing or a bad thing.
  4. I'm investigating this hardware which might fit your requirement: https://www.mccdaq.com/DAQ-HAT.aspx
  5. I'll be putting out videos on testing all the hardware out there and compatibility with LVCE, over time. As I do, I'll be populating this page: https://labviewwiki.org/wiki/Linx_Toolkit_Hardware_Compatibility_List If others confirm compatibility, then please update that page.
  6. Ya, you're kinda in a gray area, between release dates. However, you can still download it and play with it. That's what VMs are for right?
  7. The LabVIEW community edition, community is tiny right now and it's up to all of us to build it up and help others. We are the pioneers so to speak. Don't forget we have the LabVIEW Wiki to use as a place to create compatibility tables and information. Creating a LabVIEW compatibility table should be the first thing on there, actually.
  8. I've tried the Pi4 it works no problem. No idea about the Pi Compute. However it has the same CPU and guts of a Pi3, which also works, so don't see any issue.
  9. That's a good question. I know it's not officially supported in the LINX documentation. I think it has to do with the type of ARM processor used on the zero vs the Pi 4 (for example). I just received a Pi zero, in my hands and will be trying that out soon. So I'll let you know if I find out anything. I remember seeing some info by someone in the community working on this and will post any info i find. Edit: LINX toolkit does not support Pi Zero. If you need a small form factor Pi then look for a device with the same or similar CPU.
  10. I thought I'd reply to this thread for posterity. LabVIEW Community Edition is now fully released starting today. Just to summarize: LabVIEW 2020 and NXG 5.0 are part of the release. Includes everything that comes with LabVIEW and NXG Professional Edition, Including App Builder (exe builds). No watermarks or feature restrictions LabVIEW NXG Community Edition includes the LabVIEW NXG Web Module Extending SystemLink Cloud evaluation to 6 months during 2020 LINX toolkit included with install. Supports: Arduino via se
  11. Hey LAVA friends. I'm going to be doing a live-stream on Youtube next Tuesday April 28, (10AM Pacific) to go over LabVIEW Community Edition. I'd love to see you guys there. It'll be interactive with chat for your questions, and I will be making an attempt to talk to a Raspberry Pi and Arduino. If you're curious about low-cost hardware or just want to find out what's new in the latest LabVIEW. Join me here: https://youtu.be/4HLVqYXpxIo. Edit: If any of you have done any projects with the supported hardware. Let me know and I can mention you or pull you into the discussion. - Thanks.
  12. If you want to try LabVIEW, you can download a free full version of LabVIEW for non-commercial use. It contains the LINX toolkit so you can use Arduino, RaspBerry Pi and Beagleboard: Download LabVIEW for Free
  13. Ok, now your idea has 2 votes... 😀 Ya, I decided to delete them all manually, and also the Update Service installers, which are probably temporary packaged files for the update service.
  14. I work with VMs and monitoring VM drive space is one issue I look at every now and then. The "C:\ProgramData\National Instruments" folder on one of my VMs is using 40GB. Does anyone know the proper way to clean up the NI crap? Using SpaceSniffer, it show the bulk of it is used by the Update Service and NI Package Manager. I'm sure it's just leftover installers that may be needed.
  15. Don't forget cRIO has RT so you can implement a lot of programming on the RT side for various scenarios. As a master of the LabVIEW language and NI hardware. I would prefer a platform that allows me to use the language I already know and love. I can provide a PC application that implements anything the customer desires. then I can configure a cRIO and implement ECAT, serial, Devicenet, DAQ, DIO or whatever they want using the same language and skills. If NI does not support the desired hardware i need to talk to, they have many other options like DLL calls and other ways of interfacing that I
  16. What I would like to see is a way to minimize the map or set constant by double-clicking on it. Like you can do with cluster constants. Hand editing Maps is such a small use-case but useful for some I guess. You usually work with these things programmatically. Thanks for the tool.
  17. i get it. Sometimes you gotta patch and move on. In parallel, though, I'd open a ticket with NI to get them to spend some resources on worrying about your problem too.
  18. I made a workaround. Instead of typdefing the entire Map, I just typedef the datatype inside the Map. This is probably the best way to do it anyway. Similar to typedefing an array element vs the entire array. Regardless, however, this is still a bug. Thanks for looking into it.
  19. Ok this is so random how I found this, but I was able to reproduce it. I'm hoping others on here can reproduce it as well. If this is a known issue then please link to the source for reference. I've attached code that reproduces it. But basically in order to reproduce it: Place a Map datatype in the private class data of the class. Make the Map datatype a typedef. lava.zip
  20. I'm noticing that when I probe LV class wires in LabVIEW 2019 SP1, it won't display any data on the probe. In fact it appears as if that part of the code never executed. I just can't figure out how to reproduce it. I'm wondering if anyone else has noticed this behavior. I can clearly see that I have multiple probes on one diagram and the probe attached to a class wired shows "Not Executed" in the probe watch window, even though "Retain Wire Values" is enabled. LabVIEW restart does not fix it. classprobe.mp4
  21. It was not developed in a bubble. There was already a close relationship between the VIPM team and NI. So they knew the requirements and the need. It's been over 5 years since the release of NIPM, so not much movement however... That might have been the first step, but hardly the long-term plan. In reality, I think the main reason for lack of development on NIPM is that people got shuffled around and new management came in and the original development plans for NIPM got put on a shelf. I can tell you that NI had the goal of full VIPM replacement. There is much churn internally at
  22. NI caused this problem themselves. NIPM should have provided all the features of VIPM from the start and then added GPM features. Lack of investment. Now they're playing catchup, but technology is moving on.
  23. Well, it seems to be more of a back, than a front. GitHub is becoming the package repo. GitHub is not making a front end manager. Agree this would be hard or impossible to achieve. Ok, ya this is a more attainable goal and a possible path forward. But GPM is not widely adopted and has limitations. NIPM will win by default, because it is made and fully supported by NI. However, it has a long way to go to support all the features we (as developers) need. It's a dumb installer and has no smarts related to the LabVIEW environment. For example, you cannot target LabVIEW by v
  24. I feel this is somehow related. GitHub supports packages as described here: https://help.github.com/en/github/managing-packages-with-github-packages Do you think this is something that we can utilize for LabVIEW package distribution?
  • Create New...

Important Information

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