Comfort event log files auto download and save

[Guest]

Is it possible to send a request to comfort from a pc to download the event log and save it in a particular directory?

I know that E? will report one \'line\' of the event log, but what I would like to do ideally is send a command every 2 weeks which will present me with a complete log. (2 weeks is about 240 entries.)

If this not possible via external requests, is it possible to do this via internal programming?

[admin]

Would that be possible with a script in Homevision XL?

[Guest]

I\'m sure a script could be written, what I\'m unsure of is the way to do it. In Configurator for example, when I press the button to upload the log, am I actually sending a string of E? commands, one after each receipt of data, and then ceasing once the \'FF\' string is received?

[admin]

The format of the E? commands are in the Comfort Serial command document found in
https://www.cytech.biz/Default.aspx?cmd=sQ0OYE9X66w%2b0P%2bAcFsmAI3j73Rwtfrj&fileid=163&dcid=8&pageindex=

Extract from the re;event part below

[img]file:///C:/DOCUME%7E1/LUCHIU%7E1/LOCALS%7E1/Temp/moz-screenshot-1.jpg[/img]PC: E?00
UCM: EVnn (byte1) (byte2) (byte3) (byte4) (byte5) (byte6)
PC: E?
UCM: EVnn (byte1) (byte2) (byte3) (byte4) (byte5) (byte6)
PC: E?
...
PC: E?
UCM: EVFF (no more events)

nn  is the event number 0 to 0FFH in memory. The event number is NOT a chronological  number from firts to last. It is the number of the event log slot in memory. When the event log is full and new events are added, the oldest event is overwritten by the new one. The position of the oldest event thus rotates through the event log memory

When the number of events exceeds 255, the number will roll over to 00, ie only the least significant byte is sent. This is to maintain compatibility with older software and hardware where only 255 max events are available. Comfort Ultra II has 600 events while OPT has 255 events
Hence the software application should not give any meaning to the event number in the message

The Event Log is a first-in first-out buffer.As new events are added, the oldest event gets lost.
The event log is sent 1 event at a time. The application starts by sending E?00 to request for the first event (only the first event is valid to start the event log). When UCM EV message is received, the application should send an E? Message which shall fetch the next event in the event log. If there are no more events, the UCM will reply with FF in the event number field
Byte1 is the month MM 01 to 12 in decimal
Byte 2 is the day DD 01 to 31 (decimal)
Byte 3 is the hours HH in 24 hr format 00 to 23 (decimal)
Byte 4 is the minutes MM 00 to 59 (decimal)
Byte 5 is the event code according to the following list
Byte 6 is the event parameter according to the following list (in the document)