Release Announcements

[djandruczyk]

All releases will be announced here:

[djandruczyk]

MegaTunix 0.9.23 released!:
- Full support for MS2-Extra 3.0.3 firmware series (thru x)
- Full support of JimStim interactive control including automated ctrl
- Win2k support returned with hybrid dual runtime integrated installer
- Numerous bugfixes and memory leak removals
- Minor performance fixes.
- 2D display bugfixes with vertexs "freezing"
- Broke ECU's out into persona's and mtx now prompts at startup to choose
one to use. Required because ms2-e 3.x drops comms if it gets non-api
commands. . this is a precursor to further modularization to other ECU's
- Improved stability and feedback in network mode
- Removed global MTX lock allowing multiple instances
- added "-P" CLI option to specify a specific serial port to be used
which disables serial port autoscanning, when used
- Dashdesigner, Gaugedesigner and mtxloader all ported to use GtkBuilder over
glade.


NOTE: Major change for this release for windows users. The separate GTK+ runtime IS NO LONGER REQUIRED!. If you installed in previously I strongly urge you to uninstall it and reboot prior to installing this version. The MegaTunix installer includes a private hybrid runtime that is isolated, and should not interact with anything else on the system. Please start a thread if you notice any issues.

Binaries for debian lenny, and ubuntu hardy, jaunty, karmic and lucid (lucid may work on maverick, I don't have a maverick box so haven't tested there, I've heard reports the GTK+ version there is buggy).

https://sourceforge.net/projects/megatunix/files/

[StevenD57]

Dave:
Has there been any improvements or planned improvements to the log display part of Megatunix?

I am at a point in my project where I have the car running but I would like to be able to view and analyze the logs from my runs to see what is going on. The last time I asked about some issues I was seeing with log replays you responded by telling me you knew there were problems in this are and that this part of the app could use a re-write. If Megatunix is not able to replay log files is there any possibility of doing it with some sort of external program?
--
Steve

[djandruczyk]

Dave:
Has there been any improvements or planned improvements to the log display part of Megatunix?

I am at a point in my project where I have the car running but I would like to be able to view and analyze the logs from my runs to see what is going on. The last time I asked about some issues I was seeing with log replays you responded by telling me you knew there were problems in this are and that this part of the app could use a re-write. If Megatunix is not able to replay log files is there any possibility of doing it with some sort of external program?
--
Steve

MegaTunix CAN display the logs, however there may be artifacts visible during playback, and you may needto move the log position bar once after you start playback to force the display to refresh. I do have new widgets written that looks similar to megalogviewer (without cost however), though I haven't put them into full use yet in the logviewer. Lately I've been focusing on the plugin architecture, and other (non MS) ecu support. So, in summary, you CAN view and playback logs, but the interface is clunky and non optimal, BUT usually usable.

[VolvoGuy50]

Are there any future plans to expand this to MS3?

[StevenD57]

MegaTunix CAN display the logs, however there may be artifacts visible during playback, and you may needto move the log position bar once after you start playback to force the display to refresh. I do have new widgets written that looks similar to megalogviewer (without cost however), though I haven't put them into full use yet in the logviewer. Lately I've been focusing on the plugin architecture, and other (non MS) ecu support. So, in summary, you CAN view and playback logs, but the interface is clunky and non optimal, BUT usually usable.

I have several logs recorded now but whenever I try to play them back all I get is a black screen. I have tried moving the log position bar but that seems to do nothing. Is there a particular version of Megatunix I should be running to view the logs?

[djandruczyk]

MegaTunix CAN display the logs, however there may be artifacts visible during playback, and you may needto move the log position bar once after you start playback to force the display to refresh. I do have new widgets written that looks similar to megalogviewer (without cost however), though I haven't put them into full use yet in the logviewer. Lately I've been focusing on the plugin architecture, and other (non MS) ecu support. So, in summary, you CAN view and playback logs, but the interface is clunky and non optimal, BUT usually usable.

I have several logs recorded now but whenever I try to play them back all I get is a black screen. I have tried moving the log position bar but that seems to do nothing. Is there a particular version of Megatunix I should be running to view the logs?

If you're on linux, I encourage you to try a developmental version (via git branch modular_0.4)

You didn't mention what version you currently use.

[djandruczyk]

Are there any future plans to expand this to MS3?

Yes. A very generous user donated a MS-3/MS3x to me for development purposes, since the cost of it was beyond my current means, which should hopefully arrive in the next few days, once it gets here, development and testing against it will commence.

[jsmcortina]

A very generous user donated a MS-3/MS3x to me for development purposes, since the cost of it was beyond my current means, which should hopefully arrive in the next few days, once it gets here, development and testing against it will commence.

Advance notice - we are hoping to change the low-level communications method during 1.1 development - as we've briefly discussed before.

The actual tuning data exchanged will be mostly the same save additions and evolution.

1.0 release will stay as it is.

James

[djandruczyk]

A very generous user donated a MS-3/MS3x to me for development purposes, since the cost of it was beyond my current means, which should hopefully arrive in the next few days, once it gets here, development and testing against it will commence.

Advance notice - we are hoping to change the low-level communications method during 1.1 development - as we've briefly discussed before.

The actual tuning data exchanged will be mostly the same save additions and evolution.

1.0 release will stay as it is.

James

urls/links to the new protocol and/or a comparison of old vs new would be strongly appreciated.

However, I'm of the opinion of a significant change in the low level communications should warrant a MAJOR number change, not a minor number change as that is a very significant change. i.e MS3-Extra 2.x with a new low level comms api, instead of 1.1). I'd see a "significant change" would be something like a packet-ized communications (with something like a header, checksum, acknowledgement and packet start.end markers, i.e. analagous to a (very) simplified version of TCP/IP)

[jsmcortina]

As far as I'm aware nobody is working on MS3-Extra.

There's no URL as we haven't come up with anything yet. I just wanted to remind you so you weren't all upset when it changes.

I don't really get the concern about numbers myself. So what if we call it 1.1 or 1.2 or 7.8 ?

James

[djandruczyk]

As far as I'm aware nobody is working on MS3-Extra.

There's no URL as we haven't come up with anything yet. I just wanted to remind you so you weren't all upset when it changes.

I don't really get the concern about numbers myself. So what if we call it 1.1 or 1.2 or 7.8 ?

James

To me its just good programming style. Major api change (i.e. going from MS's stock protocol to something robust, i.e. a packetized interface with proper start/stop markers, header, checksums etc) is something I'd think would warrant a major version number change, but its entirely up to you. Since, MTX now has plugins per device subset, It'll just end up being another choice in the box, so, it can be MS3-1.0 and MS3-2.x, or MS3-1.1, I don't care either way, but by making it 2.x vs 1.1, it allows the 1.0 tree to grow/evolve without ending up with 1.0.<some large number>, it can progress as 1.0, 1.1, 1.2.x and so on. To each, his own, I guess.

[StevenD57]

I have several logs recorded now but whenever I try to play them back all I get is a black screen. I have tried moving the log position bar but that seems to do nothing. Is there a particular version of Megatunix I should be running to view the logs?

If you're on linux, I encourage you to try a developmental version (via git branch modular_0.4)

You didn't mention what version you currently use.

I was using 0.9.23-rc1 on OpenSuSE 11.3 but just yesterday I downloaded 0.9.24-modular_0.3
I built the code but I have not tried it out yet though. So there is a separate git tree for the 4.0 code?
If so do I use a different git reference that the usual "git clone git://github.com/djandruczyk/MegaTunix.git" ???

[24c]

So there is a separate git tree for the 4.0 code?
If so do I use a different git reference that the usual "git clone git://github.com/djandruczyk/MegaTunix.git" ???

I think the instructions have been referenced before in this "Segmentation Fault" thread.
viewtopic.php?f=106&t=39008#p272132

Code: Select all

cd ~/
mkdir git
cd git
git clone git://github.com/djandruczyk/MegaTunix.git
cd Megatunix
git checkout modular_0.4
./autogen.sh --enable-debug
make
sudo rm -rf /usr/local/share/MegaTunix  ## REMOVE the old/existing version as lots of filenames changed and we don't want cruft laying around
sudo make install

[djandruczyk]

So there is a separate git tree for the 4.0 code?
If so do I use a different git reference that the usual "git clone git://github.com/djandruczyk/MegaTunix.git" ???

I think the instructions have been referenced before in this "Segmentation Fault" thread.
viewtopic.php?f=106&t=39008#p272132

Code: Select all

cd ~/
mkdir git
cd git
git clone git://github.com/djandruczyk/MegaTunix.git
cd Megatunix
git checkout modular_0.4
./autogen.sh --enable-debug
make
sudo rm -rf /usr/local/share/MegaTunix  ## REMOVE the old/existing version as lots of filenames changed and we don't want cruft laying around
sudo make install

There is no 4.0 code

In any version control system, there is usually the concept of "branches" (think of a tree), where development is isolated from the "trunk". branches have names, I'm currently working on hte modular_0.4 branch, and will shortly be merging that back to the master (trunk), and splitting off to a new branch mainly that I've accomplished my goals for the modular_0.4 branch.

[StevenD57]

I think the instructions have been referenced before in this "Segmentation Fault" thread.
viewtopic.php?f=106&t=39008#p272132

Code: Select all

cd ~/
mkdir git
cd git
git clone git://github.com/djandruczyk/MegaTunix.git
cd Megatunix
git checkout modular_0.4
./autogen.sh --enable-debug
make
sudo rm -rf /usr/local/share/MegaTunix  ## REMOVE the old/existing version as lots of filenames changed and we don't want cruft laying around
sudo make install

This did not work:

Code: Select all

[me@mysystem git]$ !2539
git clone git://github.com/djandruczyk/MegaTunix.git
Initialized empty Git repository in /home/sad/MTX_VexFiles/git/MegaTunix/.git/
remote: Counting objects: 31042, done.
remote: Compressing objects: 100% (4885/4885), done.
remote: Total 31042 (delta 26575), reused 30563 (delta 26096)
Receiving objects: 100% (31042/31042), 9.78 MiB | 742 KiB/s, done.
Resolving deltas: 100% (26575/26575), done.
Checking out files: 100% (942/942), done.
[me@mysystem git]$ cd MegaTunix/
[me@mysystem MegaTunix]$ git checkout modular_0.4
error: pathspec 'modular_0.4' did not match any file(s) known to git.


[djandruczyk]

I think the instructions have been referenced before in this "Segmentation Fault" thread.
viewtopic.php?f=106&t=39008#p272132

Code: Select all

cd ~/
mkdir git
cd git
git clone git://github.com/djandruczyk/MegaTunix.git
cd Megatunix
git checkout modular_0.4
./autogen.sh --enable-debug
make
sudo rm -rf /usr/local/share/MegaTunix  ## REMOVE the old/existing version as lots of filenames changed and we don't want cruft laying around
sudo make install

This did not work:

Code: Select all

[me@mysystem git]$ !2539
git clone git://github.com/djandruczyk/MegaTunix.git
Initialized empty Git repository in /home/sad/MTX_VexFiles/git/MegaTunix/.git/
remote: Counting objects: 31042, done.
remote: Compressing objects: 100% (4885/4885), done.
remote: Total 31042 (delta 26575), reused 30563 (delta 26096)
Receiving objects: 100% (31042/31042), 9.78 MiB | 742 KiB/s, done.
Resolving deltas: 100% (26575/26575), done.
Checking out files: 100% (942/942), done.
[me@mysystem git]$ cd MegaTunix/
[me@mysystem MegaTunix]$ git checkout modular_0.4
error: pathspec 'modular_0.4' did not match any file(s) known to git.


Strange it did for me:

Code: Select all

cd
mkdir t
cd t
git clone git://github.com/djandruczyk/MegaTunix.git
Initialized empty Git repository in /home/dave/t/MegaTunix/.git/
remote: Counting objects: 31042, done.
remote: Compressing objects: 100% (4885/4885), done.
remote: Total 31042 (delta 26575), reused 30563 (delta 26096)
Receiving objects: 100% (31042/31042), 9.78 MiB | 858 KiB/s, done.
Resolving deltas: 100% (26575/26575), done.
dave@shrapnel:~/t$ cd MegaTunix/
dave@shrapnel:~/t/MegaTunix$ git checkout modular_0.4
Branch modular_0.4 set up to track remote branch modular_0.4 from origin.
Switched to a new branch 'modular_0.4'

I tried from a "new" machine I've never used git on before and it still worked OK with the same results.

[StevenD57]

Before I started this process I created a new git directory and cd'ed into it. As I quoted I did my checkout and then cd'ed into the Megatunix dir and tried the checkout modular_4.0

I just tried it again and it gave me the same error.

I will try on a completely different machine.

[StevenD57]

Before I started this process I created a new git directory and cd'ed into it. As I quoted I did my checkout and then cd'ed into the Megatunix dir and tried the checkout modular_4.0

I just tried it again and it gave me the same error.

I will try on a completely different machine.

That is very strange. I just tried it on a different machine and it worked fine.
Same exact steps. Weird

[StevenD57]

There is no 4.0 code

In any version control system, there is usually the concept of "branches" (think of a tree), where development is isolated from the "trunk". branches have names, I'm currently working on hte modular_0.4 branch, and will shortly be merging that back to the master (trunk), and splitting off to a new branch mainly that I've accomplished my goals for the modular_0.4 branch.

What were your goals for the modular_4.0 or the modular_3.0 code branches? Just curious to see what might have changed.