|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Deploying Code Shortcut
Don't you mean ftp?
|
|
#2
|
|||
|
|||
|
Re: Deploying Code Shortcut
I personally think it would be easier to just undeploy and deploy my code. It literally only takes 30 seconds extra and doesn't require me to memorize the whole command prompt sequence or the file location.
![]() However, that was a very interesting post! |
|
#3
|
||||
|
||||
|
Re: Deploying Code Shortcut
Yeah that should be FTP.
I haven't tried this method, but you should be able to create a batch (.bat) file to run all these commands for you. Just enter each command in order on a new line. Use the PAUSE command to check your progress if something goes wrong. |
|
#4
|
||||
|
||||
|
Re: Deploying Code Shortcut
or.. you can take the easy way. Download FileZilla and use the simple drag and drop method to move the files..
|
|
#5
|
|||
|
|||
|
Re: Deploying Code Shortcut
or, you could just use windriver. our code deploys in 15-20 seconds over wireless. makes getting access to the robot much easier,, and we have never had a corruption problem so far.
|
|
#6
|
|||
|
|||
|
Re: Deploying Code Shortcut
That's our experience too, and wired is even faster. We can deploy code in the pits in mere seconds after the compile succeeds. Compile and deploy speed is one of the biggest advantages we have seen from the switch from Labview to C++.
|
|
#7
|
|||
|
|||
|
Re: Deploying Code Shortcut
I agree with Arjun and 2611.Shoorter. Deploying code from Wind River/C++ seems much faster than deploying from LabView. I haven't worked with LabView personally, but I always joke with the programmer on our sister team when it takes forever for them to deploy code.
|
|
#8
|
||||
|
||||
|
Re: Deploying Code Shortcut
Quote:
http://fireftp.mozdev.org/ |
|
#9
|
|||||
|
|||||
|
Re: Deploying Code Shortcut
When deploying code from the classmate, our team had to wait nearly a minute and a half. Once we switched over to our competition laptop, it took nearly half as long. We saw much more of an improvement after switching computers, so I think the problem lies with the hardware the computer relies on.
|
|
#10
|
|||
|
|||
|
Re: Deploying Code Shortcut
sorry about the typos, I haven't slept much, and I do mean ftp. In the case of my team this works really well for us, but to each his (or her) own.
|
|
#11
|
|||
|
|||
|
Re: Deploying Code Shortcut
Well, as far as deploying code actually goes, the times to deploy vary based on programming language, and I have worked with all 3, in my experience in order quickest to slowest is
Java - seconds + reboot time C++ - seconds + reboot time Lab-View - Minutes + reboot time With all programming language, they do exactly what your doing, they Compile, connect to the FTP, copy the files, and reboot. And they optimize it as much as possible so making a batch file isn't going to speed it up any more. Also, theres a little more to it than JUST uploading to the FTP, but if there were an effectively faster way of doing it, they would have done it. |
|
#12
|
||||
|
||||
|
Re: Deploying Code Shortcut
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.
|
|
#13
|
||||
|
||||
|
Re: Deploying Code Shortcut
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 |
|
#14
|
||||
|
||||
|
Re: Deploying Code Shortcut
hm
is there another way to do this besides being connected to Port 1 on the Crio, like using the bridge or port 2? |
|
#15
|
||||
|
||||
|
Re: Deploying Code Shortcut
Quote:
HTH |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|