Megasquirt Support Forum (MSEXTRA)

StevenD57 wrote: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 wrote:
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.

StevenD57 wrote:

djandruczyk wrote:
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?

VolvoGuy50 wrote:Are there any future plans to expand this to MS3?

djandruczyk wrote: 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 wrote:

djandruczyk wrote: 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

jsmcortina wrote: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 wrote:

StevenD57 wrote:
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.

StevenD57 wrote: 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" ???

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

24c wrote:

StevenD57 wrote: 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.
http://www.msextra.com/forums/viewtopic ... 08#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

24c wrote: I think the instructions have been referenced before in this "Segmentation Fault" thread.
http://www.msextra.com/forums/viewtopic ... 08#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

[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.

StevenD57 wrote:

24c wrote: I think the instructions have been referenced before in this "Segmentation Fault" thread.
http://www.msextra.com/forums/viewtopic ... 08#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.

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'

StevenD57 wrote: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.

djandruczyk wrote: 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.