Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Stagg54 last won the day on September 28 2019

Stagg54 had the most liked content!

Community Reputation


About Stagg54

  • Rank
    Very Active

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2009
  • Since

Contact Methods

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Lookup the LabVIEW Python Node for calling Python from LabVIEW. That may not meet your needs on a CRIO. Under the linux-rt the VI runs in a chroot jail and so you have to do some tricks like using SSH to call python. Google and the NI forums should have some information on that. Another option is to pass data via TCP/IP. Also there is a DAQmx driver for Python, if you want to do everything in Python. The latest CRIOs (at least some of them) support DAQmx within LabVIEW. Not sure if that support extends to Python. Hope that helps.
  2. Project Euler is good. So is Advent of Code. You can also check out any of the code katas. There's a ton out there. Also there is a book called "Automate The Boring Stuff With Python." It is in Python, but the projects are very practical. They could almost all easily be translated into LabVIEW.
  3. Any list we put together is probably still going to have false positives. All we can really hope for is to flag things for further review. It could point out some problems. For instance, a math library that is using TCP/IP is probably an instant red flag. Also any list if we make it public, will just result in a cat and mouse game, because people who are determined will find ways around it. All we are really doing is just making it harder and picking off the low hanging fruit. That is all cyber security in general is doing. A determined and skilled attacker with sufficient resources
  4. So we had a discussion during Virtual Coffee about malicious packages and vetting. How do we verify that code is not malicious? What might flag something as malicious? We can use VI analyzer to check for certain things such as: PW protected VIs Removed BDs Call Library Node .NET nodes Network nodes (TCP, UDP, etc) File I/O nodes Shell commands Run on open Subvis with no icon or hidden under other objects What should we add to that list? Also we need to be careful with the fact that people can use #vian_ignore to
  5. unfortunately I had inherited a giant project. The main VI had a 17 frame deep stacked sequence structure. Frame 17 was the main logic but it needed 16 frames to initialize all the global variables in the correct order. It was written in LabVIEW 5 and upgraded to 6.1 with no SCC. It was my introduction to all things LabVIEW. It was a fun project.
  6. also why did they take the bite out of the upper left corner of the N? It looks weird. Maybe just to help differentiate from the garbage company?
  7. It could use a dose of any kinda color over that boring dull gray.
  8. You must have missed out on the joy of insane objects. https://labviewwiki.org/wiki/Insane_Objects
  9. For all the complaints I have about NXG, that decision I do agree with.
  10. One Word: Scripting Until we have scripting how do they expect anyone to be productive. It's like going back to the dark ages.
  11. We are still looking for more presentations. If you have something please submit it thanks.
  12. As a package creator I would like to be able to see how many people have downloaded my package.
  13. As a package consumer I would like to be able to subscribe to packages so that I get notified when a new version is available.
  • Create New...

Important Information

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