Differences

This shows you the differences between two versions of the page.

--- dh4d:bluetooth [2017/02/16 18:42] – wadmin
+++ eros:bluetooth_module [2017/09/06 20:06] (current) – ↷ Page moved and renamed from dh4d:bluetooth to eros:bluetooth_module Pedro Ramilo
@@ Line 1: / Line 1: @@
 ===== Using the Bluetooth Interface Module =====
-The Bluetooth interface module can be optionally installed at factory, when we build your DHD4D hand.
+The Bluetooth interface module can be optionally installed at factory, when your unit is manufactured.
-It provides a console using the Bluetooth Serial Port profile with similar functionality to the [[dh4d:usbconsole|USB console]]. The main difference with using Bluetooth is that you can access and Query the hand wireless, even **while your robot is operating**.
+The USB interface used the Bluetooth Serial Port profile which creates a Virtual COMM port on the Host device. By default it is configured to expose the [[eros:consolecommands|Console]].
+The firmware is capable of simultaneously receiving and process commands through the main connector the Console, which means you can perform **online, wireless diagnostics** and maintenance of your unit.
-In addition, the RH4D/DH4D can simultaneously receive and process commands through the Dynamixel Protocol and the console, making it ideal for on-the-fly diagnostics, fine tuning and control.
 ==== Connecting to your hand over Bluetooth ====
 Each hand is configured at the factory with a broadcasting name ''SEED_[S/N]''.
-For ease of use, you can change this name after connecting, using the [[dh4d:consolecommands|''bwn'']] console command.
+For ease of use, you can change this name after connecting, using the appropriate [[eros:consolecommands|console command]].
 For security reasons, pairing with the hand is also protected by a code. The **default code is 1234**.\\
-We strongly recommend changing the default pin once you receive your hand. This should be done for security reasons to prevent  unexpected  behavior caused by unauthorized users connecting to the unit.
+We strongly recommend changing the default pin once you receive your hand. This should be done for security reasons to prevent  unexpected  behavior caused by unauthorized access.
-Changing the pairing code is a very simple step and it done through the [[dh4d:consolecommands|''bwp'']] console command.
+Changing the pairing code is a very simple step and it done through the appropriate [[eros:consolecommands|console command]].
-(if you happen to lose your pairing code, it can be reset via the [[dh4d:usbconsole|USB Console]] with the ''bwp'' command or through the Dynamixel Protocol/Control Tables, in the appropriate address of the Virtual ID)
+(if you happen to lose your pairing code, it can be reset via the [[eros:settingup_usbconnection|USB connection]]  or through the Dynamixel Protocol/Control Tables, in the appropriate address of the Main board ID)
 ==== Connection procedures ====
@@ Line 90: / Line 91: @@
 === iPhone / iOS ===
-Currently the DH4D uses a Bluetooth 2.0 module.
+Currently the Seed Robotics units use a Bluetooth 2.0 module.
 Unfortunately due to Apple's own licensing restrictions, it is not possible to connect a stock iOS device to a generic Bluetooth 2.0 module with SPP profile.\\
@@ Line 98: / Line 99: @@
     * Check if your hand has the Bluetooth module installed. Bluetooth is an optional component that must be fitted when your hand is manufactured.
     * Make sure your hand is powered up, __using External Power__. If you are connecting to the hand over USB without applying external power, only the main processor is powered. External power is required to power the Bluetooth module.
-    * Check if the the Bluetooth module has been disabled using the Control tables. The [[dh4d:dynamixelcontroltables|Control table]] for the Virtual ID has a specific setting to power off the Bluetooth module in order to save energy.
+    * Check if the the Bluetooth module has been disabled using the Control tables. They have a specific setting to power off the Bluetooth module in order to save energy.
-    * For advanced troubleshooting procedure, connect to the [[dh4d:usbconsole|USB console]] and issue the command ''bti''. It will report if the Bluetooth module is installed, its power status and the name and pairing codes. If necessary reset the name and pairing code using the ''bwn'' and ''bwp'' commands.
+    * For advanced troubleshooting procedure, connect via [[eros:settingup_usbconnection|USB]]  and issue the command ''about'' and ''status''. It will report if the Bluetooth module is installed, its power status and the name and pairing codes. If necessary reset the name and pairing code using the appropriate [[eros:consolecommands|console commands]].
-  * I send commands to the hand but it does not respond
+  * I send commands to the hand but it does not respond:
     * Ensure you are properly connected to the hand and that it is powered up
     * Make sure you have the line termination set to ''CR+LF''. The unit expects a ''CR+LF'' at the end of each command. This is an option in most Serial Terminal applications, so please ensure it is set accordingly.