Need 2014 Driver Station Software

[Joe Ross]

Originally Posted by Greg McKaskle

As for Java dependencies. I'm not the right person to comment on that. I know that the cRIO will still need Squawk JVM and that the language changed enough that the libraries are not that compatible. I would guess that a new 2015 image on a cRIO 4 slot will still run fine with older Java tools, but I'd wait for a beta team or WPI student to confirm.

Only LabVIEW supports the v57 image. Java teams should continue using last year's development tools and image.

[jhersh]

Originally Posted by Joe Ross

Only LabVIEW supports the v57 image. Java teams should continue using last year's development tools and image.

The old Java libraries would have to be updated to support the new Network Communications API to read joysticks and tele-op / auto mode selections and the like (the same way LabVIEW for the cRIO was). Other than that it should work with the Net Beans tools.

[FrankJ]

Originally Posted by jhersh

The old Java libraries would have to be updated to support the new Network Communications API to read joysticks and tele-op / auto mode selections and the like (the same way LabVIEW for the cRIO was). Other than that it should work with the Net Beans tools.

I think our team is going to go with use the 2014 image on the Crios. I don't think I am even going to hint the programers that there are other options. (We keep them in a dark place with the mushrooms.)

[Qbot2640]

We program in Labview, and I really don't want to have both 2014 and 2015 driver station software on our DS laptop. What do I need to do?

Do I have to re-deploy my 2014 robot code from the 2015 software?
CAN I re-deploy 2014 from 2015, or would I have to re-write the program in 2015 Labview?
Will I need to re-image first?
Is there anything else?

To me this seems like the kind of ordinary functionality that tons of teams would need to have, to continue demonstrating their old robots this year...if it is so difficult, then why is there not a step by step instruction provided with the title "How to run your old robots from the new driver station software"

[Alan Anderson]

Originally Posted by Qbot2640

We program in Labview, and I really don't want to have both 2014 and 2015 driver station software on our DS laptop. What do I need to do?

If you're using a 4-slot cRIO, you can put the proper image on it, program it with this year's LabVIEW, and control it with this year's Driver Station.

The 2014 and 2015 Driver Station programs coexist without conflict (though I think the 2015 installer erases the contents of the folder, so you have to install the 2014 one last).

[RufflesRidge]

Originally Posted by Alan Anderson

The 2014 and 2015 Driver Station programs coexist without conflict (though I think the 2015 installer erases the contents of the folder, so you have to install the 2014 one last).

And the 2014 installer overwrites the 2015 dashboard so you should rename the 2015 dashboard first if you want to keep it.

[Qbot2640]

Originally Posted by Alan Anderson

If you're using a 4-slot cRIO, you can put the proper image on it, program it with this year's LabVIEW, and control it with this year's Driver Station.

We are using a 4 slot cRIO....
Can I open and deploy the program that we wrote in 2014 Labview with 2015 Labview, or do we need to re-write last year's program in the new software?

[Greg McKaskle]

You shouldn't need to rewrite all of your code, but you should look at the indices in Begin and update them to be zero based. There may be some other areas such as the compressor that you need to look at.

Work on a copy of the code, and you should find out within a few minutes whether you will have issues or not.

Greg McKaskle

[Qbot2640]

Originally Posted by Greg McKaskle

You shouldn't need to rewrite all of your code, but you should look at the indices in Begin and update them to be zero based. There may be some other areas such as the compressor that you need to look at.

Work on a copy of the code, and you should find out within a few minutes whether you will have issues or not.

Greg McKaskle

Thanks for the answer...but that was what I was hoping was not the case. We have only one programmer, who is learning the task as she goes and is doing great, but programming is definitely our weakness this year. If we have to go through our previous year's program to make changes that will end up being a project for after this season. I was really hoping to be able to demonstrate last year's robot throughout build season and competition season along side this year's practice bot.

[Greg McKaskle]

There is a solution that doesn't require any code change. Don't change any of the tools used for the robot and everything still works.

If you have already installed over the DS, zip up the 2015 DS directory, install 2014, rename it, and unzip the 2015 one.

Unless there is just a ton of code from 2014, it probably won't take but a few hours to upgrade to 2015, but this gives your team options.

Greg McKaskle