VOXL ESC FPV queries
-
Hi @Jetson-Nano, sorry i originally did not realize that you are running PX4 outside VOXL2. In this case
px4-listenerapproach will not work.However, in the case of PX4 running on flight core (v1 or v2), there is still communication between Flight Core and VOXL2.
voxl-mavlink-servershould be communicating with the Flight Core via UART and passing messages back and forth. Depending whether the forwarding of RC topic is enabled or not,voxl-mavlink-serverwould receive those messages (if enabled) and in that case they would be accessible on VOXL2.@tom , can you please elaborate on how to double check if the RC message is set up to forward to
voxl-mavlink-serverfrom Flight Core (if not, how to enable it) and how to actually read that message?Thanks!
Alex
@Alex-Kushleyev @Jetson-Nano You'll want to make sure that in
/etc/modalai/voxl-mavlink-server.confthaten_external_uart_apis set totrueOnce you restart the service you should be able to run
voxl-inspect-mavlink mavlink_offboardto view the generated messages from FC -
@Alex-Kushleyev @Jetson-Nano You'll want to make sure that in
/etc/modalai/voxl-mavlink-server.confthaten_external_uart_apis set totrueOnce you restart the service you should be able to run
voxl-inspect-mavlink mavlink_offboardto view the generated messages from FC@tom @Alex-Kushleyev thanks guys. I will check it and get back to you with the result.
-
@tom @Alex-Kushleyev thanks guys. I will check it and get back to you with the result.
@Alex-Kushleyev @tom
Guys I checked what you guys mentioned.
Theen_external_uart_apis set to True, but when I run the commandvoxl-inspect-mavlink mavlink_offboard, the terminal is showingwaiting for pipe to connectand not showing anything else.Adding to the previous point there is no mavlink_offboard showing up.
-
@Alex-Kushleyev @tom
Guys I checked what you guys mentioned.
Theen_external_uart_apis set to True, but when I run the commandvoxl-inspect-mavlink mavlink_offboard, the terminal is showingwaiting for pipe to connectand not showing anything else.Adding to the previous point there is no mavlink_offboard showing up.
@Jetson-Nano , is
voxl-mavlink-serveractually running? you can check usingvoxl-inspect-services.Also, are you sure that your Flight Core V2 is connected to
/dev/ttyHS1, which would be implied by usingautopilot_uart_bus: 1. How exactly are you connecting it to VOXL2?Alex
-
@Jetson-Nano , is
voxl-mavlink-serveractually running? you can check usingvoxl-inspect-services.Also, are you sure that your Flight Core V2 is connected to
/dev/ttyHS1, which would be implied by usingautopilot_uart_bus: 1. How exactly are you connecting it to VOXL2?Alex
@Alex-Kushleyev
yes thevoxl-mavlink-serveris running, I had checked it.I am following this documentation for FC connections.
-
@Alex-Kushleyev
yes thevoxl-mavlink-serveris running, I had checked it.I am following this documentation for FC connections.
@Jetson-Nano , can you please clarify which connector on VOXL2 is your Flight Core connected to (for uart communication) and whether you have any indication that the communication is established? Have you previously been able to connect to VOXL2 from QGC and access the Flight Core V2 while it has been connected to VOXL2?
Alex
-
@Jetson-Nano , can you please clarify which connector on VOXL2 is your Flight Core connected to (for uart communication) and whether you have any indication that the communication is established? Have you previously been able to connect to VOXL2 from QGC and access the Flight Core V2 while it has been connected to VOXL2?
Alex
@Alex-Kushleyev I currently use, VOXL2 USB 3.0 Expansion Adapter connected to VOXL2. From the UART7 port of the Expansion Adapter I have connected to 6-PIN Telemetry1 Port in Flight Core V2.
My connection is similar to this,
As you mentioned earlier, I'm establishing connection through port
/dev/ttyHS1. When I run thecatcommand to read the messages from this port, I get garbled data as below,
.I'm not exactly clear when you mean if I have tried connecting to VOXL2 from QGC and access the Flight Core V2. Few things I have tried is,
-
Connecting to FlightCore V2 by connecting to Wifi of VOXL2. I also have a Wifi setup on VOXL2, which also acts as my Telemetry line. From QGC I connect to this local network to access FC data and PX4 parameters on Flight Core V2.
-
I have tried and tested few mavlink message commads which communicate with PX4 directly for C2C.
-
-
@Alex-Kushleyev @Jetson-Nano You'll want to make sure that in
/etc/modalai/voxl-mavlink-server.confthaten_external_uart_apis set totrueOnce you restart the service you should be able to run
voxl-inspect-mavlink mavlink_offboardto view the generated messages from FC@tom As per your response on shifting to
voxl-inspect-mavlink mavlink_offboard, I see that even in mavlink server documentation from ModalAI that service pipeline is not listed. Is it that something that has to be explicitly be enabled somewhere?
Even as per the documentation, I dont see this service pipeline listed.
-
@tom As per your response on shifting to
voxl-inspect-mavlink mavlink_offboard, I see that even in mavlink server documentation from ModalAI that service pipeline is not listed. Is it that something that has to be explicitly be enabled somewhere?
Even as per the documentation, I dont see this service pipeline listed. -
@Jetson-Nano I could have the naming wrong. If you inspect
mavlink_onboardwhat kind of data do you see? -
@tom This is the output I get,
-
@Jetson-Nano Since you don't have voxl-px4 running I think that data is likely coming from your external flight controller
@tom yes, the message is coming from external flight controller, Flight core v2. Now can you share how to double check if the RC message is set up to forward to voxl-mavlink-server from Flight Core (if not, how to enable it) and how to actually read that message?
-
@tom yes, the message is coming from external flight controller, Flight core v2. Now can you share how to double check if the RC message is set up to forward to voxl-mavlink-server from Flight Core (if not, how to enable it) and how to actually read that message?
@Jetson-Nano Probably should also look at the pipe for messages from the flight controller to the GCS (Labeled mavlink_to_gcs in the above diagram but you'll have to double check that name). Generally the flight controller is configured with two mavlink streams. One is the onboard stream that has high rate messages and is intended for local use (e.g. on VOXL or VOXL 2) and the other is more the default settings for communication with a GCS. You can configure what each of these streams contain in PX4. You can add streams, change stream rates, etc. all via PX4 configuration. Please refer to the PX4 documentation for details on how to do this.
-
@Jetson-Nano Probably should also look at the pipe for messages from the flight controller to the GCS (Labeled mavlink_to_gcs in the above diagram but you'll have to double check that name). Generally the flight controller is configured with two mavlink streams. One is the onboard stream that has high rate messages and is intended for local use (e.g. on VOXL or VOXL 2) and the other is more the default settings for communication with a GCS. You can configure what each of these streams contain in PX4. You can add streams, change stream rates, etc. all via PX4 configuration. Please refer to the PX4 documentation for details on how to do this.
Hi @Eric-Katzfey, I was thinking another approach, where we can use pymavlink to get the RC_channel data. Any inputs to the mentioned approach, is it feasible?
-
Hi @Eric-Katzfey, I was thinking another approach, where we can use pymavlink to get the RC_channel data. Any inputs to the mentioned approach, is it feasible?
@Jetson-Nano Yes, that should work. You should be able to send heartbeats from a Python script using pymavlink and connect to the flight controller via voxl-mavlink-server. Then you should start receiving all the normal messages sent out by the flight controller to the GCS which should include the RC channels message.
-
@Jetson-Nano Yes, that should work. You should be able to send heartbeats from a Python script using pymavlink and connect to the flight controller via voxl-mavlink-server. Then you should start receiving all the normal messages sent out by the flight controller to the GCS which should include the RC channels message.
-
This post is deleted!
@Alex-Kushleyev can you check the above mentioned approach
-
@Alex-Kushleyev can you check the above mentioned approach
@Jetson-Nano , I am sorry, I don't have this hardware set up right now, so I can't actually test what you are trying to do. I will check with the team regarding who can test it.
Alex
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login