The engine was off. I had the ignition on and SManager showed that the ecu was online. I had just downloaded a datalog file from the ecu, when I noticed everything going haywire. Every sensor changed on its own and all the ecu codes came and went at random.
has anyone seen this before? what could this mean?
What the heck is going on with this datalog file?!!!!
What the heck is going on with this datalog file?!!!!
You do not have the required permissions to view the files attached to this post.
Bad news...
I uploaded my tune from this computer again, and I am getting odd readings still. This file was with the motor idling.
Could these readings be bad because the voltage is below 12v?
How can I test the ECU to verify that it and the S300 are ok?
the car runs fine at idle, so all this is not making any sense.
In case it helps, I have included my calibration also.
I uploaded my tune from this computer again, and I am getting odd readings still. This file was with the motor idling.
Could these readings be bad because the voltage is below 12v?
How can I test the ECU to verify that it and the S300 are ok?
the car runs fine at idle, so all this is not making any sense.
In case it helps, I have included my calibration also.
You do not have the required permissions to view the files attached to this post.
serial #
I will try and locate the box that the S300 came in when I go back to my parents house. If I can not find the box, is there another way to find out the serial number?
I will check the voltage again, but what is happening is, at idle the voltage is 12v, not 14v. It is not jumping around like the datalog is representing... So, what could cause the datalog to be screwy?
I am putting my ECU / S300 into a GSR today with a P72 base map and see if there are any problems present there. If it runs fine, I will try and swap the relay and test again. What other electrical things should be checked? It is a brand new Acura Alternator, and the battery is new as well, and tests good.
I will check the voltage again, but what is happening is, at idle the voltage is 12v, not 14v. It is not jumping around like the datalog is representing... So, what could cause the datalog to be screwy?
I am putting my ECU / S300 into a GSR today with a P72 base map and see if there are any problems present there. If it runs fine, I will try and swap the relay and test again. What other electrical things should be checked? It is a brand new Acura Alternator, and the battery is new as well, and tests good.
It might have helped if you had given us the same information you had posted on Honda-Tech. Since the ECU is fine in another car, the problems has to do with the wiring and electronics in your car. At this point I would suggest taking the car to an Acura dealer to have them help diagnose and correct the problem.ITR 1102 wrote:Long story short,
a coworker changed out my battery and in the process grounded the crap out of it to the point that sparks went flying and some smoke came up.
We tested the alternator and the output was not acceptable, so I got a new one from Acura. This was installed over the weekend. The car runs fine on the street, however this weekend was supposed to be spent on the track. After the car had seen about 4 to 5 laps on the track the motor would cut out for a few seconds and then come back online (either full power or nothing)
We basically figured this has to be the distributor, so I have a new Distributor King on the way. Problem now is, sitting at a traffic light yesterday at idle and the AC on, the battery light started flickering / coming and going, but the idle did not change any.
What else needs to be checked or replaced? Could a relay have been damaged, or what else could have been effected by the grounding out?
I pulled the datalog from the ecu from when it was acting up, and there were only a few very brief voltage drops (14 to 12), but that could have been due to the AC cycling on.
Help me out guys
I guess that would have helped. I posted that on three different forums, and I forgot to put it in this thread. :roll:
I am waiting to hear back from the insurance claim adjuster to tell me what they are going to do for me (at my work, not my personal insurance).
I checked the voltage at the battery, and all of the grounds. With the car off it is 12.7 and at idle it is 14.3
I have not had a chance to check any of the voltage readings at the ecu wire harness yet. I still need to look up in the helms and figure out which wires on the OBD1 conversion harness to use.
IF YOU HAVE A DIAGRAM AS TO WHICH WIRES I NEED TO CHECK THE VOLTAGE OF AT THE ECU, COULD YOU PLEASE POST IT?
Thanks
p.s. could the distributor issue cause any of these odd readings? The new one won't be delivered until tomorrow.
I am waiting to hear back from the insurance claim adjuster to tell me what they are going to do for me (at my work, not my personal insurance).
I checked the voltage at the battery, and all of the grounds. With the car off it is 12.7 and at idle it is 14.3
I have not had a chance to check any of the voltage readings at the ecu wire harness yet. I still need to look up in the helms and figure out which wires on the OBD1 conversion harness to use.
IF YOU HAVE A DIAGRAM AS TO WHICH WIRES I NEED TO CHECK THE VOLTAGE OF AT THE ECU, COULD YOU PLEASE POST IT?
Thanks
p.s. could the distributor issue cause any of these odd readings? The new one won't be delivered until tomorrow.
Fixed
I just wanted to let everyone know that the problem has been resolved.
There was nothing wrong with my car. The problem was that onboard datalogging was enabled, and I was using the laptop to datalog at the same time.
I did some tests and found that I can use one or the other, but as soon as both are used simultaneously, I immediately get crazy readings.
Matt,
is this a known or common problem, or am I the first to report such an issue? It is not too big of a problem regardless because if you are datalogging through the laptop then there is no reason to use the onboard, and vice versa. If you can duplicate this on your own vehicles, perhaps there should be a notice or warning in the datalogging section in SManager
There was nothing wrong with my car. The problem was that onboard datalogging was enabled, and I was using the laptop to datalog at the same time.
I did some tests and found that I can use one or the other, but as soon as both are used simultaneously, I immediately get crazy readings.
Matt,
is this a known or common problem, or am I the first to report such an issue? It is not too big of a problem regardless because if you are datalogging through the laptop then there is no reason to use the onboard, and vice versa. If you can duplicate this on your own vehicles, perhaps there should be a notice or warning in the datalogging section in SManager
Thank you for the update.
This is known, but you stated that you tried it in another vehicle without any problems, so this based on the earlier problems indicated that it was not a problem with the s300.
When in doubt it is also a good idea to not use your same calibration when trouble shooting. It is a good idea to create a new calibraiton to eliminate other posibilities.
You can see how this was a difficult issue to find from both sides. Hindsight is always 20/20.
This is known, but you stated that you tried it in another vehicle without any problems, so this based on the earlier problems indicated that it was not a problem with the s300.
When in doubt it is also a good idea to not use your same calibration when trouble shooting. It is a good idea to create a new calibraiton to eliminate other posibilities.
You can see how this was a difficult issue to find from both sides. Hindsight is always 20/20.