Tuner Studio / Shadow dash / over run at idle

[87quest-TSI]

I played with this a bit yesterday and some today.

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

The interwrite Delay was set on auto.
when you make changes do you have to close shadow dash for them to take affect?
I saw no real change when I made changes from the min to the max of 40ms, but I didn't close and restart between changes.
I was still getting random processor errors. I just tried it again to today and same thing.

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.

I made the changes in tunerStudio (;tsWriteBlocks = on) and it made little to no difference.
I did try it with the BT and usb.
Here is a new debug file with this change made using usb.

[LT401Vette]

Actually... It occurred to me that in ShadowDash you would have to edit the ini to turn off tsWriteBlocks also or the interWriteDelay has no effect.

On the PC you might need to increase the interWriteDelay in the ini if you are still seeing no effect, but I would thing just turning it off would make the difference.

[87quest-TSI]

On the PC you might need to increase the interWriteDelay in the ini if you are still seeing no effect, but I would thing just turning it off would make the difference.

Not sure if i'm doing something wrong or not, but how much Delay might I have to add?
I stared from what it was and went as high as 100 in steps of 10 with no significant change.
Should I go higher?
When I was testing I was using BT with tuner studio.

[LT401Vette]

The interWriteDelay setting in Shadow Dash won't work unless you edit the ini file to turn tsWriteBlocks off
Once tsWriteBlocks is turned on, there is no interWriteDelay used, ts or SD will write full arrays to the buffer so they will be sent as fast as possible.

On your device go into the dir:
/Shadow Dash MS/MS3/projectCfg/

Edit mainController.ini

Turn off tsWriteBlocks in that file. Then you should be able to adjust the interWriteDelay.

I would expect that 2 - 3 ms interWriteDelay would be plenty over USB. However, with Bluetooth you often need a good deal more.
What happens over bluetooth is that even if you write each byte with a 3ms pause between each byte, the bytes will sometimes queue up in another buffer in the BT layer, then flush all at once thus eliminating the interWriteDelay. So you sometimes need to have a large enough interWriteDelay to insure that each byte fully flushes out before the next is written. In wort cases, a 25ms interWriteDelay is needed.

[87quest-TSI]

The above was in reference to Tuner studio.
I have not played with shadow dash yet.

[LT401Vette]

Can you send / post your ini file?
With interWriteDelay at 100 you should most certainly be seeing a difference even if it is dog slow runtime data or timeouts.

[87quest-TSI]

here it is.
Right now I have it set to 50.

[LT401Vette]

It is the ini file that I need.
There is no interWriteDelay in the msq.

[87quest-TSI]

opps..

[LT401Vette]

Looks like it needs 1 more edit:
writeBlocks = off

Make sure it isn't commented
;tsWriteBlocks = on
writeBlocks = off
interWriteDelay = 10

You will certainly need to lower the interWriteDelay from 50, the firmware times out between bytes at that level. I would expect 2ms to be plenty on USB.

[jsmcortina]

2ms should be plenty as the full speed inter byte time is less than 0.1ms.

James

[87quest-TSI]

Still no joy.
Bring the rpm to about a 1000 or above and it's fine.
I went as high as 30 using usb and tuner studio.
There where a few times I thought it helped, but after a bit it starts doing it and that was when I had it set to 30.
it was the same thing when I tried it with BT.

[LT401Vette]

There is always plan B...
If you try the beta TS, even if the protocol error occur it will not pause on an Over-Run error, it will immediately retry so the effects should be minimal.

http://www.efianalytics.com/TunerStudio/beta/

[87quest-TSI]

I'll give it a try tomorrow.

[jsmcortina]

I just noticed that you are using EDIS and re-checked the MS2/Extra code. Seems that in the EDIS case, there are remnants of the old MS2/BG ignition code which does slow divides in the ignition interrupt routine. That is almost certainly a big contributor to the over-run. I long ago removed those divides from the MS3 implementation of EDIS, I'll look to do the same for the next MS2/Extra dev code.

James

[87quest-TSI]

The beta TS work good when I tried it using BT.
Did not try it with usb yet.

[jsmcortina]

Please also try out the new MS2/Extra development code I just released. http://www.msextra.com/forums/viewtopic ... 91&t=57121

I believe that this should resolve the root cause of the over-runs when using EDIS. However, as noted in that topic - TAKE CARE - this is a re-write of the way EDIS is handled and has only had bench testing so far.

James

[87quest-TSI]

I'll give it a try when it warms back up a bit.
It's to cold out.

[87quest-TSI]

Please also try out the new MS2/Extra development code I just released. http://www.msextra.com/forums/viewtopic ... 91&t=57121

I believe that this should resolve the root cause of the over-runs when using EDIS. However, as noted in that topic - TAKE CARE - this is a re-write of the way EDIS is handled and has only had bench testing so far.

James

ok I had a chance to try it today. It's much better then it was.
The data rate still droops some, but it might be normal now. Car seems to idle a bit smoother then it did. Seemed like there was a phantom miss sometimes before.
I put tuner studio 2.6.04 back on for testing and used usb.
Overall I think the car runs better.
Let me know if theirs anything else I can help test or try.

[87quest-TSI]

I have also tried it with shadow dash and no longer have the processor error.
Tested using BT.