Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PLL unlocks hard to deal with #72

Open
darrylmasson opened this issue Mar 12, 2020 · 0 comments
Open

PLL unlocks hard to deal with #72

darrylmasson opened this issue Mar 12, 2020 · 0 comments

Comments

@darrylmasson
Copy link
Collaborator

This blurs the line between a hardware problem redax isn't supposed to deal with, and a software solution that redax could be responsible for.

If something wonky happens with a digitizer's PLL input, the board's behavior deviates from normal. The board will reacquire its PLL lock after a second or so, but it's now at a different phase in the clock cycle. Resetting the PLL lock of one board invalidates the PLL lock of all the boards down the clock chain.

Boards perform the PLL lock procedure when they boot, so traditionally when one needs to reset the PLL one reboots the crate. This is tedious and requires manual intervention. As redax lacks the inter-process communication necessary to access sequential digitizers mounted in a VME crate, an alternate solution would be to have a crate controller in each crate that instructs each digitizer to reset its PLL lock. The arming sequence then would begin with each crate controller going down the clock chain and resetting all boards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant