nextround of improvements for 0.9.15

[djandruczyk]

Currently working on mtx pre-0.9.15 CVS.

Command line arguments, to shut up megatunix nag screens (most common for Serial I/O problems).
Options currently implemented include:
-q, quiet
-r hide runtime text values window
-m, hide main gui (useful for CarPC's dash usage)
-s, hide main status window
-v dump the version number

Working on options for automated datalogging to files, useful for long term logging to a USB key. Should be done in a couple days.

Cool stuff:
I rewrote a subsection of the I/O handling code with regards to the serial ports, so that its no longer necessary to specify the serial port, or baud rate. MegaTunix will take care of it automatically, by scanning through ports (configurable in the main conf file), and automatically detecting the ECU, making it even easier to just "plug and go". It even allows you to unplug nad SWITCH serial ports ON THE FLY. So if you decide you MUST change serial ports on the fly you can now do it, and plug that into the SAME MS, it'll continue and keep going without requiring megatunix to restart. It only becomes a problem if you have multiple MS's connected to your computer at once, but that's not too likely (yet) This means that megatunix is resiliant to just about any sort of serial I/O problem, aside from a gremlin injecting fake data onto the line. (no tuning SW would work with that) and recovers gracefully and automatically.

More to follow. Feel free to add other requests. (Yes I know about MS-2, I'm working on it, but that's like a 300 lb couch potatoe trying to climb mt. everest. It takes a while.)

[rabiddeity]

Plug and go is seriously AWESOME for those of us with USB converters that assign a port at random. Excellent job. I'm waiting with bated breath for the MS-II support so I can start using those pretty gauges...

[jsmcortina]

Not sure if this applies to many, but on my old laptop when I tried a serial port scanner it rebooted the machine without warning.

James

[rabiddeity]

Hmm, Linux is a bit better about drivers not rebooting or locking a machine, but for the Windows port maybe write the scanned ports to a log file as they're being scanned (with a pipe flush after each one) and give the user the ability to disable scanning on certain ports if they cause problems. I think this is something that could be put in a .conf file or added to the command line.

[djandruczyk]

Not sure if this applies to many, but on my old laptop when I tried a serial port scanner it rebooted the machine without warning.

James

Sounds like a typical bad driver/windows problem. Best bet is to finally ditch that old ancient machine and pickup a free (or super cheap) workplace hand-me-down one.

[djandruczyk]

Hmm, Linux is a bit better about drivers not rebooting or locking a machine, but for the Windows port maybe write the scanned ports to a log file as they're being scanned (with a pipe flush after each one) and give the user the ability to disable scanning on certain ports if they cause problems. I think this is something that could be put in a .conf file or added to the command line.

The ports to be scanned are already (or will be for 0.9.15) in the main mtx config file. They can be hand edited if need be and extensive logging is dumped to the comms tab if/when serial comms are lost or it's searching.

[jsmcortina]

Not sure if this applies to many, but on my old laptop when I tried a serial port scanner it rebooted the machine without warning.

James

Sounds like a typical bad driver/windows problem. Best bet is to finally ditch that old ancient machine and pickup a free (or super cheap) workplace hand-me-down one.

I already replaced that machine a while back, but if it happens on one, it might happen on others. Sounds like you have the issue covered though.

James