Igcs 203 ar drone tilt control

The important change is the sendMoveCommand method in the iGCS/Comm/Interfaces/iGCS/iGCSMavLinkInterface.* files.  The rest was to support testing this new method.
is the :( because the outputMotionData is in this file or the couple of
extra whitespaces.

If its the former, I guess I took your original CoreMotionsUtils request as
a Utility Functions to the CoreMotion stuff.  I'm guessing now that you
meant all the Core Motion Stuff.  Just let me know if that the case and I
can move the remaining stuff as appropriate.

-dave

On Tue, Nov 25, 2014 at 5:55 PM, Andy Brown <notifications@github.com>
wrote:

> In iGCS/UserInterface/ViewControllers/ArDroneViewController.m:
>
> > +                                                GCSMAVRotationAngles anglesOfRotation = [self outputMotionData:deviceMotion];
> > +                                                DDLogDebug(@"Pitch : %d, Roll : %d, Yaw : %d", anglesOfRotation.pitch, anglesOfRotation.roll, anglesOfRotation.yaw);
> > +                                                [[CommController sharedInstance].mavLinkInterface sendMoveCommandWithPitch:anglesOfRotation.pitch andRoll:anglesOfRotation.roll andThrust:self.thrust andYaw:anglesOfRotation.yaw andSequenceNumber:self.sequenceNumber];
> > +                                                self.sequenceNumber++;
> > +                                                if(error){
> > +
> > +                                                    DDLogDebug(@"%@", error);
> > +                                                }
> > +                                            }];
> > +
> > +
> > +}
> > +
> > +
> > +-(GCSMAVRotationAngles)outputMotionData:(CMDeviceMotion*)deviceMotion
> > +{
>
> :(
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/fightingwalrus/iGCS/pull/117/files#r20912032>.
>