Mtx does not refresh tabs when retrieving data from ECU

[Cha0z97]

Hi all,

I've just installed v0.9.22 of megatunix and after playing around a little with it, I noticed some odd behaviour.
I did some testing, and it does burn any new settings to the ECU correctly, since I've been able to get a reasonable rpm after changing some setting to a 60-2 teeth trigger wheel. However, when I changed those settings to something else and hit the Get data from ECU button, the settings weren't reverted to the ones from the ECU. I did some further testing, and this is the case for at least some other controls and the VE table.

A bit about my setup :
Using :
- megatunix v0.9.22
- MS2 on a V3 board, powered by the relaisboard, sensor input provided by Jimstim.
- MS2 ECU is loaded with MS2Extra v2.1.0d firmware
- Textual version according to mtx :MS2Extra Rel 2.1.0q
- ECU signature : MS2/Extra 2.1.0d Release 20100123 21:43BST (c) KC/JSM**MS2
- OS: Ubuntu 10.04 LTS

I've also tried the regular MS2Extra 2.1.0 regular firmware, also to no avail.
Also note, I used to run v0.9.19, with the regular MS2 firmware on an older version of Ubuntu. Please forgive me, I don't recall which version.

I hope I have supplied enough information, if further info is needed, please let me know.

Thanks in advance

[djandruczyk]

Please pull from git and compile/install that version and see if the behavior persists there.

See http://msextra.com/forums/viewtopic.php?f=106&t=35786

[Cha0z97]

I'm running 0.9.23rc-1 now, but the same behaviour persists.

[djandruczyk]

I'm running 0.9.23rc-1 now, but the same behaviour persists.

Does megatunix load up the settings from the ECU on startup correctly on all tabs? So far I haven't been able to duplicate your issue..

[Cha0z97]

It does not. It says :
Updating controls on page 0
Updating controls on page 1
Updating controls on page 2
Updating controls on page 3
Updating controls on page 4
Ready

However, they are not the right settings.

[djandruczyk]

It does not. It says :
Updating controls on page 0
Updating controls on page 1
Updating controls on page 2
Updating controls on page 3
Updating controls on page 4
Ready

However, they are not the right settings.

Are the values all zeroes, or scrambled?

What happens when you click "Get data from ECU", do they update with valid values?

What OS, and Megatunix version?

[Cha0z97]

Well, mtx kinda does nothing, so it seems. For instance, the first thing I'd like configure is the trigger wheel. I need to have a decent trigger handling, otherwise a relay starts ticking vehemently. So when I start mtx, and open the Global Settings tab, no values are shown. Then it starts to update the controls. Spark mode is filled with EDIS (which is on the top of the list). I set this to Toothed wheel and click ' Permanently store data in ECU' . I click the ' ignition tab' . Here spark mode is already set to ' toothed wheel'. I configure the wheel settings conforming to the JimStim output. I hit the store button again. Now, I powercycle the ECU and the ticking seizes. I now close mtx answering no to all questions and start mtx again. I click ' global settings again' The fields are empty initially, but when updating the controls, EDIS appears as the selected Spark mode. When I click get data from ECU, EDIS is still the selected spark mode.

However, when I take a look at the runtime vars, I get a clean RPM.

This tells me that mtx burns the ECU correctly, no problem in the writing area. I'm a software developer myself, and my guess would be that mtx does not know how to parse the received settings data coming from the ECU, and therefore assumes a default state. I've tried 3 different firmware versions, and thus far, the only one that does not show this behaviour is the standard MS2 one.

I've also tried TunerStudio to help pinpoint the problem to mtx rather than the ECU or the way the firmware was loaded, but no problems here.

For OS and Firmware versions, please look at my first post.

PS,
I think you're doing a great job developing this product, and I'd love to help where I can removing any glitches that may occur.

[djandruczyk]

Well, mtx kinda does nothing, so it seems. For instance, the first thing I'd like configure is the trigger wheel. I need to have a decent trigger handling, otherwise a relay starts ticking vehemently. So when I start mtx, and open the Global Settings tab, no values are shown. Then it starts to update the controls. Spark mode is filled with EDIS (which is on the top of the list). I set this to Toothed wheel and click ' Permanently store data in ECU' . I click the ' ignition tab' . Here spark mode is already set to ' toothed wheel'. I configure the wheel settings conforming to the JimStim output. I hit the store button again. Now, I powercycle the ECU and the ticking seizes. I now close mtx answering no to all questions and start mtx again. I click ' global settings again' The fields are empty initially, but when updating the controls, EDIS appears as the selected Spark mode. When I click get data from ECU, EDIS is still the selected spark mode.

However, when I take a look at the runtime vars, I get a clean RPM.

This tells me that mtx burns the ECU correctly, no problem in the writing area. I'm a software developer myself, and my guess would be that mtx does not know how to parse the received settings data coming from the ECU, and therefore assumes a default state. I've tried 3 different firmware versions, and thus far, the only one that does not show this behaviour is the standard MS2 one.

I've also tried TunerStudio to help pinpoint the problem to mtx rather than the ECU or the way the firmware was loaded, but no problems here.

For OS and Firmware versions, please look at my first post.

PS,
I think you're doing a great job developing this product, and I'd love to help where I can removing any glitches that may occur.

That's very strange, and I cannot duplicate that behavior here on my end. Are you 100% sure that you're waiting until the gui says "READY..." on the bottom bar BEFORE changing anything? If you change a control during the update, i.e. after it's rendered it but BEFORE its finished doing all the others, it is possible that megatunix can loose track of that change and NOT send it to the ECU, though the control will typically stay red if you do that.


Is it only that one control that is misbehaving?