<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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>,</p>
<p><br>
</p>
<p>the ADC firmware is printed right after the firmware of the VME module:</p>
<p><br>
</p>
<p></p>
<div><span style="font-size:8pt">0: a:1: ..Serial number=0x00800172. (module/sis_3316/sis_3316.c:1305)</span><br>
<span style="font-size:8pt">10: a:1: ..id/firmware=0x33162010. (module/sis_3316/sis_3316.c:1312)</span><br>
<span style="font-size:8pt">10: a:1: ..adc[0] firmware=0x01250911. (module/sis_3316/sis_3316.c:1315)</span><br>
<span style="font-size:8pt">11: a:1: ..adc[0] has 16 bits. (module/sis_3316/sis_3316.c:1322)</span><br>
<span style="font-size:8pt">10: a:1: ..adc[1] firmware=0x01250911. (module/sis_3316/sis_3316.c:1315)</span><br>
<span style="font-size:8pt">11: a:1: ..adc[1] has 16 bits. (module/sis_3316/sis_3316.c:1322)</span><br>
<span style="font-size:8pt">10: a:1: ..adc[2] firmware=0x01250911. (module/sis_3316/sis_3316.c:1315)</span><br>
<span style="font-size:8pt">11: a:1: ..adc[2] has 16 bits. (module/sis_3316/sis_3316.c:1322)</span><br>
<span style="font-size:8pt">10: a:1: ..adc[3] firmware=0x01250911. (module/sis_3316/sis_3316.c:1315)</span><br>
<span style="font-size:8pt">11: a:1: ..adc[3] has 16 bits. (module/sis_3316/sis_3316.c:1322)</span></div>
<p></p>
<p><br>
</p>
<p>and</p>
<p><br>
</p>
<p></p>
<div><span style="font-size:8pt">10: a:1: ..Serial number=0x00800170. (module/sis_3316/sis_3316.c:1305)</span><br>
<span style="font-size:8pt">10: a:1: ..id/firmware=0x3316a012. (module/sis_3316/sis_3316.c:1312)</span><br>
<span style="font-size:8pt">10: a:1: ..adc[0] firmware=0x0125a012. (module/sis_3316/sis_3316.c:1315)</span><br>
<span style="font-size:8pt">11: a:1: ..adc[0] has 16 bits. (module/sis_3316/sis_3316.c:1322)</span><br>
<span style="font-size:8pt">10: a:1: ..adc[1] firmware=0x0125a012. (module/sis_3316/sis_3316.c:1315)</span><br>
<span style="font-size:8pt">11: a:1: ..adc[1] has 16 bits. (module/sis_3316/sis_3316.c:1322)</span><br>
<span style="font-size:8pt">10: a:1: ..adc[2] firmware=0x0125a012. (module/sis_3316/sis_3316.c:1315)</span><br>
<span style="font-size:8pt">11: a:1: ..adc[2] has 16 bits. (module/sis_3316/sis_3316.c:1322)</span><br>
<span style="font-size:8pt">10: a:1: ..adc[3] firmware=0x0125a012. (module/sis_3316/sis_3316.c:1315)</span><br>
<span style="font-size:8pt">11: a:1: ..adc[3] has 16 bits. (module/sis_3316/sis_3316.c:1322)</span></div>
<p></p>
<p><br>
</p>
<p>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.</p>
<p><br>
</p>
<p>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).</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings</p>
<p>Günter<br>
</p>
<p><br>
</p>
<p><br>
</p>
<br>
</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> Dienstag, 23. Januar 2024 14:15:41<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] How to start a DAQ system after NURDLIB, TRLOII, DRASI, etc. were updated</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
Dear Günter,<br>
<br>
how about the lines '..adc[0] firmware=' ? The ADC FPGAs have a different <br>
image than the VME FPGA.<br>
<br>
Perhaps they were not present with the older software..?<br>
<br>
I do not know much about the SSI3316 firmware versions, but from the looks <br>
of it, we have at least three different ones at hand so far for the VME <br>
FPGA:<br>
<br>
0x3316200e, 0x33162010, 0x3316a012<br>
<br>
Best regards,<br>
Håkan<br>
<br>
<br>
On Tue, 23 Jan 2024, Weber, Guenter Dr. wrote:<br>
<br>
> <br>
> Dear friends,<br>
> <br>
> <br>
> attached please find the output of the old system. To me it looks as if<br>
> every single setting of the SIS3316 modules is printed to screen. In total<br>
> almost 2000 lines for just two modules.<br>
> <br>
> <br>
> I find the following serial number entries:<br>
> <br>
> <br>
> Line 701:<br>
> <br>
> 10: a:1: ..Serial number=0x00800172. (module/sis_3316/sis_3316.c:1305)<br>
> 10: a:1: ..id/firmware=0x33162010. (module/sis_3316/sis_3316.c:1312)<br>
> <br>
> <br>
> Line 796:<br>
> <br>
> 10: a:1: ..Serial number=0x00800170. (module/sis_3316/sis_3316.c:1305)<br>
> 10: a:1: ..id/firmware=0x3316a012. (module/sis_3316/sis_3316.c:1312)<br>
<br>
<br>
<br>
<br>
> <br>
> <br>
> <br>
> Best greetings<br>
> <br>
> Günter<br>
> <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: Dienstag, 23. Januar 2024 12:32:50<br>
> An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
> Betreff: Re: [subexp-daq] How to start a DAQ system after NURDLIB, TRLOII,<br>
> DRASI, etc. were updated <br>
> <br>
> Dear Günter,<br>
> <br>
> On Tue, 23 Jan 2024, Weber, Guenter Dr. wrote:<br>
> <br>
> > as far as I know we never touched the SIS3316 firmware. But, as you know<br>
> by<br>
> > now, I know every little about the details of our DAQ, unfortunately.<br>
> <br>
> Could you for the other DAQ system (with working SIS3316), check the<br>
> output at startup or module re-init corresponding to these lines:<br>
> <br>
> 10: module/sis_3316/sis_3316.c:1355: ..Serial number=0x00800178.<br>
> 10: module/sis_3316/sis_3316.c:1362: ..id/firmware=0x3316200e.<br>
> 10: module/sis_3316/sis_3316.c:1365: ..adc[0] firmware=0x0125000c.<br>
> 10: module/sis_3316/sis_3316.c:1365: ..adc[1] firmware=0x0125000c.<br>
> 10: module/sis_3316/sis_3316.c:1365: ..adc[2] firmware=0x0125000c.<br>
> 10: module/sis_3316/sis_3316.c:1365: ..adc[3] firmware=0x0125000c.<br>
> <br>
> 10: module/sis_3316/sis_3316.c:1355: ..Serial number=0x008001a7.<br>
> 10: module/sis_3316/sis_3316.c:1362: ..id/firmware=0x33162010.<br>
> 10: module/sis_3316/sis_3316.c:1365: ..adc[0] firmware=0x01250011.<br>
> 10: module/sis_3316/sis_3316.c:1365: ..adc[1] firmware=0x01250011.<br>
> 10: module/sis_3316/sis_3316.c:1365: ..adc[2] firmware=0x01250011.<br>
> 10: module/sis_3316/sis_3316.c:1365: ..adc[3] firmware=0x01250011.<br>
> <br>
> and see what versions those modules have loaded?<br>
> <br>
> Cheers,<br>
> Håkan<br>
> <br>
></div>
</span></font>
</body>
</html>