(02-Oct-2021, 10:21 PM)High View Wrote: I read this somewhere:” …While you should not have any problem with takeoff when Air Mode is enabled, landing can be hard to impossible.”
I disabled Air Mode and reduced Motor Idle Throttle Value [percent] from 5.5 to 5.4.

Both of those seemed to help.

Then I went outside to fly LOS for the first time.  I have a switch which selects between Angle and Acro.  I got the quad in the air in Angle mode hovered then switched to Acro and practiced hovering and a few small moves.  My longest flight might have approached 30 seconds.  I would usually overreact to correct a move and down it would tumble.  I need to learn how to dampen, roll, yaw and pitch until I get better at flying Acro.

The 85 Pro 2 does not have taillights.  So, I ran my batteries to exhaustion-not good.  When I start flying with goggles, I will be able to see the voltage and a warning.  I expect that there is a way to have the Taranis warn with a buzz/vibration when I trigger a preset value.  I doubt that I would hear a buzzer, but I might feel a vibration. 

Any thoughts to get me started?

Have fun!!

The reason it is easier to take off than land period is before taking off, the props are barely spinning pushing little to no air downward. When landing, there is lots of air being pushed down and bouncing back up from the ground.

What Air Mode is about is for being able to control Pitch, Roll, and Yaw, with the throttle all the way down.
Picture being in a dive. With Air Mode on, you can still control the quad (roll, pitch, ect) with the throttle at "0". With Air Mode off, the quad will keep diving with no way to alter any rotation without giving it some throttle.


To smooth out the sticks, I find it much easier flying using some RC Expo in Betaflight. In Betaflight, go to "PID Tuning" and click on the "Rateprofile Settings" tab. As you add RC Expo, it lessens the sensitivity of the sticks near the center position. As you can see in the pic, it moves out from the center a ways before it starts having much affect. You might want to start at about "0.65" to start with as the ones in the pic are for a 75mm whoop I have that has some very peppy motors for its size.




Here is a vid on how to setup an audible voltage reading when battery gets below a certain level. What I suggest is to add another "Special Function" so if you don't hear it, you will feel a vibration when it reads it out. Joshua does not go over that in the video but it is pretty simple to do.
Around 5:20 in the vid, he is setting up the special function to read out the voltage. When you are done with that, add another special function just below the one you just created, and use the same logical switch from above, but instead of choosing "Play Value" keep scrolling and choose "Haptic". If you tab to the next value, set it to "3". That seemed to be the most noticable of the vibration patterns for me.
Remember the voltage setting needs to be set to whatever battery size you are using (1S, 2S, ect).

(03-Oct-2021, 12:01 AM)brettbrandon Wrote: The reason it is easier to take off than land period is before taking off, the props are barely spinning pushing little to no air downward. When landing, there is lots of air being pushed down and bouncing back up from the ground.

What Air Mode is about is for being able to control Pitch, Roll, and Yaw, with the throttle all the way down.
Picture being in a dive. With Air Mode on, you can still control the quad (roll, pitch, ect) with the throttle at "0". With Air Mode off, the quad will keep diving with no way to alter any rotation without giving it some throttle.


To smooth out the sticks, I find it much easier flying using some RC Expo in Betaflight. In Betaflight, go to "PID Tuning" and click on the "Rateprofile Settings" tab. As you add RC Expo, it lessens the sensitivity of the sticks near the center position. As you can see in the pic, it moves out from the center a ways before it starts having much affect. You might want to start at about "0.65" to start with as the ones in the pic are for a 75mm whoop I have that has some very peppy motors for its size.




Here is a vid on how to setup an audible voltage reading when battery gets below a certain level. What I suggest is to add another "Special Function" so if you don't hear it, you will feel a vibration when it reads it out. Joshua does not go over that in the video but it is pretty simple to do.
Around 5:20 in the vid, he is setting up the special function to read out the voltage. When you are done with that, add another special function just below the one you just created, and use the same logical switch from above, but instead of choosing "Play Value" keep scrolling and choose "Haptic". If you tab to the next value, set it to "3". That seemed to be the most noticable of the vibration patterns for me.
Remember the voltage setting needs to be set to whatever battery size you are using (1S, 2S, ect).

Looks like some good info. I'll give it a try tomorrow and let you know the results.

Thanks

(03-Oct-2021, 03:35 AM)High View Wrote: Looks like some good info. I'll give it a try tomorrow and let you know the results.

Thanks

No good results after three hours.

At 4:03 in the Bardwell video, he scrolls down to TELEMETRY. The other choices are there but that line is missing on my Taranis x9d plus.
 
Have I missed something in my Binding?  Somewhere along the way, I saw a popup, where the first choice was: “Set telemetry on”.  I think I chose that line.
 
I have turned on Telemetry in the Config Tab then gone to command line and typed save and enter  After disconnecting from the Configurator and reentering the Telemetry button is off.
 
I assume that any receiver made to work with my Taranis can handle telemetry.

(03-Oct-2021, 04:34 PM)High View Wrote: No good results after three hours.

At 4:03 in the Bardwell video, he scrolls down to TELEMETRY. The other choices are there but that line is missing on my Taranis x9d plus.
 
Have I missed something in my Binding?  Somewhere along the way, I saw a popup, where the first choice was: “Set telemetry on”.  I think I chose that line.
 
I have turned on Telemetry in the Config Tab then gone to command line and typed save and enter  After disconnecting from the Configurator and reentering the Telemetry button is off.
 
I assume that any receiver made to work with my Taranis can handle telemetry.

I have a Taranis QX7 and for my Tinyhawk 2, it shows "Telemetry" available in that drop down list. The Telemetry switch is "not" active in Betaflight/Configuration. If I choose a new model in the Taranis, Telemetry is not in the drop down list.
Try going to your "Telemetry" page in the Taranis. For me, it is page 12 out of 13 pages. It looks like for Telemetry to be visable in the drop down, Telemetry sensors have to be showing on that page. My Tinyhawk 2 shows sensors on that page and the new model does not.

If your quad is not showing sensors on that page, you could try the "Discover new sensors" to see if anything shows up. The quad would have to be powered up to do this.

I just took a look at the Beta85 Pro 2 on getfpv's site. I have 2 of the flight controller boards they show being used in that quad. I am wondering if they are using a different FC than the one pictured as it has a "bind" button, and you say the one you have does not.

getfpv pic


FC I have


When I connect to this board with my Taranis, it does show "telemetry sensors" and telemetry is available from the drop down list.

(03-Oct-2021, 08:49 PM)brettbrandon Wrote: I have a Taranis QX7 and for my Tinyhawk 2, it shows "Telemetry" available in that drop down list. The Telemetry switch is "not" active in Betaflight/Configuration. If I choose a new model in the Taranis, Telemetry is not in the drop down list.
Try going to your "Telemetry" page in the Taranis. For me, it is page 12 out of 13 pages. It looks like for Telemetry to be visable in the drop down, Telemetry sensors have to be showing on that page. My Tinyhawk 2 shows sensors on that page and the new model does not.

If your quad is not showing sensors on that page, you could try the "Discover new sensors" to see if anything shows up. The quad would have to be powered up to do this.

My board does not have a bind button.
 
I put a battery in the quad turned on the TX and selected the model.
Then, following your directions, I went to the Telemetry page and Discover New Sensors produced this:
 

1,2 and 3 were blinking.  

I don't know what an A1 and A2 Sensor means. I do know that a fully charged Lipo has a nominal charge of 8.4 volts. Perhaps I entered that somewhere????

I very much appreciate your help. But, I don't want to become a PIA. So, when you've had enough, type "Nothing More to offer" and I'll not reply asking for more help.

On FrSky receivers, the telemetry Ai and A2 are basically:

A1 = Lipo voltage
A2 = Average individual cell voltage

But at times these need to be calibrated.

I do not have an FrSky receiver to walk through the steps myself but I am sure you can find something on youtube.

(04-Oct-2021, 02:50 PM)High View Wrote: My board does not have a bind button.
 
I put a battery in the quad turned on the TX and selected the model.
Then, following your directions, I went to the Telemetry page and Discover New Sensors produced this:
 

1,2 and 3 were blinking.  

I don't know what an A1 and A2 Sensor means. I do know that a fully charged Lipo has a nominal charge of 8.4 volts. Perhaps I entered that somewhere????

I very much appreciate your help. But, I don't want to become a PIA. So, when you've had enough, type "Nothing More to offer" and I'll not reply asking for more help.

Apparently BETAFPV is using a different flight controller then what is shown on the getfpv site. I went to BETAFPV's site and they currently show this FC for the BETA85 Pro 2. It may be that you still have a different FC as this one still has a "bind" button.




Question: Were RSSI, A1, and A2 showing before you selected Discover Sensors.
The blinking is just showing that the sensors are currently "active". If you view it with the quad powered down, they should not be blinking but should still show in the list.


I am having to guess that the particular FC you have, does not support telemetry (may want to contact BETAFPV to verify that).
Still, all is not lost. Most of the whoops I build are not setup to be monitored in the goggles. What I do on those whoops is to set a timer for just before the battery runs out. I usually do a few hover tests to see how much time before the battery gets to the point where the quad starts descending due to lack of power. I take note of the time and subtract 30 seconds from it. Then I set a timer to notify me when that time is up at which point I land. I have a audible giving me the timer. I just looked and it can be set to "Haptic" as well. Just tried a hover with the timer set to 2 minutes. At 1:30, 1:40, and 1:50, it gave me a single vibration for each. Then it gave me a vibration every second for the last ten seconds of the timer. This isn't the best solution, but should help from running a battery all the way down until you start using the goggles...

This is on the first page of my Taranis QX7 (same page you bind from) to set the timer.
Set Timer 1 for about half a minute before your battery goes.
If you check the "Minute" box, you should get a vibration every minute as well.
Set "Countdown" to "Haptic".

(05-Oct-2021, 01:48 AM)kafie1980 Wrote: On FrSky receivers, the telemetry Ai and A2 are basically:

A1 = Lipo voltage
A2 = Average individual cell voltage

But at times these need to be calibrated.

I do not have an FrSky receiver to walk through the steps myself but I am sure you can find something on youtube.

Thanks for responding.  

I assume A1 and A2 refer to the voltage on the TX???

I don't know if my receiver is capable of Telemetry.  

BetaFPV has not responded to my asking the question.  They don't know what board I have.  I don't know what to tell them about it, except that there is no bind button.  About a week ago I provided images of the quads underside and order and delivery forms from getFPV-Those forms show the SKU.  I haven't heard anything from BetaFPV.

getfpv doesn't seem to know either.

My order form shows: "BetaFPV Beta85 Pro 2 Brushless Whoop 2s Quadcopter (Frsky)"

Image from getfpv sales page:



I have been unable find anything on youtube that seems pertinent.

(05-Oct-2021, 03:21 AM)brettbrandon Wrote: In trying to get an accurate answer to you question, I discovered something that need more checking.  I set up two Models for the 85 pro. On model 85 pro 1, after I chose "Discover Sensors" the number show in column 2 of the Menu selection shows a larger number.

I will be gone most of the day. I'll get back to this as soon as I can.

Thanks

Apparently BETAFPV is using a different flight controller then what is shown on the getfpv site. I went to BETAFPV's site and they currently show this FC for the BETA85 Pro 2. It may be that you still have a different FC as this one still has a "bind" button.




Question: Were RSSI, A1, and A2 showing before you selected Discover Sensors.
The blinking is just showing that the sensors are currently "active". If you view it with the quad powered down, they should not be blinking but should still show in the list.


I am having to guess that the particular FC you have, does not support telemetry (may want to contact BETAFPV to verify that).
Still, all is not lost. Most of the whoops I build are not setup to be monitored in the goggles. What I do on those whoops is to set a timer for just before the battery runs out. I usually do a few hover tests to see how much time before the battery gets to the point where the quad starts descending due to lack of power. I take note of the time and subtract 30 seconds from it. Then I set a timer to notify me when that time is up at which point I land. I have a audible giving me the timer. I just looked and it can be set to "Haptic" as well. Just tried a hover with the timer set to 2 minutes. At 1:30, 1:40, and 1:50, it gave me a single vibration for each. Then it gave me a vibration every second for the last ten seconds of the timer. This isn't the best solution, but should help from running a battery all the way down until you start using the goggles...

This is on the first page of my Taranis QX7 (same page you bind from) to set the timer.
Set Timer 1 for about half a minute before your battery goes.
If you check the "Minute" box, you should get a vibration every minute as well.
Set "Countdown" to "Haptic".

Can you refresh us as to what has happened so far?

It seems you have your radio bound and have the basic telemetry coming in for A1, A2 and RSSI.

That's all the telemetry you need on a micro.

Besides SPI receivers are terrible with advanced telemetry resulting in rx losses at short distances.

So a bit of a refresher as to where you are at?

Here is where we are this morning: I am bound, armed and have been flying. 
 
I have set up the Velocidrone simulator. In their tutorials, they recommend that before you try to learn to fly ACRO you practice LOS.  When doing that without voltage feedback, I flew three batteries to the point where my balance charger, would produce an error.  I lied to the charger and told it they were NiMH until I got the voltage to 7.3.  Then back to Lipo to finish the charge.  That experience started us down the telemetry road.
 
High praise to both of you for pointing the way.
 
I have also flown with the goggles where I see a constant voltage readout.
 
Yesterday I ended with: “I discovered something that needs more checking”
 
Earlier, I had set up two Models for the 85 pro- 85A and 85B. On model 85A, where I had previously chosen "Discover Sensors" the number shown in column 2 of the Menu selection shows a larger number.
 
This morning I checked and the 85A which has a second column number larger than the 85B, shows RSS1, A1 and A2. On this model, I had previously selected FIND SENSORS.  Those lines are absent on 85B-the smaller number.
 
My thought is that the larger number means something has been added to the setup.  To check that, I went to the Telemetry page on both.
 
The lesser number does not show any sensors added and the larger number shows two added sensors.
Next, I turned off the TX, opened it and selected 85A - the larger number - and went to the Logical Switches page. When I scrolled down the list of assignments, SUCCESS-Telemetry is now a choice.
 
I haven’t finished working through the process in Bardwell’s How to make your Taranis readout low voltage but I am very hopeful. 
 
When I have a chance to complete the process, I’ll report back.