04-19-2018 01:46 AM
Actually, such an error is issued.
In general, even when trying to connect using Hardware setup wizzard in the Test step, there is a constant reboot, and, as a result, the equipment is not reset to the end. Actually, how to fix it? Or are these 2 unrelated problems? The project specifies exactly the IP that is displayed in the hardware installation.
04-20-2018 11:12 AM
Hi ademosh,
It looks like you're trying to interface with an sbRIO, right? What is the physical connection between the computer and the sbRIO? Can you right click on the sbRIO and click Connect?
If that doesn't work, there are a few other things you can try:
Let me know how those steps work for you!
Thanks,
04-24-2018 09:23 AM
Noone.
Connection via Ethernet cable. Entered into safe mode. Even in it after the discovery of the sbRIO and the transition to the next step is a reboot my PC. NI MAX doesn't showed blockages by the antivirus and its like. By the way, the system was displayed there with such "error". Perhaps the reason is in it (I apply the screen) in it?
As a result, the connection with the Real Time module(with the target in 2014 VIEW) has not been established.
I work with the switched off switch of motors and the included master.
Could there be a problem in my network card?
04-25-2018 04:25 PM
Hi ademosh,
To be clear, have you gone through the steps of trying to reset the IP address of your device? There could be a problem with the device itself, if you are unable to reset its IP settings.
I do not think there is a problem with your computer's network card. I have found that this 'inconsistent IP settings' can come up from having driver versions (and thus NI MAX version) older than 16.0. Are you able to upgrade your drivers to 16.0 or later? Specifically, I would look at CompactRIO 16.0. Let me know if that works for you!
Thanks,
04-26-2018 12:37 AM
It turns out to reload the IP address. But it does not reset to zero, but immediately takes on a new meaning.
I'll try to download the drivers, maybe this will fix the problem. Could there be any other reasons for inoperability, other than a breakdown of the system itself?