...
Relevant Functional Block Diagram
to be added
...
Software Actions
Action | Notes | |
---|---|---|
1 | Green controller 1: take pressure measurement | Value reported as telemetry (see below) |
2 | Green controller 2: take pressure measurement | Value reported as telemetry (see below) |
3 | Red controller 1: take pressure measurement | Value reported as telemetry (see below) |
4 | Red controller 2: take pressure measurement | Value reported as telemetry (see below) |
5 | Green controller 1: turn pump on | |
6 | Green controller 1: turn pump off | |
7 | Green controller 2: turn pump on | |
8 | Green controller 2: turn pump off | |
9 | Red controller 1: turn pump on | |
10 | Red controller 1: turn pump off | |
11 | Red controller 2: turn pump on | |
12 | Red controller 2: turn pump off |
...
Description | File | Source | |||||
---|---|---|---|---|---|---|---|
1 | SPC Controller Spec Sheet |
| |||||
2 | SPC Controller Manual |
| |||||
3 | SPC ModBus Register Map |
| |||||
4 | SPC Firmware |
| |||||
5 | SPC Labview Drivers |
|
...
Relevant Software
Description | File | Source | ||||||
---|---|---|---|---|---|---|---|---|
Snippit from device manual explaining simplicity of telnet connection. SG tested this with PuTTY and it works; simplest command to test is the device name:
which should return:
| From page 14 of “SPC Controller Manual”, posted just above. Full command list starts on page 19 of same manual. (Steve is annotating the command list for KPF’s needs) | |||||||
Python code that Steve lifted from web, slightly modified, and found it worked! Key part in here (I think) is the command structure; this is the 'Read Pressure' command:
|
| https://gist.github.com/tspspi/779d96f305f719082d2db1e201856375/revisions | ||||||