Thread: Java vs Labview
View Single Post
  #35   Spotlight this post!  
Unread 09-05-2016, 16:22
AlexanderTheOK AlexanderTheOK is offline
Guy
no team
 
Join Date: Jan 2014
Rookie Year: 2012
Location: Los Angeles
Posts: 146
AlexanderTheOK is just really niceAlexanderTheOK is just really niceAlexanderTheOK is just really niceAlexanderTheOK is just really nice
Re: Java vs Labview

I've already been a part of two switchovers from labview to Java, and both times the team has gained quite a bit.

I could rant about all of the benefits we have received out of it, but many have already been mentioned in this thread.

One thing that hasn't been however, is that you can use both... at the same time. I give credit where it's due: Labview is phenomenal for viewing things. I've found that the graphing on the dashboard has in particular allowed much faster PID tuning.

Thankfully the WPILibraries give us a way to send data between robot code and Labview dashboards. This means you can have Java code running on the robot, and tune PID, and even do vision processing on the dashboard. Best of both worlds.

Last edited by AlexanderTheOK : 09-05-2016 at 16:23. Reason: grammar
Reply With Quote