DFI and ECM Discuss all aspects of DFI (Digital Fuel Injection), ECMs (Electronic Control Module), scanners, and diagnostic equipment. Fine tune your Third Gen computer system for top performance.

Some software/ALDL q's

Thread Tools
 
Search this Thread
 
Old Nov 19, 2004 | 02:01 PM
  #1  
Goumba T's Avatar
Thread Starter
Senior Member
20 Year Member
 
Joined: Jul 2003
Posts: 604
Likes: 0
From: Howard Beach, NYC
Car: 1990 TA
Engine: LB9 305
Transmission: 4L60
Some software/ALDL q's

For the software writing gurus:

As stated in a previous post, I'm working on software for PocketPC for at least the 165 and 730 ECMs.

I've hacked up a cable, damned if I know if it works yet or not. There isn't anything in existence on building a PocketPC compatible data cable - so I don't know if I need to do anything different than a run of the mill USB data cable. And manufacturers aren't too open with their pin-outs.

From what I can tell, the ECM does not respond if I do not send a valid request. Is this correct? If I send an incorrect byte, I get nothing?

Is there anything I can do to find out if the cable itself works? Being that its an ALDL connector on the one end limits me to testing on the computer itself. Any way to get the ECM to just dump so I can play with the cable till the PPC starts receiving?

TIA
Reply
Old Nov 19, 2004 | 03:43 PM
  #2  
RBob's Avatar
Moderator
iTrader: (1)
 
Joined: Mar 2002
Posts: 18,432
Likes: 233
From: Chasing Electrons
Car: check
Engine: check
Transmission: check
From what I can tell, the ECM does not respond if I do not send a valid request. Is this correct? If I send an incorrect byte, I get nothing?
Pretty much. ECM won't respond to data that it does not understand.

Any way to get the ECM to just dump so I can play with the cable till the PPC starts receiving?
There are some MaskIDs that will xmit chatter. The $88 ('730) and $58 ('749) are two that do this. You should see the constant chatter coming across.

RBob.
Reply
Old Dec 11, 2004 | 11:45 PM
  #3  
Goumba T's Avatar
Thread Starter
Senior Member
20 Year Member
 
Joined: Jul 2003
Posts: 604
Likes: 0
From: Howard Beach, NYC
Car: 1990 TA
Engine: LB9 305
Transmission: 4L60
Thanks RBob, now I've run into a new issue (hopefully a non-issue):

I've been trying to connect to the ECM with no success. I can't tell if its the cable or not, but the cable hooked up to a laptop worked last I used it (about 6 months ago).

Now, here's the thing: PocketPCs aren't like desktops when it comes to the serial port. The controller can only use predefined rates - and you guessed it, 8192 isn't one of them.

I know with a PC-PC connection if one is set to a rate the other can't handle/doesn't support, it adjusts. Will this work with the ECM? If I set the software to comnicate at 9600, will I be able to communicate with the ECM?

I'm guessing it won't matter as long as I don't go below 8192bps, it'll work, but I'll ask before I go nuts trying just to find out its not possible.
Reply
Old Dec 12, 2004 | 09:21 AM
  #4  
RBob's Avatar
Moderator
iTrader: (1)
 
Joined: Mar 2002
Posts: 18,432
Likes: 233
From: Chasing Electrons
Car: check
Engine: check
Transmission: check
The ECM can't change it's baud rate. With the PCs/Laptops we use a UART clock divisor of 14 which gives 8228 baud. Not perfect but good enough to talk to the ECM which is 8192 baud (less than a 1% difference in speed).

RBob.
Reply
Old Dec 12, 2004 | 01:52 PM
  #5  
Goumba T's Avatar
Thread Starter
Senior Member
20 Year Member
 
Joined: Jul 2003
Posts: 604
Likes: 0
From: Howard Beach, NYC
Car: 1990 TA
Engine: LB9 305
Transmission: 4L60
Originally posted by RBob
With the PCs/Laptops we use a UART clock divisor of 14 which gives 8228 baud. Not perfect but good enough to talk to the ECM which is 8192 baud (less than a 1% difference in speed).
8228 is no good either. At least the iPaq will not allow any user defined speeds. The closest I can get is 9600 with the built-in serial port of the iPaq.

Looks like I'll put this on hold for a bit.
Reply




All times are GMT -5. The time now is 09:27 PM.