Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Cannot change video transmitter settings
#1
My flight controller can't change or even just check video transmitter settings. The video itself, OSD, smartaududio, all works correctly, except for changing power and channel of transmitter. Another problem that is likely related to this is when I enter "resource" in betaflight console, it shows that SERIAL_RX 2 is on A03, but "resource show" says that A03 is free.

I already tried to flash many versions of firmware, but the issue persisted. One time I managed to get it working by swapping and rebinding resources, but then the OSD stopped working.
My guess is that I have not quite right firmware target, but I can't find target files for my particular FC. Moreover, I can't even find mentions of my board on the internet at all.
Markings on my FC say that it is CrazyBee Pro V3.3 F4 FS, it is a stock controller on my Mobula 7 1-2S, a model mentions of which also pretty hard to find.

I am sorry if my English isn't very good, not my native language. Thank you in advance for any help!
Reply
Login to remove this ad | Register Here
#2
… if memory serves me, the v3 version of that fc had issues… (speedybee).. don’t quote me..
I would try another fc to rule out vtx issues
Reply
#3
Try the target and version: CRAZYBEEF4FS - Version 4.3.1

The markings suggest it's an SPI FlySky version.

The webpage for it is a jumble, because as everyone knows, HM makes a million versions of every FC and gives them all different version numbers, but doesn't actually create separate pages for them. :/

So I think it's this one. The info in the page confirms the above target as correct. You can try it anyway. If not you need to email Happymodel and hope they have a clue what board it actually is.

https://www.getfpv.com/happymodel-mobula...frsky.html
Try Not, Do or Do Not
- Yoda

Reply
#4
Something seems wrong here. The specs for the CrazyBee Pro V2 fc shows 1-2s (which is what you say you have), where the specs for the V3 fc shows 2-4s (will not handle 1s). 

Are you running FlySky or FrSky?

EDIT: Also, Welcome to the forum...
[-] The following 1 user Likes brettbrandon's post:
  • hugnosed_bat
Reply
#5
(16-Jan-2024, 05:32 PM)Rob Axel Wrote: … if memory serves me, the v3 version of that fc had issues… (speedybee).. don’t quote me..
 I would try another fc to rule out vtx issues

Wrong brand. Speedybee does not make the Crazybee. That's Happymodel.
Reply
#6
(17-Jan-2024, 04:42 AM)brettbrandon Wrote: Something seems wrong here. The specs for the CrazyBee Pro V2 fc shows 1-2s (which is what you say you have), where the specs for the V3 fc shows 2-4s (will not handle 1s). 

Are you running FlySky or FrSky?

EDIT: Also, Welcome to the forum...

If the markings on his board end in FS and not FR, then it's a flysky.  

Quote:Markings on my FC say that it is CrazyBee Pro V3.3 F4 FS

I have had several HM boards with that code (that needed a different Rx), but mostly ones with FR.
Try Not, Do or Do Not
- Yoda

Reply
#7
(17-Jan-2024, 10:55 PM)Pathfinder075 Wrote: If the markings on his board end in FS and not FR, then it's a flysky.  


I have had several HM boards with that code (that needed a different Rx), but mostly ones with FR.

Apparently Happymodel does not have a clue as they are showing a CrazybeeF4FS to be used for FrSky EU-LBT. The following is from the page that you linked above and is also calling it version 2.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Image: X1l4rYLl.png]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I was just trying to clarify which RX was being used.

My main question was that they claim to have a Mobula7 1-2s, and saying it is version 3.3. All the specs I see show that fc, version 2 is 1-2s, and version 3 is 2-4s...
Something is not jiving...


I'm done
Reply
#8
I previously had a broken Moblite7 that had a 1-2S FC with FCC FlySky on it, it had the same code as this one and that was the firmware that worked on Betaflight. I put QS on it in the end for testing, but it seems that fw is a generic multi-version type. You set LBT vs FCC in the CLI or GUI, option is in the Receiver Tab of BF. I always use FCC (even though I live in an LBT country) because it seems using LBT restricts power usage and a whole bunch of other options, so I take the view of fk it and just use what works for me, but also FrSky D8 isn't an LBT supported protocol anyway, you have to use D16 and I prefer D8. Same with ELRS, but another topic. Big Grin

As to the revision, yeah i couldn't find a V3.3 for the Mob7 1-2S, but then it's not the first time i've come across HM FC (and BetaFPV FC too) with weird version numbers and no corresponding support pages. But the fact it is a 2S version of a Mob7 is telling, since as far as I can see they phased those out in 2022 in favour of the 1S with high kv motors. There is a vendor in the UK that still sell the FrSky and probably FlySky Mob's, so possibly they are still available, but I haven't seen the 2S version since I first started out in this hobby.

I do wish the OP would post some pictures and a dump. It would make life a bit easier.
Try Not, Do or Do Not
- Yoda

Reply
#9
(17-Jan-2024, 03:18 AM)Pathfinder075 Wrote: Try the target and version: CRAZYBEEF4FS - Version 4.3.1
That's the target which is automatically detected by BF, I tried many versions, all the same. Also, even with this target, on-board gyroscope is not detected by default and has to be specified in build flags.

(17-Jan-2024, 04:42 AM)brettbrandon Wrote: Are you running FlySky or FrSky?
FlySky.

I will post photos and dump in around half an hour.
Reply
#10
Dump in attachments.
Photos are too big to send here, I've put them on Google Drive:
https://drive.google.com/drive/folders/1...sp=sharing

Additionally, I can say that my drone was a Mobula 7, but now FC, camera with VTX and canopy are the only parts that were there when I bought it, everything else broke with time and got replaced.


Attached Files
.txt   BTFL_cli_20240118_211827_CRAZYBEEF4FS.txt (Size: 25.21 KB / Downloads: 12)
Reply
#11
Send an email to Happymodel and see if they can tell you what target you need. Also don't rely on Auto Detect, it was telling me last week that my BetaFPV board (betafpvsx1280 target) was a MatekF411, which it clearly wasn't. I flashed it manually in Expert mode and moved on.

That FC of yours looks rather old. The Mob7 model looks like the 2020 (or earlier) release. So I had a look around and found a video by a guy called Tarek who some on here will have come across before. It looks like he is using CRAZYBEEF4FS on 4.0.6, but on a later video he uses 4.2.0 so i would start with 4.0.6 and see if you can get it working. Video below.



So my suggestion is to revert to 4.0.6 and see if it works. Trust me you don't need anything in 4.4 on a quad that old. What you need is stability, not cutting edge. When i got my Crazybee v3.1 based Cine8 back in 2021, I immediately tried to upgrade it to 4.3.1 and spent maybe 3 months unable to fly before SnowLeopard told me that it wouldn't work on any version later than 4.2, so upon putting 4.2.11 on and applying the dump file, I was back in the air in about 5 mins. If you have an old quad, put the version that originally came on it, back on. If it flew ok back then, don't try and fix it. Wink

Also found some original dump files from a post on RCG.

https://www.rcgroups.com/forums/showthre...rogress%29
Try Not, Do or Do Not
- Yoda

Reply
#12
I tried to flash 4.0.0 firmware from the post on RCG. When I finally found configurator version that can flash it, i just got almost bricked FC. Not in DFU mode, it wasn't even recognized as USB device, so i put it in DFU and flashed back version that was at least recognized.
Reply
#13
I will just buy a new FC. I am very tired of all this, and not willing to spend another month trying to fix it. Thank you for trying to help.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  1S Battery Settings in OSD segler999 7 806 23-Nov-2023, 01:34 AM
Last Post: segler999
Question Solved Which VTX settings for Moblite7 HDZero? SquirrelFPV 7 297 21-Nov-2023, 07:05 PM
Last Post: hugnosed_bat
  Help Video and Radio signal issues retrobatman 5 266 21-Nov-2023, 12:34 PM
Last Post: SnowLeopardFPV
  mobeetle6 tuning/settings request Palcuz 2 347 14-Oct-2023, 02:17 AM
Last Post: segler999
  Help No Video BadRaven 0 161 12-Jul-2023, 04:04 PM
Last Post: BadRaven


Login to remove this ad | Register Here