[Alex@AKMotorwerk]

Originally Posted by Bimmer335i07

+1

My top speed is only 130.

I didn't get the zsp, but I have all the zsp components in my car now. All I need is the speed limiter removal. Not that I will ever go past 155, but at least I can go past 130. LOL!

Originally Posted by ultimateendz

bubble said he already did it....

shoot me a PM.... we'll get this going on ur cars

[ultimateendz]

Originally Posted by Alex@SupremePower

+1.... LOL

in before the rate lock!!!!

[Alex@AKMotorwerk]

Originally Posted by ultimateendz

in before the rate lock!!!!

HAHAHHAA.... see you on Friday bro

[Mike@N54Tuning.com]

Originally Posted by Septro

A Dyno (but most are limited to 200mp/h



While I agree - I think they are already limiting functions between enthusiasts versus proffessional with the VIN lock down. Hell I would take a 1 VIN lock to have parity in features between the tools. The sales they would get selling individual tools would more than offset the loss of $500 bucks for the professional version.



So you are saying the 'delimiter' defeat doesn't really work on the BT tool because you tested it or because you read it somewhere on the internet and it must be true?

Well I am going downstairs to the car right after I post this to test it and we will see whats up. Will post my findings shortly. No point speculating but I believe the OP already said it was done so I am confused by the contradiction.

Mike

[sd390r]

You guys are really complaining about the pro version lol a few months ago everyone was dying to clear codes + scrambling to try and find a GT1 everytime something went wrong

[ianthegreat]

Originally Posted by sd390r

You guys are really complaining about the pro version lol a few months ago everyone was dying to clear codes + scrambling to try and find a GT1 everytime something went wrong

old news, this is america

[Mike@N54Tuning.com]

Well I can verify it works.. Only thing is you CAN'T input your own number so you are still limited to the max on the menu, which is 155MPH, which in my books is fine, and for those guys without the sport package a great feature.

I was hoping you could put in your own number but I guess you are limited with the operational parameters of the DME.

Mike

[sd390r]

yeah that would make sense

[DMETune]

Originally Posted by Septro

So you are saying the 'delimiter' defeat doesn't really work on the BT tool because you tested it or because you read it somewhere on the internet and it must be true?

These are the 4 values inside the DME:
V_MAX_1 (km/h) [206]


V_MAX_2 (km/h) [235]


V_MAX_3 (km/h) [250]


V_MAX_4 (km/h) [243]

This won't "delimit" anything.

It's all spelled out here, so yeah, it's probably true.

[Bubbles]

Originally Posted by ultimateendz

bubble said he already did it....

The Dinan Flash already incorporates a delimit so I did not adjust my coding.

[Bubbles]

Originally Posted by sd390r

You guys are really complaining about the pro version lol a few months ago everyone was dying to clear codes + scrambling to try and find a GT1 everytime something went wrong

Short-term memories.

Originally Posted by Mike@N54Tuning.com

Well I can verify it works.. Only thing is you CAN'T input your own number so you are still limited to the max on the menu, which is 155MPH, which in my books is fine, and for those guys without the sport package a great feature.

I was hoping you could put in your own number but I guess you are limited with the operational parameters of the DME.

Mike

Thanks for testing it out Mike.

[mwahlert]

Originally Posted by Bimmer335i07

+1

My top speed is only 130.

I didn't get the zsp, but I have all the zsp components in my car now. All I need is the speed limiter removal. Not that I will ever go past 155, but at least I can go past 130. LOL!

where did you manage to find a set of ZSP seats? i could use a set myself.

[bulldog_yyc]

Originally Posted by DMETune

These are the 4 values inside the DME:
V_MAX_1 (km/h) [206]


V_MAX_2 (km/h) [235]


V_MAX_3 (km/h) [250]


V_MAX_4 (km/h) [243]

This won't "delimit" anything.

It's all spelled out here, so yeah, it's probably true.

is the ECU spec available on the net somewhere?

[DMETune]

Originally Posted by turkish335

is the ECU spec available on the net somewhere?

Not that I know of, no.

[jzchen]

I bought the pro version just for this purpose, but after they got it up and running, I found my limiter set to 243km/hr, or 150mph. It is not accurate that it is set to 130 mph if you don't have the sports package. I haven't confirmed you can adjust it to 250km/hr, or 155mph yet because it didn't work for a while. They say it should now but my car is at the dealer, (note the Reset ECU in the history section of the tool webpage)... They can send you a code to remove the limiter altogether, but as I understand a fault code will result.

Originally Posted by Bimmer335i07

+1

My top speed is only 130.

I didn't get the zsp, but I have all the zsp components in my car now. All I need is the speed limiter removal. Not that I will ever go past 155, but at least I can go past 130. LOL!

[DMETune]

It would be interesting to see if the code change (done after 54 minutes of total run time) actually does anything since it's written here that it does not.

Mike/Bubbles, can either of you *safely* test whether or not this code 'change' actually has an impact on speed limit?

0000:8017E908 WriteDataByCommonIdentifierMAIN: ; DATA XREF: ROM:801E6860o
0000:8017E908
0000:8017E908 ; FUNCTION CHUNK AT 0000:80175A72 SIZE 000000A8 BYTES
0000:8017E908 ; FUNCTION CHUNK AT 0000:80175BA0 SIZE 00000012 BYTES
0000:8017E908 ; FUNCTION CHUNK AT 0000:80175C24 SIZE 00000356 BYTES
0000:8017E908 ; FUNCTION CHUNK AT 0000:80176260 SIZE 0000001A BYTES
0000:8017E908
0000:8017E908 movh.a a4, #0xC040
0000:8017E90C lea a4, [a4]-0x3CD4
0000:8017E910 ld16.a a15, [a4]
0000:8017E912 lea a2, dword_D0001B4C
0000:8017E916 ld16.bu d15, [a15]
0000:8017E918 st16.h [a2], d15
0000:8017E91A ld.hu d15, dword_D0001B4C
0000:8017E91E sha32 d15, d15, #8
0000:8017E922 st16.h [a2], d15
0000:8017E924 ld.hu d15, dword_D0001B4C
0000:8017E928 ld16.bu d0, [a15]1
0000:8017E92A or16 d15, d0
0000:8017E92C st16.h [a2], d15
0000:8017E92E mov32 d15, #0x1000
0000:8017E932 ld.hu d0, dword_D0001B4C
0000:8017E936 sub16.a sp, #8
0000:8017E938 jeq32 d15, d0, loc_8017EA30
0000:8017E93C mov32 d15, #0x1001
0000:8017E940 jeq32 d15, d0, loc_8017EA70
0000:8017E944 mov32 d15, #0x3000
0000:8017E948 jeq32 d15, d0, loc_8017EAAC
0000:8017E94C mov32 d15, #0x3001
0000:8017E950 jeq32 d15, d0, loc_8017EB60
0000:8017E954 mov32 d15, #0x3010
0000:8017E958 jeq32 d15, d0, loc_8017EBFC <- 2E 30 10

0000:8017EBFC loc_8017EBFC: ; CODE XREF: WriteDataByCommonIdentifierMAIN+50j
0000:8017EBFC movh.a a12, #0xC040
0000:8017EC00 lea a12, [a12]-0x3CDE
0000:8017EC04 ld.hu d15, [a12]0
0000:8017EC08 jeq16 d15, #4, loc_8017EC1A
0000:8017EC0A movh.a a15, #0xC040
0000:8017EC0E lea a15, [a15]-0x3D00
0000:8017EC12 ld.hu d15, [a15]0
0000:8017EC16 jz32.t d15:4, loc_8017F9D2
0000:8017EC1A
0000:8017EC1A loc_8017EC1A: ; CODE XREF: WriteDataByCommonIdentifierMAIN+300j
0000:8017EC1A movh.a a2, #0xC040
0000:8017EC1E lea a2, [a2]-0x3D00
0000:8017EC22 mov16 d8, #0
0000:8017EC24 movh.a a15, #0x8000
0000:8017EC28 lea a15, [a15]0x1DB0 ; 0x80001DB0
0000:8017EC2C ld16.bu d15, [a15]
0000:8017EC2E jz16 d15, loc_8017EC4C
0000:8017EC30 movh.a a15, #0x8000
0000:8017EC34 lea a15, [a15]0xD00 ; 0x80000D00
0000:8017EC38 ld16.bu d15, [a15]
0000:8017EC3A jz16 d15, loc_8017EC4C
0000:8017EC3C mov.u d0, #0x7E40
0000:8017EC40 ld32.w d15, [a0]0x3740 ; 0xD000B740 (TRT)
0000:8017EC44 addih d0, d0, #5
0000:8017EC48 jlt.u d0, d15, loc_8017EE10
0000:8017EC4C
0000:8017EC4C loc_8017EC4C: ; CODE XREF: WriteDataByCommonIdentifierMAIN+326j
0000:8017EC4C ; WriteDataByCommonIdentifierMAIN+332j
0000:8017EC4C lea a15, [a0]0x4CD
0000:8017EC50 ld16.bu d15, [a15]
0000:8017EC52 jeq32 d15, #0, loc_8017EB48
0000:8017EC56 lea a15, [a0]0x405
0000:8017EC5A ld16.bu d15, [a15]
0000:8017EC5C jeq32 d15, #0, loc_8017EB48
0000:8017EC60 ld.hu d15, [a2]0
0000:8017EC64 jnz32.t d15:4, loc_8017EDA8
0000:8017EC68 ld16.a a15, [a4]
0000:8017EC6A ld16.bu d0, [a15]2
0000:8017EC6C jge.u d0, #4, loc_8017F8DE
0000:8017EC70 insert d15, d15, #1, #4, #1
0000:8017EC74 st16.h [a2], d15
0000:8017EC76 movh.a a15, #0xC040
0000:8017EC7A lea a15, [a15]-0x3BC4
0000:8017EC7E mov16 d15, #0x78
0000:8017EC80 st16.b [a15], d15
0000:8017EC82 movh.a a15, #0xC040
0000:8017EC86 ld32.w d15, [a15]-0x3CD0
0000:8017EC8A ld.hu d0, [a12]0
0000:8017EC8E add16 d15, d0
0000:8017EC90 st32.w [a15]-0x3CD0, d15
0000:8017EC94 ld16.a a4, [a4]
0000:8017EC96 add16.a a4, #2
0000:8017EC98 j32 loc_80175A9E

If TRT (Total Running Time) is over 0x7E40 (almost 54 minutes) then....

0000:8017EE10 loc_8017EE10: ; CODE XREF: WriteDataByCommonIdentifierMAIN+1F0j
0000:8017EE10 ; WriteDataByCommonIdentifierMAIN+2A4j ...
0000:8017EE10 ld.hu d15, [a2]0
0000:8017EE14 insert d15, d15, #0, #4, #1
0000:8017EE18 st16.h [a2], d15
0000:8017EE1A j32 loc_8017F9E0

0000:8017F9E0 loc_8017F9E0: ; CODE XREF: WriteDataByCommonIdentifierMAIN+124j
0000:8017F9E0 ; WriteDataByCommonIdentifierMAIN+512j ...
0000:8017F9E0 movh.a a15, #0xC040
0000:8017F9E4 lea a15, [a15]-0x3BC4
0000:8017F9E8 mov16 d15, #0x12 <------- KWP Error 0x12 subFunctionNotSupported
0000:8017F9EA st16.b [a15], d15
0000:8017F9EC ret16
0000:8017F9EC ; End of function WriteDataByCommonIdentifierMAIN

[RiXst3r]

Originally Posted by DMETune

It would be interesting to see if the code change (done after 54 minutes of total run time) actually does anything since it's written here that it does not.

Mike/Bubbles, can either of you *safely* test whether or not this code 'change' actually has an impact on speed limit?

0000:8017E908 WriteDataByCommonIdentifierMAIN: ; DATA XREF: ROM:801E6860o
0000:8017E908
0000:8017E908 ; FUNCTION CHUNK AT 0000:80175A72 SIZE 000000A8 BYTES
0000:8017E908 ; FUNCTION CHUNK AT 0000:80175BA0 SIZE 00000012 BYTES
0000:8017E908 ; FUNCTION CHUNK AT 0000:80175C24 SIZE 00000356 BYTES
0000:8017E908 ; FUNCTION CHUNK AT 0000:80176260 SIZE 0000001A BYTES
0000:8017E908
0000:8017E908 movh.a a4, #0xC040
0000:8017E90C lea a4, [a4]-0x3CD4
0000:8017E910 ld16.a a15, [a4]
0000:8017E912 lea a2, dword_D0001B4C
0000:8017E916 ld16.bu d15, [a15]
0000:8017E918 st16.h [a2], d15
0000:8017E91A ld.hu d15, dword_D0001B4C
0000:8017E91E sha32 d15, d15, #8
0000:8017E922 st16.h [a2], d15
0000:8017E924 ld.hu d15, dword_D0001B4C
0000:8017E928 ld16.bu d0, [a15]1
0000:8017E92A or16 d15, d0
0000:8017E92C st16.h [a2], d15
0000:8017E92E mov32 d15, #0x1000
0000:8017E932 ld.hu d0, dword_D0001B4C
0000:8017E936 sub16.a sp, #8
0000:8017E938 jeq32 d15, d0, loc_8017EA30
0000:8017E93C mov32 d15, #0x1001
0000:8017E940 jeq32 d15, d0, loc_8017EA70
0000:8017E944 mov32 d15, #0x3000
0000:8017E948 jeq32 d15, d0, loc_8017EAAC
0000:8017E94C mov32 d15, #0x3001
0000:8017E950 jeq32 d15, d0, loc_8017EB60
0000:8017E954 mov32 d15, #0x3010
0000:8017E958 jeq32 d15, d0, loc_8017EBFC <- 2E 30 10

0000:8017EBFC loc_8017EBFC: ; CODE XREF: WriteDataByCommonIdentifierMAIN+50j
0000:8017EBFC movh.a a12, #0xC040
0000:8017EC00 lea a12, [a12]-0x3CDE
0000:8017EC04 ld.hu d15, [a12]0
0000:8017EC08 jeq16 d15, #4, loc_8017EC1A
0000:8017EC0A movh.a a15, #0xC040
0000:8017EC0E lea a15, [a15]-0x3D00
0000:8017EC12 ld.hu d15, [a15]0
0000:8017EC16 jz32.t d15:4, loc_8017F9D2
0000:8017EC1A
0000:8017EC1A loc_8017EC1A: ; CODE XREF: WriteDataByCommonIdentifierMAIN+300j
0000:8017EC1A movh.a a2, #0xC040
0000:8017EC1E lea a2, [a2]-0x3D00
0000:8017EC22 mov16 d8, #0
0000:8017EC24 movh.a a15, #0x8000
0000:8017EC28 lea a15, [a15]0x1DB0 ; 0x80001DB0
0000:8017EC2C ld16.bu d15, [a15]
0000:8017EC2E jz16 d15, loc_8017EC4C
0000:8017EC30 movh.a a15, #0x8000
0000:8017EC34 lea a15, [a15]0xD00 ; 0x80000D00
0000:8017EC38 ld16.bu d15, [a15]
0000:8017EC3A jz16 d15, loc_8017EC4C
0000:8017EC3C mov.u d0, #0x7E40
0000:8017EC40 ld32.w d15, [a0]0x3740 ; 0xD000B740 (TRT)
0000:8017EC44 addih d0, d0, #5
0000:8017EC48 jlt.u d0, d15, loc_8017EE10
0000:8017EC4C
0000:8017EC4C loc_8017EC4C: ; CODE XREF: WriteDataByCommonIdentifierMAIN+326j
0000:8017EC4C ; WriteDataByCommonIdentifierMAIN+332j
0000:8017EC4C lea a15, [a0]0x4CD
0000:8017EC50 ld16.bu d15, [a15]
0000:8017EC52 jeq32 d15, #0, loc_8017EB48
0000:8017EC56 lea a15, [a0]0x405
0000:8017EC5A ld16.bu d15, [a15]
0000:8017EC5C jeq32 d15, #0, loc_8017EB48
0000:8017EC60 ld.hu d15, [a2]0
0000:8017EC64 jnz32.t d15:4, loc_8017EDA8
0000:8017EC68 ld16.a a15, [a4]
0000:8017EC6A ld16.bu d0, [a15]2
0000:8017EC6C jge.u d0, #4, loc_8017F8DE
0000:8017EC70 insert d15, d15, #1, #4, #1
0000:8017EC74 st16.h [a2], d15
0000:8017EC76 movh.a a15, #0xC040
0000:8017EC7A lea a15, [a15]-0x3BC4
0000:8017EC7E mov16 d15, #0x78
0000:8017EC80 st16.b [a15], d15
0000:8017EC82 movh.a a15, #0xC040
0000:8017EC86 ld32.w d15, [a15]-0x3CD0
0000:8017EC8A ld.hu d0, [a12]0
0000:8017EC8E add16 d15, d0
0000:8017EC90 st32.w [a15]-0x3CD0, d15
0000:8017EC94 ld16.a a4, [a4]
0000:8017EC96 add16.a a4, #2
0000:8017EC98 j32 loc_80175A9E

If TRT (Total Running Time) is over 0x7E40 (almost 54 minutes) then....

0000:8017EE10 loc_8017EE10: ; CODE XREF: WriteDataByCommonIdentifierMAIN+1F0j
0000:8017EE10 ; WriteDataByCommonIdentifierMAIN+2A4j ...
0000:8017EE10 ld.hu d15, [a2]0
0000:8017EE14 insert d15, d15, #0, #4, #1
0000:8017EE18 st16.h [a2], d15
0000:8017EE1A j32 loc_8017F9E0

0000:8017F9E0 loc_8017F9E0: ; CODE XREF: WriteDataByCommonIdentifierMAIN+124j
0000:8017F9E0 ; WriteDataByCommonIdentifierMAIN+512j ...
0000:8017F9E0 movh.a a15, #0xC040
0000:8017F9E4 lea a15, [a15]-0x3BC4
0000:8017F9E8 mov16 d15, #0x12 <------- KWP Error 0x12 subFunctionNotSupported
0000:8017F9EA st16.b [a15], d15
0000:8017F9EC ret16
0000:8017F9EC ; End of function WriteDataByCommonIdentifierMAIN

Impressive... !

[battlehawk1025]

i try changing it. but every single time it goes back to the original speed limit. any ideas why?

[Mike@N54Tuning.com]

I think the menu defaults to 235 km/hr. Mine is the sport package so it should be 250 km/hr and at first it said 235 km/hr as well. I coded all the speeds successfully so I think it works. Can't test it as I already have it a 250. I guess I could set it to 200 and see if it cuts out, but again not anytime soon as I won't do this on the street.

Mike

[luca335i]

Yer doing this on my car mike

[battlehawk1025]

Originally Posted by Mike@N54Tuning.com

I think the menu defaults to 235 km/hr. Mine is the sport package so it should be 250 km/hr and at first it said 235 km/hr as well. I coded all the speeds successfully so I think it works. Can't test it as I already have it a 250. I guess I could set it to 200 and see if it cuts out, but again not anytime soon as I won't do this on the street.

Mike

i no i have to 250 from the factory but it says 235 any idea? i mean how do i no i changed it successfully

[jzchen]

There should be a Reset ECU or ECU Reset in the Commands section. You need to set the speed you want and then somehow Reset the ECU. It was missing and I cannot confirm it is there yet. There is also a way to reset it via Command Console: type in "11,01" without the "" marks, and press Enter. I'm a little scared to try this Command Console, for 5mph that I'll probably never use anyways. (Please check with Duram if the 11,01 is correct for your specific ECU.)

Originally Posted by battlehawk1025

i try changing it. but every single time it goes back to the original speed limit. any ideas why?