Skip to content

Dev: No ability to boot a multi crate system. #299

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

Open
ntbrewer opened this issue Sep 18, 2017 · 5 comments
Open

Dev: No ability to boot a multi crate system. #299

ntbrewer opened this issue Sep 18, 2017 · 5 comments

Comments

@ntbrewer
Copy link

Looking at the code I don't find a way (master or Dev) to boot two or more pixie crates.

I'm creating this issue so I can contribute to the solution. I have an interest to fix this in Acquisition and Interface for boot and poll2. There should be a method in scan which also accommodates this function, I suppose, but I don't use it currently and I can't support it easily.

Who wants to help?
Or should I branch?

@ksmith0
Copy link
Contributor

ksmith0 commented Sep 18, 2017

This is something I was gearing up towards accomplishing, but never was able to get the time to finish it. The project requires some extra hardware to connect the two crates together and to be able to speak to both controllers. As I recall, I was able to get a machine (r230) to communicate with two crates, but the booting was confused as to which crate contained which module. This may require some fine tuning to the XIA API or the PAASS Interface. There was no way to specify that a module lived in crate 0 or 1 and it wasn't immediately obvious how to tell the API in which crate I was interested.

@ntbrewer
Copy link
Author

I am finding that to be true myself. I'm rereading the app files and includes from xia. I'm meeting tomorrow to discuss in person moving this part of development forward. Thanks for clarifying what has been done.

@ksmith0
Copy link
Contributor

ksmith0 commented Sep 21, 2017

What do you mean meeting in person?

@tking53
Copy link
Collaborator

tking53 commented Sep 21, 2017

With me. He came to UT to pickup the inter-crate comm hardware.

@xia-stan
Copy link

This functionality is not supported by PixieSDK. At this time, it's impossible to tell which module lives in which crate.

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

No branches or pull requests

4 participants