<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:14pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Dear <span>Håkan,</span><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px"></span></p>
<p><span><br>
</span></p>
<p><span>thank you for the prompt reply.</span></p>
<p><span><br>
</span></p>
<p><span>Attached please find the manual for the V767A module. On page 25 the GEO REGISTER is discussed. And is I understand, your interpretation is correct that only V767AB is the outlier where the GEO address can be set via software.</span></p>
<p><span><br>
</span></p>
<p><span>Thanks a lot for paying attention to these details!</span></p>
<p><span><br>
</span></p>
<p><span><br>
</span></p>
<p><span><br>
</span></p>
<p><span>Best greetings</span></p>
<p><span>Günter</span></p>
<p><span><br>
</span></p>
<p><br>
</p>
<div id="x_Signature">
<div style="font-family:Tahoma; font-size:13px"></div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Håkan T Johansson <f96hajo@chalmers.se><br>
<b>Gesendet:</b> Sonntag, 28. April 2024 18:21:53<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] UCESB - SPEC file for CAEN V767</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
Dear Günter,<br>
<br>
I see. But I suspect this is then not a difference between the V767 and <br>
V767A, but rather between if the module has a JAUX connector (short one <br>
between the big P0 and P1 connectors) on the back. With the JAUX, it <br>
should indeed take this field from the position in the crate, and the <br>
corresponding config register is only readable.<br>
<br>
The manual I find only talks about a 128 ch version, and then V767 and <br>
V767B, where B does not have the JAUX connector... (I do find a <br>
64-channel V767A module referenced in an old sales catalogue. Seems <br>
CAEN's naming scheme leaves a bit to be desired...)<br>
<br>
I've added recognition of VME_CAEN_V767x_NO_GEOM_MATCH, which, if defined <br>
before the .spec file is included, avoids the MATCH/CHECK of that header <br>
field.<br>
<br>
Cheers,<br>
Håkan<br>
<br>
<br>
<br>
On Sun, 28 Apr 2024, Weber, Guenter Dr. wrote:<br>
<br>
> <br>
> Dear Håkan,<br>
> <br>
> <br>
> if I understand correctly, if the GEO address is not set via software this<br>
> number is determined by the position of a module in the VME crate. Thus,<br>
> even if you have access to the main.cfg of a certain measurement, it is<br>
> still unclear what the right GEO number is. The only chance to determine the<br>
> right number for a module would be to either have the information where the<br>
> module was (and how this translates to the GEO number) or to look into the<br>
> raw LMD data and search for the data block of the module in question. This<br>
> is not very convenient, in particular as in our most people will use the DAQ<br>
> and the corresponding software as a black box.<br>
> <br>
> <br>
> If this is correct, maybe it would be a good idea to make the GEO check<br>
> optional (if this is possible within the code, i. e. by defining geom = -1<br>
> as a wild card).<br>
> <br>
> <br>
> <br>
> Best greetings<br>
> <br>
> Günter<br>
> <br>
> <br>
> ____________________________________________________________________________<br>
> Von: subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Håkan<br>
> T Johansson <f96hajo@chalmers.se><br>
> Gesendet: Samstag, 27. April 2024 15:41:21<br>
> An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
> Betreff: Re: [subexp-daq] UCESB - SPEC file for CAEN V767 <br>
> <br>
> Hi Günter,<br>
> <br>
> thanks for the V767 .spec file. I have added it, with some modifications:<br>
> <br>
> The 0x767a767a marker word does as far as I see in the V767 manual not<br>
> come from the module, but I suspect is a barrier inserted in the nurdlib<br>
> configuration. That should be matched outside the module in the unpacker.<br>
> <br>
> The geom bits MATCH would be used for unpacking to find the correct<br>
> module, independent of how the module 'learnt' which number it should<br>
> have. I removed the #ifdefs around that.<br>
> <br>
> I suppose that the 64-channel version always has a zero in bit 30 of the<br>
> data words?<br>
> <br>
> I hope I managed to put the CHECK_COUNT and MARK_COUNT correctly, such<br>
> that the lngth checking passes for actual data...<br>
> <br>
> Please test.<br>
> <br>
> Cheers,<br>
> Håkan<br>
> <br>
> <br>
> <br>
> On Fri, 26 Apr 2024, Weber, Guenter Dr. wrote:<br>
> <br>
> ><br>
> > Dear friends,<br>
> ><br>
> ><br>
> > attached please find a first version of the SPEC file for the TDC module<br>
> we<br>
> > added to NURDLIB a while ago.<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Best greetings<br>
> ><br>
> > Günter<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> <br>
></div>
</span></font>
</body>
</html>