Re: Area Detector manta camera communication issue

["Pratt, Linda \(DLSLtd, RAL, LSCI\) via Tech-talk" <tech-talk at aps.anl.gov>]

Matt,

The EF looks rather like it is part of a Byte Order Mark (BOM) character FFEF which has lost a leading FF possibly having been interpreted as an ASCII form feed at some stage and ignored.

The  rest of the character codes do not look like the BOM for UTF-8, which Unicode recommend is not added to UTF-8 files anyway.  It would look like EF BB BF.

The trouble is it is difficult to analyse further as the text has now passed through your e-mail system,  and my e-mail reader etc as well - I can see you have a special apostrophe character in your dont, which suggests to me you might be on a Microsoft system.  On a linux system you can use od -ax to help with character issues, I am not familiar with what the Microsoft equivalent would be.

Linda

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Cobb, Tom (DLSLtd,RAL,LSCI) via Tech-talk <tech-talk at aps.anl.gov>
Sent: 14 May 2025 13:29
To: Matt Shaw - STFC UKRI <matt.shaw at stfc.ac.uk>; Jemian, Peter R <jemian at anl.gov>; tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Area Detector manta camera communication issue

 

Interesting, maybe the firmware got corrupted... Maybe updating the firmware (or reloading the same firmware) would fix it?

Thanks,

Tom

---

From: Matt Shaw - STFC UKRI <matt.shaw at stfc.ac.uk>
Sent: 14 May 2025 12:59
To: Jemian, Peter R <jemian at anl.gov>; Cobb, Tom (DLSLtd,RAL,LSCI) <tom.cobb at diamond.ac.uk>; tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: RE: Area Detector manta camera communication issue

 

You don't often get email from matt.shaw at stfc.ac.uk. Learn why this is important

Hi Pete,

 

If I run xmllint on the file I get my xml I get an encoder error

 

parser error : Input is not proper UTF-8, indicate encoding !

Bytes: 0xEF 0x61 0x64 0x3C

  <pInvalidator>UserSetL▒ad</pInvalidator>

 

I would expect the ▒ to be an o

But if I grep my xml I don’t see that ▒

 

Cheers,

Matt

 

 

From: Jemian, Peter R <jemian at anl.gov>
Sent: 14 May 2025 12:48
To: Cobb, Tom (DLSLtd,RAL,LSCI) <tom.cobb at diamond.ac.uk>; tech-talk at aps.anl.gov; Shaw, Matt (STFC,DL,TECH) <matt.shaw at stfc.ac.uk>
Subject: Re: Area Detector manta camera communication issue

 

Can you syntax check that XML file using xmllint?

 

  -  Pete

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Cobb, Tom (DLSLtd,RAL,LSCI) via Tech-talk <tech-talk at aps.anl.gov>
Sent: Wednesday, May 14, 2025 6:23:09 AM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>; Matt Shaw - STFC UKRI <matt.shaw at stfc.ac.uk>
Subject: Re: Area Detector manta camera communication issue

 

Hi Matt,

 

Does downloading the genicam XML (as specified on https://areadetector.github.io/areaDetector/ADGenICam/ADGenICam.html#downloading-the-xml-file) work? If so, what does the encoding on the XML file look like?

 

Thanks,

Tom

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Matt Shaw - STFC UKRI via Tech-talk <tech-talk at aps.anl.gov>
Sent: 14 May 2025 11:55
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Area Detector manta camera communication issue

 

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)

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom.

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom.

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom.