[DFTF] We eat what we CAN, and what we can't, we CAN...

[Mike Copioli]

Originally Posted by Hugh Meyer

Joe,

2CAN:
Last year the 2CAN and serial port were the two options. NI must support them. This year may be different.

The 2CAN plugin is supported by Cross the Road Electronics, not NI. It is legal for any team to create their own Ethernet to CAN gateway. The API is the same for both serial and Ethernet the only difference is the plugin.

Originally Posted by Hugh Meyer

2CAN Web Page:
The 2CAN will show much data if you hit it with a web browser. We could not do that and control the Jaguars from the CRIO at the same time. It is one or the other.

This should not be the case , we update 10 Jags at a 5mS rate and view the web dash without issue. The Web dash transaction should be the only thing being delayed, if at all, since they have a lower priority than the Set transactions.

Originally Posted by Hugh Meyer

Also, the configuration to get to connect the web interface to the 2CAN is not a legal mode, since you must have a path directly from the browser to the 2CAN. Normally the 2CAN must be connected to the CRIO for normal robot operation. This year may be different, since the 2CAN will be connected to the switch.

I see no rule that states this configuration illegal as long as the "commands" are not altered.

<R59> If CAN-bus communications are used, the CAN-bus must be connected to the cRIO-FRC
through either the Ethernet network connected to Port 1, Port 2, or the DB-9 RS-232 port
connection.
A. Ethernet-to-CAN bridges or RS-232-to-CAN bridges (including the Jaguars, MDLBDC24)
may be used to connect the CAN-bus to the cRIO-FRC.
B. Additional switches, sensor modules, custom circuits, third-party modules, etc. may also be
placed on the CAN-bus.
C. No device that interferes with, alters, or blocks communications between the cRIO-FRC and
the Jaguars will be permitted (tunneling packets for the purposes of passing them through
an Ethernet-to-CAN bridge is acceptable as the commands are not altered).