<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Dear Pablo,<br>
<br>
from the log I'm convinced that the ramp delay is something related
to the board firmware. I say this because looking the log it is
clear that all the power on commands are received by the boards at
the same time, but for a reason that we have to understand, sometime
a channel doesn't perform the ramp correctly but its first 5/6 steps
are anomalous.<br>
<br>
Here is a example extracted from your log:<br>
<br>
[2019-09-20T13:54:34]: [hvcaentest2] bd [0] ch [22] par [Pw] val
[true];<br>
[2019-09-20T13:54:34]: [hvcaentest2] bd [0] ch [23] par [Pw] val
[true];<br>
<br>
[2019-09-20T13:54:35]: [hvcaentest2] bd [0] ch [23] par [VMon] val
[1.09];<br>
[2019-09-20T13:54:35]: [hvcaentest2] bd [0] ch [22] par [VMon] val
[8.95];<br>
<br>
[2019-09-20T13:54:37]: [hvcaentest2] bd [0] ch [23] par [VMon] val
[2.03];<br>
[2019-09-20T13:54:37]: [hvcaentest2] bd [0] ch [22] par [VMon] val
[365.29];<br>
<br>
[2019-09-20T13:54:38]: [hvcaentest2] bd [0] ch [23] par [VMon] val
[4.37];<br>
[2019-09-20T13:54:38]: [hvcaentest2] bd [0] ch [22] par [VMon] val
[749.49];<br>
<br>
[2019-09-20T13:54:40]: [hvcaentest2] bd [0] ch [23] par [VMon] val
[6.31];<br>
[2019-09-20T13:54:40]: [hvcaentest2] bd [0] ch [22] par [VMon] val
[1133.44];<br>
<br>
[2019-09-20T13:54:41]: [hvcaentest2] bd [0] ch [23] par [VMon] val
[7.74];<br>
[2019-09-20T13:54:41]: [hvcaentest2] bd [0] ch [22] par [VMon] val
[1483.76];<br>
<br>
<br>
[2019-09-20T13:54:43]: [hvcaentest2] bd [0] ch [23] par [VMon] val
[8.11];<br>
[2019-09-20T13:54:43]: [hvcaentest2] bd [0] ch [22] par [VMon] val
[1499.73];<br>
<br>
<br>
[2019-09-20T13:54:44]: [hvcaentest2] bd [0] ch [23] par [VMon] val
[161.48];<br>
[2019-09-20T13:54:44]: [hvcaentest2] bd [0] ch [22] par [VMon] val
[1499.73];<br>
<br>
both ch22 and ch23 received the power on command at 13:54:34, but
the ch22 instead of ramping up as ch23 it starts a sort of anomalous
ramp (1.09,2.03,4.37,6.31,7.74,8.11,161,48). I think this is
someting that is related to the board, because the ramp is
implemented in the board firmware and the only issue that could
involve software should be a delay of the power on command. But if
the power up command had arrived in delay the VMon value would stay
around 1V from 13:54:35 to 13:54:43. A channel that has a VMon that
move from 1.09 to 8.11 means that the power up command was arrived,
it cannot happen if the channel is off. <br>
We have to reproduce this behaviour here in CAEN in order to
understand and solve this issue on A7030TN firmware.<br>
<br>
I would ask you a test, if you have time, can you repeat one of your
test adding to the GECO log also the channels status information and
the Ramp up? (i.e. from GECO logging configuration select PW, VMon,
Status , RUp for all channels) <br>
This will help us in our investigation.<br>
<br>
Best Regards,<br>
Alberto
<p><br>
</p>
<div class="moz-cite-prefix">Il 27/09/2019 18:09, Pablo Campero
Rojas ha scritto:<br>
</div>
<blockquote type="cite"
cite="mid:SN6PR0901MB2480C58C38F83293BBF2B5B0CC840@SN6PR0901MB2480.namprd09.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">Hello Alberto and Greg,</span></p>
<p style="margin: 0in 0in 0pt; color: rgb(0, 0, 0); line-height:
normal; font-family: Calibri,Arial,Helvetica,sans-serif;
font-size: 12pt;">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black"><br>
</span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black"></span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">I had a chance to re-test the same HV
board (S/N: 304) to check if the latency issue to ramp to the
set voltage happen always in the same channel.</span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">I also repeated the same test but
with another HV board (same model board: A7030TN, S/N: 297) at
the same SY4527 mainframe's slot 0. </span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">Attached find the document report
with the results and findings, I also uploaded additional
screenshots and data log files at
</span><a href="https://userweb.jlab.org/~campero/"
moz-do-not-send="true"><span style="font-size:12.0pt;
font-family:"Arial",sans-serif;mso-fareast-font-family:"Times
New Roman";
color:#0066CC;border:none windowtext
1.0pt;mso-border-alt:none windowtext 0in;
padding:0in">https://userweb.jlab.org/~campero/</span></a><span
style="font-size:12.0pt;font-family:"Arial",sans-serif;mso-fareast-font-family:
"Times New Roman";color:black">.</span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black"></span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">From the GECO 2020 data logged
analysis and EPICS-CSS screen monitoring data, confirmed that:</span></p>
<ul style="margin-bottom: 0in">
<li><span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">The delay to ramp to the set
voltage does not occur always in the same channel (s).
</span></li>
<li><span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">The delay issues was present with
the second board tested in the same mainframe's slot 0 as
well, the time is consistent ~ 10 s for all delay incidents
(Time difference measured between <i>Pw enabled/channel on </i>
and channel starts ramping up).
</span></li>
<li><span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">EPICS-CSS (EPICS Client) readout
matched with CAEN GECO 2020 data logged.
</span></li>
</ul>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black"></span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black"><br>
</span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">Perhaps this is not a hardware issue,
since all channels that presented ramp up delay issues
recovered by themselves in the next ramp up/down-cycles.</span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black"></span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black"><br>
</span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">Best Regards,</span></p>
<p style="margin: 0in 0in 8pt; line-height: 107%; font-family:
"Calibri",sans-serif; font-size:
11pt;margin-bottom:0in; margin-bottom:.0001pt; line-height:
normal">
<span
style="font-size:12.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New
Roman";color:black">Pablo</span></p>
<div style="color:rgb(0,0,0); font-size:12pt"><br>
</div>
<div style="color:rgb(0,0,0);
font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
Alberto Lucchesi <a class="moz-txt-link-rfc2396E" href="mailto:a.lucchesi@caen.it"><a.lucchesi@caen.it></a><br>
<b>Sent:</b> Friday, September 13, 2019 6:53 AM<br>
<b>To:</b> Pablo Campero Rojas <a class="moz-txt-link-rfc2396E" href="mailto:campero@jlab.org"><campero@jlab.org></a>; Greg
Kibilko <a class="moz-txt-link-rfc2396E" href="mailto:greg@setechsales.com"><greg@setechsales.com></a>; Gianni Di Maio
<a class="moz-txt-link-rfc2396E" href="mailto:g.dimaio@caen.it"><g.dimaio@caen.it></a>; Nicola Paoli
<a class="moz-txt-link-rfc2396E" href="mailto:n.paoli@caen.it"><n.paoli@caen.it></a>; Enrico <a class="moz-txt-link-rfc2396E" href="mailto:e.pardini@caen.it"><e.pardini@caen.it></a><br>
<b>Cc:</b> dsg-hallc controls
<a class="moz-txt-link-rfc2396E" href="mailto:dsg-hallc_controls@jlab.org"><dsg-hallc_controls@jlab.org></a><br>
<b>Subject:</b> Re: [EXTERNAL] Re: CAEN-SY4527 test Results
using Advanced GECO features</font>
<div> </div>
</div>
<div style="background-color:#FFFFFF">
<p style="margin-top: 0px; margin-bottom: 0px;margin-top:0px;
margin-bottom:0px; margin-top:0px; margin-bottom:0px">
<tt>Dear Pablo,<br>
<br>
</tt><tt><span class="x_tlid-translation x_translation"
lang="en"><span title="">thanks to your suggestions
</span></span>we were able to reproduce the same test as
described in your document and we found some interesting
information.<br>
As I told you in my previous email we saw that some channels
did not ramp up/down randomly and looking into the GECO log
we saw that the pw on/off command did not arrive to the
hardware.<br>
Enabling the logging into the IOC, we verified that the
missing commands (showed by the GECO log) were not arrived
also into EPIC IOC, so it seems the client not always send
all the commands, sometime it miss to send one or more.
<br>
I don't know why this happens, we know that there is a
function thtat the EPICS framework calls to set a command
and that function sometime is called 36 times (every time
giving the right channels to power up) and sometime is
called 35 and in this cane one channel obviously is not
powered on/off.<br>
We have several customemers that asked us if our mainframe
has EPICS IOC but we received very few support request
about EPICS so, or nobody use our IOC or someone use it with
a different EPICS client, I'm sorry but I don't know anyway
I would suggest you to try with a different one because it
seems the software you sent us it seems the first suspect.<br>
<br>
We also verified the discrepancy of values between GECO and
EPCIS, we reproduced it and also in this case we checked the
log from GECO and IOC logging file.
<br>
We noticed two things, the first is that the status in EPCIS
client did not change while the channel where powered on/off
from the GECO. Looking the IOC LOG file we see that the PV
linked to the Status were changed but the EPICS gui not.
<br>
We used also caget.exe and camonitor commands to verify the
PV "Status" and we received the right value, so also in this
case the wrong value seems to be only in the EPICS client
(HVCAEN-7030TN-Expert_slot0.opi).
<br>
The second issue were in the Process Variable PW, also in
this case the value changed in the GECO did not change in
the EPICS client.
<br>
The IOC log file showed that the value was changed but the
camonitor did not update to the correct value (as thw EPCIS
client HVCAEN-7030TN-Expert_slot0.opi), the caget command
instead shows the right value.
<br>
This is because the "Pw" Process Variable has the type
"Binary Output" (while the Status has the type Analog Input)
and BO do not follow the group "monitor parameters" so they
must be explicity read (I'm not an EPICS expert but I
suppose that AO can be retrieved with monitor while BO must
be get with get).<br>
<br>
Actually I'm not able to reproduce the problem of the ramp
delay but from the log file it seems this issue is not in
the software but is related to the board.
<br>
Can you check if the delay is always on the same channel or
not?<br>
</tt></p>
<p style="margin-top: 0px; margin-bottom: 0px;margin-top:0px;
margin-bottom:0px; margin-top:0px; margin-bottom:0px">
<tt>I think that we should have a reliable EPICS client (I
mean at least that it reliably sends all the commands to the
board) in order to proceed with other tests to investigate
the other open issues,<br>
alternatively I suggest to only use GECO at least to verify
that hardware works as expected, then we can put our focus
on EPCIS control.</tt><tt><span class="x_tlid-translation
x_translation" lang="en"><span title=""><br>
<br>
</span></span></tt></p>
<p style="margin-top: 0px; margin-bottom: 0px;margin-top:0px;
margin-bottom:0px; margin-top:0px; margin-bottom:0px">
<tt>Best Regards,<br>
Alberto<br>
<br>
</tt></p>
<div class="x_moz-cite-prefix">Il 10/09/2019 15:48, Pablo
Campero Rojas ha scritto:<br>
</div>
<blockquote type="cite"><span>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">Hello Alberto,</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">Find my answers/comments
in blue font bellow:</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
background:white"><br>
</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="background:white;
font-family:Calibri,Helvetica,sans-serif">“(ERROR:
Failed to register
</span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">../PABLO_SCRIPTS/HV-Board-36ch-hvcaentest2/All_HVBoards_Rup_36ch.js.)
so
</span></span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">can you help us to solve this
issue?</span></span><span style="background:white;
font-family:Calibri,Helvetica,sans-serif">”</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">To replicate the test with
one board connected in the mainframe we
<u>do not need to run</u> the <i>HVCAEN-MainExpertControls.opi</i>
screen. The error is generated when a value is trying to
be entered for the RUp parameter in that screen, and
CS-Studio is not finding the associated script. I did
not send those JavaScript that were developed to turn
on/off or set six parameters for all 16 HV boards’
channels (576 channels) simultaneously. I can provide
these eight JavaScripts, if you want to replicate the
test with all 16 A7030TN boards connected.</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">Use the following CSS-BOY
screens to replicate the tests:</span></p>
<ol>
<ol style="margin-bottom:0in">
<li><span style="background:white; color:blue;
font-family:"Times New Roman",Times,serif">HVCAEN-7030TN-Expert_slot0.opi
(controls/monitors turn on/off and main parameters
for 36 channels)</span></li>
<li><span style="background:white; color:blue;
font-family:"Times New Roman",Times,serif">HVCAEN-7030TN-RampTest_slot0.opi
(Monitor voltage ramp up/down for 36 channels)</span><span
style="color:blue; background:white"><br>
</span></li>
</ol>
</ol>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">Additionally, you must use
the eight JavaScript (contained in the “slot0” folder)
as part of the
<i>HVCAEN-7030TN-Expert_slot0</i> screen to control
power on/off and six input parameters for all 36
channels simultaneously. Board has to be connected at
slot 0.</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white"></span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
background:white"><br>
</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="background:white;
font-family:Calibri,Helvetica,sans-serif">“(one is a bug
in the EPICS
</span><span
style="font-family:Calibri,Helvetica,sans-serif">IOC the
otheris a bug in the EPICS client)”.</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">It could be the EPICS
client but keep in mind that a separate test by another
user at JLab was performed
<span style=""> </span>by using a different EPICS client
/Program (NI-EPICS Client/cRIO) and found the similar
issues with the addition of the random changes of the
parameters for no reason. (<b>Note</b>: For that test,
more than one A7030TN board was connected at the same
time (x16)). </span><span
style="font-family:""",serif;
color:#201F1E"><br style="">
<br style="">
</span><span style="font-family:"inherit",serif;
background:white"></span></p>
<span style="font-size-adjust:none">
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="background:white;
font-family:Calibri,Helvetica,sans-serif">“We noticed
also that the command order is different from EPCIS to
GECO,
</span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span
style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">I mean using GECO the
channels are powered averytime in the same order
</span></span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span
style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">(0,1,2,3, .., 35) while using
EPICS the order is random, this lead me to
</span></span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span
style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">think that probably the EPCIS
framework in same way desn't respect the
</span></span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span
style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">initial commands order. This
behavior in principle it is not bad but due
</span></span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span
style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">to to the fact that the
commands are not executed in milliseconds, there
</span></span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span
style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">cuold be little delay between
a power-up of a channel and a power up of
</span></span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span
style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">the near channel.</span></span><span
style="background:white;
font-family:Calibri,Helvetica,sans-serif">”</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">I already tried a 10,
100 and 1000 ms delay (in JavaScripts) between the
power on/off and set parameters commands of each
channel but it did not work. I noticed that most of
the time I had randomly the missed channel/s turned
on/off or with missed set parameters, as you noticed
in the previous sent test results report.</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif"><br>
</span></span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif"> </span></span><span
style="background:white;
font-family:Calibri,Helvetica,sans-serif">“I noted
that you already send me some script but with
different name, </span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span
style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">are these the same as those
requested by the .opi files and I only have
</span></span><span
style="font-family:""",serif;
color:#201F1E"><br>
</span><span
style="font-family:"inherit",serif;
background:white"><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size-adjust:none">to rename them or need I
something new?</span></span><span
style="background:white;
font-family:Calibri,Helvetica,sans-serif">”</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">See first answer above.
No need to re-name none of them, .opi files are
already configure to read/run JavaScript that I sent.</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt; line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:""",serif;
color:#201F1E"><br style="">
<br style="">
</span><span
style="font-family:"inherit",serif;
background:white"></span></p>
<span style="font-size-adjust:none">
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt;
line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white"></span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt;
line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">Best Regards,</span></p>
<p style="margin-top: 0px; margin-bottom:
0px;margin-top:0px; margin-bottom:0px; margin-top:0px;
margin-bottom:0px; margin:0in 0in 8pt;
line-height:107%;
font-family:"Calibri",sans-serif;
font-size:11pt">
<span style="font-family:"inherit",serif;
color:blue; background:white">Pablo </span>
</p>
</span></span><br>
</span>
<div style="color:rgb(0,0,0);
font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" face="Calibri, sans-serif"
color="#000000"><b>From:</b> Alberto Lucchesi
<a class="x_moz-txt-link-rfc2396E"
href="mailto:a.lucchesi@caen.it" moz-do-not-send="true"><a.lucchesi@caen.it></a><br>
<b>Sent:</b> Monday, September 9, 2019 12:23 PM<br>
<b>To:</b> Pablo Campero Rojas <a
class="x_moz-txt-link-rfc2396E"
href="mailto:campero@jlab.org" moz-do-not-send="true">
<campero@jlab.org></a>; Greg Kibilko <a
class="x_moz-txt-link-rfc2396E"
href="mailto:greg@setechsales.com"
moz-do-not-send="true">
<greg@setechsales.com></a>; Gianni Di Maio <a
class="x_moz-txt-link-rfc2396E"
href="mailto:g.dimaio@caen.it" moz-do-not-send="true">
<g.dimaio@caen.it></a>; Nicola Paoli <a
class="x_moz-txt-link-rfc2396E"
href="mailto:n.paoli@caen.it" moz-do-not-send="true">
<n.paoli@caen.it></a>; Enrico <a
class="x_moz-txt-link-rfc2396E"
href="mailto:e.pardini@caen.it" moz-do-not-send="true">
<e.pardini@caen.it></a><br>
<b>Cc:</b> dsg-hallc controls <a
class="x_moz-txt-link-rfc2396E"
href="mailto:dsg-hallc_controls@jlab.org"
moz-do-not-send="true">
<dsg-hallc_controls@jlab.org></a><br>
<b>Subject:</b> [EXTERNAL] Re: CAEN-SY4527 test Results
ussign Advanced GECO features</font>
<div> </div>
</div>
<div class="x_BodyFragment"><font size="2"><span
style="font-size:11pt">
<div class="x_PlainText">Dear Pablo,<br>
<br>
I looked your report and the logfile you sent us.<br>
<br>
Concernign the test 1, I noticed that the GECO logger
did not record the <br>
RUp/RDwn command so I presume the logger has been
started after those <br>
settings, this is bad because I did not see if all the
ramp set commands <br>
arrived to the mainframe (probably the channels with
wrong ramp value <br>
didn'r receive the set command).<br>
The test shows that a couple of channels are not
powered on/off and this <br>
is confirmed by the log file , the power on/off
command is not arrived <br>
for the channels that showed issue.<br>
There are two possible causes of this error (one is a
bug in the EPICS <br>
IOC the otheris a bug in the EPICS client).<br>
We are now trying to replicate the issue, we fought a
little with cs <br>
studio because we never used it, but now we are near
to be able to use <br>
it, now we are having an error because some script ar
enot present <br>
(ERROR: Failed to register <br>
../PABLO_SCRIPTS/HV-Board-36ch-hvcaentest2/All_HVBoards_Rup_36ch.js.) so
<br>
can you help us to solve this issue?<br>
As soon as we are able to run the test we can see
where the command are <br>
missed because we can start the IOC in DEBUG mode and
see its I/O.<br>
<br>
Concerning the test2 we noticed that using GECO all
the commands are <br>
received by the SY4527 and this confirm the fact that
the issue is <br>
related to the couple EPICS IOC/client.<br>
We noticed also that the command order is different
from EPCIS to GECO, <br>
I mean using GECO the channels are powered averytime
in the same order <br>
(0,1,2,3, .., 35) while using EPICS the order is
random, this lead me to <br>
think that probably the EPCIS framework in same way
desn't respect the <br>
initial commands order. This behavior in principle it
is not bad but due <br>
to to the fact that the commands are not executed in
milliseconds, there <br>
cuold be little delay between a power-up of a channel
and a power up of <br>
the near channel.<br>
<br>
In test 2 there is a channel that for two times had a
delay of the ramp, <br>
it is not the channel 17 (as described in the
document) but it is the <br>
channel 23. We don't have an explanation about this
wrong behavior, we <br>
never experienced something like that and we woudl
like to reproduce <br>
here the issue with one of our board using your EPICS
software (we are <br>
trying).<br>
<br>
The fact that GECO and ssh showed the same result
while EPICS client has <br>
different values) confirm that the system is correctly
working and the <br>
issue is related to the EPICS IOC/Client. As soon as
we are able to run <br>
the CSS test we hope to give you more details about
this wrong behavior.<br>
<br>
I think the right steps are:<br>
- understand better the problem showed in your test
(we are doing it)<br>
- fix it<br>
- increase the complexity of the setup and see the
result.<br>
<br>
<br>
I noted that you already send me some script but with
different name, <br>
are these the same as those requested by the .opi
files and I only have <br>
to rename them or need I something new?<br>
<br>
Best Regards,<br>
<br>
Alberto<br>
Il 06/09/2019 15:39, Pablo Campero Rojas ha scritto:<br>
> Hello Gianni and Greg,<br>
><br>
> Attached find report for the tests performed for
CAEN A7030 HV board, the report shows the results for
two test:<br>
><br>
> Test 1: Tested CAEN A7030 HV board by setting and
monitoring PVs using CSS-BOY screens with Advanced
Logging Feature enabled.<br>
> Test 2: Tested CAEN A7030 HV board using
GECO2020 Script and logging Advanced Features.<br>
><br>
> The data log files and additional screenshots for
each test can be found at: <a
href="https://userweb.jlab.org/~campero/"
moz-do-not-send="true">
https://userweb.jlab.org/~campero/</a><br>
><br>
> Let me know if you have any issues to access to
the files.<br>
><br>
> Best Regards,<br>
> Pablo Campero<br>
><br>
><br>
> ________________________________<br>
> From: Greg Kibilko <a
class="x_moz-txt-link-rfc2396E"
href="mailto:greg@setechsales.com"
moz-do-not-send="true">
<greg@setechsales.com></a><br>
> Sent: Wednesday, September 4, 2019 8:51 AM<br>
> To: Pablo Campero Rojas <a
class="x_moz-txt-link-rfc2396E"
href="mailto:campero@jlab.org"
moz-do-not-send="true">
<campero@jlab.org></a><br>
> Subject: Re: Re-sending email with link to
download files requested<br>
><br>
> Hi Pablo,<br>
><br>
> Just a quick note to check your status. Have you
had a chance to perform the tests requested by CAEN?<br>
><br>
> Cheers,<br>
> Greg<br>
><br>
> On 8/28/2019 11:25 AM, Pablo Campero Rojas wrote:<br>
> Hello Gianni,<br>
><br>
> Thank you for the code and the instructions. I'll
be performing this test in the upcoming days and I'll
get back to you once I have the results.<br>
><br>
> Best Regards,<br>
> Pablo<br>
><br>
><br>
> ________________________________<br>
> From: Gianni Di Maio <a
class="x_moz-txt-link-rfc2396E"
href="mailto:g.dimaio@caen.it"
moz-do-not-send="true">
<g.dimaio@caen.it></a><a
class="x_moz-txt-link-rfc2396E"
href="mailto:g.dimaio@caen.it"
moz-do-not-send="true"><mailto:g.dimaio@caen.it></a><br>
> Sent: Wednesday, August 28, 2019 10:36 AM<br>
> To: Pablo Campero Rojas <a
class="x_moz-txt-link-rfc2396E"
href="mailto:campero@jlab.org"
moz-do-not-send="true">
<campero@jlab.org></a><a
class="x_moz-txt-link-rfc2396E"
href="mailto:campero@jlab.org"
moz-do-not-send="true"><mailto:campero@jlab.org></a><br>
> Cc: Alberto Lucchesi <a
class="x_moz-txt-link-rfc2396E"
href="mailto:a.lucchesi@caen.it"
moz-do-not-send="true">
<a.lucchesi@caen.it></a><a
class="x_moz-txt-link-rfc2396E"
href="mailto:a.lucchesi@caen.it"
moz-do-not-send="true"><mailto:a.lucchesi@caen.it></a>;
Nicola Paoli
<a class="x_moz-txt-link-rfc2396E"
href="mailto:n.paoli@caen.it" moz-do-not-send="true"><n.paoli@caen.it></a><a
class="x_moz-txt-link-rfc2396E"
href="mailto:n.paoli@caen.it" moz-do-not-send="true"><mailto:n.paoli@caen.it></a>;
Enrico
<a class="x_moz-txt-link-rfc2396E"
href="mailto:e.pardini@caen.it"
moz-do-not-send="true"><e.pardini@caen.it></a><a
class="x_moz-txt-link-rfc2396E"
href="mailto:e.pardini@caen.it"
moz-do-not-send="true"><mailto:e.pardini@caen.it></a>;
Greg Kibilko
<a class="x_moz-txt-link-rfc2396E"
href="mailto:greg@setechsales.com"
moz-do-not-send="true"><greg@setechsales.com></a><a
class="x_moz-txt-link-rfc2396E"
href="mailto:greg@setechsales.com"
moz-do-not-send="true"><mailto:greg@setechsales.com></a><br>
> Subject: Re: Re-sending email with link to
download files requested<br>
><br>
> Hello Pablo,<br>
><br>
> here is the code to activate the logging
function.<br>
><br>
> d14146h04187f00221m03<br>
><br>
> Concerning the instructions to activate the
functionality are available in the user manual
attached.<br>
> SYx527 System Advanced Features at page 27.<br>
><br>
> Very good to know that you see the problem even
with the GECO alone, but, for our test please use
both( ie GECO + EPICS software)<br>
> Once you have connected GECO please enable
immediately the log for all the parameters of the
board you are testing ( start with only one board for
the moment).<br>
> Use your EPICS software to do the test and once
reproduced the problem stop the GECO logging and send
us the entire logfile describing us what happened.<br>
> At the moment we do not have an A7030 board
available so right now we can not do the same test,
but we will soon.<br>
><br>
> Best regards.<br>
> Gianni<br>
><br>
> Il 28/08/2019 00:50, Gianni Di Maio ha scritto:<br>
> Hello Pablo,<br>
> message received...<br>
> Tomorrow I will try to download the files.<br>
> OK proceed with the test with A7030 board.<br>
> Tomorrow I will let you know the activation code
and relative instructions.<br>
> Best regards.<br>
> Gianni<br>
><br>
> Il 27/08/2019 20:31, Pablo Campero Rojas ha
scritto:<br>
> Hello Gianni,<br>
><br>
> I sent you the email below a few hours ago, but
it seems like caen.it has rejected the email, I got a
"security/policy settings issues at caen.it".<br>
><br>
> I'm assuming that the issues are the result of
the attempts to send you a .zip file, which had all
the EPICS files that I used for my test.<br>
> Please try these link instead: <a
href="https://userweb.jlab.org/~campero/"
moz-do-not-send="true">https://userweb.jlab.org/~campero/</a><br>
> Let me know if you can get the files this time.<br>
><br>
><br>
>
.<br>
> Hello Gianni,<br>
><br>
> To clarify or add one point more to the summary
that you mentioned; the arbitrarily changes from its
pre-set values issue also has been noticed while a
user at JLab was using only GECO2020 with no external
EPICS client as part of the test setup.<br>
><br>
><br>
> Currently, DSG group does not have on hand the
A7435 HV board to get the recommended setup; we do
have HV board A7030 that we could use instead. Is that
ok for the recommended test?<br>
><br>
> The serial number for the SY4528 Basic CPU: 0760.<br>
> Please send me details instructions to activate
this functionality/option in GECO2020, which will help
to solve the issues.<br>
><br>
><br>
> Attached is a zip file with the EPIS CSS-BOY
screens (.opi files) and Java scripts (.js files that
run as part of the CSS screens) used to test SY4527
systems.<br>
> The specifications about the setup and details
for the software versions used for the test can be
find at:
<a
href="https://www.jlab.org/div_dept/physics_division/dsg/presentations2/Hall%20C%20HV%20CAEN%20Test%20Results.pdf"
moz-do-not-send="true">
https://www.jlab.org/div_dept/physics_division/dsg/presentations2/Hall%20C%20HV%20CAEN%20Test%20Results.pdf</a><br>
><br>
> Best Regards,<br>
><br>
> Pablo Campero<br>
> Detector Support Group<br>
> Jefferson Lab<br>
> 757-269-7034<br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> CAEN S.p.A. Gianni Di Maio<br>
> Maintenance Division Manager<br>
> Email: <a class="x_moz-txt-link-abbreviated"
href="mailto:g.dimaio@caen.it"
moz-do-not-send="true">g.dimaio@caen.it</a><<a
href="mailto:g.dimaio@caen.it"
moz-do-not-send="true">mailto:g.dimaio@caen.it</a>><br>
> Skype: gdimaio_caen<br>
> Cell:+393482556525<br>
><br>
> CAEN S.p.A.<br>
> Tel.: +39 0584 388 398<br>
> Fax: +39 0584 388 959<br>
> Email: <a class="x_moz-txt-link-abbreviated"
href="mailto:info@caen.it" moz-do-not-send="true">info@caen.it</a><<a
href="mailto:info@caen.it" moz-do-not-send="true">mailto:info@caen.it</a>><br>
> via Vetraia,11 • 55049 • Viareggio (LU) • Italy<br>
> Cod.Fisc. e p.IVA IT00864500467<br>
> <a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it&d=DwIF-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=C9l7VLVY2CjU9VF3rf_9p8Ob5VnJ_uJtMCx_CJovZdg&s=1YcsNaBfDXCLlmV4aSpWjvpIlvwL3ggiZDSRN0JTuf8&e="
moz-do-not-send="true">
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it&d=DwIF-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=C9l7VLVY2CjU9VF3rf_9p8Ob5VnJ_uJtMCx_CJovZdg&s=1YcsNaBfDXCLlmV4aSpWjvpIlvwL3ggiZDSRN0JTuf8&e=</a>
<<a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it&d=DwMF-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=E-P8t1rpOcX8LElZZhOE0mKQI61LJDakqpB08crZI18&s=2fsoHSr_K9zdQEP7A3baz0OQ4gcl3HP5P_T0n9X02o4&e="
moz-do-not-send="true">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it&d=DwMF-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=E-P8t1rpOcX8LElZZhOE0mKQI61LJDakqpB08crZI18&s=2fsoHSr_K9zdQEP7A3baz0OQ4gcl3HP5P_T0n9X02o4&e=</a>><br>
><br>
> Le informazioni trasmesse attraverso la presente
comunicazione via mail ed eventuali allegati sono da
intendersi di esclusiva spettanza del destinatario.
Nel caso in cui le stesse raggiungessero, per
qualunque motivo, soggetti diversi dai destinatari,
questi dovrebbero darne immediata notizia al mittente.
In ogni caso, eventuali soggetti diversi dai legittimi
destinatari della presente comunicazione sono
esplicitamente diffidati da ogni utilizzazione, sia ai
sensi del D.Lgs. n. 196/2003 "Codice in materia di
protezione dei dati personali" sia ai sensi degli art.
616 e ss. Codice Penale che sanziona la violazione del
segreto sulla corrispondenza.<br>
> The information contained in this transmission
may contain privileged and confidential information
and is intended only for the use of the person(s)named
above. If you are not the intended recipient, or an
employee or agent responsible for delivering this
message to the intended recipient, any review,
dissemination, distribution or duplication of this
communication is strictly prohibited. If you are not
the intended recipient, please contact the sender
immediately and destroy all copies of the original
message.<br>
><br>
> --<br>
> CAEN S.p.A. Gianni Di Maio<br>
> Maintenance Division Manager<br>
> Email: <a class="x_moz-txt-link-abbreviated"
href="mailto:g.dimaio@caen.it"
moz-do-not-send="true">g.dimaio@caen.it</a><<a
href="mailto:g.dimaio@caen.it"
moz-do-not-send="true">mailto:g.dimaio@caen.it</a>><br>
> Skype: gdimaio_caen<br>
> Cell:+393482556525<br>
><br>
> CAEN S.p.A.<br>
> Tel.: +39 0584 388 398<br>
> Fax: +39 0584 388 959<br>
> Email: <a class="x_moz-txt-link-abbreviated"
href="mailto:info@caen.it" moz-do-not-send="true">info@caen.it</a><<a
href="mailto:info@caen.it" moz-do-not-send="true">mailto:info@caen.it</a>><br>
> via Vetraia,11 • 55049 • Viareggio (LU) • Italy<br>
> Cod.Fisc. e p.IVA IT00864500467<br>
> <a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it&d=DwIF-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=C9l7VLVY2CjU9VF3rf_9p8Ob5VnJ_uJtMCx_CJovZdg&s=1YcsNaBfDXCLlmV4aSpWjvpIlvwL3ggiZDSRN0JTuf8&e="
moz-do-not-send="true">
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it&d=DwIF-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=C9l7VLVY2CjU9VF3rf_9p8Ob5VnJ_uJtMCx_CJovZdg&s=1YcsNaBfDXCLlmV4aSpWjvpIlvwL3ggiZDSRN0JTuf8&e=</a>
<<a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it&d=DwMF-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=E-P8t1rpOcX8LElZZhOE0mKQI61LJDakqpB08crZI18&s=2fsoHSr_K9zdQEP7A3baz0OQ4gcl3HP5P_T0n9X02o4&e="
moz-do-not-send="true">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it&d=DwMF-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=E-P8t1rpOcX8LElZZhOE0mKQI61LJDakqpB08crZI18&s=2fsoHSr_K9zdQEP7A3baz0OQ4gcl3HP5P_T0n9X02o4&e=</a>><br>
><br>
> Le informazioni trasmesse attraverso la presente
comunicazione via mail ed eventuali allegati sono da
intendersi di esclusiva spettanza del destinatario.
Nel caso in cui le stesse raggiungessero, per
qualunque motivo, soggetti diversi dai destinatari,
questi dovrebbero darne immediata notizia al mittente.
In ogni caso, eventuali soggetti diversi dai legittimi
destinatari della presente comunicazione sono
esplicitamente diffidati da ogni utilizzazione, sia ai
sensi del D.Lgs. n. 196/2003 "Codice in materia di
protezione dei dati personali" sia ai sensi degli art.
616 e ss. Codice Penale che sanziona la violazione del
segreto sulla corrispondenza.<br>
> The information contained in this transmission
may contain privileged and confidential information
and is intended only for the use of the person(s)named
above. If you are not the intended recipient, or an
employee or agent responsible for delivering this
message to the intended recipient, any review,
dissemination, distribution or duplication of this
communication is strictly prohibited. If you are not
the intended recipient, please contact the sender
immediately and destroy all copies of the original
message.<br>
><br>
> --<br>
> Greg Kibilko<br>
> SETS - SE Technical Sales, Inc.<br>
> 112 Tyra Lane<br>
> Townville, SC 29689<br>
> P: (864) 356-2606<br>
> CAEN Products<<a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it_csite&d=DwMD-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=EKYIDEH5c_qBONS0ZtpytsfH21iBGjnfDemmcBZ97wc&s=1eeoi4jZPyvQnEEf2hyhlGsCpr4_cfwb9kVnS0gB6zA&e="
moz-do-not-send="true">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.caen.it_csite&d=DwMD-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=EKYIDEH5c_qBONS0ZtpytsfH21iBGjnfDemmcBZ97wc&s=1eeoi4jZPyvQnEEf2hyhlGsCpr4_cfwb9kVnS0gB6zA&e=</a>><br>
> CAEN SyS Products & Solutions<<a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__caensys.com_products-2Dand-2Dsolutions_&d=DwMD-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=EKYIDEH5c_qBONS0ZtpytsfH21iBGjnfDemmcBZ97wc&s=Q-WOOcM3qQOAaPYtd-li08YCoG4tlCcBw_F9xedkU-Y&e="
moz-do-not-send="true">https://urldefense.proofpoint.com/v2/url?u=https-3A__caensys.com_products-2Dand-2Dsolutions_&d=DwMD-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=EKYIDEH5c_qBONS0ZtpytsfH21iBGjnfDemmcBZ97wc&s=Q-WOOcM3qQOAaPYtd-li08YCoG4tlCcBw_F9xedkU-Y&e=</a>><br>
> IOxOs Products<<a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ioxos.ch&d=DwMD-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=EKYIDEH5c_qBONS0ZtpytsfH21iBGjnfDemmcBZ97wc&s=0ubwG8gKZKsSe_dxMOR92YxzmPuEZ-KHQ0954wsHvq0&e="
moz-do-not-send="true">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ioxos.ch&d=DwMD-g&c=CJqEzB1piLOyyvZjb8YUQw&r=LBO4X3ekFDih7d6NqFyLjA&m=EKYIDEH5c_qBONS0ZtpytsfH21iBGjnfDemmcBZ97wc&s=0ubwG8gKZKsSe_dxMOR92YxzmPuEZ-KHQ0954wsHvq0&e=</a>><br>
<br>
</div>
</span></font></div>
</blockquote>
</div>
</blockquote>
</body>
</html>