Open TomComm27 opened 7 months ago
I have 2 of those SB 405W. Both are working here. Dont think its bug related
What else could I try to find out what the problem is?
Have you tried another computer, or connecting with your phone or pad with the speedybee app?
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.
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
I haven't tried Betaflight yet, I will definitely do that and give feedback! What is exciting is that ArduPilot works!
Well thats great. If you get Betaflight to work maybe a developer here can help you since they are quite alike
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:
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?
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.
And if you then could connect, maybe at the same time load a dump or diff from me
I tried it exactly as you described:
flashed Betaflight firmware with "Full chip erase"
flashed in the INAV Configurator WITHOUT "Full chip erase Unfortunately again without success:
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?
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
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?
I have the exact same problem. Can flash iNav but can't connect to it. Tried different computers.
Had the same problem. First thing connect the FC to the battery and then put the FC into bluetooth mode, Blue light flashing. Make sure bluetooth is on in your phone or tablet, open the Speedybee app and it should connect. On my I phone, using WIFI I had to turn the FC on in WIFI mode White light flashing and then connect my phone to the Speedybee WIFI signal. After that go into the app and open. It did take awhile to connect. Hope this may help. Cheers
Which target did you flash? One common mistake is flashing the "Mini" target. The Mini board is a quadcopter board, not compatible with the Wing or Wing Mini.
Which target did you flash? One common mistake is flashing the "Mini" target. The Mini board is a quadcopter board, not compatible with the Wing or Wing Mini.
Used the SPEEDYBEEF405WING target. Even tried the FW on Speedybee's page. Flashing works fine but can't connect to it afterwards.
In that case, the next three things I would do:
Make sure you don't have any other programs running that will try to use the serial port. That includes the Arduino IDE, a 3D print slicer such as Cura, and ExpressLRS Configurator.
Disconnect or power off anything you have connected to UART1 or UART3.
Run the Zadig driver fixer if you're on Windows.
Steps to Reproduce
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.