The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Latest xPLHal Released


  • Subject: Latest xPLHal Released
  • From: Tony Tofts
  • Date: Sat, 27 Dec 2003 11:14:00 +0000

Hi All,

The latest service and exe versions of xPLHal have been uploaded to
www.xplhal.com

Changes/Enhancements are

A) Added new scripting function mymsg=xpl.loadbody(<body filename>)

This has been added to save time scripting repetitive messages
It loads a pre-written message body from Scripts\Messages folder (e.g.
x10a.txt)
Note: Using the vbscript 'replace' command it's possible to then change (if
required) variable components of the loaded message body before sending
(e.g. an x10 device - replace {x10} with A1)

B) Config amendment

When a new xpl device appears on the network with the hbeat (rather than
config) message schema it is now sent a request for it's config settings
only once, rather than on each heartbeat. This reduces the amount of
traffic
on the network with regards to devices that do not support the config
schema

C) Config Device list

When xPLHal closes it now saves the current device list to
xplhal_devices.xml and reloads it on start.

D) Hub Connection List

When xPLHal closes it now saves a list of the current hub connections to
xplhal_hub.xml and reloads it on startup. This way if xPLHal is rebooted
(say for an upgrade) instead of devices being deaf until they next
heartbeat, they are instantly alive.

For both C) and D) above, if the heartbeat timeout has been reached (2 *
interval + 1) then the devices are removed from the lists. This prevents an
old list being loaded in the event of an unexpected long shutdown (e.g.
power failure).

Regards
Tony






xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.