I have the exact same error.Re: myRIO - 1900 Unrecoverable error: Inconsistent IP settings

[jmcnaugh]

I have been attempting to use my myRIO device on my laptop while I am at home. I have been using this myRIO since Fall  2019 in Controls 1 on the my university's computer lab machines and have experienced no errors. I recently tried to install LabVIEW 2018 version on my personal computer, which I believed to have installed successfully. Yet, when I tried to connect the myRIO to my computer after I installed all of the software, I would launch the getting started wizard only for it to fail due to a “communication error”. The power light would be lit blue, but the status light would remain dim.

I then proceeded to try multiple different USB cables to see if the physical connection was the issue. This did not change the communication error response. I eventually looked at the National Instruments forums, played in the Measurement & Automation Explorer for hours trying different methods, but nothing seems to work. The myRIO would not connect to my laptop.

I eventually turned the myRIO into safe mode, and to no avail. The following message now comes up after I launch the getting started wizard and select my myRIO:

Unrecoverable error

An error occurred while attempting to check software installed on ...

Details:

The myRIO is in an unhandled state and cannot be recovered

Current State: Inconsistent IP Settings

I have made sure the IP address mode is set to static and the default IP address is set to 172.22.11.2 in the Measurements& Automation Explorer. I have tried to find any solutions to the inconsistent IP settings issue, and every posted solution seems to lead to dead end for me: either I can’t log into the myRIO, I’m unable to format the myRIO, etc.

If anyone has any ideas about how to solve this error, that would be greatly appreciated.

[Bob_Schor]

The software on your myRIO needs to be consistent with the software on your PC.  Here are a number of key questions:

• What version of LabVIEW are you running in your Computer Labs?  Is it 32-bit LabVIEW (probably) or 64-bit?
• I know you installed LabVIEW 2018 on your home PC.  Was it 32-bit LabVIEW or 64-bit?
• Is the myRIO "your" myRIO, or does it belong to the course?
• Did you install the myRIO Toolkit when you installed LabVIEW 2018?
• When you plug the myRIO into your PC's USB Port, does your PC make the "USB Connect" sound?  Does the "Welcome to myRIO" (that's not the name of the pop-up, but you probably know what I mean) box pop up?
• If you open MAX, can you see any Remote Systems with your myRIO connected?

As it happens, I h  ave some myRIOs at home.  I'm about to (yet again) reinstall LabVIEW on one of my PCs, and will be setting up my myRIO when I have LabVIEW 2019 reinstalled.  Reply with answers to the above questions.  If you are still having problems and not making progress, I might be able to help once I get my PC reconfigured ...

Bob Schor

[MrTumble]

I have an identical error.

I've been given a myRIO kit by my University to use at home as, although the university is open, all the labs are closed.

myRIO is connected by USB and on connection shows the serial number for the device in the myRIO USB monitor. It reports IP address 172.22.11.2, but I'm trying to connect by USB and that shouldn't make a difference.

On launching the Getting Started Wizard, the device is found and the correct serial number is shown. On clicking NEXT, the connection fails with the error details; 

The myRIO is in an unhandled state and cannot be recovered.

Current State: Inconsistent IP Settings

I have 64-bit Windows10, but have installed 32-bit LabView2019 with myRIO toolkit.

When the USB is plugged in, the computer makes the "USB Connect sound" and the "Welcome to myRIO"  pops up.

In MAX, the device appears under Remote Systems, but can't do anything to it.

The device status light is consistently off.

I have tried to hold the reset button, but that makes no difference. I was beginning to wonder if the device is bricked until I came across the original post above after four hours of getting nowhere.

Any suggestions gratefully received.

[Bob_Schor]

---

@MrTumble wrote:

I have an identical error.

I've been given a myRIO kit by my University to use at home as, although the university is open, all the labs are closed.

myRIO is connected by USB and on connection shows the serial number for the device in the myRIO USB monitor. It reports IP address 172.22.11.2, but I'm trying to connect by USB and that shouldn't make a difference.

The only way to communicate with the myRIO is through TCP/IP.  When you plug in using the USB cable, you are establishing a TCP/IP connection that uses 172.22.11.2 for the myRIO.

On launching the Getting Started Wizard, the device is found and the correct serial number is shown. On clicking NEXT, the connection fails with the error details; 

The myRIO is in an unhandled state and cannot be recovered.

Current State: Inconsistent IP Settings

I'll come back to this ...

I have 64-bit Windows10, but have installed 32-bit LabView2019 with myRIO toolkit.

My system is the same.  I assume you have the 2019 myRIO toolkit.  When LabVIEW starts, does it say "LabVIEW 2019 myRIO Toolkit"?  This really shouldn't matter for the Error you saw, but comes into play when you try to program the myRIO.

When the USB is plugged in, the computer makes the "USB Connect sound" and the "Welcome to myRIO"  pops up.

Good, mine is the same.

In MAX, the device appears under Remote Systems, but can't do anything to it.

What happens if you click on the myRIO icon under Remote Systems?  Can you see a display under "System Settings"?

The device status light is consistently off.

Right now, mine is also off.  About the only time it comes on is when I do a Software Reboot, or when I first plug in the Power.

I have tried to hold the reset button, but that makes no difference. I was beginning to wonder if the device is bricked until I came across the original post above after four hours of getting nowhere.

You want to be careful with that Reset Button.  It is possible to wipe the myRIO's firmware, and (trust me) it can be, shall we say, "difficult" to get it back.

Any suggestions gratefully received.

---

Whew.  Now I can type in regular colors!

Here's a screen shot from MAX, looking at the System Settings page of the myRIO connected to my PC (I was going to say "of my myRIO", but that sounds silly ...).

If you look closely, you'll notice a particularly advance Feature -- the ability to Reset the myRIO at a Future Date (hmm -- I think I got the month wrong ...).

Anyway, this shows the Ethernet connection (via the USB Cable), and the fact that it is also connected using the myRIO's 802.11 Wireless capability.  The Operating System is the current one for the myRIO, and should show up if you can see this display in MAX on your machine.

What I suspect is wrong can be cured by the "Update Firmware" button -- the myRIO may have the proper Operating System, but might not have  LabVIEW 2019 and its Drivers installed.  See the expanded Software tab in MAX, above.  If you are missing Software (i.e. nothing shows up under Software) or it is a different LabVIEW Version, you may need to "Update Firmware", which will take 10-20 minutes and will definitely involve your seeing the Status Light flash.

But Wait -- there's more ...

When the original myRIO USB Monitor started up, did you try "Configure myRIO"?  Did you get an annoying Pop-Up saying you needed to download Silverlight?  Did you do that?

In order to get this to work, you have to do a little "magic".  Silverlight is an obsolete Microsoft routine.  Chrome and Edge can't use it, but Internet Explorer can.  Once you have it installed, open IE and put the address 172.22.11.2 in it.  You should get the myRIO configuration page.

Warning -- do not set a Login, as removing it is extremely difficult (may require shipping the myRIO back to NI). 

With the myRIO Configuration Tool, you will be able to see many of the things that MAX shows you.  Some of the "features" you won't be able to open (see warning, above), but the sixth button, Software Management, should show you the currently installed software.

Take a look, check it out with your myRIO, and come back here if you have more questions.

Bob Schor

[MrTumble]

Thank you for the comprehensive run through of things to try. I really appreciate your time and detailed instructions.

First let me confirm I've got the right software - LabVIEW 2019 myRIO Toolkit

When I connect the myRio to my PC, the USB Monitor pops up and indicates the serial number and the IP address that you mentioned 172.22.11.2

On clicking the option to Launch the Getting Started Wizard, it takes me to a screen where it says "Found one myRio" and confirms the name and s/n of the device. On clicking NEXT, it then begins to try to connect, but this is the point at which it fails with the unrecoverable error.

So that's no help. Over to NI MAX instead.

Here the device appears under Remote Systems

But the big difference here is there is nothing like what you have visible on my system.

I'm on the System Settings tab, and it describes the Hostname, Model and Serial Number, but there's no ability to make any changes to the system her at all. 

I note that on the bottom, where yours says "CONNECTED - RUNNING" mine reports "Inconsistent IP Settings"

I checked under my network adapters, and I did find an additional connector with the IP address 172.2.1.1, so there ought to be a network connection over the USB as you say.

I tried a PING from the command prompt, but didn't get anything back on the address 172.22.11.2.

I checked Internet Explorer and it tells me I have Silverlight 5.

On trying to navigate to http://172.22.11.2/ it just reports "Cannot reach this page"

I think there might be that this myRIO is missing its software, as it simply won't let me in to do anything.

If you had any further suggestions I'd appreciate the advice.

Andy.

[Bob_Schor]

Thanks for your response.  Here are some things to try:

• On my system, with the USB cable plugged into the myRIO and my laptop, if I look at the Network Connections (from Settings, Network and Internet, Network Connections), it shows one called "Ethernet 6", with the name "National Instruments USBLAN Adapter #2".  Do you have something like this on your system?
• I'm not sure where to find the IP for this Adapter.  However, if I Ping one address below the IP for the myRIO (i.e. at 172.22.11.1), I get a "hit" if the myRIO is connected via USB, and a TimeOut if it is disconnected.  I'm pretty sure this is the IP of the Host port mentioned in the previous point.
• Working your findings in reverse, can you try to Ping 172.2.1.2, the address one higher than what might be your Host Adapter?  Do you see a connection?

If the answer to the third point is "Yes", then you've "found" your myRIO.  The only remaining problem is attaching to it.  Here are some things to try.  I'm going to do this with my system as I write this, to be sure I'm more-or-less giving you good information, at the minor, I hope, risk of screwing up my installation.  Here's what I'm doing:

1. Open MAX.  Open Remote Systems.  Find myRIO.  Click "Delete" and delete it.
2.  Close and reopen MAX.  Hover over Remote Systems.  MAX starts looking, and in about 5 seconds finds the myRIO, but only by finding its configured IP address (this is not something I expected!).  I'm going to continue, anyway.  I just turned the myRIO's WiFi (never mind how), and now it has disappeared from MAX, though it is still plugged in to USB.
3. Now, if you select Remote Systems, the "Create New" box should pop up and ask you to "Choose the type of item you want to add."  Chose "Remote Device (not on the local subnet)".
4. Since you might not know your device's IP, give its Host Name (which I hope you know -- it was probably originally "NI-myRIO-1900-<Serial Number>".
5. Well, that didn't work!  So I provided the IP 172.22.11.2.  It found it, showing me the Host Name (which I'd used in Step 4, unsuccessfully).  Curiously, it showed up with the name "172.22.11.2", but when I closed MAX and reopened it, it came up with the Host Name, as it had before I deleted the device.  Looking at is properties, it looks fine, except that the WiFi settings are missing.
6. Turned WiFi back on, everything looks good.

In your case, if Steps 4 and 5 don't work, try Step 5 with the IP 172.2.1.1, as mentioned above.

Post the results of your efforts here.

Bob Schor

[MrTumble]

Thank you for the continued suggestions.

I do have the National Instruments USBLAN Adapter, and it's IP4 address is set to: 172.2.11.1

Prom Command line I can PING 172.2.11.1, but got no response from 172.2.11.2.

Thinking this may be an issue with my Firewall or antivirus, I have turned off both. Even now there is no ping back from 172.2.11.1.

The myRIO appears in MAX, but the status continues to report as Inconsistent IP settings on the System Settings tab.

Under the Network Settings tab, a MAC address for the device appears, and it reports that the Static IP address of 172.22.11.2 is detected, but it also flags Inconsistent IP settings at the bottom of the window.

I have tried your suggestion of deleting the device in MAX, and the restarting MAX. When I restart MAX, the Remote Systems refreshes, and the device appears once again.

I have deleted it once again and tried re-adding through your Create New suggestion. This also fails by Host Name and IP address, reporting the error "Unable to Initialise connection to remote targets"

Additionally I did a System Restore on my PC to before I installed any NI software and reinstalled the 32-bit version of LabView 2019, myRIO Toolkit, Real-Time module, and MAX. along with all the recommended dependencies.

My lecturer and his assistant have both confirmed that theirs work, so it must be my fault. And I am fuming as I think the bottom line here is the device I've been given is the problem.

I think the only thing I can do now is return it to them and see if they can get it to work and confirm if the device itself is the problem, or if I'm missing some magic module to unlock the ability to write to the device.

Thank you for your suggestions. I do appreciate your time.

[Bob_Schor]

Based on the testing you've done, the various things that you've tried, and the care you have taken in documenting the problem, I am inclined to agree with you that there is (probably) something "gone wrong" with your actual myRIO, either in the hardware inside (so it drops a bit from the IP Address it has been assigned) or in its "BIOS".

I would go to your lecturer or his assistant and ask to borrow another myRIO (or, if you are working with a laptop, bring your laptop with you and do it while they watch).  [Note that I'm aware that Covid-19 rules might make "in person meets" difficult].  I think, based on your testing and responses, that plugging another myRIO into your PC would lead to instant success, meaning that your myRIO "is the problem", and (as they say in Pittsburgh) "needs fixed".

I'm sending you a Private Message through this Forum (click on your name in the upper right corner to go to your Profile, or search for Users on the search bar for yourself).

By the way, I don't understand the phrase "We will say NI again if you do not appease us" which appears to be part of your signature ...

Bob Schor

[Gabriel.mr · Accepted solution]

Hello, 

I also have the exact same error, however I was able to solve it.

First I realized, by means of the discussion above, that even though the connection is made by a USB wire, the PC recognize My Rio as an ethernet connector, by meabs of the adapter, so thank you guys.

To solve it, I just entered in my network configurations (in panel control), clicked with the right button and chosed "dignostic".

Diagnostic shows "DHCP not configured", so I clicked in "configure DHCP" and next, next, next ... until it shows me the message "solved".

I disconnected and connected my device and then it was recognized.

I hope to be useful! 

Thanks!! 

[Bob_Schor]

Thanks, mr gabriel, for adding this bit of information!  I would not have thought about checking the Ethernet connection, as mine are all working (even WiFi).  With luck, other myRIO users who are having similar connection difficulties will stumble on this Post and will find a plethora of things to try to fix the problem.

Bob Schor