tridge / cuav Goto Github PK

I'm unable to build ("python setup.py build") on a 64 bit Ubuntu machine. It works fine on my 32 bit Ubuntu machine.

It seems the ubuntu package for libjpeg-turbo8-dev is compiled without -fPIC option, but cuav/image is compiled with -fPIC. This is causing the linker to fail.

Should I be recompiling libjpeg-turbo locally rather than using the packaged version? This contradicts instructions in the diydrones article, which indicates libjpeg-turbo-progs is sufficient on Ubuntu.

This is a bug in the interaction between cuav code and the mavproxy_CUAV module in MAVProxy.

On a 64 bit virtualbox ubuntu system (with libjpeg-turbo manually installed as per INSTALL.txt in pull request #4 ). MAVProxy, pymavlink and cuav were all installed manually from sources using "python setup.py ..." (clean, build then install). After that, cuav/tests/test_gcs.py fails with the following error:

Unable to load module CUAV.camera: [Errno 2] No such file or directory: '/usr/local/lib/python2.7/dist-packages/MAVProxy-1.0.9-py2.7.egg/MAVProxy/modules/mavproxy_CUAV/../../../cuav/data/chameleon1_arecont0.json'
Unknown command 'camera boundary cuav/data/OBC_search2.txt'
Unknown command 'camera view'

In MAVProxy/modules/mavproxy_CUAV/camera.py:103, camera params are loaded from a file whose location is hardcoded relative to __file__. This location is correct assuming we are running from adjacent source directories (MAVProxy and cuav), but incorrect once the modules are deployed to eggs in dist-packages.

I'm happy to fix this, but what's the right approach? Reference an environment variable? attempt both locations with a try/catch block? Move the mavproxy_CUAV package into the cuav code base and then import it from MAVProxy?

I was using cuav locally with geosearch.py.

On the mosaic window, I tried to navigate the pages with ctrl+N/P, but it didn't resond.

When I switched my keyboard to Greek and tried again it worked.

Anyway, it would be nice if there was a scrollbar and an autoscroll functionality.

I've been looking through the block_xmit.py code and wanted to give it a try over a serial link via telemetry antennae. The code currently uses UDP and I was wondering what would be involved modifying it to support a serial connection too? Would this contribution be useful?