Jump to content

emcware

Members
  • Posts

    6
  • Joined

  • Last visited

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    1992

Contact Methods

Recent Profile Visitors

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

emcware's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

2

Reputation

  1. I have been using Parallels on my Mac to develop LabVIEW (for Windows) code for years and have been very happy with it. I have been trying for some time to get this working with the M1 chip. I have an Apple M1 Mac mini and more recently, an M1 MacBook Pro. Installing Windows 11 ARM is straightforward. LabVIEW does install and I am able to partially open my projects but I have a lot of packages as dependancies and am not able to get VI Package Manager to work. But more significantly, every time I install NI-Max, it kills Windows and I am no longer able to boot. I recommend you keep ‘Snapshots’ of your Parallels VMs as you get thinks working. Hopefully you will have more success than me.
  2. Thanks everyone for the great suggestions. I can't wait to try these.
  3. Hello, I recently discovered a new function in LabVIEW 2019 called ‘Get Command Line Arguments.vi’. It allows an application build from LabVIEW to be launched and accept arguments from another application. The arguments come in the form of a string array. I was not aware of this but it is and has been possible for some time to do the same thing using the ‘Application:Command Line Arguments property node. I often call applications to perform specific tasks from my main program. It is reasonable to ask ‘why not simply embed the functionality’ directly into your main LabVIEW application?’ In my case, my main application is very large (1000s of sub-VI and yes, lots of OOP) and it take quite a bit of time to compile and build the application, which I distribute to a number of users. I find in some cases it is easier to develop a separate application to perform a specific task and I may have a number of revisions during development and/or maintenance. I often build applications from Python using pyinstaller and I call these from my LabVIEW application. However, with Python I can include a simple print statement to generate output and my main LabVIEW application is able to read these print statements. Is there a method to pass parameters back to the main LabVIEW application after the small executable has finished, equivalent to how I use print statements in python? Here is link to 'Get Command Line Arguments.vi' https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YHdICAW&l=en-US thanks,
  4. Hi Rolf, Thank you for responding. I was starting to think I am the only person that builds LabVIEW applications with a Mac. I don't think the root cause is a driver or graphics card because it happens on every Mac I have when I use LabVIEW 2016, 2017, 2018, 2019 and 2020. The problem with the yellow icons and the yellow graph don't happen with LabVIEW 2015 or earlier. The root cause seems to be the invoke node that takes a reference of a vi and gets it's image data. The 256 bit color palette array in the cluster bundle is being corrupted by the application builder. So (you can see in the source code) I bundled my own 256 color palette array and it solved the problem so that the plot is no longer yellow when I build an application.
  5. After living with this for 5 years, I have finally figured out the solution for the yellow plots. The root-cause of the yellow plots appears to be that the standard 256 color palette contained in a cluster coming out of an invoke node (FP.Get Image) become corrupted by the application builder on Mac OS X. The colors when running source code vs. when build into an application are very different. My workaround is to bundle the 256 colors directly in the source code. Of course, I am using 8-bit color. I would assume that if a higher bit-depth is needed, then a different set of reference colors would need to be bundled but I have not investigated that. I also suspect the yellow icons are similarly corrupted but I don't know how or if I could solve that. But at least now I can save my plots using LabVIEW 2020. I hope this helps someone else that has been frustrated with this. A screenshot of the work-around is below. I also have attached a screenshot showing the yellow icon.
  6. Hello, When I build an application with LabVIEW for Mac OS X (2016 through 2020), the icon is yellow and when I save a plot of data, the png is yellow as well. Running the source code is fine, the icons are normal (black text, white background) and my png plots of data are normal. Does anyone else see this behavior with the LabVIEW Application builder for Mac OS X? My only option is to continue to use LabVIEW 2015. Main.vi Some Plot.vi try_LV_2020_Save_Plot.aliases try_LV_2020_Save_Plot.lvlps try_LV_2020_Save_Plot.lvproj
×
×
  • Create New...

Important Information

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