@Eric-Katzfey

only 420000 work for me for CRSF RAW

hi guys ,
quick update , after a lot of testing and after we take out the IO board and still got some wobbling from the drone , we re-calibrate the f55 esc we got diffrent results from the last calibration , after updated the last resullts we did a flight test and the drone fly smoothly .

thanks for the support ,
i hope that this topic will help others
@Eric-Katzfey @Moderator @Alex-Kushleyev

@Eric-Katzfey how to start the system with crsf raw mode?
i didnt found it on the modalAi portal .
for mavlink mode i tracked open topic that says use voxl-px4 -r for mavlink...
this link : https://docs.modalai.com/voxl2-rc-configs/#crsf leading to "page not found"

thanks for the support !

@Moderator Sdk 0.9.5
Crossfire nano rx connected to j19 ,using mavlink mode.
For unknown reasons in this mode I can control the drone but a lot of mavlink massages disappear, no battery status system status almost half of the tabs in mavlink inspector on qgc are gone .

What I’m doing wrong?
Can I use csrf raw on that Sdk?or should I move to v1.0?

should I try use spectrum receiver?

@Eric-Katzfey @Alex-Kushleyev @Chad-Sweet
hi guys,
we about to build 4 more drones with same setup ( 8 total) and we have to be sure about the hardware, how can you help us to work this through?
can one of the dev team can give us support through emails? its hard to support this with one massage a day ( we have time zone problem )

@Eric-Katzfey
hi eric , i uploaded the log here (too many characters )
https://we.tl/t-36gYH3HTue
if you guys can support us through email it will be much faster .
thanks.

@Moderator hi
first of all we use it to connect RC receiver and we also need the other pwm pins for servo operate .

we tried to connect the crossfire nano directly to j19 and change the mode to mavlink (just to see how the drone perform ),

we succeed to do that only with voxl-px4 -r command that we do every restart (im guessing there is an easy way to do it if you can guide us through )
but that causes a lot of mavlink massages and status tabs like battery status and a bunch of other tabs in qgc mavlink inspector to disappear .

if there is some guidelines that i missed to work properly with crossfire receiver without IO board for now ,
that will give us a lot of space for keeping developing .

hi @Alex-Kushleyev
OK, we got a significant improvement but it comes with a lot of questions and other problems that came up .

first , i took the IO board out and connected the crossfire directly to J19 as shown at picture in the previous massage.

then i configured the receiver to work in mavlink mode and started the voxl px4 service with voxl-px4 -r

(as i founded in other topic in the forum) .

as a result we got pretty smooth flight and actuator output looks great :
https://review.px4.io/plot_app?log=dd187870-0fb2-4dc9-a0f6-694c4c3bdea2

now since we need this IO board how can we solve this problem ?

moving to work with mavliink causes a lot of missing mavlink messages and tabs in qgc mavlink inspector, but this problem should be in a new topic (i will publish later ) .

looking forward for any help/solution .

@Chad-Sweet Hi chad
we using v1.12.31 , but thanks for the heads up , our next step was moving to 1.14 and we need that board so obviously we cant use it with this version .

@Alex-Kushleyev just noticed that the other guy that opend the issue in px4 forum using ModalAi rb5 and same version as we using .
https://discuss.px4.io/t/weird-actuator-output-logs-problems-tuning/32839.