New to tuner pro (dashboard)

rjnelson1975 · Post by **rjnelson1975** » Sun Jan 01, 2012 8:23 am

I am new to tunerpro and fuel injection tuning in general. I installed tunerpro rt and got the laptop hooked up the the ecm (1227165) through the aldl connector/usb adapter. I am getting some communication but the readings on the dash board are all messed up. All the gauges do are bounce up and down from min to max. I have 1227165 definition loaded. Any help? thanks

EagleMark · Post by **EagleMark** » Sun Jan 01, 2012 11:24 am

Sounds like you have a glitch. Your adx is fairly popular did you get the latest avaialble from downloads?

This thread may help
http://forum.tunerpro.net/viewtopic.php?t=2215

EagleMark · Post by **EagleMark** » Sun Jan 01, 2012 11:27 am

What mask?

rjnelson1975 · Post by **rjnelson1975** » Sun Jan 01, 2012 12:56 pm

I don't know what the "mask" is? could you describe it and tell me how to fix it? thanks for the reply.

rjnelson1975 · Post by **rjnelson1975** » Sun Jan 01, 2012 12:59 pm

$6E is the mask and I just downloaded it today thanks.

rjnelson1975 · Post by **rjnelson1975** » Sun Jan 01, 2012 1:37 pm

Just some more info on my set-up. I have a 383 sbc in a 98 s10 with a tuned port fuel injection system. Truck runs great but idle is a little rough and a little rich. I would like to get in to using tunerpro to fix these small issues and to get into fuel injection tuning as a whole. The ecm is stock (1227165) with a hypertech chip that came with it. With the truck running well and scan tools working, I know I must be doing something wrong with the tunerpro set-up. Again the issue is that I plug in and start data flow but the all of the dashboard readings just bounce from min to max and the DA: at the bottom of the screen goes from connected to error and back again just like the dashboard readings. Do I have to have a bin loaded? xdf? I tried to get these files from cod59.org but am having trouble with registration.

EagleMark · Post by **EagleMark** » Sun Jan 01, 2012 2:20 pm

You do not need bin or xdf/mask to data log. But here's a link to a few bins and defs:
http://www.gearhead-efi.com/Fuel-Inject ... rmation-6E

Really sounds like you are not getting a proper connection from your cable to laptop. If you installed your cable with proper drivers you can check connection in TunerPro by going to tools, Preferences and Data Acq/Emulation. TunerPro likes Com3-4.

Or try another USB port and open TP again...

EDIT: I added a couple adx files there with a pause which helps with glitch... but I think you have above problems. You can try the
$6E-1227165-V1.adx
and
$61-1227165-V1.2.adx

rjnelson1975 · Post by **rjnelson1975** » Sun Jan 01, 2012 2:35 pm

Checked the cable with TP ,"cable found and functional". using com4. Are there some special settings that may need adjustment in the adx editor like:
"connect command"
"monitor command"
"disconnect command"
"parity"
"idx item defaults"
"dependency's"
"different commands maybe?"

tried different baud rates with no effect.
The cable that I am using is from aldlcable.com with 12 pin on one end to usb on the other. It also has a jumper on the usb end witch I have tried all of the options with no luck.

Any ideas? thanks

EagleMark · Post by **EagleMark** » Sun Jan 01, 2012 2:42 pm

Email me your adx I will take a look! mark at eagle-mark.com

Baud is usually set to 0 which is default...

You could try the others in meantime... they do not have a connect or disconnect and I am not sure they are needed on this adx...

EagleMark · Post by **EagleMark** » Sun Jan 01, 2012 2:59 pm

what year make and model is your car?

rjnelson1975 · Post by **rjnelson1975** » Sun Jan 01, 2012 3:06 pm

The tuned port system was an e-bay purchase so I don't know the exact vehicle that it came off of. thanks

EagleMark · Post by **EagleMark** » Sun Jan 01, 2012 4:13 pm

I looked at ALDL files for $6E and there seems to be a huge difference in 89 to 90. From what you told me you have one that is the far more complicated of the 2.

Try the other one I linked you to.

I would like to see what yours looks like and I can match it to the ALDL.ds file.

rjnelson1975 · Post by **rjnelson1975** » Mon Jan 02, 2012 1:16 pm

Tried the other adx files, same result (readings bouncing) prom id on the item list is also changing.

EagleMark · Post by **EagleMark** » Mon Jan 02, 2012 2:37 pm

Well if I have correct ALDL filesand it is a 1989 it is a very complicated adx to create, read below. Then I will give an example of 1990 which is completly differant and simple...

"DATA STREAM A59 SPECIFICATION

ENGINE USAGE:
5.0l PFI - (LB9) - (F) - 89
5.7l PFI - (L98) - (8) - 89

DATA PIN: ALDL DATA AT 8192 BAUD IS TRANSMITTED ON ALDL
PIN "E".

BAUD RATE: 8192

MODES : DATA STREAM ATTACHED FOR ALDL MODE 1

THESE ENGINES USE A 'HYBRID' ECM, AND THE 8192 DATA
COMMUNICATIONS OCCUR ON ALDL PIN 'E'
Serial data shall be unidirectional from the ECM to a connected
device at 160 baud when the ECM is not in the ALDL mode. When the
ECM is in the ALDL mode (10k), the ECM shall transmit the normal
25 parameter ALDL list at the 160 baud rate. The ECM shall then
be moded to listen for a period of 50 ms for an inbound message
from an ALDL test device at an 8192 baud rate. If a valid message
is received, communications shall continue at an 8192 baud rate
until a power down reset. Otherwise, the ECM shall be moded for
160 baud, transmit the 25 parameter ALDL list and then listen for
50 ms for an 8192 baud inbound message.
------------------------------------------------------------

DATA PIN : READ DATA ON PIN "E" OF ALDL CONNECTOR

BAUD RATE : 160

MODES : THIS IS THE DEFAULT MODE OF COMMUNICATING WITH
THE VEHICLE.

..PAGE

8192 COMMUNICATIONS

THESE ENGINES USE A 'HYBRID' ECM, AND THE 8192 DATA
COMMUNICATIONS OCCUR ON ALDL PIN 'E'. "

now for 1990...

" DATA STREAM A100 SPECIFICATION

ENGINE USAGE:
5.0 PFI (LB9) (VIN=F) 90, 91
5.7 PFI (L98) (VIN=8) 90, 91

DATA PIN : READ DATA ON PIN "M" OF ALDL CONNECTOR

BAUD RATE : 8192 BAUD - BI-DIRECTIONAL
..PAGE
MODE 0 (INPUT MESSAGE)
ALDL REQUEST: THE ALCL TESTER MUST TRANSMET THE FOLLOWING
MESSAGE TO THE ECM, AFTER AN IDLE LINE IS
DETECTED.
- MESSAGE ID = $F4
- MESSAGE LENGTH = $56
- MODE = $00
- SUM CHECK

ECM RESPONSE: THE ECM WILL TRANSMIT THE FOLLOWING MESSAGE.
- MESSAGE ID = $F4
- MESSAGE LENGTH = $56
- MODE = $00
- SUM CHECK

MODE 1 (ALCL MODE)
THE UART ALDL MODE - MODE 1 WILL ONLY BE ACTIVE IF REQUESTED
BY THE ALCL TESTER.
ALDL REQUEST:
- MESSAGE ID = $F4
- MESSAGE LENGTH = $56
- MODE = $01
- MESSAGE NUMBER = $00
- SUM CHECK

THE ECM WILL RESPOND WITH THE FOLLOWING MESSAGE:
- MESSAGE ID = $F4
- MESSAGE LENGTH = $95
- MODE = $01
- DATA BYTE 1
.
.
- DATA BYTE 63
- SUM CHECK

MODE 10 (CLEAR MALFUNCTION CODES)
ALDL REQUEST:
- MESSAGE ID = $F4
- MESSAGE LENGTH = $56
- MODE = $0A
- CHECKSUM

THE ECM BROADCASTS NO NORMAL MODE MESSAGES, NOR DOES IT ISSUE AN $F0 POLL."

Since you tried the simple ones on the link I gave and did not work, I may be able to see what's wrong with the more complex version you have if I could see it?

Or your just not connected properly with cable from car to laptop with correct drivers installed?

EagleMark · Post by **EagleMark** » Mon Jan 02, 2012 2:42 pm

Cables have jumpers between Pin M which is usually 8192 Baud and Pin E which is usually 160 Baud. Reciving data only on one line. Complicating matters of the first example...

rjnelson1975 · Post by **rjnelson1975** » Mon Jan 02, 2012 5:01 pm

going to try reloading the aldl software and drivers. will let you know

rjnelson1975 · Post by **rjnelson1975** » Wed Jan 04, 2012 6:09 am

Tryed all different kinds of drivers with no better results. Running windows 7 would that be an issue maybe? Would an older version of TP work? The drivers that I tryed were ment for win7. I will keep trying, getting frustrated. thanks

EagleMark · Post by **EagleMark** » Wed Jan 04, 2012 6:21 am

If you have had other software hooked up to cable it is worse to get hooked to TP.

I really don't know why TPV5 is so hard to get to once you have used your cable with other software? I wish I knew an exact cause an answer for you...

http://support.moates.net/2009/02/10/us ... oting-101/

http://support.moates.net/2009/02/10/tr ... tallation/

http://support.moates.net/2009/02/10/us ... s-ftclean/

rjnelson1975 · Post by **rjnelson1975** » Wed Jan 04, 2012 9:11 am

I have ran another software package and different cable on this laptop for a transmission controler (Baumannator 4l60e) that works fine.

Post by **Mangus** » Thu Jan 05, 2012 9:07 pm

rjnelson1975 wrote:I have ran another software package and different cable on this laptop for a transmission controler (Baumannator 4l60e) that works fine.

A few things aren't adding up here. First, your statement quoted here - that is completely unrelated to the '165. Second, the '165, if from a 1986 TPI vehicle, would use $32 mask, and the 6E mask wouldn't work for it.

1990 does not use a '165 ECM; it uses a 7730 ECM and $8D mask.

Code 59 will only run on '65 and 7730 ECMs.

Your first order of business should be to identify exactly what ECM you have in it, and exactly what chip is in it.

rjnelson1975 · Post by **rjnelson1975** » Sun Jan 08, 2012 8:01 am

To verify the numbers for the ecm: serv. no. 01227165. There was another tag on the ecm case with these numbers: 16141781 and a 861781m010531194. The hypertech chip had "88 tpi" written on the side. There was a little window on the chip that had a 601 and a 12b. Communication wire on the aldl is on "m". The cable is an aldlcable.com unit with obd1 on the one end and usb on the other. The laptop that I am using is a brand new Lenovo running windows 7. Should I try moving the communication wire on the aldl connector to "e" maybe? What mask should work?

Post by **Mangus** » Sun Jan 08, 2012 9:54 am

88 TPI is $32B mask. Basically the same as $6E, basically the same ADS/ADX.

Don't forget that you need 10K of resistance between A&B. in order for ALDL data to flow.

rjnelson1975 · Post by **rjnelson1975** » Sun Jan 08, 2012 11:26 am

Tunerpro is giving me an error message when I try to load $32b. Failed to load 1227165_160.adx. Unrecognized encoding (parser does not support UTF-8 language encodings). I tried the file as an ads and as an adx with the same error. ??

Post by **Mangus** » Sun Jan 08, 2012 11:27 am

rjnelson1975 wrote:Tunerpro is giving me an error message when I try to load $32b. Failed to load 1227165_160.adx. Unrecognized encoding (parser does not support UTF-8 language encodings). I tried the file as an ads and as an adx with the same error. ??

Don't use 160. Use the 6E definition. Also, they're ADS files. Acquisition->Import Definition->From ADS...

rjnelson1975 · Post by **rjnelson1975** » Sun Jan 08, 2012 12:46 pm

Yes, Yes, Yes !!! It works now. Now I can start to play. Thank you for all of your patience with me. I am sure there will be more questions, but I am good to go for now. Thanks again!!!

EagleMark · Post by **EagleMark** » Sun Jan 08, 2012 12:48 pm

rjnelson1975 wrote:To verify the numbers for the ecm: serv. no. 01227165. There was another tag on the ecm case with these numbers: 16141781 and a 861781m010531194. The hypertech chip had "88 tpi" written on the side. There was a little window on the chip that had a 601 and a 12b. Communication wire on the aldl is on "m". The cable is an aldlcable.com unit with obd1 on the one end and usb on the other. The laptop that I am using is a brand new Lenovo running windows 7. Should I try moving the communication wire on the aldl connector to "e" maybe? What mask should work?

I'm confused? If you have a ALDLCABLE.com cable with OBDI end? How would you move communication wire from M to E ? It just plugs in. Inside the OBDI plug on end E and M are jumpered so they can gather data from 160 baud on pin E and 8192 baud on pin M so it works on both.

Or do you have bare pin cable on end? No molded plug and need to plug the wires into ALDL port? If so you need to move communication wire to pin E on ALDL port for this ECM if it is 1988 - 1989.

And what Mark said!

Don't forget that you need 10K of resistance between A&B. in order for ALDL data to flow.

This is the little jumper on USB end of aldlcables.com cable. Look at their instructions for correct pins to jump for 10k resistor.

EagleMark · Post by **EagleMark** » Sun Jan 08, 2012 12:50 pm

rjnelson1975 wrote:Yes, Yes, Yes !!! It works now. Now I can start to play. Thank you for all of your patience with me. I am sure there will be more questions, but I am good to go for now. Thanks again!!!

D'oh!

rjnelson1975 · Post by **rjnelson1975** » Sat Mar 17, 2012 12:23 pm

I now have a gr1 adapter, pocket romulator 2, burn2 chip burner. Tried to emulate today with tunerpro v5, usb to serial adapter, pocket romulator, and gr1 adapter all hooked up. I downloaded the bin off the chip (hypertech) with the burn2 and uploaded it into the romulator and tunerpro. Everything looks good with TP telling me that it is emulating, but the engine barely runs and responds. I checked all of the orientations of the cabels and chip. I even unplugged the romulator from the gr1 and the engine still runs (poorly)????
Can the ecm still run with the stock chip plugged in to the gr1 only (no chip in the zif socket)????? Is there going to be a problem running the hypertech chipset with this configuration, or will I have to work with a stock memcal????
Any advice??
thanks

rjnelson1975 · Post by **rjnelson1975** » Sat Mar 17, 2012 1:54 pm

I think I may have found an issue with the bin download from the hypertech chip. When I go into tunerpro and bring up the bin and look at the tables there is no data in the graphs. Definition problem???

EagleMark · Post by **EagleMark** » Sat Mar 17, 2012 3:56 pm

I don't know what a gr1 is and I know nothing about the romulater. But you should really read the bin fro 00000 to FFFFF and if it's a 24 pin the fourth digit will be the mask ID like 42 or a 28 pin chip will be 8th digit like "6E" and get the right definitions for your bin.

In AutoProm to emulate you should "Use a setting of “AA at 08” for 28 pin applications, and “AA at 04” for 24 pin ECMs." to emulate. This disables checksum while your changing things emulating.

rjnelson1975 · Post by **rjnelson1975** » Sun Mar 18, 2012 6:35 am

I have a 28 pin chip. Using mask $32b. I tried the 00000 FFFFF and it did not work. I also tried downloading the bin from the chip with each and every chip supported in the drop down window in tunerpro with some of them giving me all zeros in the graphs and some giving me 89.65 in all of the cells. What did you mean by the 8th digit?? Is that a spot in the address??
thanks

EagleMark · Post by **EagleMark** » Sun Mar 18, 2012 9:29 am

Sounds like your using wrong mask? Or buring to wrong offset?

If you open the bin in hex editor and find first lines that are not FF or 00 the 8th digit of hex counting from 0, not 1 will be mask ID.

rjnelson1975 · Post by **rjnelson1975** » Sun Mar 18, 2012 12:39 pm

checked the mask id and it is 32. still getting no data in the graphs

EagleMark · Post by **EagleMark** » Sun Mar 18, 2012 2:59 pm

I've never dealt with $32 but I looked in my collection and there is a $32, $32B, $32 BUA, $32 V6 and $32 extended... I uploaded them all for you to try here:
http://www.gearhead-efi.com/Fuel-Inject ... rmation-32

EagleMark · Post by **EagleMark** » Mon Mar 19, 2012 5:00 am

rjnelson1975 wrote:checked the mask id and it is 32. still getting no data in the graphs

If you open Mask ID in XDF Scalers does it say 32?

rjnelson1975 · Post by **rjnelson1975** » Mon Mar 19, 2012 2:55 pm

cant find mask id in scalers . seems like no matter what i do the ecm is always in limp home mode. I even tried two 32 masks from moates.net. all uploads to the romulator seem to be working ok. tunerpro is emulating ok. everything looks to be working but always in limp home mode, unless I reinstall the hypertech chip in the ecm?????