Flashhack - New LT1 flash tool

[steveo]

steveo, some thoughts:
1. Having high latency is not a unique problem to this interface; it happens in all sorts of applications. What if there was a way to determine the latency? Without being hooked to the vehicle, if I just plug in the USB to serial converter and then send a message and read the same message right back since TX and RX are connected together, can't we figure out the latency for a given hardware setup? Heck, just have the user turn the key off and wait for the bus to quiet, the software could figure out the latency even with the cable connected to the vehicle, if the PCM doesn't pull it to ground when off?
2. Then, watching the B-body idle traffic scan data, there WAS a repeating pattern of messages, and some of those gaps were significant. What if we listened to the bus and figured out the pattern, then How long a gap do we need to make a bus master message? How long is that message?
3. Knowing our latency and knowing the message pattern, couldn't we then insert a bus master request at the right time?

i think you're assuming a level of precision that doesn't exist consistently between interfaces and drivers. i'm done trying to 'time' the thing as i want an approach that works for everyone with every interface so i don't have to deal with everyone asking me why its not working. there's a reason no windows based aldl software is doing that. of course if someone else wants to develop and test that approach i will definitely use it upon success but it does have to use QSerialPort as i need this to be multi-platform as well

[sherlock9c1]

Thinking big picture, if the sledgehammer method works for now, there's more value add to be had in other areas. Smash away and move on.

[steveo]

i've been trying stuff all night and i'm just too burned out by this aldl crap to write a proper testing routine.

just try this i hope it works.

http://fbodytech.com/flashhack/

[steveo]

oh, to just test the connection routine, use 'load kernel' in the advanced tab or something, if it loads the kernel good, if not no good

[Grizz1118]

Well received my cable today and read ecm with no problems using flashback .4.1 also made changes in tunerpro then wrote revised bin back to ecm and only error had during either was while writing had latency between boot up of t and e sides

[Grizz1118]

Also had some difficulty lowering the latency in com port settings. If I lowered to 1 when I would plug cable in I could not control my pointer until unplugged cable. Changed to 10 and had no more problems.

[steveo]

i've never seen that before. you might have some weird driver issue but i'm glad it worked for you. you might not have to lower your com port latency with the new connection routine, it works fine at 16ms for me.

[NomakeWan]

Testing 0.4.2, something different happens this time. It still can't connect to the PCM to load the kernel or download the BIN, but unlike previous attempts it's actually making changes to the car. My digital dash freaks out, the SERVICE ASR light comes on, and the auto climate control goes into error mode. SERVICE ABS does not illuminate. It's odd though, I don't recall WinFlash or EEHack causing the digital dash to freak out like that. Maybe I just didn't notice...but I think I would've noticed something like that.

Anyway, as always, logs attached. First log is running as normal, second log is with "alternative ALDL connection routine" checked. The only difference appeared to be that one process was faster to error out than the other.