Evo X Logging
#874
I had mode 23 stop working with evoscan 2.7beta5 the other day. All the values don't change when I hit start logger with ecu "mode23 usa evo x" selected.I uninstalled/reinstalled, and it's doing the same thing. The tactrix cable and connector are working fine because when I switch to ecu "evo x" (non-mode 23) it logs fine, with values switching regularly; also ecuflash works. My other thread got ignored, so can mfred, tephra, or evo4mad help out? Below is a screen shot of what the values are stuck at every time I hit log with ecu "mode23usaevox" selected. Note, those values always read those same numbers when I hit start.
Last edited by boostin20; Jan 3, 2010 at 11:47 AM.
#875
I had mode 23 stop working with evoscan 2.7beta5 the other day. All the values don't change when I hit start logger with ecu "mode23 usa evo x" selected.I uninstalled/reinstalled, and it's doing the same thing. The tactrix cable and connector are working fine because when I switch to ecu "evo x" (non-mode 23) it logs fine, with values switching regularly; also ecuflash works. My other thread got ignored, so can mfred, tephra, or evo4mad help out? Below is a screen shot of what the values are stuck at every time I hit log with ecu "mode23usaevox" selected. Note, those values always read those same numbers when I hit start.
#876
I'm not sure what you're talking about with tephra's app. If I can read/write to ecu with ecuflash and in evoscan log with just "evoX" ecu selected, do you really think the cable/connector or ecu is to blame?
#877
It's hard to say what your problem is with little info that you posted, that's why the first step is to confirm that Evoscan IS infact the problem.....
#878
First of all, SIC thanks for helping me out. I downloaded and logged a quick trip down the street with tephra's logger. Below is what came out of it. I tried to attach it, but the attachment restrictions are retarted. I put a screenshot below. there's another 18 pages, but the two left rows only show up.
It makes me think there's an issue with the tactrix connector (switched usb cables-no difference), but the whole ecuflash still working for reading/writing is confusing me.
Btw, since you're saying I'm not giving much info to help troubleshoot, tell me what I need to provide, and I'll be glad to post anything up.
It makes me think there's an issue with the tactrix connector (switched usb cables-no difference), but the whole ecuflash still working for reading/writing is confusing me.
Btw, since you're saying I'm not giving much info to help troubleshoot, tell me what I need to provide, and I'll be glad to post anything up.
Last edited by boostin20; Jan 3, 2010 at 03:51 PM.
#879
Okay, so now it seems like the problem is either hardware related or something may be wrong with your ROM. Did you recently change anything in your ROM prior to this?? Something may have disabled mode23 logging by changing one of your maps.
Try this, backup your current ROM and get a clean virgin ROM of the same ROM ID. Enable mode23 in the virgin ROM and write it to your ECU. See if you can log correctly, if all is well, there maybe something you changed in the ROM that disabled mode23.
Try this, backup your current ROM and get a clean virgin ROM of the same ROM ID. Enable mode23 in the virgin ROM and write it to your ECU. See if you can log correctly, if all is well, there maybe something you changed in the ROM that disabled mode23.
#880
Okay, so now it seems like the problem is either hardware related or something may be wrong with your ROM. Did you recently change anything in your ROM prior to this?? Something may have disabled mode23 logging by changing one of your maps.
Try this, backup your current ROM and get a clean virgin ROM of the same ROM ID. Enable mode23 in the virgin ROM and write it to your ECU. See if you can log correctly, if all is well, there maybe something you changed in the ROM that disabled mode23.
Try this, backup your current ROM and get a clean virgin ROM of the same ROM ID. Enable mode23 in the virgin ROM and write it to your ECU. See if you can log correctly, if all is well, there maybe something you changed in the ROM that disabled mode23.
#881
So I am looking at the ActiveWGDC Correction RequestID for the 2008 Evo X. The Wiki Says that the ID is at row 8 column B, but that loaction gives an 80876D. However, the Evoscan Data.xml shows 808B51. I have logged WGDCC with it successfully.
Is the location that the wiki gives for WGDCC incorrect?
Is the location that the wiki gives for WGDCC incorrect?
#882
Okay, so now it seems like the problem is either hardware related or something may be wrong with your ROM. Did you recently change anything in your ROM prior to this?? Something may have disabled mode23 logging by changing one of your maps.
Try this, backup your current ROM and get a clean virgin ROM of the same ROM ID. Enable mode23 in the virgin ROM and write it to your ECU. See if you can log correctly, if all is well, there maybe something you changed in the ROM that disabled mode23.
Try this, backup your current ROM and get a clean virgin ROM of the same ROM ID. Enable mode23 in the virgin ROM and write it to your ECU. See if you can log correctly, if all is well, there maybe something you changed in the ROM that disabled mode23.
I got my battery and flashed with a new map no previously saved on my computer. Mode 23 worked after that. Thanks, for the help SIC.