This is an approximation of the steps involved in duplicating what I've done.
I use Ubuntu Linux on my home computer, and run Windows XP on a VMware instance inside it. Ubuntu and VMware versions do not matter. vrDIALOG claims compatability with Windows98ME, 2000, and XP. If it worked under Windows Server 2003 (which I haven't tested), that might be better - see about the rdesktop issue below.
In a world of free electricity and unlimited space it might be better to run Windows on a separate computer - but as I need a Linux box anyway, I use VMware rather than run another computer continuously. Alternatively, it ought to be possible to run the perl/bash parts under Windows using something like cygwin. It might be possible to just run vrDIALOG under WINE but getting the USB interface to work that way might be difficult.
vrDIALOG is available from plumber's merchants. I have version "v2.1.2.18". There isn't any changelog or facility to download newer versions from Vaillant as far as I am aware.
The virtual machine is configured to boot automatically when the host boots, login automatically, and then (if USB worked properly) all that should be required is to put the AutoHotKey macro into the startup group, for a proper unattended startup to work. Unfortunately this doesn't work - see below about the USB issue.
The host exports a file share to the VM using samba, and the VM mounts it automatically at startup. vrDIALOG is installed as per the instructions (usual "insert cd, next-next-next" type thing).
Although it's not a configurable option in the menus, it's possible to get it to log to a different location by editing the registry, searching for "Software\HolschSoft\vrDIALOG810\LastPath" and editing the "log" key to a directory (which must exist) on the samba share. It creates a new logfile with sensible filename of the form YYMMDD-HHMMSS every time logging is started; it also closes the old file, and starts a new one, at midnight. The write buffer is flushed every few minutes, not every line, so most of the time the last line of log data in the file is incomplete.
It was then necessary to get the USB interface to work. The USB device which ships with vrDIALOG has USB ID "1482:1005" and claims to be a "Vaillant VRD-USB PC-Interface" - occasionally it's mis-identified as "Ricoh USB Device", in which case it must be disconnected and reconnected before it will work. At startup, the USB device seems to fail to initialise correctly if the eBUS is connected; no error is given, but vrDIALOG gives an error when it attempts to scan the bus. It was definitely more troublesome when connected via a USB hub.
Before starting to look at macro automation (the AutoHotKey part), I got logging working. I set vrDIALOG to log every 1 minute and not log configuration data. It is unfortunately a little bit flakey and occasionally changes the order of fields in the CSV file. It's best not to minimize the vrDIALOG "data" window once opened, as it sometimes will then refuse to maximise again.
The AutoHotKey macro starts vrDIALOG, starts logging, and then waits for a trigger to either switch on, or switch off, the heating.
The logfiles are processed by a perl script that attempts to work out whether each log line is valid or corrupted, extracts the 'interesting' fields and inserts them into an RRDtool RRD. A bash script, does the dirty work of working out which the last two files are and extracing the last few lines from each, then calling the perl script.
vrDIALOG allows most (but not all) operations which can be made from the boiler and programmer/timer/compensator controls, to be made from the PC. It logs all the data which can be read from the boiler controls, but is much easier to use and quicker. There is no document listing all the field names; they (and the ordinary controls) are not always easy to match with what's in the boiler and controls documentation.
The list of logfile field names is here. Some are labels, some are always zero/null/empty, and some are duplicates.
There is an access database file with the software, which contains much
hidden treasure in respect of explanations of the field names and insight
into what they are used for. I've not made much progress with this yet.
Questions? Comments? Email strowger(atsign)hx7.net
All of my 1-wire adaptors and sensors are from Sheepwalk Electronics