Hi @aol , support for exlap has appeared in other products. If you were to simply support it but not the authentication material which you've no reason to know, your work likely would be under the existing licenses in which the protocol was published under.
My concern with it commercially, is if the data rates on some channels are sufficient to avoid aliasing.
@dirtyfreebooter fwiw, I have a working concept of exlap to racechrono on a ESP32-S3. It ingests exlap over wifi, and produces a canbus pid sent over DIY bluetooth.
I need to still build out all the channels and stress test the data rates to see whether it is a reliable signal with the additional overhead of exlap->wifi->processing->ble->racechrono.
It may not be good for high frequency signals, or the latency may be too high, or the esp32 support unreliable (https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/coexist.html)
I will use it, regardless, to capture low rate signals that are not on the chassis canbus like the TPMS sensors. This saves me from having to wire two canbus channels.
