openecu.org

by **visualsinz** » Sun Dec 30, 2007 12:30 pm

I have been getting the:
Voltage is 4.23
voltage is too low
error when flashing with ecuflash.
ive tried jumping the flashblock (tapping into the wire that loops) to the battery.
ive tried tapping into the OBDII 16 pin (12 supply) to the battery, which i think has messed up my OBDII cause now i get a get kernel error.
ive tried tappin in the OBDII 4 pin (ground) and grounding it out.

all this with a battery charger connected.

I have a 02 usdm wrx and ive heard they have a problem with this. I have however tried everything that has worked for others and came up with nothing.

if you know if tapping into the 4 and 16 pin could have messed something up that would be helpful too cause now im worried. thank you in advanced.

by **Easyrider** » Sun Dec 30, 2007 1:33 pm

The low voltage error usually comes up if you forget to jump the flashing connector-so i presume that when you tried to flash that you joined the 2 green connectors and you had a bad connection bridging the other single connector.

by **visualsinz** » Sun Dec 30, 2007 1:58 pm

i had the green test connectors connected and have a brand new setup. they were suppose to fix the problem with the flash block where they had a loose connection issue. how would i determine if i have a bad connection at the flash block? also, would spicing into the obdII at pin 16 and 4 cause a problem?

by **Easyrider** » Sun Dec 30, 2007 5:17 pm

Best way to know if the flash block connection is ok is to test for no resistance over your block connector (the one you plug into the flash block)
Cant help you with splicing into the OBD wires-you shouldnt have any need to do this-why have you?

by **visualsinz** » Sun Dec 30, 2007 5:56 pm

worked for someone in another post

by **visualsinz** » Sun Dec 30, 2007 7:10 pm

just for clarification, im using the tactrix 1.3 and enginuity 1.34. attached is a log reading the ecu and several trying to flash

<html><head><meta name="qrichtext" content="1" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Courier'; font-size:8pt; font-weight:400; font-style:normal;">
[20:52:28.937] Version 1.34.1435
[20:52:28.937] 11 memory models read.
[20:52:28.937] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[20:52:29.062] 219 ROM metadata models scanned.
[20:52:29.062] checksum module "subarudbw" loaded.
[20:52:29.062] flashing tool "wrx02" loaded.
[20:52:29.062] flashing tool "wrx04" loaded.
[20:52:29.062] flashing tool "sti04" loaded.
[20:52:29.062] flashing tool "sti05" loaded.
[20:52:29.062] flashing tool "mitsukernel" loaded.
[20:52:29.062] flashing tool "mitsukernelocp" loaded.
[20:52:29.062] flashing tool "shbootmode" loaded.
[20:52:53.468] Using interface OpenPort 1.3 Subaru TX47BvEX74c3f4d53675fc04f1d6c5401966815fa5e3edb3
[20:52:57.890] denso02_bootloader_cmd_start
[20:52:59.125] denso02_bootloader_cmd_start
[20:53:00.343] denso02_bootloader_cmd_start
[20:53:01.562] denso02_bootloader_cmd_start
[20:53:02.781] denso02_bootloader_cmd_start
[20:53:03.218] kernel get version
[20:53:03.562] interface close
[20:53:03.562] interface close
[20:53:13.218] A4SGD10C (283 tables) inheriting 16BITBASE (404 tables)
[20:53:13.234] A4SGE01C (1 tables) inheriting A4SGD10C (404 tables)
[20:53:13.250] 196608 byte image read.
[20:53:17.578] Using interface OpenPort 1.3 Subaru TX47BvEX74c3f4d53675fc04f1d6c5401966815fa5e3edb3
[20:53:21.375] denso02_bootloader_cmd_start
[20:53:22.593] denso02_bootloader_cmd_start
[20:53:23.828] denso02_bootloader_cmd_start
[20:53:25.031] denso02_bootloader_cmd_start
[20:53:26.250] denso02_bootloader_cmd_start
[20:53:26.703] kernel get version

by **Easyrider** » Wed Jan 02, 2008 9:19 am

Just an idea-
Check behind the passenger footwell plastic side pannel-on mine there was another set of green connectors(the same as under the dash)-these should be permanently connected(theyre linked with the dash ones)-
I had an issue where i couldnt read/flash and got the "kernel get version"
error come up, i eventually found these plugs disconnected by pure chance!! Once connected,everything worked fine.

by **visualsinz** » Wed Jan 02, 2008 11:20 am

i have an 02. i know the newer wrxs have 2 sets, but i didnt think the older ones did. i will check tonight and update

by **Easyrider** » Wed Jan 02, 2008 12:13 pm

Mine's an 02(uk though)

by **visualsinz** » Wed Jan 02, 2008 12:46 pm

ill try tonight and post it up. i hope that could be the case. i will be happy and and the same time want to kick myself for 2 months of fooling with it!

by **visualsinz** » Wed Jan 02, 2008 4:42 pm

popped the door panel off of the passenger side and found the green test connectors. they were already securely coneected, so that was no good. thanks for the suggestion though. back to square one

by **Easyrider** » Wed Jan 02, 2008 4:51 pm

Well-i dont know then.
Have you managed to read the ROM yet?
If not then you may have a problem with COM port settings-i also got the kernel error when i had a modem using the COM3 also which caused a conflict between the modem and the tactrix cable-i just changed the modem to another COM number in system devices on the PC.

by **visualsinz** » Wed Jan 02, 2008 5:35 pm

before i cut the OBDII wires i could read the rom, but it wouldnt enter test mode (fans cycle, etc.). after i cut them and connected them back, i get the get kernel error, but it now enters into test mode. ive tried two different laptops lately and get the same thing.

by **Easyrider** » Wed Jan 02, 2008 5:40 pm

Sorry, Im all out of ideas now-maybe someone else has some ideas-Hope you get it sorted, anyhow,getting late now, im off to bed(1:40am here).

by **visualsinz** » Wed Jan 02, 2008 5:42 pm

thank you. i appreciate your help

openecu.org

Low Voltage Error- Tried everything

Low Voltage Error- Tried everything

Who is online