-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remote will not work with new Fujifilm updates #46
Comments
Thanks for the report. One of the challenges is once I update my X-T30, I can no longer test the older protocol. |
@93RichardB and @adrianuseless Can either/both of you please elaborate what exactly no longer works? NB. I had to delete |
I open blue tooth pairing on the XT4, get message ‘start pairing with compatible device’, press connect on the M5, it shows ‘6228X-T4-6228, click OK,, goes to thermometer ‘connecting’, then ends and goes back to connect/Scan/Delete… menu. Camera indicates no connection.
Actually, now after doing this a couple of times, selecting connect leads to a menu that just has ‘Back’, no thermometer.
Hope this helps.
From: Guo-Rong ***@***.***>
Sent: Monday, July 24, 2023 8:32 PM
To: gkoh/furble ***@***.***>
Cc: 93RichardB ***@***.***>; Mention ***@***.***>
Subject: Re: [gkoh/furble] Remote will not work with new Fujifilm updates (Issue #46)
@93RichardB <https://github.com/93RichardB> and @adrianuseless <https://github.com/adrianuseless>
I upgraded my X-T30 to v2.01 and confirmed the existing implementation still works.
A quick look at the Bluetooth traffic log with the new Xapp suggests the protocol has not been changed.
Can either/both of you please elaborate what exactly no longer works?
NB. I had to delete furble from the camera pairing then scan and pair again after updating.
—
Reply to this email directly, view it on GitHub <#46 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAPUOS45GCEYDK3LNOXEIEDXR4HWVANCNFSM6AAAAAA2KI4RQA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BAPUOS42VZ5BKWZYLNE2F73XR4HWVA5CNFSM6AAAAAA2KI4RQCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTCI2TNA.gif> Message ID: ***@***.*** ***@***.***> >
|
@93RichardB Thank you for the reply! I would like to confirm the following items:
|
OK. More information:
I turned Bluetooth off on iPhone. Deleted Bluetooth connections on phone and furble. Entered pairing on phone, selected scan on furble. Scan found 4 identical instances of the XT4 (all same serial), chose one and selected connect. It connected! Pressed shutter release button on furble, and furble lost connection and went back to Connect/Scan/Delete menu. No photo taken. Under delete it still shows the XT4 as present, but connecting fails, unless I delete pairing first, then same sequence of events.
Hope that helps.
From: Guo-Rong ***@***.***>
Sent: Monday, August 7, 2023 1:18 AM
To: gkoh/furble ***@***.***>
Cc: 93RichardB ***@***.***>; Mention ***@***.***>
Subject: Re: [gkoh/furble] Remote will not work with new Fujifilm updates (Issue #46)
@93RichardB <https://github.com/93RichardB> Thank you for the reply!
I would like to confirm the following items:
* previous pairing connections were deleted
* on both camera and furble
* a smartphone is not nearby and/or bluetooth is disabled
* with my Android device, the new X app aggressively pairs in the background with no human intervention 😐
* this had me really confused for a while
* the target camera shows up when a new pairing request is started (ie. it appears in the Scan menu)
—
Reply to this email directly, view it on GitHub <#46 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAPUOS2J3CSY5ZUZHCACFQTXUB27FANCNFSM6AAAAAA2KI4RQA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BAPUOSYZLE4ZVQGLRO3MXYTXUB27FA5CNFSM6AAAAAA2KI4RQCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTDL52TI.gif> Message ID: ***@***.*** ***@***.***> >
|
I assume when you say 'phone' you actually mean camera?
Woah, that's weird.
This is progress of sorts, definitely useful. |
Oops. Yes Camera not phone. I did turn Bluetooth off on my iPhone before I started.
Richard
Sent from my iPad
…________________________________
From: Guo-Rong ***@***.***>
Sent: Wednesday, August 9, 2023 3:07:37 AM
To: gkoh/furble ***@***.***>
Cc: 93RichardB ***@***.***>; Mention ***@***.***>
Subject: Re: [gkoh/furble] Remote will not work with new Fujifilm updates (Issue #46)
Deleted Bluetooth connections on phone and furble. Entered pairing on phone, selected scan on furble.
I assume when you say 'phone' you actually mean camera?
Scan found 4 identical instances of the XT4 (all same serial), chose one and selected connect.
Woah, that's weird.
I will see if I can reproduce this, that is unexpected.
It connected! Pressed shutter release button on furble, and furble lost connection and went back to Connect/Scan/Delete menu. No photo taken. Under delete it still shows the XT4 as present, but connecting fails, unless I delete pairing first, then same sequence of events. Hope that helps.
This is progress of sorts, definitely useful.
—
Reply to this email directly, view it on GitHub<#46 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAPUOS5NGM46TNRMB42BLJTXUMZLTANCNFSM6AAAAAA2KI4RQA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@93RichardB This leads to further questions:
If you can access the serial port, I can generate a debug build to see if we can get some more insights. |
How could I access the serial port? Let’s me know how to do it and I will try.
Richard
Richard
Sent from my iPad
…________________________________
From: Guo-Rong ***@***.***>
Sent: Sunday, August 20, 2023 5:30:14 AM
To: gkoh/furble ***@***.***>
Cc: 93RichardB ***@***.***>; Mention ***@***.***>
Subject: Re: [gkoh/furble] Remote will not work with new Fujifilm updates (Issue #46)
Scan found 4 identical instances of the XT4 (all same serial), chose one and selected connect.
Woah, that's weird. I will see if I can reproduce this, that is unexpected.
@93RichardB<https://github.com/93RichardB>
I cannot reproduce this behaviour, it's not supposed to be possible.
The underlying Bluetooth LE library filters out duplicate advertisements during scanning.
Is there a bug here ... or perhaps we are seeing non-duplicate entries ... hmmm.
This leads to further questions:
1. During scanning does the 'Found' message box say 4?
2. Are you able to access the serial port to see the debug output?
If you can access the serial port, I can generate a debug build to see if we can get some more insights.
—
Reply to this email directly, view it on GitHub<#46 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAPUOS3RSRXNAQFMRIJKAU3XWHKKNANCNFSM6AAAAAA2KI4RQA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Sure! Thanks for helping. The serial port of the M5StickC is same USB-C cable connection used to program the device, so we just need to get you an app to connect and read from it during a scan & connect. |
I can use Windows 10 or Linux (mint). Most comfortable with Windows.
From: Guo-Rong ***@***.***>
Sent: Sunday, August 20, 2023 8:45 PM
To: gkoh/furble ***@***.***>
Cc: 93RichardB ***@***.***>; Mention ***@***.***>
Subject: Re: [gkoh/furble] Remote will not work with new Fujifilm updates (Issue #46)
How could I access the serial port? Let’s me know how to do it and I will try. Richard Richard Sent from my iPad
Sure! Thanks for helping.
Firstly, what operating system would you be using?
The serial port of the M5StickC is same USB-C cable connection used to program the device, so we just need to get you an app to connect and read from it during a scan & connect.
—
Reply to this email directly, view it on GitHub <#46 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAPUOS3MDD62N7BXLLQACITXWKVQFANCNFSM6AAAAAA2KI4RQA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BAPUOSYOO2TDOBDEVKDHQADXWKVQFA5CNFSM6AAAAAA2KI4RQCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTEOYFIU.gif> Message ID: ***@***.*** ***@***.***> >
|
@93RichardB Excellent, thank you!
It will either work and you will see readable output. Let me know how you go. |
@93RichardB
Then something like this during a successful connect:
|
Also, note that I have created a new discussion (#47) to try and capture more data points from the community. |
Result of scan:
Name = 6228X-T4-6228
Address = 04:7b:cb:04:12:d3
Token = d2602380
Name = 6228X-T4-6228
Address = 04:7b:cb:04:12:d3
Token = d2602380
Name = 6228X-T4-6228
Address = 04:7b:cb:04:12:d3
Token = d2602380
Result of connect:
Connecting
Connected
Pairing
Token = d2602380
Paired!
Identifying
Identified!
Configuring
Configured
Index entries: 1
Loading index entry: 47BCB0412D3
[0] 47BCB0412D3 : 47BCB0412D3
Overwriting existing entry
Saved 47BCB0412D3
Index entries: 1
Remote Control
Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
Core 1 register dump:
PC : 0x400eaa16 PS : 0x00060630 A0 : 0x800eaafd A1 : 0x3ffc8860
A2 : 0x00000000 A3 : 0x3ffc88c4 A4 : 0x3ffc3d7c A5 : 0x3ffc3d7c
A6 : 0x00004ff0 A7 : 0x00004777 A8 : 0x00000014 A9 : 0x00000004
A10 : 0x3ffc8d68 A11 : 0x80000001 A12 : 0x80095e44 A13 : 0x3ffc8780
A14 : 0x00000003 A15 : 0x00060023 SAR : 0x00000018 EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000008 LBEG : 0x40090504 LEND : 0x4009051a LCOUNT : 0x00000000
Backtrace:0x400eaa13:0x3ffc88600x400eaafa:0x3ffc88a0 0x400f06ce:0x3ffc8900 0x400d952e:0x3ffc8920 0x400d9793:0x3ffc8ab0 0x400d7312:0x3ffc8b30 0x400d7952:0x3ffc8bd0 0x400d7e55:0x3ffc8bf0 0x400d8dc2:0x3ffc8c10 0x400f3f79:0x3ffc8cd0
ELF file SHA256: 0000000000000000
Rebooting...
M5StickCPlus initializing...OK
E (672) ledc: freq_hz=0 duty_resolution=13
[ 677][E][esp32-hal-ledc.c:75] ledcSetup(): ledc setup failed!
[ 679][E][Preferences.cpp:50] begin(): nvs_open failed: NOT_FOUND
[ 705][E][Preferences.cpp:50] begin(): nvs_open failed: NOT_FOUND
[ 706][E][Preferences.cpp:50] begin(): nvs_open failed: NOT_FOUND
Index entries: 1
Loading index entry: 47BCB0412D3
Connecting
That looks like it might be useful information!
Richard
From: Guo-Rong ***@***.***>
Sent: Monday, August 21, 2023 10:23 PM
To: gkoh/furble ***@***.***>
Cc: 93RichardB ***@***.***>; Mention ***@***.***>
Subject: Re: [gkoh/furble] Remote will not work with new Fujifilm updates (Issue #46)
I can use Windows 10 or Linux (mint). Most comfortable with Windows.
@93RichardB <https://github.com/93RichardB> Excellent, thank you!
OK, let's try the simplest option first, using some online browser based tools, through Windows.
I haven't had great success with this, but ... here goes:
* Go here: https://serial.huhn.me/
* Plug in your M5StickC-Plus
* Click 'Connect'
* Find your device and connect
It will either work and you will see readable output.
Or it will issue an error about being unable to connect (if this happens, we probably need to use a specific app).
Let me know how you go.
—
Reply to this email directly, view it on GitHub <#46 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAPUOS63RGARQCFCEIAYQPLXWQJXZANCNFSM6AAAAAA2KI4RQA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BAPUOS3ZNCOIVHDAC2WZ443XWQJXZA5CNFSM6AAAAAA2KI4RQCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTESJTSU.gif> Message ID: ***@***.*** ***@***.***> >
|
@93RichardB Woah, that's excellent, thanks for the output! This is totally unexpected, it's a full system crash and reboot. I think there are 2 problems, separate but probably related:
Give me a bit to review the code. I will probably build a debug image for you to test. |
Happy to help!
More rounds is fine
Richard
From: Guo-Rong ***@***.***>
Sent: Wednesday, August 23, 2023 8:11 PM
To: gkoh/furble ***@***.***>
Cc: 93RichardB ***@***.***>; Mention ***@***.***>
Subject: Re: [gkoh/furble] Remote will not work with new Fujifilm updates (Issue #46)
Result of scan:
@93RichardB <https://github.com/93RichardB> Woah, that's excellent, thanks for the output!
I will likely ask for a few more rounds as we debug this, I hope this is OK.
This is totally unexpected, it's a full system crash and reboot.
I think there are 2 problems, separate but probably related:
1. The scan has multiple identical entries
2. It crashes in the "Remote Control" loop
Give me a bit to review the code. I will probably build a debug image for you to test.
—
Reply to this email directly, view it on GitHub <#46 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAPUOS3TM45RPEAJIBSUQ6LXW2LXRANCNFSM6AAAAAA2KI4RQA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BAPUOS6YVKZW55CX6JGDTZTXW2LXRA5CNFSM6AAAAAA2KI4RQCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTEY6HW4.gif> Message ID: ***@***.*** ***@***.***> >
|
@93RichardB There are no code changes, but I have rebuilt and added the elf image so I can debug the stacktrace dumped on the serial port. |
@93RichardB
With the associated elf image, I should be able to work out where it crashed. |
No further reports have been received, closing this issue as stale. |
Sorry for not getting back to you. Lent my camera to my son for a few weeks and then didn’t pick back up. Will try again this week.
From: Guo-Rong ***@***.***>
Sent: Wednesday, March 13, 2024 6:38 AM
To: gkoh/furble ***@***.***>
Cc: 93RichardB ***@***.***>; Mention ***@***.***>
Subject: Re: [gkoh/furble] Remote will not work with new Fujifilm updates (Issue #46)
No further reports have been received, closing this issue as stale.
—
Reply to this email directly, view it on GitHub <#46 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAPUOS7B4HJU4274QTMJ523YYAT7LAVCNFSM6AAAAAA2KI4RQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJUGA3TEMZSGE> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BAPUOS7Z5FX4RXR7XVIXNB3YYAT7LA5CNFSM6AAAAAA2KI4RQCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTW3MQQC.gif> Message ID: ***@***.*** ***@***.***> >
|
No problem, please use the pre-release v2.0.0-beta and the web installer to ensure your device is properly programmed. |
Sorry for the delay. Eventually I was unable to test the XT-4 again, but I can confirm that the X-H2 works!
From: Guo-Rong ***@***.***>
Sent: March 13, 2024 8:00 PM
To: gkoh/furble ***@***.***>
Cc: 93RichardB ***@***.***>; Mention ***@***.***>
Subject: Re: [gkoh/furble] Remote will not work with new Fujifilm updates (Issue #46)
Sorry for not getting back to you. Lent my camera to my son for a few weeks and then didn’t pick back up. Will try again this week.
No problem, please use the pre-release v2.0.0-beta and the web installer to ensure your device is properly programmed.
—
Reply to this email directly, view it on GitHub <#46 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAPUOSYJXAPA5H7IWFC7PETYYDSBRAVCNFSM6AAAAAA2KI4RQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJWGE2DKNZWHE> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BAPUOSYWV6KGSQBLUD4TW7LYYDSBRA5CNFSM6AAAAAA2KI4RQCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTW7LCGS.gif> Message ID: ***@***.*** ***@***.***> >
|
No problems @93RichardB, thank you for the confirmation and glad it works for you now (albeit on a different/new camera). |
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
The text was updated successfully, but these errors were encountered: