-
Notifications
You must be signed in to change notification settings - Fork 8
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
OSD cell voltage & weird behaviour #84
Comments
Please flash your OSD again with "Full chip erase". |
I flashed the OSD with full chip erase but the black boxes are still there. Do I have to do a downgrade first? I noticed that after flashing the OSD, I have to update the Impulse OSD Logo that appears at startup. If I dont update the logo, its like one big black box instead of the logo at startup. |
Hm, if you flash with full chip erase it does write the default font completely new and all those black boxes should disappear. Did it reset all the settings to default when you flashed with full chip erase? There is a possibility for a defect on you OSD board. Please contact your dealer - it is up to them how to handle this situation. |
Have him do the rescue flash where u solder the pads with a wire and snip
it. Worked for me.
…On Sun, Dec 27, 2020, 1:37 PM awolf78 ***@***.***> wrote:
Hm, if you flash with full chip erase it does write the default font
completely new and all those black boxes should disappear. There is a
possibility for a defect on you OSD board. Please contact your dealer - it
is up to them how to handle this situation.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#84 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKDU7JTMFFJGBEGVD3SCV4TSW55FPANCNFSM4VK3V6KA>
.
|
That only forces the bootloader so you can flash in case the firmware got corrupted somehow or cannot start. |
Thanks guys! Today I will rescue flash just in case and if its not normal after flashing I probably will use this PDB in my freestyle quad. What do you think? It's safe to fly like that? |
After you flash with "Full chip erase" make sure you leave the Lipo connected for a minute or two. It rewrites the font and if you unplug the Lipo during that time these issues can happen. |
Hi Im back. Tried to full chip erase but my device is blacklisted now. I tried 5 times or so before. Still need to try it with lipo plugged in for a few minutes. |
Removed you from the blacklist. |
So I did the rescue flash and full chip erase properly. No improvements but I will use it in my freestyle quad then. Thx for the great support and have a good one guys |
I was testing my 6s Li-ion battery and had a little crash were one of the crossfire antenna went off.
I didt'n notice it at first but after another flight with a normal 6s pack I went indoor and replaced the antenna.
After replacing I went out and flew another 6s Li-ion pack. I noticed that the cell voltage in the osd was completely off.
It showed me a value between 4.20 and 4.40.
I was very confused because only if I plugged in the Li-ion batterys, the value was wrong. If I plugged in a normal and uncharged Lipo the value was correct.
I reflashed the FC, the OSD and the ESC but the problem persists. I reseted the telemetry data in the taranis but in the taranis the values are correct. I charged the Li-ion batterys and the cell voltage was correct again. But everytime I connect a uncharged Li-ion battery it gives me a wrong value in the OSD.
Is it because of the low voltage of the Li-ion, a bug or is anything broken?
Then a flew a pack to test if its safe flying. The cell voltage is ok until I plug an empty Li-ion battery in. But now I had massive OSD flickering till the OSD was completely gone. I set the camera sync to 100 and it fixed the issue.
Now everything is ok except the stats of my CRSF-link and the timer shows no symbols anymore. Its just a black box were the symbol normaly is. Here's a screenshot:
https://ibb.co/89HJ20F
Could you please tell me what is causing the black boxes and the cell voltage thing? Thanks man!
The text was updated successfully, but these errors were encountered: