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.

Sign up for GitHub

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

Jump to bottom

su-servo: rtio collisions + done #1028

Closed

hartytp opened this issue May 31, 2018 · 1 comment

Assignees

Labels

area:documentation area:su-servo

Milestone

Collaborator

hartytp commented May 31, 2018

please can you document what the done parameter from get_status means, and how (if at all) it is intended to be used by users?
possibly related question: what is the expected behaviour for back-to-back calls (no delay between them) to set_config(enable=0) 'set_config(enable=1)

The text was updated successfully, but these errors were encountered:

jordens self-assigned this

jordens added area:documentation area:su-servo labels

jordens added this to the 4.0 milestone

Member

jordens commented May 31, 2018

ACK. A couple comments:

Done pulses during regular operation each time a servo iteration is complete. When disabled it becomes permanently asserted when the pending servo cycles are complete.
set_config does not support replacement (unlike the per-channel RTIO control interfaces) and should leave the servo enabled. In t_servo/t_RTIO cases it would delay the next servo cycle by one RTIO cycle (when the restart coincides with the time between the two memory accesses).

jordens closed this as completed in

5dbdc56

jordens modified the milestone: 4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment