[subexp-daq] How to start a DAQ system after NURDLIB, TRLOII, DRASI, etc. were updated

[Weber, Guenter Dr.]

Dear Håkan,


the ADC firmware is printed right after the firmware of the VME module:


0: a:1: ..Serial number=0x00800172. (module/sis_3316/sis_3316.c:1305)
10: a:1: ..id/firmware=0x33162010. (module/sis_3316/sis_3316.c:1312)
10: a:1: ..adc[0] firmware=0x01250911. (module/sis_3316/sis_3316.c:1315)
11: a:1: ..adc[0] has 16 bits. (module/sis_3316/sis_3316.c:1322)
10: a:1: ..adc[1] firmware=0x01250911. (module/sis_3316/sis_3316.c:1315)
11: a:1: ..adc[1] has 16 bits. (module/sis_3316/sis_3316.c:1322)
10: a:1: ..adc[2] firmware=0x01250911. (module/sis_3316/sis_3316.c:1315)
11: a:1: ..adc[2] has 16 bits. (module/sis_3316/sis_3316.c:1322)
10: a:1: ..adc[3] firmware=0x01250911. (module/sis_3316/sis_3316.c:1315)
11: a:1: ..adc[3] has 16 bits. (module/sis_3316/sis_3316.c:1322)


and


10: a:1: ..Serial number=0x00800170. (module/sis_3316/sis_3316.c:1305)
10: a:1: ..id/firmware=0x3316a012. (module/sis_3316/sis_3316.c:1312)
10: a:1: ..adc[0] firmware=0x0125a012. (module/sis_3316/sis_3316.c:1315)
11: a:1: ..adc[0] has 16 bits. (module/sis_3316/sis_3316.c:1322)
10: a:1: ..adc[1] firmware=0x0125a012. (module/sis_3316/sis_3316.c:1315)
11: a:1: ..adc[1] has 16 bits. (module/sis_3316/sis_3316.c:1322)
10: a:1: ..adc[2] firmware=0x0125a012. (module/sis_3316/sis_3316.c:1315)
11: a:1: ..adc[2] has 16 bits. (module/sis_3316/sis_3316.c:1322)
10: a:1: ..adc[3] firmware=0x0125a012. (module/sis_3316/sis_3316.c:1315)
11: a:1: ..adc[3] has 16 bits. (module/sis_3316/sis_3316.c:1322)


We never had look at the firmware and also exchanged or six SIS3316 modules for each other. Thus, my assumption is that differences in the firmware number should not matter. But of course, I am not sure about this.


What puzzles me right now is the fact, that on the old system we get so much more output on the command line. On the new system it is just the SIS3316 firmware information and, for some reason, the threshold settings (out of a ton of various setting options for this type of module).





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: Dienstag, 23. Januar 2024 14:15:41
An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
Betreff: Re: [subexp-daq] How to start a DAQ system after NURDLIB, TRLOII, DRASI, etc. were updated


Dear Günter,

how about the lines '..adc[0] firmware=' ?  The ADC FPGAs have a different
image than the VME FPGA.

Perhaps they were not present with the older software..?

I do not know much about the SSI3316 firmware versions, but from the looks
of it, we have at least three different ones at hand so far for the VME
FPGA:

0x3316200e, 0x33162010, 0x3316a012

Best regards,
Håkan


On Tue, 23 Jan 2024, Weber, Guenter Dr. wrote:

>
> Dear friends,
>
>
> attached please find the output of the old system. To me it looks as if
> every single setting of the SIS3316 modules is printed to screen. In total
> almost 2000 lines for just two modules.
>
>
> I find the following serial number entries:
>
>
> Line 701:
>
> 10: a:1: ..Serial number=0x00800172. (module/sis_3316/sis_3316.c:1305)
> 10: a:1: ..id/firmware=0x33162010. (module/sis_3316/sis_3316.c:1312)
>
>
> Line 796:
>
> 10: a:1: ..Serial number=0x00800170. (module/sis_3316/sis_3316.c:1305)
> 10: a:1: ..id/firmware=0x3316a012. (module/sis_3316/sis_3316.c:1312)




>
>
>
> 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: Dienstag, 23. Januar 2024 12:32:50
> An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
> Betreff: Re: [subexp-daq] How to start a DAQ system after NURDLIB, TRLOII,
> DRASI, etc. were updated
>
> Dear Günter,
>
> On Tue, 23 Jan 2024, Weber, Guenter Dr. wrote:
>
> > as far as I know we never touched the SIS3316 firmware. But, as you know
> by
> > now, I know every little about the details of our DAQ, unfortunately.
>
> Could you for the other DAQ system (with working SIS3316), check the
> output at startup or module re-init corresponding to these lines:
>
> 10: module/sis_3316/sis_3316.c:1355: ..Serial number=0x00800178.
> 10: module/sis_3316/sis_3316.c:1362: ..id/firmware=0x3316200e.
> 10: module/sis_3316/sis_3316.c:1365: ..adc[0] firmware=0x0125000c.
> 10: module/sis_3316/sis_3316.c:1365: ..adc[1] firmware=0x0125000c.
> 10: module/sis_3316/sis_3316.c:1365: ..adc[2] firmware=0x0125000c.
> 10: module/sis_3316/sis_3316.c:1365: ..adc[3] firmware=0x0125000c.
>
> 10: module/sis_3316/sis_3316.c:1355: ..Serial number=0x008001a7.
> 10: module/sis_3316/sis_3316.c:1362: ..id/firmware=0x33162010.
> 10: module/sis_3316/sis_3316.c:1365: ..adc[0] firmware=0x01250011.
> 10: module/sis_3316/sis_3316.c:1365: ..adc[1] firmware=0x01250011.
> 10: module/sis_3316/sis_3316.c:1365: ..adc[2] firmware=0x01250011.
> 10: module/sis_3316/sis_3316.c:1365: ..adc[3] firmware=0x01250011.
>
> and see what versions those modules have loaded?
>
> Cheers,
> Håkan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chalmers.se/pipermail/subexp-daq/attachments/20240123/787b3698/attachment.html>