Page History

...

• The remaining (8) FEB's were flashed with firmware image 0xD0000000.  Ben or Ryan can provide a list of fixes/improvements that this version of the firmware contains.
• The FEB's were powered on, and the links were all checked.  A large amount of errors were immediately seen on  DPM 3/Data Path 0-2 and DPM 0/Data Path 0.  The first group of links that had errors were all associated with the same FEB.  It's harder to tell if this is the case with the errors on DPM 0/Data Path 0.
• Two fibers  (F & H)  were switched at the back of the COB in order to check if the link errors followed the DPM.  After the switch, the link errors were observed on DPM 10/Data Path 0-2.  This is where they were expected to appear if the errors were due to something downstream of the DPM.  This eliminated the DPM as being the cause of the link errors.
• After switching the fibers at the back of the COB back to their original position, the same fibers were switched at the flange.  Once again, the errors showed up on DPM 10/DP 0-2.  This eliminated the fibers from being the problem.
• The problematic links were then traced to FEB 6b.  In order to check if the problem was originating upstream of the FEB's, high speed cables 6b and 6t were switched. This was done through the side windows on the SVT box and was relatively easy to do. When this was done, the errors began to appear on DPM 5/6, which were the DPM's that were connected to 6t before the switch.  This seems to indicate that the link problems were originating from the FEB and not upstream.  We switched back the high speed cables to their original state.
•  Finally, we switched the high speed cables connected to 6b and 6t at the flange.  Once again, we saw the same behavior observed during 5 above. This confirms that the link errors were being generated by the FEB's.
• The system was let run for a few hours and the links were logged in order to check long term stability.

2015-02-16

New GUI to check hybrid sync status is now active:  svtHybSync.adl. 
It now contains information about the sync status for the FEBs. It looks like it’s working: I can see that the powered FEB right now has sync 0x0 for all data paths. The other don’t have a “valid xml” which make sense. We can change the error codes later. Please look at this and tell me if this status corresponds to what your expect. Below the sync I have information about the data DPM’s. It will allow us to see the status and configuration of all DPM’s. I’m also adding the link errors to this GUI. It works but I have turned it off now as it’s too slow. I’ll be working on that tomorrow morning. (Pelle)