Log entry time 22:06:22 on October 04, 2010

Entry number 333650

This entry is a followup to: 333649

Followups:

• 333743 10/05/10 16:45 R. Michaels epicsLogger script split in two

I'm fairly sure the EPICS truncations are due to the ET insertion
algorithm, since it was historically necessary to limit this (and issue
a warning) to avoid crashing the ET system.  The DVCS HV stuff comes 
near the end, and the truncation limit is 17500 bytes. I suppose it 
could be tweaked or studied or perhaps even fixed, but the easiest
workaround is to split the epicsLogger script into two : 
epicsLogger1 and epicsLogger2.

Here's how to tell if you are truncating

epicsLogger makes a temporary file ~/epics/halla.epics
and fastEpicsLogger makes ~/epics/fast.epics.  These in
turn get inserted into the datastream.  Use "wc -c" to
count how many characters (bytes):

[a-onl@adaql2 ~/epics]$ wc -c halla.epics
18441 halla.epics
[a-onl@adaql2 ~/epics]$ wc -c fast.epics
1794 fast.epics

Note, halla.epics is 941 bytes bigger than the limit of 17500.
Therefore, that last part (presumably DVCS HV) gets thrown out
and a warning "etInsertEvent: WARNING: truncating ..." (etc)

Simply make these temporary files less than 17500 bytes as a workaround.