sleuth255

Yup, recovered just fine to v1.1.18. Just need to figure out why flashing my test build bricked it. The HEX file for my test build was the same size as...

Ok... interesting data coming up. I successfully compiled version 1.3.1 with a quick change just to make sure I didn't get installed versions mixed up (settings/about says "FW: 1.3.1 (Sleuth)")....

As I figured, commenting out lines 768-774 in handler_ibus.c had no effect. Cutout still happens. Just to dot all my "i"'s and cross all my "t"s, I down revved to...

The display appears to power off completely then come back on a few seconds later showing the same screen as before. Not seeing anything in the code that leaps out...

I think that a good example of your module interdependency description might also be the TV and NAV devices which hand off control of the GT device. I use my...

Well this is a bother: navcoder can't snoop the I-Bus when its using a K+DCAN cable. It appears to only be seeing traffic that it generates. Looks like I'm going...

Ha! Never thought to even look at the BluBus CLI... Thought the UART connection was for flashing only lol. Setting things up now...

Still working to get a trace; couldn't get it to fail initially... Finding out how added another piece to the puzzle: the problem only happens after the car wakes up...

Got it! The screen cut out right after this happened: [44430] DEBUG: IBus: RX[7]: E8 05 D0 59 11 02 77 [44521] DEBUG: IBus: RX[5]: F0 03 68 01 9A...

Hmmm... looks BlueBus is sending something to the GT at 46791 and its responding at 46870 just before the cutout. Ident? Then ident response is logged right around where screen...