Posts made by bensusana

@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.

@Alex-Kushleyev the only thing comes in mind its the receiver (frsky/crossfire tried them both) working through voxl IO board ,
i was thinking to connect it directly to j19 as shown in your description .
any other ideas for testing will be much appreciate , its a major problem causing all of our developing drone grounded .

@Alex-Kushleyev hi alex
i noticed that , as you can see i added link for a similar problem from px4 forum ,
beside the frame motors and the receiver all of the components are from modalAi nothing custom ,
for fact, we have same builds with voxl1 that's working great, the only differences are modalAi esc and Io board.

i have 3 quads 2 of them with voxl2 flight-deck and have the same actuator outputs...

@bensusana one more thing , all of the F55 ModalAi esc's on our builds were fully calibrated as explained in your calibrate procedure .

Hello guys ,
I'm calling for your help after hours of tune flights that we made with voxl2 (actually 3 drones with voxl 2)
and we don't getting any good results, there is some wobbling that all of the 3 suffering from , no matter any of rate tune we tried / attitude gains that solves our problem .

we build 4th drone with same setup (frame/motors/esc) but with Kakute f7 fc with px4 and even with very bad vibration issues it flying super smoothly .

so lets go through our setups and changes that we already tried.

we are talking about 5" carbon frame ( racer frame) with voxl2 flight-deck+v2 modem , F55 ModalAi esc, voxl2 i/o board with crossfire receiver and tmotor f40 pro iv 2400kv motors with 5" tri prop hq .

after tune was pretty fine but still we getting this wobble in stabilize mode indoor flight and also outdoor in position hold.
we tried to install only voxl2 without the flight-deck and without dumpers only standoffs with thine O-rings, still nothing change same wobbling .

we tried that also with different frame and different voxl2 board and nothing change .

the third try ,we took all different frame and the vary same problem occurred, wobbling .

the 4th try ,we took same setup but only this time without voxl2 but with kakute fc with px4 and it fly's smooth as i mention above .

we have about 4 drones based on similar frame with voxl1 and the tune was very easy, pretty much nothing was change from the default and it fly's great .

here is some log file from our last try (voxl2 board attached without O-ring only board attached to standoffs ) :
https://review.px4.io/plot_app?log=35849e36-1a8a-4718-abe1-d57c9d66a964

there is some problem in the actuator outputs look like saturation that i didn't managed to solve (tried different rx/tx) can it be some false coming from the i/o board?

here is example from px4 forums: https://discuss.px4.io/t/weird-actuator-output-logs-problems-tuning/32839.

@Patrick-Hinchey
hi patrick
did you manage to solve the tune problem ?
we king of facing same problem with our drone
any help will be appreciate

hi @Eric-Katzfey
im trying to work with mRo ist8308 gps module on voxl 2 sdk 0.9.5 with no luck .

i tried to looking at voxl-px4.config and i can see only ist8310.

is it even supported on this build ?

thanks in advance
ben

hi guys
i need a quick tip from your experience ,
im trying to use flightdeck v2 on regular 5" frame with high speed flight dynamics .

i wanted to know if you think that i should use different dumpers(original blue ones )or even different solution for such a frame and flight dynamics .

@afdrus
thank you !

hi @afdrus afdrus
can you share how did you enable voa on voxl2 platform?
i didn't fund much details

@Adrian-Hidalgo @Alex-Kushleyev @Eric-Katzfey
UPDATE:
we have open the flightdeck and surprisingly discovered that the barometer sensor was stuck in his cover and ripped off
, look like it was glued to the barometer cover , that explain all.

you should check to see if something in this cover is too tight or glued .

we have 4 flightdeck's and now we afraid to move the voxl board from it
since we never took the board out of the deck or crashed it i cant see another reason .

.