 Thu May 26 01:44:45 2016, Patrick Coleman-Smith, [HowTo] Use the Multiplicity Trigger Firmware, V8.18, and update the files 
|
Done. Awaiting test. See attachments 1-2.
|
 Thu May 26 10:03:11 2016, Patrick Coleman-Smith, [HowTo] Specification Document for MACB including suggested setup.
|
| Attached is the specification for the MACB with the settings currently available. |
|
Thu May 26 14:19:13 2016, Patrick Coleman-Smith, [HowTo] Access AIDA documentation
|
The latest version of the FEE64 software Interface document ( May 2016 ) is available as a .pdf from
http://npg.dl.ac.uk/documents/edoc000/#AIDA. EDOC955
|
|
Wed Jun 1 12:14:08 2016, Patrick Coleman-Smith, [HowTo] React to "Check Clock Status => FEE64 Failure"
|
If there are more than one failures then check how they map to the MACB HDMI connections.
Are they all connected to the just one MACB ? => Check the HDMI cable at the MACB Layer Port.
Are they all connected to several MACBs which have a common "Parent" ? => Check the HDMI cable at the "Parent"
|
|
Thu Jul 7 17:16:11 2016, Patrick Coleman-Smith, Install & Run new firmware with diagnostics for the SYNC
|
Connected to aidas from daresbury.
Started Firefox with windows for Rpi, Merge, Runcontrol.
Power on FEEs from Pi.
|
|
Thu Jul 14 16:55:32 2016, Patrick Coleman-Smith, Changes to AIDA software
|
An updated copy of the merger has been downloaded ( merger64.AD ) with a copy of /MIDAS/Merger/AIDA/Startup.
These two enable the output of all of the SYNC data items to the TapeServer.
|
|
Mon Jul 18 12:00:16 2016, Patrick Coleman-Smith, Report of remote operation of Aida at RIKEN 11/7 to 14/7
|
Normal
0
false
false
false
|
|
Thu Jul 28 11:35:58 2016, Patrick Coleman-Smith, [HowTo] Apply Thermal paste to FPGA
|
| |
|
Mon Aug 1 11:30:07 2016, Patrick Coleman-Smith, First time remotely power up HV in RIKEN from Daresbury
|
Logged into aidas1 and opened the nnrpi1 relay control window ... powered up the FEE64s.
seperatly connected to ribfdaq and opened a firefox to aidas1:8015.
By the time the firefox had appeared on my desktop the FEE64s had started up. |
|
Mon Aug 15 09:55:08 2016, Patrick Coleman-Smith, Found a candidate for DAQ failure.
|
The problem :-
The DAQ stops working and can only be fixed by a reboot of the FEE64s.
The Candidate:- |
|
Wed Aug 17 14:10:05 2016, Patrick Coleman-Smith, Linux Memory problem solutions for FEE64
|
The problem indicated by "page allocation failure" and the kernal subsequently "killing" the AidaExecV8 process is due ( it appears
) to memory availability.
Solution 1:- Reduce the amount of memory used for histogramming. That would be by disabling the .V histograms or changing the size of the .H and/or |
|
Wed Aug 17 14:44:52 2016, Patrick Coleman-Smith, [HowTo] start acquisition using the new "Start ASIC Readout" button
|
Due to sometimes operating with very noisy systems, both at Daresbury and RIKEN, I have installed a change to the startup of the system.
The Runcontrol GO button now only starts the output of SYNC pulses. A further button labelled "Start ASIC Readout" ( see attached photo
) needs to be pressed to start the ASIC ADC, Discriminator and Correlation readout. |
|
Mon Aug 22 11:45:07 2016, Patrick Coleman-Smith, Software updated in Aida
|
Logged into aidas1, installed AidaExecV8 with a test of the time difference between SYNC data items. Failure to be 0x40000 clocks will cause a statistic
to be incremented. "SYNC Time Warp"
Installed updated versions of /MIDAS/TclHttpd/Html/AIDA/RunControl/sys.tcl and /MIDAS/TclHttpd/Html/AIDA/RunControl/implementation.tcl |
|
Wed Sep 7 16:11:25 2016, Patrick Coleman-Smith, Updated layout.txt file in aidas1
|
Used the layout reported in ELOG357 and updated the layout.txt file used in the "Layout and Status" browser window.
The file is in /MIDAS/config/TclHttpd/aidas1
The browser window "Layout and Status" is accessed from the Control browser window. |
|
Wed Nov 23 14:50:59 2016, Patrick Coleman-Smith, [ Info ] What does the System Wide Clock check mean when it fails.
|
The System Wide check called "Check Clock Status" reads the status register from the FEE64 units in the system and compares the value
of each bit against a template depending if the FEE64 is Master or not.
The bit fields have the following meaning :- |
|
Wed Jan 18 14:16:47 2017, Patrick Coleman-Smith, Repaired Modules returning to RIKEN
|
Five modules are being returned to RIKEN after repair.
The MAC addresses are :-
00:04:a3:2a:ED:8f |
|
Mon May 8 10:00:02 2017, Patrick Coleman-Smith, [HowTo] Operating document for the Pi_Monitor FEE64 console logging equipment
|
The operating proceedure for the Raspberry Pi FEE64 console monitor is attached.
Please let me know if more detail is required.
|
|
Thu May 18 15:20:44 2017, Patrick Coleman-Smith, [HowTo] Connecting a USB console interface to the FEE64
|
The three attachments show the orientation of the console cable pcb relative to the FEE64 connectors.
The first with the other cables and the other two with no cables for clarity of position. |
|
Wed May 24 13:39:12 2017, Patrick Coleman-Smith, Examination of Console Logs -- and a couple of reminders
|
I have tarred and zipped all 24 logs and shipped them back to the UK. Now I can browse through them.
Studying the "panics" :=
nnaida17 has one which is an NFS mount failure. |
|
Wed May 24 14:51:06 2017, Patrick Coleman-Smith, Examination of Console Logs -- and a couple of reminders
|
Quote:
I have tarred and zipped all 24 logs and |