Closed pan-sattan closed 3 years ago
I have a similar issue. Baud detection works, but no mavlink detection (Mavlink 1/2, 115k/57k)
Hello, I'm 'not a Betaflight user but I have some questions
all infos are there... latest betaflight, fport, access protocol, latest opentx... I am able to decode s.port from R9m with another arduino and code... but want to uae this one for tracker
Hi Guys,
Merci d'être venu Marius.
I will look at this today. One thing you have not given me is firmware version number.
Remember f.port is 115200 b/s.
firmware of betaflight is 4.2.2 I checked it right now... or do you mean another firmware? opentx 2.3.9, R9m flex firmware ACSST 20190117, R9mm flex fport 20190201 sorry I have hare two modules, but using this one
and if I use bluetooth mod for my R9m together with app telemetry viewer, it works normally. My HC-05 is set to baud 57600, even that works with arduino decoder from Pawelsky
No, I meant AntTrack version number. So are you using Mavlink, and serial or BT
I've tried several of the newer versions. Mavlink on serial.
I used v2.15.4 and frsky protocol, serial input Now I tried v2.15.5 and it moves on! I will keep testing...
Oops, it's my bad!
I added frInvert for FrSky telemetry input (for mello73), but left it so it is also inverting Mavlink telemetry.
Please, in the meantime, go to your ESP32 variant setup, and change frInvert line like this:
bool frInvert = false; // DON'T INVERT FOR MAVLINK
I am about to publish a new version, with FrSky UDP input and a few other improvements. I will fix this issue there.
Sorry for the inconvenience. No excuses for this!
I am glad, that I can test it, or help you in development... I change it and thats the result:
Yeah, it looks correct now. Thanks for the feedback.
Now maybe activate these macros to see some telemetry:
#define Debug_Mav_Heartbeat
#define Debug_Mav_GPS
I tried, but it stops with Mavlink 2 found... nothing else is comming
could be the betaflight issue? or maybe non GPS signal in my flat
I'm not sure what protocol Betaflight outputs these days
I think the same like INAV
this works for me with decoder from Pawelsky
Can your fc connect to a Mission Planner. I'm afraid I don't know Pavelka. Can you post a link?
I will try later mission planner.
I am not able to connect my FC in MP
Could you do some research and find out which protocol you are using.
its Frsky protocol
Ok pan-sattan, we should be able to solve this. I just tested FrSky S.Port again and it works here, but now I see above you mention F.Port. I have not added F.Port support yet.
ok, is there something what I can do or help you somehow?
Thanks for offering, but I already have written the F.Port code for other projects. I just need to adapt it here.
@pan-sattan:
From your images I can't see where you pick up the F.Port telemetry. Could you show me were your wiring brings in the P.Port FrSky telemetry, I don't have a fport R9M, mine is S.Port.
But I just ordered one. It will take about a week to come I think. I have wanted to try the new R9M/R9 mini OTA for a while now. :)
source for esp32 is here: from top s.port,+5V,GND
ok, got it. Thanks.
On Sun, 28 Feb 2021, 09:09 pan-sattan, notifications@github.com wrote:
source for esp32 is here: from top s.port,+5V,GND
[image: 20210228_080452] https://user-images.githubusercontent.com/59567959/109410600-41c1a180-799c-11eb-8220-3a096d646ddc.jpg
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/zs6buj/AntTracker/issues/30#issuecomment-787407410, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCLS5PNDXKBCZTZYODRACDTBHT3FANCNFSM4YGXHUCQ .
I have posted a Beta of V2.16.1 which adds support for F.Port (1 & 2).
I can only test it properly once I get me new ACCESS Rm9/R9
Thanks. I see you activated some of the debugging. Try only this one:
Make sure your flight computer is powered up, and it would be good if your GPS could see the sky without obstruction.
I was able to debug S.Port.
Please could you try V2.16.2 (Beta). You should get something like this:
Starting AntTrack_F version:2.16.02
Display support activated: Landscape
version:2.16.02
Target Board is ESP32 / Variant is LILYGO® TTGO T-Display ESP32 1.14 inch ST7789 Colour LCD
Mavlink Serial In
Heading_Source = Flight Computer
Serial port rx pin 13 is IDLE_LOW, inverting rx polarity
AutoBaud - sensing rxPin 13
Baud rate detected is 57600 b/s
FrSky S.Port found
FrSky read good!
FrSky 0x5004 Dist to home=0.0 Rel Alt=30.0
Passthru dialect detected
FrSky 0x5002 Num sats=12 gpsStatus=3 HDOP=8 gpsAlt=15.2 hdopGood=1 neg=0
FrSky 0x800 latitude=-25.9462109
FrSky 0x800 longitude=28.0435505
FrSky 0x5005 Heading=129.2
FrSky 0x5004 Dist to home=0.0 Rel Alt=30.0
FrSky 0x5002 Num sats=12 gpsStatus=3 HDOP=8 gpsAlt=15.2 hdopGood=1 neg=0
FrSky 0x800 latitude=-25.9462109
GPS good
GPS lock good! Push set-home button anytime to start tracking.
yes, its finally work, I am able to see Heading, which is moving...
anyone can help me?
I am using:
betaflight + fport R9mm
X9D + R9M ACCESS - S.PORT + GND pins used
esp32 dev board
define ESP32_Variant 1
OLED display GND, 5V, SDA - PIN 21, SCL - PIN 22
define Display_Support
define SSD1306_Display
Serial port on PIN27, GND
define Telemetry_In 0
GY-271 GND, 5LV, SDA - PIN 21, SCL - PIN 22
const uint8_t Heading_Source = 2;
nothing else is connected or changed in config...
oled display is working, but in debug I can see that no telemetry is going inside... I tried inverter and the same... on the screen is that telemetry is not going into esp32 board
Any idea what should be wrong? could be, that I dont have in my flat any gps sats found? zero values comes from taranis..
Is there any possibility to switch in config FAKE VALUES?