Tuner Studio / Shadow dash / over run at idle

For discussion of other tuning and logging softwares

Moderators: jsmcortina, muythaibxr

87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Tuner Studio / Shadow dash / over run at idle

Post by 87quest-TSI »

Hi,

Tonight after logging the drive home I was looking at the last page on Shadow dash and I see a yellow flash so I look closer to see what it says.
It's a processor error. what dose this mean? Is it with the mega squirt processor or the processor on my phone?
I'm guessing it's something with the mega squirt tough, so how do I find out whats causing this?

Thanks
Last edited by 87quest-TSI on Fri Dec 19, 2014 5:08 pm, edited 1 time in total.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Shadow dash / processor error

Post by LT401Vette »

Are you sure it wasn't a "Protocol Error" flashing?
That means there are errors in the data being sent or received by SD or MegaSquirt.
If it is staying online, then the errors are being handled in the retries, but it may causes pauses in your gauges and data logs.

The AppDebug.txt in the /ShadowDash MS/ dir would tell what errors are occurring.

What type of communication are you using? USB or Bluetooth? If Bluetooth, what BT Adapter are you using?
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Re: Shadow dash / processor error

Post by 87quest-TSI »

LT401Vette wrote:Are you sure it wasn't a "Protocol Error" flashing?
That means there are errors in the data being sent or received by SD or MegaSquirt.
If it is staying online, then the errors are being handled in the retries, but it may causes pauses in your gauges and data logs.

The AppDebug.txt in the /ShadowDash MS/ dir would tell what errors are occurring.

What type of communication are you using? USB or Bluetooth? If Bluetooth, what BT Adapter are you using?
Hi Phil,

I'm using bluetooth. not sure what brand it is. I've been using it for years now. It's translucent green if that helps. I'll look to see if theirs any #'s on it.
Now I have been seeing slow downs in data rate when I'm using tuner studio, but only at idle. as soon as rpm's go up to about 1100 the data rate stays steady and it happens weather I'm using bt or usb.

Thanks for your help.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Shadow dash / processor error

Post by LT401Vette »

Are you seeing Protocol Errors in TS too?
It is easier to debug there.
Under the Tools Menu, TS will show what type of Protocol Errors you are getting.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Re: Shadow dash / processor error

Post by 87quest-TSI »

LT401Vette wrote:Are you seeing Protocol Errors in TS too?
It is easier to debug there.
Under the Tools Menu, TS will show what type of Protocol Errors you are getting.
I'm getting overrun and every now and then the protocol error go's to 1 then back to 0. This happens below 1000 rpm's.
over 1000 rpm's it's good.
More I watch it, the protocol error happens at the same time as the overrun.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Re: Shadow dash / processor error

Post by 87quest-TSI »

87quest-TSI wrote:
LT401Vette wrote:Are you seeing Protocol Errors in TS too?
It is easier to debug there.
Under the Tools Menu, TS will show what type of Protocol Errors you are getting.
I'm getting overrun and every now and then the protocol error go's to 1 then back to 0. This happens below 1000 rpm's.
over 1000 rpm's it's good.
More I watch it, the protocol error happens at the same time as the overrun.
So is this something I need to figure out and fix or is this kinda normal?
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Shadow dash / processor error

Post by LT401Vette »

You really shouldn't get them often. Some wheel decoders have caused this more frequently. Usually it is at higher RPMs, not idle though.
The beta TS doesn't pause so long when it happens, the next SD will handle it the same as the beta TS.

A TunerStudioAppDebug.txt with comm debug turned on will help get better detail.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Re: Shadow dash / processor error

Post by 87quest-TSI »

Here's a debug file from today.
I really don't know what to look for or what it all means, but it dose look to me that theirs some kind of problem going on.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Shadow dash / processor error

Post by LT401Vette »

You do have a very high rate of over-runs being reported.

To determine if it is related to your BT Adapter, Is it similar when using a serial port, USB to Serial or real serial?
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Re: Shadow dash / processor error

Post by 87quest-TSI »

LT401Vette wrote:You do have a very high rate of over-runs being reported.

To determine if it is related to your BT Adapter, Is it similar when using a serial port, USB to Serial or real serial?
Oh I guess I should have said that this was with using the usb to serial adapter.
I do have another usb to serial adapter that I can try to see if it's the same.
It dose do it when I use BT as well.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Re: Shadow dash / processor error

Post by 87quest-TSI »

Here's another debug file with the other usb to serial adapter that I have.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Shadow dash / processor error

Post by LT401Vette »

It looks pretty much the same.
I'm not sure why you are getting so many Over-runs, perhaps James has some input.
This should probably be moved over to the MS2 Extra forum.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Re: Tuner Studio / Shadow dash / over run at idle

Post by 87quest-TSI »

Yesterday I did disconnect the alternator to see if that made a difference and It did not make a difference.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Tuner Studio / Shadow dash / over run at idle

Post by LT401Vette »

One other thing I can think of is, do you have both the BT adapter and USB connected? Even if only using one, I do often times get errors on an MS3 (Has onboard USB and a DB9) if talking to the USB and the BT adapter is connected to the DB9.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Re: Tuner Studio / Shadow dash / over run at idle

Post by 87quest-TSI »

LT401Vette wrote:One other thing I can think of is, do you have both the BT adapter and USB connected? Even if only using one, I do often times get errors on an MS3 (Has onboard USB and a DB9) if talking to the USB and the BT adapter is connected to the DB9.
Nope. I use one or the other.
The BT adapter that I use is the one that you sell.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Tuner Studio / Shadow dash / over run at idle

Post by LT401Vette »

At this point this appears to be a firmware issue. I would post in the MS2 Extra sections.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
jsmcortina
Site Admin
Posts: 39587
Joined: Mon May 03, 2004 1:34 am
Location: Birmingham, UK
Contact:

Re: Tuner Studio / Shadow dash / over run at idle

Post by jsmcortina »

There are two issues.
1. why so many overruns - I'll have a look.
2. why does TS go offline when it sees an overrun.

James
I can repair or upgrade Megasquirts in UK. http://www.jamesmurrayengineering.co.uk

My Success story: http://www.msextra.com/forums/viewtopic ... 04&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
New users, please read the "Forum Help Page".
jsmcortina
Site Admin
Posts: 39587
Joined: Mon May 03, 2004 1:34 am
Location: Birmingham, UK
Contact:

Re: Tuner Studio / Shadow dash / over run at idle

Post by jsmcortina »

OK, so I had a look at that log.
Seems there are over-runs about 1% of the time

Code: Select all

12/19/14 2:26:28 PM :Warning: Controller Reported an Over-run
...
12/19/14 2:26:28 PM :Debug: call failed protocol validation, running stats: 56 failed validation, 5559 successful.
That doesn't seem too bad. The ECU's top priority is running the engine and if it is busy it may be late servicing the serial interrupt.

In this log, TS 2.6.04 is retrying (good) but it looks to be pausing.

Code: Select all

12/19/14 2:26:28 PM :Debug: Protocol reported error after write 0x81, waiting 450ms and retry 
There's no need to wait half a second, immediate retries should be ok.

I'm not sure if it is possible, but a useful action would be to insert a small inter-character delay as that's where the over-run is occurring.

In other testing here today, I found that TS 2.6.11 was not retrying after over-run and was going offline.

Code: Select all

22/12/14 19:45:24 :Time: 4:26.076: Received, 3 bytes
x00 x01 x81                                                           ...

22/12/14 19:45:24 :Warning: Controller Reported an Over-run
22/12/14 19:45:24 :Time: 4:26.076: Received, 4 bytes
x48 xBD x5C x3B                                                       H.\;

22/12/14 19:45:24 :Debug: call failed protocol validation, running stats: 1 failed validation, 2309 successful.
22/12/14 19:45:24 :Time: 4:26.076: Response packet reported failure., 7 bytes
x00 x01 x81 x48 xBD x5C x3B                                           ...H.\;

22/12/14 19:45:24 :Debug: goOffline Starting, Time:0
22/12/14 19:45:24 :Info: Deactivated Turbo Baud, goOffline
James
I can repair or upgrade Megasquirts in UK. http://www.jamesmurrayengineering.co.uk

My Success story: http://www.msextra.com/forums/viewtopic ... 04&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
New users, please read the "Forum Help Page".
87quest-TSI
Helpful MS/Extra'er
Posts: 118
Joined: Sat Jun 11, 2005 9:59 pm
Location: North Alabama

Re: Tuner Studio / Shadow dash / over run at idle

Post by 87quest-TSI »

If theirs anything I can do or try to help figure this out let me know.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Tuner Studio / Shadow dash / over run at idle

Post by LT401Vette »

In Shadow Dash you can add an interwriteDelay in preferences, all the way at the bottom.

In TunerStudio, you will need to edit your ini file.

To do so, edit the file:
[YourTunerStudioProject]/projectCfg/mainController.ini

Search for
tsWriteBlocks = on

Add a ; to the beginning of that:
;tsWriteBlocks = on

That will comment that out and TS will include a short delay between each byte written.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
Post Reply