MUT at high baudrates WORKS! 62500 tested.

Reply Subscribe

Thread Tools

Search this Thread

Apr 1, 2009 | 04:18 PM

#61

shadow1

Evolved Member

iTrader: (38)

Joined: Feb 2005

Posts: 660

Likes: 0

From: Laurel, MD

FYI the 62500 baud rate is not Logworks compatible. I tried maxing my MUT baud rate on my 96940011 rom. I use Logworks, and the openport plug in would not connect at that speed. I had to keep the baud rate at the stock rate.

Apr 2, 2009 | 02:15 AM

#62

R. Mutt

Evolving Member

Joined: Feb 2006

Posts: 264

Likes: 6

From: Vancouver, BC

Quote:

Originally Posted by bez_bashni

2 MORE patched definitions.

Thanks for posting this.

Quick question: In the definition for 90550001 I see the following tables in addition to the 3 baud rates:

Code:

<table name="MInIdleRpm" address="198d" type="1D" level="1" scaling="RPM8"/>

	<table name="MAXIDLERPM" address="2209" type="1D" level="1" scaling="RPM8"/>

	<table name="IDLE_RPM_ADDITION_DRIVE" address="197f" type="1D" level="1" scaling="RPM8"/>

	<table name="IDle_RPM-Adition_NEUTRAL" address="197d" type="1D" level="1" scaling="RPM8"/>

	<table name="IGN_RELATED_FORK_MIN" category="Timing" address="1631f" type="1D" level="1" scaling="uint8"/>

	<table name="IGN_RELATED_FORK_MAX" category="Timing" address="1631d" type="1D" level="1" scaling="uint8"/>

	<table name="REAL_PULSE_MACHINE_CODE_E0" category="Misc" address="16db8" type="1D" level="1" scaling="Hex8"/>

	<table name="REAL_PW_MACHINE_CODE_value" address="16db9" type="1D" level="1" scaling="Hex8"/>

	<table name="IGNITION_FINAL3_MCODE_E0" category="Misc" address="16324" type="1D" level="1" scaling="Hex8"/>

	<table name="IGNITION_FINAL3_DATA (10-70)" category="Misc" address="16325" type="1D" level="1" scaling="uint8"/>

Could you tell explain what those tables do. I've never seen or heard of them before and the table names aren't very descriptive.

Apr 2, 2009 | 04:29 PM

#63

lan_evo_mr9

Evolved Member

iTrader: (10)

Joined: Feb 2006

Posts: 1,097

Likes: 2

From: MD

anything for 88590015? Can you raise the "stock" baud rate higher than default? My logging seems really slow for some reason. When I open the excel spread sheet, I'm barely getting a sample every 600 rpms during a pull.

Apr 2, 2009 | 04:35 PM

#64

tephra

EvoM Guru

iTrader: (6)

Joined: Feb 2007

Posts: 9,486

Likes: 67

From: Melbourne, Australia

how many items are you logging?

i was logging so quick that I often had multiple lines with the same RPM..

Apr 2, 2009 | 05:54 PM

#65

lan_evo_mr9

Evolved Member

iTrader: (10)

Joined: Feb 2006

Posts: 1,097

Likes: 2

From: MD

I'm only logging at most 8-10 items. I have cable selection to Evoscan USB cable with nothing else selected. I log 2 byte load, normal rpm, inj duty cycle, timing, knock, and a couple other key items. Nothing crazy. I have 5.10 installed and have my MUT table set to 2 byte stuff. I have your 2 byte to 1 byte set to 1.2. I have a text document saved that says evoscan1byte. Do I need to transfer that to the xml data for evoscan? I'm running Vista so it's a PITA to do simple stuff like this. Somehow I need to turn that text doc into an xml in order to save it. Is this the right train of thought?

Last edited by lan_evo_mr9; Apr 2, 2009 at 06:55 PM.

Apr 2, 2009 | 07:33 PM

#66

lan_evo_mr9

Evolved Member

iTrader: (10)

Joined: Feb 2006

Posts: 1,097

Likes: 2

From: MD

I added the definition for 1 byte load to evoscan dataxml and it isn't showing up in "loggable" items. Is this normal?

EDIT:
I was able to save the 1 byte definition to the data xml and switched the type of cable to "mitsubishi" and Evoscan USB. This resulted in extremely fast logging, but I still have a 300-500 rpm gap during a pull above 4K. It logs multiple entries when cruising for the same RPM just like Tephra said but still have the big gap when pulling. Any ideas or solutions would be greatly appreciated.

Last edited by lan_evo_mr9; Apr 2, 2009 at 07:53 PM.

Apr 2, 2009 | 08:02 PM

#67

lan_evo_mr9

Evolved Member

iTrader: (10)

Joined: Feb 2006

Posts: 1,097

Likes: 2

From: MD

Here is the excel sheet- go to line 1080ish and you will see what I'm talking about.

Attached Files

EvoScanDataLog_2009.04.02_22.37.25.zip (30.4 KB, 0 views)

Apr 2, 2009 | 08:43 PM

#68

black E

Evolved Member

iTrader: (77)

Joined: Mar 2007

Posts: 546

Likes: 45

From: Boca Raton FL

Apr 2, 2009 | 08:46 PM

#69

black E

Evolved Member

iTrader: (77)

Joined: Mar 2007

Posts: 546

Likes: 45

From: Boca Raton FL

Quote:

Originally Posted by thermaldynamics

I am making close to 100whp more than my friend so the extra logging rate comes in handy during a 3rd gear pull because it happens quicker. I am tuning my friends car and his power level will be approaching/ or atleast getting closer to mine and I will need the extra log speed to tune accurately without skipping to many load/rpm cells.

Thanks in advance guys.

Apr 2, 2009 | 08:49 PM

#70

tephra

EvoM Guru

iTrader: (6)

Joined: Feb 2007

Posts: 9,486

Likes: 67

From: Melbourne, Australia

no I mean on a pull I will get multiple lines with the same rpm.. of course cruising you will...

take a screenshot of your evoscan screen when logging - you prolly got the logging options wrong

Apr 3, 2009 | 05:00 AM

#71

lan_evo_mr9

Evolved Member

iTrader: (10)

Joined: Feb 2006

Posts: 1,097

Likes: 2

From: MD

How do you have your options set?

Apr 5, 2009 | 02:03 AM

#72

R. Mutt

Evolving Member

Joined: Feb 2006

Posts: 264

Likes: 6

From: Vancouver, BC

bump for my question

Apr 28, 2011 | 07:58 AM

#73

05blue8

Evolved Member

iTrader: (28)

Joined: Mar 2007

Posts: 843

Likes: 5

From: Austin, TX

I'm bumping this up because it's awesome detail and it just helped me out a TON (again). For anyone having connectivity/logging issues add the xml to your rom file and open your map, then see what was in there. This wasn't in my definition so I figured it was fine, I added it then opened the map and it was set to 62500 by the first tuner of this car I'm guessing. The big issue is that the samples are so fast I get inconsistent data and was never able to resolve this so slowing it back down worked

Apr 28, 2011 | 08:06 AM

#74

shadow1

Evolved Member

iTrader: (38)

Joined: Feb 2005

Posts: 660

Likes: 0

From: Laurel, MD

I played with higher baud rates a long time ago. It never worked for me. Screwed up my datalogging.

Dec 4, 2011 | 02:25 AM

#75

Danieln

Evolved Member

iTrader: (1)

Joined: Apr 2008

Posts: 563

Likes: 0

From: EUROPE

Different roms (log in 4th gear + same RPM interval)

LOG 1:

2438
2469
2531
2563
2625
2688
2750
2844
2938
3063
3188
3281
3438
3563
3656
3813
3906
4031
4188
4250
4406
4500
4625
4750
4844
4969
5094
5188
5344
5438
5531
5625
5750
5844
5938
6031
6156
6250
6313
6406
6500
6625
6688
6750
6844
6938
7000
7063
7156

LOG 2:

2563
2750
2969
3281
3531
3844
4156
4375
4688
4969
5250
5469
5719
5969
6219
6469
6688
6938
7094
7313

So where is the difference in resolution>?
This is not because of the baudrate in the rom.....

Reply Share

First
Prev
5 / 6
Next
Last