Chief Delphi - cRIO connection issue-can't deploy code

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)

- - cRIO connection issue-can't deploy code (http://www.chiefdelphi.com/forums/showthread.php?t=111439)

Re: cRIO connection issue-can't deploy code

Quote:

Originally Posted by integr8 (Post 1217239)

Ethernet adapter Ethernet:

Connection-specific DNS Suffix: (blank)
Description: Realtek PCIe GBE Family Controller
Physical Address: 08-2E-5F-7B-6B-38
DHCP Enabled: No
Autoconfiguration Enabled: Yes
Link-local Ipv6 Address: fe80::dc16:faef:92f9:7b3d%12(Preferred)
IPv4 Address: 10.13.7.5 (Preferred)
Subnet Mask: 255.255.255.0
Default Gateway: 10.13.7.4
DHCPv6 IAID: 25219439
DHCPv6 Client DUID: 00-01-00-01-18-4a-43-38-08-2E-5F-7B-6B-38
Dns Server:
fec0:0:0:fff::1%1
fec0:0:0:fff::2%1
fec0:0:0:fff::3%1
NetBIOS over Tcpip: Enabled

Check the items I bolded. If you disabled IPv6 why is it still showing up in ipconfig /all?

You can try the troubleshooting information in this document.

Try setting your network config back to default and startover, following the instructions in the above document. You may have inadvertently changed something.

Quote:

Troubleshooting cRIO Imaging

If the cRIO Imaging Tool is unable to locate the cRIO, or a Timout error message is displayed during cRIO Imaging, the issue is likely with the network configuration. One or more of the following steps may be necessary in order to image your cRIO:

Disable all other Network Adapters on the computer. Open the Network Connections window from the Control Panel (see Network Adapter Properties step above), then for each adapter other than the Local Area Connection you are using to image the cRIO, right-click on the adapter and select Disable.
Try using a network switch between the cRIO and computer: Some computers have issues reconnecting to the cRIO after the cRIO reboots as part of the imaging process. Placing a switch between the two devices, such as the D-Link DAP-1522 provided in the Kit of Parts typically mitigates this problem.
Disable Windows Firewall: Windows Firewall may be blocking the cRIO Imaging Tool, preventing it from detecting the cRIO. If possible, temporarily disable the Firewall by going to Start > Control Panel > System and Security > Windows Firewall > Turn Windows Firewall on or off. If the Firewall cannot be disabled, make sure that the FRC cRIO Imaging Tool is allowed through by selecting Allow a program or feature through Windows Firewall from the Windows Firewall screen, then click Change Settings and make sure that FRC CRIO Imaging Tool is listed and has a checkmark for all three network locations. If it is not listed you will have to add it using the Allow another program... button and browsing to the imaging tool location C:\Program Files\National Instruments\LabVIEW 2012\project\CRIO Tool
Try a different PC: If none of the above steps work, try using a different computer to image the cRIO.

Re: cRIO connection issue-can't deploy code

We were able to successfully connect to and reimage the cRIO but now when we deploy the code we get a new error. It says:

"Access denied: This target is running a version of LabVIEW Real-Time that is different than the Real-Time Module software on the host computer. You can verify the version and reinstall the Real-Time software using Measurement & Automation Explorer."

Any advice is appreciated.

Re: cRIO connection issue-can't deploy code

First, reopen your imaging tool and verify that it says that the cRIO's current image is 47.

Next, verify that you've installed the labview updates from usfirst.org (Including the bridge configurator, I believe there are 4 total).

Re: cRIO connection issue-can't deploy code

Make sure you selected LabView when imaging, not Java or C++.

Re: cRIO connection issue-can't deploy code

We had this issue on Team 3389 last weekend and it drove me nuts as the programming mentor.

We finally spent a few hours on the phone with NI on Monday and discovered there is a bug in the Smart Dashboard code currently. There are two workarounds, one of which I forget.

The work-around we are using is to shutdown the Dashboard app until AFTER you've deployed your code (via deploy or running from Robot Main.vi)

Since starting to use this work-around we've had no issues. I'm surprised this hasn't made it to an update or official blog post.

Hope this helps,
James Culp
Programming Mentor
Team 3389 RoboSpectrum
http://www.team3389.info/