|
EvoScan for Evo X Beta Parameter CAN-ID's? Log attached
1 Attachment(s)
Hey all, I've been playing around with Evoscan v2.6 beta 11 to see if I can log my USDM GSR. I "think" I'm getting close, as I've changed some of the CAN ID's and made a log. However, some of the numbers seem like they're off. Can someone tell me how this second gear log looks? This is on a stock USDM GSR. The AbsLoad and AccLoad are both maxing out at 255 at WOT. Do any of the values I've logged make sense?
CAN ID's I changed: Timing Advance = 7-0 Injector Pulse Width = 8-0 Absolute Load = 20-1 (this is still wrong, as it maxes out at 255, but gives slightly different values than 20-0 and 21-0. Note that 20-0 and 21-0 give the same values so I left that as AccLoad = 21-0.) Airflow= 22-0 Also, I could not edit the CAN ID's through Evoscan as it would lead to a bunch of errors. I had to close Evoscan and manually edit the Data.xml file with Notepad. Second gear USDM GSR Log Attached (with factory reflash #2 ecu id 52680018) |
Thank you! Changing these now. I think the Load cap at 255 may be an issue with the CAN protocol or something. Or at least with how EvoScan is pulling values.
|
This came from the ECUFlash forum... Be careful with the Can x-x values. I have been messing with the Boost CAN ID as it also maxes out at 255. I haven't had any time to mess with the logging much lately to verify what he has posted below and how that affects each data item.
I found this after massaging the boost numbers in excel and combining multiple fields as CAN messages are often split to span 2 data fields to get around the 8 bit transmit limit. 8 bit maximum = 255. Now I am questioning the other fields.
Originally Posted by evo4mad
(Post 6925452)
I am out of the country on business till 22april, but until then here is EvoScan Beta11 for you guys to have a play with and give me some feedback.
EvoScan v2.6 beta 11 has support for OpenPort2.0 and support for EvoX (EvoX forumulas are still work in progress, perhaps you guys can take a look at some of them, I have ticked the ones that I have worked out so far) Excel version of my EvoX driving log for working out formulas: EvoScanBeta11EvoXLog.zip EvoScan v2.6 Beta11: (has a new Data.xml included, it contains the new EvoX CAN requests) download EvoScanUPGRADEv2.6Beta11.zip here If don't need EvoX dataitem support, and just after a version compatable with Openport2.0 without overwritting your existing data.xml formulas then you can download this version. download EvoScanUPGRADEv2.6Beta11_NoDataXML.zip here OpenPort2.0 + EvoX/CAN Notes: Select OpenPort2.0 radio button, select EvoX/CAN radio button, the baudrate is 500000, select ECU as EvoX To read some values from EvoX/CAN, you must change the trailing number. there is a possibility of 4 bytes that are returned from each CAN request, for example CAN0-0, CAN0-1, CAN0-2, and CAN0-3, then the sequence continues with CAN1-0, CAN1-1, CAN1-2, CAN1-3, CAN2-0, etc until CAN25-3 you will find CAN2-0 = CAN3-0 = CAN4-0 = CAN5-0 are the same, I just gave them a number that is in sequence for the dataitems. (etc, also CAN2-3 = CAN3-3 = CAN4-3 = CAN5-3) Tactrix have now run out of OpenPort2.0 cables, Colby is just waiting on a hard to source part from Germany, expect a 2-3 week delay, you can still order them from www.limitless.co.nz/cables, I have some low stock of OpenPort 2.0, and 100s of Openport1.3U and other cables in stock. |
There should not be load cap. I am logging with PCMScan and I have not experienced a load cap while logging load values. Something is wrong with the logging parameters. I am sure it will work out in the end once Hamish comes up with a full working version.
|
^+1
I've got WOT runs on the highway in 3rd using a slightly modified version of Gunzo's map that peaked out at 269 load. Here's hoping this gets (knock count) corrected soon so i can paypal Hamish my $25 |
Originally Posted by rfielder
(Post 6981482)
This came from the ECUFlash forum... Be careful with the Can x-x values. I have been messing with the Boost CAN ID as it also maxes out at 255. I haven't had any time to mess with the logging much lately to verify what he has posted below and how that affects each data item.
I found this after massaging the boost numbers in excel and combining multiple fields as CAN messages are often split to span 2 data fields to get around the 8 bit transmit limit. 8 bit maximum = 255. Now I am questioning the other fields. |
Wow, I wish I understood all this stuff. lol
|
Sweet we're getting close. I logged timing today and worked great although the log seemed a little slow. Got the job done.
|
So no idea on what the CAN request ID is for MAP/boost?
What potential is there to develop MUT-III support for EvoScan? Would that cover the Evo X? |
Originally Posted by WarmAndSCSI
(Post 6987955)
So no idea on what the CAN request ID is for MAP/boost?
What potential is there to develop MUT-III support for EvoScan? Would that cover the Evo X? We would neeed MUT-III support to get knock retard, and it didn't sound to me like that would happen anytime soon. |
I've been logging timing advance, but I don't think it's accurate. It doesn't drop nearly low enough. Who knows? Maybe I'm not in the load cells I think I am in.
IMHO EvoScan doesn't look promising for the Evo X unless we get MUT-III support. Are there any MUT-III loggers currently available? |
Originally Posted by WarmAndSCSI
(Post 6985132)
Care to share what the Boost CAN request is? :)
I used CAN 6-1 and 6-3. When I first logged it, I had no boost gauge so I could not verify if that was the correct request. I used added them together and offset for 0 when the engine was not running. I just dumped all of the data into Excel and then massaged it. Now that I have a working boost gauge, the "math" that I did was not accurate. I also feel that the CAN requests that I was using wasn't correct either. I need more time to further investigate the requests. Have you come up with anything? :D |
Originally Posted by WarmAndSCSI
(Post 6989338)
I've been logging timing advance, but I don't think it's accurate. It doesn't drop nearly low enough. Who knows? Maybe I'm not in the load cells I think I am in.
IMHO EvoScan doesn't look promising for the Evo X unless we get MUT-III support. Are there any MUT-III loggers currently available? |
Originally Posted by Guru
(Post 6992139)
Timing seems to work just fine for me. Dropping to around 14 and ramping up steadily to 22-23 or so.
|
Originally Posted by Guru
(Post 6992139)
Timing seems to work just fine for me. Dropping to around 14 and ramping up steadily to 22-23 or so.
|
| All times are GMT -7. The time now is 04:17 PM. |
© 2026 MH Sub I, LLC dba Internet Brands