On the newest firmware you have uploaded, there is a cross and line in the middle of the screen (Horizon bar), and I can't get rid of it. It is displayed even when not chosen in OSD menu. Can you please check it ?
Also the betaflight OSD tab is not displaying in configurator. (btw - we don't need it , right? )

Hi Guy's!

My name is Javier I'm a frame designer... my website is www.guerrilladrone.com. That being said... I'm about to install my first RaceBase FC into my LittleTad 137. I notice that there's no manual, but also notice they are working on it.

I'm going to need some help getting the FC set up, like wiring... it's a bit confusing when I see two video inputs, I come from Sp Racing and I'm not real familiar with this board.

Can somebody point me to the right direction?

Thanks in advance!!

Javier
Guerrilla Drone
www.GuerrillaDrone.com
[email protected]

Hi Javier, I went through the same situation as you but with some help here in the forum and some trial and error I managed to get it setup and running.

I suggest you to read through this thread as some questions were already answered by marbalon (the board designer) and leave here any other questions you still have and we'll do our best to help you.

(19-Sep-2016, 04:36 PM)blazomusic Wrote: On the newest firmware you have uploaded, there is a cross and line in the middle of the screen (Horizon bar), and I can't get rid of it. It is displayed even when not chosen in OSD menu. Can you please check it ?
Also the betaflight OSD tab is not displaying in configurator. (btw - we don't need it , right? )

Hmm strange because I use this version, but this nigh I worked with BF devs and push my changes to BF sources. So in the package on the server you can find also new prebuild of version 3.0.1. Please try it. There is also option in menu called sidebars, try to disable it also.

OSD tab in GUI should works soon, some people is working on it.

(20-Sep-2016, 06:31 AM)guerrilladrone Wrote: Hi Guy's!

My name is Javier I'm a frame designer... my website is www.guerrilladrone.com. That being said... I'm about to install my first RaceBase FC into my LittleTad 137. I notice that there's no manual, but also notice they are working on it.

I'm going to need some help getting the FC set up, like wiring... it's a bit confusing when I see two video inputs, I come from Sp Racing and I'm not real familiar with this board.

Can somebody point me to the right direction?

Thanks in advance!!

Javier
Guerrilla Drone
www.GuerrillaDrone.com
[email protected]

Look i the first post. There is a pinout description  - with this it should be easy to wiring everything. 

Regards,
Marcin.

(20-Sep-2016, 12:35 PM)marbalon Wrote: Hmm strange because I use this version, but this nigh I worked with BF devs and push my changes to BF sources. So in the package on the server you can find also new prebuild of version 3.0.1. Please try it. There is also option in menu called sidebars, try to disable it also.

OSD tab in GUI should works soon, some people is working on it.

That's great news looking forward to have all the features directly from BF.

Edit: Will the OSD menu still work to change the PIDs and rates in the field without computer?

(20-Sep-2016, 11:48 AM)tozes Wrote: Hi Javier, I went through the same situation as you but with some help here in the forum and some trial and error I managed to get it setup and running.

I suggest you to read through this thread as some questions were already answered by marbalon (the board designer) and leave here any other questions you still have and we'll do our best to help you.

Hello!

Thanks for the reply... yes, I did went through the thread but I notice Marbalon explained to you about vbat and the video in part, the jumper... thats the part that is getting me... where to connect power into the FC? and I dont see any VBAT label on the board either

Thanks again 

Javier

---

(20-Sep-2016, 12:35 PM)marbalon Wrote: Hmm strange because I use this version, but this nigh I worked with BF devs and push my changes to BF sources. So in the package on the server you can find also new prebuild of version 3.0.1. Please try it. There is also option in menu called sidebars, try to disable it also.

OSD tab in GUI should works soon, some people is working on it.



Look i the first post. There is a pinout description  - with this it should be easy to wiring everything. 

Regards,
Marcin.

Hi Marcin!

on the wiring picture shows on the opposite side of the USB port I see pads for "video in", "Battery", "GND", "5V out", so what about the other pads for video and camera?? I notice another set of pads that say "Current Sensor". Those are the two parts that are getting me real confuse... I don't see a "VBAT" label anywhere.

Thanks in advance!!

The port on the right side is labeled POWER PORT so it is only to connect the power, but I need to change labels because it is not so clear.

So please connect your battery+ to Battery pad, GND to GND. And if you want to power your VTX and camera using main battery also make a jumper between pads Video In and Battery. If want to use step-down eg. from PDB you can connect it to Video In. 5V out leave unused. Current sensor pads is dedicated to current sensor if you have PDB with this. With this wiring you will have power on the VTX and Cam port.

About firmware 3.0.1 reuploaded - you have a right but I didn't catch it because I always disable ACC.

Ok i checked 3.0.1, it is ok, no more horizon bar in this firmware.

I had another issue though.. After I save and exit the OSD with connected battery, 2 of 4 motors start spinning quite hard for a second.( good I remove props when doing this) I think it is dengerous. Can you please check if you have the same issue ? I didn't have this issue on 3.0.0. But I had it on 2.9.1 too. I decided not to change anything on OSD. Actually on 2.9.1 after this happened first time, one ESC was burned and second time quad jumped and rolled through air, I have this issue on YouTube posted. I will send you link in private message.

(20-Sep-2016, 03:41 PM)guerrilladrone Wrote: Hello!

Thanks for the reply... yes, I did went through the thread but I notice Marbalon explained to you about vbat and the video in part, the jumper... thats the part that is getting me... where to connect power into the FC? and I dont see any VBAT label on the board either

Thanks again 

Javier

The Battery pin on the schematic is your VBat and AFAIK it's used exclusively for voltage sensor, i.e. it doesn't provide power input to the FC. Then you have Video In (the name is confusing indeed) right next to Battery which is the power input for all the electronics in the FC, including the OSD and the pads where you connect your camera and VTX.
Basically you can connect those 2 pins directly to the battery as long as you don't run higher than 4S (which is the maximum supported by Video In), and that's why there's the mention to put a jumper between Battery and Video In.

On mine looks like this, hope you can see something useful since i took the photo without disassembling:


Basically I just added a blob of solder between the 2 pads to create the jumper.

(20-Sep-2016, 03:23 PM)blazomusic Wrote: I had another issue though.. After I save and exit the OSD with connected battery, 2 of 4 motors start spinning quite hard for a second.( good I remove props when doing this) I think it is dengerous. Can you please check if you have the same issue ? I didn't have this issue on 3.0.0. But I had it on 2.9.1 too. I decided not to change anything on OSD. Actually on 2.9.1 after this happened first time, one ESC was burned and second time quad jumped and rolled through air, I have this issue on YouTube posted. I will send you link in private message.

Please send me information about our ESC output configuration: oneShot/multishot/ synced/unsynced etc. 

It is not probably related with OSD but if there is a bug and we can catch it I can push this info to BF dev team.

I'm using multishot with unsynced PWM at 32k and it is OK, but I know this bug in the past was related with some of this settings.

I fly wih blheli_s multishot 8khz/8khz/Unsynced 8khz. First I burned Aikon SEMF blheli_s 30A when saving OSD, and now I use racerstar 30A v2 blheli_s. And as I said earlier now the (one or two) motors are spinning when saving. On 3.0 it didn't happen which is strange. It happend on 2.9.1 though. Maybe it is a bad unit ?

(21-Sep-2016, 11:44 AM)blazomusic Wrote: I fly wih blheli_s multishot 8khz/8khz/Unsynced 8khz. First I burned Aikon SEMF blheli_s 30A when saving OSD, and now I use racerstar 30A v2 blheli_s. And as I said earlier now the (one or two) motors are spinning when saving. On 3.0 it didn't happen which is strange. It happend on 2.9.1 though. Maybe it is a bad unit ?

No I think it is something with software, will try to reproduce this on my setup. Why you don't use 32k on PWM ? It is decrease jitter. Btw I have only bad experience with blheli_s like many people with YAW twitching.

Motors were spinning when saving on 2.9.0, it was BF firmware bug, see release notes: https://github.com/betaflight/betaflight...tag/v2.9.1
It should be fixed on 2.9.1 though.

(21-Sep-2016, 11:54 AM)Konrad Stepanajtys Wrote: Motors were spinning when saving on 2.9.0, it was BF firmware bug, see release notes: https://github.com/betaflight/betaflight...tag/v2.9.1
It should be fixed on 2.9.1 though.

Code:

Fix spinning motors after save in configurator for Multishot and Oneshot42

Yeah, but was it betaflight configurator, or OSD ? I have problems only when save and exit through OSD.

(21-Sep-2016, 11:49 AM)marbalon Wrote: No I think it is something with software, will try to reproduce this on my setup. Why you don't use 32k on PWM ? It is decrease jitter. Btw I have only bad experience with blheli_s like many people with YAW twitching.

It is strange, I changed to 32kHz unsynced and the motors are not spinning. I tried 5 times. I was using 8kHz because I think my motors sounded best. Marbalon, did you try to reproduce the bug on 8kHz ?

One last two questions, there is option to display nickname in OSD, where I can set it? I was searching through OSD and can't find it.
Also what is "NC" pad in LED PORT?

Thanks for your work Marbalon, I love this controller, and I hope there will be full support for the future versions! If you need a tester, I can always help.

(21-Sep-2016, 05:20 PM)blazomusic Wrote: Yeah, but was it betaflight configurator, or OSD ? I have problems only when save and exit through OSD.

Hmm... i only had it in configurator, didn't have it on OSD save.