[subexp-daq] UCESB - SPEC file for CAEN V767

[Håkan T Johansson]

Dear Günter,

I see.  But I suspect this is then not a difference between the V767 and 
V767A, but rather between if the module has a JAUX connector (short one 
between the big P0 and P1 connectors) on the back.  With the JAUX, it 
should indeed take this field from the position in the crate, and the 
corresponding config register is only readable.

The manual I find only talks about a 128 ch version, and then V767 and 
V767B, where B does not have the JAUX connector...  (I do find a 
64-channel V767A module referenced in an old sales catalogue.  Seems 
CAEN's naming scheme leaves a bit to be desired...)

I've added recognition of VME_CAEN_V767x_NO_GEOM_MATCH, which, if defined 
before the .spec file is included, avoids the MATCH/CHECK of that header 
field.

Cheers,
Håkan



On Sun, 28 Apr 2024, Weber, Guenter Dr. wrote:

> 
> Dear Håkan,
> 
> 
> if I understand correctly, if the GEO address is not set via software this
> number is determined by the position of a module in the VME crate. Thus,
> even if you have access to the main.cfg of a certain measurement, it is
> still unclear what the right GEO number is. The only chance to determine the
> right number for a module would be to either have the information where the
> module was (and how this translates to the GEO number) or to look into the
> raw LMD data and search for the data block of the module in question. This
> is not very convenient, in particular as in our most people will use the DAQ
> and the corresponding software as a black box.
> 
> 
> If this is correct, maybe it would be a good idea to make the GEO check
> optional (if this is possible within the code, i. e. by defining geom = -1
> as a wild card).
> 
> 
> 
> Best greetings
> 
> Günter
> 
> 
> ____________________________________________________________________________
> Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Håkan
> T Johansson <f96hajo at chalmers.se>
> Gesendet: Samstag, 27. April 2024 15:41:21
> An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
> Betreff: Re: [subexp-daq] UCESB - SPEC file for CAEN V767  
> 
> Hi Günter,
> 
> thanks for the V767 .spec file.  I have added it, with some modifications:
> 
> The 0x767a767a marker word does as far as I see in the V767 manual not
> come from the module, but I suspect is a barrier inserted in the nurdlib
> configuration.  That should be matched outside the module in the unpacker.
> 
> The geom bits MATCH would be used for unpacking to find the correct
> module, independent of how the module 'learnt' which number it should
> have.  I removed the #ifdefs around that.
> 
> I suppose that the 64-channel version always has a zero in bit 30 of the
> data words?
> 
> I hope I managed to put the CHECK_COUNT and MARK_COUNT correctly, such
> that the lngth checking passes for actual data...
> 
> Please test.
> 
> Cheers,
> Håkan
> 
> 
> 
> On Fri, 26 Apr 2024, Weber, Guenter Dr. wrote:
> 
> >
> > Dear friends,
> >
> >
> > attached please find a first version of the SPEC file for the TDC module
> we
> > added to NURDLIB a while ago.
> >
> >
> >
> >
> > Best greetings
> >
> > Günter
> >
> >
> >
> >
> >
> >
> 
>