I recall a 'recommended tool list' on the Forscan sites. For some activities the USB tools are preferred because they provide a faster and more reliable link when doing module programming. So in general USB is preferred - but Bluetooth is likely to be OK these days at a close distance. Both present a serial interface to the software you are using so will be limited by the implemented serial baud rates.
https://forscan.org/forum/viewtopic.php?t=6142
Forscan supports a few tools though. I have some tools that support the J2534 API and can confirm it works for those as well. J2534 is a pretty robust standard now. I have a few different tools that support J2534 and when I load up a J2534 driver for them it will then work with software that has J2534 support - such as licensed versions of Forscan or the Motorcraft IDS software for Ford. Actually most OEM diagnostics software are written to support J2534 these days as the US EPA mandated J2534 support around 2004 I think.
You won't go wrong with an OBDLink device. Reliable and great support.
But I also have one of these and it does everything I need it to do, i just have to manually switch between the HSCAN (
PCM, Cluster) and the MSCAN (Radio, GEM other modules we don't get like climate control and speech recognition). The Airbag and
ABS module answer on a 3rd communications bus called ISO9141 - which these tools can access as well.
https://www.ebay.com.au/itm/31358730...kAAOSwVSBg3YbG
Lukeyson