Replies to This Discussion

Permalink Reply by alex corbett on July 16, 2012 at 11:25pm

Jazztech, yes I'm using 2.4 for my fpv tx. My tri seems to be rtl'ing ok again now. Just seems to go weird every now and then. I did check out a log from my loiter and the graph has the correct shape but the lines are very jagged and not smooth, I wander if I am picking up noise from somewhere.

• ▶ Reply

Permalink Reply by graham newton on July 4, 2012 at 3:00am

I still have an issue with GPS... I get a solid blue light on the GPS Unit, but the mission planner (connected via Xbee) does not pick up GPS signal. 0 satcount, but solid blue light... My GPS location does not show on the mission planner.

I am running APM1 with 2.6 (modified for octo quad)

Any help would be appreciated.

Thanks

• ▶ Reply

Permalink Reply by James on July 4, 2012 at 3:15am

graham,

i occasionally have this problem and in my case i suspect the cable is the cause.  whenever this occurs i power down APM, reseat the GPS cable, and start it up again.  as far as i can tell this solves the problem pretty much every time.

james

• ▶ Reply

Permalink Reply by graham newton on July 4, 2012 at 7:43am

Thanks I will do another inspection

• ▶ Reply

Permalink Reply by steve F11music.com on July 4, 2012 at 7:48am

Exactly the same problem I occasionally have. Solid blue but zero sats reported in MP. I unplug main power and reset gps connector and restart. Solves it maybe 100% of the time but I'm not sure if the problem was the cable. Have to test if a restart is all that is correcting it. I'm using latest arduplane code. Haven't noticed the problem on my quad but it might be because I'm flying it less often.

• ▶ Reply

Permalink Reply by Robert Valley on July 4, 2012 at 11:25am

Just an update on my needing forward trim in Acro mode but not in level mode. I solved the problem by recalibrating the rear motor ESC high end to 82% this makes it run faster at any throttle setting. It didn't change level mode at all.

Bob 

• ▶ Reply

Permalink Reply by jazztech on July 4, 2012 at 12:57pm

Wow, that's an ugly fix ;) Hope it will not go forward or shake at WOT. Does it ? Increasing the pitch rate I did help a bit or was completely ineffective ?My tri may have a CG very forward when adding some batteries for "long duration" flights, but it still does maintain the desired angle in acro mode. I hope yours will not go nuts if you change the CG.

• ▶ Reply

Permalink Reply by Robert Valley on July 4, 2012 at 1:17pm

I was flying it around today and it seems fine. I tried a few full throttle punch outs as well and it went straight up. It is quite windy today and Acro is OK in the wind but level mode needs some tuning it was rocking some. I had 10 inch props on it as well and it seems to like 9 inch better.

• ▶ Reply

Permalink Reply by Jonathan M on July 4, 2012 at 1:02pm

Robert,  I have the exact same issue as you, and I think it's really CG sensitive.  My CG is slightly aft right now, and i get that rotation in acro mode.  I currently run with no rate_i, but i may try adding some.  

• ▶ Reply

Permalink Reply by Mike Mac on July 5, 2012 at 3:12am

What’s the LED_MODE parameter? I noticed that on 2.5 the default is 0 and on 2.6 it’s 9?

• ▶ Reply

DeveloperPermalink Reply by Randy on July 5, 2012 at 5:30am

Mike,

     I think the LED_MODE parametr is a bit mask.  Here's are the comments around taken from the leds.pde.

// Copter LEDS by Robert Lefebvre
// Based on the work of U4eake, Bill Sanford, Max Levine, and Oliver
// g.copter_leds_mode controls the copter leds function via bitmath
// Zeroeth bit turns motor leds on and off:                                           00000001
// First bit turns GPS function on and off:                                           00000010
// Second bit turns Aux function on and off:                                        00000100
// Third bit turns on Beeper (legacy Piezo) function:                            00001000
// Fourth bit toggles between Fast Flash or Oscillate on Low Battery:   00010000  (0) does Fast Flash, (1) does Oscillate
// Fifth bit causes motor LEDs to Nav Blink:                                       00100000
// Sixth bit causes GPS LEDs to Nav Blink:                                       01000000

// This code is written in order to be backwards compatible with the old Motor_LEDS code
// I hope to include at least some of the Show_LEDS code in the future
// copter_leds_GPS_blink controls the blinking of the GPS LEDS
// copter_leds_motor_blink controls the blinking of the motor LEDS
// Piezo Code and beeps once on Startup to verify operation
// Piezo Enables Tone on reaching low battery or current alert

So I guess 9 is binary 00001001...so zero'th bit and 3rd bit...so it looks like the leds are on by default and so is the piezo beeper (which most people don't have!).

• ▶ Reply

Permalink Reply by u4eake on July 5, 2012 at 11:09am

Makes sense to have a default of 9 so that motorleds and piezo are on by default.  It used to be like that in the old code, before copterleds was implemented.  Back then piezo and motorleds were also on by default, so that people only had to plug the leds in to get them working, without having to recompile.

I see little harm in having them on by default.  Don't think many people are using those pins for somthing else.

• ▶ Reply

• ‹ Previous
• 1
• …
• 51
• 52
• 53
• 54
• 55
• …
• 68
• Next ›
• Page