Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6901.6902.me72.xml Optimal Ignition Table's strange RPM's from 2123 to 2372 ? #11

Closed
Wiw3K opened this issue Jun 29, 2019 · 12 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@Wiw3K
Copy link

Wiw3K commented Jun 29, 2019

RPM in those tables are from 2123 to 2372 are those correct ? where are other RPM's

@zarboz
Copy link
Owner

zarboz commented Jun 29, 2019

Which file are you dealing with ?

@zarboz
Copy link
Owner

zarboz commented Jun 29, 2019

That way I can trouble shoot the right thing for you

@Wiw3K
Copy link
Author

Wiw3K commented Jun 29, 2019

Found out in winols and compared to my bin and Your xdf - but have to manually put rows/cols , base offset is 10000 for fullread in TunerPro as i have.
optimal ignition table bank 1

@zarboz
Copy link
Owner

zarboz commented Jun 29, 2019

Please refer to the wiki on how to choose the right xdf for your dme once you confirm you’re using the right xdf
Then report if still different

@Wiw3K
Copy link
Author

Wiw3K commented Jun 29, 2019

I am using right XDF for my software version, take a look:
SW
xml

XDF Name is: 6901.6902.ME72.xdf

@zarboz
Copy link
Owner

zarboz commented Jun 29, 2019

That comment section is old I need to updated it
Please download the most recent file directly from the github rather than from the releases page

I will inspect this soon

@zarboz zarboz added the bug Something isn't working label Jun 29, 2019
@zarboz zarboz pinned this issue Jun 29, 2019
@zarboz
Copy link
Owner

zarboz commented Jun 29, 2019

I don’t have my laptop with me I’ll have to refer to the table but I’m pretty sure that one uses an internal address for the RPM registers

@Wiw3K
Copy link
Author

Wiw3K commented Jul 4, 2019

Looks like Your RPM table is wrong, i made it hard coded without pre-defined RPM values and it works well, already made pop bang stage 1 :) Look @ WinOLS @ this table.

@zarboz
Copy link
Owner

zarboz commented Jul 4, 2019

I need to address the offsets not being internally mapped I will work on this

@Wiw3K
Copy link
Author

Wiw3K commented Jul 4, 2019

Ok, temporary fix for this is define RPM values like i posted, it works. looking for FKSTT for 6901 & 6902 :)

@zarboz zarboz closed this as completed Jul 8, 2019
@zarboz zarboz reopened this Aug 20, 2019
@zarboz
Copy link
Owner

zarboz commented Aug 20, 2019

through some discussion over private message it has come to my attention that many maps are not accurate for 6901/2

I will probably put all existing xdf in defunct folder and then start a new XDF based around a 6901/2 binary

@Wiw3K
Copy link
Author

Wiw3K commented Aug 20, 2019 via email

@zarboz zarboz closed this as completed Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants