Hardcoded paths called about mavproxy HOT 11 CLOSED

There's an updated version of MAVProxy at http://firmware.diydrones.com/Tools/MAVProxy/ that should help you.

from mavproxy.

Downloaded the "latest" (I assume the latest is 2015-05-13) and similar issues

from mavproxy.

I can't seem to be able to replicate the issue. Which flight controller (and version) and you connecting to?
Are you running MAXProxy with any commandline options?

from mavproxy.

No FC attached. And also no cmdline options on the screenshot.

from mavproxy.

Any chance you could scroll to the top of your console so I could see the entire output? It should start with "Logging to mav.tlog"

from mavproxy.

The console when opened, without any commands issued, yet. Still the eggs dir :)

Closing the Mavproxy console

from mavproxy.

btw:

This is quite easy to duplicate. The screenshots are from a freshly installed Windows7-64. So a similar VM with a freshly installed (and Windows updated) replicates this behavior easily...

from mavproxy.

The "Using deprecated class PySimpleApp" message is a known warning. It doesn't affect the functionality of the program.
As for the "EOFError", that is normal when exiting MAVProxy.
How did you get the "Nonetype object has no attribute 'param_set_send' error from previously? I'm unable to replicate that particular message.

from mavproxy.

If I remember correctly that came up because I chose Clear Mission without FC attached.

from mavproxy.

Ahh yes, I see now.

The issue is that some MAVProxy modules don't check to see if there's a valid connection before executing a command.

The hardcoded directories in the error messages are an artifact of the compilation process, but do not affect the running of the program.

from mavproxy.

ok. thanks

from mavproxy.