pcmhacking.net

Gampy wrote:Thank you!

bill12690 wrote:[06:33:29:453) Kemel Version: 01030500

Interesting ...

My apologies, I noticed an error in my previous message and edited it accordingly. The kernel version should be 0103050C. Image to text conversion failure on my part!

Oh, ok ... Are you aware there are multiple ways to save PCM Hammers logs as text files ...

1. File, Save ...
2. Options, Settings, Log, Save on exit ...
3. Click in the displayed text box and copy by either of the following two techniques ...
. . Right Click, Select All, Right Click Copy
Or
. . Ctrl-A, Ctrl-C
And
. . Paste into Notepad, and save as ...

Then you can attach them via the 'Upload Attachment' process here on the PcmHacking website.
While in the Post Editor (Not Quick Reply), look to the lower left,
Select: Upload Attachment
Select: Browse
. Browse to the Log file you saved and select it.
Select: Open

Select: Add The File

-Enjoy

Gampy wrote:Oh, ok ... Are you aware there are multiple ways to save PCM Hammers logs as text files ...

1. File, Save ...
2. Options, Settings, Log, Save on exit ...
3. Click in the displayed text box and copy by either of the following two techniques ...
. . Right Click, Select All, Right Click Copy
Or
. . Ctrl-A, Ctrl-C
And
. . Paste into Notepad, and save as ...

Then you can attach them via the 'Upload Attachment' process here on the PcmHacking website.
While in the Post Editor (Not Quick Reply), look to the lower left,
Select: Upload Attachment
Select: Browse
. Browse to the Log file you saved and select it.
Select: Open

Select: Add The File

-Enjoy

I have since been copying and pasting the log files manually, I just didn't happen to in that particular case for some reason, but I had snapped a picture with my phone to find an XDF later based off the OSID. Oversight on my.part, but have been saving them straight from PCM Hammer ever since!

another failed write ugh. i have 0 issues with the power supply im using when writing directly to the chips so i doubt thats the smoking gun :/

spyder09 wrote:another failed write ugh. i have 0 issues with the power supply im using when writing directly to the chips so i doubt thats the smoking gun :/

Just because it works with a programmer does not mean it's good for a VCI, and every different VCI design will react differently to the quality of power delivered.

It's more about the level/quality of power conditioning and fault tolerances in the individual VCI.
Wiring also plays a big role ... We had a user that was constantly getting failures, until he rearranged the cables on his bench.

Not saying it is for sure a power issue ...

-Enjoy

Gampy wrote:

spyder09 wrote:another failed write ugh. i have 0 issues with the power supply im using when writing directly to the chips so i doubt thats the smoking gun :/

Just because it works with a programmer does not mean it's good for a VCI, and every different VCI design will react differently to the quality of power delivered.

It's more about the level/quality of power conditioning and fault tolerances in the individual VCI.
Wiring also plays a big role ... We had a user that was constantly getting failures, until he rearranged the cables on his bench.

Not saying it is for sure a power issue ...

-Enjoy

I will order another power supply tonight but was able to write one just now without issues, tried the same PCM again that failed before was able to read it out, but not write to it still fails on erase flash

see attachment

attaching new debug file

fyi attempted to flash 4 different ones in a row. was able to read each out without issues, first 3 failed to write (all 3 seemed to be 12597978 OS on the pcm) all failing as soon as it tries to erase flash. Last one was a different OS 12605261 and was able to flash successfully

I see the OBDXPro doesn't report voltage, nor does it report what it receives (No RX: lines) ...

The OS version has nothing to do with failures, just coincidence, what could correlate is the hardware number.

-Enjoy

Gampy wrote:I see the OBDXPro doesn't report voltage, nor does it report what it receives (No RX: lines) ...

The OS version has nothing to do with failures, just coincidence, what could correlate is the hardware number.

-Enjoy

I might need to update the OBDX pro routines to output voltage and decoded rx line. Will make it easier for debugging.