Project

General

Profile

Bug #23567

sbndaq - Bug #23554: Triggers but no fragments

BNL WIBs sending data not properly formatted

Added by Iker de Icaza Astiz about 1 month ago. Updated 12 days ago.

Status:
New
Priority:
Urgent
Start date:
11/07/2019
Due date:
% Done:

80%

Estimated time:
Spent time:
Duration:

Description

Hi Mayank

There seems to be an issue with the optical communication with WIB's and TPC.

Ideally there should be a check in the code to make sure the data being send along is OK. Granted, I have no idea if this is feasible.

Besides troubleshooting the cause for this, please also make an entry in the wiki to document the cause and solution.

This is related to issue #23554

Feel free to change assignee.

History

#1 Updated by Jose Ignacio Crespo Anadon about 1 month ago

  • Subject changed from BNL WIBs not sending data or not properly formatted to BNL WIBs sending data not properly formatted

#2 Updated by William Badgett about 1 month ago

I suggest trying the older WIB we used in the VST last year with a single QSFP. We have seen "real" fake data from the older WIB, but not (so far) from the production WIB currently in place

#3 Updated by Mayank Tripathi 12 days ago

  • % Done changed from 0 to 80

Problems: 1) BNL WIBs not sending Data.
2)BNL WIBs sending data but not properly formatted.

Cause and solution for 1) The PTB not being tight enough on either the PTC or the WIB caused the BNL WIB to stop sending data. After trying to snug them in, the data was received fine.
Cause and solution for 2) Even when the data is received some channels showed 0xBAD, which is a holdover from WIB testing that doesn't affect the data and only is in WIB channel ID mode. There were some other unexpected elements, like in FEMB ID 0x0007 we could see 0x5BC and 0x0038. Jack expects a bit of weirdness in the channel ID mode with this FW. This will most likely be fixed in the next firmware version.



Also available in: Atom PDF