ms2 extra

streetknight · Post by **streetknight** » Tue Aug 14, 2007 7:48 pm

ok i have a ms2 extra set up and i wanted to know if i could use megatunix to check my vr sensor? is that possible with out having to reload the firmware on ms2extra and not have to load ms2.

JeroenBosma · Post by **JeroenBosma** » Sun Oct 28, 2007 7:28 am

I would like to know this but it seems the Extra software is not supported. I'll try a release.

JeroenBosma · Post by **JeroenBosma** » Sun Oct 28, 2007 7:58 am

Well..

Not working. I guess it is hard to be an early adaptor.

djandruczyk · Post by **djandruczyk** » Sun Oct 28, 2007 9:21 am

JeroenBosma wrote:Well..

Not working. I guess it is hard to be an early adaptor.

MegaTunix doesn't yet support MS2 CPU's and firmware. IF you have VR issues, you can stick the MS-I CPU back in and run the MS-I Extra firmware and use megatunix's TTM to check your tooth/trigger signals.

barf · Post by **barf** » Thu Nov 01, 2007 12:07 am

what is r equired for MS2 support? how can we help?

I have MS2 and just checked out megatunix from CVS. great work djandruczyk! buy you a beer if you're ever in christchurch new zealand!

PS the configure script from CVS is failing for me, something about a syntax error line 20323

djandruczyk · Post by **djandruczyk** » Fri Nov 02, 2007 6:52 pm

barf wrote:what is r equired for MS2 support? how can we help?

I have MS2 and just checked out megatunix from CVS. great work djandruczyk! buy you a beer if you're ever in christchurch new zealand!

PS the configure script from CVS is failing for me, something about a syntax error line 20323

When updating CVS, run "./autogen.sh" this is documented in the how to get megatunix running on Linux (ubuntu) thread.

As for MS-2. One of the most time consuming things that I have to do that I'd prefer to offload is Tab design. This involves using Glade, and creating tabs to display all the controls applicable to the firmware. The part is tricky as it requires collating a large amount of info from megatune ini's, the firmware itself (As many of the stuff in the MT ini is ambiguous, or outright confusing), and trying to determine which is the best way to logically group the controls.

NOTE: controls can be place anywhere, and you can even have multiple controls referring to the SAME variable (useful if a control is "dual-purpose", or is applicable in two different logical groupings)

I prefer to group controls into functional groups, esp if they are "conditionally tied" controls. (i.e. controls that are ONLY active if another control is enabled or disabled. Megatunix allows this via keys in the datamap files. (don't worry about having to write those, they are a bit tricky.)

So IF you WANT TO HELP. start designing tabs, with each tab you create, create a text document listing ALL the control names (using hte same control names as megatune, might be wise, as it makes it easier for me to cross reference, in case of bugs, this file should also list the page (if applicable), Offset, var size (8 bit, 16 bit, signed/unsigned, bitfiled, whatever), and any conversions used, to convert between MS and real-world presentation. IF any ofthe controls or groups or controls are dependant on the state of something, make a note of that. as well.

Use exiting tabs as models to get started, and there's README files in the Gui dir of megatunix describe things in slightly more detail.

If u find existing tabs for existing firmwares are confusing, or poorly designed, improve them, test em and submit them to me for inclusion.

UnaClocker · Post by **UnaClocker** » Fri Nov 02, 2007 7:53 pm

Sometimes I wish I were seriously injured and layed up in bed for a month or two.. I know I could do the tabs for ya.. Just don't have time..
In the mean time, can we just get the communications/datalogging/gauges working? No big deal to fire up MT to change settings from time to time, but I really like the MTx Gauges, it'd be great to at least have those running with MS2E..

(Goes back to my old request for just a gauge program).

djandruczyk · Post by **djandruczyk** » Sat Nov 03, 2007 7:20 am

UnaClocker wrote:Sometimes I wish I were seriously injured and layed up in bed for a month or two.. I know I could do the tabs for ya.. Just don't have time..
In the mean time, can we just get the communications/datalogging/gauges working? No big deal to fire up MT to change settings from time to time, but I really like the MTx Gauges, it'd be great to at least have those running with MS2E.. (Goes back to my old request for just a gauge program).

Now you have an idea of waht I went through and how I feel, about all the effort I put into designing those tabs. (yes they take longer than writing a MT .ini, but I think it leads to an overall better performing, lookig and easier to use software, though this is only my personal opinion.

The current version of MtX (CVS) has a "gauge only" mode, which hides the other windows, usefull for CarPC's run "megatunix with "-m -r -s" options (use megatunix --help tp get the list of options).

MS2 comms still isn't working as I am in progress on rewriting the I/O routines to remove the cruft and complexity (not idea WTF I was thinking when i wrote it originally) to replace it with a more robust and simpler/extensible I/O model that'll work with MS-2 and future MS items.

UnaClocker · Post by **UnaClocker** » Fri Dec 21, 2007 8:19 pm

All I want for Christmas is MS2E support. At least for the gauges and logging portion of the program.

Post by **jsmcortina** » Sat Dec 22, 2007 8:20 am

The tooth logger would be great too. (NB MS2/Extra has more data compared to MS1/Extra)

James