Differences

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

--- bluetoothconfignew [2019/05/27 21:06]
jfduval
+++ bluetoothconfignew [2020/06/23 01:50] (current)
sbelanger [Bluetooth LEDs:]
@@ Line 3: / Line 3: @@
 The first question is: is my module configured or not? If you obtained it from Dephy, as part of an Actuator Package or another pre-tested setup, it likely is. If you assembled a test adapter yourself, it is guaranteed to not be configured. If you start the setup procedure listed in [[bluetoothconnect|Using Bluetooth]] and your PC shows a peripheral named RBNT-xxxx it indicates that your module has not been configured yet. Keep going through the steps of [[bluetoothconnect|Connecting a module to your computer for the first time]], then jump to the next section of this page.
+====== Bluetooth LEDs: ======
+Each RN-42 Bluetooth module has two LEDs (one green, one red). The list below covers the typical patterns seen on our products. Please refer to the module's [[http://ww1.microchip.com/downloads/en/DeviceDoc/bluetooth_cr_UG-v1.0r.pdf|documentation]] for all the details.
+^ Green LED Blink Rate ^ Mode^
+| No LED | No Power, or held in reset by a microcontroller|
+| Once per second | Waiting for port opening (**can't** be switch in CMD mode)|
+| 2 times per second | Startup/Configuration Timer (default 60s, **can** be switch in CMD mode) |
+| 10 times per second | Module is in Configuring mode (CMD mode) |
+| Solid On | Serial Port Connected |
+^ Red LED Blink Rate ^ ^
+| Blink in Bursts | (In CMD mode) When a command is sent |
+| Blink in Bursts | (In Data mode) When new data is received and the module hasn't been configured yet |
+----
+===== Plan 3.0 =====
 ===== Using the Plan GUI to configure a Bluetooth module =====
   - Make sure that your module is powered and detected by your computer
-  - Use Plan 2.0 to do this, some versions of Plan 3.0 have a know bug in the config code.
+  - Use the latest Plan 3.0 to do this, some versions of Plan 3.0 have a known bug in the config code.
+  - Using the "Bluetooth Config" window, connect to the right COM port.
+  - Click on "Set mode: Cmd".
+    - The Green LED will start blinking quickly. If it doesn't, do not continue with the following steps. Power cycle and start over. You only have a short period of time to enter "set mode: Cmd" from the power-up. Typically around 15s.
+  - Click on "GUI". You'll see quick Orange flashes every 500ms. Wait for the progress bar to be complete.
+  - Click on "Reboot"
+{{ :configbluetoothguiplan3.0.gif |}}
+At this point, you can re-open the COM port and start using the GUI. Power cycling is not typically needed. Windows might keep listing your module as an RBNT-xxxx for a little while, but it will eventually refresh it to be FlexSEA-xxxx. All other computers should see it as FlexSEA-xxxx almost immediately.
+----
+===== Legacy: Plan 2.0 =====
+===== Using the Plan GUI to configure a Bluetooth module =====
+  - Make sure that your module is powered and detected by your computer
+  - Use Plan 2.0 to do this, some versions of Plan 3.0 have a known bug in the config code.
   - Using the Configuration window, connect to the right COM port.
   - Under Bluetooth, click on Set mode: Cmd.
     - The Green LED will start blinking quickly. If it doesn't, do not continue with the following steps. Power cycle and start over.
   - Click on "GUI". You'll see quick Red flashes every 500ms. Wait for the progress bar to be complete.
@@ Line 16: / Line 51: @@
 At this point you can re-open the COM port and start using the GUI. Power cycling is not typically needed. Windows might keep listing your module as an RBNT-xxxx for a little while, but it will eventually refresh it to be FlexSEA-xxxx. All other computers should see it as FlexSEA-xxxx almost immediately.

FlexSEA Wiki

User Tools

Site Tools

Differences

Page Tools