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
Bind latest Beta85 pro 2
#16
If non of the quads bind then the only thing in common is your radio.
Reply
Login to remove this ad | Register Here
#17
(28-Sep-2021, 12:49 PM)High View Wrote: None of them bind.  I do get to the point that when I enter bind_rx into CLI it says binding.... But, when I then press exit on the blinking Bind button on the TX none of the blinking lights change.  They all have the same dump file if that means they all have the same firmware.

Thanks again

Try using this command in the CLI to bind.

bind_rx_spi

When you are finished binding, you have to type "save" and hit "enter" in the CLI or it will not stay.

Also, if you are using "D8" mode in the transmitter, you need to make sure it is the same in "Betaflight/Configuration'. It should be "D" not "X" in the "Receiver" section.

[Image: sWZOytql.png]
[-] The following 1 user Likes brettbrandon's post:
  • High View
Reply
#18
(28-Sep-2021, 04:12 PM)kafie1980 Wrote: If non of the quads bind then the only thing in common is your radio.

Agreed.  What action should I take?
Reply
#19
(28-Sep-2021, 08:41 PM)brettbrandon Wrote: Below is a summary of what I have tried.

There is no bind button on the quad

I’m running BF Configurator 10.7.0 with BTFL 4.2.0. 
 
Attempt to bind Taranis X9D plus ACCST 2.4 GHz to Beta85 Pro 2 with this file on the quad:
1-BTFL_cli_85pro2_SPI_Frsky FCC.txt
Which begins with:
# dump
 
# version
# Betaflight / STM32F411 (S411) 4.2.8 Feb 15 2021 / 12:09:04 (101738d8e) MSP API: 1.43
# config: manufacturer_id: BEFH, board_name: BETAFPVF411RX, version: b500c5ae, date: 2020-04-26T06:31:02Z
 
# start the command batch
batch start
 
board_name BETAFPVF411RX
manufacturer_id BEFH
 
# name: 85 pro2
 
 
Steps I take:
1.     Plug only usb cable between computer and quad-which connects Betaflight
2.     Calibrate accelerometer
3.     Go to CLI and enter “bind_xr”  Binding … appears, type save and press enter (bind_xr_spi produces an error.  Elsewhere I have read that I should use bind_xr for BF 4.2 which I am running).
4.     Go to Model Setup page on Taranis X9D plus ACCST 2.4 GHz and press Bind to get it blinking.  Wait 5 seconds and press EXIT.
Result:
            The steady bright Green and alternating small Blue lights have not changed, which I take to mean no binding.

This info appears at the top of BF screen:
[Image: y52RREtl.jpg]
I am using the D8 mode in the TX.  In the Receiver tab, I cannot find any place where "D" of "X" is shown. 

I did find the place to set "D" and the diff all shows:



I also noticed this on bottom right of Receiver tab I pressed "Bind Receiver" and "Save"


I pressed Bind Receiver and then noticed this at top of BF:


Thanks for your help.


Try using this command in the CLI to bind.

bind_rx_spi

When you are finished binding, you have to type "save" and hit "enter" in the CLI or it will not stay.

Also, if you are using "D8" mode in the transmitter, you need to make sure it is the same in "Betaflight/Configuration'. It should be "D" not "X" in the "Receiver" section.

[Image: sWZOytql.png]
Reply
#20
I don't know if I am replying to the correct post.  
After many more hours, I may have made some progress.  I changed two things after typing bind_rf into the CLI command line.

First, I moved the TX 4ft. from the quad.
Second, I put the transmitter in bind before typing bind_rf then Save and Enter. 

When I entered in that order, the BF screen changed. For the first time, the quad image in BF was flipping at a fast rate and the sliders moved in the Receiver tab.
The blinking lights did not change.  Is there another way to tell if I’m bound?
The mode is D8 and CLI shows it. 
Does the changing screen, flipping quad and moving  sliders indicate anything useful?

Thanks for any help
Reply
#21
(30-Sep-2021, 03:33 PM)High View Wrote: I don't know if I am replying to the correct post.  
After many more hours, I may have made some progress.  I changed two things after typing bind_rf into the CLI command line.

First, I moved the TX 4ft. from the quad.
Second, I put the transmitter in bind before typing bind_rf then Save and Enter. 

When I entered in that order, the BF screen changed. For the first time, the quad image in BF was flipping at a fast rate and the sliders moved in the Receiver tab.
The blinking lights did not change.  Is there another way to tell if I’m bound?
The mode is D8 and CLI shows it. 
Does the changing screen, flipping quad and moving  sliders indicate anything useful?

Thanks for any help

Here is another attempt at showing the very slight progress I've made after many hours of research.

Tried to include a video but mp4 files are not allowed.
 
The process below got a spinning quad and sliders moving in Betaflight when I move sticks.
  1. Place TX 4ft away from Quad
  2. Have TX with Bind blinking
  3. Plug USB cable from Quad into computer
  4. Calibrate
  5. Select Receiver tab
  6. In Receiver tab, click Bind receiver
  7. In Receiver tab, Click Save
  8. Press Enter on blinking Bind in RX
In addition to the rotating quad, the sliders in the Receiver tab moved when I moved the sticks.
What should I do after step 8???
 
When I disconnect the USB and connect a battery, I still see a steady bright green light and a dim blinking blue light.
 
What state am I in?
Reply
#22
I seem to be the only one replying to the this thread I started.
So, this will be my last entry unless I get notice that the someone else is active.

GetFPV tell me that I am bound because the quad spins and reacts to stick movements in Betaflight.

If that is true, I need to learn how to arm the thing.

Thanks again to the two contributors who took time to help.
[-] The following 1 user Likes High View's post:
  • brettbrandon
Reply
#23
(30-Sep-2021, 11:04 PM)High View Wrote: I seem to be the only one replying to the this thread I started.
So, this will be my last entry unless I get notice that the someone else is active.

GetFPV tell me that I am bound because the quad spins and reacts to stick movements in Betaflight.

If that is true, I need to learn how to arm the thing.

Thanks again to the two contributors who took time to help.

You need to setup your switches for Arming, Flight Modes, Turtle Mode, ect...



[url=https://www.youtube.com/watch?v=RaYJY3YGHT4][/url]
[-] The following 1 user Likes brettbrandon's post:
  • High View
Reply
#24
(30-Sep-2021, 11:37 PM)brettbrandon Wrote: You need to setup your switches for Arming, Flight Modes, Turtle Mode, ect...



[url=https://www.youtube.com/watch?v=RaYJY3YGHT4][/url]

 
Thanks for your response and the link.
I have set up switches to Arm, choose mode, etc.
However, I have to connect to BF and perform the entire BIND procedure each time to see any action in the Receiver and Mode tabs.  While connected, plugging in a battery does not cause any change.  Whereas, my 75Xs show movement when I plug in a battery.
The 75s will arm and fly- not the 85.
Contrary to what getfpv says, I don’t think I am bound.  I certainly cannot arm the 85.
[-] The following 1 user Likes High View's post:
  • brettbrandon
Reply
#25
One thing I still don't understand is that you say "FRSKY_D" or "FRSKY_X" does not show up in the Betaflight "Configuration/Receiver" section. This is how it looks with my quads with a "SPI FrSky" receiver. Make sure that "SPI" shows up in the "Receiver Mode" window.

[Image: UVIoAIpl.png]


If your stick movements are showing in Betaflight, then it has to be at least partially connected.

When you are in the Modes page setting up the switches, do you see the switches move when you move them on the transmitter?
[-] The following 1 user Likes brettbrandon's post:
  • High View
Reply
#26
(01-Oct-2021, 08:43 PM)brettbrandon Wrote: One thing I still don't understand is that you say "FRSKY_D" or "FRSKY_X" does not show up in the Betaflight "Configuration/Receiver" section. This is how it looks with my quads with a "SPI FrSky" receiver. Make sure that "SPI" shows up in the "Receiver Mode" window.

[Image: UVIoAIpl.png]


If your stick movements are showing in Betaflight, then it has to be at least partially connected.

When you are in the Modes page setting up the switches, do you see the switches move when you move them on the transmitter?

I did finally find the right spot and set it to FRSKY_D and the diff_all shows it set.

The switches do move correctly in the Modes tab.

I have four of the quads.  I've been reluctant to strip the plastic off another box.  However, my wife reminds me of one of my sayings namely: 

"At age 84 I have more money than time".  

So, I'm not going to push the "Post Reply" button until I give another one a try.

I ashamed to admit:  The second one did arm.

Now I have to descale the throttle and detune the other sticks. The batteries I'm using are 2s HV 350mAH

My heart felt thanks.

Don't go too far away. "The fat lady didn't sing yet"
[-] The following 1 user Likes High View's post:
  • brettbrandon
Reply
#27
I use this on two whoops that I use indoors as well as outdoors.

Reply
#28
(01-Oct-2021, 09:52 PM)brettbrandon Wrote: I use this on two whoops that I use indoors as well as outdoors.


Thanks for the link.  I followed the instructions to set scale to 50%.  It helped.
I’m having some strange behavior.
I can take off and hover at 6 inches or six feet.  When I bring the quad down as slowly as I can manage it starts to hop up and down wildly when it touches the floor. It continues to hop with the throttle all the way down.  I don’t think the problem is prop wash-no problem hovering at 6 inches.  Bringing it in is the problem.
I know I can hit the disarm switch at about a foot up and let it flop down.
I have other whoops that just twitch a little when I land them.
What should I change?

If I did it right, there is a pdf file attached

I didn't change any of these settings.


Attached Files
.pdf   PID and Receiver tabs-211002 - 1105.pdf (Size: 335.26 KB / Downloads: 86)
Reply
#29
All my whoops do that to some extent. If I fly under a chair or something real close to the ground moving too slow, it will start hopping. As long as I have some forward movement, its ok. I think it is worse with whoops as the ducts force most all the air straight down where it bounces and comes straight back up giving a major "prop wash" like effect. I don't seem to have near the problem while flying in Acro.

You can try lowering the "Motor Idle Throttle Value" located under "ESC/Motor Features" in the "Configuration" section of Betaflight. That adjusts how fast the props spin with no throttle.

I usually land my whoops more like an airplane than a helicopter to reduce that problem as well. Also, you can also see how close you are to the ground little better with some forward tilt of the camera while moving.
Reply
#30
(02-Oct-2021, 05:12 PM)brettbrandon Wrote: All my whoops do that to some extent. If I fly under a chair or something real close to the ground moving too slow, it will start hopping. As long as I have some forward movement, its ok. I think it is worse with whoops as the ducts force most all the air straight down where it bounces and comes straight back up giving a major "prop wash" like effect. I don't seem to have near the problem while flying in Acro.

You can try lowering the "Motor Idle Throttle Value" located under "ESC/Motor Features" in the "Configuration" section of Betaflight. That adjusts how fast the props spin with no throttle.

I usually land my whoops more like an airplane than a helicopter to reduce that problem as well. Also, you can also see how close you are to the ground little better with some forward tilt of the camera while moving.

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 following 1 user Likes High View's post:
  • brettbrandon
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  BetaFPV Meteor65 Pro SeismicCWave 97 1,902 15-May-2024, 07:02 AM
Last Post: SeismicCWave
  Build BetaFPV Meteor65 Pro 1S Build brettbrandon 30 927 14-May-2024, 06:03 PM
Last Post: brettbrandon
  Converted to Meteor65 from Pro SeismicCWave 33 713 13-May-2024, 06:22 AM
Last Post: SeismicCWave
  Betafpv Meteor 75 Pro flying jittery and flyaways...[SOLVED] baevans11 5 297 10-May-2024, 11:41 PM
Last Post: segler999
  Meteor65 pro walksnail build, 24g. ph2t 2 204 07-May-2024, 04:11 AM
Last Post: FPVme


Login to remove this ad | Register Here