<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:14pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<div id="divtagdefaultwrapper" style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
<p>Dear <span>Håkan</span>,</p>
<p><br>
</p>
<p>to me it looks like <br>
</p>
<p><br>
</p>
<div><span style="font-size: 10pt;">$VULOM4_CTRL --addr=$addr --trig-status</span></div>
<br>
<p></p>
starts a never ending printout of the current status of the VULOM.</div>
<div style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
<br>
</div>
<div style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
Is there a possibility to just get the status a single time and then stop the execution?</div>
<div style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
<br>
</div>
<div style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
My intention is to check, after setting up the VULOM, when synchronization is done and it is safe to start the DAQ.</div>
<div style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
<br>
</div>
<div style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
<br>
</div>
<div style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
<br>
</div>
<div style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
Many thanks and best greetings</div>
<div style="font-size: 14pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
Günter<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr style="display:inline-block; width:98%" tabindex="-1">
<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, 22. Februar 2024 17:06<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] Report of a possible bug of the CAEN_V560 module</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
On Thu, 22 Feb 2024, Weber, Guenter Dr. wrote:<br>
<br>
> <br>
> Dear Hans,<br>
> <br>
> <br>
> many thanks! And in particular for all the detailed explanations.<br>
> <br>
> <br>
> For the VULOM "sleep 1" did not do the trick, but "sleep 10" worked. Is<br>
> there any chance to ask the VULOM if it feels ready to do the job, instead<br>
> of using a random waiting time?<br>
<br>
Now there is! Update trloii and recompile trlo_ctrl,<br>
<br>
--trig-status will at the end show some extra lines:<br>
<br>
Serial timestamp status:(0x000a8004) words: 4 badbits: 0 CHKsum:0x00<br>
Serial timestamp: Sync: no Bitstr. sync: no, had loss Data ptn: no, had loss<br>
<br>
Where it should say "Sync: ok" when the receiver has locked.<br>
<br>
The 'had loss' and bad bits count can be cleared (when locked) by issuing<br>
"pulse = SERIAL_TSTAMP_FAIL_CLEAR"<br>
<br>
> Also I noticed that when aksing the VULOM which firmware it is using, we get<br>
> a slightly different reply than the actual firmware number:<br>
> <br>
> RIO4-MCAL-1 mbsdaq > vulomflash --addr=3 --read<br>
> VULOM base address: 0x03000000<br>
> hwmap_mapvme.c:398: LOG: Virtual address for VULOM/TRIDI @ VME 0x03000000 is<br>
> 0x3005e000.<br>
> Performing command 'read'...<br>
> VOLUM+0 => 0x14091f20<br>
> VOLUM+RANGE_REG(0x800000) => 0x0000006a<br>
> Released vme ptr.<br>
> But the actual firmware number is 1409285e.<br>
> <br>
> For comparison should one look only at the first four hex numbers? Or is<br>
> there more to take into account?<br>
<br>
Yes, vulomflash --read reads at offset 0, and at that offset is also a <br>
TRIVA module mimic, which only uses the low 16 bits however. So the high <br>
16 bits give part of the firmware hash.<br>
<br>
> For the V560 module, misusing the bitmask for the counter resolved the<br>
> issue. At the end of this mail, I attach the new log. Maybe you find<br>
> something notable, but to me it looks fine now.<br>
> <br>
> <br>
> Our next steps would be as follows:<br>
> <br>
> <br>
> 1) Wait for you to implement the bugfixes of the last days into NURDLIB.<br>
> <br>
> 2) Setting up the test system with the most recent version of NURDLIB and<br>
> checking, if our minimal system with VULOM and V560 is now running smoothly.<br>
> <br>
> 3) Hammering the V767 TDC into NURDLIB.<br>
> <br>
> 4) Once we have achieved this, we would go back to testing the SIS3316<br>
> modules.<br>
> <br>
> <br>
> <br>
> Best greetings<br>
> <br>
> Günter<br>
<br>
Cheers,<br>
Håkan<br>
<br>
<br>
<br>
</div>
</span></font></div>
</div>
</div>
</body>
</html>