std ecu-xxx.ini to megatunix .ecu conversion tool?

[piledriver]

Is there a tool in the tree to import ecu .ini files to megatunix profiles and.ecu snapshots?

I'm running the patched 303u with digital in knock on DI JS7(PE0), knock ONLY works on PE0/(PE1?).
megatunix of course thinks that's bloody impossible, so I'm stuck using TS if I want to use all the analog ports for analog signals... (this should have been std since day one IMHO, the js7 jumper wire mod is simple)

Getting it working in TS was of course trivial by setting up a new project and loading the appropriate .ini as the ecu definition... (basically like megatune)

[djandruczyk]

Is there a tool in the tree to import ecu .ini files to megatunix profiles and.ecu snapshots?

I'm running the patched 303u with digital in knock on DI JS7(PE0), knock ONLY works on PE0/(PE1?).
megatunix of course thinks that's bloody impossible, so I'm stuck using TS if I want to use all the analog ports for analog signals... (this should have been std since day one IMHO, the js7 jumper wire mod is simple)

Getting it working in TS was of course trivial by setting up a new project and loading the appropriate .ini as the ecu definition... (basically like megatune)

This is possible, but requires work in different areas. the .ecu files only determin current settings, not the gui layout. In MT/TS the megatune .ini files determine the gui layout, and unfortuantely they are locked into the .ecu files. You can't decode the settings into something the ECU can accept without the megatune .ini file (bad idea in my opinion, by marrying the two configs together like that).

I would need to see what you changed in the default tunerstudio .ini for your firmware. It would require a modified .datamap file and an updated interrogation profile file, to tell mtx to use those alternate files to work with your changes. Since I have no idea what you changed and what tab its on, I cannot help more wihtout either you moded ini and docs on what you did, or a more thorough explanation.

[racingmini_mtl]

If you do get the needed information please post here on how you go about making the changes.

This is exactly the type of thing that has stopped me from using MegaTunix (other than just giving it a try). It may be a bad idea in principle but with a fast changing firmware and interface this is a major hurdle for MTx acceptation. The MT/TS ini may be ugly and a bad idea in principle but it does make things very simple once you know how to use it.

Another thing I have no idea how it will even be possible to do it in MTx is the CAN device. This is relatively easy in TS since it simply takes the device ini and adds the needed menus to the interface and can use and log the new variables. And it will be relatively easy to have some type of mix between the 2 (or more) devices to create new log/display outputs. I have no idea if this will ever be possible with the MTx way of doing things (without having to jump through hoops for each and every setup). But I may be wrong about this since I know almost nothing about it but the response above doesn`t make me very confident aboout it.

Jean

[djandruczyk]

If you do get the needed information please post here on how you go about making the changes.

This is exactly the type of thing that has stopped me from using MegaTunix (other than just giving it a try). It may be a bad idea in principle but with a fast changing firmware and interface this is a major hurdle for MTx acceptation. The MT/TS ini may be ugly and a bad idea in principle but it does make things very simple once you know how to use it.

Another thing I have no idea how it will even be possible to do it in MTx is the CAN device. This is relatively easy in TS since it simply takes the device ini and adds the needed menus to the interface and can use and log the new variables. And it will be relatively easy to have some type of mix between the 2 (or more) devices to create new log/display outputs. I have no idea if this will ever be possible with the MTx way of doing things (without having to jump through hoops for each and every setup). But I may be wrong about this since I know almost nothing about it but the response above doesn`t make me very confident aboout it.

Jean

MTX isn't a RAD application (Rapid App Design), unlike MT and its TS cousin. MtX's design was for usability, not fast changes.
I haven't yet gotten that can board working, I don't have any docs on it, and it appears to be missing a large number of parts. I would like to finish it, but need to find the time to buy all the parts for it to complete it.

[racingmini_mtl]

I haven't yet gotten that can board working, I don't have any docs on it, and it appears to be missing a large number of parts. I would like to finish it, but need to find the time to buy all the parts for it to complete it.

You don't need anything more than what you have on the board to communicate through CAN. I'll email you more about it.

Jean

[jsmcortina]

As Jean says, the Extender is really simple to hook up.

Give it power and ground and then connect the two CAN wires to an MS2/MS3.

You can then run the can_scan utility that comes with MS2/Extra to interrogate the CAN network via serial.

The MS3 manuals have what is hopefully a reasonable description of how to use and set up CAN.

James

[piledriver]

... Since I have no idea what you changed and what tab its on, I cannot help more without either you moded ini and docs on what you did, or a more thorough explanation.

The ini comes with the new firmware, just like always. The only change apparent from a GUI standpoint was PE0/PE1 become the ONLY options for knock in. It was seamless in TS and no mods to TS were required.

I'll happily send you the .ini from the firmware pack and anything else you'd like.

I don't see a way to post it, but the FW available here:
(beware-- mediafire.com is popup city under Windows, and won't work at all w/noscript.. D/L under Linux no problem, oddly.) http://www.mediafire.com/?ly8588bls2rjeio

Thread: http://www.msextra.com/forums/viewtopic ... 01&t=35993

[djandruczyk]

... Since I have no idea what you changed and what tab its on, I cannot help more without either you moded ini and docs on what you did, or a more thorough explanation.

The ini comes with the new firmware, just like always. The only change apparent from a GUI standpoint was PE0/PE1 become the ONLY options for knock in. It was seamless in TS and no mods to TS were required.

I'll happily send you the .ini from the firmware pack and anything else you'd like.

I don't see a way to post it, but the FW available here:
(beware-- mediafire.com is popup city under Windows, and won't work at all w/noscript.. D/L under Linux no problem, oddly.) http://www.mediafire.com/?ly8588bls2rjeio

Thread: http://www.msextra.com/forums/viewtopic ... 01&t=35993

I checked your ini in your build and all you did was change the visible information. not any ecu data. so technically it will work just fine in MTX it'll just show the wrong text in the choice..

- knkport = bits, U08, 927, [2:2], "MS2 AD7/JS4", "MS2 AD6/JS5"
+ knkport = bits, U08, 927, [2:2], "MS2 PE0", "MS2 PE1"

So if you picked "MS2 AD7/JS4" in Mtx it would be the same thing as if you selected "MS2 PE0" in TS/MT.

If you wanted that in Mtx, you would copy C:\program files\megatunix\dist\Gui\ms2-e-3.x-boost_knock_launch.datamap to C:\program files\megatunix\.MegaTunix\Gui\ms2-e-3.x-boost_knock_launch.datamap
edit the file and change line 209 from:
choices=MS2 AD7/JS4,MS2 AD6/JS5
to
choices=MS2 PE0,MS2 PE1
And it would display as you wanted.

Don't ask if the MT.inis will ever be supported, they will not be, they cannot fit into MtX's design goals.

[piledriver]

Thank you, that's what I needed to know to keep using MTX.

I was simply hoping you had a magic perl script so you didn't have to manually parse the new FW revs etc.

I haven't tried the latest windows builds, I try not to use windows at all when possible, and prefer a VM then...

[djandruczyk]

Thank you, that's what I needed to know to keep using MTX.

I was simply hoping you had a magic perl script so you didn't have to manually parse the new FW revs etc.

I haven't tried the latest windows builds, I try not to use windows at all when possible, and prefer a VM then...

The same steps are applicable in linux/OS-x
For linux copy the original from /usr/local/share/MegaTunix/Gui to ~/.MegaTunix/Gui and edit the same way.