Firmware 3.8 ist verfügbar:
https://www.prusa3d.com/drivers/
So sehen die Files aus:
Moin zu sammen,
die ersten Updates und Fehlerbehebungen für das TBS Fusion. Hier mal per copy and paste:
Extensive Fusion update! After moving office and starting to slowly settle in, here's a quick list of things that we have identified that may help you get your Fusion up and running. First, the good is that the issues are far and between considering how many we shipped. Nevertheless, we strive for perfection and perfection is what we will deliver! We thank all of our customers that are having issues on the patience that they have shown. This here is meant as a first, exhaustive list of all problems and how you can help us address them as quickly as possible.
As with all issues, if you require one-on-one support, please contact our Customer Service either by slipping into DM with Mike Chin here on FB, or opening a support ticket. Any products that need to be replaced will require a support ticket, just to keep some kind of traceability. You can open up these support tickets with your point of sale, or with TBS.
Now, to the meat of the post:
* Rebooting / Black Screens: Remember that you need the power board even without the Crossfire connectivity on all goggles except HDO/HD2-T2. You will need the power board connected on ALL goggles once we do make the Crossfire connectivity available (and you intend to use it). So for HDO/HD2-T2 users there's no hurry, but we do recommend installing the power board at some point in time. Next generation Orqa and Fatshark goggles will work completely without power boards.
* Update problems: There are 2 kinds of update problems. First is bootloader related issues. Agent-X needs to be on the latest version (2.0.21). Uninstall and download if it doesn't auto-update. When on the latest version and still not working, hold down the joystick while plugging in the Fusion, then update. Second issue, reboots or flickers during update. Your USB isn't providing enough power. The easiest fix here is to update while your goggles are running. And remember, after updating you always need to re-calibrate!
* Camera issues: Some FPV cameras are resulting in a black vertical line down the middle, or jumping screen at the edge of reception. This is caused by some form of incompatibility between the Fusion algorithm and the camera. It's fixable, we just need a bit of time. To assist us in finding the problem, please give us a list of your setup (Camera, OSD, VTx) to help us in pinpointing the problems faster.
* Screens not sticking down: No two ways about it, we should have caught this. It's a glue/double-side tape issue. The good news is, once you've got the covers on, it's no longer a problem. If your screen popped off, simply push it back down, and put the cover on. Be careful, don't apply force to the outer edges, as the screens are fragile. We're finding a better tape, and will send these out free of charge to anyone affected if necessary. Aligning the screen is simple. Put it down so you can only see the last line of text on the wifi module, that will center it nicely with the cover.
* Reception: We've seen some people having worse than expected reception and/or lines in feed. First thing to check is for shorts between the GND and signal pads of the modules. Second thing is calibrating the receivers (Settings -> Calibration). If the issue persists, please contact our customer support, or open a support ticket. Even if you are not dissatisfied with your reception, we will hopefully have some good news in the coming days (along with a very economic upgrade route). Stay tuned!
* Joysticks not "clicking" in a certain direction: Our assumption here is that it only happens with the case on. In that case, it would be a tolerance issue between the socket of the goggles and the position of the stick. A bit of "tough love" helps in this case.
* Manual: Jenni and I are working on the manual. it's coming, but Jenni has been on a trip and I've been moving office and home. Excuses, excuses. We're behind, but getting to it.
I will expand on this list as more surface, and rest assured we are doing everything possible that the very few cases of this will disappear as shipping continues. And on that note, more Fusions are shipping out today and we expect to fill all backorders before end of this week.
Genau kann man das hier nachlesen: https://www.facebook.com/group…ermalink/678580349294405/
Die FW bekommste noch net über Github.
Alex hat in der FB Gruppe über ein Google drive frei gegeben...
Die Gruppe findest oben in der Beschreibung
In Facebook wurde eine Testversion der 1.40i veröffentlicht.
RC40i changes:
- Added GPS support (yet telemetry/osd only)
- Runcam pass through added (for SpeedyBee app)
- GPS pass through (for uCenter connection)
- Fixed BB gyro scaling and other compatibility issues
- Add EVO crossfire parameters editor support (latest EVO required)
- Added crossfire router (first fc that supports routing!)
- Added turtle mode safety (works after at least one arming)
- Changed lots in crossfire code
- Changed RX processing code (should be more sensitive and direct)
- Disabled StartAssist
- Added I-term windup killer (no I term until you hit 5% throttle)
- Unify SA fixes
- Added VIRTUAL LQ for non crossfire receivers
- Added Full EVO support for ANY receiver
- KissFC can be used as ANY-RECEIVER->Crossfire relay station
- Added digital RSSI for F-PORT receivers
Small HOWTOs:
GPS:
You can use cheap M8N and newer gpses out of the box, some old once may require some manual
configuration. You will get telemetry to frsky/crossfire and if osd supports it - to OSD.
GPS can be connected to any serial port, just select GPS in advanced serial configuration.
EVO:
This is great VTX and i truly like how it works with kiss / fettec / GPS combo. Evo is fully supported
with ANY receiver. Stick menus and pid changes etc. Well, some testing will not harm,
since TBS just released it to public beta.
You can connect it in 3 ways...
1. To crossfire receiver. In gui - select TBS crossfire EVO
2. To Kiss serial. In gui - select TBS crossfire EVO AND assign VTX to evo serial port.
3. To kiss serial as SA device. In gui - select TBS Smartaudio VTX to evo serial port.
You have to enable crossfire/SA protocol on evo and define stick channels.
Yaw left will bring you to EVO osd menu, once more to crossfire parameters editor.
The firmware is available ONLY in hex for and ONLY here (not in the gui).
I am really curious about your feedback and suggestions. Thank you all for testing and support.
Alex AKA FedorCommander
Findet man in dieser Gruppe:
https://www.facebook.com/groups/907549762675568/
Neue Firmeware 3.21 verfügbar:
on the road mit MaSeFlight
and SchrödiFPV
Ein paar runden mit MaSeFlight
gedreht:
Auch mal alles auf aktuellen Stand gebracht....
Der Humquad am Spielplatz
Erste Testrunde mit der RunCam 5
Ein paar Runden mit FlyFreeFPV:
Update Piloten mal auf den neusten Stand gebraucht....
und Playliste von #bckflp eingefügt.
Vielleicht mal den Umbau probieren:
https://blog.prusaprinters.org…qX2dxeNmJdjZpyo39i9tuV6gk
Der hat ne Höhe von 37cm.. gibt aber auch nen MMU umbau, der sollte höher sein...
Seit ersten August ist die Version 4.0.5 verfügbar:
https://github.com/betaflight/betaflight/releases
Versionshistory von BF 4.0.4
osd_esc_rpm_freq_pos parameter in CLI (#8404);Betaflight 4.0.3