pcmhacking.net

I only downloaded it a few mins before posting that, but tried again and its still F5 when reading engine data (freeze frame and faults work).

VL400 wrote:I only downloaded it a few mins before posting that, but tried again and its still F5 when reading engine data (freeze frame and faults work).

Thats reeeaaally Odd...
I just reuploaded it again but its the same file I think.

Coding for selecting which frame to fire off is:
ElseIf ConnectedVehicleType = SupportedVehicles.VSV6 Then
ReadFrameEngine = {&HF5, &H57, &H1, &H0, &HB3}
ReadFrameTrans = {&HF5, &H57, &H1, &H3, &HB0}
ElseIf ConnectedVehicleType = SupportedVehicles.VR Or ConnectedVehicleType = SupportedVehicles.VSS12V8 Then
ReadFrameEngine = {&HF4, &H57, &H1, &H0, &HB4}
ReadFrameTrans = {&HF4, &H57, &H1, &H4, &HB0}


No reason why it is getting the F5.
I did the test on the bench and it definitely picks up the correct engine/trans frames when selecting VR or VS S1/2 V8

Tried a fresh install and still F5 on only the engine data, it connects, gets freeze frame and current errors using F4.

VL400 wrote:Tried a fresh install and still F5 on only the engine data, it connects, gets freeze frame and current errors using F4.

I have absolutely no idea why its doing that!!
When I step through the code.. it sets the ID's as F4.... hmmm

I cannot figure it out why its sending F5 instead of F4. While stepping through the code its setup as F4, and then if monitoring with another cable it fires of F4.. so Im not sure whats happening when doing a final build!

So plan of attack, is to completely rip out that section of code and re-write it. Hopefully will have v0.0.0.3 out and ready for testing soon.

Just a thought. I just downloaded AEDInstaller.exe again from page 10 a short time ago and it's still displaying Product Version: 0.0.0.1 in the About section. I assumed the current download version would be 0.0.0.2 as you mention above you will have v0.0.0.3 out and ready for testing soon. Could this be why VL400 still sees F5 when reading engine data? Maybe new update not happening.

My recent new download has not solved my "Did not detect any raw data from vehicle" linking problem with all my bench ECM/PCMs. It will eventually link if all the ticks are removed in the settings boxes but still see no data on screen.
Looks like your application is looking for a heart beat which my bench ECM/PCMs are not providing as none have BCMs attached.

Tried both versions again. In V0001 it gets the unknown error when selecting manual, auto it logs ok. You can select auto on a manual ECU and the trans frame is a bunch of 0 data, and selecting manual with an auto PCM you should just get engine data.
Console View
Waiting for next command...
[14:42:11:721] Attempting to Connect to Comport...
[14:42:11:753] Searching for Device...
[14:42:11:768] Beginning device connection..!
[14:42:11:768] Finding ALDL Device
[14:42:11:784] Device Found
[14:42:11:784] Detecting ECU Prescence
[14:42:12:175] Connection Established
[14:42:16:171] Reading Faults..
[14:42:16:405] Processing Data!
[14:42:16:577] Completed, Faults Processed!
[14:42:19:562] Reading Freeze Data
[14:42:23:743] Reading Engine Data..
[14:42:25:242] Unknown Error Occurred!
[14:42:26:900] Reading Engine Data..

Serial port monitor log, what a pain with win7 and win8 64bit. Nothing like good old portmon under winxp, so if you have another license can use that in future.
f4 57 01 00 b4
f4 57 01 00 b4
f4 57 01 03 b1
f4 57 01 00 b4
f4 57 01 00 b4
f4 57 01 04 b0
f4 57 01 00 b4
f4 57 01 04 b0
f4 57 01 00 b4
f4 57 01 04 b0
f4 57 01 00 b4
f4 57 01 04 b0
f4 57 01 00 b4
f4 57 01 04 b0
f4 57 01 00 b4
f4 57 01 04 b0



And the same with V0002 Console View
Waiting for next command...
[14:46:46:797] Attempting to Connect to Comport...
[14:46:46:844] Searching for Device...
[14:46:46:859] Beginning device connection..!
[14:46:46:859] Finding ALDL Device
[14:46:46:875] Device Found
[14:46:46:875] Detecting ECU Prescence
[14:46:47:281] Connection Established
[14:46:50:844] Reading Faults..
[14:46:55:615] Processing Data!
[14:46:55:740] Completed, Faults Processed!
[14:46:58:508] Reading Freeze Data
[14:47:04:076] Reading Engine Data..
[14:47:06:691] Comport timed out! No data detected at all
[14:47:06:691] No response.. retrying..
[14:47:07:160] Comport timed out! No data detected at all
[14:47:07:176] No response.. retrying..
[14:47:07:645] Comport timed out! No data detected at all
[14:47:07:660] Retry limit reached, Did not detect engine data response!
[14:47:12:075] Reading Engine Data..
[14:47:13:565] Comport timed out! No data detected at all
[14:47:13:565] No response.. retrying..
[14:47:14:034] Comport timed out! No data detected at all
[14:47:14:034] No response.. retrying..
[14:47:14:503] Comport timed out! No data detected at all
[14:47:14:503] Retry limit reached, Did not detect engine data response!


f4 57 01 00 b4
f4 57 01 00 b4
f4 57 01 03 b1
f5 57 01 00 b3
f5 57 01 00 b3
f5 57 01 00 b3
f5 57 01 00 b3
f5 57 01 00 b3
f5 57 01 00 b3

VL400 wrote: Serial port monitor log, what a pain with win7 and win8 64bit. Nothing like good old portmon under winxp, so if you have another license can use that in future.

I find accessport is really good for 64 bit on both win8 and win7

Alright so I have checked multiple times, even with a second cable to monitor the line and its definitely sending F4,57,01,00,B4 now.

So to fix up getting any 'invalid' frames, Im re-initializing the multiple threading for the data processing. Before the data is chucked into the gauges, Im going to make it check frame length and also validate checksum. This should get rid of any expecting errors that happened before.

Ohhhhhhhhh I think I know whats causing the errors maybe... since if no transmission data is read out. When it gets passed through one of the functions to process data. It is expecting a byte array.. which is not present since no data has been read!

Alright.. lets fix that little error up!