Wanted to post a followup on the trouble that was found with the C300 chair.First I want to thank all of you that posted suggestions, comments, schematics, links, software, etc. I greatly appreciate your help and efforts.
The problem found was the Extra Low Speed Inhibit. I did not find any issue with the actual switch located on the seat elevator. Looking at the inhibits in the program I noticed the Extra Low Speed Inhibit was set to 100. I changed this to 0, uploaded the new parameters and the chair was working as expected. I also changed the steering parameters turn acceleration / deceleration / etc as suggested by Burgerman on the site. The changes made a noticable difference in the steering for the better. Also played with some of the other parameters to get a feel of the options available.
One of the problems I ran into was with the programming cable. I ordered a Arduino FT232 USB to TTL cable off of ebay. Link here:
http://www.ebay.com/itm/161181323524?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AITI would not suggest ordering from this supplier.
Once I received the cable and connected it to my pc, tried Windows XP and Windows 7, I could not get the machine to recognize the adapter, install drivers, or setup the virtual com port. I contacted FTDI and asked for suggestions on setting up the drivers for the device. FTDI suggested that I use USBView, a program that be downloaded from there site, to pull the output of the FT232 chip on the adapter cable and send a copy to them. There main concern was the Venderid (VID) and Productid (PID) assigned to the chip. FTDI responded that the chip on the cable/adapter was a non-Genuine, fake, or custom configured chip that would not work with the certified default drivers found on there site. Also note that the supplier did not provide any drivers nor have any knowledge of drivers needed. The problem with the FT232 chip that I had was the PID was set to 0x0000. FTDI commented the current PID setting of the FT232 chip was not a valid PID for chips they release to work with default drivers.
Through further digging I found that FTDI does have a program that will allow you to alter there drivers or create your own custom driver to work with custom PIDs assigned to FT232 chip. Below is the process used to create two custom driver inf files that would communicate with the FT232 chip with a PID set to 0x0000.
FTDI provides a program ( FT_INF ) which is able to config their driver to work with custom PIDs ,
The program can be downloaded from this link
http://www.ftdichip.com/Support/Utilities/FT_INF_v2.0.61.242_Installer.exe Then you will need an old FTDI driver like this: (NOTE: I was told that the newer drivers can detect a non-genuine (fake) chip and may not work. )
32bit:
http://www.ftdichip.com/Drivers/CDM/CDM%202.08.30%20WHQL%20Certified.zip64bit:
http://www.ftdichip.com/Drivers/CDM/CDM%202.08.30%20WHQL%20Certified.zipNext run the FT_INF, set chip type to FT232/245R and PID to 0000 (or whatever PID value USBView output from your chip / cable), then extract above zip,
in Time Stamp/Filename, select ftdibus and ftdiport, then using this
>> to add your prefer config to right menu.
Next click Generate files.
2 new
inf files will be generated. Copy the 2 files to the folder where you extracted the ziped files, and overwrite them.
Then manually point windows to your new driver.
I used this procedure with Windows XP and was able to get the OS to recognize the adapter, install drivers, and setup the virtual com port. The cable was then completed using XLR / Neutrix plug, 1N4148 diode, and 47K ohm resistor as described in Woody schematic here:
http://www.wheelchairdriver.com/board/viewtopic.php?f=2&t=2111&start=640Once the cable was completed and connected to the chair, the correct com port was selected in Mobility Programming software and the program stated Active Comm. At this point the program could be retrieved / read from the controller and new parameters written to the controller.
I thought the above might help other that may experience the same problems.
Thanks again to everyone,
Richie