Re: BlueSaab v6.1

Posted by Karlis on Jun 08, 2019; 9:15pm
URL: http://bluesaab-forum.90.s1.nabble.com/BlueSaab-v6-1-tp1356p1449.html

It's a bit more complicated than that.

If a node (OpenSID, BlueSaab, TWICE, DICE, etc.) has the capability to write on SID, it has to send out SID resource requests every second. These requests have a byte that tells SID if the resource is needed immediately or "I can write to SID, but at this moment I don t want to".

In theory if BlueSaab has been granted access to SID and OpenSID comes in, BlueSaab could detect that and step down. However, SID will not grant OpenSID access because BlueSaab is already using the top priority access type. Even if SID switches between the two I'm pretty sure it will cause a lot of flickering -> bad UX.

We have to remember that OpenSID is based on a tool SAAB engineers used to gather test metrics from engine runs so while running the tool they did not care (did not grant) about any other equipment on the car except for engine management system.