GM Reverse Engineering

[Tazzi]

Well makes sense why efilive/hptuners hardware is expensive. Its the price you pay to be able to do the work!

[VX L67 Getrag]

I finally had a little success with my elm327 1.5 today but gets about 9 lines of message & says buffers full but no where near it's limit, so been told it may be the elm not being able to keep up!

So can't wait for the real thing from antus once he gets his gear in!

[Tazzi]

I finally had a little success with my elm327 1.5 today but gets about 9 lines of message & says buffers full but no where near it's limit, so been told it may be the elm not being able to keep up!

So can't wait for the real thing from antus once he gets his gear in!

*sigh*.. Thats not good news mate! Looks like I might as well just run mine over with the car when it comes.

Iv read alot of people on Justcomms and other forums using elm cables with no trouble to get engine trouble codes and such. Are you using a generic obd2 software package? Could be how the data is being handled.. since all the cable should be doing is passing the data to the computer? Generally is the software that dictates the buffer size.

Try running serial port monitor on the cables port.. and see how much info is travelling though... Id be surprised if it was quite busy and had alot of chatter.

[antus]

Torque on android works pretty well.

[delcowizzid]

Ive got an elm and the only software i can get to connect is palmer perfomance stuff all th e freebies dont seem to woork

[VX L67 Getrag]

With just seeing data with OBDII isn't that simple as just serial port monitor, you need to tell the ELM or any interface commands for what to do hence why you need a terminal!

That coolterm program works pretty well so far apart from getting the error message so not sure if it's software or hardware but have a few ideas to try!

Not sure on the Torque & Android option,, but will be something else to learn & need to setup another PC for it!

EDIT: topic I have stumbled across & could be the answer...
http://www.mp3car.com/engine-management ... quest.html

[Tazzi]

With just seeing data with OBDII isn't that simple as just serial port monitor, you need to tell the ELM or any interface commands for what to do hence why you need a terminal!

That coolterm program works pretty well so far apart from getting the error message so not sure if it's software or hardware but have a few ideas to try!

Not sure on the Torque & Android option,, but will be something else to learn & need to setup another PC for it!

EDIT: topic I have stumbled across & could be the answer...
http://www.mp3car.com/engine-management ... quest.html

Yeah looks like hes getting the same problem. I dunno, just google obd2 software and try each one. See what works.. im sure half of them have trials, just need to see if it works.

But yea, the elm grabs the data which is then sends to your computer using the comport its installed on, should be able to simply chuck the serial monitor on and watch whats flowing through.

[Tazzi]

Still havent received the elm yet, not that it sounds like theres much hope, could be a matter of just needing to make my own logger and auto clear the buffer/read all buffer and store in array ect.

Back to tech2 logging.. anyone know what "Serial Data Bus Isolation - Cutoff" is/does? Its an output control in the bcm and its normally set to "normal". Im a bit hesitate to send it off in my car since it sounds like it messes with how the bcm communicates data. I figured it might turn the chatter off until turned back on? Kinda what happens with the mode8 but longer or until ignition turned off-on? Would make a damn good way to smash through entire module reads.

[VL400]

Its to isolate the bus in case of congestion, leaves just the BCM and PCM free to talk - all other modules can still talk amongst themselves but dont have the BCM (bus master) anymore. Pin 1 of the diagnostic connector is the second bus. The command will be controlling a relay in the BCM to link the two bus together.

[Tazzi]

Its to isolate the bus in case of congestion, leaves just the BCM and PCM free to talk - all other modules can still talk amongst themselves but dont have the BCM (bus master) anymore. Pin 1 of the diagnostic connector is the second bus. The command will be controlling a relay in the BCM to link the two bus together.

Ahhh... that sounds handy. So when changing it to "cut-off", all the chatter from all the other modules will be cutoff? Id imagine that would remove alot of the traffic.