Comments

• Mike R. October 8, 2012 at 9:52am

  Welcome to the club Marty :)
• 

  Marty LaBelle October 8, 2012 at 8:25am

  I am officially joining this group, having received my first APM, and QuadCopter components a few days ago. I've been wanting to build one for years, now that I'm out of the Army and building my future career; I'm jumping in.

  I've started finding my way around the forums and I have found even the most active contributors welcoming. This is not the case on other forums, and I appreciate it. Thanks!
• Zachary Koh September 27, 2012 at 5:00am

  @Jani Sorry for the lack of description. I meant to change the "stabilized" pitch angle (such that the quad would be "stabilizing" towards a vertical position rather than horizontal).
  
  Eg:
  Regular quad position while hovering in stabilize:

  +-----===-----+
  
  New position that the "stabilize" function will try to achieve:
  
  +
  |

  |

  ||

  ||

  |

  |
  +
• Developer

  Jani Hirvinen September 27, 2012 at 4:39am

  @Zachary, can you explain a bit more what you plan to do and on which axis
• Zachary Koh September 27, 2012 at 2:52am

  I'm trying to change the "reference" for the stabilize function from eg: 90deg to 180deg.

  Can anyone proficient in understanding the ArduCopter program point me to where I should be looking?
  Your help would be much appreciated.
• Zachary Koh September 26, 2012 at 4:33am

  @Marooned

  Hmm. Do you mean using Mission Planner to upload the 2.7.3 firmware erases the existing radio calibration?

  If that's the case, we should not have to redo the radio calibration since we uploaded both 2.7.3 and our custom program through the Arduino compiler and not Mission Planner.
• 

  Marooned September 26, 2012 at 4:13am

  Updating to 2.7.3 erased eeprom hence this radio calibration. Updating to earlier firmwares left eeprom so no calibration was needed. Anyway, I just wrote what helped me in similar situation. You can try (it takes no more than a minute) or wait for other hints.
• Zachary Koh September 26, 2012 at 4:10am

  @Marooned
  The team moved from the 2.7.3 to our custom program without performing radio calibration and did not have any problems. But moving back, the 2.7.3 produced no response.
  If shifting from one firmware to the next did not give any problem, shifting back to the first should not either.. Right? Pretty perplexed here.
• 

  Marooned September 26, 2012 at 3:52am

  Zachary: did you do radio calibration after uploading new firmware? I forgot about it and had the same effect as you described.
• Zachary Koh September 26, 2012 at 3:51am

  @Randy
  THANKS. I was extremely worried that my programming could have created some problem with the power distribution and inadvertently fried the apm.
  
  But now, we realized that our NEW program allows the apm to function properly (i.e. board powers up, ESCs arm, motors respond to throttle input). However, uploading the regular ArduCopter 2.7.3, the motors stay in calibration mode (consistent beeping), regardless of what we do. Do you know why?
  
  

  As for ESC overheating, is it caused by malfunctioning power distribution?

  Thanks.