solved.
I found rotate_tracking option of voxl-configure-cameras command.

I would like to install the Tracking camera upside down.

I understand that I have to change extrinsics.conf.
https://docs.modalai.com/configure-extrinsics/

But Qvio Overlay on the web portal is still upside down.
Is there an option to invert it like camera_config.xml in Hires?
https://forum.modalai.com/topic/305/camera-orientation-parameter

Also, would you please advise if there are any accuracy issues or other settings that should be changed?

I tested these sensors with VOXL Flight.

hires: Starvis IMX412
tracking: OV7251 167° Tracking Sensor Module
ToF

The error occured after I typed voxl-configure-cameras 6 and check hires view in voxl-portal.

-- Logs begin at Thu 1970-01-01 00:00:04 UTC, end at Thu 1970-01-01 00:01:06 UTC. --
Jan 01 00:00:07 apq8096 systemd[1]: Started voxl-camera-server.
Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: Camera server is now stopping
Jan 01 00:00:10 apq8096 bash[2030]: There is a chance that it may segfault here, this is a mmqcamera bug, ignore it
Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: Stopping tracking camera
Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: tracking camera stopped successfully
Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: Stopping hires camera
Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: hires camera stopped successfully
Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: Stopping stereo camera
Jan 01 00:00:10 apq8096 bash[2030]: Segmentation fault:
Jan 01 00:00:10 apq8096 bash[2030]: Fault thread: voxl-camera-ser(tid: 2030)
Jan 01 00:00:10 apq8096 bash[2030]: Fault address: 0x68
Jan 01 00:00:10 apq8096 bash[2030]: Address not mapped.
Jan 01 00:00:10 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Main process exited, code=killed, status=11/SEGV[[0m
Jan 01 00:00:10 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Unit entered failed state.[[0m
Jan 01 00:00:10 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Failed with result 'signal'.[[0m

system image: 3.8.0 / voxl-suite: 0.7

And I also tested it with System Image 4.0, but the error also occured.

-- Logs begin at Thu 1970-01-01 00:10:17 UTC, end at Thu 1970-01-01 00:13:17 UTC. --
Jan 01 00:12:42 apq8096 systemd[1]: Stopped voxl-camera-server.
Jan 01 00:12:42 apq8096 systemd[1]: Started voxl-camera-server.
Jan 01 00:12:43 apq8096 bash[3645]: ERROR:   Camera 1 failed to find supported preview config: 640x480
Jan 01 00:12:43 apq8096 bash[3645]: ERROR:   Failed to start camera: tracking, exiting
Jan 01 00:12:43 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Main process exited, code=exited, status=255/n/a[[0m
Jan 01 00:12:43 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Unit entered failed state.[[0m
Jan 01 00:12:43 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Failed with result 'exit-code'.[[0m
Jan 01 00:12:53 apq8096 systemd[1]: Stopped voxl-camera-server.
Jan 01 00:12:53 apq8096 systemd[1]: Started voxl-camera-server.
Jan 01 00:12:53 apq8096 bash[3976]: WARNING: Recieved RAW10 frame, will be converting to RAW8 on cpu
Jan 01 00:12:59 apq8096 bash[3976]: ERROR:   Recieved Fatal error from camera:hires
Jan 01 00:12:59 apq8096 bash[3976]: ERROR:   Sending request 3, ErrorCode: -ENODEV
Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: hires request thread recieved ESTOP
Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: tracking result thread recieved ESTOP
Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: hires result thread recieved ESTOP
Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: tof result thread recieved ESTOP
Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: tracking request thread recieved ESTOP
Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: tof request thread recieved ESTOP
Jan 01 00:12:59 apq8096 bash[3976]: ------ voxl-camera-server INFO: Camera server is now stopping
Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Deleting buffers: 3 of 16 still in use
Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Deleting buffers: 3 of 16 still in use
Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Deleting buffers: 3 of 16 still in use
Jan 01 00:13:00 apq8096 bash[3976]: ------ voxl-camera-server INFO: Camera server exited gracefully

I found "ERROR: Recieved Fatal error from camera:hires" from the message.
so I disabled hires with voxl-camera-server.conf.
And ToF and Tracking work.
Would this require replacing the Starvis camera?
Or do I need to set up something else?

@stevedan Couldn't find the way to solve so we sent back to ModalAI with RMA.
I wonder what was the issue of this.

@Eric-Katzfey Yes, it works.
I am not sure if changing the settings on the GCS side will affect the connection to other copter.
But now it seems fine.
Thanks.

@Eric-Katzfey
It's UgCS.
The default is v1.0.
It's possible to set v2 or auto.
But if I set auto, it fails to connect.
Because it tries to negotiate with v1 at first and VOXL doesn't handle it.

To reproduce:
set MAV_PROTO_VER to 1 (always use version 1)
VOXL cannot get any information from PX4.

voxl-mavlink seems to support only MAVLink 2.
https://gitlab.com/voxl-public/voxl-sdk/third-party/voxl-mavlink/-/tree/master/files

The third-party application I use uses MAVLink1 in part, which results in an error (actually no response).
Do you plan to support MAVLink v1.0 in the future?

@Alex-Kushleyev
Thank you for your reply.
I used MSU-M0026-1-01.
When changing to Green-ish, the gain becomes 69 (sorry, no snapshot).
I have a few other snapshots.

When the Gain drop, image turn to Green-ish.
Do you have plan to release WB setting feature?
It would be very useful to be able to change WB from config setting file without changing the source.