gkoh / furble Goto Github PK

Hi

I am not a tech person but I do own a gfx100s and would love a wireless remote

I have no clue about coding etc but would be happy to pay for one to be made and I would test....

Adrian

Shutter lock currently requires 2 hands:

• hold button b
• press button a

This seems overly complicated.

This can be simplified to be just be:

• long press button a

Where 'long press' we can arbitrarily define as 'hold button a down for longer than 500ms'.

Canon EOS support for focus during shutter control doesn't behave as expected.
Investigate how or whether it is possible to bring up to parity with the Fujifilm cameras.

The web installer is quite ... minimal.
Add some details of the project or similar so people know what it is without needing to click through to the actual github project.

When A or B are pressed (and not released) the camera does auto-focus and releases shutter immediately, not waiting for button (A or B) release.
Tested on Canon EOS-RP

          > Have you tried increasing the transmit power in settings?

Yeah, it was on max. Ended up just dropping the remote below the tripod whenever I needed to go more than a couple of metres away

Originally posted by @matthudsonau in #73 (comment)

Is it possible to dim the Display more or (better) use a black backround with white font (for OLED users) to save Battery ❓

Thank you.... 😄

Where is the Donation Button? I would say "Thanks" to the dev...

          I'm going to throw it here (because it should be handled by the UI changes): Connect should not be an option if the saved connection list is empty

Originally posted by @matthudsonau in #80 (comment)

With technical advance and the advent of esp-web-tools, flashing furble to a device can now be done without needing to install software.

The following can be done to support this:

• publish all 4 binary artifacts generated by platformio for flashing an ESP32
• publish a manifest as required by esp-web-tools
• create a very basic index page to include esp-web-tools
• identify a hosting platform for the web installer
• create a workflow to automate upload and deployment during release

As started in #51 by @sbstjn and added in #60 , creating a more feature rich interval timer

Will there be a support release for M5StickC PLUS2?
Thanks

Hey, Congratulation for a very nice 1.0 Version and a bin. I flashed the bin file with ESPHome Alllication and it works perfect. I tried every Theme/Settigs and im really happy. Especially the „focus only“ - i love it - THX! Donation coild be also add to the main page ☺️

Now to the suggestion: maybe you could edit, that the installation is easy with ESPHome and link to the App 😉

To better support non-developers, do the following:

• start generating binary releases
• start versioning said releases
• identify flash programmers for:
  • Windows
  • MacOS
  • Linux?

The ultimate aim would be to reduce the consumer workflow to:

• buy M5Stick
• install flashing tool
• download furble binary release
• program M5Stick
• use furble

This would remove the requirement for non-developers to install the entire ESP32 toolchain.

Discussed in #94

Add a remote control mode that supports shutter lock.
Use case is described by @matthudsonau here.

Preface: I have no idea if this belongs in this project, or if I should just 'steal' the camera communication parts and make my own

I now have a M5Stack Core2 (ok, two: I like to have a spare to loan out to people). With the touch interface and the addition of two extra buttons (three below the screen and two on the side of the case) there's definitely a lot more options for a UI than on the M5Stick, plus the bigger screen means that the current UI could definitely stand to be improved

If you have more than one remote they're all called furble.
This makes it difficult/messy if you're developing/testing or doing interesting things with multiple cameras and multiple remotes.

Add a way to identify the remote via name. Perhaps using some fragment of the ESP32 ChipID?

Support was confirmed for:

• X-H2S (@val123456)
• XT5 (@stulevine)

See #42 and #44.

Discussed in #42

Maybe a more "User Friendly" Tutorial will open this Project to more Users! Its so f**king Awesome what Fujifilm Users can get here!

Like this step-by-step guide.... (just as an idea)

1. Install PlattformIO (Infos here: https://docs.platformio.org/en/latest//core/installation/methods/installer-script.html#super-quick-macos-linux)
2. Download this Code and extract it to the folder.....
3. Plug in your... and turn it on...
4. Start this code in Terminal...

Just a little more Infos ;-)

With #43 done, need to update the README to include:

• links to device (for purchase)
  • GPS unit
• new menu settings to enable GPS
• new device support
  • M5Core/M5Core2
  • M5StickC Plus2
• interval mode
• shutter lock
• web based install method

Maybe it would be better to find this nice Project, when you rename it from

"furble - FUjifilm Remote Bluetooth Low Energy"

to

"furble - Fujifilm Remote Bluetooth Trigger/Button" (Trigger or Button or both)

I just found the way to furble in an Forum as a link from anybody. With Google search i cant find a link to furble ;-)

Donation button + better finiding in google search = Fame & Money 🤣

To ensure future merges don't suffer from indentation or style conflicts, apply a format now and enforce it with CI.
Adding a clang-format file would help here.

The release of new firmware for recent Fujifilm cameras to support the Tripod Grip TG-BT1 has broken our pairing.
During a new pairing request, furble claims success, but the camera just sits there waiting for a valid pairing partner.
Going to need a fix for this, furble is now dead with the new firmware.

Instead of the backlight turning off, you get a fun strobe effect. Guess the LCD pinout change wasn't entirely without problems...

There's a fair amount of code duplicated between EOS M6 and EOS RP.
Try to refactor and remove it.

At the same time, work out if the focus button could be supported.

After #36, it will still be useful to separate pairing and connecting.
Based on this, the connection for older Canon EOS (smartphone only) will be different to newer Canon EOS (remote control).

Refactoring will allow us to use the same pairing code for all Canon EOS, but different connect code.

At the moment there is no monitoring of the connection status by the remote, so often the only indication that the connection has failed is that the camera stops responding

Sometime in the last 12 months the M5StickC was end-of-life'd with the M5StickC PLUS being the fully compatible replacement.
The M5StickC PLUS has a larger screen, thus the hacks to M5ez will need to be updated.

Is it possible to use the other Key as Focus button? So we could have Focus & Shutter... the M5 have a second button 😉

Thanks for the nice Code !

I ordered at "banggood" for 25$ my m5Stick C-Plus and connected it with my Fujifilm X-S10. Everythings works YEAH

Thank you!

See #20.

Newer cameras that are support the new tripod remote (TG-BT1) have new firmware (eg. 1.50 for X-T30).
With this firmware, when furble connects, a little smart phone icon appears under the Bluetooth icon.
This is expected as furble is built from replicating the protocol between the smart phone app and the camera.

It would nice if we could work out the TG-BT1 protocol as that is more in-line with furble.

The underlying M5Stack libraries are separate for M5StickC and M5StickC-Plus.
With the new M5Unified library, it will much simpler to support the entire M5 range without managing the device differences ourselves.

See here for more:
https://github.com/m5stack/M5Unified

By default the ESP32 uses transmit power level 5, which is +3dBm.
Community reports suggest this is good for 10-15 metres (I have not personally tested).

Add a transmit power setting, allowing one to choose level 6 (+6dBm) and 7 (+9dBm).
This will allow one to perhaps increase operational distance, but possibly at the cost of battery power.

There's no reason why we cannot support the other M5Stack controller variants, we just need to careful with menu handling.

See #50.

The default camera app in both iOS and Android triggers the shutter when the 'volume up' key is sent.

This requires:

• building a BLE server
  • with the mobile device, the connection orientation is reversed, the ESP32 is the peripheral whilst the mobile is the central
• advertising the right services (HID, etc)
• pairing with the mobile as a keyboard
• wiring the shutter release to send 'volume up'
• bending the workflows of 'normal' cameras and mobiles to be similar

I have heard from other users who have updated their Fujifilm cameras that the remote has stopped working

Can this be corrected so to will work?

Adrian

Thanks to @wolcano for delving into the Canon EOS more.
It looks like pairing and connecting for Canon can and should be separated, especially due to an 'acceptance' bit where the camera needs an 'OK' to complete the pair.

For Canon EOS, the pair acceptance result comes via a BLE notification.
Which seems to be:

• service UUID 00010000-0000-1000-0000-d8492fffa821
• characteristic 00010006-0000-1000-0000-d8492fffa821
• indicator value 0x02 -> accept
• indicator value 0x03 -> reject

This is consistent with the efforts from https://github.com/robot9706/CanonBLEIntervalometer

As provided by @sbstjn in #51

Equipment: M5StickC PLUS, GFX 100ii

When in shooting mode, quickly tapping a button only seems to trigger the shutterPress/focusPress functions, and the shutter/focus is locked on until the button is long pressed (another quick press keeps the function locked on)

I actually find this behaviour to be very useful, however trying to 'unstick' the buttons is annoying. It would be a lot better if a second quick press simply turned the function off