View Single Post
  #2   Spotlight this post!  
Unread 22-01-2017, 21:57
bdaroz's Avatar
bdaroz bdaroz is offline
Programming Mentor
AKA: Brian Rozmierski
FRC #5881 (TVHS Dragons)
Team Role: Mentor
 
Join Date: Jan 2016
Rookie Year: 2016
Location: Albany, NY
Posts: 409
bdaroz has much to be proud ofbdaroz has much to be proud ofbdaroz has much to be proud ofbdaroz has much to be proud ofbdaroz has much to be proud ofbdaroz has much to be proud ofbdaroz has much to be proud ofbdaroz has much to be proud ofbdaroz has much to be proud of
Re: Java Connection Problems

We used Java last year. Sometimes we were very fast, sometimes slower.

There are a number of things that affect connection speed.

Generally things happen in this order:
1. Scores from the last match are finalized, and the FMS begins reconfiguring the network.
2. The configuration process took at least 90s to 2 minutes.
3. Radios connect to the field access point
4. Robot-Driver station connectivity can begin

In our case at the Tech Valley regional, the biggest delay was often in FMS configuration. Often we were on the field, and booted, before the score from the last match posted.

In some of our matches our delay was in robot boot times, especially the radio. Usually the RoboRio would boot, and run the code, before the radio was booted.

So, while it's true C++ code starts faster on the RoboRio (the Java JVM takes a bit to load before it can start the code), in most cases the slight delay (a few seconds at most) doesn't matter. I can't speak to LabView, but I suspect it's equally irrelevant.
Reply With Quote