I've come across yet another odd behavior from a Runcam camera.  Since the Runcam Hybrid, my sense has been quality at Runcam has really gone downhill with random issues popping up everywhere.

In this case, my Runcam Split 4 (the single board, whoop size 1080p 60FPS cam) seems to conflict with something preventing my RapidFire to get a signal lock.  The kicker is that if I power off / disconnect the Runcam, I *immediately* get signal lock.

I have tried all of the following with zero success:

* Recalibrated the RapidFire and also made sure it had the latest firmware.

* Testing 2 other quads one of which uses the same Matek Mini VTX used with the problematic Runcam Split 4 and on each one, I get an *immediate* signal lock.

* Tried powering the Runcam Split 4 off direct 3S lipo.

* Tried phsycally separating the Split 4 and the Matek VTX on the bench.

* Tried switching to PAL.


I am beside myself as to why this is happening.  I really need this signal lock since this is supposed to be a micro long range (the Diatone Roma build).  I'll tell ya I am pissed at Runcam.  Their shit just seems to keep f*cking breaking.

That's weird. Does anything showing up on the spectrum analyzer or just not getting a clean video signal when you power on the goggles? Tried disconnect the vtx and see if there's some funky rf being sent out from the runcam stomping on your vtx.

Video is perfectly clean. But I am hesitant to go out much further than the 500m or so without that signal lock.

Already tried physically separating the VTX from the Runcam PCB on the bench - same issue. Also made sure I was using the right VTX trable for the Matek Mini. Short of it is, I am using that Matek Mini VTX on another build where I am having zero issues. This Matek Mini specifically was used on a previous build with a Caddx Tarsier with zero issues.

I really just think Runcam has gone to shit.

Have you tried the legacy mode on the RapidFIRE module (assuming that mode still exists in the latest firmware versions)? That will put you back into old school diversity mode which doesn't require a sync lock. TBH, I would probably trust diversity more than the RapidFIRE modes for doing long range flights with.

Lol, just posted something similar. I just bought my rapidfire module together with the Runcam split 4 and I have the same issue. Just found out now, that if no signal bars on the osd, no signal lock. I have the exact same issue.

Thats a good point Snow. I'd still like to get the RSSI bars working if anything since this likely is a symptom of a bigger issue that could lead to a critical failure midflight.

End of the day, Runcam needs to pull its head out of its ass.

Ok for anyone having this issue, I think it may be a power related issue.  I had tried to power the Split 4 off lipo earlier but still had the problem of the RapidFire not locking.  I am later going to try and power the Split 4 off a 9v BEC rather than straight off a 5v pad on the FC and will report back.

Scratch that.  Just tried powering off 9v BEC still issue.  Also tried powering off of the Matek VTX 5V and G pads still issue.

Here is the oddity ... when I hook the Split 4 up to my camera testing rig which is just a RDQ Mach 3 VTX, I am getting signal lock with the RapidFire.  I cannot figure out what the difference in the setup is.  I have already tried bypassing the FC power distribution altogether by powering direct off lipo as well as with a BEC off lipo.  I am not having any issues with the Matek on my Gecko. And when I tried hooking up the Split 4 to the Gecko build with the Matek, same issue with no signal lock. I just don't freeging get it.

Ok just tried replacing the Matek VTX with a TBS Pro. Same issue.

i have the exact same problem with the TBS Unify32 Nano v1.1, I have two of them. I get a signal lock with both of them on the Caddx Ratel but no signal lock with the runcam split 4

Like you were suggesting to me, Stat, it's an issue with the Split 4. Runcam just needed to get their new product of the week out as quickly as possible and decided quality testing was for chumps, evidently.

I am seriously beginning to suspect a FPV industry-wide memo was sent out something to the effect of, "Watch out for this ronin guy.  He likes bringing the manufacturers to task and calling out their crap quality control.  If he reaches out to you, ask stupid questions and he will eventually get bored and move on." ... cos this is the response I got from ImmersionRC when I showed them the video ...

ImmersionRC Repairs Wrote:Hi,

I am a little confused, in your video how do you have a video image when the camera (split 4) is not powered on?

Regards,
Dave

 

So I'm actually, really hoping that memo is real because if this is the tech guy behind the gadget I use to send $$$$$ of gear out to the great wide, yonder, we are all direly effed.

Shoot I totally forgot to share this video.  Runcam kept bugging me with questions so I made this for them and posted it public.  

Hilarity ...



These morons have there heads stuck so far up their woohoo it's not even funny anymore. Gonna avoid these idiots like covid.

(06-Jan-2021, 09:28 AM)the.ronin Wrote: Hilarity ...



These morons have there heads stuck so far up their woohoo it's not even funny anymore. Gonna avoid these idiots like covid.

I thought the newer Runcam’s had firmware updates? So something like this can’t be fixed by a firmware update? Strange to me unless its really a hardware issue.

They probably won’t offer you a refund I assume.

I have the same issue with split 3 and Eachine EV300O/SKY04X. The problem is "fixed" moving from mix to diversity mode.

Anyway, funny answer you got.