Pocket PC and Tactrix cable
Evolving Member
Joined: Apr 2007
Posts: 195
Likes: 1
From: Slovakia
Just to update - I have managed to get the Tactrix cable working and logging into a PDA (Acer n50 - with USB host support) - using some kind of test software (build based on johnbank's serial logger). Once I get it cleaned up - I will post.
Evolved Member
Joined: Jan 2006
Posts: 953
Likes: 2
From: Oxfordshire
The N50 has a USB host built in, so you just plug an adapter cable into the base of the N50 and the Tactrix into that. I got the Tactrix detected by hacking the .inf files to reflect the PID and VID, after Galvitron pointed me in the rigt direction for the drivers for the ARM processor.
Evo828 will have to fill you in about the software as that bit of news is all his own.
MB
Evo828 will have to fill you in about the software as that bit of news is all his own.
MB
Evolving Member
Joined: Apr 2007
Posts: 195
Likes: 1
From: Slovakia
I installed this driver into my pocket pc (Acer n50):
http://www.ftdichip.com/Drivers/D2XX...D2XXDriver.zip
Instructions:
http://www.ftdichip.com/Documents/In...tion_Guide.pdf
I modified the inf file so it contains the PID ID of my cable. I do not use the serial emulation - connect directly through ftdi driver.
Harware: Acer N50 + USB Host cable + Tactrix (actually Openport cable from Hamish)
Software:
Of course - you need to install .net compact framewok 2.0 into your pocekt pc!!
The logger itself - is a combination of john's earlier serial cable logger + his new logger - which uses FTDI routines. Attached as well.
I am attaching the exe for testing.
Marek
http://www.ftdichip.com/Drivers/D2XX...D2XXDriver.zip
Instructions:
http://www.ftdichip.com/Documents/In...tion_Guide.pdf
I modified the inf file so it contains the PID ID of my cable. I do not use the serial emulation - connect directly through ftdi driver.
Harware: Acer N50 + USB Host cable + Tactrix (actually Openport cable from Hamish)
Software:
Of course - you need to install .net compact framewok 2.0 into your pocekt pc!!
The logger itself - is a combination of john's earlier serial cable logger + his new logger - which uses FTDI routines. Attached as well.
I am attaching the exe for testing.
Marek
Tester.zip
Here is the tester for the Tactrix cable. Sorry about the delay. All this does is try to read and see if you can get past the problem I am having. Unzip, then copy the contained cab file to your device using activesync. Then run the cab from the device and once it is done you will see a new program in Start->Programs. Make sure you have the tactrix cable in when you run it. It will give you either success read or fail message.
Here is the tester for the Tactrix cable. Sorry about the delay. All this does is try to read and see if you can get past the problem I am having. Unzip, then copy the contained cab file to your device using activesync. Then run the cab from the device and once it is done you will see a new program in Start->Programs. Make sure you have the tactrix cable in when you run it. It will give you either success read or fail message.
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
This is really good news. I wondered about upgrading to an Acer N50 so I can use FTDI and 15625 baud, but my old HTC Wallaby (XDA I) upgraded to WM2003SE does the job and I have all the charger/serial/OBD cable setup all done for my car.
Although it is unrealistic to flash, if we get map switching added into the app it could rival a certain commercial offering.
I would like to ask for help on two items:
1. Please make the error checking more robust on the FTDI logger.
2. Please help me work out how to make the same code work to scroll graphs on the PC.
Although it is unrealistic to flash, if we get map switching added into the app it could rival a certain commercial offering.
I would like to ask for help on two items:
1. Please make the error checking more robust on the FTDI logger.
2. Please help me work out how to make the same code work to scroll graphs on the PC.
I am troubled because the FTDI_Read request is working for yours but not mine. Maybe I have too old of a tactrix cable...
In the logger posted above it does the init then a FT_Read then starts the logger. The call to FT_Read fails on my device/cable...
In the logger posted above it does the init then a FT_Read then starts the logger. The call to FT_Read fails on my device/cable...
Evolved Member
Joined: Jan 2006
Posts: 953
Likes: 2
From: Oxfordshire
John, I tested the PC logger, it worked pretty much as expected including the ROM reads. I could just make out the graph scrolling but it was as if it used only 2 pixels for width.
Jeremy, Evo828s version works on my setup, but didn't with the version you modded from Johns original, so I suspect it isn't a hardware issue.
MB
Jeremy, Evo828s version works on my setup, but didn't with the version you modded from Johns original, so I suspect it isn't a hardware issue.
MB
Maybe my cable. When I get back to L.A. I will try the new version. If it doesn't work it is my cable and all of my time was wasted
Oh well, at least there is a solution now.
Oh well, at least there is a solution now.
Evolving Member
Joined: Apr 2007
Posts: 195
Likes: 1
From: Slovakia
This is really good news. I wondered about upgrading to an Acer N50 so I can use FTDI and 15625 baud, but my old HTC Wallaby (XDA I) upgraded to WM2003SE does the job and I have all the charger/serial/OBD cable setup all done for my car.
Although it is unrealistic to flash, if we get map switching added into the app it could rival a certain commercial offering.
I would like to ask for help on two items:
1. Please make the error checking more robust on the FTDI logger.
2. Please help me work out how to make the same code work to scroll graphs on the PC.
Although it is unrealistic to flash, if we get map switching added into the app it could rival a certain commercial offering.
I would like to ask for help on two items:
1. Please make the error checking more robust on the FTDI logger.
2. Please help me work out how to make the same code work to scroll graphs on the PC.
Does anyone know how to get milliseconds working on he pocketpc logger - whatever I do - they still seem to appear on whole thousands - so I am not able to get any smaller. Now when I am logging 3-4 rowsof data per second (also would like to speed up a little bit) - I do not know the exact timing of these rows
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
Not sure how you get ms, look in data.time. ?
Using the serial port on the Pocket PC I get about 8 lines a second. On the laptop version using FTDI I get similar. I wonder if the FTDI drivers are a bit slow on the Pocket PC?
Using the serial port on the Pocket PC I get about 8 lines a second. On the laptop version using FTDI I get similar. I wonder if the FTDI drivers are a bit slow on the Pocket PC?