Area Detector manta camera communication issue

[Matt Shaw - STFC UKRI via Tech-talk <tech-talk at aps.anl.gov>]

Hi,

 

I’m having an issue with connecting to certain manta cameras (G-235B & G-319B)

The cameras are pingable from my ioc, and I can see them via arv-tool-0.8, but when I try to connect via the IOC I get the following

 

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

aravisConfig("CAM08", "xxx.xxx.xxx.xxx", 0, 0, 0)

ADAravis: Looking for camera xxx.xxx.xxx.xxx...

 

(process:3830): XML-CRITICAL **: 11:09:34.977: Input is not proper UTF-8, indicate encoding !

Bytes: 0xEF 0x61 0x64 0x3C

 

ADAravis: Your tick frequency is 1000000000

So your timestamp resolution is 1.000000 ns

2025/05/14 11:09:34.984 ADAravis:makeStreamObject: Making stream failed, err=No stream channel found, retrying in 5s...

ADAravis: Looking for camera xxx.xxx.xxx.xxx...

 

(process:3830): XML-CRITICAL **: 11:09:40.352: Input is not proper UTF-8, indicate encoding !

Bytes: 0xEF 0x61 0x64 0x3C

 

 

(process:3830): GLib-WARNING **: 11:09:40.356: GError set over the top of a previous GError or uninitialized memory.

This indicates a bug in someone's code. You must ensure an error is NULL before it's set.

The overwriting error message was: No stream channel found

2025/05/14 11:09:40.357 ADAravis:makeStreamObject: Making stream failed, err=No stream channel found

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

If I try to pull info from the camera via arv-tool-0.8 I get a similar response:

 

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

~]$ arv-tool-0.8 -a 192.168.1.147

 

(arv-tool-0.8:5000): XML-CRITICAL **: 11:37:59.483: Input is not proper UTF-8, indicate encoding !

Bytes: 0xEF 0x61 0x64 0x3C

 

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

I assume that this is an issue with the XML coming from the camera in the wrong format / missing some data, but I can’t find reference to this “XML-CRITICAL”

Has anyone experienced this behaviour before and been able to fix?

 

Thank you in advance

Matt Shaw

(Daresbury Lab)