doc/bt_manual_v10.md
<a id="top"></a> rev. v1.1
^Top
It can easily connect to Bluetooth mobile phone, portable computer, etc. Without USB cable, complicated permissions or driver settings.
Built-in battery can support standalone mode, off-line sniffing, off-line reading & simulation, etc. The temperature of the device is stable.
^Top
^Top
^Top
^Top
Please download the latest source code from Rfid Research Group's Github repo: https://github.com/RfidResearchGroup/proxmark3
To compile the client and firmware with FPC support, the easiest way is to
Makefile.platform.sample ⇒ Makefile.platform
cp Makefile.platform.sample Makefile.platformMakefile.platform, uncomment the line #PLATFORM_EXTRAS=BTADDON by removing the #make clean; make -j./pm3-flash-fullimageYou are now ready to run the client with the serial port you got from your BT device on your laptop etc.
See instructions below.
^Top
From the homebrew-proxmark3 readme
brew tap rfidresearchgroup/proxmark3brew install --with-blueshark proxmark3^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.
^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.
First time you do this you might need to go into Bluetooth more settings and add a outgoing com port. If so, follow these steps below.
First open your bluetooth settings, click on "more options".
^Top
<p align='center'> </p>Install driver: http://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers
Insert the adapter into the USB port. The adapter will search automatically and establish the connection. The adapter will remember the device that was first connected and after that the same device will be connected.
The adapter button can be used to delete memory so that other add-on can be searched and connected.<p align='center'>
After the connection is established, the blue state LED on add-on will turn on solid.
look for CP2104 USB tp UART bridge controller under devices in order to get the assigned serial port
^Top
^Top
This requires to have compiled the client with Bluetooth support.
Be sure your user has permissions to use Bluetooth
bluetooth: sudo adduser $USER bluetooth then log out and log insudo ...hcitool scan
Scanning ...
aa:bb:cc:dd:ee:ff PM3_RDV4.0
Instead of aa:bb:cc:dd:ee:ff, you'll see your MAC address.
If you don't have hcitool, you can use bluetoothctl and scan on as shown in next section.
./proxmark3 -p bt:aa:bb:cc:dd:ee:ff
The first time, your OS will ask you for pairing. The default PIN is 1234. If PIN is not typed in quickly, the client might timeout. Simply restart it again after pairing.
If your OS doesn't prompt you for pairing or if the device connects and immediately disconnects, you can pair it in command line, e.g. (again, replace with your addon MAC address):
bluetoothctl
[bluetooth]# remove aa:bb:cc:dd:ee:ff
[bluetooth]# pairable on
[bluetooth]# scan on
Discovery started
...
[CHG] Device aa:bb:cc:dd:ee:ff Name: PM3_RDV4.0
[bluetooth]# trust aa:bb:cc:dd:ee:ff
[bluetooth]# pair aa:bb:cc:dd:ee:ff
[agent] Enter PIN code: 1234
[bluetooth]# quit
^Top
<p align='center'> </p>Insert the adapter into the USB port. The adapter will search automatically and establish the connection. The adapter will remember the device that was first connected and after that the same device will be connected.
The adapter button can be used to delete memory so that other add-on can be searched and connected.<p align='center'>
After the connection is established, the blue state LED on add-on will turn on solid.
a serial port /dev/ttyUSB0 will be created, use Proxmark3 client on it
./proxmark3 -p /dev/ttyUSB0
^Top
rfcomm is a deprecated tool which might be unavailable in your Linux distribution.
hcitool scan
Scanning ...
aa:bb:cc:dd:ee:ff PM3_RDV4.0
Instead of aa:bb:cc:dd:ee:ff, you'll see your MAC address.
sudo rfcomm bind rfcomm0 aa:bb:cc:dd:ee:ff
Replace aa:bb:cc:dd:ee:ff by your MAC address.
The blue state LED on the add-on will keep blinking after the
connection is established. Only when the Proxmark3 client opens the
/dev/rfcomm0 port, the blue LED turns on solid, indicating that the
connection is successful.
Use Proxmark client on BT-serial port
./proxmark3 -p /dev/rfcomm0
See instructions above (method 1) for initial pairing.
^Top
^Top
With MacOS Mojave 10.14.5 you could experience some continuously disconnecting and difficult to reconnect the device at the system wakeup, to avoid this problem do a PRAM reset before to add your Proxmark3 RDV4 Blue Shark:
After reboot you can go ahead to pairing your Proxmark3 RDV4 Blue Shark:
/dev/tty.PM3_RDV40-DevB will be created, use Proxmark3 client on it./proxmark3 -p /dev/tty.PM3_RDV40-DevB
^Top
^Top
cp210x serial usb driver enabled and working, like the USB_ACM driver to communicate wireless./dev/ttyUSB0 will be created. To see if it's working, run tsudo ls /dev/ttyU* and it should list /dev/ttyUSB0.tsudo proxmark3/client/proxmark3 -p /dev/ttyUSB0^Top
^Top
Settings of the Blue Shark add-on and of the white dongle:
115200 8N1PM3_RDV4.01234If 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.
^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
^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.
^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.
^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.