Fired when a command was received from the desktop software for an expansion board
Fired when the client wants to find out which boards are connected
Fired when the client wants to find out which boards are connected
Fired when the client wants to find out which boards are connected
Fired when the client receives a line of cached data
Fired when a client requests a download of a particular session
Fired when the client has requested a status list update, TcpServer as argument
Fired when the client has a completed session list received from the server
Fired when a board has finished processing a data line
Fired when the expansion board receives a data row for processing during a download. Allows pre-processing of data
Fired when the client requests the server to delete a logging session from the database
Fired when the client wishes to force the board to be RESET to fix an error
Fired when the client has requested a connection to the data logger
Fired when an error was received by the client from the data logger
Fired when logging starts on the server
Fired when logging stops on the server
Fired when the client loses the TCP connection (after three attempts)
Fired when plugins are loaded
Fired when an asynchronous process finishes to allow clients to update the UI
Fired when an asynchronous process starts to allow clients to update the UI
Fired when expansion boards should be registered with the board manager
Fired when the client requests a status update from the server
Fired to let subscribers know a message is ready to be received from the reply queue. Normally should only be subscribed to by the Application