simple_connect
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| simple_connect [2026/05/26 14:03] – pklapetek | simple_connect [2026/06/01 15:08] (current) – pklapetek | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Connection test ===== | ===== Connection test ===== | ||
| - | This simple client | + | This simple |
| - | Used commands: | + | It connects to the Gwyscope server and gets raw information about server start time. After that it reads 20 values of what is the actual “error signal” and exits. It can be used to learn how to set up the connection over Ethernet and how the Gwyfile object based messages used for communication are set up and passed through the connection. |
| + | |||
| + | Used commands | ||
| '' | '' | ||
| Line 10: | Line 12: | ||
| Note that as the “error signal” depends on the actual operation regime, also called “mode” (proportional feedback, amplitude feedback, etc.), as defined in hwserver.ini file on the server, the reported value of error signal can have different meanings, to control it, set also “state” command as in the next examples. Similarly, the setpoint parameter and PID settings depend on actual realisation of the feedback loop, direction of the signals defined in hwserver.ini, | Note that as the “error signal” depends on the actual operation regime, also called “mode” (proportional feedback, amplitude feedback, etc.), as defined in hwserver.ini file on the server, the reported value of error signal can have different meanings, to control it, set also “state” command as in the next examples. Similarly, the setpoint parameter and PID settings depend on actual realisation of the feedback loop, direction of the signals defined in hwserver.ini, | ||
| + | |||
| + | To explore it further, see the [[https:// | ||
simple_connect.1779797034.txt.gz · Last modified: 2026/05/26 14:03 by pklapetek
