[ATPCR]

I have a question for those of you that have worked in Binary Editor with the RAAD4,1998 and READ0 1999 to 2001 Explorer 5.0 pcms. I would like to know the pcm clock speeds of the two different strategies. Thanks in advance for the information.

[jsa]

Post the bin files.

[ATPCR]

@jsa The RAAD bin file is 224k.

RAAD4 98Explorer5.0AWD F87FAVB_RAAD3G5-20240620-135024.bin

(224 KiB) Downloaded 198 times

So is the READ0 file.

Ken stock 1999mm awd 5.0 XU7AAFA_READ0A7-20240228-143158 (1).bin

(224 KiB) Downloaded 211 times

I'm not currently a BE user so I'm unable to look at them in TunerPro because definition files do not exist yet.
I'm guessing that they need to be converted to 256k too to look at them in BE.
Thanks John, Greg

[jsa]

Greg,

Definition files would be required for both BE and TP, and the author would need to have included the XTALHPS scalar.

No they do not need to be converted to 256kb for BE.

As the there is no definition at hand with XTALHPS included, I've used SAD to disassemble the bins and compared to a previously disassembled RZASA bin with a known XTALHPS location. I've looked for where the RAM Pointers are setup and identified XTALHPS afterwards.

RZASA

Code: Select all

126ea: 08                 byte      8            XTALHPS_27
.
.
823bc: a1,80,16,ec        ldw   Rec,1680         RP16 = 1680;
823c0: b3,f4,04,34        ldb   R34,[Rf4+4]      TMP1L = XTALHPS_27;               # [126EA] 0x8
823c4: a1,66,ac,46        ldw   R46,ac66         TMP0L = S.0x1AC66;
823c8: b3,f4,05,36        ldb   R36,[Rf4+5]      TMP2L = SPI_BIT_TRANSFER_RATE24;
823cc: 99,06,34           cmpb  R34,6            

READ0

Code: Select all

1258e: 06                 byte      6            XTALHPS_24
.
.
823fe: a1,80,16,ee        ldw   Ree,1680         Ree = 1680;
82402: a1,56,77,46        ldw   R46,7756         TMP0L = 7756;
82406: b3,f4,05,36        ldb   R36,[Rf4+5]      TMP2L = [1258f];
8240a: b3,f4,04,34        ldb   R34,[Rf4+4]      TMP1L = XTALHPS_24;               # [1258E] 0x6
8240e: 99,02,34           cmpb  R34,2

RAAD4

Code: Select all

12646: 02                 byte      2            XTALHPS_18
.
.
82400: a1,80,16,ee        ldw   Ree,1680         Ree = 1680;
82404: a1,b0,76,46        ldw   R46,76b0         R46 = 76b0;
82408: b3,f4,05,36        ldb   R36,[Rf4+5]      R36 = [12647];
8240c: b3,f4,04,34        ldb   R34,[Rf4+4]      R34 = XTALHPS_18;               # [12646] 0x2
82410: 99,02,34           cmpb  R34,2            

Once the XTALHPS value is found, apply this formula to it for the clock speed.

Code: Select all

(X/2*3+15)

READ0 is 24MHz
RAAD4 is 18MHz

[ATPCR]

Thanks, John, for taking the time to check these bin files out using your SAD abilities. I'm in discussions with another Explorer friend about having definition files developed for '98 RAAD and '99 to '01 READ0 for TunerPro. And thanks for answering a question for me August 4th, 2024, on another forum. I'm in talks too about the def files development.
Last week, I PCMflashed with my "Spanish" Scanmatik and Oleg's module #29 the READ0 file into a pcm meant for the RAAD files and there was a very noticeable idle speed difference. All that I could think of was that the pcm clock speeds must be different.
The stock '99 Ex/MM 5.0 was running at 750 rpms and with the READ0 bin file flashed into the '98 with the slower clock speed, the idle rpm was 600. I was assuming that the reason why was a clock speed difference. I didn't go forward with any other testing and put things back the way that they were stock.
But the pcm clock speeds seem to have a marked effect.

[jsa]

Boostedeverything on the other forum, has been working on READ0 which has been labelled as EQE3. It'd be worth contacting him to see what he's willing to share.

All the time dependant actions would be screwed running 24MHz code on an 18MHz box. Surprising it even ran at all.

[ATPCR]

I didn't feel like a test drive was even a good idea after the noticeable idle change. There was no safe place to do a test drive and pull over in an emergency. The next thought was, what was it doing to fuel pressure? My fuel pressure gauge is broken so I was unable to check that. I won't do any more cross "hardware code" experiments.