Hi
I recently started using mavproxy on my Mac and could easily run udp/tcp connection with qgroundcontrol using a pixhawk and wifly.
Next step is to use mavproxy.
With mavproxy I first successfully used USB cable using the following command:
python mavproxy.py --aircraft=copter --quadcopter --master=/dev/tty.usbmodem1 --baud=57600
copter/logs/2015-01-30/flight1
Logging to copter/logs/2015-01-30/flight1/flight.log
MAV> _RAPM: barometer calibration complete
APM: GROUND START
Init Gyro**APM: Initialising APM...
INS
----------------------------------------
G_off: 0.01, 0.03, -0.05
A_off: 0.00, 0.00, 0.00
A_scale: 1.00, 1.00, 1.00
Ready to FLY APM: PreArm: RC not calibrated
APM: ArduCopter V3.2 (c8e0f3e1)
APM: PX4: dea2cfd1 NuttX: 7a62e351
APM: Frame: QUAD
APM: PX4v2 002A002D 35324706 36343032
Received 417 parameters
Saved 417 parameters to copter/logs/2015-01-30/flight1/mav.parm
STABILIZE> Mode STABILIZE
APM: PreArm: RC not calibrated
However using same setup and but over tcp/udp I used the following command:
python mavproxy.py --aircraft=copter --quadcopter --master=192.168.1.77:14550
It gave me strange continous output and thus communication instability. Has anyone seen this before? Some kind of setup problem?
python mavproxy.py --aircraft=copter --quadcopter --master=192.168.1.77:14550
copter/logs/2015-01-29/flight53
Logging to copter/logs/2015-01-29/flight53/flight.log
MAV> APM: ArduCopter V3.2 (c8e0f3e1)
APM: PX4: dea2cfd1 NuttX: 7a62e351
APM: Frame: QUAD
APM: PX4v2 002A002D 35324706 36343032
LD2u?THR_ACCEL_I jECuBATT_CURR_PINs{3STABILIZE> Mode STABILIZE
< A4~221M75z1 z3) 13&.sU|1|37?}1|}2+ no heartbeat
link 1 down
1u2@|1Nz2y18Ky1^|1]w2|1D~1 40XA~2cno heartbeat
~3{~2$d~1l]3,|1w%y2%x1Hz09KC7I|1h}4o}1 v~3{1no heartbeat
fetching parameters
}3Z~1NESC>o`wWPNAV_SPEED_UP =`no heartbeat
no heartbeat{zz1]w1ow0lq357(x3z3z20`
Replies