Re: Memcal ID Tool with Data Version 1.10
Posted: Thu Oct 11, 2018 9:03 pm
made those bin id changes.
pcmhacking.net
Electronic Fuel Injection - Developement & Tuning
https://pcmhacking.net/forums/
Memcal ID Tool with Data Version 1.11
Page 12 of 13
Re: Memcal ID Tool with Data Version 1.10
Posted: Tue Apr 02, 2019 6:42 pm
Am I missing something, says it includes the bins and xdf files, can only see bins
Re: Memcal ID Tool with Data Version 1.10
Posted: Wed Apr 03, 2019 8:49 pm
no, ive fixed it now
Re: Memcal ID Tool with Data Version 1.10
Posted: Fri Nov 10, 2023 12:04 pm
Hey mate, can it identify Kalmaker bins?The1 wrote:no, ive fixed it now
Re: Memcal ID Tool with Data Version 1.10
Posted: Sat Jul 27, 2024 10:12 am
I just noticed the $5D ATFY VN V6 bin included with the memcal ID tool has a heap of extra data between 0x800 and 0x1000.
All the other $5D bins seem to show this area zeroed out.
The memcal ID tool also doesn't recognize the file when you try and ID it, but it recognizes all the other 5D files.
Is the file included there a bad copy?
All the other $5D bins seem to show this area zeroed out.
The memcal ID tool also doesn't recognize the file when you try and ID it, but it recognizes all the other 5D files.
Is the file included there a bad copy?
Re: Memcal ID Tool with Data Version 1.10
Posted: Sat Jul 27, 2024 2:08 pm
I dug through my delco collection and got super lucky. One of them had an ATFY memcal in it. I knew grabbing all those ECU's at the wreckers years ago would pay off one day 
It ID'ed successfully and read as an NEC UPD27C128.
The result is very different to the ATFY4410 file included in the "Data V1.02" zip.
ATFY is actually $A5 code, not $5D. Memcal ID tool identifies it successfully.
I've actually got no idea what the existing file in the ZIP even is, I cant work it out. I assume something that had been programmed onto a memcal by someone, and the sticker was never changed, so someone assumed it was still a standard memcal.
It ID'ed successfully and read as an NEC UPD27C128.
The result is very different to the ATFY4410 file included in the "Data V1.02" zip.
ATFY is actually $A5 code, not $5D. Memcal ID tool identifies it successfully.
I've actually got no idea what the existing file in the ZIP even is, I cant work it out. I assume something that had been programmed onto a memcal by someone, and the sticker was never changed, so someone assumed it was still a standard memcal.
- ATFYmemcal.png (657.71 KiB) Viewed 12125 times
Re: Memcal ID Tool with Data Version 1.10
Posted: Sat Jul 27, 2024 2:29 pm
Went though all my others while I was going.
Only other thing I found was the 4 numbers after CKUN (4122, currently listed as CKUN ???? on memcals.html)
Only other thing I found was the 4 numbers after CKUN (4122, currently listed as CKUN ???? on memcals.html)
- CKUN-4122.png (223.31 KiB) Viewed 12120 times
Re: Memcal ID Tool with Data Version 1.10
Posted: Sat Jul 27, 2024 6:11 pm
Cool thanks, I updated https://pcmhacking.net/memcals.html with that information.
Re: Memcal ID Tool with Data Version 1.10
Posted: Thu Dec 12, 2024 9:19 pm
Here's one not listed at all on memcals.html (CFYU):
It's from a 1997 VT 3.8 Auto.
Based on the description for the V8 CFYZ, this must be a "Pre-release", and probably an earlier version than CFYX that is listed.
I'll post up a bin when I get it (I asked to borrow it to read a copy, and it's in the mail).
Based on the description for the V8 CFYZ, this must be a "Pre-release", and probably an earlier version than CFYX that is listed.
I'll post up a bin when I get it (I asked to borrow it to read a copy, and it's in the mail).
Re: Memcal ID Tool with Data Version 1.10
Posted: Mon Dec 16, 2024 3:53 pm
Attached is the CFYU bin.
ID's as $A5C. I've compared to CJKU ("1st release", also $A5C).
All the differences that are defined appear to be traction control related. The "Traction control spark reduction" is full of FF values, so it looks like this was a pre-traction control calibration. The "Traction Control A/F Ratio" and "Available Torque vs Mode" are full of logical values, but they are different to the values in CJKU.
There's a handful of what seem to be tables that are different that aren't defined in the XDF.
There's also 3 bytes of variation outside of the calibration area: 1CDFE, 1CDFF, and 1CE00. This CFYU is "0x01, 0x01, 0x01". The "1st release" CJKU is "0xBD, 0xC8, 0xE4".
It seems 0x01 is HC11 machine code for NOP, and 0xBD is a jump instruction. So I'm guessing its just skipping over something (probably related to traction control?).
Technically I guess this is another variation of $A5
ID's as $A5C. I've compared to CJKU ("1st release", also $A5C).
All the differences that are defined appear to be traction control related. The "Traction control spark reduction" is full of FF values, so it looks like this was a pre-traction control calibration. The "Traction Control A/F Ratio" and "Available Torque vs Mode" are full of logical values, but they are different to the values in CJKU.
There's a handful of what seem to be tables that are different that aren't defined in the XDF.
There's also 3 bytes of variation outside of the calibration area: 1CDFE, 1CDFF, and 1CE00. This CFYU is "0x01, 0x01, 0x01". The "1st release" CJKU is "0xBD, 0xC8, 0xE4".
It seems 0x01 is HC11 machine code for NOP, and 0xBD is a jump instruction. So I'm guessing its just skipping over something (probably related to traction control?).
Technically I guess this is another variation of $A5