FreeEMS-Tuner Development Diary - Comments

[Fred]

Another few thoughts :

1. Do you want me to split this thread into two halves before I take it over with "comments"
2. Debug string messages - dump them to the console and log them? I'm not sure you would want a pop up message for each one, but a console tab option could be handy I guess, for now just dumped to the console it was launched from will be AWESOME :-)
3. Error code messages - you'll want to have a lookup table for these per firmware revision. I'd really like to see my makefile take care of a lot of the config for each tuning tool as it would save a lot of work. Extracting the #define error codes into another format from a specific file would be pretty easy for anyone who knows sed or awk or similar. That way the firmware build could self configure the tuning tool to some extent? If we could suss out a similar technique for the data structures (tables and structs etc) that would be cool too. Just thinking out loud here, but the main thing is an error > message mapping that outputs a message like the one below this list for each error packet received

12456 = "fred screwed up and forgot to configure the flux gate capacitor"

or similar?

Your call, but errors and debugs to the console would = awesome :-) should = easy too :-)

Fred.

[sry_not4sale]

Another few thoughts :

1. Do you want me to split this thread into two halves before I take it over with "comments"

Yeah might be an idea ya noisey bastard

[*]Debug string messages - dump them to the console and log them? I'm not sure you would want a pop up message for each one, but a console tab option could be handy I guess, for now just dumped to the console it was launched from will be AWESOME
[*]Error code messages - you'll want to have a lookup table for these per firmware revision. I'd really like to see my makefile take care of a lot of the config for each tuning tool as it would save a lot of work. Extracting the #define error codes into another format from a specific file would be pretty easy for anyone who knows sed or awk or similar. That way the firmware build could self configure the tuning tool to some extent? If we could suss out a similar technique for the data structures (tables and structs etc) that would be cool too. Just thinking out loud here, but the main thing is an error > message mapping that outputs a message like the one below this list for each error packet received[/list]

12456 = "fred screwed up and forgot to configure the flux gate capacitor"

or similar?

Your call, but errors and debugs to the console would = awesome should = easy too

Fred.

Yeah a console tab, and a very verbose log to file are both already underway

[Fred]

Done, I hope the split meets with your approval :-)

Real console and a console tab? I'd actually prefer the real thing for dev use as it allows me to use grep etc. The tab is a good thing for general use though :-)

Fred.

[Fred]

Bugger :-(

Have you joined this club : http://www.diyefi.org/forum/viewtopic.php?f=13&t=425 ?

Which ever one you joined I know your pain. I only got my OS installed and my screen died. Then i pulled it down and put it back and the usb controller went out... now I'm an EEE user hard core.

Fred.

[sry_not4sale]

Frixed!!!

Is a toshiba tecra, has a dodgy d/c socket or charger or cord. Not sure which, but always seems to come right if I give it a good telling off

[Fred]

Then email it to me and I'll try it!

Is it distributed as a binary? Or interpreted from source at run time?

Fred.

[sry_not4sale]

Run from source, haven't cleaned up dependencies yet.

Patience my friend

[Fred]

No stress :-)

If/when you get it ready, even if I have to run it from source, do send it my way with some instructions! :-)

I've been flat out trying to recruit testers, and I've had a few "sure, where do i get it" answers, but in the short term, I AM your testing pool ;-)

Fred.

[Fred]

Implemented the watcher pattern for comms, which lets the gui elements monitor packets.

publish/subscribe ? :-) or have I been too brain washed by the commercial world already?

Could have had a working example running, but have been thinking of the future as I go and making it extensible as possible :mrgreen:

Good man! That's what I was doing with the Java one i started on. I was trying to get work and work on the firmware at the same time though... It wasn't working out the best.

I can't wait to try it :-)

Fred.

[Fred]

Just thought I'd throw in a brag post here about having used this app tonight :-)

plugged it through interceptty and watched it talk garbage to the serial monitor and get garbage back.

ran first time, didn't crash, fast, good start if you ask me!

I reckon in a few days I'll be a genuine user of this tool!

That is IMO very cool.

Good work Aaron.

Fred.