Note: The SIXNET I/O Tool Kit now includes a Datalog Server driver that accepts logged data from a SIXNET client and creates ASCII text files from the data. This server software should be suitable for many applications involving client initiated data transfers. The following information is provided for software developers who wish to write their own datalog server software.
When a SIXNET station acts as a datalog client, a simple driver is needed at the server end to parse the received messages, store the data into the database in a manner appropriate for the application, and acknowledge the message. It is also possible for the reply message to synchronize the clock in the remote station and assign a new reporting time by passing parameters back in the acknowledgement reply.
Please note that programmers familiar with the SIXNET Universal Driver will find that this documentation suggests a few new simplifications in the message header. These innovations are fully compatible with all existing data formats for all existing Universal Driver messages. Please be assured that if a slave driver is implemented to receive these datalog messages, no other considerations for future compatibility with expanded capabilities need be considered. This is the only message that needs to be implemented to receive datalog records from a SIXNET client.
Refer to the following topics for information on the message sent by the client station, and the required responses.
Datalog Client Message Definition
Overview to Message Simplifications
Including a Control Character in a Message String
Suggestions for Writing a Robust and Flexible Data Transfer Interface