{"id":16508,"date":"2017-01-27T10:14:48","date_gmt":"2017-01-27T16:14:48","guid":{"rendered":"http:\/\/www.multitech.net\/developer\/?page_id=16508"},"modified":"2019-09-04T09:29:09","modified_gmt":"2019-09-04T14:29:09","slug":"bluetooth","status":"publish","type":"page","link":"https:\/\/www.multitech.net\/developer\/software\/mlinux\/using-mlinux\/bluetooth\/","title":{"rendered":"Bluetooth"},"content":{"rendered":"

This feature is only available on certain products and models (not available with all devices).<\/em><\/p>\n

NOTE:<\/strong> This information only applies to mLinux\u2122\u00a0<\/sup>3.x firmware which uses BlueZ4. For Bluetooth on mLinux 4.x or higher, refer to BlueZ5 Pan Setup<\/a>\u00a0and BlueZ5 Serial Setup<\/a>.<\/p>\n

Bluetooth Setup<\/b><\/p>\n

The device includes BlueZ 4 software used as a Bluetooth stack. \u00a0To operate, you must install BlueZ 4 on your Linux computer.<\/p>\n

For newer levels of Linux, you may need to find BlueZ 4 outside of the normal software package manager.<\/p>\n

You can also use BlueZ 5 with Ubuntu on your Linux machine. You need to set up BlueZ 5 with compatibility mode for BlueZ 4 on your PC.<\/p>\n

BlueZ 5 using Ubuntu on Linux Computer \u2013 Set Compatibility Mode<\/b><\/p>\n

To set BlueZ 5 in compatibility mode:<\/p>\n

1. Find the file \/etc\/systemd\/system\/dbus-org.bluez.service<\/b>.
\n2. Change the line by replacing:<\/p>\n

ExecStart=\/usr\/lib\/bluetooth\/bluetoothd<\/pre>\n
with<\/p>\n
ExecStart=\/usr\/lib\/bluetooth\/bluetoothd --compat<\/pre>\n
3.\u00a0To restart bluetooth, enter:\u00a0<\/span><\/p>\n
pc: sudo systemctl daemon-reload\r\npc: sudo systemctl restart bluetooth<\/pre>\n
4. To change permissions on \/var\/run\/sdp<\/b> , enter:\u00a0<\/span><\/p>\n
pc: sudo chmod 777 \/var\/run\/sdp<\/pre>\n
5. If you are using GUI management on your Linux system, verify that Bluetooth is on and set it to visible.\u00a0Or if you are using the command line, enter:\u00a0<\/span><\/p>\n
pc: sudo hciconfig hci0 piscan<\/pre>\n
Classic Bluetooth Serial Communications<\/b><\/p>\n
If you log in through the debug port to the device using Minicom, you need to change the Minicom control character.\u00a0You can’t have two levels of Minicom and control both with the same character.<\/p>\n
You can also use SSH instead.<\/p>\n
To change the character in Minicom:<\/p>\n
1. Enter the command:<\/p>\n
pc: sudo minicom -s<\/pre>\n
\u00a0This command displays the Configuration menu<\/b> for Minicom.<\/p>\n
2. \u00a0\u00a0Under the Configuration<\/b>, select Screen and keyboard<\/b>.<\/p>\n
3. \u00a0\u00a0Enter the command key: B <\/b>(the resulting command key is <ctrl> + B)<\/b>.<\/p>\n
4. \u00a0\u00a0Select <esc><\/b> which returns you to Configuration<\/b>.<\/p>\n
5. \u00a0\u00a0Select Save setup as dfl <\/b>which sets your recent configuration as default.<\/p>\n
6. \u00a0\u00a0Select Exit from Minicom<\/b>.<\/p>\n
Bring up Bluetooth<\/b><\/p>\n
To bring up Bluetooth using Ubuntu, enter this command:
\n
\n<\/span><\/p>\n
pc: sudo hciconfig hci0 up<\/pre>\n
Bluetooth reset<\/b><\/p>\n
Bluetooth resets automatically on reboot.<\/p>\n
To manually reset Bluetooth, enter the following commands:<\/p>\n
pc: sudo systemctl daemon-reload\r\npc: systemctl restart bluetooth<\/pre>\n
Bluetooth TTY communications with Ubuntu<\/b><\/p>\n
To use Ubuntu for Bluetooth communications:<\/p>\n
1. Enter the command:<\/p>\n
pc: sudo hciconfig hci0 up<\/pre>\n
2. On Ubuntu Linux, determine the bluetooth MAC address. \u00a0Enter the command:\u00a0<\/span><\/p>\n
pc: hciconfig<\/pre>\n
The system displays the following:\u00a0<\/span><\/p>\n
hci0:\u00a0 Type: BR\/EDR\u00a0 Bus: USB\r\nBD Address: 00:02:72:21:A7:D7\u00a0 ACL MTU: 1021:7\u00a0 SCO MTU: 64:1\r\nUP RUNNING PSCAN ISCAN\r\nRX bytes:59680 acl:3203 sco:0 events:1827 errors:0\r\nTX bytes:47076 acl:3264 sco:0 commands:115 errors:0<\/pre>\n
For this example above, the address is: 00:02:72:21:A7:D7<\/b><\/p>\n
<\/b>3. Create a TTY node for Bluetooth communications (for both sides). Enter the following:\u00a0<\/span><\/p>\n
pc: sudo mknod -m 666 \/dev\/rfcomm0 c 216 0<\/pre>\n
4. Make Bluetooth discoverable on a scan. Enter:\u00a0<\/span><\/p>\n
pc: sudo \/usr\/sbin\/hciconfig hci0 piscan<\/pre>\n
5. Add the channel. Enter:\u00a0<\/span><\/p>\n
pc: sudo \/usr\/bin\/sdptool add --channel=22 SP<\/pre>\n
6. Start RFCOMM to listen for a connection. Enter:\u00a0<\/span><\/p>\n
pc: sudo rfcomm listen \/dev\/rfcomm0 22 &<\/pre>\n
7. Now log into the device. Use the MAC address from Ubuntu on the rfcomm command line as in this example. Enter the following:\u00a0<\/span><\/p>\n
mtcdt: \/usr\/sbin\/bluetoothd\r\nmtcdt: hciconfig hci0 up\r\nmtcdt: hcitool scan\r\nmtcdt: mknod -m 666 \/dev\/rfcomm0 c 216 0\r\nmtcdt: rfcomm connect \/dev\/rfcomm0 00:02:72:21:A7:D7 22 &<\/pre>\n
Example output (Bluetooth messages are written to the console):\u00a0<\/span><\/p>\n
[1] 571\r\nBluetooth: RFCOMM TTY layer initialized\r\nBluetooth: RFCOMM socket layer initialized\r\nBluetooth: RFCOMM ver 1.11\r\nConnected \/dev\/rfcomm0 to 00:02:72:21:A7:D7 on channel 22\r\nPress CTRL-C for hangup<\/pre>\n
8. Now you list the connections from each side entering the same hcitool con<\/strong> command twice (one for master and one for slave):\u00a0<\/span><\/p>\n
mtcdt: hcitool con\r\nConnections:\r\n< ACL 00:02:72:21:A7:D7 handle 1 state 1 lm MASTER<\/pre>\n
mtcdt: hcitool con\r\nConnections:\r\n> ACL 00:23:A7:49:5C:D9 handle 11 state 1 lm SLAVE<\/pre>\n
The other system should now see the connection.<\/p>\n
9. Start minicom on the computer and the device:\u00a0<\/span><\/p>\n
pc: sudo minicom -D \/dev\/rfcomm0\r\nmtcdt: <ctrl>bE\u00a0 [This turns echo on]\r\nmtcdt: <ctrl>bA\u00a0 [This adds a line feed]\r\nmtcdt: minicom -D \/dev\/rfcomm0\r\nmtcdt: <ctrl>aE\u00a0 [This turns echo on]\r\nmtcdt: <ctrl>aA\u00a0 [This adds a line feed]<\/pre>\n
Now you have a TTY connection to communicate.<\/p>\n
10. Type a message and watch it appear on the other side.<\/p>\n
11. To terminate in minicom, enter:
\n<\/span><\/p>\n
mtcdt: <ctrl>aX or <ctrl>bX.<\/pre>\n
12. If you connect to the rfcomm0 device because the interface is in a bad state, reset as shown:\u00a0<\/span><\/p>\n
mtcdt: rfcomm release 0\r\nmtcdt: hciconfig hci0 up\r\nmtcdt: \/usr\/sbin\/hciconfig hci0 piscan<\/pre>\n
This clears rfcomm0<\/p>\n
13. Now enter the appropriate rfcomm<\/i> command on both sides and the link should come back up.<\/p>\n
Classic Bluetooth File Push (sending data)<\/b><\/p>\n
To do File Push<\/b> on Bluetooth, you first must verify your computer runs Ubuntu with Bluetooth. Use the Ubuntu system with Bluetooth to receive the data.<\/p>\n
Follow these instructions to do File Push<\/b>:<\/p>\n
1. On the device, install the following two packages:<\/p>\n
mtcdt: libopenobex1_1.5-r0.0_arm926ejste.ipk\r\nmtcdt: obexftp_0.23-r0.0_arm926ejste.ipk<\/pre>\n
2. In Ubuntu, under Personal File Sharing Preferences<\/b> and Receive Files over Bluetooth<\/b>, check Receive Files in Downloads folder over Bluetooth<\/b>.<\/p>\n
3. In the drop-down, Accept files,<\/b> <\/i>select <\/i>Always<\/b> <\/b>and check Notify about received files<\/b>.<\/p>\n
\"\"<\/p>\n
Received files will be in the Downloads<\/b> directory.<\/p>\n
4. Obtain the MAC address<\/b> of the ubuntu system using this command:
\n<\/span><\/p>\n
mtcdt: hciconfig<\/pre>\n
The system displays the following results:\u00a0<\/span><\/p>\n
hci0:\u00a0 Type: BR\/EDR\u00a0 Bus: USB\r\nBD Address: 5C:F3:70:74:04:AF\u00a0 ACL MTU: 1021:8\u00a0 SCO MTU: 64:1\r\nUP RUNNING PSCAN ISCAN\r\nRX bytes:98993 acl:854 sco:0 events:904 errors:0\r\nTX bytes:21459 acl:632 sco:0 commands:289 errors:0<\/pre>\n
In this case, the MAC address<\/b> is 5C:F3:70:74:04:AF<\/b> labeled as\u00a0BD address<\/b>.<\/p>\n
5. Copy a large file to the device for testing.
\n<\/span><\/p>\n
mtcdt: cd \/boot\r\nmtcdt: scp initrd.img-3.13.0-98-generic root@conduit:\/var\/volatile<\/pre>\n
6. On the PC, find the channel number to specify in the list the services of the Ubuntu system. Enter:\u00a0<\/span><\/p>\n
PC: sdptool browse local<\/pre>\n
\u00a0<\/span>The following results display:\u00a0<\/span><\/p>\n
...\r\nService Name: OBEX Object Push\r\nService RecHandle: 0x10008\r\nService Class ID List:\r\n\u00a0 \u00a0 \u00a0 \u00a0\"OBEX Object Push\" (0x1105)\r\nProtocol Descriptor List:\r\n\u00a0 \u00a0 \u00a0 \"L2CAP\" (0x0100)\r\n\u00a0 \u00a0 \u00a0 \"RFCOMM\" (0x0003)\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0Channel: 9\r\n\u00a0 \u00a0 \u00a0 \"OBEX\" (0x0008)\r\nProfile Descriptor List:\r\n\u00a0 \u00a0\"OBEX Object Push\" (0x1105)\r\n \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Version: 0x0100\r\n...<\/pre>\n
Under OBEX Object Push<\/b>, look for Channel<\/b> in the listing. In this case, the channel number is 9<\/b>.<\/p>\n
7.To execute the File Push, enter the directory location and the following command including the MAC address and channel number:\u00a0<\/span><\/p>\n
mtcdt: cd \/var\/volatile\r\nmtcdt: time obexftp -SH -b 5C:F3:70:74:04:AF -B 9 -U none -p linux_3.13.0.orig.tar.gz -o f1<\/pre>\n
Bring down Bluetooth<\/b><\/p>\n
To bring down Bluetooth using Ubuntu, enter this command:
\n<\/span><\/p>\n
pc: sudo hciconfig hci0 down<\/pre>\n","protected":false},"excerpt":{"rendered":"
This feature is only available on certain products and models (not available with all devices). NOTE: This information only applies to mLinux\u2122\u00a03.x firmware which uses BlueZ4. For Bluetooth on mLinux 4.x or higher, refer to BlueZ5 Pan Setup\u00a0and BlueZ5 Serial Setup. Bluetooth Setup The device includes BlueZ 4 software used as a Bluetooth stack. \u00a0To […]<\/p>\n","protected":false},"author":1478,"featured_media":0,"parent":9184,"menu_order":9,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"class_list":["post-16508","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/16508","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/users\/1478"}],"replies":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/comments?post=16508"}],"version-history":[{"count":64,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/16508\/revisions"}],"predecessor-version":[{"id":16559,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/16508\/revisions\/16559"}],"up":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/9184"}],"wp:attachment":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/media?parent=16508"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}