You mean "Load Table" button on the "Tuning Table" tab?

I'll get on that. You want it to load just a sort of generic table, or maybe a dynamically created semi-random table?

Yeah that button

It will probably only be useful for testing datalogging (the highlighted cell that moves around), and adjusting values. So whatever you think would work. Maybe work in some data logs too?

Sorry for A not being clear with respect the URL B telling you pull instead of clone.

Good to see you guys are in action, so am I!

Fred.

I've spent the last 2 hours or so wading through code. It's clear I need a little hand-holding. Aaron, get on Instant Messenger sometime so I can lean on you a little tomorrow or Tuesday or something. A couple of questions could go a long way to getting me self sufficient again and the forum is too slow to be efficient. For now I'm headed to bed.

I may not be much/any help, but you can get me on gmail and fb chats if you wanna try asking and Aaron isn't awake. My schedule is sleep in till 10, be online for an hour or 2, go do stuff in the afternoon, come home and stay online late. Aaron goes to bed a few hours before me each night, so you'll get me after he's faded out already, if that is any use.

I may not know python specifics, but I understand what it is supposed to be doing and hacked it a bit myself here and there. I also can tell you what I'd like to see out of it from my perspective, though since getting home and not needing it for the Volvo anymore, that is lower priority than various other things. At least until I get another in car test rig going.

Fred.

Today I put a new regulator and a heatsink on Aaron's dev board! Yay. Temperature controlled soldering stations are REALLY nice to use! :-) Right now we can't seem to load firmware to it, maybe the serial adapter is dodgy, but we CAN get the SM to dump register contents etc, so not sure what is going on. The results are the same with Aaron's box and my EEE.

No excuses for testing/dev now, ey mate ;-)

Fred.

Just fired this up using a non usb serial port (my atom330 box has one too!!! yay) and ran it against the test rig, still works sweet :-) Just had to get some libs and that bootstrap, not even sure if I needed that or not - no, just removed it, all is well now. Ready to test further work when you are, mate :-)

Just burned a few cells then refreshed the table and the failing to burn all clicks issue is still present (of course) so we should work on that when you next get a chance. I imagine we'll need to discuss it quite a bit to figure out what is actually required from each of us. I have free national toll calls (and ozzy apparently) so if you have a land line, or don't mind chatting on your lunch break at work, we can talk at zero cost.

Fred.

It's still eating way too much CPU to just be processing packets and displaying numbers in a table from them :



Did we ever figure out what was going on there? Is it just the gui component you're using that's slow? or the way you break down the binary stream into packets? both?

I vaguely remember you saying you'd been to a conference or something and found a better way to process binary? It has to be possible to make it more efficient, right? That C parser utility does it almost instantly, if we could get half way to that, it'd be fast enough :-)

Fred.

Just pushed two small changes up to github and sent out a pull request to you, Ben and Sean[0], please accept :-)

Fred.

Added some documentation to your key fix, merged into devtrunk in my repo.

Thank you for your patches!