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]

Re: Re: motion detectors: need some input




Tom Van den Panhuyzen wrote:

>Would this be a feasible scenario:
>
>1) standard motion detectors
>2) connected to a VIOM unit
>3) connected to an MSS100
>4) connected to the LAN via a wireless access point
>5) another wireless access point on the already existing hub
>6) xpl-messages on the LAN
>
>Questions:
>Between 1) and 2): the VIOM detects the open/close state of a motion
>detector ?  No extras required ?
>
>6) I do not understand how RS232 signals are packaged and put on the
>network... What is needed to interprete these packages ?  Will it work
>with John's xPL VIOM interface ?
>
>Thanks,
>Tom
>
>
One other possibility - instead of the VIOM use a NETIOM (still from
Phaedrus). This would save on an MSS100 (doing myself out of a sale
here). The Netiom is effectively an Ethernet connected version of the
VIOM , with a slightly different feature set.  The NETIOM will be
available shortly from Phaedrus  with xAP firmware inbuilt or (likely
better for you as you wouldn't need to bridge it with an xPLHAL script)
xPL firmware which is I believe provided by Lehane on this list. Your
PIR's will now not be 'serial tunnel' or PC dependent and will send
trigger information out directly on Ethernet, this removes a few
dependencies which should make it quicker, more reliable and
surprisingly .... cheaper

Kevin



xPL Links: http://www.xplproject.org.uk http://www.xplhal.com http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx
To Subscribe:  ukha_xpl-subscribe@xxxxxxx
To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx

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.