# Starling 2 Max V2; SDK 1.4.0; camera-server and VOXL-Portal

Source: https://forum.modalai.com/topic/4138/starling-2-max-v2-sdk-1-4-0-camera-server-and-voxl-portal
Category: Development Drones (https://forum.modalai.com/category/44/development-drones)
Tags: starling
Posted: 2025-02-02 21:39:27 UTC by JoeC
Replies: 2 · Views: 815

## JoeC · 2025-02-02 21:39:27 UTC

Hello, Bottom Line:  I was unable to access cameras in voxl-portal after a fresh flashing of SDK 1.4.0 on a new Starling 2 Max V2; required for intrinsics calibration.  Further digging showed errors related to the "server disconnecting" regularly appear with 'voxl-inspect-cameras -a'.  Errors are:
"
ERROR in pipe_client_open opening request pipe: No such device or address
Most likely the server stopped without cleaning up
Client is cleaning up pipes for the server
ERROR in pipe_client_open opening request pipe: No such device or address
Most likely the server stopped without cleaning up
Client is cleaning up pipes for the server
<similar lines...>
"
SKU setting is: 
family code:   MRB-D0012 (starling-2-max)
compute board: 4 (voxl2)
hw version:    2
cam config:    29
modem config:  11 (Microhard v2, pMDDL2450(M0048))
tx config:     9 (ghost)
extras config: 0 (none)
SKU:           MRB-D0012-4-V2-C29-T9-M11-X0

I note that using 'voxl-inspect-cam tracking_down' or other camera requests appear to work; I went up to listing 4 cameras at once.  Could it be that the bus is saturated with too many cameras?  

Are there other diagnostics that can be run to nail down what's going on?  The physical configuration is unchanged from a stock vehicle.

## Reply by Alex Kushleyev (ModalAI staff) · 2025-02-03 19:57:53 UTC

Hello @JoeC , this may be related to an issue mentioned in the following thread. please take a look

https://forum.modalai.com/topic/4139/voxl-portal-wont-display-live-camera-feeds-after-sdk-1-4-0-upgrade

## Reply by JoeC · 2025-02-04 00:44:18 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev Hi Alex, Thanks!  Yes, that was exactly the problem.  I switched to the dev branch using 'voxl-configure-pkg-config', downloaded the latest voxl-portal ('apt get update && apt install voxl-portal'), and then switched back to the 1.4.0 pkg.  Voxl-Portal works just fine now.