You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At some point, we'll need to have an interface with LabView where we have both LabView and Dionysos running and LabView sends the state coordinates to Dionysos and Dionysos reply with the control to use.
That will be needed of the controller is complicated and cannot be communicated to LabView.
Yousef told me that we could use https://www.ni.com/en/support/documentation/supplemental/06/basic-tcp-ip-communication-in-labview.html
Maybe it would be even easier to communicate with files: e.g., LabView write the states in a file in which Dionysos reads the state and Dionysos writes the control in another file in which LabView read the control.
This read/write could be implemented in LabView as a MathScript.
The text was updated successfully, but these errors were encountered:
At some point, we'll need to have an interface with LabView where we have both LabView and Dionysos running and LabView sends the state coordinates to Dionysos and Dionysos reply with the control to use.
That will be needed of the controller is complicated and cannot be communicated to LabView.
Yousef told me that we could use https://www.ni.com/en/support/documentation/supplemental/06/basic-tcp-ip-communication-in-labview.html
Maybe it would be even easier to communicate with files: e.g., LabView write the states in a file in which Dionysos reads the state and Dionysos writes the control in another file in which LabView read the control.
This read/write could be implemented in LabView as a MathScript.
The text was updated successfully, but these errors were encountered: