pcmhacking.net

tek1229 wrote:Hey there, Felt like I should be saying hi here..

I have been tinkering with elm327 devices for a bit, starting with my 04 S10 and learning how to interface one with an arduino for a fan controller, later on I wrote some code for vpw right on the arduino..

Now many years later I have upgraded my main ride to a 13 silverado, played with that a little but the high speed CAN is busy!! Started out doing some googling and I found this site, and this forum..

Bravo!!!! I imagine I will be emaiing Tazzi shortly looking to try out his kewl new program..

If it helps anyone I do have a Tech 2, a GM MDI, and access to gm technician information.. Gotta admit though, this deep it isn't a whole lotta help usually..

Just been reading 20 pages or so, started getting crosseyed so bookmarking this site and calling it a nite...

Thanks again, I hope to be able to get some info from here and also hand out some of my own.. Tom- Tek1229...

Sounds like your a bit tech savy so you should pickup on CAN easily

Unfortunately a tech2,MDI and even access to GM SI isnt too much help these days unless you able to reverse engineer the data.

So I logged the VE SS while driving to the shops and back.

Interesting the Left/Right O2 sensor PID readings that the LS1's use output some interesting results, alot of movement going on there. And Im not sure how those two readings compare to the SAE Bank1/2 sensor 1/2 readings.
Also, with so many PID's being logged, SOE was logging at a cruisey 130frames/second.

But the SS also uses Bank 1 and 2 + Sensor 1 and 2

Attached are a couple logs. They maaaaaay not work on the version currently available (v0.0.1.5a), I am about to update v0.0.1.5b in a moment
Log one (To Shops) has the following PIDs to flick between:
-Coolant Temperature
-B1 Short term fuel trim
-B1 LTFT cruise acceleration
-B2 short term fuel trim
-B2 LTFT cruise acceleration
-Engine RPM
-Engine Speed
-Spark advance
-Intake Air temperature
-Mass air flow
-Throttle position
-Right O2 Sensor
-Left O2 Sensor

Log two (Back home)
--Coolant Temperature
-B1 Short term fuel trim
-B1 LTFT cruise acceleration
-B2 short term fuel trim
-B2 LTFT cruise acceleration
-Engine RPM
-Engine Speed
-Spark advance
-Intake Air temperature
-Mass air flow
-Throttle position
-Bank1 O2 sensor 1
-Bank1 O2 sensor 2
-Bank2 O2 sensor 1
-Bank2 O2 sensor 2
-Requested Torque
-Knock Retard

Also note, that when replaying the data, the data is played back a little bit slower then "normal time", this is because the graphing feature actually "re-adds" all data points each time which takes alot of processing.

*Edit
Cant upload the files due to their extensions, I have just popped them into a .rar. Just extract and open

Thats v0.0.1.5b now up and going.
Loads the above logs without any trouble from my laptop.

Next to complete is:
- Finish "update check" routine.
- Add trans detected property to fault read/engine read so when its not detected at beginning these two functions are disabled.

Future additions:
-Retry the freeze data implementation (routines still there.. just not turned on)
-MX WIFI support
-AVT Support

And thats about it I think!

Updating feature has now been implemented
Will automatically detect if an update is available.

Will be pushing this update into mainstream soon.

Sounding good, will try and have a play with it on the weekend.

v0.0.1.6 has now been released mainstream.

All updates can now be automatically downloaded once available!

*Edit
And those logs I posted above should replay perfectly.

Some little things to sort out in the next update. Iv found that because Im recording so quickly in the VE SS, that Im clocking over 130ish frames/sec which is alot of data to process and display on the gauges. After a little bit (Depending on computer speed) there is a bit of lag between what is displayed and whats currently happening the laptop cannot process the data quick enough! Otherwise I have to do some extreme threading delegating and each gauge gets its own processing thread.. although this will probably clock the computer to its full processing power.

So the plan here, is to optimize the data displayed. All the engine data will be logged so it can be all replayed. But I will make the application only update the visual gauges ~30frames per second rather than the full 140+. This setting will be adjustable, but Im hoping that it will significantly increase performance especially on any slightly slower/older laptops.

Things on the to-do list:
1. Optimizing, and reducing the "frames/sec" displayed on the gauges. So the plan here, is that all data will be added to the "graphing", but only updated when that tab is selected. And also only displaying ~30frames/sec

2. The "replay PIDs" and "Live engine PIDs" need to be reloaded between each use. Eg.. replayed data.. then selected live engine data.. then it will need to be reloaded again if wanting to replay data.

3. Some new engine fault codes I obtained for the VE SS that I will be implementing.

4. New engine engine and transmission data from the VE SS

5. Attempt to re-implement the freeze data in the "fault codes" section.

Hi, I updated to v0.0.1.6 last night, now I'm getting a "Startup processing error has occured. Please contact support for help!"

Dave001 wrote:Hi, I updated to v0.0.1.6 last night, now I'm getting a "Startup processing error has occured. Please contact support for help!"

From what version did you update from?
I might have to roll back to that version and see whats happening.

Will send through another license to see if that resolves the matter

Sorted!
Computer had been modified which affected the licensing.

Enjoy Dave!