![]() Those hardware drivers depend on kernel drivers that must run in the Windows kernel. But it's at least a potential way forward and if somebody else wants to give it a shot, UTM may be an option.ĭo you managed to get this working? I'm not looking at LabView but 488.2 drivers, that are not available for windows arm, just x86, I was thinking in running QEMU/UTM to get x86 windows and use usb passthrough to get NI software in this ""VM"".Īny hardware driver is almost certain to not work. I'm not super optimistic about this, since ultimately it'll be running emulated, not under virtualization. This is also possible my error somewhere, but I haven't gone back to figure it out. However, when I rebooted after install, Windows gets angry about not being able to find the "Desktop" for the user, and kind of loses its mind. I did get it to boot and install Win10 x86. I suspect this is an error on my end, since it was the first thing I tried and I may have misunderstood some of the config. ![]() I can't get it to install Win11 x86, because it seems to insist there's an architecture mismatch. I'll write things up better when I have something real to show for it, but so far: I've been working to get Windows x86 to stand up on UTM (which I gather is really just a fancy frontend to QEMU). I took a crack at this when I got my M1 back in December and got nowhere, but now I have progress. ![]() I've gone through ~25 Windows 11 snapshots trying to get at least some basic add-ons installed like DAQ, but haven't had any luck I was able to install base LV with the math toolbox but nothing else. Hopefully you will have more success than me.ĭid you figure out how to get it installed? I'm currently experiencing the same problems. I recommend you keep ‘Snapshots’ of your Parallels VMs as you get thinks working. But more significantly, every time I install NI-Max, it kills Windows and I am no longer able to boot. 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. Installing Windows 11 ARM is straightforward. I have an Apple M1 Mac mini and more recently, an M1 MacBook Pro. I have been trying for some time to get this working with the M1 chip. My name is Kevin Ross and I am a System Engineer for Austin Consultants.I have been using Parallels on my Mac to develop LabVIEW (for Windows) code for years and have been very happy with it. Over the last few months I have been working on a project for our sister company Green Running, which is an energy monitoring and reporting company. The project I have been working on is to find a small, cheap platform for National Instruments (NI) LabVIEW. In this blog, I explore some options that will hopefully give you some insight into what is available at the moment. LabVIEW Requirementsįirst things first, understanding what the minimum requirements are to run NI LabVIEW. You can find out more about this on the National Instruments website. NI LabVIEW has been designed to run on the three main Operating Systems (OS), Windows, Mac OS X, and Linux. Depending on how you want to use LabVIEW will depend on the requirements. If you wish to use the development environment to develop code, then you require more from your OS compared to if you just want to install the run-time engine and run your built LabVIEW application. OK, so we know LabVIEW will work on the three big OS’s, now we need to pick one. Windows and Mac OS X have licensing costs associated with them, so that rules them out as we want to keep the cost down. We are then left with Linux which is an open source language (open source meaning free). ![]() Link: What Linux Distributions Do National Instruments Driver and Software Support? Linux Linux is a very diverse OS and has many different “flavours”. All of these flavours are based on the Linux Kernel which are the brains, in essence it is the OS. The “flavours” of Linux such as, Ubuntu, Debian, Fedora, Red Hat and OpenSUSE are known as distributions. These distributions have a different look and feel when they sit on top of the Kernel. As a user friendly interface that makes calls to the Linux Kernel, each distribution has its own unique implementation of calls to the Kernel. In order for us to run LabVIEW on a Linux system we require a specific Kernel version and also a specific distribution that NI support. NI sell a specific version of LabVIEW that is designed for Linux, unfortunately there is no cheap way of getting hold of LabVIEW, the Linux license cost just as much as a windows LabVIEW licence. If you want to go cheap then program using a text based language.
0 Comments
Leave a Reply. |