Mazdaedit
01-23-2015, 08:33 PM
#901
I'm sure that same scenario is played out all over the world . I just got told by a "genius" here that he is fitting a Microtec LT10 and upgrading his injectors , fitting fuel pump and regulator . He has an NA streetport and has been told he needs all that because of all the extra power he will have. What a joke !
Any luck with Epifan ?
Any luck with Epifan ?
lemme send him a msg now
02-12-2015, 02:09 PM
#906
Should Mazda 'be able to program new keys from scratch if I have a Mazda edit flash ? They have issues. And don't know what the problem is. They say they can connect but aren't getting signal from the keys to reprogram the keys. They think it's the key switch sensor or wiring harness... I just need a for sure thing that they can do a reprogram of keys with a mazdaedit flash on the ecu
02-12-2015, 05:56 PM
#907
Should Mazda 'be able to program new keys from scratch if I have a Mazda edit flash ? They have issues. And don't know what the problem is. They say they can connect but aren't getting signal from the keys to reprogram the keys. They think it's the key switch sensor or wiring harness... I just need a for sure thing that they can do a reprogram of keys with a mazdaedit flash on the ecu
02-12-2015, 06:39 PM
#908
I asked epifan he was unsure as well. Figured someone may have had a reprogram after a mazdaedit flash. They can connect to the ecu but they can't reprogram the ecu to accept key ids. They say it doesn't respond to the keys. I hope I find out something asap.
Mazda is a bunch of clueless people with great machines. Wish all mechanic shops had the ecu programmers and tools.
Mazdaedit can't disable the immoblozer unless it's a mx5.... Maybe it would be a feature we could get him to add... Racing beat can disable the anti theft system in there flash
Mazda is a bunch of clueless people with great machines. Wish all mechanic shops had the ecu programmers and tools.
Mazdaedit can't disable the immoblozer unless it's a mx5.... Maybe it would be a feature we could get him to add... Racing beat can disable the anti theft system in there flash
02-13-2015, 09:13 AM
#909
ME does not, and is NOT capable of programming keys. it does not interferer with the immobilizer module. you can flash the ECU 10 million times and it still will not allow you to start the car.
Dealers (IDS) will NOT be able to flash ANY ME flashed ECU, simply because ME changes the security SEED/KEY and IDS will not be able to issue the erase command because it does not uses Mazda's default SEED/KEY. You need to ask epifan to give you a "return to stock flash", so it changes the security SEED/KEY back to stock Mazda's version. THEN dealer can flash it.
I have an idea of what ME's security SEED/KEY algorithm is, but I don't have the time to crack it. but someday I will try it, cuz it makes life much easier once my subscription runs out.
Dealers (IDS) will NOT be able to flash ANY ME flashed ECU, simply because ME changes the security SEED/KEY and IDS will not be able to issue the erase command because it does not uses Mazda's default SEED/KEY. You need to ask epifan to give you a "return to stock flash", so it changes the security SEED/KEY back to stock Mazda's version. THEN dealer can flash it.
I have an idea of what ME's security SEED/KEY algorithm is, but I don't have the time to crack it. but someday I will try it, cuz it makes life much easier once my subscription runs out.
Last edited by nycgps; 02-13-2015 at 10:21 AM.
02-19-2015, 12:20 PM
#911
ME does not, and is NOT capable of programming keys. it does not interferer with the immobilizer module. you can flash the ECU 10 million times and it still will not allow you to start the car.
Dealers (IDS) will NOT be able to flash ANY ME flashed ECU, simply because ME changes the security SEED/KEY and IDS will not be able to issue the erase command because it does not uses Mazda's default SEED/KEY. You need to ask epifan to give you a "return to stock flash", so it changes the security SEED/KEY back to stock Mazda's version. THEN dealer can flash it.
I have an idea of what ME's security SEED/KEY algorithm is, but I don't have the time to crack it. but someday I will try it, cuz it makes life much easier once my subscription runs out.
Dealers (IDS) will NOT be able to flash ANY ME flashed ECU, simply because ME changes the security SEED/KEY and IDS will not be able to issue the erase command because it does not uses Mazda's default SEED/KEY. You need to ask epifan to give you a "return to stock flash", so it changes the security SEED/KEY back to stock Mazda's version. THEN dealer can flash it.
I have an idea of what ME's security SEED/KEY algorithm is, but I don't have the time to crack it. but someday I will try it, cuz it makes life much easier once my subscription runs out.
02-19-2015, 08:49 PM
#912
02-20-2015, 09:55 PM
#914
When they do a fresh flash with IDS, they enter the default file name into the system, which means it's just the same version that the car came with, after that they will need to perform the update to update it to the newest flash.
ME(Mazdaedit) does not access immobilizer
There are ways to defeat immobilizer, but that's not something you want to do, even no one really wants to steal Rx8.
02-22-2015, 08:39 PM
#915
Is it true that the oiling, dwell, and other tables will automatically interpolate if I set the rev limit anywhere above the 9000RPM that the tables show? I don't think there's a way to add columns to tables, and I don't want to go past 9k and have the OMP shut itself.
This is a neat tool.
This is a neat tool.
02-23-2015, 09:46 AM
#916
Nope,
this is what I just got back from epifan
basically it means you can change the value of the maps to say, 9500 rpm, but you cannot just add another line to the map.
Edited : Ok I just checked Cobb AP Racer, cannot add another line, but I can play with the values, same with ME
this is what I just got back from epifan
You can change axis values of a maps. It is not possible to change map dimensions
Edited : Ok I just checked Cobb AP Racer, cannot add another line, but I can play with the values, same with ME
Last edited by nycgps; 02-23-2015 at 09:48 AM.
02-23-2015, 01:26 PM
#917
Is it true that the oiling, dwell, and other tables will automatically interpolate if I set the rev limit anywhere above the 9000RPM that the tables show? I don't think there's a way to add columns to tables, and I don't want to go past 9k and have the OMP shut itself.
This is a neat tool.
This is a neat tool.
EG : remove the 720rpm column , move all the other columns (including the numbers in them ) over one . Then add your 9500rpm column at the end.
03-23-2015, 03:07 PM
#918
03-23-2015, 06:32 PM
#920
Registered
Join Date: Apr 2013
Location: South Wales, UK
Posts: 68
Likes: 0
Received 0 Likes
on
0 Posts
Copy the attached file on to the MicroSD card to get the OpenPort to log. This is the last version I wrote from scratch (the one FlameShades uses 
) which I think I posted a while back - the commonly available example causes log corruption when the actual AFR is read in a certain way.
As for knock detection, I vaguely remember either the detection or the resulting commanded retardation being available through one of the 0x22 or manufacturer specific PIDs - I'll have a look through my notes later and check I wasn't imagining things. I know the accuracy or sensitivity of the detector is in dispute but it's worth a shot, if it can be read that is.
) which I think I posted a while back - the commonly available example causes log corruption when the actual AFR is read in a certain way.As for knock detection, I vaguely remember either the detection or the resulting commanded retardation being available through one of the 0x22 or manufacturer specific PIDs - I'll have a look through my notes later and check I wasn't imagining things. I know the accuracy or sensitivity of the detector is in dispute but it's worth a shot, if it can be read that is.
03-23-2015, 07:10 PM
#921
Copy the attached file on to the MicroSD card to get the OpenPort to log. This is the last version I wrote from scratch (the one FlameShades uses ) which I think I posted a while back - the commonly available example causes log corruption when the actual AFR is read in a certain way.
As for knock detection, I vaguely remember either the detection or the resulting commanded retardation being available through one of the 0x22 or manufacturer specific PIDs - I'll have a look through my notes later and check I wasn't imagining things. I know the accuracy or sensitivity of the detector is in dispute but it's worth a shot, if it can be read that is.
) which I think I posted a while back - the commonly available example causes log corruption when the actual AFR is read in a certain way.As for knock detection, I vaguely remember either the detection or the resulting commanded retardation being available through one of the 0x22 or manufacturer specific PIDs - I'll have a look through my notes later and check I wasn't imagining things. I know the accuracy or sensitivity of the detector is in dispute but it's worth a shot, if it can be read that is.
I wasn't sure who made up the file so didn't want to post it up publically. Would be great if you can find the knock sensor parameter !
03-23-2015, 07:39 PM
#922
Registered
Join Date: Apr 2013
Location: South Wales, UK
Posts: 68
Likes: 0
Received 0 Likes
on
0 Posts
No problem 
if there's any other parameter you would find useful let me know and I'll try and build it in. It can be picky when reading some PIDs in combination or even just in a certain order.
I thought I'd seen it somewhere - how about this in mode 0x22:
22 1746 knock retard amount ROM:0005DC88 subStruct <0x1746, 0x100, 0xFFFE0000, canKnockRetardAmount>
I'll drop it in tomorrow and see what I get. Could be fun testing it though :/
if there's any other parameter you would find useful let me know and I'll try and build it in. It can be picky when reading some PIDs in combination or even just in a certain order.I thought I'd seen it somewhere - how about this in mode 0x22:
22 1746 knock retard amount ROM:0005DC88 subStruct <0x1746, 0x100, 0xFFFE0000, canKnockRetardAmount>
I'll drop it in tomorrow and see what I get. Could be fun testing it though :/
03-23-2015, 08:15 PM
#923
No problem if there's any other parameter you would find useful let me know and I'll try and build it in. It can be picky when reading some PIDs in combination or even just in a certain order.
I thought I'd seen it somewhere - how about this in mode 0x22:
22 1746 knock retard amount ROM:0005DC88 subStruct <0x1746, 0x100, 0xFFFE0000, canKnockRetardAmount>
I'll drop it in tomorrow and see what I get. Could be fun testing it though :/
if there's any other parameter you would find useful let me know and I'll try and build it in. It can be picky when reading some PIDs in combination or even just in a certain order.I thought I'd seen it somewhere - how about this in mode 0x22:
22 1746 knock retard amount ROM:0005DC88 subStruct <0x1746, 0x100, 0xFFFE0000, canKnockRetardAmount>
I'll drop it in tomorrow and see what I get. Could be fun testing it though :/
03-24-2015, 07:47 AM
#924
that accepts the mini sd card, which will prompt for logging with the logcfg.txt file on it.
how long can it log, how about the whole track session which is 20-30 min?
How big of the card I need. It wold be nice for someone to write how to log post...
03-24-2015, 07:53 AM
#925
Copy the attached file on to the MicroSD card to get the OpenPort to log. This is the last version I wrote from scratch (the one FlameShades uses ) which I think I posted a while back - the commonly available example causes log corruption when the actual AFR is read in a certain way.
As for knock detection, I vaguely remember either the detection or the resulting commanded retardation being available through one of the 0x22 or manufacturer specific PIDs - I'll have a look through my notes later and check I wasn't imagining things. I know the accuracy or sensitivity of the detector is in dispute but it's worth a shot, if it can be read that is.
) which I think I posted a while back - the commonly available example causes log corruption when the actual AFR is read in a certain way.As for knock detection, I vaguely remember either the detection or the resulting commanded retardation being available through one of the 0x22 or manufacturer specific PIDs - I'll have a look through my notes later and check I wasn't imagining things. I know the accuracy or sensitivity of the detector is in dispute but it's worth a shot, if it can be read that is.