Drone Control 1.1.1 – Some bug fixes

There were some bugs in the new library that were resolved in the newest version of the drone control library (1.1.1):

  • A memory leak caused by the HUD was resolved
  • The network scan is now done three times if it fails
  • A bug when connecting to both the drone network and the drone itself was resolved

The new version 1.1.1 is now available at GitHub .
There is also a new binary out there, containing the new version of the drone control application as well as the detection application. It is available here.

Advertisements

15 Responses to Drone Control 1.1.1 – Some bug fixes

  1. Hello William,

    There was indeed a hard-to-track issue with the progressive commands. I changed the code. Try again 🙂

  2. The firmware version to set currently only changes the command for the camera switch. Since I’m currently working on the drone, I have read through the newest developer guide documents.

    It seems that the PCMD command has not been changed at all. For the two drones I’m currently using, everything went fine with firmware version 1.7.10 and 1.7.11.

    So, unfortunately, I think that this is an issue of your drone.

  3. William Ding says:

    Hi Thomas,
    Thanks a lot for your reply, i just back from travelling and don’t have time to do the testing again. the firmware i currently use is “1.7.6”. i will update you after i implement the testing again. by the way i really found a place i can set the firmware version on the UI, but through reading the source code it seems like that this parameter is not used. i don’t know whether i’m right? thanks again.

  4. Hello William,

    Since I don’t have to work this christmas, I think I’ll have some time looking at the problems that currently appear.

    I have some questions:

    What firmware version are you using. Have you used the correct manual (the one for your firmware version)?

    Have you looked at the code only or have you debugged the code so you can be sure the correct commands are sent?

  5. William Ding says:

    Hi Thomas,
    Recently i tried to remotely control my drone by your Drone Control .Net release at July 30 2011. i found that it only can take off and land. The drone seems like that doesn’t response to my other key press such as “A”,”D”,”S”,”W”, etc. does it turn into hover mode automatically after the drone take off ? i checked your source code according to command “AT*PCMD=%d,%d,%d,%d,%d,%d”. you Always set the flag (argument 2) bit zero to one to make the drone consider the other arguments.Setting it to zero makes the drone enter hovering mode (staying on top of the same point
    on the ground). So the drone should work well. i don’t know why. Could you give me some suggestions. thanks!

  6. robert says:

    Thanks for the answer originalone1984 –
    I downloaded a joystick sensitivity program for that from Logitech but can’t really try it out since Drone Control 1.1.1 crashes a lot – it might have something to do with the installation of .NET Framework 4 on my Vista64 laptop but I’m not a software guy so can’t tell (the latest Microsoft updates for .NET don’t want to install).

  7. That’s right, joystick sensitivity has not yet been built in. Since I don’t have a lot of time atm, this may take a while, I’m afraid.

  8. robert says:

    Hi,
    Thanks for AR.Drone-Control.NET –
    Works great with my Logitech Extreme 3D joystick on Vista x64!

    I’ve been reading and searching but cant find the settings for joystick sensitivity?
    Buttons mapping is fine but I’d like to decrease the pitch sensitivity (so the drone moves less with larger movements of the stick) …

    Any advice is appreciated!
    Thanks, – robert

  9. This version should work on Windows 7 64 Bits. I’m using it, myself. That’s a wierd error … Xaml parsing has never been a problem in any previous version of the drone library.

    Maybe there is a problem with encoding settings, but this is particularly wierd failure.

  10. Yann says:

    Here is the errors I have in the event viewer :
    Application: ARDrone.UI.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Windows.Markup.XamlParseException
    Stack:
    at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri)
    at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
    at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
    at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
    at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
    at System.Windows.Application.LoadComponent(System.Uri, Boolean)
    at System.Windows.Application.DoStartup()
    at System.Windows.Application.b__1(System.Object)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.DispatcherOperation.InvokeImpl()
    at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
    at System.Threading.ExecutionContext.runTryCode(System.Object)
    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
    at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    at System.Windows.Threading.DispatcherOperation.Invoke()
    at System.Windows.Threading.Dispatcher.ProcessQueue()
    at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
    at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
    at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
    at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
    at System.Windows.Threading.Dispatcher.Run()
    at System.Windows.Application.RunDispatcher(System.Object)
    at System.Windows.Application.RunInternal(System.Windows.Window)
    at System.Windows.Application.Run(System.Windows.Window)
    at ARDrone.UI.App.Main()

    and :

    Faulting application name: ARDrone.UI.exe, version: 1.0.0.0, time stamp: 0x4ddbeed1
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7bafa
    Exception code: 0xe0434352
    Fault offset: 0x0000b727
    Faulting process id: 0x4774
    Faulting application start time: 0x01cc419351e80d94
    Faulting application path: Z:\ARDrone\ARDrone Control .NET-1.1.1\ARDroneUI\ARDrone.UI.exe
    Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
    Report Id: 914348cb-ad86-11e0-b371-20cf30049a58

  11. Yann says:

    Hello,
    Should it work in Win7 64bits? I tried on 2 differant computers but when I lunch ARDrone.UI.exe, nothing happen at all. (no error, no windows,…)

  12. The invert axis checkbox is one thing that was planned for the next versions (as well as a Wii calibration mode). But if you want to make an official request, go to the GitHub page and enter your wish into the issue tracker.

  13. michael says:

    Can i add somesthing to the wishlist ? 🙂

    i’d like de posibility to invert axis from the joystick ..
    and set funktion like “make picture” or “start/stop video” on the buttons

  14. This could be my fault. Maybe I forgot to update the video recording functionality. If this is the case, I’ll have it updated in the next version of the library.

    The next version could be out within the next two to three weeks.

  15. michael says:

    Great Job ..
    i became my drone ond friday and flew the whole weekend just with that exe (mosly just over the screen) on a asus eee win7 32bit dual core atom 2GB ram

    make picture works , but not the video thingi (in uncompressed mode i get a video file but can’t play it , compressed kills the prog.)
    i think i have to add some libs

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: