Imaging tool error
 

Hi we are trying to update our crio. We are getting this message error on the screenshot. Here some information for what we are using.
Yellow crossover cable
local wireless connection ip:10.39.88.6 sub:255.255.255.0
router ip 10.39.88.6
crio ip: 10.39.88.2

Re: Imaging tool error
 

The router IP is probably 10.39.88.1, because having the same IP as your laptop will prevent them from communicating.
You should check on that.

P.S.
You should click the box that says "Always run deployed code at startup"

Re: Imaging tool error
 

Ok we will try that and for the startup since we will be running lots of defferent programmes and changing them we will turn the startup on during competitions

Re: Imaging tool error
 

Then don't expect them to run if you don't start them.

Re: Imaging tool error
 

i didnt quite get the 10.39.88.1 where do i entre this ip

Re: Imaging tool error
 

The router is assigned an IP address of 10.te.am.1, so in your case it's 10.39.88.1
It is set for you by the FRC Bridge Config Utility, although it can be set by hand too.

The convention for the IP addresses we use are:

• 10.te.am.1 - router
• 10.te.am.2 - cRIO
• 10.te.am.4 - (used if an additional router is desired)
• 10.te.am.5 - Driver Station Ethernet
• 10.te.am.6 - programming laptop
• 10.te.am.9 - Driver Station wireless
• 10.te.am.11 - Axis camera

Re: Imaging tool error
 

Mark, I was under the impression that the .4 IP is supposed to be the default gateway for everything in the robot network. What do you use as the gateway IP?

Re: Imaging tool error
 

There is no gateway in the network, so you can leave that blank.
Supplying a fictitious IP address for a device that doesn't exist (e.g., .4) won't harm things, but it also won't matter.

When this FRC control system was first developed for the 2009 season we were issued a router used at the driver station plus a separate robot bridge. That router was assigned the address 10.te.am.4. However, that router wasn't a gateway either.

A gateway typically takes you to a WAN or Internet, not to someplace else on the same LAN.
A gateway is a transition point from one type of network to another.
Since none of our robot network traffic leaves our LAN, a gateway is never used or even looked for. (and by IP convention private IP addresses like 10.xx.yy.zz are not allowed through gateways anyway)
In general, the gateway field is only required when you have a more complex network where network traffic must hop across several different types of networks or get out through an Internet Service Provider.

Re: Imaging tool error
 

We tried to connect with this ip: 10.39.88.1 and we also tried to connect with the two subnet: 255.255.255.0 and 255.0.0.0, the same error message, as the screenshot show it, appears

Re: Imaging tool error
 

Try Disabling all other network interfaces on your laptop, e.g., wireless.
Leave only the Local Area Connection Enabled.
Use an Ethernet between the laptop and the router and another between the router and the cRIO.

Control Panel->Network and Sharing Center -> Change adaptor settings
right-click on the one's you don't need -> Disable

Start the Driver Station app and see what the ping tests show on the Diagnostics tab.
You should see green lights for Enet Link, Bridge, & Robot

Re: Imaging tool error
 

All the other network interface are disabled, but we still can`t update the cRIO with the imaging tool

Re: Imaging tool error
 

Can you post the results of typing "ipconfig /all" at a command prompt? That'll help us narrow down the potential problem points.

Re: Imaging tool error
 

We finally managed to update our crio with imaging tool when we turn on the pin for safe mode it work witout any problem and now has the v47image

Re: Imaging tool error
 

Im having this same issue and safe mode doesnt seem to be working

Re: Imaging tool error
 

try it on your classmate our toshiba had some hard time.

To put it simply our classmate is not available at the moment

Could it have anything to do with the laptops firewall permission settings?

Re: Imaging tool error
 

I don't think so because when you run the imaging tool there's a pop-up for the firewall.

Our problem ended up being the firewall