Kleptomania Control Infrastructure communication specifications

Communication with each team

For receiving clock signals:

Listen at port 4122. Control server connects each time for sending a message to each machine at this port. The following messages are sent:

“Blue\n” for signaling the start of Blue Period

“Green\n” for signaling the start of Green Period

“Yellow\n” for signaling the start of Yellow Period

“Pause\n” for signaling the start of Pause Period

After sending the message, connection is closed.

To send an alarm signal

Connect at port 4123 to localhost. Send the message “Alarm\n”. You do not get any response weather or not alarm is accepted. After sending the message, connection is closed.

Imp: In both the cases a new connection is made for sending/receiving a new message.

A new connection is made every time in order to make it easier for the control server to detect any fault in the system, in which case it pauses the entire system after the end of the cycle.

Communication with the display server

Communication with the display server is done according to the communication specifications of the display server.

I suggest that none of the teams change any of their implementations for communicating with the control infrastructure as each team is able to communicate with the control infrastructure properly.

Currently, the control server only pauses the system if it has any problem in communicating with the registration clients. Do you want that it pauses the system if it has problem in communicating with any of the teams’ monitoring system i.e. it also detects if any of the monitoring system crashes down. What about in the communication with the display server.