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

G4 Tutorial design your own run protocol #27

Open
6 tasks
floesche opened this issue Oct 27, 2020 · 0 comments
Open
6 tasks

G4 Tutorial design your own run protocol #27

floesche opened this issue Oct 27, 2020 · 0 comments

Comments

@floesche
Copy link
Member

  • The panel_com wrapper – 1st paragraph, misspelled please
  • Change screens to panel controller
  • When you use Panel_com you are getting matlab to talk to G4Host, so you are using the same software just with the additional step matlab step.
  • Penultimate paragraph - If this is the only place it is explained, you might want to add that it will wait for tcp connection (opening a communication channel from matlab). And before you can run a command in matlab you should see that a tcp connection was initiated (forgot the actual phrasing)
  • You cannot create new panel_com commands because the host can only read the defined commands. Even if you know what hex string to send, the host still needs to implement it. and that is done completely in labview
  • Default run protocol – this is awesome and potentially really helpful.
    Perhaps add headings in the code and refer to them instead of the code lines, since those might change

This issue is part of the second feedback round, received 2020-10-26.

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