RE: HomeVision and C-Bus

["Kevin Hawkins" <lists@xxxxxxxxxxxxxxxxx>]

=20

> -----Original Message-----
> From: Mark McCall [mailto:lists@xxxxxxx]=20
> Sent: 24 June 2004 16:37
> To: ukha_d@xxxxxxx
> Subject: RE: [ukha_d] HomeVision and C-Bus
>=20
> > HV will require one serial port connected permanently to=20
> the C-Bus=20
> > RS232 module. It may however be temporarily swapped back=20
> to facilitate=20
> > programming of either C-Bus or HomeVision.  Are most=20
> people happy with=20
> > this ??
>=20
> I bought a 2nd hand additional HV serial port with your=20
> board in mind Kevin.

I know I tried to buy that same one !=20=20
You do need to be able to run the latest ROM's - and some very early
HomeVision units can't do this. I thought yours was one in this category or
have you sorted this ? - Didn=92t you buy unit #0004 or something :-)

>=20
> > If I
> > provided a HomeVision additional serial port extension=20
> box (similar to=20
> > the existing serial port expansion) but with a direct=20
> C-Bus connection=20
> > inside would people be interested in buying such an add on ?
>=20
> Is this all that's required for HV to drive C-Bus?=20

Yes it would be all that is required for the 'macro' solution, it is
probably about half the cost of the gateway solution (=A3100+VAT vs =A3199)

Or is=20
> this the solution that requires lots of Macros unlike your=20
> "hardware" solution.

This is the macro based solution - it uses more macros and more resources
e=
g
variables and processor time within HomeVision and also does not handle
instant synchronisation with C-Bus - although it does over time.  My
'hardware' solution already has inbuilt C-Bus so not a problem and performs
faster with less demands on HomeVision, it also has power on synch.
Actuall=
y
both solutions need extra macros but the software only solution needs more.

K