<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>we have to DAQ systems with identical hardware. Whenever, there is a new version (TRLOII, NURDLIB, DRASI, etc.) from your side that we want to test, I am setting up one of them with the most recent software version.</p>
<p><br>
</p>
<p>So, right now we have a running system that is roughly on the software status of two months ago (if I remember corretly, this was after the repository change as we first had to ask you to recreate the SIS3316 development branch) with some modifications from
our side to the SIS3316 code (committed about six weeks ago). And we have the 'new' system that has identical hardware and the software status from last week. </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> Donnerstag, 18. Juli 2024 15:47:46<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] New warning meassage in R3BFUSER</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
Dear Günter,<br>
<br>
did I follow this thread correctly that these tests are with 'new' <br>
hardware, i.e. a setup which has no working reference software?<br>
<br>
You have / are using the SIS3316 modules in another physical setup with <br>
some fairly recent branch in the previous nurdlib repository?<br>
<br>
<a href="https://gitlab.com/chalmers-subexp/nurdlib.prelgpl21/-/network/master">https://gitlab.com/chalmers-subexp/nurdlib.prelgpl21/-/network/master</a><br>
<br>
--<br>
<br>
If so, there are three changes at the same time:<br>
<br>
- Nurdlib updates (also split by the repository change).<br>
<br>
- The SIS3316 code branch adapted from the previous to the new repository.<br>
<br>
- A new hardware setup.<br>
<br>
Cheers,<br>
Håkan<br>
<br>
<br>
<br>
On Thu, 18 Jul 2024, Weber, Guenter Dr. wrote:<br>
<br>
> <br>
> Dear Håkan,<br>
> <br>
> <br>
> with diff = 1 the DAQ is running as long as only the VULOM4B is readout. Adding a SIS3316<br>
> module results in an readout error of that module, followed by a reset of the DAQ.<br>
> <br>
> <br>
> Thus, I am currently unable to test SIS3316_check_hit_reworked_rebased. Sorry :-(<br>
> <br>
> <br>
> <br>
> <br>
> Best greetings<br>
> <br>
> Günter<br>
</div>
</span></font>
</body>
</html>