Deploying Code Shortcut

[wireties]

Originally Posted by Mk.32

hm
is there another way to do this besides being connected to Port 1 on the Crio, like using the bridge or port 2?

All that is required is for the robot (the FTP server) to have a IP path to the FTP client. The physical path does not matter, only that a logical path exists. It can definitely go through the bridge but am not sure about cRio port #2. The FTP server on the robot might be listening on port 2 (it certainly is capable of it) but I've never tested this configuration.

HTH

[Mk.32]

Originally Posted by wireties

All that is required is for the robot (the FTP server) to have a IP path to the FTP client. The physical path does not matter, only that a logical path exists. It can definitely go through the bridge but am not sure about cRio port #2. The FTP server on the robot might be listening on port 2 (it certainly is capable of it) but I've never tested this configuration.

HTH

Recently I tried that however was unable to get it to work with the IP, 10.36.47.2 (our team number) however using Port 1 with the same IP works fine. And Suggestions on what ip? or is there some router config we need to do?

[Greg McKaskle]

The second IP port is normally configured to 192.168.0.xxx. It can be changed via Max, but I suspect that the imaging tool will put it back. I'm not sure if an ftp server is active on the port. I suspect it can be configured if needed.

Greg McKaskle

[wireties]

Originally Posted by Mk.32

Recently I tried that however was unable to get it to work with the IP, 10.36.47.2 (our team number) however using Port 1 with the same IP works fine. And Suggestions on what ip? or is there some router config we need to do?

You need to have the ftp client on the same subnet. Port 2 is on subnet 192.200.0.0 I think. Access the console on the robot and type 'ifconfig' or 'ifShow'. That will tell you the IP address of the robot on both port 1 and 2. So if the robot is 192.200.0.1, use 192.200.0.100 or the computer running the ftp client program.

HTH

[Mk.32]

ah that makes since, quick question how do you access the console on the robot?

[beth_hadley]

Thanks for posting - you were a great team to work with this weekend at the Ann Arbor regional. We will definitely look into using this or a similar protocol for deploying code. Good luck in your future endeavors! GO FIRST!

~Beth

[WizenedEE]

I don't really get it. Building the code takes longer than deploying does, and deploying is much more useful in terms of debugging.

Several other things:

I'd assume (or at least hope) that all teams know how to do this or something equivalent already, or else they wouldn't be able to compete.

There's no reason to hard-wire the C-RIO to do this, unless you want the downloading time of two or three seconds to be improved.

Doesn't the "run as startup" option in labview do the same thing?

Windows Explorer is also an ftp server... just go to the address bar and type in "ftp://10.xx.yy.2"

I never thought about making a batch file though -- that sounds like a great idea.

[johnmaguire2013]

Originally Posted by WizenedEE

I don't really get it. Building the code takes longer than deploying does, and deploying is much more useful in terms of debugging.

Several other things:

I'd assume (or at least hope) that all teams know how to do this or something equivalent already, or else they wouldn't be able to compete.

There's no reason to hard-wire the C-RIO to do this, unless you want the downloading time of two or three seconds to be improved.

Doesn't the "run as startup" option in labview do the same thing?

Windows Explorer is also an ftp server... just go to the address bar and type in "ftp://10.xx.yy.2"

I never thought about making a batch file though -- that sounds like a great idea.

> Windows Explorer is also an ftp client... just go to the address bar and type in "ftp://10.xx.yy.2"
FTFY.

Also, Windows Explorer lacks many of the features a client such as FileZilla offer.

[Zach O]

Our team has actually set up a sweet system for autonomous that concurs the task of not having to deploy code.

Our autonomous code actually parses an text file found on the robot that we transfer using FTP. This makes for a quick and easy way to change autonomous' and helps to avoid touching or changing code on the robot, that might affect our teleop code.

We determined we can change our autonomous code from one to another in 11 seconds.