3.03 Alpha supported, needs testers!

[djandruczyk]

I have finished up MSnS-Extra 3.03U Alpha support in MegaTunix. Currently this is only available in git (version control). Those willing to test (OS-X/Linux), please checkout a copy and give it a shot and report back missing features, bugs and whatnot.

Feel free to hop in ##megasquirt on IRC (irc.freenode.net) for git commit notifications and/or to reach me directly.

[piledriver]

Vote of confidence:
Latest git pulls work ~reliably, (says version 0.9.22, but has or awhile) except or the huge reduction in serial update rate after the main comms issues preventing reliable initial connections was fixed.

[djandruczyk]

Vote of confidence:
Latest git pulls work ~reliably, (says version 0.9.22, but has or awhile) except or the huge reduction in serial update rate after the main comms issues preventing reliable initial connections was fixed.

Be more descriptive about this latter issue please.

[piledriver]

Vote of confidence:
Latest git pulls work ~reliably, (says version 0.9.22, but has or awhile) except or the huge reduction in serial update rate after the main comms issues preventing reliable initial connections was fixed.

Be more descriptive about this latter issue please.

Thought we covered it in the other thread...

I had to reduce the update rate from 20 to 50ms and reduce all the other settings to <5 in order to not freeze the GUI.
You added a queue readout so one could see when the rate reduction was needed.

(when it connected) the GUI worked fast and with the default update rates.on the first git versions I tried...
My laptops CPU is ~ equivalent to most netbooks folks use for tuning MS, 1.8 GHz Pentium M, display is 1024x768.

You'll never see the performance/GUI layout issues on a high performance desktop at high resolutions, just on machines people use for tuning.
Many netbooks can't even do 1024x768...

MTX looks/works great on a quad core Athlon2 BE at 3.6GHz @1600x1200 and a ATI HD4XXX video-
Laptop @ 1024x768 and old ATI chipset--- Not so much, but workable.

[djandruczyk]

Vote of confidence:
Latest git pulls work ~reliably, (says version 0.9.22, but has or awhile) except or the huge reduction in serial update rate after the main comms issues preventing reliable initial connections was fixed.

Be more descriptive about this latter issue please.

Thought we covered it in the other thread...

I had to reduce the update rate from 20 to 50ms and reduce all the other settings to <5 in order to not freeze the GUI.
You added a queue readout so one could see when the rate reduction was needed.

(when it connected) the GUI worked fast and with the default update rates.on the first git versions I tried...
My laptops CPU is ~ equivalent to most netbooks folks use for tuning MS, 1.8 GHz Pentium M, display is 1024x768.

You'll never see the performance/GUI layout issues on a high performance desktop at high resolutions, just on machines people use for tuning.
Many netbooks can't even do 1024x768...

MTX looks/works great on a quad core Athlon2 BE at 3.6GHz @1600x1200 and a ATI HD4XXX video-
Laptop @ 1024x768 and old ATI chipset--- Not so much, but workable.

Interesting, the changes were needed due to a bad threading bug that was present previously. Before there were minimal/no checks regarding threaded operations and gui interaction which lead to strange lockups, crashes and other bad behavior. I'll look into your current performance anomalies, but I don't seem to have them, and my main devbox albeit semi-powerful is 6+ years old (old dual athlon 2.2 ghz).

[piledriver]

I'd feel bad but it was initially reported by someone else

I suspect your 6 year old dev box is still far better than many if not most tuning laptops/netbooks it's intended for.

[24c]

I tried to get MegaTunix to see my cased MicroSquirt running MSExtra 3.03u today, but although it saw the /dev/tty.PL2303-0000101D and the /dev/cu.PL2303-0000101D addresses from the Prolific USB Serial adapter, I couldn't get any comms.

I did a quick search in Terminal using ls -l /dev/tty* and saw all the usual suspects, but even if I put in the port address that was working in TunerStudio it failed.

I must be doing something wrong...

Will try on the desktop later.

[djandruczyk]

I tried to get MegaTunix to see my cased MicroSquirt running MSExtra 3.03u today, but although it saw the /dev/tty.PL2303-0000101D and the /dev/cu.PL2303-0000101D addresses from the Prolific USB Serial adapter, I couldn't get any comms.

I did a quick search in Terminal using ls -l /dev/tty* and saw all the usual suspects, but even if I put in the port address that was working in TunerStudio it failed.

I must be doing something wrong...

Will try on the desktop later.

Strange. I have no trouble with 3.0x on the macbook and a pl2303 adapter. did you try "Communications->Locate Port" and follow the steps/prompts?

[24c]

I did follow the Locate Port steps, and I got two ports detected

/dev/tty.PL2303-0000101D
/dev/cu.PL2303-0000101D

displayed within the dialog box with an exclamation mark in it, but after hitting the green Yes button it did nothing. I could start the engine on the MicroSquirt, but no dash values were changing. The MicroSquirt was powered up beforehand, and works fine in TunerStudio with the same adapter, which I quit before starting X11. I am trying to clear the desk where the rig is, so I can swap the cranks over, and try it again, but this time, take screenshots & try another adapter.

I am only trying to test 3.0.3 back to back, give you some feedback, and also because I'd like to be able to change the firmware on my other cased Microsquirts within OSX (X11).

[24c]

I have tried this on my rig, with another MicroSquirt using TunerStudio and USB Serial went OK & I got comms.

Quit everything, restarted, and ran MegaTunix, and also tried the other USB port. The USB Serial LED is not flashing like normal, and I can't get MegaTunix to see it...

Here's a screenshot of my xterm window

Screen shot 2010-09-02 at 21.15.03.png

Any ideas please? Is it possible to have a dialog box to choose one of several devices detected? If you type in a port name, I assume Enter or Return would set it.


I am running MacBook Pro 2.4 C2D, 4GB RAM, 10.6.4

[djandruczyk]

I have tried this on my rig, with another MicroSquirt using TunerStudio and USB Serial went OK & I got comms.

Quit everything, restarted, and ran MegaTunix, and also tried the other USB port. The USB Serial LED is not flashing like normal, and I can't get MegaTunix to see it...

Here's a screenshot of my xterm window

Screen shot 2010-09-02 at 21.15.03.png

Any ideas please? Is it possible to have a dialog box to choose one of several devices detected? If you type in a port name, I assume Enter or Return would set it.


I am running MacBook Pro 2.4 C2D, 4GB RAM, 10.6.4

Which version of megatunix are you trying? 0.9.22? Or from git? If you want to specify a port, just de-select "Auto-Scan Serial Ports" and type in the name in the Serial Port Box and hit enter/return.

I am testing on the macbook, and so far I haven't been able to make it fail yet.

[24c]

I am using 0.9.21, and I have tried all you said.
Maybe I have done something wrong...

[djandruczyk]

I am using 0.9.21, and I have tried all you said.
Maybe I have done something wrong...

Please try 0.9.22, or pull from git as shown below. There have been a LOT of changes since 0.9.21 including lots of crash-fixes.
see my signature below for links

Code: Select all

sudo  port install git-core
mkdir git
cd git
git clone git://github.com/djandruczyk/MegaTunix.git
cd MegaTunix
./autogen.sh
make
sudo make install

0.9.22 has a deadlock bug when trying to close an open dashboard, which is fixed in git.

[24c]

Thanks for that, just pulled the git version as per your post instructions...started X11, typed in megatunix in xterm window....and still no comms. Dialogs are the same as before.

Screen shot 2010-09-02 at 23.02.17.png

I know I not a UNIX person, but this is probably quite frustrating for you by now.

[24c]

OK I have no idea, but unplugging the USB adapter and double clicking the communications tab repeatedly, eventually created this...

Screen shot 2010-09-02 at 23.29.42.png

Go figure what is happening

[24c]

So I "saved" the settings, and now I get the following in the comms box, I would have thought it might have started at the higher baud rate first, seen as 115200 is the default AFAIK.
I can spin the crank and get RPM readings...looks interesting.

Screen shot 2010-09-02 at 23.51.19.png

[djandruczyk]

So I "saved" the settings, and now I get the following in the comms box, I would have thought it might have started at the higher baud rate first, seen as 115200 is the default AFAIK.
I can spin the crank and get RPM readings...looks interesting.

Screen shot 2010-09-02 at 23.51.19.png

Strange that it didn't work previously. I suspect it might be a quirk in the PL2303 driver. I got mine from sourceforge http://osx-pl2303.sourceforge.net/ If you got yours from someplace else,that may be part of the reason, I'm not too sure, since TS worked fine for you.

Let me know if the issue continues..

[24c]

I have just tested the four Microsquirts I have, three on MSExtra 3.0.3, and a B&G 2.880. I have had good comms with all, except the B&G which keeps losing comms, (cycling between successful and lost comms). I am not bothered by this, as I need to upgrade this unit to later B&G code anyway, but it might be the secondhand unit.

BTW, I thought I'd try logging the RPM on my crank rig, using the MSExtra MicroSquirts and I got this error and MegaTunix closes down.

Screen shot 2010-09-03 at 09.51.07.png

No idea what it means, just posted FYI.

PS Going to try MegaTunix on a running engine now, will report back.
PPS USB Serial worked OK, but I found it worked just as well, by not powering the MicroSquirt up, getting the Comms error Dialog Box on screen, and then powering up, and after a couple of seconds everything was as it should be.

[24c]

Just installed MegaTunix on an iMac 27" i7 and from start to finish using the git version, on a 2MB broadband (download rate 270Kb max) it took 1 hour 20 mins. On top of this was the previous Xcode update 14 mins, and X11 from the DVD, 5 mins including restart. Now I just need to run the 5m USB cable up to the cased MicroSquirts and see if I can get comms with those pesky Prolific ATEN USB Serial adapters

PS MegaTunix worked fine on the running engine, but I need to rework the gauge limits and layout. Seems faster than TunerStudio, I like the comms status updates, not sure about the port selection dialog, but overall very brief first impressions, it seems slightly quirky & full of info boxes, but then I am used to the latter (TS), but no disrespect intended towards MegaTunix.

[svocapri]

Does the GIT version support 3.0.3v? I would like to test if it does.