I tried with Python 3.6, which is not working well
so I changed to Python 2 and it output no error
do you have any comment?
and i want to send the distance data via mavlink
am I correct to set the connection to "udpout:192.168.2.1:14450"?
master = mavutil.mavlink_connection('udpout:192.168.2.1:14450')
wait_conn(master)
master.mav.param_set_send(
1,
1,
"RNGFND_TYPE",
10, # "MAVLink"
mavutil.mavlink.MAV_PARAM_TYPE_INT8)
min = 10 # minimum valid measurement that the autopilot should use
max = 40 # maximum valid measurement that the autopilot should use
distance = 20 # You will need to supply the distance measurement
type = mavutil.mavlink.MAV_DISTANCE_SENSOR_UNKNOWN
id = 1
orientation = mavutil.mavlink.MAV_SENSOR_ROTATION_PITCH_270 # downward facing
covariance = 0
tstart = time.time()
print('Mavlink connected...')
while True:
time.sleep(0.5)
master.mav.distance_sensor_send(
(time.time() - tstart) * 1000,
min,
max,
distance,
type,
id,
orientation,
covariance)
print(".")
am I correct to set the connection to "udpout:192.168.2.1:14450"?
@TunaLobster We don't really currently do alternate vehicle models with autotest. I've been considering on and off adding it. One reason it's not helpful for the autotest suite so much is that the flight dynamics may be different enough that the autotests don't pass! For someone constructing their own tests it is probably feasible.
You could play around with it - it's the
--frame parameter, and it does work for different types of multi frame, for example.
@techsolution123 You can also create aliases to move forward with your SITL testing faster (I often make one-letter aliases to make it faster....). You can also create mavproxy modules to help out.
I have QGC app which shows the pi camera video with instrument panel of ardupilot
It seems there are some unused sensor values, so I want to use them to show another custom sensor values I installed on the vehicle, which are contact sensors
I have to show 2~3 sensor values, and I succeeded in showing 1 value on the MAV_DISTANCE_SENSOR
but still wondering which sensor values I can use.
If you have any experiences or suggestions, please let me know
I've no idea if QGC supports such a view
(checked - it doesn't know anything about obstacle_distance)
I am having trouble connecting my Arducopter to a dronekit sitl instance.
the error is link timeout due to no heartbeat
the source of the error is a function named
vehicle = connect(connection_string,wait_ready=True)
so is this due to my mavlink version?
the error is link timeout due to no heartbeat
the source of the error is a function named
vehicle = connect(connection_string,wait_ready=True)
so is this due to my mavlink version?
I have a bash code called launchSitl which is establishing link with qgc mavproxy and sitl
I have a a python script which is using drone kit
I'm using pymavlink to convert binary files to json. When I print out the lines of my json before writing them to the file, everything looks as I would expect. However, the file seems to have some sort of encoding issue and is unusable. Does anyone know what encoding it could be using? I know that it's not ASCII or UTF-8. Any suggestions on how to change how I'm writing to the file?
` if args.format == 'json':
` if args.format == 'json':
# Format our message as a Python dict, which gets us almost to
# proper JSON format
data = m.to_dict()
# Remove the mavpackettype value as we specify that later.
del data['mavpackettype']
# Also, if it's a BAD_DATA message, make it JSON-compatible by
# removing array objects
if 'data' in data and type(data['data']) is not dict:
data['data'] = list(data['data'])
# Prepare the message as a single object with 'meta' and 'data'
# keys holding the message's metadata and actual data respectively.
meta = {"type": m.get_type(), "timestamp": timestamp}
if args.show_source:
meta["srcSystem"] = m.get_srcSystem()
meta["srcComponent"] = m.get_srcComponent()
outMsg = {"meta": meta, "data": data}
# Now print out this object with stringified properly.
print(json.dumps(outMsg) + '\n')
if json_output is not None:
json_output.write((json.dumps(outMsg) + '\n'))`
@peterbarker This is my version of mavlogdump.py - the workflow this is part of needs a specific type of JSON that the default mavlogdump won't do. json_output is a file, created as
json_output = open(os.path.join(args.json_out_dir, dt.strftime("%Y%m%d_%H%M_{}.json".format(args.log.split('/')[-1].split('.')[0]))), mode='w')
I've just knocked up a quick hack based on your snippets here and it appears to work as intended.
@JessicaBlunt
#!/usr/bin/python
import json
from pymavlink import mavutil
fh = open("/tmp/out.json", mode='w')
mlog = mavutil.mavlink_connection("/home/pbarker/rc/flight-data/bixler/logs/2017-10-29/flight4/flight.tlog")
while True:
m = mlog.recv_match()
data = m.to_dict()
del data['mavpackettype']
if 'data' in data and type(data['data']) is not dict:
data['data'] = list(data['data'])
timestamp = 16
meta = {"type": m.get_type(), "timestamp": timestamp}
if False:
meta["srcSystem"] = m.get_srcSystem()
meta["srcComponent"] = m.get_srcComponent()
outMsg = {"meta": meta, "data": data}
print(json.dumps(outMsg) + '\n')
fh.write((json.dumps(outMsg) + '\n'))
fh.close()
@meher1087 Not really sure what you're after there. Does cleanflight itself do mavlink?