Skip to content
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

Rssi on top bar #1824

Closed
janky69 opened this issue Oct 28, 2016 · 11 comments
Closed

Rssi on top bar #1824

janky69 opened this issue Oct 28, 2016 · 11 comments

Comments

@janky69
Copy link

janky69 commented Oct 28, 2016

Hi, i have "-" in rssi value in top bar and the speach say "zero" dbm. Its problem only for me? Thank you!

@guiseco
Copy link
Contributor

guiseco commented Oct 28, 2016

same to me.

@janky69
Copy link
Author

janky69 commented Oct 28, 2016

I mean, it was previously value of mavlink radio signal and some bars in
phone signal strange style... But i am not sure...

Dne pátek 28. října 2016 Guilherme S. Blanco [email protected]
napsal(a):

same to me.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1824 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQMV2Zx8qHm6C3DpGxtjShxpyGY_tJQGks5q4jq5gaJpZM4KjmVx
.

S přáním všeho dobrého Jiří Janka

@trip5ter
Copy link

trip5ter commented Nov 1, 2016

I have the Same issue, seems to be a problem with Tower 3 and tower 4.0.0 and the latest 4.0.0-beta.9, when i use droid planner 2 RSSI information from the SiK radios is displayed correctly.

Additionally, when I first installed Tower 3 from Google Play Store RSSI information was displayed, it was only after an update of Tower that the rssi was lost....

@mariansoban
Copy link

mariansoban commented Nov 7, 2016

I'm not quite sure, but - couldn't this be the issue?
Radio status message is injected to Mavlink communication directly in telemetry radio.
Telemetry radios send their system/component ID like:
https://github.com/ArduPilot/SiK/blob/master/Firmware/radio/mavlink.c#L47-L49
// use '3D' for 3DRadio
#define RADIO_SOURCE_SYSTEM '3'
#define RADIO_SOURCE_COMPONENT 'D'

There was a change in Dronekit for Android lib, there are new conditions in GenericMavLinkDrone.onMavLinkMessageReceived() and ArduPilot.onMavLinkMessageReceived():
public void onMavLinkMessageReceived(MAVLinkMessage message) {
if (message.sysid != this.getSysid()) {
// Reject Messages that are not for the system id

https://github.com/dronekit/dronekit-android/blob/develop/ClientLib/src/main/java/org/droidplanner/services/android/impl/core/drone/autopilot/apm/ArduPilot.java#L389
https://github.com/dronekit/dronekit-android/blob/develop/ClientLib/src/main/java/org/droidplanner/services/android/impl/core/drone/autopilot/generic/GenericMavLinkDrone.java#L578

@guiseco
Copy link
Contributor

guiseco commented Nov 7, 2016

I can not test in the simulator (dronekit-sitl). Apparently the simulator does not deliver that data.

@billbonney
Copy link
Member

I had the same issue in APM Planner. I can put in. PR to fix.

@mariansoban
Copy link

mariansoban commented Nov 7, 2016

Now I'm convinced, that the issue is the one I wrote before because of this:
https://github.com/dronekit/dronekit-android/blob/develop/ClientLib/src/main/java/org/droidplanner/services/android/impl/core/drone/autopilot/generic/GenericMavLinkDrone.java#L240-L243
public short getSysid() {
return heartbeat.getSysid();
In other words, system ID to compare is taken from heartbeat packet - this value should be '1', which is system ID of vehicle.
Telemetry radio sets system ID to '3' for radio status packet and this packet is later filtered in Tower on those lines in onMavLinkMessageReceived() method.

@guiseco
Copy link
Contributor

guiseco commented Nov 7, 2016

Nice catch !

Em 7 de nov de 2016 1:19 PM, "mariansoban" [email protected]
escreveu:

Now I'm convinced, that the issue is the one I wrote before because of
this:
https://github.com/dronekit/dronekit-android/blob/develop/
ClientLib/src/main/java/org/droidplanner/services/android/
impl/core/drone/autopilot/generic/GenericMavLinkDrone.java#L240-L243
public short getSysid() {
return heartbeat.getSysid();
In other words, component ID to compare is taken from heartbeat packet -
this value should be '1', which is component ID of vehicle.
Telemetry radio sets component ID to '3' for radio status packet and this
packet is later filtered in Tower on those lines in
onMavLinkMessageReceived() method.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#1824 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK5WeAqFX44cbotTTUZu5ghRTvZ3dhXaks5q70FrgaJpZM4KjmVx
.

@guiseco
Copy link
Contributor

guiseco commented Nov 11, 2016

@ne0fhyk Are you alive ?

@m4gr3d
Copy link
Member

m4gr3d commented Nov 15, 2016

@guiseco yes :) . I've just been very busy for the past couple months with getting the YouTube VR app out.
I'll review the pr that's out to fix the issue.

@m4gr3d
Copy link
Member

m4gr3d commented Nov 15, 2016

Closing this issue at it's being addressed in dronekit/dronekit-android#462 by @billbonney.

@m4gr3d m4gr3d closed this as completed Nov 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants