Runcam Split control Flaky

[Redshifft]

Very intermittent UART control on 1.8.1 with Runcam Split V1 on latest fw v2.0 (or any other fw) When it works the control acts like a toggle, I'm am unsure if this is even the correct. Regardless at next boot it often does not even work at all.

[azolyoung]

Thanks for your help!

Yeah, I have forward your idea to my colleague. we have receive some user feedback, they also met this problem, runcam split will interfere the GPS device. And we make a EMC box or Aluminum box, put runcam split into the box(The runcam split has been insulated), then runcam split and gps can work fine together.

[putimir]

Tried today, but no luck (MATEKF405SE + RCSplit V1, V2.0.0,16th,Jan 2018)...

Is the fix universal or it is hw/fw specific?

I received info from Runcam, that the solution is in Runcam firmware not iNav...?

[azolyoung]

@putimir

I want to confirm:, your tx\rx of rcsplit has been connected with the spare uart of the flight controller?Will your rcsplit blue light continue to flash after power-on? When the blue light continues to flash, does your rcsplit have inserted a sdcard, and this sdcard has free space?

[putimir]

your tx\rx of rcsplit has been connected with the spare uart of the flight controller? - yes absolutely

I have set my split to auto record, so after power on, + 2 sec (cca), it starts to record, so the blue led blinks in cca 1 sec intervals...

If I then try to operate the remote (via TX switch / iNav modes), nothing happens. I also tried to reboot FC after power on, but no luck either....

[Redshifft]

Hey @Redshifft, I got the board today, can you provide more detail on the procedure:

I suppose I need to power the board with 5v, right?
I cut & connect the white signal wire on one side (the one with usb plug) to the RX pin of the split - what do I use on the other / FC side? (using Matek F405-WING, iNav ofcourse) How do I map PWM on iNav?
Is there any documentation on which PWM values translate to which Split commends?

Thanks a lot!

Sorry mate, I did not see your question, Inav has a new mixer now, sure someone can help you get just a high, medium and low pwm out of servo output. map to a 3 way switch and play with it, a fast toggle switches modes and on end starts and stops record or picture. Take a look at painless360 on YT think he had a vid on Runcam control :)

[stale[bot]]

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.

[Nihilistic]

I'm having the same problem with my Runcam Split 2S wired to a Matek F405-CTR. I know the wiring and switches are set up correctly, because if I reboot the FC either via the iNAV configurator or OSD stick menu, all three of the transmitter switches will operate the Split 2S as they're supposed to. But, none of them work after the initial power up without a reboot of the FC with the Split 2S already powered up. I'm running iNAV 2.0.1

[Haukanes]

I added a small delay before the init() function in main, which fixed the issue for me.

[teckel12]

@Haukanes Do you have the changes you can share so we can merge into 2.1? You can just attach or post them here and I can do the pull request if you want.

[Haukanes]

You can see it in my inav fork. It was not meant for a final version, just to check if slowing bootup would help.

[datamann]

https://github.com/Haukanes/inav/commit/321248028f8c18d49ab8d8ee2d18fcda55fa8cc4#diff-c27ac60319310f0e3b936bca81499818

[azolyoung]

Sorry to reply so late. Last week until now, it took some time to debug the issue that runcam split can't be controlled via iNav. This time, I finally reproduce the uncontrollable phenomenon. Because the Split data cannot be received correctly during the initialization process, the initialization fails. At present, I can't find the specific reason. Since I have spent a lot of time looking for the cause, but still can't locate the problem. So for the time being I made a compromise, using two cli commands to make the camera's features recognizable correctly. The main changes to the test firmware linked below are: 1.Change the Split communication protocol to asynchronous, avoid blocking camera initialization, causing motor restart or other strange problems. 2.Added rcdevice_protocol_version and rcdevice_feature to manually identify the camera's characteristics and protocol version number.

If you still can't enable camera control using the following firmware, please paste the following three commands into the cli interface and try again: set rcdevice_protocol_version = 1 set rcdevice_feature = 7 save

https://s3.amazonaws.com/rctmpfiles/inav_test_fws/inav_2_1_fix_rcsplit_telemetry_control/inav_2.1.0_MATEKF405.hex https://s3.amazonaws.com/rctmpfiles/inav_test_fws/inav_2_1_fix_rcsplit_telemetry_control/inav_2.1.0_MATEKF405SE.hex https://s3.amazonaws.com/rctmpfiles/inav_test_fws/inav_2_1_fix_rcsplit_telemetry_control/inav_2.1.0_MATEKF722.hex https://s3.amazonaws.com/rctmpfiles/inav_test_fws/inav_2_1_fix_rcsplit_telemetry_control/inav_2.1.0_OMNIBUSF4PRO.hex https://s3.amazonaws.com/rctmpfiles/inav_test_fws/inav_2_1_fix_rcsplit_telemetry_control/inav_2.1.0_OMNIBUSF4V3.hex

[Bobi456789]

Hi , I would be extremely grateful if you could help me. I have the same problem with runcam split 2s firmware V 3.1.0 but with kakute f4 v2 , inav 2.0.1 thank you so much

[azolyoung]

@Bobi456789

Yeah, thanks for you help! following firmware is for KAKUTEF4 and F7.

https://s3.amazonaws.com/rctmpfiles/inav_test_fws/inav_2.1.0_KAKUTEF7.hex https://s3.amazonaws.com/rctmpfiles/inav_test_fws/inav_2.1.0_KAKUTEF4.hex

[Bobi456789]

Hello, I tried your firmware but did not work for me. My card is kakute f4 V2. Maybe you gave me the firmware for Kakute f4. thank you.

[azolyoung]

@Bobi456789

Sorry, although you have repeatedly stressed v2:(. I still generated a v1 for you. . Here is the correct V2 firmware: https://s3.amazonaws.com/rctmpfiles/inav_test_fws/inav_2_1_fix_rcsplit_telemetry_control/inav_2.1.0_KAKUTEF4V2.hex

[teckel12]

What is everyone's experience when using the Split and GPS? Lots of reports of the Split causing GPS issues.

[azolyoung]

I tried making a box with Aluminum EMF Foil, wrapping the splits and exposing only the 3 PIN nests. In this case, when the GPS and the Split are firmly connected together (one above, one below), the GPS can search for stars normally. On our company's balcony, we can also search for 6-8 stars. The box made last time has lost. I will do another for testing.

When the Split is powered on, it will interfere the gps search. We find that as long as the Split and the GPS module are not particularly close, the GPS will work normaly. The split can cause high frequency interference to the GPS, so it is impossible to search for stars. Adding a shielded box to the split will improve the situation.

[teckel12]

@azolyoung So unfortunate. I'd love to try split, but the GPS interference is a deal-breaker for me

[putimir]

I get the best results (which are very good actually), if I don't power the split until I get sat fix, which is usually within 30 secs or so from cold start, and then power on the split ..try it

[Bobi456789]

Hello, I tested the firmware, split 2s works but I had a problem with the configuration system. So I'm going back to 2.0.0. Thanks anyway for your help

[Nihilistic]

@teckel12

I have a BN-880 mounted on the middle of the top plate of a Kensun KK210 frame, a little bit rearward of the stack. Individual ESC's on the arms, F405-CTR mounted on rubber bobbins, the Split 2S above it on spacers and the included gummies. And my GPS gets a lock with low HDOP in the normal amount of time, and just gets better throughout the flight. My Crossfire Nano RX will cause more interference if it's too close, so it's mounted forward, and the VTX is at the rear. POS & ALT HOLD works great, and RTH works great.

What I like to do is wire the GPS, RX, and VTX, with longer wires than necessary at first, so you can play around with placement while everything is powered up. You could try putting your VTX on the bottom plate behind the stack, and your BN-880 above it on the top of the top plate. That's enough clearance to avoid mag or GPS interference from the VTX, and then your GPS isn't sitting directly above the Split 2S.

Maybe other GPS modules are more sensitive. I have a mini M8N I got from banggood that's in a puck, and it costs twice as much as the BN-880, weighs twice as much, and locks in half the satellites, and takes twice as long to do it. It's sitting unused in my parts bin. BN-880 for the win!

[Nihilistic]

@azolyoung Is this fix going to get rolled into a future release? I hate to keep bugging you to add the fix to all these targets every time they release a new RC.

[teckel12]

@Nihilistic Even though the BN-880 is a clone, it's a damn good GPS module, and only $18. The only GPS I fly with.

I've heard such bad stories about the Split and GPS signal strength that it's really got me worried about wasting the $$ on the Split or losing the entire quad due to GPS interference.

So you find that the Split stack is where the interference is, it's not with the camera or cable between the camera and the stack?

I wonder if there's much difference in interference between thr Split and the Caddx Turtle.

[Nihilistic]

@teckel12 I have my BN-880 almost directly above the stack, sticky taped to the top side of the top plate. It's maybe a centimeter rearward of being directly above the stack, to make room forward for where I used to mount my Mobius Mini. It has enough clearance from the VTX and Crossfire Nano RX and other stuff that I get plenty of satellites, and haven't noticed any issues with the magnetometer. There might be an even more optimal arrangement, but this one works well enough I feel I can trust RTH to work manually or upon fail safe.

I've never actually tried mounting the GPS on a staff to see if there would be a noticeable improvement (quicker 3D fix and/or more satellites). I typically get as many as 17 satellites with HDOP below 2, and I don't even have Galileo enabled, so I don't feel the need to bother. If I needed waypoints or wanted rock solid POS/ALT hold to turn my quad into a flying selfie stick, than I might find further tweaking beneficial.

Good question. I'd like to see one of the youtube reviewers that has the Split 2S, Caddx Turtle V2, and the new Fox Mix, do some interference testing with a spectrum analyzer or something. I've seen Bruce at RCmodelreviews test various key chain style cameras (like the Mobius) for interference before.

[stale[bot]]

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.

[stale[bot]]

Automatically closing as inactive.