Actually danl has posted religiously in the ecuflash forum for a long time and has donated a lot of valuable knowledge of what he has learned over the years. So saying he is following you around is a blatant attack at him.......just want to clear that up.

And to be on topic here......

It seems the majority of the issues surrounding evoscan are with EvoX and/or the OP2.0 cables. I run the original tactrix 1.3 cable and to date I have no issues with evoscan on my IX, even on vista 64-bit (other than serial wideband logging). I am also running the latest beta 2.6, but your issues differ as you are on a completely different platform and/or cable that I do not use.

When claiming issues with software you really should try and be more specific so it doesn't make other people believe something isn't working or causing a computer to break. Also keeps **** storms from starting as well .

 

...........Anyway; by disabling the multithreading I was able to get a perfect log (fast!) for the EVO 8 using the 2.0 cable, but not for the Subaru using the 1.3 cable, logging is still about once every .5 seconds. BTW: the Subie in question is an 03 2.5RS. I haven't had a chance to check logging speed for the 2.0 cable on the EVO X, the car I was using for testing is down at the moment.

 

Thanks for clarifying what car and what cable you are having troubles with.

 

any updates hamish ??

 

i'm having problems with the map tracer showing data. The sample logs show everything, but when i do a new log, then try to open it in the map tracer, it show nothing.
Already upgraded to 2.6.
Any help please.

 

I will be adding new EvoX dataitems soon. Such as Boost (MAP) and also Knock Sum and making the CAN openport 2.0 logging faster. Are there any other requests for DataItems you need?

 

I think I will disable multithreading by default. its nothing but trouble hehe.

 

Hey Hamish, have you been in contact with tephra? He was saying that maybe dumping the CANXX stuff and going to direct PIDs would be better for the EvoX.

 

 

Hi SiC, The CAN protocol must talk on a shared BUS. So it doesn't make sense to go direct to the PIDs because the physical connection does not support this. But we can go via CAN direct to the RAM for any information in the EVOX ecu. Support for this will be in EvoScan v2.6 beta13.

 

I see, well I hope to see beta13 soon

Thanks,
SiC

 

are we going to see anything new for the gps logger in the near future?

 

any pictures of the units in the car? custom or using the stock suction cup mount doesn't matter.

 

yes, EvoScan GPS Navigator v1.4 is in development.

 

I don't have any pics of it in my car. Perhaps someone on here with a unit can take some pictures for us.