Bug or badconfig, don't know.

[coyotanark]

Hi

I have a DIYPNP running very well in a Ford Probe. I was under 3.3.1 and everything works well. I added a TinyIOx who is used for the moment only to plug my Innovate MTX with RS232. I had to update to 3.3.2 as there were a bug in 3.3.1 avoiding me to correctly use the afr info (jean belanger told me this and it seems he was right).

But now I can't use anymore autotune. When I'm the page, it keeps telling that "Minimum RPM" is an active filter whatever my engine speed, it is set at 500rpm so I don't understand.
In spite of this, when I click on Start, it seems to works but he leans all of my values until I stop it. And it puts me far much leaner than my AFR targets. I didn't try to continue to see anymore, don't wanna break my engine running lean so I don't have any datalog.

Here is a screenshot showing the active filter and my project.

Capture d’écran 2014-08-20 à 12.06.35.png

Probe 3.3.2_2014-08-20_13.06.25.tsproj.zip

[LT401Vette]

Nothing jumps out at me as wrong with your project.

I don't have everything here to completely reproduce your hardware setup. (No Tiny IOx)

If you create a new project with just the MegaSquirt is it working fine?

[coyotanark]

I can't try this because without my TinyIOx, I won't have any AFR info, so I can't use autotune.

[racingmini_mtl]

Phil,

Do you have access to a CAN device that has some ADCs? Do you still have an IOx? You would then simply need to poll the ADCs on the CAN device and use CANADC as the EGO source to duplicate the setup.

Jean

[LT401Vette]

I don't mean to physically remove the TinyIOx, just create a TunerStudio project that only has the the MegaSquirt setup and doesn't talk to the Tiny IOx, the MegaSquirt will still talk to the Tiny IOx to get the AFR data.

It also might help to get a look at your TunerStudioAppDebug.txt

[coyotanark]

As you can see (on the screenshot), what seems strange is that the AFR is good in the graph (green line) at the bottom...

[LT401Vette]

Phil,

Do you have access to a CAN device that has some ADCs? Do you still have an IOx? You would then simply need to poll the ADCs on the CAN device and use CANADC as the EGO source to duplicate the setup.

Jean

That old IOx has too old a firmware to work and it doesn't seem to want to take a firmware update.

I can setup a megaquirt or GPIO for ADC's when back at the shop, but where I am at now all I have here today is an MS3.

[coyotanark]

Where can I find this file? I'll try to reload my old project from before the TinyIOx.

[LT401Vette]

The TunerStudioAppDebug.txt is in the TunerStudioProjects folder

You should be able to load the old project, let TS update the ini is needed, but make sure you take the Controller Settings if you get a Difference Report.

[racingmini_mtl]

That old IOx has too old a firmware to work and it doesn't seem to want to take a firmware update.

It seems I can't PM you so I'll put it here.

You probably need to use the downloader which uses the "new" serial protocol: http://www.jbperf.com/io_extender/firmw ... dl_ms3.exe. Then you should be able to download the latest firmware: http://www.jbperf.com/io_extender/firmw ... _0_1_2.zip. If you can't then you need to use the bootloader jumper but on your old board you actually need to jump the pad to a ground pad and not the one beside it because there was a bug on that board and that pad is not grounded. And power cycle with the jumper in place. Email me if you still can't get this working.

Jean

[coyotanark]

My file makes 1.8Mo, I can't upload it here. I can email it if you want.

EDIT:
I can't reload my old project because I just modified it. I tried to load an old msq, but it didn't changed anything. And I made a small datalog with my actual config and autotune at idle. Not too long to don't be dangerous.

2014-08-20_18.07.22.msl.zip

[LT401Vette]

That old IOx has too old a firmware to work and it doesn't seem to want to take a firmware update.

It seems I can't PM you so I'll put it here.

You probably need to use the downloader which uses the "new" serial protocol: http://www.jbperf.com/io_extender/firmw ... dl_ms3.exe. Then you should be able to download the latest firmware: http://www.jbperf.com/io_extender/firmw ... _0_1_2.zip. If you can't then you need to use the bootloader jumper but on your old board you actually need to jump the pad to a ground pad and not the one beside it because there was a bug on that board and that pad is not grounded. And power cycle with the jumper in place. Email me if you still can't get this working.

Jean

I had Brian working on this with you quite some time back. I will pass this on.

[coyotanark]

Please give an email for me to send you the file. Thanks!

[LT401Vette]

support <at> efianalytics. com

[coyotanark]

Hi

I just sent the mail at the moment.

I have to add that neither ShadowDash on the last stable release or the last beta work anymore since I added the TinyIOx. I may have something to do, but I can't find any documentation about it.

Thanks!

[LT401Vette]

Jean, Turns out Brian did have it working now. He had emailed you and added a boot jumper.

[coyotanark]

I just saw that a new version of TS is available (2.6.04). According the changelog, it should solve my problems? And FYI, Shadow dash (1.25 stable) succeed to connect AND read the config 1 time on 4 approximately. I'll keep trying make it work better.

[LT401Vette]

There is nothing in 2.6.04 to address a problem here, we haven't reproduced the problem yet.

With Shadow Dash, do you mean it successfully connects about 1 out of 4 times?

Rather than jumbling this thread with multiple problems, can you email support <at> efianalytics. com with what kind of tablet it is, what you are using for connectivity and what firmware you are using (even though it is in this thread, it saves figuring that out later)

[coyotanark]

Ok. But not until the next week-end because I'm far away from home for holidays.

[LT401Vette]

I have found the problem, it is a bug in TS.

It looks like you need to disable runtime reads for the CAN device while running VE Analyze.

I will put out a beta to patch this.