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
Quanum Pico / Micro SciSky headaches (possibly binding issue?)
#1
I just picked up a Quanum Pico flight controller (which is the same thing as a Micro SciSky FC) and an OrangeRx (version 2.1) module for my Turnigy 9xr receiver.  Got it all set up using these instructions.  Initially I had problems binding until I saw advice to "literally touch the antenna from the RX and TX together during binding" and that appeared to work.  
The reason I think it worked is that if the TX is turned on, the LED on the Pico doesn't flash red but is solid.  Also in Cleanflight if the TX is turned on the numbers on the Receiver tab are all 998 instead of 1500 (if the TX is off).

Onto my problem.
When I plug in a battery, the motors just go straight to full power and the quadcopter isn't responsive to any commands from the TX.
I am unable to plug in USB and battery at the same time because that supposedly fries this board.

I have a fully built 210 quadcopter with Naze32 that works fine.  I use that with an FrSky module and a D4r receiver.  

I added a new Model to the TX and set it to use DSM2.

I did read somewhere someone with this exact issue set their "pwm_motor_rate=16000" and it fixed it for them but not for me.

Can anyone help?
Reply
Login to remove this ad | Register Here
#2
PWM motor rate should be 32000 i think, also make sure battery polarity is correct
Don't be a LOS'er, be an FPV'er :)  My Gear - Facebook - Instagram - Twitter
Reply
#3
Even though you can't plug in the battery and USB at the same time, once your transmitter is bound to the onboard Rx, you can check the receiver tab in cleanflight by doing the following.

Make sure you are bound, then unplug the USB.  Turn on the transmitter, then plug the USB back in and connect cleanflight.  You should now be able to tell if your sticks are working correctly.  This works for me with a Spektrum.

You can't run the motors from USB power, but this might help you determine if your channels are correct, and if any are reversed.
Reply
#4
Oscar, I've tried the motor rate 32000 as well, same issue.

Sloscotty, this is what happens with receiver tab:

TX off = all inputs at 1500.  
TX on = all inputs at 998, but no response to any input.  

I'm not 100% sure if the OrangeRX is binding correctly though.  When I turn it on holding the bind button, the led on the OrangeRx module blinks fast for about 2 seconds, then stops blinking at all.  However, like I said, the board definitely acts differently if the TX is on vs off so I THINK it's bound.
Reply
#5
Did you setup your RX in cleanflight? Enable RX_Serial and choose Spektrum receiver in configurator?
Don't be a LOS'er, be an FPV'er :)  My Gear - Facebook - Instagram - Twitter
Reply
#6
(05-Jul-2016, 07:06 PM)jamesw Wrote: I'm not 100% sure if the OrangeRX is binding correctly though.  When I turn it on holding the bind button, the led on the OrangeRx module blinks fast for about 2 seconds, then stops blinking at all.  However, like I said, the board definitely acts differently if the TX is on vs off so I THINK it's bound.

When bound (and detecting your transmitter), the red led at the front of the FC should light solid.

To enter binding mode, turn off your transmitter, and plug in the FC (via USB is OK).  The red light will blink slowly at first.  After 5-10 seconds, it will start to blink rapidly - this indicates the on-board Rx is in bind mode. Then do what you need with your Tx to bind.
Reply
#7
(06-Jul-2016, 02:22 AM)sloscotty Wrote: When bound (and detecting your transmitter), the red led at the front of the FC should light solid.

To enter binding mode, turn off your transmitter, and plug in the FC (via USB is OK).  The red light will blink slowly at first.  After 5-10 seconds, it will start to blink rapidly - this indicates the on-board Rx is in bind mode. Then do what you need with your Tx to bind.


Ok, then my TX is definitely bound.

Just in case it's helpful here is a dump from the Betaflight configurator.  I flashed it most recently to AlienFlight because I had seen someone with my same issue saying that worked for them.  However I've also flashed it as a Naze32 and had the same problems.  Also you can see that I have "motor_pwm_rate=16000", again because someone with my same issue said that worked for them, but I've tried 32000 with the same problem.

Do you notice anything in these instructions that looks incorrect?  Because that's what I've followed each time I've flashed it (and followed the very first time I set it up without flashing it to a different firmware).
Reply
#8
(06-Jul-2016, 02:27 PM)jamesw Wrote: Ok, then my TX is definitely bound.

Just in case it's helpful here is a dump from the Betaflight configurator.  I flashed it most recently to AlienFlight because I had seen someone with my same issue saying that worked for them.  However I've also flashed it as a Naze32 and had the same problems.  Also you can see that I have "motor_pwm_rate=16000", again because someone with my same issue said that worked for them, but I've tried 32000 with the same problem.

Do you notice anything in these instructions that looks incorrect?  Because that's what I've followed each time I've flashed it (and followed the very first time I set it up without flashing it to a different firmware).

I am running Cleanflight/NAZE 1.12.0 on mine (this is what it came with).  I think I didn't change much.  I compared my dump with yours and noticed a couple of things (may or may not be applicable).

Looks like you have Oneshot125 turned on - I do not.
My pwm rate is 32000.
I also have a looptime variable that is not in your dump.  Mine is "set looptime = 3500"

Most of the other stuff where we have common variables looks OK (upon quick glance).  The ones above stood out to me.
Reply
#9
(06-Jul-2016, 02:58 PM)sloscotty Wrote: I am running Cleanflight/NAZE 1.12.0 on mine (this is what it came with).  I think I didn't change much.  I compared my dump with yours and noticed a couple of things (may or may not be applicable).

Looks like you have Oneshot125 turned on - I do not.
My pwm rate is 32000.
I also have a looptime variable that is not in your dump.  Mine is "set looptime = 3500"

Most of the other stuff where we have common variables looks OK (upon quick glance).  The ones above stood out to me.


Ok sloscotty, I reflashed it to your exact setup there and now when I plug in the battery the motors don't go crazy!.......but I can't get it to respond to anything.

The red LED goes solid (so it's bound).  The blue LED (next to VIN) goes solid.  The green LED (next to GND) blinks slowly and never stops.

I've tried setting up switches to arm but nothing seems to work.  
Here is the most recent dump.

This might be a TX issue I guess.  I'm using a Turnigy 9XR with an OrangeRx 2.1 module.  I set the Model up on the TX to "PROTO DSM2" and "DSMTYPE: DSM2only"
Other than that the settings are the same as they would be with my FrSky module in the TX.

I feel like this is progress, but still not good enough.  :-\
Reply
#10
(06-Jul-2016, 06:25 PM)jamesw Wrote: The red LED goes solid (so it's bound).  The blue LED (next to VIN) goes solid.  The green LED (next to GND) blinks slowly and never stops.

Sounds like it is not arming.  The green led should go solid when armed.  (I am not sure, but I think the blinking green means it is trying to set the gyro/acc.  You did initial calibration in cleanflight, right?)  When I'm ready to fly, I set the quad down, and the green light blinks for a few moments, then goes out.  When I arm, it goes solid.

I suspect you are not arming.  I don't use a switch, I use the stick.  Your throttle (and or yaw) endpoints may not be set correctly (low enough for throttle) in your Tx to arm by stick (I don't know what is required to arm by switch).

Here is my dump to compare (Just realize you'll have to set your endpoints appropriately.  Im using a DX8 so my Tx settings may not be relevant to yours, but I'm using 125% on both ends of throttle travel.):

Code:
# dump

# version
# Cleanflight/NAZE 1.12.0 Jan 11 2016 / 16:02:07 (7a4bc02)
# dump master

# mixer
mixer QUADX
mmix reset
smix reset


# feature
feature -RX_PPM
feature -VBAT
feature -INFLIGHT_ACC_CAL
feature -RX_SERIAL
feature -MOTOR_STOP
feature -SERVO_TILT
feature -SOFTSERIAL
feature -GPS
feature -FAILSAFE
feature -SONAR
feature -TELEMETRY
feature -CURRENT_METER
feature -3D
feature -RX_PARALLEL_PWM
feature -RX_MSP
feature -RSSI_ADC
feature -LED_STRIP
feature -DISPLAY
feature -ONESHOT125
feature -BLACKBOX
feature -CHANNEL_FORWARDING
feature VBAT
feature RX_SERIAL
feature MOTOR_STOP
feature FAILSAFE


# map
map TAER1234


# serial
serial 0 1 115200 57600 0 115200
serial 1 64 115200 57600 0 115200


# led
led 0 15,15:ES:IA:0
led 1 15,8:E:WF:0
led 2 15,7:E:WF:0
led 3 15,0:NE:IA:0
led 4 8,0:N:F:0
led 5 7,0:N:F:0
led 6 0,0:NW:IA:0
led 7 0,7:W:WF:0
led 8 0,8:W:WF:0
led 9 0,15:SW:IA:0
led 10 7,15:S:WF:0
led 11 8,15:S:WF:0
led 12 7,7:U:WF:0
led 13 8,7:U:WF:0
led 14 7,8:D:WF:0
led 15 8,8:D:WF:0
led 16 8,9::R:3
led 17 9,10::R:3
led 18 10,11::R:3
led 19 10,12::R:3
led 20 9,13::R:3
led 21 8,14::R:3
led 22 7,14::R:3
led 23 6,13::R:3
led 24 5,12::R:3
led 25 5,11::R:3
led 26 6,10::R:3
led 27 7,9::R:3
led 28 0,0:::0
led 29 0,0:::0
led 30 0,0:::0
led 31 0,0:::0


# color
color 0 0,0,0
color 1 0,255,255
color 2 0,0,255
color 3 30,0,255
color 4 60,0,255
color 5 90,0,255
color 6 120,0,255
color 7 150,0,255
color 8 180,0,255
color 9 210,0,255
color 10 240,0,255
color 11 270,0,255
color 12 300,0,255
color 13 330,0,255
color 14 0,0,0
color 15 0,0,0

set looptime = 3500
set emf_avoidance = OFF
set i2c_overclock = OFF
set gyro_sync = OFF
set gyro_sync_denom = 1
set mid_rc = 1500
set min_check = 1100
set max_check = 1900
set rssi_channel = 0
set rssi_scale = 30
set rssi_ppm_invert = OFF
set rc_smoothing = ON
set input_filtering_mode = OFF
set min_throttle = 1100
set max_throttle = 2000
set min_command = 1000
set servo_center_pulse = 1500
set 3d_deadband_low = 0
set 3d_deadband_high = 0
set 3d_neutral = 0
set 3d_deadband_throttle = 0
set motor_pwm_rate = 32000
set servo_pwm_rate = 50
set retarded_arm = OFF
set disarm_kill_switch = ON
set auto_disarm_delay = 5
set small_angle = 25
set fixedwing_althold_dir = 1
set reboot_character = 82
set gps_provider = NMEA
set gps_sbas_mode = AUTO
set gps_auto_config = ON
set gps_auto_baud = OFF
set serialrx_provider = SPEK1024
set sbus_inversion = ON
set spektrum_sat_bind = 0
set telemetry_switch = OFF
set telemetry_inversion = OFF
set frsky_default_lattitude =  0.000
set frsky_default_longitude =  0.000
set frsky_coordinates_format = 0
set frsky_unit = IMPERIAL
set frsky_vfas_precision = 0
set hott_alarm_sound_interval = 5
set battery_capacity = 0
set vbat_scale = 110
set vbat_max_cell_voltage = 43
set vbat_min_cell_voltage = 33
set vbat_warning_cell_voltage = 35
set current_meter_scale = 400
set current_meter_offset = 0
set multiwii_current_meter_output = OFF
set current_meter_type = ADC
set align_gyro = DEFAULT
set align_acc = DEFAULT
set align_mag = DEFAULT
set align_board_roll = 0
set align_board_pitch = 0
set align_board_yaw = 0
set max_angle_inclination = 500
set gyro_lpf = 42HZ
set moron_threshold = 32
set imu_dcm_kp = 2500
set imu_dcm_ki = 0
set yaw_control_direction = 1
set pid_at_min_throttle = ON
set yaw_motor_direction = 1
set yaw_jump_prevention_limit = 200
set tri_unarmed_servo = ON
set servo_lowpass_freq = 400
set servo_lowpass_enable = OFF
set failsafe_delay = 10
set failsafe_off_delay = 200
set failsafe_throttle = 1000
set failsafe_kill_switch = ON
set failsafe_throttle_low_delay = 20
set failsafe_procedure = 1
set rx_min_usec = 885
set rx_max_usec = 2115
set acc_hardware = 0
set baro_hardware = 0
set mag_hardware = 0
set blackbox_rate_num = 1
set blackbox_rate_denom = 1
set blackbox_device = SERIAL
set magzero_x = 0
set magzero_y = 0
set magzero_z = 0

# rxfail
rxfail 0 a
rxfail 1 a
rxfail 2 a
rxfail 3 a
rxfail 4 h
rxfail 5 s 1500
rxfail 6 h
rxfail 7 h
rxfail 8 h
rxfail 9 h
rxfail 10 h
rxfail 11 h
rxfail 12 h
rxfail 13 h
rxfail 14 h
rxfail 15 h
rxfail 16 h
rxfail 17 h

# dump profile

# profile
profile 0

# aux
aux 0 2 0 1600 2050
aux 1 26 2 925 1350
aux 2 0 0 900 900
aux 3 0 0 900 900
aux 4 0 0 900 900
aux 5 0 0 900 900
aux 6 0 0 900 900
aux 7 0 0 900 900
aux 8 0 0 900 900
aux 9 0 0 900 900
aux 10 0 0 900 900
aux 11 0 0 900 900
aux 12 0 0 900 900
aux 13 0 0 900 900
aux 14 0 0 900 900
aux 15 0 0 900 900
aux 16 0 0 900 900
aux 17 0 0 900 900
aux 18 0 0 900 900
aux 19 0 0 900 900

# adjrange
adjrange 0 0 0 900 900 0 0
adjrange 1 0 0 900 900 0 0
adjrange 2 0 0 900 900 0 0
adjrange 3 0 0 900 900 0 0
adjrange 4 0 0 900 900 0 0
adjrange 5 0 0 900 900 0 0
adjrange 6 0 0 900 900 0 0
adjrange 7 0 0 900 900 0 0
adjrange 8 0 0 900 900 0 0
adjrange 9 0 0 900 900 0 0
adjrange 10 0 0 900 900 0 0
adjrange 11 0 0 900 900 0 0

# rxrange
rxrange 0 1000 2000
rxrange 1 1000 2000
rxrange 2 1000 2000
rxrange 3 1000 2000

# servo
servo 0 1000 2000 1500 45 45 100 -1
servo 1 1000 2000 1500 45 45 100 -1
servo 2 1000 2000 1500 45 45 100 -1
servo 3 1000 2000 1500 45 45 100 -1
servo 4 1000 2000 1500 45 45 100 -1
servo 5 1000 2000 1500 45 45 100 -1
servo 6 1000 2000 1500 45 45 100 -1
servo 7 1000 2000 1500 45 45 100 -1

set gps_pos_p = 15
set gps_pos_i = 0
set gps_pos_d = 0
set gps_posr_p = 34
set gps_posr_i = 14
set gps_posr_d = 53
set gps_nav_p = 25
set gps_nav_i = 33
set gps_nav_d = 83
set gps_wp_radius = 200
set nav_controls_heading = ON
set nav_speed_min = 100
set nav_speed_max = 300
set nav_slew_rate = 30
set alt_hold_deadband = 40
set alt_hold_fast_change = ON
set deadband = 0
set yaw_deadband = 0
set throttle_correction_value = 0
set throttle_correction_angle = 800
set default_rate_profile = 0
set gimbal_mode = NORMAL
set acc_cut_hz = 15
set accxy_deadband = 40
set accz_deadband = 40
set accz_lpf_cutoff =  5.000
set acc_unarmedcal = ON
set acc_trim_pitch = 0
set acc_trim_roll = 0
set baro_tab_size = 21
set baro_noise_lpf =  0.600
set baro_cf_vel =  0.985
set baro_cf_alt =  0.965
set mag_declination = 0
set pid_controller = LUX
set p_pitch = 40
set i_pitch = 30
set d_pitch = 23
set p_roll = 40
set i_roll = 30
set d_roll = 23
set p_yaw = 85
set i_yaw = 45
set d_yaw = 0
set p_pitchf =  1.400
set i_pitchf =  0.400
set d_pitchf =  0.030
set p_rollf =  1.400
set i_rollf =  0.400
set d_rollf =  0.030
set p_yawf =  3.500
set i_yawf =  0.400
set d_yawf =  0.010
set level_horizon =  3.000
set level_angle =  5.000
set sensitivity_horizon = 75
set p_alt = 50
set i_alt = 0
set d_alt = 0
set p_level = 90
set i_level = 10
set d_level = 100
set p_vel = 120
set i_vel = 45
set d_vel = 1
set yaw_p_limit = 500
set gyro_soft_lpf = OFF
set dterm_cut_hz = 0
set yaw_pterm_cut_hz = 0
set gtune_loP_rll = 10
set gtune_loP_ptch = 10
set gtune_loP_yw = 10
set gtune_hiP_rll = 100
set gtune_hiP_ptch = 100
set gtune_hiP_yw = 100
set gtune_pwr = 0
set gtune_settle_time = 450
set gtune_average_cycles = 16

# dump rates

# rateprofile
rateprofile 0

set rc_rate = 70
set rc_expo = 100
set rc_yaw_expo = 20
set thr_mid = 50
set thr_expo = 10
set roll_rate = 0
set pitch_rate = 0
set yaw_rate = 50
set tpa_rate = 0
set tpa_breakpoint = 1500

#

EDIT: I just noticed your min_throttle is set to 1000 and min_check is set to 1100. Mine are both at 1100.
Reply
#11
Alright, I've got all my settings the same as yours (where it's important). I will test again after work.

I'll have to figure out how to set my endpoints on the Turnigy. I have no idea how to do that (I bought it used and it was all set up already).
Reply
#12
Ok, next update. Green LED stops blinking (and goes off)......but still no response to inputs of any type and won't arm at all.

Here are pictures of all my TX settings on this model.

I'm starting to wonder if this is a problem with the OrangeRx module. I've heard people have problems binding it to the Inductrix which has a Spektrum rx.
Reply
#13
Ok, some more debugging information. In CleanFlight when I plug in the quad, if the TX is turned ON the receiver tab looks like this. With the TX turned OFF the receiver tab looks like this.

That HAS to be my problem somehow right?
Reply
#14
(07-Jul-2016, 10:47 PM)jamesw Wrote: Ok, some more debugging information.  In CleanFlight when I plug in the quad, if the TX is turned ON the receiver tab looks like this.  With the TX turned OFF the receiver tab looks like this.

That HAS to be my problem somehow right?

I just looked through your transmitter settings.  Only thing I'm curious about is if you used template for HELI or for Simple 6-channel (don't use HELI, although I don't think that is your problem).  I did a quick search, and if your OrangeRX module is one of the newer ones, it may have some dip switches on it.  If it does, try enabling switches 3 & 5. ( https://www.reddit.com/r/Quadcopter/comm...le_doesnt/ )

If you have those switches, and it doesn't work, you might try rebinding after you set the switches.  (Turn off Tx, plug in usb and wait for fast flashing red light, then turn on Tx with bind button held.)

I think you are correct about the module somehow being the problem.  The FC is getting a signal from the Tx - it's just all "minimums".

EDIT: Just found this: http://www.hobbyking.com/hobbyking/store...272X15.pdf
If this is your module, you will need to set the switches to DSM2-1024/22 (I'm not sure if that is what 3&5 do or not)
Reply
#15
Weird, I was positive that I bought "the new one" when it comes to the OrangeRx module, but mine looks exactly like that one....except without the dip switches. Looking at the board in the OrangeRx there is circuitry that looks like it would fit dipswitches perfectly, but there are no dipswitches and it's covered in plastic.

According to the pdf link you posted. Switch 3 sets DSM2(x) to Manual mode and Switch 5 sets DSM2(x) to 11ms (22ms if OFF). I wonder if I can crack open the case and manually set those switches with solder...

Found this thread that tells me how to change those settings via hitting the bind button.

Quote:The designers of the module did add a feature for this - you can manually switch between modes by quickly pressing the BIND button three times.

When in DSM2/22ms the module light is off. In DSM2/11ms the light on the module flashes once then after a pause flashes once again and so on - this is the indication of the module RF mode. In DSMX/22ms the module flashes twice and in DSMX/11ms it flashes three times.

I have been able to switch the mode using this (I see the light doing different patterns).  Now I just need to figure out what pattern is the right one.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Binding TinyHawk 3 Plus ExpressELRS/Betafpv Lite Radio 3 fpvNewbie 21 516 20-Mar-2024, 12:01 PM
Last Post: NewToFPV
  VTX issue - ATOMRC hurricane 5 bar1 1 115 10-Mar-2024, 12:36 PM
Last Post: hugnosed_bat
Video Troubleshooting motor issue - I'm stuck, help! doraymon 7 241 25-Feb-2024, 05:48 PM
Last Post: Pathfinder075
  issue in walksnail x Eyes.fpv 0 124 09-Feb-2024, 07:15 PM
Last Post: Eyes.fpv
  FrSky R-XSR not binding with Taranis QX7 ACCST Pete10 6 222 26-Dec-2023, 06:06 PM
Last Post: Rob Axel


Login to remove this ad | Register Here