Mazdaedit
04-14-2013, 08:30 AM
#404
Registered
Join Date: Jan 2011
Posts: 43
Likes: 0
Received 0 Likes
on
0 Posts
we have 2 dozen tactrix OP 2.0 cables in stock, if anybody needs one.
Also looking for a crash test dummy for s2 testing in the san antonio area with ME. You buy a cable, we will tune your car for free in exchange for testeing and feedback on the files
04-15-2013, 06:38 AM
#407
Registered
Join Date: Jan 2011
Posts: 43
Likes: 0
Received 0 Likes
on
0 Posts
Yes, and we have your original read, but since I don't have the car here, it is almost impossible to use as a test subject. If you want to buy a copy of ME light, I will gladly send you files to test
04-18-2013, 08:14 PM
#409
Hmmmmmm.........
Join Date: Mar 2005
Location: Melbourne, Australia
Posts: 3,564
Likes: 0
Received 6 Likes
on
4 Posts
For those with an OP2, I have been working on a Standalone logging config file.
I have it mostly done with the exception of whenever I use the Actual AFR PID (0x34) I get some erratic results in other PIDs, the other PID that becomes erratic depends on where PID 34 is in my config file. I have logged this with Tactrix and will update as soon as I hear back. In the mean time, I have attached it for others use.
FYI, dont trust the Voltage field as I haven't finalised it and i think the problem above is interfering with it.
fueling_mode is 2 = Closed Loop, 4 = Open Loop. 8 and 16 seem to only show up on startup.
I have it mostly done with the exception of whenever I use the Actual AFR PID (0x34) I get some erratic results in other PIDs, the other PID that becomes erratic depends on where PID 34 is in my config file. I have logged this with Tactrix and will update as soon as I hear back. In the mean time, I have attached it for others use.
FYI, dont trust the Voltage field as I haven't finalised it and i think the problem above is interfering with it.
fueling_mode is 2 = Closed Loop, 4 = Open Loop. 8 and 16 seem to only show up on startup.
Last edited by auzoom; 04-18-2013 at 08:29 PM.
04-19-2013, 05:36 PM
#411
Hmmmmmm.........
Join Date: Mar 2005
Location: Melbourne, Australia
Posts: 3,564
Likes: 0
Received 6 Likes
on
4 Posts
Of what? Standalone logging? Its part of the OpenPort. Chuck an SD card in it, slam that file on the root of the SD card and plug the OP in. It will start logging as soon as rpm hoes above 100.
04-20-2013, 02:50 AM
#412
Registered
Many thanks for all your help with this auzoom.
Could that AFR issue explain why I was getting the -40 to 215 temp on the IAT?
I'll try that new file tomorrow, gonna see Tim Wednesday so I might get some advice from there.
Could that AFR issue explain why I was getting the -40 to 215 temp on the IAT?
I'll try that new file tomorrow, gonna see Tim Wednesday so I might get some advice from there.
04-20-2013, 07:11 AM
#415
Hmmmmmm.........
Join Date: Mar 2005
Location: Melbourne, Australia
Posts: 3,564
Likes: 0
Received 6 Likes
on
4 Posts
I was on my phone before so couldnt be bothered looking it up openecu.org • View forum - Openport Stand-Alone Logging Beta
06-28-2013, 11:20 PM
#416
For those with an OP2, I have been working on a Standalone logging config file.
I have it mostly done with the exception of whenever I use the Actual AFR PID (0x34) I get some erratic results in other PIDs, the other PID that becomes erratic depends on where PID 34 is in my config file. I have logged this with Tactrix and will update as soon as I hear back. In the mean time, I have attached it for others use.
FYI, dont trust the Voltage field as I haven't finalised it and i think the problem above is interfering with it.
fueling_mode is 2 = Closed Loop, 4 = Open Loop. 8 and 16 seem to only show up on startup.
I have it mostly done with the exception of whenever I use the Actual AFR PID (0x34) I get some erratic results in other PIDs, the other PID that becomes erratic depends on where PID 34 is in my config file. I have logged this with Tactrix and will update as soon as I hear back. In the mean time, I have attached it for others use.
FYI, dont trust the Voltage field as I haven't finalised it and i think the problem above is interfering with it.
fueling_mode is 2 = Closed Loop, 4 = Open Loop. 8 and 16 seem to only show up on startup.
I just tried it on an S2 and I don't get a reasonable value for RPM (it comes out as 81xx). Also, MAF voltage rather than calculated g/s would actually be more convenient for tuning if we can figure that out.
07-14-2013, 05:22 PM
#418
New Member
Join Date: Mar 2013
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
Has anyone tried Mazdaedit on a UK car? I had an error on doing an actual ECU read(even though it read the VIN etc.) which the developer couldn't figure out. In the end he refunded me but just wondering if anyone else has had better success?
07-15-2013, 03:11 PM
#419
Have no idea if this would have helped you but maybe for others who are having frustrations it might.
07-16-2013, 10:58 AM
#420
New Member
Join Date: Mar 2013
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
Thanks for the reply Brettus, do you have any specific tricks and did you ever get anything like the following?
[09:39:59.585] found OpenPort 2.0 (J2534) cable
[09:40:01.257] CAN init...
[09:40:01.304] ECU SW partnumber: XXXX
[09:40:01.335] ECU VIN: XXXXX
[09:40:01.398] can: invalid cmd response [7F1022]
[09:40:01.398] unable to read response #1
[09:39:59.585] found OpenPort 2.0 (J2534) cable
[09:40:01.257] CAN init...
[09:40:01.304] ECU SW partnumber: XXXX
[09:40:01.335] ECU VIN: XXXXX
[09:40:01.398] can: invalid cmd response [7F1022]
[09:40:01.398] unable to read response #1
07-16-2013, 11:26 AM
#421
Registered
Was your ECU ever flashed by another? Like Pettit? That's similiar to the errors I was getting when I tried to tune an ECU that had the Pettit flash on it.
I confirmed it wasn't a software issue by trying it on someone elses car that I knew was stock and it worked so I swaped ECU's and it fixed the problem.
thewird
I confirmed it wasn't a software issue by trying it on someone elses car that I knew was stock and it worked so I swaped ECU's and it fixed the problem.
thewird
07-16-2013, 12:27 PM
#422
Thanks for the reply Brettus, do you have any specific tricks and did you ever get anything like the following?
[09:39:59.585] found OpenPort 2.0 (J2534) cable
[09:40:01.257] CAN init...
[09:40:01.304] ECU SW partnumber: XXXX
[09:40:01.335] ECU VIN: XXXXX
[09:40:01.398] can: invalid cmd response [7F1022]
[09:40:01.398] unable to read response #1
[09:39:59.585] found OpenPort 2.0 (J2534) cable
[09:40:01.257] CAN init...
[09:40:01.304] ECU SW partnumber: XXXX
[09:40:01.335] ECU VIN: XXXXX
[09:40:01.398] can: invalid cmd response [7F1022]
[09:40:01.398] unable to read response #1
Haha, well I just tried my first flash, and got a write error 
Tried to upload the stock rom, no go. Tried to start the car, no go....
After some contemplation I managed to find the right combination to make it work:
1. Make sure the ignition is off
2. Unplug the openport from the usb port and make sure mazdaEdit is not running.
3. Plug the openport into the obd port. (no need to unplug, replug if it is already plugged in)
4. Turn ignition on
5. Plug in the openport to the usb port
6. Start mazdaEdit, start the flash utility (F11)
7. Hit the read information about ECU icon (F3)
8. Open the ECU rom image using the file open icon
9. Hit the write icon (F9)
10. Don't move or touch anything while it uploads the data.
With my part-written flash, step 7 was not able to read any information from the ecu, but I was still able to write the data successfully.
I'm sure there are other combinations that work, but there are also some that don't!
Tried to upload the stock rom, no go. Tried to start the car, no go....
After some contemplation I managed to find the right combination to make it work:
1. Make sure the ignition is off
2. Unplug the openport from the usb port and make sure mazdaEdit is not running.
3. Plug the openport into the obd port. (no need to unplug, replug if it is already plugged in)
4. Turn ignition on
5. Plug in the openport to the usb port
6. Start mazdaEdit, start the flash utility (F11)
7. Hit the read information about ECU icon (F3)
8. Open the ECU rom image using the file open icon
9. Hit the write icon (F9)
10. Don't move or touch anything while it uploads the data.
With my part-written flash, step 7 was not able to read any information from the ecu, but I was still able to write the data successfully.
I'm sure there are other combinations that work, but there are also some that don't!
07-16-2013, 04:10 PM
#423
Thanks for the reply Brettus, do you have any specific tricks and did you ever get anything like the following?
[09:39:59.585] found OpenPort 2.0 (J2534) cable
[09:40:01.257] CAN init...
[09:40:01.304] ECU SW partnumber: XXXX
[09:40:01.335] ECU VIN: XXXXX
[09:40:01.398] can: invalid cmd response [7F1022]
[09:40:01.398] unable to read response #1
[09:39:59.585] found OpenPort 2.0 (J2534) cable
[09:40:01.257] CAN init...
[09:40:01.304] ECU SW partnumber: XXXX
[09:40:01.335] ECU VIN: XXXXX
[09:40:01.398] can: invalid cmd response [7F1022]
[09:40:01.398] unable to read response #1
close down the program and re-open
Close down the laptop and restart
unplug the usb cord and plug it in somewhere else
Curse the programmer using every profanity in my vocabulary
Then
try all of the above in reverse order back to front and sideways ................... eventually ................IT works !!!!!!!!!
07-16-2013, 04:52 PM
#424
Bikes are Rotaries
Join Date: Feb 2013
Location: Kerikeri, NZ
Posts: 303
Likes: 0
Received 0 Likes
on
0 Posts
Can't be 100% sure but I do think I've had that error or something similar. All I do is stuff like :
close down the program and re-open
Close down the laptop and restart
unplug the usb cord and plug it in somewhere else
Curse the programmer using every profanity in my vocabulary
Then
try all of the above in reverse order back to front and sideways ................... eventually ................IT works !!!!!!!!!
close down the program and re-open
Close down the laptop and restart
unplug the usb cord and plug it in somewhere else
Curse the programmer using every profanity in my vocabulary
Then
try all of the above in reverse order back to front and sideways ................... eventually ................IT works !!!!!!!!!
