01-16-2017 03:29 PM
I have recently been trying to use a myRIO with my windows 10 PC for a university project. I have the student/home version of LabVIEW 2015, and the 2015 myRIO toolkit installed. In the devices and printers page, it comes up as "Generic USB-EEM Network Adapter" and in properties it says it is the NI myRIO. When I connect it to power and USB I am prompted with the menu shown in section 2 of this link (http://www.ni.com/product-documentation/14603/en/) but clicking on the Launch the getting started Wizard, it immediately prompts me with "No NI myRIOs were found". Any help??
01-17-2017 10:18 AM
Hi PGoodhand,
Since this thread hasn't been active in a while, I would recommend posting your message in a new thread so that you can get more views and exposure. This will help your question get answered faster.
Good luck!
03-31-2017 04:27 PM
I have the same problem
03-31-2017 04:36 PM
I found a solution, it is posted here:
http://forums.ni.com/t5/LabVIEW/No-myRIO-detected/m-p/3575025
If you have any more issues, I recommend finding a more recent thread or making a new one.
03-31-2017 05:07 PM
I did the steps in the link, but nothing work yet
04-02-2017 04:07 PM
OK, I'm going to try to walk you through this. I've got a Windows 10 PC at home with LabVIEW 2016 and LabVIEW Real-Time installed, but no myRIO software. So here are the steps I took (and am taking, since I haven't finished yet ...):
Bob Schor
04-02-2017 04:49 PM
OK, I'm back with IE as my browser for the Forums. When I opened LabVIEW and tried to Configure myRIO, I got a pop-up saying I needed to install Microsoft Silverlight, which I did, but still had the error. Oops, I forgot to set IE as my default browser, which I now have done. Let's see what happens:
Bob Schor
04-03-2017 11:50 AM
Sigh. I've just spent about two hours on the phone with an Applications Engineer from NI trying to demonstrate and fix this issue. NI appears to be "vaguely aware" that there is "some problems with myRIO and Windows 10", but it also seems to be the case that (a) many (all?) of the AEs run Windows 7, (b) few of them (at least those handling Support calls) work with myRIOs, (c) the internal NI documentation does not (yet) specifically address this issue (though, as I said, there is some vague awareness of it), and (d) my AE didn't know if a CAR (a Corrective Action Report) or a Workaround was available (but he'll try to find out).
We did try a few things. There is, apparently, a new version of the NI System Configuration Tool, 16.0.1, which fixes some issues that MAX has (but, so far, not this one). I did upgrade to that, but it didn't help. We were able, using IE and the Web-Based System Configuration Tool to establish Wireless Connection with myRIO, but it wasn't easy, it wasn't intuitive, and it wasn't logical. I'm going to try to reproduce the steps that seemed to work (if you try and it doesn't work for you, I probably left out a step, for which I apologize -- I'm going to try to give you the (il)logic that may lead you in the right direction to figure it out for yourself ...).
I'll follow up on my request to NI, and as I learn more, I'll add to this Post. I've impressed on my helpful AE that (a) the myRIO is a significant Product, particularly in the Academic Market, (b) the myRIO has been out for at least two years, (c) Windows 10 has been out for two years and is becoming the by-far-most-common OS installed on new PCs (it takes an effort to get a Windows 7 system), and (d) the latest LabVIEW 2016 is specifically Windows 10 compatible. So such a flaw in using a "significant" NI Product (the myRIO) with the latest version of LabVIEW (LabVIEW 2016) running on the OS for which it was designed (Windows 10), particularly eight months after Software Release, is a Very Serious Problem.
Stay tuned. As I learn things, I'll test them, and the moment there is Something That Works, I'll post it.
Bob Schor