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: Visonic Powermax Security Alarm


  • Subject: Re: Visonic Powermax Security Alarm
  • From: Phil Dye <phil@xxxxxxx>
  • Date: Wed, 2 Feb 2005 09:14:11 +0000
  • References: <dab14ce05011905257da87214@mail.gmail.com> <20050119141040.1F61376ABF@spf6-1.us4.outblaze.com> <dab14ce05011906124161cea@mail.gmail.com>


On Wed, 19 Jan 2005 14:12:29 +0000, Phil Dye <phil.dye@xxxxxxx>
wrote:

> Although http://tinyurl.com/4785y suggests that
the BT VP1000 is _not_
> the same as the standard Powermax. If it turns out not to have half of
> those features, it'll be going back...

Well, I've only just gotten around to setting it up, and have found
the following differences;

- the hardware is essentially a Powermax, although the case is BT branded
- there are no inputs for the hardwired zones (29/30), or output for
external siren (although strangely one is available?). The solder pads
are on the PCB, but simply no connectors - a shaped blanking plate
covers the unused spaces.
- opening the case reveals a ROM labelled "BT" something; so
customised firmware I guess
- that firmware has no support for the hardwired zones (29/30), X10,
or notification to anything other than the supported central station
(ie Intamac).
- the sensors (one mag contact, two PIRs, one keyfob) appear to be
standard Visonic parts, with BT logos printed on the case.

All in all, whilst I'm disappointed it has some features missing, I
still think it's a good buy for the price, so I've kept it. Now, if
only I can get hold a genuine Powermax ROM, I suspect that'd bring
back all those features...

--
phil



UKHA_D Main Index | UKHA_D Thread Index | UKHA_D 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.