i know on the fbody, it doesn't speak unless it's spoken to... and i think the bbody module is the same. silencing it wouldn't hurt anything anyways. on the f-body, the "traction control" light is a hardware thing, doesn't use the aldl bus
once i have your working code in my hands i'll probably abstract things even further then push it into beta and get some b-body guys testing. that way we can have a cookie cutter connection method for all three vehicle types which can improve as we go.
it'd be nice if there was a way to determine beyond a shadow of a doubt if modules ever push notifications to the aldl stream even without a heartbeat, but it's undocumented, so logging or hacking the module apart are the only ways... i doubt it's common practice, but errors in the datastream often make me go 'hmm' since they really shouldn't happen beyond actual electrical noise.
we really need to keep the vehicle type selector regardless, i need that branching for the next generation of definition file (which will allow us to have vehicle-specific module readouts for sir/abs/etc), and that can't be runtime configurable anyway, so that gives us the opportunity to make each method of initial connection and its maintenance super optimal.
Reply With Quote
Bookmarks