Lets talk about the long deploying time

[lucas.alvarez96]

Originally Posted by virtuald

This year's deploy scripts makes more ssh calls than it previous made, and if your mDNS resolving isn't particularly fast, it might be the cause. You can test this (ish) by opening a command prompt and doing a 'ping' of roborio-XXXX-frc.local, where XXXX is your team number, if it takes awhile for it to figure how to resolve that address, that could be the culprit.

Do you know if it's possible to automatically fall back to static IP?

[snekiam]

Originally Posted by lucas.alvarez96

Do you know if it's possible to automatically fall back to static IP?

You could add a static route to your hosts file

[Jaci]

GradleRIO has recently been updated to be 2017 compatible. Deploy times are anywhere from 5-15 seconds. For each deploy, there are only 3 ssh sessions (one for discovery, one for NI utils, one for user code), and libraries are only deployed if they have changed or have not been deployed before (e.g. wpilib, opencv, talonsrx, cscore, etc).

You can see the project here: https://github.com/Open-RIO/GradleRIO

[Hess1113]

I use LabVIEW and one simply edit to your code and you have to build it and Run as startup. This take about 3-5 minutes but one main issue is you have to sit next to your computer due to a couple of warning messages appearing.

[Rsave7]

Originally Posted by Hess1113

I use LabVIEW and one simply edit to your code and you have to build it and Run as startup. This take about 3-5 minutes but one main issue is you have to sit next to your computer due to a couple of warning messages appearing.

Yup.

Thats one of the infinite downsides to using labview. We really need to switch soon!!

[The Doctor]

If you really want to, you could submit an issue or pull request to the official WPIlib. Clearly, as Jaci points out, it could be faster with the right code.

https://github.com/wpilibsuite/allwpilib

[SamCarlberg]

Originally Posted by The Doctor

If you really want to, you could submit an issue or pull request to the official WPIlib. Clearly, as Jaci points out, it could be faster with the right code.

https://github.com/wpilibsuite/allwpilib

The deploy stuff is in the Eclipse plugins project

Java deploy tasks are here (build.properties and build.xml)

C++ here

[Greg McKaskle]

Specifically for LV users. I just tested the default code which includes vision acquisition and analysis.

A build was 25 seconds. A Run as Startup was 18. The first time I did these things on my new installation it was longer because it is building more things and caching them.

The interactive deploy (pressing the run button) was about 60 seconds when the target was running something else that needed to be canceled. It was 20 seconds on a target where the VIs were reloaded but the target had them cached. The interactive run was 3 seconds for small changes where the Main VI was not closed.

This was on an i5 several years old - $400 laptop.

Greg McKaskle

[c0d3rman]

One thing I found is that using a manual DNS server (8.8.8.8 & 8.8.4.4 for me) made the lookup take significantly longer (40 seconds with, 10 seconds without).