Once upon a time in our early history we had a working electric wheel chair in the space. This is some info from when we were trying to hack the control system on it. It developed some minor wiring issues which needed to be repaired so it could run again so it laid dormant the last few years of its life. It left our group when we moved out of our building at S. Rogers Street at the end of 2017.
Our electric wheel chair appears to use a derivative of the CAN bus for it's control network, we need some tools for working on this. There are some different ways to go, however on something like this we need known-good tools to start out with. If anyone wants to go in on a CANUSB cable we can begin hacking on this wheel chair controller. From what I've read this cable essentially gives you a serial interface to the CAN bus, use minicom/hyperterminal/etc. to read data off the bus and to inject commands into it. In theory we could watch the joystick issue commands to the controller and then write some arduino code to mimic the joystick.
CANUSB interface cable money
We need $150 to buy this, who wants to go in?
- Nathan - $40
- Jay - $40
- Jenett - $40
- CAN-NI-Bus: 
- CANUSB cable: 
- USA reseller $139: 
- ATMega162 with CAN interface / development platform: 
USA reseller appears to be imagecraft again, appears to be the RS232 device on the above page.
- Sparkfun CAN-BUS Shield ($45): 
- Seeed Studio CAN-BUS Shield ($23): 
- Excellent Documentation: 
- Microchip CAN bus anal. tool ($130): 
- SJA1000 IC used by the CANDIP-M162 board:
- DX key - parallel port DXBUS interface sold by Dynamic Controls (no longer sold):
Documents relating to our wheel chair, controller, and the DX Bus protocol
- Ours is the Alante 202: 
- Maker of the controller: 
- Wheel chair parts list, including Dynamic controller parts: 
- Document including pinouts (see p. 36) from Invacare 
Dolphin after-market joystick made for our wheelchair series
Raptor PS servicemanual_Vedlegg 1_dolphin-installation-manual.pdf 
- page 22:
The DX Hand Held Programmer (HHP) is the normal programming tool used by dealers, allowing easy adjustment of all commonly adjusted Drive Program parameters.
Warning : The DX HHP is for use only by wheelchair manufacturers, their authorised dealers and support personnel. It is not intended for use by the wheelchair user.
The DX HHP Manual should be read and understood before attempting to use it.
Fault codes: 
Other peoples tribulations on this same subject
Engineering project using DXBUS protocol, they used a DX hardware interface to control the chair via a laptop: 
A Smart Electric Wheelchair Using UPnP They used some parallel port interface to insert their laptop into the system to issue commands: 
Others asking about reversing the DX Bus protocol: 
Interfacing to DXBUS with a PIC
- PIC dxbus hacking (dosman's note: this search no longer finds schematics for the controller, included for completeness only):
 ... Google this --- Dynamic DX Joystick Controller schematic -- and you will get a rather larger [93 page PDF file] that explains the whole specification. This is suppose to be THE 1101 joystick module. ...
- DXBUS info (SLM integration):
- from the manual:
... Programmable parameters relating to the SLM are contained in the DX Remote (UCM Remote) and the SLM programs. These programs can be modified using the PCD (Programming Configuration Diagnostic) tool. ...
Verification that DXBUS is based on CAN
DXBUS appears to be partially or fully based on the CAN bus based on several references. This is from the Dolphin joystick manual (page 50): 
CAN short fault Cause:
1. Short between CANL and CANH.
Action: < The short may be within a module or within a DX Cable, or the exposed DXBUS contacts may be shorted by foreign material. Ensure that all DXBUS contacts are clean.
CAN L fault Cause:
Action < Check for a short from CANH to another DXBUS wire, or a short
Quote from the paper from the paper Schedulability Analysis of CAN based Systems with Precedence Constraints 
DXBus is a four wire communications system (two power lines and two data lines, CANL and CANH) with a maximum length of 15 meters and a transmission rate of 2/19 Mbits/s. Basically, DXBus uses CAN protocol with some extensions, i. e. special voltage values on the data lines are used for “emergency stops” or power up. CAN identifiers are assigned to modules and not to messages. As a result, 1 byte in the message data field must be used to indicate the message type, and up to 7 bytes for message data. During normal operation, DX modules communicate using Network Variables (NVs). NVs are transmitted periodically (during time slot), with period either 20ms (fast NV) or 200ms (slow NV). A more detailed description of DXBus can be obtained from . In this paper, we focus on the processes associated to DXSIR functions. DXSIR is a wheelchair with two driver wheels
Using Arduino with CAN Bus
Perhaps the fastest way to get started with the CAN Bus is with an Arduino Shield. There's more than one way to lay out a board with the SPI based MCP2551 & MCP2515 chips. Access to a Microchip CAN BUS Analyzer tool is nice, but definitely not necessary. Each of these products has a different pinout on the DB9 port, but that's not really necessary anyway. If you want to connect to your car, then maybe you will care. We are interested in wheelchair hacking, so the shield with the screw terminals may win right off the bat.
- Code to generate and send CAN messages
- Happens to use the joystick on the sparkfun shield
- Code to receive CAN messages and display them over serial
- Also blinks some LEDs, just for fun.
- Seeed Studio's Source code files for Arduino 1.0
- Including the excellent CAN library, and demos which inspired the code examples above.