EvoScan v2.6 Beta11 now supports EvoX and OpenPort2.0 datalogging
Newbie
Joined: Sep 2003
Posts: 9
Likes: 0
From: Jersey, Channel Islands
Evo X Logging on EvoScan v2.6 Beta 11
Hi guys,
Is there a way to log the boost pressure on the X's or is that still in progress? I can't see an item to tick that monitors it - Barometer is the closest i can find and i presume thats just monitoring atmospheric pressure.
Cheers!
Is there a way to log the boost pressure on the X's or is that still in progress? I can't see an item to tick that monitors it - Barometer is the closest i can find and i presume thats just monitoring atmospheric pressure.
Cheers!
Evolved Member
Joined: Oct 2002
Posts: 2,788
Likes: 1
Exact same problem for me. 1.3 cable works flawless. 2.0 cable regardless of baud rate samples only about 1 per second or less. I'm on 2.6beta11.. XP SP3.
Would appreciate some help on this. Of course I only log a small handful of data items, I don't log to screen, don't have any guage or dashboards up, etc... just log to file.
Would appreciate some help on this. Of course I only log a small handful of data items, I don't log to screen, don't have any guage or dashboards up, etc... just log to file.
I'm having an issue logging in an EVO 8 with the 2.0 cable while using windows XP. I get logs maybe every 7 seconds. I only ticked the necessary tabs in order to properly tune such as rpm, timing, and knock sum (+ whatever evoscan needs to be on to run them), and I have logger super speed enabled with realtime data logging graph disabled. I also tried a 62500 baudrate and I'm seeing no difference.
Now with the 1.3 cable, there is absolutely NO problems logging the EVO 8. I still haven't had a chance to log an EVO X with the 2.0 cable. I should be able to get one tomorrow.
By the way: is there anything that can be done about the slow logging speed of Stiscan?
UPDATE:
OK, I tried to log in an EVO X MR and I'm still having the same problem, under the same conditions but using 500000 baudrate. It only gives me a log once every second. Is there anything else I could do to make this work?
Also, a have a 1.8Ghz processor and 1.5GB of RAM, and I'm noticing the performance graph is in the upper 90% area when using the 2.0 cable.
Now with the 1.3 cable, there is absolutely NO problems logging the EVO 8. I still haven't had a chance to log an EVO X with the 2.0 cable. I should be able to get one tomorrow.
By the way: is there anything that can be done about the slow logging speed of Stiscan?
UPDATE:
OK, I tried to log in an EVO X MR and I'm still having the same problem, under the same conditions but using 500000 baudrate. It only gives me a log once every second. Is there anything else I could do to make this work?
Also, a have a 1.8Ghz processor and 1.5GB of RAM, and I'm noticing the performance graph is in the upper 90% area when using the 2.0 cable.
I'm having the same problem now that you metion it. It'll tell me the Open Port 2.0 is not responding when I try to pull codes (I don't have any). If I try to log right after I get this error, it'll give me the same "open port not responding" error. Logging works after the second attempt.
Hey crcain, I actually found an answer to this on another thread. In the logging tab, if you select "Disable Multithreading" that should solve your problems, however I'm still having slow logging issues with the Subies.
Exact same problem for me. 1.3 cable works flawless. 2.0 cable regardless of baud rate samples only about 1 per second or less. I'm on 2.6beta11.. XP SP3.
Would appreciate some help on this. Of course I only log a small handful of data items, I don't log to screen, don't have any guage or dashboards up, etc... just log to file.
Would appreciate some help on this. Of course I only log a small handful of data items, I don't log to screen, don't have any guage or dashboards up, etc... just log to file.
Evolving Member
Joined: Feb 2008
Posts: 214
Likes: 1
From: South Africa
A few quick questions...
Will this version support logging of 1byte Load from the start or do we have to do some tweaks for it to log 1Byte Load?
Like changes to the MUT table perhaps?
(I have set my 1Byte Load thingy to 1.3 in the TephraMod options of my 96530706 V7 ROM)
Also, does the MapTracer function work with 1byte Load logging on this version?
When I enable 1Byte Load logging, nothing shows up when I start the log.
2byte Load logs fine.
Thx.
Will this version support logging of 1byte Load from the start or do we have to do some tweaks for it to log 1Byte Load?
Like changes to the MUT table perhaps?
(I have set my 1Byte Load thingy to 1.3 in the TephraMod options of my 96530706 V7 ROM)
Also, does the MapTracer function work with 1byte Load logging on this version?
When I enable 1Byte Load logging, nothing shows up when I start the log.
2byte Load logs fine.
Thx.
Last edited by SeanV; May 26, 2009 at 01:44 AM.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
I used the MUTIII on the EvoX today, I got a whole lot of SST data, and some more EFI data. I will also program EvoScan this weekend so that it can do 2byte logging and will have faster datalogging for EvoX.
hey Hamish - as discussed on MSN, can you do the following:
1) fix the problem where the CAN response will jump down to 0 randomly
2) make sure the multiplexing is working, ie 1 CAN request, get all return bytes (ie CAN11-0 and CAN11-1 should be one request)
3) maybe get rid of the CANXX and just use the OBD PID, ie 0x2108, that way we can input any pid and not have to program in the CANXX into evoscan
4) 2byte response
I think thats about it for the next version
1) fix the problem where the CAN response will jump down to 0 randomly
2) make sure the multiplexing is working, ie 1 CAN request, get all return bytes (ie CAN11-0 and CAN11-1 should be one request)
3) maybe get rid of the CANXX and just use the OBD PID, ie 0x2108, that way we can input any pid and not have to program in the CANXX into evoscan
4) 2byte response
I think thats about it for the next version
it *should* be the same output as PID 0x010B (ie standard OBD PID 0x0B)
edit - actually 0x0B output looks like /2, so CAN6-0 is better anyways
Last edited by tephra; May 26, 2009 at 07:15 PM.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
How many people here have SST in their EvoX? I can put the SST logging into EvoScan if I get enough interest.
SST values such as:
Paddle Up
Paddle Down
Gear Position
Clutch 1 Temperature
Clutch 2 Temperature
SST values such as:
Paddle Up
Paddle Down
Gear Position
Clutch 1 Temperature
Clutch 2 Temperature
I would be very interested in all SST loggable functions for the track guys
Evolved Member
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Mode = 0xA0 PID = MUT_request
Baud rate is slower thou (10400).
I do not know how it translates to CAN requests as I am not that far with CAN ECU disassembly. Maybe one can try it out with CAN ECU and standard CAN tools.
Last edited by acamus; May 27, 2009 at 07:22 AM.
What do you mean?
As in using the 5baud init of 0xA0?
I have found all that controlling code, but because it's so vast I havn't been able to work it out properly.
I know that MUT_TABLE is still available via Serial, and I can change the baudrate so that's no problem
As in using the 5baud init of 0xA0?
I have found all that controlling code, but because it's so vast I havn't been able to work it out properly.
I know that MUT_TABLE is still available via Serial, and I can change the baudrate so that's no problem
Evolved Member
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Now if you are initialized and connection is build up for OBDII communication according to ISO9141, one can send Mode=A0, PID= MUT_RequestId to get value from MUT table. e.g. Mode A0 PID 26 for knock sum retrieval.
If they have retained the functionality with CAN then it would be helpful for X guys, but as I have said, I am not that far with CAN ECU disassembly yet to confirm it, and I have no mitsu CAN ECU around
