Pages: [1]
Author Topic: NMax confused  (Read 9145 times)
ejg3855
Full Member
***

Karma: +6/-0
Offline Offline

Posts: 123


« on: September 27, 2011, 05:33:31 PM »

Just looking at things and learning. I was inquring about NMax just to raise rev limit.

I downloaded the 1.8T LP file from here and was looking at it and saw 807, which makes well no sense to me. Since reading the S4 wiki this gets set to a value that is corresponding to RPM.

Logged
Gonzo
Sr. Member
****

Karma: +21/-30
Offline Offline

Posts: 483


« Reply #1 on: September 27, 2011, 08:09:12 PM »

Make sure its set to Lo Hi. If it is, you have the wrong def file or bin.

Easy way to find 1.8T rev limiter is to search for "40 6A" in hex mode.
Logged
ejg3855
Full Member
***

Karma: +6/-0
Offline Offline

Posts: 123


« Reply #2 on: September 27, 2011, 08:28:24 PM »

Make sure its set to Lo Hi. If it is, you have the wrong def file or bin.

Easy way to find 1.8T rev limiter is to search for "40 6A" in hex mode.

40 6A occurs in atleast 3 occasions. Hurmmm. It made some sense when I switched high/lo
Logged
robin
Full Member
***

Karma: +20/-1
Offline Offline

Posts: 139


« Reply #3 on: September 28, 2011, 05:48:09 AM »

That's cause there are more than one rev limiter word.
Logged
ejg3855
Full Member
***

Karma: +6/-0
Offline Offline

Posts: 123


« Reply #4 on: September 28, 2011, 06:10:19 AM »

just meaning that its used in multiple locations? for multiple tasks?

Also 40 6A when converted to decimal is 16490 thats a bit high? Or am I missing something. One file I have its set to 1A 90 and that is 6800 which makes sense.

Thanks for the help and sorry for the amateur questions.




As seen above they also don't match which is confusing, the map opens one value and then looking at the hex dump I see a different value.
« Last Edit: September 28, 2011, 06:18:30 AM by ejg3855 » Logged
Gonzo
Sr. Member
****

Karma: +21/-30
Offline Offline

Posts: 483


« Reply #5 on: October 02, 2011, 10:37:46 AM »

If you set the hexdump to 8bit this should tell you where NMAX is:


I doubt I can make it any easier for you than this.
Logged
Gonzo
Sr. Member
****

Karma: +21/-30
Offline Offline

Posts: 483


« Reply #6 on: October 02, 2011, 10:47:19 AM »

Also factor is : 0.250000

EPROM * FACTOR
(6A40) 27200 * .25 = 6800
Logged
ejg3855
Full Member
***

Karma: +6/-0
Offline Offline

Posts: 123


« Reply #7 on: October 02, 2011, 11:38:52 AM »

Also factor is : 0.250000

EPROM * FACTOR
(6A40) 27200 * .25 = 6800

helps when I look for them in the right order, thanks!
Logged
kenmac
Full Member
***

Karma: +6/-0
Offline Offline

Posts: 161


« Reply #8 on: October 08, 2011, 04:18:54 AM »

The LP definition posted in the Definitions forum is incomplete. It is a work in progress. Do you see the asterisk (*) before each of the map names in WinOLS? The asterisk indicates that that map has been changed and the offsets are verified as correct.  All maps without an asterisk indicate they were simply ported from an HS definition file and not yet updated.
« Last Edit: October 08, 2011, 04:36:17 AM by kenmac » Logged
kenmac
Full Member
***

Karma: +6/-0
Offline Offline

Posts: 161


« Reply #9 on: October 08, 2011, 09:54:36 AM »

The correct NMAX offset for this LP/PL file is 16972.

I am attaching my latest definition file. (Still a few more that need to be updated)

* - Map updated by ArgDub
** - Map updated by kenmac
Logged
kenmac
Full Member
***

Karma: +6/-0
Offline Offline

Posts: 161


« Reply #10 on: October 08, 2011, 05:33:13 PM »

Whoops, uploaded the wrong file.  This one...
Logged
ejg3855
Full Member
***

Karma: +6/-0
Offline Offline

Posts: 123


« Reply #11 on: October 08, 2011, 08:02:15 PM »

Whoops, uploaded the wrong file.  This one...

danke!
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.019 seconds with 16 queries. (Pretty URLs adds 0s, 0q)