View Single Post
  #4   Spotlight this post!  
Unread 15-01-2015, 00:58
wt200999's Avatar
wt200999 wt200999 is offline
Texas Instruments
AKA: Will Toth
FRC #3005 (Robochargers)
Team Role: Mentor
 
Join Date: Mar 2006
Rookie Year: 2004
Location: Dallas, Texas
Posts: 323
wt200999 has much to be proud ofwt200999 has much to be proud ofwt200999 has much to be proud ofwt200999 has much to be proud ofwt200999 has much to be proud ofwt200999 has much to be proud ofwt200999 has much to be proud ofwt200999 has much to be proud ofwt200999 has much to be proud of
Send a message via MSN to wt200999
Re: Joystick Explorer wont run

Quote:
Originally Posted by SuperBK View Post
I'm not sure if the 2013 and 2014 runtimes should be or even need to be mixed.
The runtime engine required depends on what version of LabVIEW the software was built on, and are not back compatible. So 2013 and 2014 can live side by side, but are only needed if you are running several applications with the different dependencies (i.e. 2014 will not cover software built on 2013). The driver station for this year was built on LabVIEW 2014 and should not be asking for 2013.

When you install the driver station for this year from the FRC Update Suite it should automatically install the necessary runtime. Is this how you installed it, and do you happen to also have last year's software installed somewhere that could maybe cause some issues? I've run into a problem like this before, where my LabVIEW software built on LabVIEW 2012 was calling a dll built on LabVIEW 2010 without me realizing it (I had both installed), so when it was installed on a different machine it was asking to install both runtimes.
__________________
Programming in LabVIEW? Try VI Snippets!

FIRST LEGO League 2004 - 2005
FRC Team 870 Student 2006 - 2009
FRC Team 3005 Mentor 2013 -