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

Twisted based SSL networking #20

Open
ThirteenFish opened this issue Sep 11, 2013 · 0 comments
Open

Twisted based SSL networking #20

ThirteenFish opened this issue Sep 11, 2013 · 0 comments
Milestone

Comments

@ThirteenFish
Copy link
Member

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 Secure Command Channel.

Over the SCC the Kivy app sends set relay commands (shorepower, igniter) and a heartbeat containing an as yet undecided message to the LTC. The LTC sends a heartbeat containing relay states, relay changed events, and set relay command failed to the Kivy app.

The Kivy app should also display some sort of connection information about the SSL link. Connected/disconnected for sure, but also packet loss, etc?

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