RomRaider Logo

RomRaider

Open Source ECU Tools
 FAQ •  Register •  Login 

RomRaider

Documentation

Community

Developers

It is currently Tue Dec 23, 2025 7:22 am

All times are UTC - 5 hours [ DST ]





Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: AVCS table definition odity
PostPosted: Sat Sep 07, 2024 4:46 am 
Offline
RomRaider Donator

Joined: Thu Jan 24, 2013 5:33 am
Posts: 96
Location: Maribor, Slovenia
While I was looking at AVCS tables for my car (2007 EDM 3.0 Spec.B 6MT, D2UH001L.xml) I noticed that the angle values were quite low compared to some other ROMs of a similar engine (same year JDM D2PH41Q, for example). And that wasn't just a 'few degrees' low - where the other ROM has a value of 50°, mine shown 13.89° of cam advance...

It's also weird that in 'Table -> Compare' menu, the 'Compare to table' option was not available, even though I had both ROM's open and was looking at the same tables.

So I had a look at definitions and I found that there are actually several sets of definitions for Intake Cam Advance Angle in the XML, all having slightly different names:

  • "Intake Cam Advance Angle (AVCS)"
  • "Intake Cam Advance Angle A (AVCS)"
  • "Intake Cam Advance Angle B (AVCS)"
  • "Intake Cam Advance Angle Cruise (AVCS)"
  • "Intake Cam Advance Angle Non-Cruise (AVCS)"
  • "Intake Cam Advance Angle Cruise (AVCS) "
  • "Intake Cam Advance Angle Non-Cruise (AVCS) "

Notice the trailing space in the last two - it's important.

They're all fairly similar (besides obvious different descriptions for A / B / Cruise / Non-Cruise), weirdly they all have 14x18 size even though they show up different sizes in RomRaider.

But crucially, one set has a different 'scaling expression':

Code:
      <scaling units="Advance (degrees)" expression="x*.0054931640625" to_byte="x/.0054931640625" format="0.00" fineincrement=".5" coarseincrement="1" />


Code:
      <scaling units="Advance (degrees)" expression="x*.001525879" to_byte="x/.001525879" format="0.00" fineincrement=".5" coarseincrement="1" />



And judging by the D2UH001L definition, the one is used for my ROM is the odd one - notice the trailing space:

Code:
    <table name=[b]"Intake Cam Advance Angle Cruise (AVCS) "[/b] storageaddress="CD6D8" sizey="11">
      <table type="X Axis" storageaddress="CD674" />
      <table type="Y Axis" storageaddress="CD6AC" />
    </table>


while the other ROM(s) use the other definition - no trailing space:
Code:
    <table name=[b]"Intake Cam Advance Angle Cruise (AVCS)"[/b] storageaddress="CE874" sizey="11">
      <table type="X Axis" storageaddress="CE810" />
      <table type="Y Axis" storageaddress="CE848" />
    </table>



So which one is the correct one for my car? Does the cam advance actually go up to 50° or is the max. 13.89° the realistic one?


Top
 Profile  
 
 Post subject: Re: AVCS table definition odity
PostPosted: Sat Sep 07, 2024 7:04 am 
Offline
Moderator

Joined: Thu May 20, 2010 4:01 am
Posts: 3117
Location: Johannesburg, South Africa
That scaling is correct - the scaling can be different across the various years' models.

From the rom:
Code:
ROM:000918B0 word_918B0:     .data.w h'E             ; DATA XREF: sub_410CE:loc_4110C↑o
ROM:000918B0                                         ; ROM:off_411D4↑o ...
ROM:000918B2                 .data.w h'B
ROM:000918B4                 .data.l flt_CD674
ROM:000918B8                 .data.l flt_CD6AC
ROM:000918BC                 .data.l word_CD6D8      ; = 0.0
ROM:000918C0                 .data.l h'8000000
ROM:000918C4                 .float 0.0054931641
ROM:000918C8                 .float 0.0


And yes, it does go up to 50 in the stock calibration:
Code:
ROM:000CD786                 .data.w h'238E          ; = 5.0e1
ROM:000CD788                 .data.w h'238E          ; = 5.0e1
ROM:000CD78A                 .data.w h'238E          ; = 5.0e1
ROM:000CD78C                 .data.w h'238E          ; = 5.0e1
ROM:000CD78E                 .data.w h'238E          ; = 5.0e1
ROM:000CD790                 .data.w h'238E          ; = 5.0e1
ROM:000CD792                 .data.w h'238E          ; = 5.0e1
ROM:000CD794                 .data.w h'238E          ; = 5.0e1

_________________
He who dies with the most gadgets wins.

Please do not PM me - use the email option.


Top
 Profile  
 
 Post subject: Re: AVCS table definition odity
PostPosted: Sat Sep 07, 2024 7:33 am 
Offline
RomRaider Donator

Joined: Thu Jan 24, 2013 5:33 am
Posts: 96
Location: Maribor, Slovenia
I find it a bit weird that my 2007 3.0 Spec.B would have so wildly different AVCS tables than a JDM 2007 3.0 Spec.B.

Left is mine, right is the JDM one:

Attachment:
AVCS_D2UH001L_vs_D2PH410Q.jpg
AVCS_D2UH001L_vs_D2PH410Q.jpg [ 401.53 KiB | Viewed 229 times ]


Top
 Profile  
 
 Post subject: Re: AVCS table definition odity
PostPosted: Sat Sep 07, 2024 7:39 am 
Offline
RomRaider Donator

Joined: Thu Jan 24, 2013 5:33 am
Posts: 96
Location: Maribor, Slovenia
Oh, I just found out how to display raw values - these are the same between both ROMs:

Attachment:
AVCS_D2UH001L_vs_D2PH410Q_raw.jpg
AVCS_D2UH001L_vs_D2PH410Q_raw.jpg [ 369.31 KiB | Viewed 228 times ]


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Style based on FI Subsilver by phpBBservice.nl