xhaju / lab-nanny Goto Github PK

Should we add information about the contents of the different channels in the database? (as in, whenever a node connects, provide a mapping (chX)-> (content of channel X) with the contents of that channel.

This way, when we look back at the contents of the database, the mapping of the different channels is accessible.

In Windows 7, the serial connection seems to be reset every 30 seconds, with about 3 seconds re-connection time.
According to http://forum.arduino.cc/index.php?topic=131739.0, this can happen if the DTR line is taken low by software for too-long a period of time. This may not happen if powered from somewhere outside of arduino (e.g. using the 5V or the 3.3V inputs)

We need to avoid potential intruders to access and control the digital channels of the lab.

To do this, see the tornado's websocket "check_origin" method.

Also:
http://stackoverflow.com/questions/25058708/tornado-web-request-origin
https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS#Origin
https://www.christian-schneider.net/CrossSiteWebSocketHijacking.html

Node sitting in the lab seems to disconnect after a while, throwing a "Type Error". Needs check and followup

To help in debugging and running, it would be useful to be able to observe master's state

While emulation in *nix systems is done through TTYs, in a Windows system those are not available.

Right now, handshakes (which allows us to change digital pin values) are very basic. Could use a rewriting of this to give it more generality.

Currently, conditional behaviour happens at the client side, but this can have several drawbacks (like the client not being connected...).
It would be interesting to implement similar, centralised behavior at the master-server level.

Change floats -> bits

Perform actions based on conditions (for example, if ch0<0.5V, turn digital channel 13 HIGH, etc.)

Such as client/node connections/disconnections. This would allow to build a more comprehensive view of the master server's performance.

It may happen that, if I turn (let's say) Pin13 HIGH in my client page, the rest of the browsers might not update their behavior.

Could we share the state of the arduinos using the same dictionary used to broadcast the analog readings?
Something like: DCHANNELS='01000111' if channels 1, 5, 6, and 7 are HIGH.