PCM Hammer Release 014

They go by many names, P01, P59, VPW, '0411 etc . Circa 1999 to 2006. All VPW OBD2 PCMs.
User avatar
Posts: 423
Joined: Fri Feb 02, 2018 3:13 pm

PCM Hammer Release 014

Postby NSFW » Fri Apr 17, 2020 7:22 pm

What's new in this release?

* The key thing was making the app reliable when used with the new ObdX Pro interfaces. I believe we've got everything straightened out now, and that's the interface I plan to use to flash my car from now on. It's much faster than the AllPro or ScanTool devices.

* The AllPro itself has also gotten much faster though (it accidentally got slower over the last few releases), and the ScanTool LX is a bit faster as well.

* Antus revised the way the kernel does CRC computation to prevent it from interfering with communications.

* Gampy fixed a couple issues in the UI and under the hood.


I've only tested with the interfaces listed above, so I'd love to hear confirmation from those of you with J2534 and AVT devices that those are still working well. :)
Attachments
PcmHammer014.zip
(1.92 MiB) Downloaded 283 times
Please don't PM me with questions about tuning or flashing - start a thread instead. Thanks!

Posts: 243
Joined: Mon Mar 09, 2020 4:35 pm
Location: California

Re: PCM Hammer Release 013 is ready for testing

Postby In-Tech » Fri Apr 17, 2020 9:51 pm

Read only, bench test.

AVT-852
[03:38:22:756] Read complete.
[03:38:22:787] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[03:38:22:803] We're not sure how much retrying is normal for a read operation on a 1024kb PCM.
[03:38:22:834] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[03:38:22:850] Starting verification...
[03:38:22:881] Calculating CRCs from file...
[03:38:22:928] Requesting CRCs from PCM...
[03:38:23:068] Range File CRC PCM CRC Verdict Purpose
[03:38:24:254] 0F0000-0FFFFF 8D0F8F91 8D0F8F91 Same OperatingSystem
[03:38:25:455] 0E0000-0EFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:38:26:640] 0D0000-0DFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:38:27:842] 0C0000-0CFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:38:29:027] 0B0000-0BFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:38:30:228] 0A0000-0AFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:38:31:414] 090000-09FFFF 7DA5C19F 7DA5C19F Same OperatingSystem
[03:38:32:615] 080000-08FFFF CDDEAE4C CDDEAE4C Same OperatingSystem
[03:38:33:801] 070000-07FFFF D006BDC7 D006BDC7 Same OperatingSystem
[03:38:35:002] 060000-06FFFF D2B04EC0 D2B04EC0 Same OperatingSystem
[03:38:36:188] 050000-05FFFF 36511E94 36511E94 Same OperatingSystem
[03:38:37:389] 040000-04FFFF F6B0E81A F6B0E81A Same OperatingSystem
[03:38:38:574] 030000-03FFFF A97E3395 A97E3395 Same OperatingSystem
[03:38:39:776] 020000-02FFFF EE1B7BAD EE1B7BAD Same OperatingSystem
[03:38:40:961] 010000-01FFFF 46111DB4 46111DB4 Same Calibration
[03:38:41:648] 008000-00FFFF 7CE23CE7 7CE23CE7 Same Calibration
[03:38:41:991] 006000-007FFF F3A109C9 F3A109C9 Same Parameter
[03:38:42:318] 004000-005FFF 85B5BB36 85B5BB36 Same Parameter
[03:38:42:771] 000000-003FFF AE42598F AE42598F Same Boot
[03:38:42:864] The contents of the file match the contents of the PCM.
[03:38:42:958] Clearing trouble codes.
[03:38:44:175] Clearing trouble codes.
[03:38:45:329] Elapsed time 00:04:40.8628933

VXDiag J2534
[03:49:22:699] Read complete.
[03:49:22:730] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[03:49:22:762] We're not sure how much retrying is normal for a read operation on a 1024kb PCM.
[03:49:22:777] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[03:49:22:808] Starting verification...
[03:49:22:840] Calculating CRCs from file...
[03:49:22:886] Requesting CRCs from PCM...
[03:49:22:980] Range File CRC PCM CRC Verdict Purpose
[03:49:24:306] 0F0000-0FFFFF 8D0F8F91 8D0F8F91 Same OperatingSystem
[03:49:25:616] 0E0000-0EFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:49:26:942] 0D0000-0DFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:49:28:300] 0C0000-0CFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:49:29:657] 0B0000-0BFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:49:30:967] 0A0000-0AFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:49:32:293] 090000-09FFFF 7DA5C19F 7DA5C19F Same OperatingSystem
[03:49:33:604] 080000-08FFFF CDDEAE4C CDDEAE4C Same OperatingSystem
[03:49:34:914] 070000-07FFFF D006BDC7 D006BDC7 Same OperatingSystem
[03:49:36:193] 060000-06FFFF D2B04EC0 D2B04EC0 Same OperatingSystem
[03:49:37:488] 050000-05FFFF 36511E94 36511E94 Same OperatingSystem
[03:49:38:798] 040000-04FFFF F6B0E81A F6B0E81A Same OperatingSystem
[03:49:40:109] 030000-03FFFF A97E3395 A97E3395 Same OperatingSystem
[03:49:41:404] 020000-02FFFF EE1B7BAD EE1B7BAD Same OperatingSystem
[03:49:42:730] 010000-01FFFF 46111DB4 46111DB4 Same Calibration
[03:49:43:447] 008000-00FFFF 7CE23CE7 7CE23CE7 Same Calibration
[03:49:43:697] 006000-007FFF 3B6FBD71 3B6FBD71 Same Parameter
[03:49:43:946] 004000-005FFF 85B5BB36 85B5BB36 Same Parameter
[03:49:44:352] 000000-003FFF AE42598F AE42598F Same Boot
[03:49:44:383] The contents of the file match the contents of the PCM.
[03:49:44:586] Clearing trouble codes.
[03:49:46:115] Clearing trouble codes.
[03:49:47:254] Elapsed time 00:05:08.4905418

OBDX_ProVT
[03:58:40:337] Read complete.
[03:58:40:368] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[03:58:40:383] We're not sure how much retrying is normal for a read operation on a 1024kb PCM.
[03:58:40:415] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[03:58:40:446] Starting verification...
[03:58:40:477] Calculating CRCs from file...
[03:58:40:524] Requesting CRCs from PCM...
[03:58:40:586] Range File CRC PCM CRC Verdict Purpose
[03:58:41:678] 0F0000-0FFFFF 8D0F8F91 8D0F8F91 Same OperatingSystem
[03:58:42:755] 0E0000-0EFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:58:43:831] 0D0000-0DFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:58:44:907] 0C0000-0CFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:58:45:984] 0B0000-0BFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:58:47:060] 0A0000-0AFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:58:48:137] 090000-09FFFF 7DA5C19F 7DA5C19F Same OperatingSystem
[03:58:49:213] 080000-08FFFF CDDEAE4C CDDEAE4C Same OperatingSystem
[03:58:50:289] 070000-07FFFF D006BDC7 D006BDC7 Same OperatingSystem
[03:58:51:366] 060000-06FFFF D2B04EC0 D2B04EC0 Same OperatingSystem
[03:58:52:442] 050000-05FFFF 36511E94 36511E94 Same OperatingSystem
[03:58:53:519] 040000-04FFFF F6B0E81A F6B0E81A Same OperatingSystem
[03:58:54:595] 030000-03FFFF A97E3395 A97E3395 Same OperatingSystem
[03:58:55:687] 020000-02FFFF EE1B7BAD EE1B7BAD Same OperatingSystem
[03:58:56:763] 010000-01FFFF 46111DB4 46111DB4 Same Calibration
[03:58:57:341] 008000-00FFFF 7CE23CE7 7CE23CE7 Same Calibration
[03:58:57:543] 006000-007FFF 7C926E2A 7C926E2A Same Parameter
[03:58:57:746] 004000-005FFF 85B5BB36 85B5BB36 Same Parameter
[03:58:58:074] 000000-003FFF AE42598F AE42598F Same Boot
[03:58:58:105] The contents of the file match the contents of the PCM.
[03:58:58:152] Clearing trouble codes.
[03:58:59:259] Clearing trouble codes.
[03:59:00:351] Elapsed time 00:04:20.8480581

OBDLinkSX
[04:30:11:623] Read complete.
[04:30:11:638] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[04:30:11:670] We're not sure how much retrying is normal for a read operation on a 1024kb PCM.
[04:30:11:701] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[04:30:11:716] Starting verification...
[04:30:11:748] Calculating CRCs from file...
[04:30:11:794] Requesting CRCs from PCM...
[04:30:11:982] Range File CRC PCM CRC Verdict Purpose
[04:30:14:571] 0F0000-0FFFFF 8D0F8F91 8D0F8F91 Same OperatingSystem
[04:30:17:176] 0E0000-0EFFFF A50F3C90 A50F3C90 Same OperatingSystem
[04:30:19:797] 0D0000-0DFFFF A50F3C90 A50F3C90 Same OperatingSystem
[04:30:22:387] 0C0000-0CFFFF A50F3C90 A50F3C90 Same OperatingSystem
[04:30:24:992] 0B0000-0BFFFF A50F3C90 A50F3C90 Same OperatingSystem
[04:30:27:644] 0A0000-0AFFFF A50F3C90 A50F3C90 Same OperatingSystem
[04:30:30:265] 090000-09FFFF 7DA5C19F 7DA5C19F Same OperatingSystem
[04:30:32:886] 080000-08FFFF CDDEAE4C CDDEAE4C Same OperatingSystem
[04:30:35:538] 070000-07FFFF D006BDC7 D006BDC7 Same OperatingSystem
[04:30:38:143] 060000-06FFFF D2B04EC0 D2B04EC0 Same OperatingSystem
[04:30:40:779] 050000-05FFFF 36511E94 36511E94 Same OperatingSystem
[04:30:43:384] 040000-04FFFF F6B0E81A F6B0E81A Same OperatingSystem
[04:30:45:990] 030000-03FFFF A97E3395 A97E3395 Same OperatingSystem
[04:30:48:595] 020000-02FFFF EE1B7BAD EE1B7BAD Same OperatingSystem
[04:30:51:200] 010000-01FFFF 46111DB4 46111DB4 Same Calibration
[04:30:53:134] 008000-00FFFF 7CE23CE7 7CE23CE7 Same Calibration
[04:30:54:710] 006000-007FFF 900ED67D 900ED67D Same Parameter
[04:30:56:239] 004000-005FFF 85B5BB36 85B5BB36 Same Parameter
[04:30:57:892] 000000-003FFF AE42598F AE42598F Same Boot
[04:30:57:924] The contents of the file match the contents of the PCM.
[04:30:58:080] Clearing trouble codes.
[04:30:59:281] Clearing trouble codes.
[04:31:00:451] Elapsed time 00:25:45.9783154

tactrix openport 2.0 J2534 device <<<<<<<<<<<<<<<<<<<<<<<<<<<Shows in drop down menu, Does not work
[04:37:03:451] PCM Hammer 013
[04:37:03:451] Loaded DLL
[04:37:08:989] VIN query failed: Timeout

Posts: 114
Joined: Thu Feb 13, 2020 11:32 pm

Re: PCM Hammer Release 013 is ready for testing

Postby ironduke » Fri Apr 17, 2020 10:21 pm

GM MDI (good clone)

[08:19:38:143] Read complete.
[08:19:38:161] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[08:19:38:185] We're not sure how much retrying is normal for a read operation on a 512kb PCM.
[08:19:38:201] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[08:19:38:217] Starting verification...
[08:19:38:236] Calculating CRCs from file...
[08:19:38:254] Requesting CRCs from PCM...
[08:19:38:327] Range File CRC PCM CRC Verdict Purpose
[08:19:40:639] 060000-07FFFF D5119D18 D5119D18 Same OperatingSystem
[08:19:42:963] 040000-05FFFF EDBD6276 EDBD6276 Same OperatingSystem
[08:19:45:277] 020000-03FFFF B98BA561 B98BA561 Same OperatingSystem
[08:19:47:045] 008000-01FFFF 0408C656 0408C656 Same Calibration
[08:19:47:262] 006000-007FFF 85B5BB36 85B5BB36 Same Parameter
[08:19:47:466] 004000-005FFF FC04B82E FC04B82E Same Parameter
[08:19:47:809] 000000-003FFF 023488D6 023488D6 Same Boot
[08:19:47:843] The contents of the file match the contents of the PCM.
[08:19:47:906] Clearing trouble codes.
[08:19:49:053] Clearing trouble codes.
[08:19:50:105] Elapsed time 00:02:22.4451301
[08:19:50:140] Saving contents to C:\Users\Owner\Documents\DIY ECM tuning\3.10.2020\P59 trials\4.17.2020.bench.read.pcmhammer.13.bin

Posts: 698
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer Release 013 is ready for testing

Postby Gampy » Sat Apr 18, 2020 12:42 am

Bum deal, taking time to test bit me this time.

v013 is useless to me (not that it matters, I build my own) ... SparkFun (STN1110)
[09:54:06:202] Reading from 32768 / 0x8000, length 1024 / 0x400
[09:54:06:202] TX: STPX H:6D10F0, R:1, D:35010400008000
[09:54:07:253] Empty response to STPX with data. That's not OK.
[09:54:07:253] Unable to send read request.
[09:54:07:254] Unable to read segment: Error
[09:54:07:254] TX: STPX H:6D10F0, R:1, D:35010400008000
[09:54:07:352] RX: 6D F0 10 36 01 04 00 00 80 00 ... Snipped
[09:54:07:361] Processing message
[09:54:07:363] 0x008000 3% 20:32
[09:54:07:382] Sending 'test device present' notification.
[09:54:07:382] Setting timeout for Minimum, 0 ms.
[09:54:07:383] TX: AT ST 01
[09:54:07:384] Did not recieve expected response. NO DATA does not equal OK
[09:54:07:385] TX: STPX H:8CFEF0, R:0, D:3F
[09:54:07:389] Setting timeout for ReadMemoryBlock, 50 ms.
[09:54:07:390] TX: AT ST 0C
[09:54:07:405] Did not recieve expected response. does not equal OK
[09:54:07:406] Reading from 33792 / 0x8400, length 1024 / 0x400
[09:54:07:406] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:08:489] Timeout during receive.
[09:54:08:489] No payload following read request.
[09:54:09:540] Timeout during receive.
[09:54:09:540] No payload following read request.
[09:54:10:592] Timeout during receive.
[09:54:10:592] No payload following read request.
[09:54:11:644] Timeout during receive.
[09:54:11:644] No payload following read request.
[09:54:12:696] Timeout during receive.
[09:54:12:696] No payload following read request.
[09:54:12:697] Unable to read segment: Error
[09:54:12:697] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:13:767] Timeout during receive.
[09:54:13:767] No payload following read request.
[09:54:14:819] Timeout during receive.
[09:54:14:819] No payload following read request.
[09:54:15:870] Timeout during receive.
[09:54:15:870] No payload following read request.
[09:54:16:922] Timeout during receive.
[09:54:16:922] No payload following read request.
[09:54:17:974] Timeout during receive.
[09:54:17:974] No payload following read request.
[09:54:17:975] Unable to read segment: Error
[09:54:17:975] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:19:048] Timeout during receive.
[09:54:19:048] No payload following read request.
[09:54:20:100] Timeout during receive.
[09:54:20:100] No payload following read request.
[09:54:21:152] Timeout during receive.
[09:54:21:152] No payload following read request.
[09:54:22:203] Timeout during receive.
[09:54:22:203] No payload following read request.
[09:54:23:255] Timeout during receive.
[09:54:23:255] No payload following read request.
[09:54:23:256] Unable to read segment: Error
[09:54:23:256] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:24:327] Timeout during receive.
[09:54:24:327] No payload following read request.
[09:54:25:378] Timeout during receive.
[09:54:25:378] No payload following read request.
[09:54:26:430] Timeout during receive.
[09:54:26:430] No payload following read request.
[09:54:27:482] Timeout during receive.
[09:54:27:482] No payload following read request.
[09:54:28:534] Timeout during receive.
[09:54:28:534] No payload following read request.
[09:54:28:535] Unable to read segment: Error
[09:54:28:535] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:29:606] Timeout during receive.
[09:54:29:606] No payload following read request.
[09:54:30:658] Timeout during receive.
[09:54:30:658] No payload following read request.
[09:54:31:709] Timeout during receive.
[09:54:31:709] No payload following read request.
[09:54:32:761] Timeout during receive.
[09:54:32:761] No payload following read request.
[09:54:33:813] Timeout during receive.
[09:54:33:813] No payload following read request.
[09:54:33:814] Unable to read segment: Error
[09:54:33:814] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:34:885] Timeout during receive.
[09:54:34:885] No payload following read request.
[09:54:35:937] Timeout during receive.
[09:54:35:937] No payload following read request.
[09:54:36:989] Timeout during receive.
[09:54:36:989] No payload following read request.
[09:54:38:040] Timeout during receive.
[09:54:38:040] No payload following read request.
[09:54:39:092] Timeout during receive.
[09:54:39:092] No payload following read request.
[09:54:39:093] Unable to read segment: Error
[09:54:39:093] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:40:164] Timeout during receive.
[09:54:40:164] No payload following read request.
[09:54:41:216] Timeout during receive.
[09:54:41:216] No payload following read request.
[09:54:42:268] Timeout during receive.
[09:54:42:268] No payload following read request.
[09:54:43:320] Timeout during receive.
[09:54:43:320] No payload following read request.
[09:54:44:371] Timeout during receive.
[09:54:44:371] No payload following read request.
[09:54:44:372] Unable to read segment: Error
[09:54:44:372] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:45:443] Timeout during receive.
[09:54:45:443] No payload following read request.
[09:54:46:494] Timeout during receive.
[09:54:46:494] No payload following read request.
[09:54:47:546] Timeout during receive.
[09:54:47:546] No payload following read request.
[09:54:48:598] Timeout during receive.
[09:54:48:598] No payload following read request.
[09:54:49:650] Timeout during receive.
[09:54:49:650] No payload following read request.
[09:54:49:651] Unable to read segment: Error
[09:54:49:651] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:50:722] Timeout during receive.
[09:54:50:722] No payload following read request.
[09:54:51:774] Timeout during receive.
[09:54:51:774] No payload following read request.
[09:54:52:826] Timeout during receive.
[09:54:52:826] No payload following read request.
[09:54:53:877] Timeout during receive.
[09:54:53:877] No payload following read request.
[09:54:54:929] Timeout during receive.
[09:54:54:929] No payload following read request.
[09:54:54:930] Unable to read segment: Error
[09:54:54:930] TX: STPX H:6D10F0, R:1, D:35010400008400
[09:54:56:001] Timeout during receive.
[09:54:56:001] No payload following read request.
[09:54:57:053] Timeout during receive.
[09:54:57:053] No payload following read request.
[09:54:58:105] Timeout during receive.
[09:54:58:105] No payload following read request.
[09:54:59:157] Timeout during receive.
[09:54:59:157] No payload following read request.
[09:55:00:208] Timeout during receive.
[09:55:00:208] No payload following read request.
[09:55:00:209] Unable to read segment: Error
[09:55:00:209] Unable to read block from 33792 to 34815
[09:55:00:230] Halting the kernel.
[09:55:00:233] TX: STPX H:6C10F0, R:1, D:20
[09:55:00:265] Clearing trouble codes.
[09:55:00:285] Setting timeout for Minimum, 0 ms.
[09:55:00:285] TX: AT ST 01
[09:55:00:293] OK
[09:55:00:544] TX: STPX H:686AF0, R:1, D:04
[09:55:00:816] TX: STPX H:686AF0, R:1, D:04
[09:55:01:088] TX: STPX H:8CFEF0, R:1, D:14
[09:55:01:360] TX: STPX H:8CFEF0, R:1, D:14
[09:55:01:381] Elapsed time 00:01:44.2832031
[09:55:01:401] Read failed, Error

If it does succeed (1 out of 10 tries) there are 400-500 retries.

ScanToolDeviceImplementation.cs - GetTimeoutMilliseconds()
Code: Select all
                    case TimeoutScenario.ReadMemoryBlock:
-                        milliseconds = 50;
+                        milliseconds = 95;
At a minimum!
Temporary is a permanent problem!

User avatar
Posts: 423
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer Release 013 is ready for testing

Postby NSFW » Sat Apr 18, 2020 5:07 am

Is it reliable with that timeout increased to 95ms?
I'm fine with making that change before the "real" release (Github's release page, threads on other forums, etc).
Please don't PM me with questions about tuning or flashing - start a thread instead. Thanks!

Posts: 698
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer Release 013 is ready for testing

Postby Gampy » Sat Apr 18, 2020 5:36 am

Oh, heck yea!

Actually, I would bump it to 100.
At 95 there are still consistent retries on Intel based units. At 100 I have yet to see any retries in 11 reads so far, 6 on Amd units, 5 on Intel, another Intel is running now ...

Yup, the Intel seems a bit slower then the AMD.
Temporary is a permanent problem!

User avatar
Posts: 423
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer Release 013 is ready for testing

Postby NSFW » Sat Apr 18, 2020 5:38 am

In-Tech wrote:Read only, bench test.
tactrix openport 2.0 J2534 device <<<<<<<<<<<<<<<<<<<<<<<<<<<Shows in drop down menu, Does not work
[04:37:03:451] PCM Hammer 013
[04:37:03:451] Loaded DLL
[04:37:08:989] VIN query failed: Timeout


Has the OpenPort worked with any other version of PCM Hammer?

I have heard that the OpenPort supports VPW, but when I asked Tactrix via email I was told that it doesn't.
Please don't PM me with questions about tuning or flashing - start a thread instead. Thanks!

User avatar
Posts: 423
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer Release 013, no, 014 is ready for testing

Postby NSFW » Sat Apr 18, 2020 5:57 am

Zip file replaced, thread title updated.
All of the previous testing is still valid, this change was very small and very safe.
Please don't PM me with questions about tuning or flashing - start a thread instead. Thanks!

Posts: 698
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer Release 013, no, 014 is ready for testing

Postby Gampy » Sat Apr 18, 2020 6:52 am

Round one with v014.

Zero retries on Intel (1m) read ... AMD up next.

The last writes I did were at code base 456a69c, and I only did a few (3 or 4) writes (on both Intel and AMD), However, I don't believe anything has changed that should make a difference. They did go perfect!

[edit] Zero retries on AMD read ...
Temporary is a permanent problem!

Posts: 114
Joined: Thu Feb 13, 2020 11:32 pm

Re: PCM Hammer Release 013, no, 014 is ready for testing

Postby ironduke » Sat Apr 18, 2020 8:29 am

With version 14. GM MDI again but 1mb ecm..

[06:25:41:915] Read complete.
[06:25:41:934] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[06:25:41:958] We're not sure how much retrying is normal for a read operation on a 1024kb PCM.
[06:25:41:977] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[06:25:41:996] Starting verification...
[06:25:42:018] Calculating CRCs from file...
[06:25:42:046] Requesting CRCs from PCM...
[06:25:42:115] Range File CRC PCM CRC Verdict Purpose
[06:25:44:373] 0E0000-0FFFFF A873B6D7 A873B6D7 Same OperatingSystem
[06:25:46:598] 0C0000-0DFFFF 807305D6 807305D6 Same OperatingSystem
[06:25:48:871] 0A0000-0BFFFF 807305D6 807305D6 Same OperatingSystem
[06:25:51:098] 080000-09FFFF CA3CB0F4 CA3CB0F4 Same OperatingSystem
[06:25:53:341] 060000-07FFFF 9A433D6B 9A433D6B Same OperatingSystem
[06:25:55:552] 040000-05FFFF 635F236F 635F236F Same OperatingSystem
[06:25:57:821] 020000-03FFFF 9667FFB0 9667FFB0 Same OperatingSystem
[06:25:59:512] 008000-01FFFF 1A17694F 1A17694F Same Calibration
[06:25:59:723] 006000-007FFF 85B5BB36 85B5BB36 Same Parameter
[06:25:59:924] 004000-005FFF B0279E47 B0279E47 Same Parameter
[06:26:00:264] 000000-003FFF 6A096F07 6A096F07 Same Boot
[06:26:00:282] The contents of the file match the contents of the PCM.
[06:26:02:347] Clearing trouble codes.
[06:26:11:531] Clearing trouble codes.
[06:26:12:595] Elapsed time 00:04:38.0491065

Next

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: No registered users and 3 guests