Hi,
Beta3 loaded.
now says 1.9.3-beta3 in message box.
Flew 10min did not crash. I mean widget did not crash.
Before logs were being created in logs dir.
Now during flying no plog log created.
for info
If I open the Yaapu Dbug tool there is lines 5000:0 to 50009:0
Then at the bottom a *.plog.
Now when checking logs dir I have the same named .plog
So I will do some more flying later, but I believe it is now working well, I am all ways in mode2 at around 155HZ .
I think you need to use a serial that has DMA on the H743. I am using
serial3 for rcin, any comments ???. Just going to look at hardware def.
@yaapu, what is a good data rate here? Is there a way to adjust that? On the bench mine stayed in Mode 2, but I donāt think the data rate was that high. I seem to think it was under 100hz. (foggy memory so donāt hold me to that number)
my testing shows around 70Hz for non DMA UARTS, and 150Hz+ for DMA enabled UARTS.
For regular crossfire (no tracer) seems to work fine even at 70Hz on non DMA UARTS.
I tuned the passthrough rate to work fine at 70Hz, the only issue is that parameters from lua scripts do not work as smooth or at all when @70Hz.
Hello All.
Loaded beta4 ā for info says beta 3 in messages
Have now done 1 hour flying all working as expected.
Tried mapping screen. Switching to screen using page button or emulated page switch zooming in and out works fine.
Which physical TX and RX pins do you have the CRSF TX and RX connected to? Assuming it is UART1 since you have serial 1 configured for the RCRX. But do you have both the rx and tx connected and are you positive you have RX->TX and TX->RX? I had a silly problem at one point with confusing the pin order on the CSRF RX, because 1 and 2 were not in a sensible order. And the CSRF receiver can be configured to put just about whatever signal you want to whatever pin you want so thatās where I would start checking. Also if you have the mavlink tx and rx set up separately, and you have āRC over mavlinkā selected, then your RC control might be happening over the mavlink serial connections rather than the CSRF connections (if you pull the CSRF completely, does the transmitter still talk to the RCRX?). If so, then you might accidentally think that the CSRF tx and rx is working when itās not at all.
sensors show up under telemetry sensors. But the Yaapu widget 1.9.3 beta 3 says āno telemetry dataā. The gps position is the only data that shows up on the widget, despite the widget saying āno gpsā
I am using:
Matek h743 wing with 4.10 dev firmware
TX16s with 2.3.11 firmware
Have my receiver on serial1 set to protocol 23 and serial1 options set to 256
When I run Yaapu debug, 5000 to 5009 = 0
Any clues to what I might be doing wrong? It sounded like others have had success with Tracer telemetry.
Having NO RC Receiver messages in telemetry message window. Bit worrying
setup
TBS MicroTX nano RX ver 4.08
opentx Jumper t16 2.3.11
arduplane 4.1
commit 3c3db5084353cde2ebaa1c2f21d30584b3886682
Author: Peter Barker pbarker@barker.dropbear.id.au
Date: Mon Feb 8 09:50:18 2021 +1100
Vagrant: augment bash when working in a git repository
This .bashrc_git originally came from tridge.
APMVERSION: ArduPlane V4.1.0dev
Telemetry Yaapu Beta4
Matek F765 Wing
USART1 SERIAL2 has DMA rcin(23) average 142 hz
Telemetry messages window only on mode change to 2.
CRSF: RFMODE 2, rate is say around 157HZ
CRT No RC RECEIVER (red)
Happens armed and disarmed.
I have not been able to find an explanation for the reason of this message
NO: No RC receiver messages in mission planner messages or logs.
No failsafe
still the same with THR_FAILSAFE = 0
I had an amazing experience
Pixracer and f405wing finally succeeded with firmware made by Yaapu
However, the cuav pixhack v3 that I have does not work because it is not the firmware provided by Yappu.
Do other FC need Yappuās firmware to work?
Because I was just doing some testing in the garage I just reset everything and there was no other problems. I did a number of short flights and resets and didnāt have any other trouble (with the script anyhow, donāt ask about the compassā¦)
mhmm, which version?
Can you check if you have any log files in the /LOGS/ folder on the sdcard?
Please update to beta4, beta3 had an extra debug option enabled that logged telemetry to file which can lead to the above issue.
Thank you for your reply
Iāll wait for Yappu to build it
May I ask you one more question?
What does n mean for n + 256 in rc_option?
Please forgive my ignorance
Hi,
support for CRSF custom telemetry has been merged into master and can be downloaded for all supported boards from ardupilot download server choosing ālatestā.
RC_OPTIONS += 256 means: add 256 to your current RC_OPTIONS value
I havenāt noticed any mode switching, it seems to be staying in mode 2. I am getting some low rates though, Iāve seen Mode 2 rates as low as 36Hz.
Yes, I have CRSF and Mavlink running, with two pairs of connections.
I just downloaded Beta4 off Github but when I started my radio it says Iām still on Beta3. I copied all the files from the zip directory, and everything was dated Feb 11 2021. Did I mess up somewhere?
