Matt,
I'm playing with EMULATOR_OFFSET variable to be able to store up to 8 bins.
#EMULATOR_OFFSET=&H0000
#EMULATOR_OFFSET=&H8000
EMULATOR_OFFSET=&H10000
But the things go wrong.
With the third line enabled, it replaces the bin @ &H0000.
At the end, I'm able to store 2 bins only, @ &H0000 and @ &H8000.
I'm surprised because I reprogram my Moates Ostrich with a H80000 bin just before with EmUtility to be sure all the space is activated.
Dealing with EMULATOR_OFFSET for Moates Ostrich
Moderator: Matt
-
- Posts: 426
- Joined: Mon May 11, 2009 7:58 pm
- Location: FRANCE
Dealing with EMULATOR_OFFSET for Moates Ostrich
[b] Custom tunes S13/Z32/GTIR. First Z32 flex fuel (E85/unleaded) [/b]
[b] 300ZX Z32 '90 400ch 100% E85[/b]
[b] 200SX S13 '92 220ch 100% E85[/b]
[b] Audi S4 B5 '99 400ch 100% E85[/b]
[b] 300ZX Z32 '90 400ch 100% E85[/b]
[b] 200SX S13 '92 220ch 100% E85[/b]
[b] Audi S4 B5 '99 400ch 100% E85[/b]
in general nistune is desgined to work in just a 64KB memory space
what that means is that a lot of the data structures we use are WORDs (0000-FFFF) so when you enter 10000 it cuts off the '1' when the address gets sent to the moates
I can add some extra processing in there for 01 00 00 to get the extra MSB byte there
what that means is that a lot of the data structures we use are WORDs (0000-FFFF) so when you enter 10000 it cuts off the '1' when the address gets sent to the moates
I can add some extra processing in there for 01 00 00 to get the extra MSB byte there
-
- Posts: 426
- Joined: Mon May 11, 2009 7:58 pm
- Location: FRANCE
-
- Posts: 426
- Joined: Mon May 11, 2009 7:58 pm
- Location: FRANCE
When do you plan to make it available ?
I really need it (if you can make a beta starting from the 0.9.12b version).
0.9.12b works fine for me, except when I move the cursor bar in the log player, the values reported are not the real ones, everything comes back to normal when shifting one step left or right.
I really need it (if you can make a beta starting from the 0.9.12b version).
0.9.12b works fine for me, except when I move the cursor bar in the log player, the values reported are not the real ones, everything comes back to normal when shifting one step left or right.
[b] Custom tunes S13/Z32/GTIR. First Z32 flex fuel (E85/unleaded) [/b]
[b] 300ZX Z32 '90 400ch 100% E85[/b]
[b] 200SX S13 '92 220ch 100% E85[/b]
[b] Audi S4 B5 '99 400ch 100% E85[/b]
[b] 300ZX Z32 '90 400ch 100% E85[/b]
[b] 200SX S13 '92 220ch 100% E85[/b]
[b] Audi S4 B5 '99 400ch 100% E85[/b]
its in 0.9.13.3b now
I've tested and we set the rom bank based on the 0bxxxx part of the emulator string
However maptracing does not work with this properly
Maptracing expects 07xxxx even with bank = 00 otherwise maptracing wont respond (nistune will then say its unavailable). So I've hard coded maptracing bank to 07
may be a moates firmware issue? need to investigate that one further and maybe contact craig from moates on this one
I've tested and we set the rom bank based on the 0bxxxx part of the emulator string
However maptracing does not work with this properly
Maptracing expects 07xxxx even with bank = 00 otherwise maptracing wont respond (nistune will then say its unavailable). So I've hard coded maptracing bank to 07
may be a moates firmware issue? need to investigate that one further and maybe contact craig from moates on this one