Currently, if you call COBDSPI::init(...) while the Freematics ONE is not connected to an OBD port, it will block execution indefinitely.
In some cases (e.g. debugging), this may not be desired. It would be nice to have a timeout option so the code can continue without an OBD host connected. A timeout should probably be considered an error (including setting obd.errors to a non-zero value).
Currently, if you call COBDSPI::init(...) while the Freematics ONE is not connected to an OBD port, it will block execution indefinitely. In some cases (e.g. debugging), this may not be desired. It would be nice to have a timeout option so the code can continue without an OBD host connected. A timeout should probably be considered an error (including setting obd.errors to a non-zero value).