RFCOMM vs. NUS

Question

Can anyone tell or give a pointer to info about RFCOMM vs. NUS (or any other vendor specific UART emulation service)? 
 Why are there vendor specific UART emulation services? Why/when should one choose vendor specific service instead of RFCOMM?

Carl Richard · Accepted Answer

Hello, turboscrew. RFCOMM is a Bluetooth Classic protocol and is not supported in Bluetooth Low Energy. Hence, it's not possible to use RFCOMM for BLE communication. You can read more about this here and here . Best regards, Carl Richard

awneil · Answer

Carl Richard gave the answers regarding RFCOMM. 
 NUS is defined here: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.0/ble_sdk_app_nus_eval.html 
 turboscrew said: Why are there vendor specific UART emulation services? 
 Because the Bluetooth SIG, in their wisdom (sic?) , decided not to define a standard one! 
 Why on earth they would make such a glaring omission is anyone's guess. My guess would be that they wanted people to user properly defined Services - not just send arbitrary, unstructured data over a UART emulation?

RFCOMM vs. NUS

Top Replies