Deploying Code Shortcut

[msulaimain]

Originally Posted by Cecil

or.. you can take the easy way. Download FileZilla and use the simple drag and drop method to move the files..

I have been using FileZilla for like forever. It is the way to go. It's basically a organized/program that is very similar to the way that is expressed above.

[wireties]

The download tool in Workbench uses FTP. All it does is automate the process for you. It should be no slower or faster than FileZilla or any other FTP client.

HTH

[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?

[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

[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.

[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?

[wireties]

Originally Posted by Mk.32

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

Get a copy of the GettingStartedWithC.pdf file from the WPI web site. It explains how to setup a debugging session with the robot. With the debugging session working, right click on the target server (in the remote systems dialog), choose "Target Tools' then 'Target Console'.

Plus I think you can telnet directly to the robot (debugging session or not) if you checked the 'Enable NetConsole' check box from the cRIO Imaging Tool applet. (not 100% sure about this, no robot to check it out on). You can telnet from any Windows command line, just issue the command 'telnet 10.12.96.2' (for our robot).

HTH

[Fletch1373]

Originally Posted by wireties

Get a copy of the GettingStartedWithC.pdf file from the WPI web site. It explains how to setup a debugging session with the robot. With the debugging session working, right click on the target server (in the remote systems dialog), choose "Target Tools' then 'Target Console'.

Plus I think you can telnet directly to the robot (debugging session or not) if you checked the 'Enable NetConsole' check box from the cRIO Imaging Tool applet. (not 100% sure about this, no robot to check it out on). You can telnet from any Windows command line, just issue the command 'telnet 10.12.96.2' (for our robot).

HTH

Just something to note: Windows 7 has telnet functionality disabled by default. To enable it, go into Control Panel, click the category "Programs", and click "Turn Windows Features on or off". A smaller window should open up with a series of options. Search down the list for "Telnet Client" and check the checkbox to the left of it then click "ok".