|
|
|
![]() |
|
|||||||
|
||||||||
17-01-2015 21:28
BitTwiddlerKind of a sad ending to an old workhorse. They were cranky but they could really take a beating.
17-01-2015 21:38
Dief ChelphiIt's not like they are expensive or anything.

17-01-2015 21:46
nighterfighterMaybe you can use it to cook corndogs, and have it catch the crumbs!
17-01-2015 22:24
yash101
A bit more of a serious reply:
Our team has one (working) cRIO left on our last year's robot for demonstrations. It's nice to have the old cRIOs available, but it is also a total bummer that there is no support for them anymore. There isn't a driver station for it. There aren't programming tools with the right plugins either.
In short, they are quite useless. The dropdown on the DS which presumable allows you to change driver station versions(?) doesn't seem to co-op with the old cRIO either.
If NI and WPI didn't drop support for the old cRIO entirely, it may be of some good use, especially while prototyping. I doubt every team has five RoboRIO's to run those small prototypes. In our team, only the programming team has access to our RoboRIO's because they are under continuous use. After all, the new RoboRIO is quite pricey.
17-01-2015 22:44
Christopher149|
A bit more of a serious reply:
Our team has one (working) cRIO left on our last year's robot for demonstrations. It's nice to have the old cRIOs available, but it is also a total bummer that there is no support for them anymore. There isn't a driver station for it. There aren't programming tools with the right plugins either. In short, they are quite useless. The dropdown on the DS which presumable allows you to change driver station versions(?) doesn't seem to co-op with the old cRIO either. If NI and WPI didn't drop support for the old cRIO entirely, it may be of some good use, especially while prototyping. I doubt every team has five RoboRIO's to run those small prototypes. In our team, only the programming team has access to our RoboRIO's because they are under continuous use. After all, the new RoboRIO is quite pricey. |
17-01-2015 22:45
Gweiss96We use our old cRios to operate our practice bots.
17-01-2015 23:41
tStanoWe dug up some laptops had been gathering dust (we got in 2010 ish once they were too old for a sponsor) and put the 2014 driver station on them. They run XP, so the new driver station won't work.
This is a good end for old XP laptops that aren't worth updating. I'm sure someone you know has one of those lying around. It was by far the easiest installation process of the year. The laptop battery's a little finnicky, but it really does great.
Its sad that this is the only way to make 6 years of robot work. I really hope NI/WPI releases a better solution in the future, but until then, I still get to use the only OS that doesn't give me problems, which I really quite enjoy.
18-01-2015 01:34
yash101
|
Since we have two decent Classmates, I think we'll keep the older one "pure" for running our two cRIO bots. (The third cRIO we own might me more useful with the OP's use case; the useful ethernet port is damaged)
|
18-01-2015 02:11
mrnobleThose are some sweet looking mecanums there, I must say. Care to share anything about where those wheels came from?
18-01-2015 03:41
wasayanwer97|
Those are some sweet looking mecanums there, I must say. Care to share anything about where those wheels came from?
|
18-01-2015 05:34
mrnobleYup. The lighting made me think the rollers were gum-rubber colored.
18-01-2015 05:47
chmconkling|
Yup. The lighting made me think the rollers were gum-rubber colored.
|
18-01-2015 05:49
chmconklingBtw everyone. That cRio has been touchy on working the last few season, so she is no good.
18-01-2015 16:20
Alan Anderson
|
It's nice to have the old cRIOs available, but it is also a total bummer that there is no support for them anymore. There isn't a driver station for it. There aren't programming tools with the right plugins either.
In short, they are quite useless...If NI and WPI didn't drop support for the old cRIO entirely, it may be of some good use, especially while prototyping. |
19-01-2015 09:04
ratdude747When those came out jaws were dropping... you laugh at them now... but back then they were revolutionary compared to the old IFI controllers of yesteryear.
19-01-2015 10:24
calvinpanho|
Last year's NI LabVIEW for FRC still creates programs; it does not expire. The driver station still works. We're using one of the 8-slot cRIOs for a mecanum testbed.
The 4-slot cRIOs are currently supported with this year's LabVIEW. |
19-01-2015 13:42
tStano|
the Windriver(C++) license it's almost over, do you know if the new software (eclipse) is capable of programming cRio?
|
19-01-2015 14:03
chmconkling|
the Windriver(C++) license it's almost over, do you know if the new software (eclipse) is capable of programming cRio?
|
19-01-2015 14:31
calvinpanho|
Yes and WPI and FIRST Technical Resources says to install eclipse
|
19-01-2015 14:42
Joe Ross
|
Yes and WPI and FIRST Technical Resources says to install eclipse
|
19-01-2015 20:22
rockychat3We have been holding off on buying a second RoboRIO, but I had a few questions on ways we could save money. For context, we have two old 4-slot cRIOs no longer on working robots and we use Java. All of the students have only 2015 tools (Labview update and Eclipse) installed, but I have held back on upgrading software in case I am the only one who can still connect to a cRIO.
(1) Is it possible to have two versions of drivers station on the same PC?
(2) Is it possible to program the cRIO from Netbeans with the old plugins and the RoboRIO from Eclipse with the new plugins on the same PC?
(3) If we did buy a new RoboRIO, could we use a standard 20AMP slot on the old PDP to power it, saving us $200 on a new PDP (for internal/prototyping, not for competition)?
As a low to mid-budget team, I don't want to throw around that kind of money if we can get nearly the same benefit for less. Thanks
-andy / 4859
19-01-2015 20:28
orangemooreThis is actually not true.
|
I don't have acess to a 4-slot crio but the current 2015 driver station should work with 4-slot cRIOs. For the 2015 driver station to work, go to the 3rd tab on the left (the gear), and change the FMS protocol from '15 to 09' to '14 You should then be able to connect to the 4 slot cRIO. I hope this helps. |
19-01-2015 20:36
Ben Wolsieffer|
I don't have acess to a 4-slot crio but the current 2015 driver station should work with 4-slot cRIOs.
For the 2015 driver station to work, go to the 3rd tab on the left (the gear), and change the FMS protocol from '15 to 09' to '14 You should then be able to connect to the 4 slot cRIO. I hope this helps. |
19-01-2015 20:38
orangemoore|
Despite that misleading switch, you are actually unable to use the new DS with the to control cRIOs running old code. See this thread for more information.
I believe it is possible to install this year's labview code on to the cRIO and allow it to use the 2015 protocol, but this doesn't work for other languages. |
19-01-2015 21:33
tStano|
(1) Is it possible to have two versions of drivers station on the same PC?
|
|
(2) Is it possible to program the cRIO from Netbeans with the old plugins and the RoboRIO from Eclipse with the new plugins on the same PC?
|
|
(3) If we did buy a new RoboRIO, could we use a standard 20AMP slot on the old PDP to power it, saving us $200 on a new PDP (for internal/prototyping, not for competition)?
|
19-01-2015 22:51
ozrienThe new roboRIO will function without the CAN feature of the PDP. It just won't have current-sense features. You will still be able to deploy code, debug, move motors, etc....
The roboRIO doesn't need the PDP CAN to function, it just needs battery voltage to power. To your point it wouldn't be legal but the question was for internal/prototyping, so you should be fine.