1227165 ECU Questions
Re: 1227165 ECU Questions
I live in Washington state in the US and unfortunately we get a lot of rain over winter and that has stall progress on my project until now. I got the wiring, intake, and the sensors mocked up in the car. Right now the issue that I am dealing with is getting data from the ECU to my android phone. All I am doing is turning on the ignition to see if I can see data from the sensors like IAT, CTS, and MAP. However I have two issues. The 27SF512 chip can be installed in the Moates G1 adapter one of two ways. I have included a youtube link below to show how Moates says the chip should be installed. When I install the chip the wrong way the bluetooth aldl adapter lights up and stays on. I then connect to it when my phone but I get an error "incorrect response length from ecu 5 vs 60" from ALDL Droid on my android phone and I don't get any data from any of the sensors. When I install the chip in the right orientation and I turn the ignition on the bluetooth adapter comes on and shuts off after 5-10 seconds so I cannot connect to it to check to see if I am receiving any data. Does ecu need to see the car running before you can pull data from the sensors? Or is there some other issue like with how the ADX file is built, an issue in the bin file, or a baud rate issue? As far as I can tell I have burned the chips right. I have tried the same bin stacked to fill up the whole chip also with no luck. Also when the ignition is on I do not get a check engine light no matter how the chip is oriented.
Chip Adapter for 1227165 ECU: http://support.moates.net/g1/
Chip: 27SF512
ADLD Droid ADX File Im Using: https://pcmhacking.net/forums/viewt ... 939#p80939
Chip Burner: http://support.moates.net/burn2/
Android App: https://www.aldldroid.com
ALDL to Bluetooth Adapter: http://www.reddevilriver.com/ALDL_Bluetooth.html
Chip Burning Software: http://support.moates.net/flash-n-burn/
Proper Chip Orientation in G1 Adapter - https://www.youtube.com/watch?v=RroPpf1fu-A
Chip Adapter for 1227165 ECU: http://support.moates.net/g1/
Chip: 27SF512
ADLD Droid ADX File Im Using: https://pcmhacking.net/forums/viewt ... 939#p80939
Chip Burner: http://support.moates.net/burn2/
Android App: https://www.aldldroid.com
ALDL to Bluetooth Adapter: http://www.reddevilriver.com/ALDL_Bluetooth.html
Chip Burning Software: http://support.moates.net/flash-n-burn/
Proper Chip Orientation in G1 Adapter - https://www.youtube.com/watch?v=RroPpf1fu-A
Re: 1227165 ECU Questions
12P on a 512 eeprom, have you stacked the bin?
- antus
- Site Admin
- Posts: 8253
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: 1227165 ECU Questions
Im not sure about the bluetooth interface, I assume that would introduce significant delay on packet transfer. Im not saying it wont work but your introducing a lot of unknowns there. The car needs to be on, the engine does not need to be running to pull data. I would expect the BT interface to stay up and running provided it has power from the OBD port, regardless of anything to do with the computer. I'd suggest mounting chips the right way. Your sending power in to pins that are not meant to have power if you swap it around and that can do hardware damage. This damage might have already occurred. You would want to verify you can still read the chip in your programmer at this stage. Also make sure you have a stacked 32kb bin as Dylan suggests.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: 1227165 ECU Questions
I have already pulled the chip out and verified that it can still be read/written too. The chip seems to still function as normal. I have a backup chip which does the exact same thing. I also have a second 1227165 ecu which functions the exact same way when the chip is oriented correctly. The bluetooth adapter leds come on for about 5-10 seconds then shuts off. I have a second ECU to verify if there was an ECU issue I had wondered if the ecu itself was bad. I attached a screenshot of how I stacked the bin if you can verify it looks like it was done correctly that would help.
- antus
- Site Admin
- Posts: 8253
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: 1227165 ECU Questions
That looks right. But the BT shouldnt shut off, its got nothing to do with the computer. Check your power to the OBD port is staying on, and if so, probably ask your hardware vendor what to expect from their interface.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: 1227165 ECU Questions
Something I want to confirm. When I was building the wiring harness I could have overlooked this. According to the factory gm camaro wiring diagram the 8192 baud port is A8 which goes to pin M on my ALDL connector. However the ose12p wiring diagram does not state which port on the ECU is for serial data. Can anyone confirm if I should be receiving data from the pin A8 on the ecu?
Pin A8: Serial data
Pin A9: Diagnostics Request
OSE12P Wiring: download/file.php?id=23730
Factory US GM Wiring Diagram: http://chevythunder.com/fuel%20injectio ... 0#1227165)
ALDL Interfaces: http://www.makinterface.de/aldl_e.php3
Pin A8: Serial data
Pin A9: Diagnostics Request
OSE12P Wiring: download/file.php?id=23730
Factory US GM Wiring Diagram: http://chevythunder.com/fuel%20injectio ... 0#1227165)
ALDL Interfaces: http://www.makinterface.de/aldl_e.php3
- delcowizzid
- Posts: 5493
- Joined: Sat Feb 28, 2009 8:38 pm
- Location: Wellington NZ
- Contact:
Re: 1227165 ECU Questions
Probably has something to do with the cable outputting at 9600 baud see it says there's a fix for tunerpro on the red devil link you shared .or it's just defective a lot of the USA guys have had dead ones on arrival
If Its Got Gas Or Ass Count Me In.if it cant be fixed with a hammer you have an electrical problem
Re: 1227165 ECU Questions
Alright I did some additional troubleshooting. I traced each wire going to the ALDL connector. I found that when I wired it originally I had hooked it up as 160 baud on the ALDL connector for some reason. I connected it so its 8192 baud on the M connector of the ALDL. That did not fix the issue. I took a multimeter and connected it to the G (12v Power) and A (Ground) connector on the ALDL. I cycled the ignition and saw I was losing power on the G connector after 5 seconds or so. The G wire goes to far back in my harness I am not sure what it is connected too, and I did not want to pull the entire harness out and trace it. So I cut the G wire and hooked it into a relay that activates when I turn on the ignition. After doing these two things my bluetooth ALDL adapter does not shut off when the ignition is on. I pulled up ALDL droid on my phone. ALDL is now seeing data from the sensors. I dont know if the data is accurate or anything I have not had time to troubleshoot further I got to work for the next two or three days. I will post if I run into any further issues. Thanks for everyone's input though. My bluetooth ALDL adapter needs power on the G pin of the ALDL connector to work.
- Attachments
-
- obd1pinout2.gif (5.04 KiB) Viewed 6953 times
- antus
- Site Admin
- Posts: 8253
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: 1227165 ECU Questions
Cool. G sounds like fuel pump so it would go off after its primed if it didnt start
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: 1227165 ECU Questions
Currently I am waiting for a fuel rail o-ring set my rail itself is leaking fuel. Should be here in the next two days when I am off work. In the meantime I wanted to look at changing two of the values in the .ADX file to imperial. Changing engine coolant temp and air temp from celsius to imperial. This should be easy making the following changes. I just have two questions does this need to be done in tuner pro like the .XDF? The second question I have is which of these .ADX files to I need to be using? With or without calcVE?
OSE_$12PV112_1BAR - Petrol.adx
OSE_$12PV112_1BAR - Petrol with calcVE.adx
From: <MATH equation="(x * .75) - 40">
To: <MATH equation="(x * 1.35) - 40">
<ADXVALUE id="4" idhash="0x86F3533B" title="Engine Coolant">
<flags>0x0000000C</flags>
<parentcmdidhash>0x55C678F5</parentcmdidhash>
<units>Coolant Degrees C</units>
<packetoffset>0x05</packetoffset>
<range low="0.000000" high="130.000000" />
<alarms low="-5.000000" high="110.000000" />
<digcount>1</digcount>
<outputtype>3</outputtype>
<datatype>13</datatype>
<unittype>15</unittype>
<MATH equation="(x * .75) - 40">
<VAR varID="x" type="native" />
</MATH>
</ADXVALUE>
<ADXVALUE id="6" idhash="0x86F347FB" title="Manifold Air Temp">
<flags>0x0000000C</flags>
<parentcmdidhash>0x55C678F5</parentcmdidhash>
<units>MAT Degrees C</units>
<packetoffset>0x07</packetoffset>
<range low="0.000000" high="130.000000" />
<alarms low="-5.000000" high="120.000000" />
<digcount>1</digcount>
<outputtype>3</outputtype>
<datatype>18</datatype>
<unittype>15</unittype>
<MATH equation="(x * .75) - 40">
<VAR varID="x" type="native" />
</MATH>
</ADXVALUE>
OSE_$12PV112_1BAR - Petrol.adx
OSE_$12PV112_1BAR - Petrol with calcVE.adx
From: <MATH equation="(x * .75) - 40">
To: <MATH equation="(x * 1.35) - 40">
<ADXVALUE id="4" idhash="0x86F3533B" title="Engine Coolant">
<flags>0x0000000C</flags>
<parentcmdidhash>0x55C678F5</parentcmdidhash>
<units>Coolant Degrees C</units>
<packetoffset>0x05</packetoffset>
<range low="0.000000" high="130.000000" />
<alarms low="-5.000000" high="110.000000" />
<digcount>1</digcount>
<outputtype>3</outputtype>
<datatype>13</datatype>
<unittype>15</unittype>
<MATH equation="(x * .75) - 40">
<VAR varID="x" type="native" />
</MATH>
</ADXVALUE>
<ADXVALUE id="6" idhash="0x86F347FB" title="Manifold Air Temp">
<flags>0x0000000C</flags>
<parentcmdidhash>0x55C678F5</parentcmdidhash>
<units>MAT Degrees C</units>
<packetoffset>0x07</packetoffset>
<range low="0.000000" high="130.000000" />
<alarms low="-5.000000" high="120.000000" />
<digcount>1</digcount>
<outputtype>3</outputtype>
<datatype>18</datatype>
<unittype>15</unittype>
<MATH equation="(x * .75) - 40">
<VAR varID="x" type="native" />
</MATH>
</ADXVALUE>