APM Planner Crash/Freeze in Terminal/CLI

I've been having this problem for a while:

Often (but not always), when I connect APM Planner to the APM board via a USB cable and click on "Terminal" to check logs or whatever, when I press enter three times to get into CLI mode, it causes APM Planner to freeze, and the only way to exit the program is with task manager.  Sometimes it happens the first time I press enter, sometimes it happens the second or third time.  Sometimes it doesn't happen at all.

I have Windows 7 Ultimate, using APM Planner 1.1.92 and 1.1.94 (but it happened with earlier versions too).  I have four APM2 boards, with different versions of Arduplane loaded (2.33, 2.34, and 2.40), and all of them give me this problem as well.

Has anyone else experienced this, or found a solution?

Thanks!

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

Join diydrones

Email me when people reply –

Replies

  • Developer

    i think ive found the source of this, it wil lbe fixed in the next build

     

  • Exact same thing started today for me..

    Win 7 Ultimate - Fully updated

    Xbee telemetry connection via USB port to 'copter

    All is well until I go to terminal screen - Instead of getting the usual init/Arducopter text telling me to hit enter 3 times for a prompt, I get machine code scrolling rapidly. If I hit enter once, APM Planner locks up, only way to kill is to end process..

    When I get the machine code scrolling, I tried to just click the dl logs button, but the log list screen scrolls rapid machine code and causes the laptop to beep..

    I do believe this is a decent size bug.. I'll try to directly connect via USB cable to see if there is a difference for me..

  • I have the same problem. When I enter any key, not only Enter, the Planner freezes (I'm using the latest 1.1.95 with mavlink 1.0). Running on Windows 7 professional.

    Actually, it is not disconnecting the COM line, either.

  • I think that the key issue to note here is that APM Planner only freezes when I press 'enter ' in the Terminal/CLI screen.  It definitely seems to happen with certain APM2's more than others.  I haven't tried it yet on a different computer, but based on Ward's reply, I get the impression it would.

    I can't see how it would be the APM2 disconnecting only when I try to access CLI mode.  Furthemore, I can use a different terminal program without any problems (X-CTU has a terminal that seems to work well for this).

    Is anyone else having this issue, or just a handful of us?

  • Developer

    are you sure the apm2 isnt browning out? try a diffrent usb port

This reply was deleted.

Activity