Closed robhaswell closed 4 months ago
Please check build: https://github.com/betaflight/betaflight-configurator/pull/3511
Also might be relevant: https://github.com/betaflight/betaflight-configurator/pull/3512 as code 37 is MSP_SET_FEATURE_CONFIG
Thanks. I'm racing tomorrow so don't wanna change anything now. But will test when I get back.
Please check build: #3511
This has the same issue.
Also might be relevant: #3512 as code 37 is
MSP_SET_FEATURE_CONFIG
This also has the same issue.
As it works on Linux this issue will be hard to debug without access to an Apple M2 16" MBP.
I have the same problem I can’t save and reboot in ports and configuration tab in motors and receiver it works. I tested this on 2 different Mac’s and multiple nighty builds but to no luck, both the Mac’s where intel Mac’s but different models. I was able to configure it with my old android phone so now I can use the bt nano 3 module to configure it with my iPhone
I have an intel Mac not an m2
I have an intel Mac not an m2
It seems that the issue is present on Intel macs as well.
I can confirm that this issue is still present in RC2.
could potentially invoke os.release()
to to get os versions to set differing NWjs versions, but such would be a painful mess.
https://nodejs.org/dist/latest-v20.x/docs/api/os.html#osrelease
https://dev.to/thejaredwilcurt/guide-to-nw-js-versions-5d38
edit: found a problem with this idea. it is built on modern "release", so any logic will still choose a modern NWjs. and as such still fails to run on older OSX.
@robhaswell did you try https://github.com/betaflight/betaflight-configurator/pull/3695 ???
im having the same problems i was sure it was just a run of bad boards- thank you for letting me know its my mac- ill use a PC for this one again huge thanks !
@robhaswell can you try https://app.betaflight.com with chromium / chrome browser?
@haslinghuis I'm afraid it still doesn't work on https://app.betaflight.com/
Was kind of expecting that. Issue is an combination of firmware and platform used.
thanks for the update i did had to use windows unfortunately... best of luck !
On Wed, Jun 26, 2024 at 3:17 PM Mark Haslinghuis @.***> wrote:
Was kind of expecting that. Issue is an combination of firmware and platform used.
— Reply to this email directly, view it on GitHub https://github.com/betaflight/betaflight-configurator/issues/3514#issuecomment-2191544024, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZZWSB44WZXECE7CALWC2I3ZJKWL3AVCNFSM6AAAAAA2LHC5V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJRGU2DIMBSGQ . You are receiving this because you commented.Message ID: @.***>
--
Describe the bug
With the following combinations:
master
betaflight and nightly configuratorsI have an issue where changes to the Ports or Configuration tabs do not save. Upon pressing Save, a warning is generated in the console and the connection becomes unresponsive, until the FC is replugged. I have experienced this with two AT32 FCs and this issue has been present for me in nightly configurator builds since I got these a few weeks ago.
What does work:
Here is a screenshot of the error, in this situation I tested making two changes to Modes before triggering the bug:
To Reproduce
Expected behavior
Settings are saved and the FC reboots.
Configurator version
10.10.0-debug-4d42a8f
Flight controller configuration
Add any other context about the problem that you think might be relevant here
Un!t has been helping me with this, and suggested desoldering the FC, which I did - no change.