![]() |
Re: cRIO 2015 : NI roboRIO
Quote:
|
Re: cRIO 2015 : NI roboRIO
The 2CAN is also integrated into the roboRIO
|
Re: cRIO 2015 : NI roboRIO
Quote:
A separtate CAN interface is included on the RoboRio. It is a 2pin signal connector and the roborio has a built in can terminating resistor. 2CAN is not on the Roborio. 2CAN is a standalone product of CTRE. Regards, Kevin |
Re: cRIO 2015 : NI roboRIO
Quote:
|
Re: cRIO 2015 : NI roboRIO
Quote:
|
Re: cRIO 2015 : NI roboRIO
Quote:
For Controller Area Networks (CAN) to work properly, both ends of the bus need to be terminated. This is because communication flows both ways on the CAN bus therefore both ends of the pair of signal wires (CAN_H and CAN_L) must be terminated. The RoboRio has an internal terminating resistor that can not be removed. This means the RoboRio should always be at one end of the CAN Interface. The PD Board, has a setable terminating resistor by way of a jumper, this means the PD Board can be used at the other end of the CAN interface if the jumper is in place. However, the PD Board does not have to be at the end of the bus, you can remove the jumper and put another device after the PD Board, just make sure to add a terminating resistor to that device. Hope this helps, Kevin |
Re: cRIO 2015 : NI roboRIO
My mistake. Still learning about the equipment.
|
Re: cRIO 2015 : NI roboRIO
Quote:
|
Re: cRIO 2015 : NI roboRIO
Does anyone know if the roborio is REQUIRED for the 2015 season, or will we have the option to continue using the cRIO for a year or two?
|
Re: cRIO 2015 : NI roboRIO
It will be required.
The cRIO's will still be compatible and can be used for practice robots. |
Re: cRIO 2015 : NI roboRIO
Quote:
|
Re: cRIO 2015 : NI roboRIO
That FIRST answer addresses the question of legality under the 2015 rules which of course cannot be commented on before January 3, 2015.
We don't know what will be REQUIRED by the 2015 rules until January 3 when the rules are released for the first time to everyone at once. There are no previews for individual teams via questions or otherwise. So while neither I nor anyone else KNOWS the 2015 rules, I deduce that FIRST giving everyone a new control system in the Kit-of-Parts means that we will all be using it. This is the 8th control system that FIRST has introduced. Every control system changeover in the past has completely replaced the previous system. I imagine this is because the old systems do not support the new capabilities and methods used for competition play. The systems only work together if the new system is degraded to operate under the limitations of the old system. We're a Beta team. One of our tests is that the new software still supports the old cRIO system. P.S. The Beta 2015 control system is actually being tested in some off-season events and it works fine alongside the old cRIO systems. However, setting up the communications means the mDNS system used by the new control system has to be disabled and the IP addresses hardcoded like the old system, and the new system has to be switched to use the old communication protocol. |
Re: cRIO 2015 : NI roboRIO
Has the programming software for 2015 been released to the public, or only the beta teams?
Is there any way to set up eclipse to program the old crio with java so that we can start getting familiar with the process? Would any beta teams be able to post a YouTube video showing off the java programming environment? |
Re: cRIO 2015 : NI roboRIO
Quote:
The software is with Beta teams only under an NDA, because we're verifying that everything works as expected and helping to refine the user documentation. We're creating bug reports and the FIRST/NI/CTRE groups are generating fixes. General teams will get the final software in the 2015 KOP along with the hardware it runs on. I'd check to see what Java Beta teams are closest to you. They will be doing workshops that you can attend and see the programming environment for yourself. |
| All times are GMT -5. The time now is 20:03. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi