Asked — Edited

Ar Drone Enable Tracking Causes Not Responding

I updated to the latest version today, this also happened on the previous version as well. All the lateset win7 updates, and .NET updates.

Can connect and run EZB no problems, can connect to the drone without issue, enable the camera, still fine live video no problem, enable color tracking, still no issue. put a red target in front of the camera, see the blue tracking square, then the circle of death mouse pointer and a screen refresh with (Not reponding). No more EZB need to kill it off and restart?

Any ideas?

Tried various USB ports for both the wifi and bluetooth (all work the same, no change) tried various com ports for the bluetooth connection. Removed the EZB bluetooth device and re-deiscovered and installed it. Went back to .NET 3.5 same problem. Let the system update back to .NET 4 still same issue.

Not sure what else to try

Thank you jimk

confused


ARC Pro

Upgrade to ARC Pro

Stay at the forefront of robot programming innovation with ARC Pro, ensuring your robot is always equipped with the latest advancements.

#1  

Digging into this a bit further, I captured a dmp from a couple of hangs and they both lead to the same symbol file errors, this server is running 64 bit windows 7, so we are in 32 bit compatability mode. It appears that it is unable ot find symbols for ntdll.dll, and wow64cpu.dll

thank you jimk

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\ARC.DMP] User Mini Dump File with Full Memory: Only application data is available

Symbol search path is: *** Invalid ***


  • Symbol loading may be unreliable without a symbol search path. *
  • Use .symfix to have the debugger choose a symbol path. *
  • After setting your symbol path, use .reload to refresh symbol locations. *

Executable search path is: Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: SingleUserTS Machine Name: Debug session time: Sun Apr 8 10:28:22.000 2012 (UTC - 4:00) System Uptime: not available Process Uptime: 0 days 0:08:55.000 .....................................WARNING: rsaenh overlaps cryptsp .WARNING: RpcRtRemote overlaps rsaenh .....................WARNING: wtsapi32 overlaps uxtheme ..WARNING: spsreng overlaps System_Xml_ni ... .WARNING: srloc overlaps EZ_B ...............WARNING: System_Xml_Linq_ni overlaps MMDevAPI .........WARNING: d3d9 overlaps wpfgfx_v0300 . *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll - *** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64cpu.dll - wow64cpu!TurboDispatchJumpAddressEnd+0x6c0: 0000000073c72e09 0000 add byte ptr [rax],al ds:fffff8800794a530=??

PRO
Synthiam
#2  

Try the latest version. Let me know if that helps.

I can reproduce the issue on someone elses computer. I cannot reproduce the issue on any of my computers:(

#3  

HI DJ: Thank you for jumping on this so quickly. Sorry to goof you day. Still hangs, but now the it looks like the color map to the live video is goofed.

The error is somewhat similar in the Dump

Loading Dump File [C:\ARC (4).DMP] User Mini Dump File with Full Memory: Only application data is available

Symbol search path is: *** Invalid ***


  • Symbol loading may be unreliable without a symbol search path. *
  • Use .symfix to have the debugger choose a symbol path. *
  • After setting your symbol path, use .reload to refresh symbol locations. *

Executable search path is: Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: SingleUserTS Machine Name: Debug session time: Sun Apr 8 21:20:57.000 2012 (UTC - 4:00) System Uptime: 0 days 23:29:06.941 Process Uptime: 0 days 0:02:05.000 .....................................WARNING: rsaenh overlaps cryptsp .WARNING: RpcRtRemote overlaps rsaenh ................WARNING: sapi overlaps System_Windows_Forms_ni .....WARNING: wtsapi32 overlaps uxtheme ..WARNING: spsreng overlaps System_Xml_ni ... .WARNING: srloc overlaps EZ_B ......................WARNING: winhttp overlaps mscoree .WARNING: webio overlaps hid WARNING: webio overlaps System_Configuration_ni .WARNING: IPHLPAPI overlaps ntmarta .............. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll - *** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64cpu.dll - wow64cpu!TurboDispatchJumpAddressEnd+0x6c0: 00000000`73c72e09 c3 ret

Sorry, jimk

#4  

just uploaded a tif screen capture, not sure if it made it. jimk

#6  

That works !!. So tracking by color works great ! But just don't switch tracking types and come back to color, it will hang. But if I pick color first, it ran for several minutes tracking a red object without issue. Went from color to motion back to color and took another dmp when it quit responding. The good news is I am comfortable trying to let it fly the drone and see what happens this eve. But unfortuantely need to leave for work :-(

Thanks again for the great Support !!!! jimk

Symbol search path is: *** Invalid ***


  • Symbol loading may be unreliable without a symbol search path. *
  • Use .symfix to have the debugger choose a symbol path. *
  • After setting your symbol path, use .reload to refresh symbol locations. *

Executable search path is: Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: SingleUserTS Machine Name: Debug session time: Mon Apr 9 08:18:58.000 2012 (UTC - 4:00) System Uptime: 1 days 10:27:08.610 Process Uptime: 0 days 0:03:45.000 .....................................WARNING: rsaenh overlaps cryptsp .WARNING: RpcRtRemote overlaps rsaenh ...........WARNING: dinput8 overlaps System_Drawing_ni ..........WARNING: wtsapi32 overlaps uxtheme ..WARNING: spsreng overlaps System_Configuration_ni ... .WARNING: srloc overlaps GdiPlus ...WARNING: propsys overlaps System_ni ....................WARNING: d3d9 overlaps wpfgfx_v0300 .. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll - *** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64cpu.dll - wow64cpu!TurboDispatchJumpAddressEnd+0x6c0: 00000000`73c72e09 c3 ret

PRO
Synthiam
#7  

@kleinjd thanks for trying it:) ... I can't re-produce the issue on my computers. It seems to be processor speed releated. Two threads are locking the image bitmap object. When this happens, C# doesn't hold the process until the lock is released - instead it hangs the entire runtime. It is a bug in C#, from what I can tell - but only a bug when the CPU has limited processing speed available and threads are not physically seperated on the processor, but are virtually seperated by pre-emptive multitasking.

So locking and synchronizing the variable does more harm than good.

It would be a lot easier if I could reproduce the issue. We have quite a few laptops here, but they're all fast I5's and I7's. I'll need to get an AMD-C50 or E350 to test with and reproduce the issue.

What are your PC specs?

#8  

HI DJ: So just like you recycling bots, I am using disgarded systems from work. This one is a storage server. Supermicro motherboard with 2x 3.2Ghz XEONs, Intel E7520 (Lindenhurst) Chipset with 4GB RAM, dual socket with HT (4 threads). http://www.supermicro.com/products/motherboard/Xeon800/E7520/X6DH8-XG2.cfm

So given the great troubleshooting you did, I am wondering if I shutdown Hyper threading and/or pin the EZB process to a specific core. If that would do it. So with no HT and pinned to socket 1 (os on socket 0) that should limit it to a single core, single thread and this might do the trick.

In case you are wondering, right now this project is confided to the basement, all my video work is done on this server as it has a nice chunk of fibre channel storage on it to store the video from various projects and gives me remote access :-)

jimk

PRO
Synthiam
#9  

Awesome jim. good to hear the software is mostly stable across multi processors. If you have time, try the latest version i posted today.

also use the Debug window (F2) to see if there are any details in the log before it locks up:)

#10  

uh oh, updated EZB and it told me I needed to update the firmware. Now I find the following, several attempts same result:

Attempting connection to COM3 EZ-B reports EZ-B Firmware V15.3 Connected Press the UPDATE button to start upgrade sending ping sending ping sending bootloader Failed to load bootloader! Have you selected the correct EZ-B COM port? Use the Help menu option to view the online help and watch a video demonstration.

jimk

#11  

No worries after all, slowed the port down to 19200 and went without issue. And the update is a SCREAMING SUCCESS !!!!

Been running all 3 targeting modes without a problem, also changing between modes without a problem. So you nailed it :-)

Set the priority to High and affinity to CPU 1, runs about 15% of the CPU.

Thank you !!!! jimk

PRO
Synthiam
#12  

:) Awesome

You souldn't need to change any COM settings. Defaults work best. I feel less is more:) So i never change anything. I install windows, and go from there.:D But, sounds like you got it working anyway!