Mazda As-Built data layout

Any issues related to FORScan application
Post Reply
Driffill
Posts: 1
Joined: Thu Sep 05, 2019 10:06 am
Vehicle: 2004 Mazda RX8 1.3l Rotary

Mazda As-Built data layout

Post by Driffill »

Hi,
Recently starting using FS to poke around the ECU on my Mazda RX8 and it seems there is an issue, i'll try my best to explain, but i am somewhat new to this type of thing, so might slip up with specific detail (but have tried hard to refine the issue myself).so here goes...

when FS reads the as built from an AUDM RX8, it appears to 'mishandle' some of the returned info..

The initial VIN data returned is used to populate the first fields of the 7E0-01-xx addresses, this offset's the following data by 22bytes. this means what should be at 7E0-00-01 is pushed to 2 bytes into 7E0-01-05.

also, it appears the Mazda as built data 'Starts' from 7E0-00-01, Whereas FS starts it from 7E0-01-xx..
this has an effect on the checksum (as addresses are included) and effectively increments them up by 1.

Example of FS .abd
  • ADD'S : DATA : CHECKSUM BYTE : INFO vs maz .ab
    ;Block 1
    7E0 G1G1 4A4D 3046 45 ...3B > ACSII to Hex
    7E0 G1G2 3130 XXXX 30 ...DF > VIN
    7E0 G1G3 XXXX XXXX 31 ...DF > (also in RKE/731)
    7E0 G1G4 XXXX FFFF FF ...4F >
    7E0 G1G5 FF2A*FFFF FF ...13 *Start 7E0-00-01 PCM1
    7E0 G1G6 FF03*0DFF FF ...FB *Start 7E0-00-02 PCM2 FE = Cruise on FF = off
    7E0 G1G7 FFFE*FFFF FF ...E9 *Start 7E0-00-03 PCM3
    7E0 G1G8 FFFF*FFFF FF ...EB *Start 7E0-00-04 PCM4
    7E0 G1G9 FFFF*FFFF FF ...EC *Start 7E0-00-05 PCM5
    7E0 G1GA FFFF*FFFF FF ...F3 *Start 7E0-00-06 PCM6
    7E0 G1GB FFFF*FFFF FF ...F4 *Start 7E0-00-07 PCM7
    7E0 G1GC FFFF*FFFF FF ...F5 *Start 7E0-00-08 PCM8
    7E0 G1GD FFFF*FFFF FF ...F6 *Start 7E0-00-09 PCM9
    7E0 G1GE FFFF FFFF FF ...F7
    7E0 G1GF FFFF FFFF FF ...F8
    7E0 G1H0 FFFF FFFF FF ...F9
    7E0 G1H1 FFFF FFFF FF ...FA
    7E0 G1H2 FFFF FFFF FF ...FB
    7E0 G1H3 FFFF FFFF FF ...FC
    7E0 G1H4 FFFF FFFF FF ...03
    7E0 G1H5 FFFF FFFF FF ...04
    7E0 G1H6 FFFF FFFF FF ...05
    7E0 G1H7 FFFF FFFF FF ...06
    7E0 G1H8 FFFF FFFF FF ...07
    7E0 G1H9 FFFF FFFF 19 ...22 0X1910 - VIN Checksum?
    7E0 G1HA 10FF 30 ...4D As above + padding

    ;Block 2 Hex > ASCII
    7E0 G2G1 *3133 48 ...96 *start 7E0-01-01 > Engine High/Standard
    ;Block 3
    7E0 G3G1 *36 ...21 *start 7E0-02-01 > Gear Type? 6Sp
    ;Block 4
    7E0 G4G1 *3035 ...51 *start 7E0-03-01 > F1/05/0A
    ;Block 5
    7E0 G5G1 *30 ...1D *start 7E0-04-01 > 0
As compared to a mazda as built file

Code: Select all

<AS_BUILT_DATA>
  <VEHICLE>
    <VIN>JM0FEXXXXXXXXXXXX</VIN>
    <VEHICLE_DATA>
      <DATA LABEL="">
        <CODE>E4BE</CODE>
        <CODE>FFFF</CODE>
        <CODE>FF9F</CODE>
      </DATA>
    </VEHICLE_DATA>
    <PCM_MODULE>
      <DATA LABEL="PCM 1">
        <CODE>FFFF</CODE>
        <CODE>FFFF</CODE>
        <CODE>0310</CODE>
      </DATA>
      <DATA LABEL="PCM 2">
        <CODE>0DFF</CODE>
        <CODE>FFFF</CODE>
        <CODE>FE1A</CODE>
      </DATA>
      <DATA LABEL="PCM 3">
        <CODE>FFFF</CODE>
        <CODE>FFFF</CODE>
        <CODE>FF0E</CODE>
      </DATA>
      <DATA LABEL="PCM 4">
        <CODE>FFFF</CODE>
        <CODE>FFFF</CODE>
        <CODE>FF0F</CODE>
      </DATA>
      <DATA LABEL="PCM 5">
        <CODE>FFFF</CODE>
        <CODE>FFFF</CODE>
        <CODE>FF10</CODE>
      </DATA>
      <DATA LABEL="PCM 6">
        <CODE>FFFF</CODE>
        <CODE>FFFF</CODE>
        <CODE>FF11</CODE>
      </DATA>
      <DATA LABEL="PCM 7">
        <CODE>FFFF</CODE>
        <CODE>FFFF</CODE>
        <CODE>FF12</CODE>
      </DATA>
      <DATA LABEL="PCM 8">
        <CODE>FFFF</CODE>
        <CODE>FFFF</CODE>
        <CODE>FF13</CODE>
      </DATA>
      <DATA LABEL="PCM 9">
        <CODE>FFFF</CODE>
        <CODE>FFFF</CODE>
        <CODE>FF14</CODE>
      </DATA>
      <DATA LABEL="7E0-01-01">
        <CODE>3133</CODE>
        <CODE>4895</CODE>
        <CODE/>
      </DATA>
      <DATA LABEL="7E0-02-01">
        <CODE>3620</CODE>
        <CODE/>
        <CODE/>
      </DATA>
      <DATA LABEL="7E0-03-01">
        <CODE>3035</CODE>
        <CODE>50</CODE>
        <CODE/>
      </DATA>
      <DATA LABEL="7E0-04-01">
        <CODE>301C</CODE>
        <CODE/>
        <CODE/>
      </DATA>
    </PCM_MODULE>

The last thing i noticed was on Mazda's AB file, it shows the BCE(?) module's config (not included with the above code), however it appears FS doesnt have the ability to read/access that area of the ECU (for RX8 PCM and BCM/E is contained within a single unit). as you may see from the code above, there isnt much to be changed within the PCM, but the BCE code looks like it could hold the interior features config for the car, so having access to this (and it reading correctly) would be extremely useful.
drwharris
Posts: 2
Joined: Wed May 12, 2021 11:08 am
Vehicle: Mazda RX-8 Series 1

Re: Mazda As-Built data layout

Post by drwharris »

Is this going to get looked at? One of the main reasons I bought FS was to be able to perform this function and I cant.
tractmec
Posts: 605
Joined: Thu May 26, 2016 11:43 pm
Vehicle: F150 5.4 Triton 2005 Expy5.4 2003 Fusion 3.0 2010

Re: Mazda As-Built data layout

Post by tractmec »

drwharris wrote:
Wed May 12, 2021 11:43 pm
Is this going to get looked at? One of the main reasons I bought FS was to be able to perform this function and I cant.
According to the Change logs this was addressed two Program updates ago shortly after this was posted by the original O/P back in December 2020. If you are still seeing this error make sure you are using the latest version 2.3.40 and if still seeing this error send your Debug files into Forscan at contact@forscan.org following the instructions at this page https://forscan.org/contactus.html under this heading: Providing FORScan Debug information!
Do not PM me as I am not an Admin nor am I a member of the FORScan Team and all questions should be asked and answered on the Open Forum so all can benefit!
Post Reply