ECUFlash / Evoscan / Mitsulogger Questions
#436
#437
ecuflash
hi guys,
noticed on ecuflash that the list on the left (with the check box's) each one is written in black text.
some are 'greyd' out - these obviously haven't been opened and can't be used.
but some I have (mainly being the ALS tables are in blue text.......why is this?......I can open these up and adjust settings but am wondering if they are actually activated/working?
thanks for the help.
Mark.
noticed on ecuflash that the list on the left (with the check box's) each one is written in black text.
some are 'greyd' out - these obviously haven't been opened and can't be used.
but some I have (mainly being the ALS tables are in blue text.......why is this?......I can open these up and adjust settings but am wondering if they are actually activated/working?
thanks for the help.
Mark.
#438
Quesion: Recently, and for NO reason my laptop decided it won't connect to the ecu in any way. It won't read from, or write to the ecu. It read from another local guys car here, but only after trying 4-5 times. I am running XP and Vista in a dual boot. Neither will connect. It worked totally fine yesterday. I'm dialing in injectors, and flashing new latencies. That's it...any ideas??
#439
Quesion: Recently, and for NO reason my laptop decided it won't connect to the ecu in any way. It won't read from, or write to the ecu. It read from another local guys car here, but only after trying 4-5 times. I am running XP and Vista in a dual boot. Neither will connect. It worked totally fine yesterday. I'm dialing in injectors, and flashing new latencies. That's it...any ideas??
Last edited by D-VO; Sep 28, 2008 at 09:29 AM. Reason: sentence fragment
#440
Have any of you guys tried to mess with the baudrate for ECUflash/evoscan? I had done the modification for the baudrate last year on another version of ECUflash that has since been deleted. However, with the new version 1.38, no matter where I try to set the baudrate, EVOscan will only work with 62500. This one's really wierd.
#441
I used to do the 62500 ROM modification but I set it back to 15625. Didn't see enough of a difference to bother with it. If evoscan only works with 62500, that means your ROM is set for 62500. You need to reset your ROM back to 15625 to log evoscan at 15625.
#442
#443
I'm not sure if it has something to with changing the code, flashing it to the ECU, then deleting ecuflash and re-installing a newer version. See? The only thing I changed was upgraded to a newer version of ECUflash.
Last edited by D-VO; Sep 28, 2008 at 09:52 AM. Reason: left out some info
#445
#446
Where in ECUflash do you check the baud rate?
-This wouldn't entirely make since. Another laptop with the same baudrate on evoscan (15625) is working on my car.
Last edited by Tx4Codeman; Sep 30, 2008 at 07:56 PM.
#447
Did you try evoscan 2.5 on your XP OS? I remember seeing a thread somewhere with someone else having a problem with vista. I'll see if I can find it.
#448
Yes. I was using the tactrix cable when we removed the power locks fuse. Neither evoscan or ECUflash works without the power locks fuse in.
Did you try evoscan 2.5 on your XP OS? I remember seeing a thread somewhere with someone else having a problem with vista. I'll see if I can find it.
Did you try evoscan 2.5 on your XP OS? I remember seeing a thread somewhere with someone else having a problem with vista. I'll see if I can find it.
Under your logging tab, Select Usb/Com/Elm, is COM1 stuck checked? I can have my tactrix plugged into 'com4', but am not able to select it. Meanwhile, under USB, tactrix 1.3b is selected. Oi.
#449
i'm having no luck getting evoscan to work either. ECUFlash is connecting/reading fine though which is weird.
the ONLY way I can get EVOScan 2.5 to connect is if I check one of the WB boxes and leave all the other parimeter unchecked. then it will connect and log the WB channel even though I don't have a WB hooked up to the computer. if I attempt to check any of the other boxes like TPS or RPM it won't connect. anyone have any ideas????
the ONLY way I can get EVOScan 2.5 to connect is if I check one of the WB boxes and leave all the other parimeter unchecked. then it will connect and log the WB channel even though I don't have a WB hooked up to the computer. if I attempt to check any of the other boxes like TPS or RPM it won't connect. anyone have any ideas????
#450
Need a little help guys
Ok I have my wideband pinned to my ECU for logging. Rear O2 disabled obviously
So I had to mod the XML in EVOSCAN with this line IIRC and enter my formula for my wideband
<DataListItem DataLog="Y" Color="" Display="Wideband AFR" LogReference="WideBand" RequestID="12" Eval="0.0274*x + 9.0" Unit="AFR" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="22" ChartMin="0" ChartMax="22" ScalingFactor="1" Notes="" Priority="1" Visible="false" />
My question is can I do this in Mitslogger? If so, is the text line the same as EVOSCAN? What is it? Where in the XML do I insert it?
THNKS GURUS
Ok I have my wideband pinned to my ECU for logging. Rear O2 disabled obviously
So I had to mod the XML in EVOSCAN with this line IIRC and enter my formula for my wideband
<DataListItem DataLog="Y" Color="" Display="Wideband AFR" LogReference="WideBand" RequestID="12" Eval="0.0274*x + 9.0" Unit="AFR" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="22" ChartMin="0" ChartMax="22" ScalingFactor="1" Notes="" Priority="1" Visible="false" />
My question is can I do this in Mitslogger? If so, is the text line the same as EVOSCAN? What is it? Where in the XML do I insert it?
THNKS GURUS