3rd Party Sensor Developers Manual

This page is for sensor hardware developers only!!!

Please read here on which ports the system listen to, under which protocols and why. Once a connection on a TCP server has been established, a register message is sent from the sensor to the system. If the message is accepted by the system, the sensor is registered to the system and is allowed to send data. If the registration request was rejected, the sensor will keep trying to register, until it succeeds or aborted by the user.

The system acts as a server that is always responsive and ready to handle new connections from sensors (they are the “clients”). Each time a new connections is opened, a thread is created which handles the communication with the relevant sensor.

Each time a sensor wants to send data, it initiates an Update Message and sends it using the connection opened before. When the message is received by the system, it is stored inside a database, available for future use by the applications. The amount of update messages that can be sent each second is limited for 100 messages. We chose to use TCP because we wanted to ensure that all the messages will reach their destination.

Each time a inner-system component wants to send an instruction, it will initiate it though the filesystem, sending it on the paths described on subscription. The sensor is responsible to check his input stream connection with the system for any pending instructions.