mirror of
https://github.com/RfidResearchGroup/proxmark3.git
synced 2025-01-05 23:52:27 +08:00
Update bt_manual_v10.md
This commit is contained in:
Iceman
GitHub
parent
3e50a30521
commit
e73aab8ed3
1 changed files with 33 additions and 1 deletions
|
|
@ -1,4 +1,5 @@
|
|||
# MANUAL Bluetooth / Battery add-on 'Blue Shark'
|
||||
<a id="top"></a>
|
||||
_rev. v1.1_
|
||||
|
||||
## Table of Contents
|
||||
|
|
@ -29,6 +30,7 @@ _rev. v1.1_
|
|||
* [6.5 Get better signals](#65-get-better-signals)
|
||||
|
||||
## 1. FEATURES
|
||||
^[Top](#top)
|
||||
|
||||
* Built-in Bluetooth 2.0 with EDR Bluetooth module, default baud rate 115200.
|
||||
* Built-in 400 mAh polymer lithium-ion battery, typical standby time up to 3.5 hours.
|
||||
|
|
@ -44,6 +46,7 @@ Built-in battery can support standalone mode, off-line sniffing, off-line readin
|
|||
|
||||
|
||||
## 2. PARAMETERS
|
||||
^[Top](#top)
|
||||
|
||||
* Battery capacity: 400 mAh
|
||||
* Standby time: 3.5h @ StandBy; 2.9h @ LF-On; 50min @ HF-On;
|
||||
|
|
@ -56,6 +59,7 @@ Built-in battery can support standalone mode, off-line sniffing, off-line readin
|
|||
|
||||
|
||||
## 3. ASSEMBLY STEPS
|
||||
^[Top](#top)
|
||||
|
||||
* Unplug your Proxmark3 RDV4.0 device from any usb cable.
|
||||
* Remove the plastic upper case of Proxmark3 RDV4.0 with opener.
|
||||
|
|
@ -72,8 +76,11 @@ Built-in battery can support standalone mode, off-line sniffing, off-line readin
|
|||
</p>
|
||||
|
||||
## 4. COMPILATION / FLASHING
|
||||
^[Top](#top)
|
||||
|
||||
#### 4.1 From Source
|
||||
^[Top](#top)
|
||||
|
||||
Please download the latest source code from Rfid Research Group's Github repo:
|
||||
https://github.com/RfidResearchGroup/proxmark3
|
||||
|
||||
|
|
@ -91,6 +98,8 @@ You are now ready to run the client with the serial port you got from your BT de
|
|||
See instructions below.
|
||||
|
||||
#### 4.2 Homebrew (macOS)
|
||||
^[Top](#top)
|
||||
|
||||
From the [homebrew-proxmark3 readme](https://github.com/RfidResearchGroup/homebrew-proxmark3)
|
||||
|
||||
1. `brew tap rfidresearchgroup/proxmark3`
|
||||
|
|
@ -98,13 +107,17 @@ From the [homebrew-proxmark3 readme](https://github.com/RfidResearchGroup/homebr
|
|||
|
||||
|
||||
## 5. CONNECT WITH BLUETOOTH
|
||||
^[Top](#top)
|
||||
|
||||
You can have both USB cable connect and BT active at the same time and connect to either serial port.
|
||||
You can also switch serial port from inside the proxmark3 client using the new command `hw connect`.
|
||||
|
||||
### 5.1 Windows
|
||||
^[Top](#top)
|
||||
|
||||
#### 5.1.1 Connecting your RDV4.0 with Bluetooth on mobile phone or computer
|
||||
^[Top](#top)
|
||||
|
||||
* Open Bluetooth and search for a device named PM3_RDV4.0.
|
||||
* Enter the paired password 1234 and establish the connection.
|
||||
* The blue state LED on the add-on will keep blinking after the connection is established. Only when the mobile phone or computer opens the correct COM port, the blue LED turns on solid, indicating that the connection is successful.
|
||||
|
|
@ -130,6 +143,7 @@ You can also switch serial port from inside the proxmark3 client using the new c
|
|||
* done!
|
||||
|
||||
#### 5.1.2 Fast connection using dedicated USB Bluetooth adapter under Windows
|
||||
^[Top](#top)
|
||||
|
||||
<p align='center'>
|
||||
<img src="http://www.icedev.se/proxmark3/blueshark/addon_hc06_dongle_1.jpg" alt="Image of blue shark add-on HC-06 white dongle" width="300"></p>
|
||||
|
|
@ -143,8 +157,10 @@ http://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp
|
|||
* look for _CP2104 USB tp UART bridge controller_ under devices in order to get the assigned serial port
|
||||
|
||||
### 5.2 Linux
|
||||
^[Top](#top)
|
||||
|
||||
#### 5.2.1 Connecting rdv4.0 with Bluetooth on Linux computer via native Bluetooth support in the client
|
||||
^[Top](#top)
|
||||
|
||||
This requires to have compiled the client with Bluetooth support.
|
||||
|
||||
|
|
@ -189,6 +205,7 @@ Discovery started
|
|||
```
|
||||
|
||||
#### 5.2.2 Fast connection using dedicated USB Bluetooth adapter under Linux
|
||||
^[Top](#top)
|
||||
|
||||
<p align='center'>
|
||||
<img src="http://www.icedev.se/proxmark3/blueshark/addon_hc06_dongle_1.jpg" alt="Image of blue shark add-on HC-06 white dongle" width="300"></p>
|
||||
|
|
@ -212,6 +229,7 @@ turn on solid.
|
|||
```
|
||||
|
||||
#### 5.2.3 (deprecated) Connecting rdv4.0 with Bluetooth on Linux computer via rfcomm
|
||||
^[Top](#top)
|
||||
|
||||
rfcomm is a deprecated tool which might be unavailable in your Linux distribution.
|
||||
|
||||
|
|
@ -245,8 +263,10 @@ connection is successful.
|
|||
See instructions above (method 1) for initial pairing.
|
||||
|
||||
### 5.3 MacOS
|
||||
^[Top](#top)
|
||||
|
||||
#### 5.3.1 Connecting rdv4.0 with Bluetooth on MacOS
|
||||
^[Top](#top)
|
||||
|
||||
With MacOS Mojave 10.14.5 you could experience some continuosly disconnecting and difficult to recconnect the device at the system wakeup, to avoid this problem do a PRAM reset before to add your Proxmark3 RDV4 Blue Shark:
|
||||
|
||||
|
|
@ -266,17 +286,21 @@ After reboot you can go ahead to pairing your Proxmark3 RDV4 Blue Shark:
|
|||
./proxmark3 /dev/tty.PM3_RDV40-DevB
|
||||
```
|
||||
### 5.4 Android
|
||||
^[Top](#top)
|
||||
|
||||
#### 5.4.1 Fast connection using dedicated Bluetooth (HC-06 Master + CP2102) adapter under Android with Termux
|
||||
|
||||
^[Top](#top)
|
||||
|
||||
1. Make sure you already followed this tutorial https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/termux_notes.md#setup and have Termux with an running Proxmark3 client ready. You need additional the `cp210x` serial usb driver enabled and working, like the `USB_ACM` driver to communicate wireless.
|
||||
2. Insert the Bluetooth adapter with an fitting USB-C/Micro-USB converter into your Android USB port and a serial port `/dev/ttyUSB0` will be created. To see if it's working, run `tsudo ls /dev/ttyU*` and it should list `/dev/ttyUSB0`.
|
||||
3. The adapter will search automatically and establish the connection to BlueShark. The adapter will remember the device that was first connected and after that the same device will be connected. After the connection is established, the blue state LED on add-on will turn on solid.
|
||||
4. If you see this, congratulations, you can run your Proxmark3 client in Termux with `tsudo proxmark3/client/proxmark3 /dev/ttyUSB0`
|
||||
|
||||
## 6. OTHER NOTES
|
||||
^[Top](#top)
|
||||
|
||||
### 6.1 Default settings
|
||||
^[Top](#top)
|
||||
|
||||
Settings of the Blue Shark add-on and of the white dongle:
|
||||
|
||||
|
|
@ -287,19 +311,27 @@ Settings of the Blue Shark add-on and of the white dongle:
|
|||
If you bought your Bluetooth adapter dongle somewhere else, make sure to set the baud rate to 115200 `AT+BAUD8`, the name `AT+NAMEPM3_RDV4.0` and PIN `AT+PIN1234` correctly.
|
||||
|
||||
### 6.1 UART and LED behavior
|
||||
^[Top](#top)
|
||||
|
||||
Bluetooth is connected to Proxmark3 RDV4.0 via UART. The USB and UART interfaces of RDV4.0 can coexist without conflict, and no special switching is required.
|
||||
|
||||
The following link has helpful notes on UART usage and baud rates:
|
||||
https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/uart_notes.md
|
||||
|
||||
### 6.2 Disassembly
|
||||
^[Top](#top)
|
||||
|
||||
There is a heat conductive double-sided tape inside the add-on, which has strong adhesive force. Therefore, if add-on needs to be removed, it needs to be pulled out from the heat sink end with greater efforts. Each disassembly will reduce the viscidity of double-sided tape. When double-sided tape is well protected, it will not affect the second use. Thermal conductivity will be slightly worse and will therefore have a direct impact on the thermal performance of the heat sink.
|
||||
|
||||
### 6.3 Battery charging
|
||||
^[Top](#top)
|
||||
|
||||
The battery charging circuit is turned on by default. Any time a USB cable is inserted, the battery will be automatically charged. The red LED will remain bright when charging.
|
||||
The red LED will be extinguished when charging is completed.
|
||||
|
||||
### 6.4 Get better signals
|
||||
^[Top](#top)
|
||||
|
||||
For the better heat dissipation, we have used a cast metal enclosure for the add-on. As a result Bluetooth wireless signals are sacrificed. For example, if the back of add-on is facing the Bluetooth host, the signal is very bad and the distance will be reduced. The best signal strength can be obtained when the front glass faces the Bluetooth host.
|
||||
If the Proxmark3 is not responding, it may be due to a poor Bluetooth connection. To improve performance, try repositioning the Proxmark3 so the glass face is directed toward the host.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue