Text

The watchdog messages begin with a date in the following format:

"dd/MM/yy HH:mm:ss.fff".

The date and time information is followed immediately by the text ",DatCo".

For each job a string is added with the following format:

"{Job name} : {w} to do, {x} done, {y} erroneous, {z} perm. failed;"

The meaning of the tags used in this format can be found below:

• {Job name} is the name of the job

• {w} is the number of the .dat files in the "to be processed" list of the job.

• {x} is the number of the .dat files in the "processed" list of the job.

• {y} is the number of the .dat files, which could not be executed for one or more tasks.

• {z} is the number of .dat files which have shown a constant failure for one or more tasks.

Binary

The binary version of the watchdog consists of 4 general integer values and for each job another 7 integer values. Each integer value is 32 bits long (4 byte).

The message length is limited to 464 byte, comprising the information for 16 jobs. (4 * 4 byte + 16 * 7 * 4 byte = 464 byte)

Bytes for unused jobs contain zero values.

The table below contains the description for each integer value.

Structure of binary watchdog message:

	Byte	Description
	0	Telegram counter; every time a telegram is sent, this value is incremented by 1.
	4	Current version number; the current version number is set to 1.
	8	Reserved integer, currently with the value 0
	12	Reserved integer, currently with the value 0
Repeated for each job max. 16 jobs	16	Job status; the value is 1 when the job is started and 0 when the job is stopped.
	20	The number of DAT files in the "to be processed" list of the job
	24	The number of DAT files in the "processed" list of the job
	28	The number of DAT files, that could not be executed for one or more tasks
	32	The number of DAT files that show a permanent failure for one or more jobs
	36	Reserved integer, currently with the value 0
	40	Reserved integer, currently with the value 0
	44	Job 2
	72	Job 3
	100	Job 4
	...	...
	436	Job 16