Comments (20)
zs6buj
commented on August 30, 2024
Hi lipk888
From what I can see your settings should work. So we expect your crossfire access point to send udp packets to 192.168.4.101 port 14550. Maybe try to connect on your phone or tablet. Download and install UDP Monitor, and try to connect and see what you get.
from anttracker.
lipk888
commented on August 30, 2024
Hi Zs6buj:
thanks for feedback,
yes i try to found mavlink output from my crossfire TX V2.
seems no mavlink massage out put from TX V2, only wifi can connect, i try both PC Qgroundcontrol or use UDP monitor. but failed for both.
so for now i just feedback this issue for TBS team hope they have feedback.
from anttracker.
kamik2
commented on August 30, 2024
there are 3 thing you need to do:
- (also 1. bug) you need to enable the mavlink option in the crossfire wifi/ udp settings every time you power up the transmitter
- (bug 2) atm the wifi fw needs to be connected to a acces point in order to send the data
- the standard port in the crossfire is 8888. you can change it to any other port you like in the wifi/ udp setings as well
both issues are adressed on the crossfire side
from anttracker.
lipk888
commented on August 30, 2024
there are 3 thing you need to do:
- (also 1. bug) you need to enable the mavlink option in the crossfire wifi/ udp settings every time you power up the transmitter
- (bug 2) atm the wifi fw needs to be connected to a acces point in order to send the data
- the standard port in the crossfire is 8888. you can change it to any other port you like in the wifi/ udp setings as well
both issues are adressed on the crossfire side
hi Kamik2:
thanks for you feedback.
- yes i checked this issue on crossfire manual it notice known bug for your mention
- you mean ATT(ESP32) need set to AP mode, then crossfire connect to ESP32 AP?
- I try change crossfire port to 14550, then ATT with STA mode connect, still not work
from anttracker.
kamik2
commented on August 30, 2024
i meant that you nee to connec the crossfire to a AP and the trcker as well (not sure if the last one is possible?) - otherwise the crossfire does not start to send mav packages.
from anttracker.
lipk888
commented on August 30, 2024
i meant that you nee to connec the crossfire to a AP and the trcker as well (not sure if the last one is possible?) - otherwise the crossfire does not start to send mav packages.
hi Kamik2:
ok, i will try later, so seems i need 3th wifi AP, both crossfire and ATT link to this 3th AP right?
from anttracker.
kamik2
commented on August 30, 2024
correct
from anttracker.
lipk888
commented on August 30, 2024
hi team:
finally i set mavlink output from crossfire TX V2, seems crossfire have some bugs as kamik2 said. crossfire need link to 3th AP then it can send out mavlink massage and then ATT link to crossfire's AP
now i face other issue, ATT feedback heartbeat good and i checked my X9D screen and INVA both show 3D fixed.
but i wait 5 mins LED still with slowly flash.OLED screen no massage feedback GPS lock as ATT notice say slowly LED means mavlink ok, fast LED means GPS lock.
so i'm not sure what i mistake or what i missing?
from anttracker.
zs6buj
commented on August 30, 2024
You could try
#define Debug_Mav_GPS
in config.h
This should show you GPS information coming in from Mavlink
from anttracker.
lipk888
commented on August 30, 2024
You could try
#define Debug_Mav_GPSin config.h
This should show you GPS information coming in from Mavlink
hi Zs6buj:
thanks for quickly reply.
i try to follow beow set, but still no massage back. and no GPS massage back is any mistake i do
from anttracker.
zs6buj
commented on August 30, 2024
lipk888
What is coming out the serial monitor?
from anttracker.
lipk888
commented on August 30, 2024
hi zs6buj:
i get log below, it seems no GPS massage feedback
16:14:51.095 -> Starting up......
16:14:51.162 -> Target Board is ESP32 Dev Module
16:14:51.195 -> Mavlink WiFi In
16:14:51.229 -> Az = 90.00 El = 0.00 hmHdg = 90.00
16:14:51.229 -> pntAz = 90 El = 0.00 LastGoodpntAz = 90 LastGoodEl = 0 hmHdg = 90.00 azPWM = 1500 elPWM = 2300
16:14:51.229 -> Heading_Source = Tracker's Own Compass
16:14:51.263 -> ----- Compass Found -----
16:14:51.263 -> Sensor: HMC5883
16:14:51.263 -> Driver Ver: 1
16:14:51.263 -> Unique ID: 12345
16:14:51.263 -> Max Value: 800.00 uT
16:14:51.263 -> Min Value: -800.00 uT
16:14:51.263 -> Resolution: 0.20 uT
16:14:51.297 -> --------------------------
16:14:51.297 ->
16:14:51.297 -> Display tracker heading for 20 seconds
16:14:51.297 -> Heading = 276
16:14:52.279 -> Heading = 276
16:14:53.293 -> Heading = 276
16:14:54.279 -> Heading = 275
16:14:55.266 -> Heading = 276
16:14:56.280 -> Heading = 276
16:14:57.295 -> Heading = 276
16:14:58.270 -> Heading = 276
16:14:59.281 -> Heading = 276
16:15:00.290 -> Heading = 276
16:15:01.269 -> Heading = 276
16:15:02.279 -> Heading = 276
16:15:03.294 -> Heading = 276
16:15:04.272 -> Heading = 276
16:15:05.284 -> Heading = 275
16:15:06.302 -> Heading = 276
16:15:07.309 -> Heading = 276
16:15:08.289 -> Heading = 275
16:15:09.303 -> Heading = 276
16:15:10.283 -> Heading = 276
16:15:11.292 -> Trying to connect to tbs_crossfire_D8BFC0FE921E.
16:15:12.908 -> WiFi connected!
16:15:12.908 -> Local IP address: 192.168.4.100
16:15:12.908 -> WiFi RSSI:-51 dBm
16:15:12.943 -> UDP started, listening on IP 192.168.4.100, UDP port 8800
16:15:15.032 -> Client connected: Remote UDP IP: 192.168.4.1 Remote UDP port: 8800
16:15:15.336 -> UDP WiFi record read:
16:15:15.336 -> 04 FE 09 3E 01 FA 00 05 00 00 00 01 00 51 03 03 DE 04
16:15:15.370 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
16:15:15.370 -> hb_count=1
16:15:15.370 -> UDP WiFi record read:
16:15:15.370 -> EC FE 09 58 01 FA 00 05 00 00 00 01 00 51 03 03 63 EC
16:15:15.370 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
16:15:15.370 -> hb_count=2
16:15:15.606 -> UDP WiFi record read:
16:15:15.606 -> 5B FE 09 72 01 FA 00 05 00 00 00 01 00 51 03 03 6B 5B
16:15:15.606 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
16:15:15.641 -> hb_count=3
16:15:15.641 -> hbGood=true
16:15:16.010 -> UDP WiFi record read:
16:15:16.044 -> 47 FE 09 7E 01 FA 00 05 00 00 00 01 00 51 03 03 B1 47
16:15:16.044 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
16:15:16.753 -> UDP WiFi record read:
16:15:16.753 -> 7C FE 09 8B 01 FA 00 05 00 00 00 01 00 51 03 03 3B 7C
16:15:16.753 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
16:15:18.475 -> UDP WiFi record read:
16:15:18.475 -> 82 FE 09 BE 01 FA 00 05 00 00 00 01 00 51 03 03 00 82
16:15:18.475 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
16:15:19.725 -> UDP WiFi record read:
16:15:19.725 -> F5 FE 09 D7 01 FA 00 05 00 00 00 01 00 51 03 03 59 F5
16:15:19.725 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
16:15:22.154 -> UDP WiFi record read:
16:15:22.189 -> 84 FE 09 0A 01 FA 00 05 00 00 00 01 00 51 03 03 0F 84
16:15:22.189 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
16:15:24.719 -> UDP WiFi record read:
16:15:24.719 -> 44 FE 09 49 01 FA 00 05 00 00 00 01 00 51 03 03 5E 44
16:15:24.755 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
16:15:25.767 -> UDP WiFi record read:
16:15:25.767 -> 0D FE 09 56 01 FA 00 05 00 00 00 01 00 51 03 03 6D 0D
16:15:25.767 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3
ap_mavlink_version=3
from anttracker.
lipk888
commented on August 30, 2024
hi zs6buj:
i get log below, it seems no GPS massage feedback
16:14:51.095 -> Starting up......
16:14:51.162 -> Target Board is ESP32 Dev Module
16:14:51.195 -> Mavlink WiFi In
16:14:51.229 -> Az = 90.00 El = 0.00 hmHdg = 90.00
16:14:51.229 -> pntAz = 90 El = 0.00 LastGoodpntAz = 90 LastGoodEl = 0 hmHdg = 90.00 azPWM = 1500 elPWM = 2300
16:14:51.229 -> Heading_Source = Tracker's Own Compass
16:14:51.263 -> ----- Compass Found -----
16:14:51.263 -> Sensor: HMC5883
16:14:51.263 -> Driver Ver: 1
16:14:51.263 -> Unique ID: 12345
16:14:51.263 -> Max Value: 800.00 uT
16:14:51.263 -> Min Value: -800.00 uT
16:14:51.263 -> Resolution: 0.20 uT
16:14:51.297 -> --------------------------
16:14:51.297 ->
16:14:51.297 -> Display tracker heading for 20 seconds
16:14:51.297 -> Heading = 276
16:14:52.279 -> Heading = 276
16:14:53.293 -> Heading = 276
16:14:54.279 -> Heading = 275
16:14:55.266 -> Heading = 276
16:14:56.280 -> Heading = 276
16:14:57.295 -> Heading = 276
16:14:58.270 -> Heading = 276
16:14:59.281 -> Heading = 276
16:15:00.290 -> Heading = 276
16:15:01.269 -> Heading = 276
16:15:02.279 -> Heading = 276
16:15:03.294 -> Heading = 276
16:15:04.272 -> Heading = 276
16:15:05.284 -> Heading = 275
16:15:06.302 -> Heading = 276
16:15:07.309 -> Heading = 276
16:15:08.289 -> Heading = 275
16:15:09.303 -> Heading = 276
16:15:10.283 -> Heading = 276
16:15:11.292 -> Trying to connect to tbs_crossfire_D8BFC0FE921E.
16:15:12.908 -> WiFi connected!
16:15:12.908 -> Local IP address: 192.168.4.100
16:15:12.908 -> WiFi RSSI:-51 dBm
16:15:12.943 -> UDP started, listening on IP 192.168.4.100, UDP port 8800
16:15:15.032 -> Client connected: Remote UDP IP: 192.168.4.1 Remote UDP port: 8800
16:15:15.336 -> UDP WiFi record read:
16:15:15.336 -> 04 FE 09 3E 01 FA 00 05 00 00 00 01 00 51 03 03 DE 04
16:15:15.370 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
16:15:15.370 -> hb_count=1
16:15:15.370 -> UDP WiFi record read:
16:15:15.370 -> EC FE 09 58 01 FA 00 05 00 00 00 01 00 51 03 03 63 EC
16:15:15.370 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
16:15:15.370 -> hb_count=2
16:15:15.606 -> UDP WiFi record read:
16:15:15.606 -> 5B FE 09 72 01 FA 00 05 00 00 00 01 00 51 03 03 6B 5B
16:15:15.606 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
16:15:15.641 -> hb_count=3
16:15:15.641 -> hbGood=true
16:15:16.010 -> UDP WiFi record read:
16:15:16.044 -> 47 FE 09 7E 01 FA 00 05 00 00 00 01 00 51 03 03 B1 47
16:15:16.044 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
16:15:16.753 -> UDP WiFi record read:
16:15:16.753 -> 7C FE 09 8B 01 FA 00 05 00 00 00 01 00 51 03 03 3B 7C
16:15:16.753 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
16:15:18.475 -> UDP WiFi record read:
16:15:18.475 -> 82 FE 09 BE 01 FA 00 05 00 00 00 01 00 51 03 03 00 82
16:15:18.475 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
16:15:19.725 -> UDP WiFi record read:
16:15:19.725 -> F5 FE 09 D7 01 FA 00 05 00 00 00 01 00 51 03 03 59 F5
16:15:19.725 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
16:15:22.154 -> UDP WiFi record read:
16:15:22.189 -> 84 FE 09 0A 01 FA 00 05 00 00 00 01 00 51 03 03 0F 84
16:15:22.189 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
16:15:24.719 -> UDP WiFi record read:
16:15:24.719 -> 44 FE 09 49 01 FA 00 05 00 00 00 01 00 51 03 03 5E 44
16:15:24.755 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
16:15:25.767 -> UDP WiFi record read:
16:15:25.767 -> 0D FE 09 56 01 FA 00 05 00 00 00 01 00 51 03 03 6D 0D
16:15:25.767 -> Mavlink in #0 Heartbeat: ap_type=1 ap_autopilot=0 ap_base_mode=81 ap_custom_mode=5 ap_system_status=3ap_mavlink_version=3
from anttracker.
lipk888
commented on August 30, 2024
sorry for mis opration for close issue.....i just reopen it ......sorry.
i just check debug mode, seems even i set GPS debug it only can output heartbeat debug
from anttracker.
zs6buj
commented on August 30, 2024
Could you comment out all debugs except the GPS debug and run it again, but longer. Remember your GPS must have clear access to the sky. :)
from anttracker.
lipk888
commented on August 30, 2024
Hi zs6buj:
i try set below , but still only have #0 massage out
not sure if it means have mavlink massage out or not
log.txt
from anttracker.
zs6buj
commented on August 30, 2024
Yes, it looks like you are getting only heartbeats down from crossfire
from anttracker.
lipk888
commented on August 30, 2024
Hi zs6buj:
today i have try other way to make sure mavlink massage send out from INAV and i confirm massage send out from INAV.
i just change crossfire Nano output from
(CRFS+MAVLINK-->CH1/2 for CRSF CH3/4 for mavlink ) to (SBUS+MAVLINK CH1--> SBUS CH3/4--> MAVLINK),
due to SBUS only output massage for RC and mavlink.
so for result, i still only can get #0 heartbeat massage and no GPS, but on transmitter if show GPS location.
from anttracker.
lipk888
commented on August 30, 2024
HI Zs6buj:
i just change code below to "GCS_Mavlink.h", so i'm sure this why i only get #0 heartbeat?
from anttracker.
lipk888
commented on August 30, 2024
Hi Zs6buj:
finally i did it, all system run good base on V2.15.
from anttracker.
Related Issues (20)
- Error installing on stm32 blue pill HOT 8
- compiling error HOT 5
- Problems with push button HOT 12
- GPIO output gpio_num error HOT 2
- Blackpill F411 HOT 2
- Problems using LTM protocol HOT 4
- tracker display HOT 3
- Help getting serial telemetry on bluepill board HOT 6
- ESP32 Dev Module - Help HOT 8
- Missing Library QMC5883LCompass HOT 1
- Esp32 with Bluetooth telemetry HOT 60
- Compass flip not working HOT 10
- Feature Request - Accelerometer input for mag tilt compensation HOT 4
- Altitude calculations not working in headingsource = 4 for 2.20.04 HOT 3
- Continuous Rotation Servo 360 HOT 1
- esp32 dev module telemetry_in via serial HOT 7
- Feature request. Servo slowdown with no delay HOT 6
- T-Display ESP32 1.14" - Problems HOT 10
- Bluetooth ble support HOT 89
- Alpha 21.21.09 wont compile HOT 11
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from anttracker.