<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 friends,</p>
<p><br>
</p>
<p>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.</p>
<p><br>
</p>
<p>I find the following serial number entries:</p>
<p><br>
</p>
<p>Line 701:<br>
</p>
<p></p>
<div>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)</div>
<p></p>
<p><br>
</p>
<p>Line 796:<br>
</p>
<p></p>
<div>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)</div>
<br>
<p></p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings</p>
<p>Günter<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 12:32:50<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>
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 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</div>
</span></font>
</body>
</html>