-
Notifications
You must be signed in to change notification settings - Fork 989
-
Notifications
You must be signed in to change notification settings - Fork 989
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PX4 connection test #68
Comments
Imu_pub sends data_raw only. Need read documentation how to configure firmware. gps: don't have compatible connector, require solder iron... param: don't respond to param request, maybe i must reset param storage? sys_status: todo: implement mode decoding. USB quirk sometime don't work, but manual start works. |
@vooon I am using release 0.6.0 as later versions with libev slowdown high-rate publishers. Please look into it. |
@mhkabir For manual init i just connect to nsh via Please add instructions how configure for that high rate. |
Okay. I have observed that if I leave the PX4 for say 15 mins or so without starting mavlink, even manual starting does not work. Minicom cannot even open NSH... You can set stream rates for ATTITUDE and HIGHRES_IMU to 200 to test highrate problem in Libev |
Still using 0.6 also, as position lock gives me a shut on connection in 0.7 (with libev). |
@mhkabir Can you send you SD card configs? |
Also waypoint plugin works (with first_pos_control_flight-5273-gd3d5aa9). Issue #68.
Testing current master (first_pos_control_flight-5273-gd3d5aa9). |
Also FW sends SYSTEM_STATUS with 0 in sensor health fields. No attitude message by default. |
Alwasy get, after running
Already checked Pixhawk params and they correspond:
|
What FW version? Todays master responds to WP correctly. With previous WP broken. |
This happens before I start GCS. Starting GCS in another cmd line, I get this in the
|
Also fix PX4 wrong ?ids usage (it set mavros ids, not target). Issue #68.
I found, that i set wrong ids pair. Now param plugin works like a charm, but WP not. |
Hmm, log indicates that WP io goes wright.
But i don't know why FCU send REJ message (maybe it rejects ACK?). QGC sends WP's (i don't connect GPS, maybe error related):
But the i request WP's in QGC:
And it works in mavros:
Log:
So i decide, that waypoint also work, in despite of FCU messages. |
Command plugin also works, when i try
But mavsafety log error, because it want confirmation ACK from FCU (but PX4 don't send it). |
Don't you have to press the safety button first so you can arm it? |
I'm getting Update: Ok I had to remove 'command' from the blacklist. I'm getting the same problem as you even though I pressed the safety button. |
Check |
I done it! It works @vooon. The problem was I didn't have the battery connected :D
|
What about takeoff and land commands? (They're related to auto mode) |
You can try it via common CommandLong. |
How to? |
Look https://pixhawk.ethz.ch/mavlink/ MAV_CMD enum. 21/22 + yaw + latlonalt. |
Ok so
Probably the best option here is tell the fcu to land in the current lat/lon, given that we are not setting up a mission but yes controlling it's behaviour. That way we don't have to send those in the cmd. |
IMU starting send data right after calibration. But ATTITUDE_QUATERNION not tested (require custom rc script). Next: implement decoding custom mode. Here i must decide style for strings, e.g. APM: "RTL", "LAND" etc, while PX4 use AUTO_RTL, AUTO_LAND... |
Also default mavlink dialect enable APM specific diag, maybe need split |
@vooon the mavlink dialect definition should be dinamic and depending on the firmware running on board read from mavros. Depending on the defines dialect, decoding of custome mode should give or a APM style or a PX4 string style. |
@TSC21 It is not possible with current implementation of mavlink. Current strings based on pymavlink utils, but it decode APM only. |
What's the default dialect in ros-*-mavlink pkg? Do we have to pymavlink\generator\mavgen.py to have pixhawk headers available also? |
ros-*-mavlink contains all dialects. Selection done by
But almost all works with common.xml. |
In Anyway, I used the process of installing from the source and did |
No, Mavlink package have all dialects, but what to use defined by |
Yes I already changed the dialect ;) |
I described in wiki... |
... And now in readme. |
Great work! :D |
GPS works, but PX4 don't send GPS time (#95). |
Btw: ATTITUDE_QUATERNION works. But i has strange slow roll CCW over X, but ATTITUDE shows same. |
All core plugins works. But still |
I've got my clone. It comes with APM:Copter 3.1.4, test connections: same as my APM2.6 (works).
Now i install current git master of PX4/Firmware.
Related #48.
The text was updated successfully, but these errors were encountered: