@Eric-Katzfey We use GPS, compass and the IO board for a PWM-controlled ESC and two servos. We also need two more PWM channels for gimbal control. That's it.
We do not use an RC. The control is purely via MAVLink. Joystick inputs are made via the MAVLink command MANUAL_CONTROL. Data is transmitted via the mobile network.
Hello everyone,
We are using the Mini VOXL with the following setup:
Camera:
IMX412 Sensor COAX BD M0161
Connector:
M0155
Here are some pictures of the setup:
I need clarification about the connection. Do we need to align the number "59" written on the Mini VOXL with the connector for proper connection? Should they overlap, as shown in the image below?
Any guidance on how to connect this correctly would be greatly appreciated.
Thanks in advance!
@Andrew-Tridgell @Eric-Katzfey I wanted to ask again about the current roadmap regarding Arduplane and the IO board for PWM.
Best regards
Tom
Perhaps it has already been considered to operate the VOXL2 with digital FPV cameras such as those from Walksnail. Maybe cameras with the same connectors also use the same standardized data formats.
Hi,
I'm curious if it's possible to connect the Image Sensor Micro-coax Adapter for VOXL 2 (MDK-M0155-1) to the Walksnail Camera System. The micro-coaxial cable shown in the picture of the VOXL 2 image sensor adapter looks very similar to the cable used in the Walksnail system. Does anyone know if these are actually the same type of cable?
@Eric-Katzfey Is there an update on the timeline yet?
Best regards
Tom
@Alex-Kushleyev That sounds excellent. I would like to use your stabilisation as soon as it is available.
Hello everyone,
is it possible to digitally stabilise the video image in real time with the VOXL2?
I am aware that image information is lost at the edges. One idea is to stabilise a 4k video image and then only transmit a stabilised HD video section from the centre.
Here you can see what I mean:
https://github.com/AdamSpannbauer/python_video_stab
I just wanted to show with the link what I mean. You would probably need other software that can also use hardware acceleration on the VOXL2.
Best regards
Tom
Hello everyone,
We use this camera:
Image Sensor 4k High-resolution, Low-light Sensor for VOXL
(Starvis IMX412 w/ M12-style Lens) (MSU-M0107)
Unfortunately, it is not recognised by the VOXL2 (see picture).
The module also says (voxl-camera-server):
ERROR: Found zero cameras connected, need at least one.
We used "voxl-configure-cameras 17" before.
Here is another interesting dmesg output that could mean something:
[ 161.278305] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address : 0xE2
[ 161.278307] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x9281
[ 161.278309] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x71
[ 161.278452] CAM_ERR: CAM-CCI: cam_cci_irq: 258 Base: pK-error, M1_Q0 NACK ERROR: 0x20000000
[ 161.278478] CAM_ERR: CAM-CCI: cam_cci_wait: 270 failed rc -22
[ 161.278480] CAM_ERR: CAM-CCI: cam_cci_transfer_end: 345 failed rc -22
[ 161.278483] CAM_ERR: CAM-CCI: cam_cci_data_queue: 870 Slave: 0xe0 failed rc -22
[ 161.278485] CAM_ERR: CAM-CCI: cam_cci_i2c_write: 1450 failed rc: -22
[ 161.278487] CAM_ERR: CAM-SENSOR: cam_cci_i2c_write_table_cmd: 123 Failed rc = -22
[ 161.278489] CAM_ERR: CAM-SENSOR: cam_sensor_set_alt_id: 768 [Applying Alternative Address] : Probe : camera_io_dev_write failed: rc=-22
[ 161.278618] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base: pK-error, M1_Q1 NACK ERROR: 0x40000000
[ 161.278642] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xe0:
[ 161.278644] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[ 161.278646] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[ 161.278649] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x9281:
[ 161.278703] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.79
[ 161.282198] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.60
[ 161.312366] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.60
[ 161.312412] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.79
[ 161.325847] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 731 [Applying Alternative Address] : Sensor Index : 391409844
[ 161.325850] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address : 0xE4
[ 161.325853] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x9281
[ 161.325855] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x72
[ 161.325999] CAM_ERR: CAM-CCI: cam_cci_irq: 258 Base: pK-error, M1_Q0 NACK ERROR: 0x20000000
[ 161.326018] CAM_ERR: CAM-CCI: cam_cci_wait: 270 failed rc -22
[ 161.326021] CAM_ERR: CAM-CCI: cam_cci_transfer_end: 345 failed rc -22
[ 161.326024] CAM_ERR: CAM-CCI: cam_cci_data_queue: 870 Slave: 0xe0 failed rc -22
[ 161.326026] CAM_ERR: CAM-CCI: cam_cci_i2c_write: 1450 failed rc: -22
[ 161.326029] CAM_ERR: CAM-SENSOR: cam_cci_i2c_write_table_cmd: 123 Failed rc = -22
[ 161.326031] CAM_ERR: CAM-SENSOR: cam_sensor_set_alt_id: 768 [Applying Alternative Address] : Probe : camera_io_dev_write failed: rc=-22
[ 161.326082] CAM_ERR: CAM-CCI: cam_cci_read: 1340 read_words = 0, exp words = 1
[ 161.326090] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[ 161.326092] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[ 161.326095] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x9281:
[ 161.326151] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.79
[ 161.326161] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base: pK-error, M1_Q1 NACK ERROR: 0x40000000
[ 161.330027] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.60
[ 161.368230] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died
voxl2:/$
By the way, we have also tried other cameras (e.g. Image Sensor 4k High-resolution for VOXL (8x8x5.8mm) (MSU-M0025) ). Always the same problem.
I would be very happy to receive any tips.
Best regards
Tom
@Eric-Katzfey That is a manageable period of time for me. We can use it to plan our product roadmap. Thank you very much and keep up the good work.