Information

ArduCopter User Group

Discussion group for ArduCopter users

Members: 2942
Latest Activity: 7 hours ago

Discussion Forum

Problem with Hexacopter using APM 2.8

Started by Darius. Last reply by Doug Adduci 7 hours ago. 33 Replies

Hello, I recently purchased a Tarot 690s hexacopter , it was partially assembled (e.i the ESCs and UBEC were already soldered to the PDB). The Flight controller is an Arducopter APM 2.8 and the TX/RX…Continue

bad LiDAR health

Started by velonica boo. Last reply by Thomas J Coyle III yesterday. 1 Reply

hi , i got Bad LiDAR Health error when i connect my  LIDAR-Lite to pixhawk . Sonarvoltage and sonarange is always zero , distance is 0 . What shall i do to make it work ?Continue

Sub 250 Gram Pixracer Build - Parts

Started by Edgar Scott. Last reply by Forrest Frantz on Thursday. 28 Replies

Since my Sub 250 gram pixracer is complete I thought I would share a parts list and some build pics.The FC is a small 36x36 Pixhawk based, its capable of full autonomous waypoint flights, ACRO, has…Continue

Go to waypoint after Loiter_Unlimited command

Started by Murdanny Mukhtar. Last reply by Murdanny Mukhtar on Thursday. 2 Replies

Hi all,I currently have the following commands on my mission.1) Takeoff2) Loiter_Unlimited3) WP According to the article on the MAV_CMD:The mission will not proceed past this command while in AUTO…Continue

Comment Wall

Comment

You need to be a member of ArduCopter User Group to add comments!

Comment by Wayne Morris on June 23, 2013 at 6:22am

OK, that sounds better. Can I download the standard firmware file from somewhere to compare with the one I compiled to ensure they match?

Comment by Stephen Dade on June 22, 2013 at 9:28pm

Wayne - The warnings are expected (and normal) with the APM code. The output file is expected to be put in a temp file - that's how the makefile is programmed.

If you're using the Arduino environment, simply select the mega2560 board and correct com port, then press "verify" and then press "upload". Arduino will take care of the details.

The makefile is only used directly if you're using Linux or Cygwin (on Windows).

Comment by Bob Doiron on June 22, 2013 at 6:40pm
Arduino will compile and download from the project directory. The 'verify', which is a compile, happens in the temp. I never did try having arduino install it...
Comment by Wayne Morris on June 22, 2013 at 6:39pm

The make file is just a configuration. I read instructions to run it.

To compile, I am selecting the sketch and clicking compile.

Thanks for the input.

Comment by Wayne Morris on June 22, 2013 at 6:36pm

So the output file is:

C:\Users\Wayne\AppData\Local\Temp\build7487716384992828737.tmp\ArduCopter.cpp.elf C:\Users\Wayne\AppData\Local\Temp\build7487716384992828737.tmp\ArduCopter.cpp.hex

I have done other Ardunio projects but the output was in the target directory.

Comment by Wayne Morris on June 22, 2013 at 6:32pm

I am getting these warnings:

Log.pde: In function 'int8_t dump_log(uint8_t, const Menu::arg*)':
Log.pde:80: warning: comparison between signed and unsigned integer expressions
Log.pde:80: warning: comparison between signed and unsigned integer expressions
ArduCopter.pde: At global scope:
ArduCopter.pde:189: warning: 'int16_t get_heli_rate_roll(int32_t)' declared 'static' but never defined
ArduCopter.pde:191: warning: 'int16_t get_heli_rate_pitch(int32_t)' declared 'static' but never defined
ArduCopter.pde:193: warning: 'int16_t get_heli_rate_yaw(int32_t)' declared 'static' but never defined
GCS_Mavlink.pde:275: warning: 'void send_simstate(mavlink_channel_t)' defined but not used
Log.pde:573: warning: 'void Log_Write_Data(uint8_t, uint16_t)' defined but not used
Log.pde:630: warning: 'void Log_Write_Data(uint8_t, float)' defined but not used
ArduCopter.pde:316: warning: 'void Log_Write_DMP()' declared 'static' but never defined
ArduCopter.pde:298: warning: 'void Log_Write_IMU()' declared 'static' but never defined
ArduCopter.pde:299: warning: 'void Log_Write_GPS()' declared 'static' but never defined
ArduCopter.pde:483: warning: 'void report_heli()' declared 'static' but never defined
ArduCopter.pde:484: warning: 'void report_gyro()' declared 'static' but never defined
ArduCopter.pde:497: warning: 'RC_Channel* heli_get_servo(int16_t)' declared 'static' but never defined
ArduCopter.pde:498: warning: 'int16_t read_num_from_serial()' declared 'static' but never defined

Comment by Bob Doiron on June 22, 2013 at 6:24pm
You hit the check mark in arduino and it does a verify by compiling it in a temp folder. That's the hex you want to install in Mission Planner. I get warnings when I compile 2.91b for a quad frame - seems related to heli code that is compiled out.
Comment by Bo Barry on June 22, 2013 at 6:19pm

Dont run the makefile. Load the Arducopter.pde and compile it

Comment by Wayne Morris on June 22, 2013 at 6:08pm

I just tried again but the same results. The mega2560 is selected already.

Comment by Bo Barry on June 22, 2013 at 4:57pm

I didn't run the makefile, I loaded up the Arducopter.pde sketch in Arduino, selected the mega2560 under Tools, and it compiled perfectly (slowly).

Still building on mine so the software hasn't been loaded.

Good luck, Bo

 
 
 

DIY Drones Monthly
Newsletter

Groups

Season Two of the Trust Time Trial (T3) Contest 
A list of all T3 contests is here. The current round, the Vertical Horizontal one, is here

© 2016   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service