{"id":23883,"date":"2018-06-18T17:31:53","date_gmt":"2018-06-18T22:31:53","guid":{"rendered":"http:\/\/www.multitech.net\/developer\/?page_id=23883"},"modified":"2019-09-04T09:13:50","modified_gmt":"2019-09-04T14:13:50","slug":"bluez-5-serial-setup","status":"publish","type":"page","link":"https:\/\/www.multitech.net\/developer\/software\/mlinux\/using-mlinux\/bluez-5-serial-setup\/","title":{"rendered":"bluez5 Serial Setup"},"content":{"rendered":"

NOTE:<\/strong>\u00a0This information only applies to devices with Bluetooth using\u00a0mLinux\u2122<\/sup> 4.x or higher which has bluez5. For devices using mLinux 3.x, refer to\u00a0Bluetooth<\/a>.<\/p>\n

Incompatible with Bluez 4<\/h2>\n

Bluez 5 is not compatible with Bluez 4 for the most part. There is more emphasis on services using UUID’s in standard Bluetooth. The command rfcomm is deprecated. A DBUS implementation has replaced the rfcomm command line utility.<\/p>\n

For Bluez 5, new applications should use PAN in most cases. PAN creates an internet connection which is much more flexible than RFCOMM. See: Bluez 5 PAN_setup.<\/a><\/p>\n

Name the device<\/h2>\n
    \n
  1. Give the device a reasonable name.<\/li>\n
  2. Create the file \/etc\/bluetooth\/main.conf:<\/li>\n<\/ol>\n
    [General]\r\nName = jakMTCDT<\/pre>\n
    Pair the device<\/h2>\n
    For Linux pairing, see the Pairing<\/a>.<\/p>\n
    For Windows, see\u00a0Bluez 5 PAN_setup.<\/a><\/p>\n
    rfcomm Python script<\/h2>\n
    RFCOMM is controlled using DBUS and works best with a language like C or Python. To assist with writing an RFCOMM application, mLinux comes with an example program called rfcomm<\/i>. rfcomm is found in the directory \/usr\/libexec\/bluetooth\/.<\/p>\n
    syntax<\/h3>\n
    nrt0:~$ \/usr\/libexec\/bluetooth\/rfcomm --help\r\nusage: rfcomm [-h] [-u uuid_or_shortcut] [--pseudoterminal] [--loopback]\r\n              [--debug] [--login]\r\n\r\nBlueZ RFCOMM server.\r\n\r\noptional arguments:\r\n  -h, --help            show this help message and exit\r\n  -u uuid_or_shortcut, --uuid uuid_or_shortcut\r\n                        Service UUID to use. Can be either full UUID or one of\r\n                        the shortcuts: gn, panu, nap. Default: spp.\r\n  --pseudoterminal      Create a pseudoterminal and put slave in \/run\/rfcomm\r\n                        Suitable for background operation.\r\n  --loopback            Echo data for testing (exclusive with pseudoterminal)\r\n  --debug               Verbose operation mode.\r\n  --login               Use RFCOMM to log into this device.<\/pre>\n
    There are basically four modes of operation for rfcomm. The uuid and debug mode may be used with any of the four modes.<\/p>\n