/furble

A wireless remote shutter release/button for Fujifilm (eg. X-T3, X-T30, X-T4, X-S10, X100V) and Canon EOS (eg. M6, RP) cameras.

Primary LanguageCMIT LicenseMIT

furble - FUjifilm Remote Bluetooth Low Energy

PlatformIO CI

A wireless remote shutter release originally targeted at Fujifilm mirrorless cameras.

The remote uses the camera's native Bluetooth Low Energy interface so additional adapters are not required.

furble is developed as a PlatformIO project for the M5StickC and M5StickC Plus (ESP32 based devices).

Supported Cameras

The following devices have actually been tested and confirmed to work:

Motivation

I found current smartphone apps for basic wireless remote shutter control to be generally terrible. Research revealed the main alternative was attaching a dongle to the camera, of which there were many options varying in price and quality. I really just wanted the Canon BR-E1, but for my camera.

What Works

  • scanning for supported cameras
  • initial pairing
  • saving pairing data
  • connecting to previously paired camera
  • shutter release

Possibly Supported Cameras

Fujifilm

Given reports from the community and access to additional cameras, it seems many (all?) Fujifilm cameras use the same Bluetooth protocol. Reports of further confirmed working Fujifilm cameras are welcome.

Canon

With access to a Canon EOS M6, I was able to implement support for it. Other Canon cameras might work, but I suspect the shutter control protocol will be different. @wolcano kindly implemented support for the Canon EOS RP.

Protocol Reverse Engineering

Android supports snooping bluetooth traffic so it was trivial to grab a HCI log to see what the manufacturer supplied camera app was doing.

For all supported cameras, a snoop log of:

  • scanning
  • pairing
  • re-pairing
  • shutter release

was analysed with Wireshark.

It was then an experiment in reducing the interaction to the bare minimum just to trigger the shutter release.

Supporting More Cameras

The best way is to repeat the previous steps, analyse the bluetooth HCI snoop log with Wireshark, implement, then test against the actual device.

Requirements

Hardware

I wanted a complete solution out of the box to have:

  • bluetooth low energy
  • physical button
  • visual indicator (LED or display)
  • battery
  • case
  • low cost

My search concluded with the M5StickC from M5Stack. The M5StickC has since been EOL and replaced with the M5StickC Plus.

The M5StickC is an ESP32 based mini-IoT development kit which covered all of the requirements (and more). At time of writing, M5Stack sell the M5StickC for US$9.95. The M5StickC Plus sells for US$19.95.

Software

The project is built with PlatformIO and depends on the following libraries:

Installation

PlatformIO does everything assuming things are installed and connected properly. In most cases it should be:

  • clone the repository
  • plug in the M5StickC
    • platformio run -e m5stick-c -t upload
  • OR plug in the M5StickC Plus
    • platformio run -e m5stick-c-plus -t upload

Usage

The top level menu has the following entries:

  • Connect
  • Scan
  • Delete Saved
  • Settings
  • Power Off

On first use, put the target camera into pairing mode, then hit Scan. If the camera advertises a known, matching signature, it should appear in the list. You can then connect to the target camera, which, if successful, will save the entry and show the remote menu.

Upon subsequent use it should be enough to hit Connect, selecting the previously paired device and leads to the remote menu.

From the remote menu you may choose to disconnect or control the shutter.

Things To Do

  • error handling is atrocious (it'll probably crash, then restart, which is OK, the M5StickC boots quickly)
  • improve the device matching and connection abstractions
    • especially if more cameras get supported

Links

Inspiration for this project came from the following project/posts:

Related projects: