There isn't really a direct replacement tool for rfcomm.īluetoothctl will show what services (specified by UUID) the RPi is making available.

Try to develop one end at a time so it is clear where the issue is. The second thing to mention is that trying to develop both ends of the connection at the same time makes life tricky. The first thing to mention is that rfcomm was deprecated back in 2017 by the BlueZ project so if you are following a tutorial, it is likely that it is out of date.

How should I fix this? What else should I check? I've restarted W10 and Raspberry a couple of times, also redo all the BT scanning and pairing - same issue every time. On the Raspberry side all this time the screen terminal session is still active and blank - if I'm pressing some keys nothing shows on RealTerm ( COM9) side. When trying to connect to COM9 RealTerm successfully connects but doesn't send any data over BT (or the Raspberry doesn't receive - not sure), and this weird thing: TXD 'pin' remains always ON until I disconnect: When trying to connect to COM5 RealTerm throws me the following error, so can't do any testing using this Outgoing COM port - I've also tested using TeraTerm - same issue, won't open the port: Now on W10 side I'm using RealTerm tool and I'm trying to connect to one of the new two COM ports that were created after pairing and connecting to Raspberry: ( COM5 - Outgoing, and COM9 - Incoming) - not sure which one should be used so I'll just try both of them. On Raspberry side I first set the BAUD rate associated to /dev/rfcomm0 port to 19200 using this command: stty -F /dev/rfcomm0 19200, then I start a terminal session on this port using the screen tool: screen /dev/rfcomm0 19200. Now I want to test the BT communication between this two devices, and I want to pass some messages using terminals.

On the W10 machine I now now have this following setup: I did the scanning, pairing and trusting using the bluetoothctl utility, then I used the rfcomm utility to create a COM port ( /dev/rfcomm0) on Debian side: sudo rfcomm connect hci0 38:FC:98:47:05:67 - W10 automatically connected and it's looking like this: I successfully paired and connected from Raspberry (using a SSH terminal) to a Windows 10 machine (Surface 3 tablet). I have a Raspberry PI 3 model B, with built-in Bluetooth hardware, and I'm running the latest Debian distro on it (Linux raspberry 5.15.61-v7+).

Windows 10 rs232 terminal