Skip to content
This repository has been archived by the owner on Mar 12, 2019. It is now read-only.

Understand why LV1 get into configured before all supervisors completes init #263

Open
kakwok opened this issue Mar 23, 2017 · 0 comments
Open

Comments

@kakwok
Copy link
Collaborator

kakwok commented Mar 23, 2017

This is observed during localDAQ testing in 904. Need to investigate deeper.
The progress bar shows correct configuration progress in this case and LV1 status changes to configured way earlier than progress bar getting close to 100%

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

No branches or pull requests

2 participants