View Single Post
  #1   Spotlight this post!  
Unread 17-07-2014, 01:08
wireties's Avatar
wireties wireties is offline
Principal Engineer
AKA: Keith Buchanan
FRC #1296 (Full Metal Jackets)
Team Role: Mentor
 
Join Date: Jan 2006
Rookie Year: 2004
Location: Rockwall, TX
Posts: 1,170
wireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond repute
Send a message via AIM to wireties
feedback on MXP board idea

I know one can live without it and there are numerous clever workarounds but it has always bothered me that the I/O connections to the controllers did not use standard sorts of latching connectors (that use the same pins and sockets). The RoboRio looks to continue this design issue (in my humble opinion). So I was thinking about a quick design that would fit over the RoboRio. It would include, at a minimum, these features:

- Latching versions of the 10 DIO, 10 PWM, 4 AIO and 4 RLY connectors
- Latching connectors for the 16 MXP digital ports (PWM/DIO/I2C/SPI)
- Latching connectors for the 4 MXP analog ports
- Latching connector for the RSL port
- TTL to RS232 level conversion circuit
- 2 DB-9 serial connectors
- Clearance for LEDs, Ethernet, USB, Power, SPI and CAN ports
- Clearance for reset and user buttons
- Can attach to 2 mounting holes near the Ethernet/USB connectors

What else? Perhaps an Arduino circuit for custom LED string control, some diagnostic LEDs, a small display?

Comments, suggestions? I'll probably open source the PCB design. But if we sold it, what might you pay for such a board (assembled or kitted out)?

TIA
__________________
Fast, cheap or working - pick any two!