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
We're moving networking code from the Phidgets webservice to our own Twisted based code. This involves an SSL based Secure Command Channel for setting relays and a UDP/PSASMessage telemetry feed for non-critical information. This issue deals with the telemetry feed.
This should be a read only link from the LTC and also the Kivy app to the telemetry server containing all sorts of interesting information. For the Kivy app this mostly is just arm state enabled and possibly a countdown. For the LTC this becomes more complex, essentially a log file as its file system is in read-only mode. It must have sensor and relay information, but also it might include errors/exceptions, SSL connection stats, etc.
The text was updated successfully, but these errors were encountered:
We're moving networking code from the Phidgets webservice to our own Twisted based code. This involves an SSL based Secure Command Channel for setting relays and a UDP/PSASMessage telemetry feed for non-critical information. This issue deals with the telemetry feed.
This should be a read only link from the LTC and also the Kivy app to the telemetry server containing all sorts of interesting information. For the Kivy app this mostly is just arm state enabled and possibly a countdown. For the LTC this becomes more complex, essentially a log file as its file system is in read-only mode. It must have sensor and relay information, but also it might include errors/exceptions, SSL connection stats, etc.
The text was updated successfully, but these errors were encountered: