I'm essentially a floater at the moment and am willing to do what's within my realm of capability. Here's the breakdown:

During GMT -600 weekday work hours:

• Monitor the IRC channels
• Stay current on forum activity

During weeknights:

• Keep updated clones of the most active git repos
• Build, adopt, and test bleeding edge releases of software and hardware
• Provide multiple build environments (32/64 bit Ubuntu/Debian, Mac OS)
• Provide a running engine to assist with testing firmware and associated apps
• Learn how to use the tools and resources necessary to assist with the above
• Provide highly opinionated feedback about code/install problems, other members, and the direction of FreeEMS/DIYEFI
• Document, help with materials, post, mentor, and interact on IRC to help foster and support a growing community
• Exercise my /kick privileges with great care (especially when drinking)

During weekends:

• Chaotic at best

Neither coding nor hardware development are strong suits of mine and I have no significant formal training in either, so consider me to be severely limited--yet insanely curious--in these areas. Nevertheless, I'm more than happy to help debug and build existing code and hardware as requested by project maintainers.

One note: Good problem solvers listen and know to ask the right questions from those who are reporting the problems (even when those reporting the problems aren't necessarily "good" at doing so). If a developer/designer interacts with me in professional way, I'll do my best to provide the best feedback possible.


-Jeff

Thanks for the write up, Sim! Did you play with the latest/greatest yet? Tacho and/or rev limit testing are welcome, but both only for amusement value :-)


OK... whatever you say!

• Provide highly opinionated feedback about code/install problems, other members, and the direction of FreeEMS/DIYEFI
• Exercise my /kick privileges with great care (especially when drinking)
• Chaotic at best

LOL * 3!


+1, I try, if I fail, please let me know.

People, let's get this tested, likewise if you have MS hardware, test it with that too, as the less bugs in the app the better:

[14:37] <mtx_git_bot> [MegaTunix/master] Fixed long standing memory leaks on shutdown with regards to RT Variables. Please test on as wide a range of firmware as possible and report faults or non-working RT vars. - David Andruczyk

[14:40] <@dandruczyk_home> FreeAir_: ^^^ go rally the troops

Hash bcd38c2, though if there are later ones, likely best to use them.

Fred.

Well I pulled and installed it, but I don't really know what you want from it. The terminal window output after letting the car run for a little bit, and then exiting it?

"faults or non-working RT vars"

Check that things like MAP and TPS behave as expected, all of them, make sure it doesn't crash, try to make it crash, click and drag and poke at everything and remember what you did when/if it dies. Just that :-)

I will check MTX against my MS2 box tonight (it seemed to be OK Sunday afternoon when I tried but I'm sure Dave has made changes

Getting to the point I can start testing on my Jaguar A3 board now that I have the SM loaded and have used Dave's firmware loader to successfully load FreeEMS-vanilla code on it as of midnight last night.

Haven't tested my MS2 with the latest MTX, but I have verified MTX is working correctly with my Jaguar A3 board without the analog input circuits built out (I can't say the readings are correct for the analog sensors). I have been able to write VE, Advance and Lambda table entries to the MCU and power down and verify the cells were the same after exiting MTX and cycling power to my Jaguar board.

MTX exits cleanly through the two nag screens so no issue there.

Will test out with my MS2 in the morning after sleep.

MTX Hash: bcd38c

I'm not using any switches when I start MTX, so my test is truely done the way a new person would run it.

An article, more for me than you, but pretty important:

http://www.inter-sections.net/2008/01/02/feedback/

And another one which shows the process that I'm going through all the time:

http://inter-sections.net/2008/05/19/pe ... -not-exist

Fred.

Firmware users, please test and move up to code from the dev branch ASAP. There are lots of reasons for doing this, but this one might sway you:

*** If you send me a log that latest OLV won't open, I won't look at it. ***

Preston is running the latest greatest on the hotel and it seems solid, so I recommend changing. When I get two more reports, I'll push what's there to master.

Until I do that, more commits are staying on my machine as motivation to upgrade and test.

1. Preston/HOTEL
2. Spudmn/MightyMini
3. Peter/Honda
4. Sim/snot rocket

Fred.

Four testers, dev pushed to master! Thanks Only 2 months to get a set of code onto four cars LOL :-)