Replies to This Discussion

DeveloperPermalink Reply by R_Lefebvre on July 8, 2012 at 3:37am

u4eake, yup, that was exactly my reasoning.  I wanted this to be backwards compatible since it's frustrating for users to when something that used to work just stops working and they have to search around trying to figure out why.  

Unfortunately, I'm not sure it's totally successful, as I've seen some problems, but I haven't been able to look into them yet.

I also owe everyone a Wiki entry about the feature.  One of the hold-ups is not having any good graphics for it.  I hate to post one of my chickenscratch MSPaint things. ;)

• ▶ Reply

Permalink Reply by Derek Ernewein on July 11, 2012 at 9:52am

I have not been able to find anything no how Copter LEDS works in terms of wiring.

I am new to APM/ArduCopter, I have APM2, I can read code (mostly debug, not so much write unless in VB6 :P).

I plan to take a look at the code to see what outputs you use, but even then I am not sure I will be able to figure it all out. I am also fairly new to RC stuff, so that gives me more things to lookup at times.

 

I think that a Wiki or at least MSPaint would be great. Even a quick one that can be added to later.

 

• ▶ Reply

Permalink Reply by steve F11music.com on July 11, 2012 at 10:44am

Yes the wiki on CopterLEDs could be more complete. Now it references a blog. I would also like to hook them to my APM2 but need to study where the connections are on APM2.

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on July 11, 2012 at 11:01am

F11: Good point. I can give you wiki access to make those changes. Please just PM me with an email address linked to a google account. 

• ▶ Reply

Permalink Reply by Brian McGrath on July 11, 2012 at 11:25am

I've made it work with the APM2. Start here:

 

http://www.diydrones.com/profiles/blog/show?id=705844%3ABlogPost%3A...

 

and then a check the code for 2.6 found that some of the analog ports are assigned to COPTER_LED

#define COPTER_LED_1 AN4   // Motor or Aux LED
#define COPTER_LED_2 AN5   // Motor LED or Beeper
#define COPTER_LED_3 AN6  // Motor or GPS LED
#define COPTER_LED_4 AN7  // Motor LED
#define COPTER_LED_5 AN8 // Motor LED
#define COPTER_LED_6 AN9  // Motor LED
#define COPTER_LED_7 AN10  // Motor LED
#define COPTER_LED_8 AN11  // Motor LED

 

My own experience was that AN4, AN6 and AN7 were functional for the LEDs and that AN5 didn't work, but it's probably because I didn't enable something that needed enabling.

Interestingly, AN10 and AN11 are also assigned to camera gimbal functionality (which I use) so I've stayed away from testing the LEDs on those ports.

 

I've got three strands of LEDs (R, G and W as Nav lights) and they work as advertised (slow flash when disarmed, solid when armed). Haven't tried the battery warning yet, since I've got Frsky telemetry telling me that on the transmitter.

 

Brian.

• ▶ Reply

Permalink Reply by Jo Peer on July 5, 2012 at 11:47pm

Just had a look at some old logs.

This is what my mag log looks like:

Is this how it is supposed to look like?

Seems like a lot of noise to me.

• ▶ Reply

Permalink Reply by Glenn M on July 6, 2012 at 3:43am

I wonder if your mag log looks that way because you had your copter headed right on 360/0 degrees and it kept jumping between them. Try holding a heading 90 degrees away from there and see if it looks better.

• ▶ Reply

DeveloperPermalink Reply by R_Lefebvre on July 8, 2012 at 3:31am

Glenn, yes, exactly.  If you fly heading due north, and flip back and forth between 359 and 1 degrees, that's what you get.  Kinda sucks, but what can you do?

• ▶ Reply

Permalink Reply by John Campen on July 6, 2012 at 3:05am

I tried to run and auto pilot mission last weekend. Im not sure I have the settings correct. The plan basically was to auto take off to 5 meters then after 30 second to go up to 20 meter, then 100, back to 40 then 20 and then land. But all it did was take off to 5 meters and just stayed there.. Can someone please look at the file and let me know whats wrong with it?

Attachments:

• ElevMiss 5m 20m 100m 20 RTL.txt, 1 KB

• ▶ Reply

Permalink Reply by John Campen on July 6, 2012 at 3:41am

this is the log. the flight starts in at about 8.30

Attachments:

• 2012-07-01 08-20-19aut.tlog, 777 KB

• ▶ Reply

Permalink Reply by John Campen on July 7, 2012 at 11:32pm

any advise anyone can offer?

• ▶ Reply

Permalink Reply by Michael Pursifull on July 8, 2012 at 12:06am

you have no navigation commands. You must have navigation (waypoint) commands, and lat/long coordinates. nav commands form the backbone of the script. Without them, it (as you can see) does nothing. 

Create a new script, using only nav (waypoint) commands. Observe how it performs the actions. Then add your yaw, etc commands. 

• ▶ Reply

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