# Image transmission between Trip2 and VOXL2

Source: https://forum.modalai.com/topic/3191/image-transmission-between-trip2-and-voxl2
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2024-03-11 06:19:54 UTC by Ethan Wu
Replies: 8 · Views: 1431

## Ethan Wu · 2024-03-11 06:19:54 UTC

Good afternoon,

I am currently working on integrating a [Trip2 camera](https://www.nextvision-sys.com/accessories/) with a voxl2 device, aiming to establish image streaming via Ethernet. However, I am encountering challenges as the voxl2 device does not recognize the Trip2 camera, despite a successful ping connection.

In an effort to better understand the handling of UVC camera image information within the voxl2 server, I am interested in exploring relevant sections of the voxl2 codebase. Could you kindly guide me to specific resources or code segments, such as those in [voxl-streamer](https://gitlab.com/voxl-public/voxl-sdk/services/voxl-streamer), that would enhance my comprehension of how UVC camera data is processed on the voxl2 server?

Furthermore, I am curious about the potential for modifying these code sections to achieve successful image transfer between the Trip2 camera and the voxl2 device. Your insights and guidance on this matter would be greatly appreciated.

Thank you for your time and assistance.

## Reply by Eric Katzfey (ModalAI staff) · 2024-03-11 16:06:00 UTC

@Ethan-Wu UVC cameras use voxl-uvc-server in our system https://gitlab.com/voxl-public/voxl-sdk/services/voxl-uvc-server. You can certainly modify the code as you need for your application.

## Reply by Ethan Wu · 2024-03-12 03:37:28 UTC (in reply to Eric Katzfey)

@Eric-Katzfey 

Hello,
I changed the ethernet connection on my Trip2 camera to use HDMI converted to USB. After running voxl-uvc-server -l, the device information is detected, but when debugging, a segmentation fault is reported. Any idea what could be causing this? Here is the error information:

``` shell
voxl2:/$ voxl-uvc-server -f 5 -d

loading config file
Enabling debug messages
=================================================================
width:                            640
height:                           480
fps:                              5
pipe_name:                        uvc
==============================================================
voxl-uvc-server starting
Image resolution 640x480, 5 fps chosen
UVC initialized
Device found
Device opened
uvc_get_stream_ctrl_format_size succeeded for format YUYV
Streaming starting

Segmentation fault:
Fault thread: voxl-uvc-server(tid: 2617)
Fault address: 0x7fae693000
Access to this address is not allowed.
Segmentation fault
```

Any insights on what might be causing the segmentation fault would be appreciated.

## Reply by Eric Katzfey (ModalAI staff) · 2024-03-12 15:52:04 UTC (in reply to Ethan Wu)

@Ethan-Wu I really don't have any idea. Often when bringing up a new UVC camera there are issues that need to be debugged and resolved.

## Reply by Ethan Wu · 2024-03-14 03:07:38 UTC (in reply to Eric Katzfey)

@Eric-Katzfey Thank you for replying, now the problem is solved and I think is a hardware issue that leads to segmentation fault.

## Reply by Ethan Wu · 2024-03-14 03:20:00 UTC (in reply to Eric Katzfey)

@Eric-Katzfey Additionally, I apologize if my initial question was unclear. I understand that VOXL supports UVC type cameras. I'd like to know if cameras transmitted via an Ethernet adapter can be used on VOXL? Or would I need to make significant modifications to the code to achieve this?

## Reply by Ethan Wu · 2024-03-14 03:22:12 UTC (in reply to Ethan Wu)

@Ethan-Wu I just did some research to find out that it seems that Ethernet can't be treated like a UVC camera, right?

## Reply by Moderator (ModalAI staff) · 2024-03-14 04:09:59 UTC (in reply to Ethan Wu)

@Ethan-Wu UVC is USB Video Device Class, [Wikipedia](https://en.wikipedia.org/wiki/USB_video_device_class)

## Reply by Eric Katzfey (ModalAI staff) · 2024-03-15 15:12:58 UTC (in reply to Ethan Wu)

@Ethan-Wu Not sure about Ethernet. UVC is specific to USB.