Does anyone know if the next generation CRIO will be able to take the same code as the current CRIO or will there need to be substantial change to the code?
You will at the very least need to recompile using a new toolchain.
It will most likely use a different runtime version as well, so I’m guessing Labview updates will be needed
There will be some exciting new features, but the languages and libraries will offer lots of compatibility.
Greg McKaskle
that is good to know. I am wanting to build a nice test bed for the students this off season. I am wondering if it would be worth it to make one this year or just wait tell next year to make a nice one?
I worry when the programmers tell me “Lots of compatibility” :eek: :] I mean a lot.
In terms of a test bed: Realize that in 2015 the controller will have a different foot print. Digital car will be gone. PD board will be different. Pneumatic controller will be different.
Totally uniformed opinion on my part, but I am thinking the hardware will not be available until the 2015 kick off… You should not let that stop you from making a test bed today. You have a lot of development time between now & then,.
we actually have a test bed right now but it just is not put together very nice. I was to make it a little more portable. It sounds like we should just use are current one until next year then make a nice portable one with the new parts
From the comments:
Teams will be able to purchase spares in late 2014, all FRC teams will get a roboRIO in their kit of Parts.
Teams will be able to purchase spares in late 2014, all FRC teams will get a roboRIO in their kit of Parts.
Great. I hope that is really the case. Along with the other hardware & programing tools needed to make it all work. Maybe a good question for Frank’s Fridays.
We’re interested to see how teams will use/program the custom electronics port; endless possibilities! The USB-B port, if I’m interpreting it correctly, will also be SUPER quick if we could use that to deploy code.