Hi!

It’s worth checking the adapter for this one – the main reason is possible interference on the CANBUS system that’s leading to data corruption, or a state where data isn’t reaching the immobiliser when it should be from other ECUs.

There are 2 causes for this that I know of:

* The adapter isn’t terminated properly and is causing issues on the CANBUS system (this would be a design issue, or a build quality issue where the incorrect termination is used, or simply not present)

* That the adapter has become disconnected and then starts searching for the correct protocol to use. During this, depending on the vehicle ECU and adapter, it may in some cases temporarily block communications (this can be seen on some Prius vehicles which are sensitive to this). Setting the protocol to use in the vehicle profile will usually prevent this issue if the connection is lost (though, the connection to the adapter shouldn’t drop out anyway, on a properly functioning phone and adapter). You can see what protocol the vehicle ECU uses when connected to it (check the adapter status screen) then set that protocol in the vehicle profile

I’m not very familiar with the carista adapters in terms of reliability issues (usually that’s a good thing as it means I’ve not seen many complaints) though you need to keep in mind it may have gone faulty.

Try the protocol option first, if it keeps happening, then check to see if the adapter connection was recently dropped (there was an option added in the latest update sent out today to do voice notifications for connection and disconnection from the adapter which should be helpful!)