So I had my first unforced error crash, womp womp. Here is the sequence of events just to lay it out there.
Flying, perfect, everything working went under a tree, saw a guy in my flight path tried to hit the brakes so as to not to fly towards him ended up rolling the drone on the ground (well that stopped it) the video in my goggles goes wonky of course but then goes black I have a visual on drone so I turtle mode anyway I right the drone and put on my goggles again Still black I go over to drone and unplug lipo and replug Video is back, but no OSD telemetry, just FOXEER bottom left and the timer on bottom right I mowed a lot of wet grass in the crash so I removed 99% of it plugged into Betaflight and updated the OSD screen to try and poke the software into recreating the OSD plug in, still no OSD telemetry.
Go home check solders and pinouts everything looks fine, still no OSD
This doesn't explain why it was working before and not now, but make sure you explicitly set the Video Format in the OSD tab (either PAL or NTSC) to match what your camera is outputting. Don't use the AUTO setting because it's not always reliable. Maybe you just got lucky before.
19-Jun-2020, 07:49 PM (This post was last modified: 19-Jun-2020, 07:50 PM by Opatry.)
So I went back and watched my DVR from the crash and well, I've uploaded it to youtube watch it below.
It looks like when I crashed and disarmed, it was fine and gave me my post flight readout but when I rearmed and turtle mode'd it, it killed the VTX. Could I have messed something up when turtling? Ive never actually done it before so this is new to me but I don't see why it should mess with the picture.
@Snowleopard I'm using the Foxeer Mini Arrow Pro and it says it can output in NTSC OR PAL so I dont know which one it is currently in and I do have my setting in BF set to AUTO.
@ Voodoo I do get picture and I get camera OSD but not BF OSD which is really what I care about... I would have to cut the wires out of their pin holder white headed connector thing and solder the cables together to try this I think. Im not too confident I wouldn't mess that up.
Also It should be noted that when I boot up drone with LiPo the only reading I get at the top is top left "NTSC" and top right "DEF"
Anyone know what "DEF" means?
I've tried uploading a new font to try and jog it, nothing...
Is it possible that I fried my FC's OSD chip? because the FC looks totally in tact, but the grass I cut up that got jammed in there was pretty wet, im wondering if it shorted out something on the board
(19-Jun-2020, 08:46 PM)voodoo614 Wrote: The OSD could have gone bad. I have a FC where the OSD would display but not picture but occasionally, it gets picture but no OSD. But never both.
I would closely check for anything odd with the OSD chip. Like dirt or corrosion. Maybe even lift leg.
Any idea how I can locate which is the OSD chip? I don't know anything about the physicality of the board besides the pads.
Here are some pics of it from just now. I think I know which is the OSD chip now, with your link. But it looks totally in tact. Could it be fried without any exterior showing damage?
I plugged in my lipo and let it sit for maybe 30 seconds and the OSD chip seemed very hot to the touch, is that normal? I'd take it if the OSD chip is in fact busted i'd need a whole new FC?
It's no secret on here that I have a very low opinion of iFlight electronics in general. We see far to many QC issues and other configuration problems with them.
The OSD chip shouldn't get hot so it sounds like it's developed a fault. Unless you are handy with hot air soldering and have a hot air rework station then it will be a new FC.
(19-Jun-2020, 10:16 PM)SnowLeopardFPV Wrote: This is your problem --> iFlight mini f4 SucceX-E
It's no secret on here that I have a very low opinion of iFlight electronics in general. We see far to many QC issues and other configuration problems with them.
The OSD chip shouldn't get hot so it sounds like it's developed a fault. Unless you are handy with hot air soldering and have a hot air rework station then it will be a new FC.
UGH... I've only been flying for about a week! one crash and the OSD fries? that seems ridiculous. And because I bought this in a stack that means i'll have to buy a new 4 in 1 ESC too...
Any recommendations for a good budget stack? Hell I wouldn't be upset if the stack has a VTX in it too cause my vtx doesn't have smart audio. I wonder if amazon will process a return on this shitty FC :O
If the 4in1 ESC is fine you won't need a new ESC. You can make any flight controller work with any 4in1 ESC. It might just take a bit of rewiring or splicing of the harness between the ESC and FC, but that is all.
(19-Jun-2020, 11:22 PM)SnowLeopardFPV Wrote: If the 4in1 ESC is fine you won't need a new ESC. You can make any flight controller work with any 4in1 ESC. It might just take a bit of rewiring or splicing of the harness between the ESC and FC, but that is all.
What is your budget?
My budget is to stay in the realm of the current stack. ~$50
Unfortunately I will be returning my stack to amazon so i'll have to send back the ESC too, but im not upset about this as I didn't really like that it was BL Heli_S anyway. I think BL Heli_32 is a little better because you can actually customize your startup beeps I know you can with BL HELI S but as far as I can tell you can only do star wars, game of thrones, and one or two others.
What do you think about the Mamba F405?
Do I need an F7 for any reason? or does an F4 do just as well?
Also i'm hoping to find a 30x30 stack so I dont have to use this stack adaptor I have in my frame as my frame only has holes for 30x30 and my current stack is a 20x20
If you only have a budget of ~$50 then your only other real option is the Mamba F405 that you already mentioned. It's still what I would class a budget stack but it's a better stack than the iFlight stacks. We don't see too many issues with the Mamba stacks, however there has been a recent spate of problems with the SBUS pad for whatever reason which has required an uninversion hack to be implemented on the receiver and a different UART to be used. We have no idea why. Maybe it's a design fault in the newer hardware revisions of that board. If you are going to run a R-XSR receiver (the one with telemetry) you are best using FPORT firmware on that anyway in which case the SBUS pad issue is irrelevant because you won't be using the SBUS pad on the FC.
(19-Jun-2020, 10:16 PM)SnowLeopardFPV Wrote: This is your problem --> iFlight mini f4 SucceX-E
Straight forward and to the point.
@OP. F4 is actually fine. It will save you some money. But you will have to deal with inversion and possibly hacking receiver. F7 is the better way to go.
![[-]](https://intofpv.com/images/collapse.png)
iFlight stacks. We don't see too many issues with the Mamba stacks, however there has been a recent spate of problems with the SBUS pad for whatever reason which has required an uninversion hack to be implemented on the receiver and a different UART to be used. We have no idea why. Maybe it's a design fault in the newer hardware revisions of that board. If you are going to run a R-XSR receiver (the one with telemetry) you are best using FPORT firmware on that anyway in which case the SBUS pad issue is irrelevant because you won't be using the SBUS pad on the FC. 