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

SUServo channel number confusion #1048

Closed
cjbe opened this issue Jun 4, 2018 · 3 comments
Closed

SUServo channel number confusion #1048

cjbe opened this issue Jun 4, 2018 · 3 comments
Assignees
Labels
Milestone

Comments

@cjbe
Copy link
Contributor

cjbe commented Jun 4, 2018

The suservo DDS channel numbers seem to be in a nonstandard order: suservo channel 7 is urukul0 channel 0, whereas I would experiment channel 7 to be urukul1 channel 3.

I am using the suservo example experiment (https://github.com/m-labs/artiq/blob/master/artiq/examples/kasli_suservo/repository/suservo.py) and the following phy incantation:

eem.SUServo.add_std(
    self, eems_sampler=(5, 4),
    eems_urukul0=(1, 0), eems_urukul1=(3, 2),
    t_rtt=15+4)
@jordens
Copy link
Member

jordens commented Jun 5, 2018

Are you sure? Do you mean both profile settings and rf switch of suservo0_ch0 end up acting on urukul1, ch3? I just checked again with the code in master (gateware and example) and it's fine there.

@jordens jordens self-assigned this Jun 5, 2018
@hartytp
Copy link
Collaborator

hartytp commented Jun 5, 2018

FWIW, I didn't see this in my tests, although they do predate the new eem.SUServo code.

@cjbe
Copy link
Contributor Author

cjbe commented Jun 5, 2018

@jordens this was a experiment / device_db mixup at my end - not an Artiq problem.

@cjbe cjbe closed this as completed Jun 5, 2018
@jordens jordens added this to the 4.0 milestone Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants