Skip to content
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

Speedybee F405 Wing App - does not connect to inav-configurator software #9974

Open
TomComm27 opened this issue Apr 25, 2024 · 13 comments
Open

Comments

@TomComm27
Copy link

Steps to Reproduce

  1. Speedybee F405 Wing zusammengebaut und Batterie + ESC Kabel angelötet.
  2. USB Verbinder mit FC und Laptop über USB-C verbunden
  3. keine Fehler im Windows Geräte Manager aufgetaucht
  4. INAV-Konfigurator 7.1 gestartet
  5. Connect Button klicken -> Fehlermeldung:
    2024-04-25 @ 06:14:57 -- Verbunden mit: COM4
    2024-04-25 @ 06:14:57 -- MSP-Verbindung erfolgreich geöffnet mit ID: 1
    2024-04-25 @ 06:15:07 -- Keine Konfiguration innerhalb von 10 Sekunden erhalten, Kommunikation fehlgeschlagen
    2024-04-25 @ 06:15:07 -- MSP-Verbindung erfolgreich geschlossen
  6. Speedybee getrennt und mit gedrücktem Boot-Button wieder mit dem USB Kabel verbunden.
  7. iNAV-Konfigurator zeigt beim Port "DFU" an
  8. Unter dem Reiter Firmwareflasher werden beide Varianten probiert:
    8.1 manuell heruntergeladene Firmware "inav_7.1.0_SPEEDYBEEF405WING.hex" ausgewählt
    8.2 SPEEDYBEEF405WING ausgewählt und Firmware 7.1
  9. immer mit "Ganzen Chip löschen" aktiviert
  10. "Flash Firmware" Taste gedrückt
  11. Programmieren: ERFOLGREICH
  12. Selber Fehler wiederfinden:
    Connect button klicken -> Fehlermeldung:
    2024-04-25 @ 06:14:57 -- Verbunden mit: COM4
    2024-04-25 @ 06:14:57 -- MSP-Verbindung erfolgreich geöffnet mit ID: 1
    2024-04-25 @ 06:15:07 -- Keine Konfiguration innerhalb von 10 Sekunden erhalten, Kommunikation fehlgeschlagen
    2024-04-25 @ 06:15:07 -- MSP-Verbindung erfolgreich geschlossen

Expected behavior

It should connect to the FC and the properties/options should appear so that I can set the FC.

Proposed solution(s)

If this is a bug, fix it please.

Additional context

Unfortunately I can't get to the CLI tab.

  • FC board name and manufacturer: Speedybee F405 Wing App
  • INAV version string: 7.1 stable
@Thidsa
Copy link

Thidsa commented Apr 27, 2024

I have 2 of those SB 405W. Both are working here. Dont think its bug related

@TomComm27
Copy link
Author

What else could I try to find out what the problem is?

@Thidsa
Copy link

Thidsa commented Apr 27, 2024

Have you tried another computer, or connecting with your phone or pad with the speedybee app?

@TomComm27
Copy link
Author

TomComm27 commented Apr 27, 2024

I have tried it with my iPhone15 and an older Samsung Galaxy with the Speedybee APP. -> The Speedybee is found but an error message always appears when connecting.
I have also tried it with my laptop and desktop computer!

Regarding the app connection, unfortunately I cannot check UART6 to see if this is activated as I cannot establish a connection.

image

@Thidsa
Copy link

Thidsa commented Apr 27, 2024

hm ok. Then something could be wrong with the flightcontroller. Have you tried to flash Betaflight or an older firmware?
Dont suppose I can come up with much more then

@TomComm27
Copy link
Author

I haven't tried Betaflight yet, I will definitely do that and give feedback!
What is exciting is that ArduPilot works!

@Thidsa
Copy link

Thidsa commented Apr 28, 2024

Well thats great. If you get Betaflight to work maybe a developer here can help you since they are quite alike

@TomComm27
Copy link
Author

I have now connected the Speedybee to Betaflight via DFU using a USB cable and installed the firmware file "betaflight_4.5.0_STM32F405.hex". The connection works but no "data" is displayed and I can't set almost anything:
image

image

image

Addition:
In the Betaflight Configuartor there is not exactly the right firmware in the FC firmware selection. I have now downloaded the best fitting one from github: "betaflight_4.5.0_STM32F405.hex"
Maybe this is the reason why I can connect but no data is loaded...

@Thidsa: Do you have INAV up on both your SP F405 Wing?

@Thidsa
Copy link

Thidsa commented Apr 28, 2024

Kind of great that you could connect. I just checked and on the speedybee page they say that there is no betaflight target for the wing board. So i've guess you flashed the target for 405 stack board for multirotors.
Anyway, maybe you could try now and flash inav again 'without' full chip erase, to see if you can retain the port settings you have now. Atleast thats what I would have done. You seem stuck anyway regarding how inav was yesterday.
If you could connect then your board maybe working and some dev here could help you get a custom target to make sure ports are like they should be.
@sensei-hacker what do you think?

Yes have latest inav on both sb 405 wing here.

@Thidsa
Copy link

Thidsa commented Apr 28, 2024

And if you then could connect, maybe at the same time load a dump or diff from me

@TomComm27
Copy link
Author

I tried it exactly as you described:

  1. flashed Betaflight firmware with "Full chip erase"
    image

  2. flashed in the INAV Configurator WITHOUT "Full chip erase
    Unfortunately again without success:
    image

I still don't understand the cloud connection. Do you mean with the internet or what should I be able to connect to?

Does anyone have an idea why the connection with the MissionPlanner to the Speedybee (with an installed ArduPilot firmware) works without any problems?
image

@Thidsa
Copy link

Thidsa commented Apr 28, 2024

Ok. Sorry was a typo. Cloud should be Could.
I hoped the ports (uarts) would stick from betaflight to inav if you didnt full erase. So you could connect with usb or speedybee app. But maybe they dont anyway. I dont know. Hope some devs can help you then. Good luck

@TomComm27
Copy link
Author

I have been in contact with Speedybee Support for several days.
I have already sent them videos and photos of my flight controller.
According to the LED status lights, everything should be fine.
I should pay attention to possible error messages from the barometer or gyroscope. -> Where should these errors appear if I can't establish a connection with INAV?

Does anyone have any ideas on how I can rule out further errors on my part or how I should continue testing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants