Discussions

Test code

Posted by Kim Skatun on July 10, 2013 at 5:01am

Hi

I am trying to turn the apm 2.0 into a logger but doesnt know quite where to start. I will try to log gps, compass,mpu,temperature and altitude as fast as possible and just dump it to the serial with the mavlink protocol. I would therefore like to get rid of all the other code and just keep these features.

Should i start with test.pde and somehow modify it or?

All help would be nice.

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –
Follow

Replies

  • Kim Skatun July 12, 2013 at 3:37am

    Thanks, im on to it. I am using a rpi to log the sensor from apm and then saved it to file and then transfer it to a server and then put it onto a database.

  • Kim Skatun July 11, 2013 at 3:33am

    At the moment i only get 25, why not 50hz?

  • Kim Skatun July 11, 2013 at 3:27am

    Any ideas how i can  modify the code to log faster?

  • Kim Skatun July 11, 2013 at 2:41am

    I edited GCS_Mavlink file so that apm sends onto serial only the data I need.By simply breaking cases in mavlink_try_send_message:

    case MSG_LOCATION:
    break;
    CHECK_PAYLOAD_SIZE(GLOBAL_POSITION_INT);
    send_location(chan);
    break;

    IS it somehow possible to get it to log with 100Hz?

    Интернет-магазин Need.by ручного инструмента и строительных материалов
    Интернет-магазин стройматериалов и ручного инструмента в Минске и Беларуси Need.by - купить строительные материалы и ручной инструмент оптом, в розни…
  • Kim Skatun July 11, 2013 at 2:33am

    I'm using mavproxy on linux to get the live data from apm. I'm using one of its options to set a higher stream rate. I've read that the max rate is 50Hz, however, I can't get more than 25Hz, no matter how big I set it.
    I edited GCS_Mavlink file so that apm sends onto serial only the data I need.
    Should I follow your previous post anyway to speed things up or is there something else which causes that I cannot reach 50Hz?

  • Søren Kuula July 10, 2013 at 8:25am
    Start with eg. the ArduPlane directory and get ArduPlane to compile OK. Now delete, in the .pde files, everything you don't want. For example, with attitude and radio control you can delete entire pde files. Others you need to edit to remove eg. control mode. Leave the HAL and all .cpp as is. Work in small steps, getting code to compile again before next kill. And also check that the mavlink and measurement parts still are working.
    Regards, Soren
This reply was deleted.

Activity