What’s a detailed procedure for doing the above, if possible.
My understanding is you can’t.
Hmm, I swear I saw a post saying you could communicate with one http://www.chiefdelphi.com/forums/showpost.php?p=1412497&postcount=2
Its seems to support the old protocol (via a switch on the setup tab), but when we tried to use it on our old robot, it would not connect. Its seems kind of wierd to include that option but not have it work.
That option on the DS was repurposed towards the end of beta testing and it no longer is used to connect to pre-2015 cRIO images using the '09-'14 communications protocol.
It now is used only to connect to the older FMS Lite which is only necessary if you will be using FMS Lite at home or will be attending a pre-ship scrimmage where FMS Lite is used instead of a regulation FMS.
FMS Protocol - This controls which version of the DS to FMS communication protocol to use. This control is only needed when connecting to a 2014 FMS such as at a Week Zero event, where it should be set to '14. This control will reset to '15 (the setting required for 2015 Competition Events) each time the DS is started.
First you need to use the cRIO imaging tool and program it with the v57 image for cRIO. This image only supports the 4-slot cRIO.
After imaging, you can use LabVIEW for FRC 2015 (LabVIEW 2014) to target the cRIO-FRC II. You can connect to it using the latest driver station since this new image supports the new network communication protocol.
Thanks Joe,
I was on the verge of pulling out my last few hairs trying to figure out why the 2015 DS wouldn’t connect to the last year’s robot.
Question: Once we re-image the cRIO will it no longer work with the old DS?
I’d hate to lose the ability to backtrack to the old DS if something goes wrong.
It should still work with the old DS.
Is there any solution for an 8-slot cRIO, or would it be best just to buy a new roboRIO (a difficult thing for our small team)?
When I try to have both LabVIEW 2013 and 2014 installed, the old drive station will run just fine, but I wanted to make a new project in LV 2013 (just for a base drivetrain and joysticks since we tore our old bot down to be a drive practice bot) and I got a yellow triangle next to the cRIO part and it said something along the lines of “The plugin is either not installed or not activated for your system. Please contact National Instruments.” Is this due to trying to run both? I ran the installer a second time in the same directory and there were no issues (it just flew through since there was nothing to do) and the NI License Manager doesn’t show any issues.
When using the cRIO imaging tool found here: C:\Program Files\National Instruments\LabVIEW 2014\project\CRIO Tool
I only see an option for v52, which our cRIO already has… How do I get v57?
Did you install the LabVIEW update? Are you a LabVIEW team?
No, we’re a Java team. I installed the National Instruments FRC 2015 Update Suite though.
Only LabVIEW has a v57 image. If you image the target as LabVIEW, you will see the option for v57, and you could then switch it back to Java.
However, this won’t help you at all since Java doesn’t support the cRIO this year. If you want to program in Java on the cRIO you have to use Net Beans and the libraries from last year.
Which means we’ll have to use the old Driver Station?
Correct.
Does anyone know where we can download the old driver station? We still want to use our old CRio for driver practice but we no longer have any of last year’s software. The NI link to last years update says “page not found”.
Bump for this
Thanks for the help guys!