Hi @qubotics-admin ,

Between the two tests, i see that one test shows 16V input voltage and the other test ~7.2V. Was the voltage applied to the ESC the same during the tests (and the ESC read it incorrectly) or the voltage was in fact different?

Such a big difference can have adverse affects on spin-up if the change in voltage is not accounted for in the esc tuning param file.

It is possible that if the ESC does not have correct parameters for your motor / propeller, the sinusoidal spinup does not have enough power and loses tracking during the spin-up phase and fails to transition to steady-state spin stage.

The ESC channel 2 on the FPV ESC is the only channel that measures the total board current, so that is why the printout is slightly different when you test the channel 2.

Please provide the following details that will help us figure out the issue:

• what voltage are you testing the ESC? 16V or 7V?
• what motor/propeller do you have and which ESC params are you using?
• does the "bad" ESC channel ever properly spin up, or it never spins up at any battery voltage?
• is this the first time you are using this motor + propeller + voltage combination with the FPV ESC , or it has been previously working reliably?
• have you performed any ESC parameter tuning using voxl-esc tools?

Alex

@bschulzhf Take a look at the voxl-vision-hub code. Specifically the vio manager: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/dev/src/vio_manager.c?ref_type=heads

@jameskuesel , i have been testing a version of camera server that supports independent zoom / drag on each of the 4 misp channels and also independent EIS modes. This means that you can have one full size unstabilized image and one or more stabilized with EIS and arbitrary zoom and look-at positions for each stream.

There is also an updated voxl-portal version that has the multi view that supports showing and interactive with multiple streams at the same time.

If you would like to test it, let me know, i will need to document a bit. Please provide some more information such as what camera you use and what use cases you need, so i can provide an exact camera server config to test (basically specs for each misp channel, - fps, dims, eis/on off and eis mode)

Alex

These are the propellers that were used for that drone https://www.getfpv.com/lumenier-6x4-slow-flyer-propeller-set-of-4-clear.html

Hello @Mason-N ,

Going back in git history, I was able to find the seeker documentation. I think this is what you are looking for:

https://gitlab.com/voxl-public/support/documentation/-/tree/530dadd6fb9d50654ea34496c3d7f02d142fd732/docs/20-dev-drones/45-seeker

https://gitlab.com/voxl-public/support/documentation/-/tree/530dadd6fb9d50654ea34496c3d7f02d142fd732/docs/20-dev-drones/45-seeker/10-seeker-user-guide

Hi @Eyal ,

• The full weight of a standard Starling 2 is about 285g (with battery).

• the maximum motor thrust at full power is ~185g (at 7.5V) -- single motor

• this means the total max thrust for 4 motors is about 740g , which means about 2.6 thrust to weight ratio

  • please keep in mind that you can never apply full power to all 4 motors due to needed motor rpm differential for control

• it is a good practice to have at least 2.0 thrust to weight ratio in order to maintain good flight control. If you follow that guidance, it means that you can add about 85 extra grams to Starling 2 and it would be at 370g

  • flight time (hover) will drop from ~35 mins to ~25 mins (not exactly linear due to lower motor/prop efficiency at higher thrust)

• it is always recommended to try to keep the center of mass as close as possible to the geometrical center of the vehicle in order to reduce the moment of intertia and off-center mass which can affect control.

• depending on where the bulk of the weight is added, re-tuning flight (attitude) controller may be needed. extra weight far from vehicle center will increase moment of intertia, so the controller will need to adjust

Stinger FPV drone is a very different vehicle and although it is smaller than Starling 2 Max, the flight time of Stinger is significantly shorter due to.. smaller propellers, heavier (more durable) frame, etc

I think it all depends on what sensors you are planning today. If you want to share that, we can try to help..

Alex

@mkriesel It's possible the kernel you're flashing is incorrect. Can you provide the full terminal output of the install?

Hi Cbay,
There is a small clock buffer on the edge of the PCB. An RMA can only replace the whole board, not replace a single device. The part to check would be here:

@RoyAzriel ,

you can back up your voxl-camera-server.conf and then run voxl-configure-cameras 29 and the following will happen:

• all the existing sensormodule files will be wiped from /usr/lib/camera to avoid confusion
• only those sensormodules that belong in C29 config will be copied from /usr/share/modalai/chi-cdk to /usr/lib/camera
• the camera server config file (/etc/modalai/voxl-camera-server.conf) will be overwritten with the defaults for C29 configuration -- you can then see the config entry for TOF sensor and copy/paste that into your old config file, if you wish or use the new config file as is.

Alex

@chinlee5 Which drone do you have? Which versions of software are you using? Are those messages appearing on QGC? Also, do not try to arm the drone or fly the drone while attached to a power supply. Only use a battery for that. If you take the drone outside with a full view to the sky so that GPS can acquire satellites do the messages go away?