EvoScan v2.6 And New EvoScan GPS/Logger/Reflashing Touchscreen Review
Why is this so difficult. Cant it be made retard proof? Where can I get these FTDI drivers that it says i don't have that i know i installed? I'm doing this exactly as you say but no matter what I get an error upon starting evoscan, then then i put 500000 in baudrate i get another error. then it says evoscan has stopped working epic fail you suck then closes. its getting really frustrating. why do you need to be a damn rocket scientist to figure this out. It says my data xml is damaged or out of date, among other errors it gives me.
Last edited by jmorris1027; Apr 12, 2009 at 11:07 AM.
Evolving Member
Joined: May 2007
Posts: 208
Likes: 0
From: Europe
Can somebody help me with baud rate setup?
The problem appears, when I wanna use beta11 with OP 2.0 cable. With OP 1.3 I can log quite fast, but when I choose OP 2.0 and 62500 baud rate my logging is very slow(pic attached):
As far as I understand, I need 3 things to setup:
1) mods in rom/xml files
2) baud rate for OP 2.0 vable in device manager
3) Evoscan setup
What can be wrong?
P.S. I'm using 90550001
The problem appears, when I wanna use beta11 with OP 2.0 cable. With OP 1.3 I can log quite fast, but when I choose OP 2.0 and 62500 baud rate my logging is very slow(pic attached):
As far as I understand, I need 3 things to setup:
1) mods in rom/xml files
Code:
<scaling name="BAUDRATE" units="units" toexpr="500000/(x+1)" frexpr="500000/x-1" format="%.0d" min="0" max="500000" inc="1" storagetype="uint8" endian="big" /> <table name="BAUDRATE1_OBD" address="ce3d" type="1D" level="1" scaling="BAUDRATE" /> <table name="BAUDRATE2_MUT" address="ce71" type="1D" level="1" scaling="BAUDRATE" /> <table name="BAUDRATE3_unknown" address="ce81" type="1D" level="1" scaling="BAUDRATE" />
57600 ???
OP 2.0 radio button + 62500 baud rate + superspeed logging
P.S. I'm using 90550001
GST motorsports I gotta love your negativity:
"So where you even logging the above items last month?"
"kind of useless at this point"
EvoScan is always the best datalogging software for Mitsubishi, just happened that PCMScan fluked it by having generic CAN support, you just wait and see, EvoScan will surpase PCMScan by miles.
Yes please test it, link is above in POST#1, there have been no comments made by you about the accuracy on the current version and requests, so you are saying they work ok? that is a huge step forward if it even logs something, considering its the first version I've ever programmed CAN protocol. Can you compare it between PCMscan and tell me if the values are perfectly the same? If so, thats excellent, its a basis for extending it beyond the generic scantools, which EvoScan always does.
"So where you even logging the above items last month?"
"kind of useless at this point"
EvoScan is always the best datalogging software for Mitsubishi, just happened that PCMScan fluked it by having generic CAN support, you just wait and see, EvoScan will surpase PCMScan by miles.
Yes please test it, link is above in POST#1, there have been no comments made by you about the accuracy on the current version and requests, so you are saying they work ok? that is a huge step forward if it even logs something, considering its the first version I've ever programmed CAN protocol. Can you compare it between PCMscan and tell me if the values are perfectly the same? If so, thats excellent, its a basis for extending it beyond the generic scantools, which EvoScan always does.
I have no questions that EvoScan will be better than a generic logger, I've been a EvoScan user since your first beta version way way back when.
-Bryan
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
I've successfully gotten it to log with the IX, but it is amazingly slow. Too slow to see anything from the log. I haven't upped the baud rate though, i'll try and see if that helps out.
I just tested it out on an EvoX. Not all parameters that were checked by default worked.
Battery level, tps, engine speed, fuel trim (LTFT), and O2 feedback (STFT) seemed to work fine.
Injector Pulse Width didn't seem to work (stayed at 0ms)
IGN timing advance (-20) & Air temp (156.2 F) showed strange numbers
Battery level, tps, engine speed, fuel trim (LTFT), and O2 feedback (STFT) seemed to work fine.
Injector Pulse Width didn't seem to work (stayed at 0ms)
IGN timing advance (-20) & Air temp (156.2 F) showed strange numbers
Ok, can anyone help with this problem. I have a long file but I keep getting errors when I try to access it or load it. I even made another copy of the file and still came up with errors. Additionally, the sample log file will not load.
This is using the new beta.
This is using the new beta.
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
You might be better looking at the CAN registers/instructions in the ECU as a starting point for tracing the CAN stuff...
There was only 1 place that the ECU refers to the MUT_TABLE, so I don't think there will be a MUT->CAN or vice-versa translation.
Hamish - Where/how did you come up with your current list of CAN ids -> logging item?
There was only 1 place that the ECU refers to the MUT_TABLE, so I don't think there will be a MUT->CAN or vice-versa translation.
Hamish - Where/how did you come up with your current list of CAN ids -> logging item?
rogue - reboot, looks like a previous process or excel has gotten your log file OPEN already... as per error message.
mrfred - not yet, fracking paper work going around in circles... maybe this week. I might look at your tables today...
mrfred - not yet, fracking paper work going around in circles... maybe this week. I might look at your tables today...
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
What color?