RE: C-Bus and HomeGate

["Kevin Hawkins" <lists@xxxxxxx>]

Hello Michael,



I have C-Gate here. I used it as my gateway for xAP before I
moved to direct support of the RS232 module. I also have HomeGate although
I
have done little more than run it up for a few minutes to prove it works.

Unfortunately I don't have a CNI (wish I did) so my C-gate
installation connects to C-Bus via the RS232. You have to configure the
interface that C-Gate uses to connect to C-Bus within the networks.txt file
- it can be quite finicky but I suspect less so with an Ethernet connection
than a serial one. I think this may already be working for you.

You need to check two things - first that C-Gate is running
correctly and has communication with the C-Bus network - you don't need to
run HomeGate for this. If that is OK then we can look at how HomeGate is
connecting to C-Gate. The only awkward things may be that I think the
version of C-Gate that is provided with HomeGate may be  a 'lite' version
and may not run with a  user interface - I can't remember.

To see if C-Gate is running correctly you can open a Telnet
session to one of its ports - I would suggest the event port (20024) or the
load change port (20025) as that throws out the most information. From the
command port (20023) you should also be able to issue commands to C-Gate.
You want to be using C-Gates port numbers  - not the CNI port - this is
only
ever used in C-Gate.

I do seem to remember there is something a little funny about
the network number. HomeGate has the facility to ammend one of the C-Gate
parameter files directly - and it needs to talk to Network 0 or 1 (can't
remember which offhand) - this bit is worth checking as you will get
nothing
without it. I assume you have a single network license ??  From your
description of an 'asynchronous socket connection' fail I am guessing that
the problem is between HomeGate and C-Gate , and not C-Gate and the CNI.



If that makes any sense than it should set you on the right track - if not
I
can probably talk you through it.



Kevin





-----Original Message-----
From: Michael Sanders [mailto:m_w_sanders@xxxxxxx]
Sent: 18 August 2003 10:33
To: ukha_d@xxxxxxx
Subject: [ukha_d] C-Bus and HomeGate



Hello everyone,

I have run into some problems with getting my C-Bus installation to
"talk"
to the C-Bus HomeGate software.  Although my installer is also chasing up
the issue (the relevant person at Clipsal is on leave!) I thought that I
would ask here as I am constantly surprised at the level of knowledge that
this group manages to pool.

Essentially, I am trying to get the HomeGate software to connect to the
C-Bus Network Interface (CNI) so that I can control anything on the C-Bus
network from HomeGate (and, therefore, my webpad).  The C-Bus installation
software works fine on the particular machine (so I know that the
connection
is good) but the HomeGate software refuses to connect to the CNI.

As I understand it, the HomeGate software relies upon C-Gate software to
connect to the CNI.  I have the C-Gate software installed and it seems to
connect to the CNI at the correct IP address (in my case 192.168.0.50).  It
uses port 14000 (which is set up as Channel 1 on the CNI).  However,
whenever it tries to send signals to the control port (20023) it fails.  As
a result, when I try to get HomeGate to connect to the CNI (either at port
20023 or port 14000) it gives me an "asynchronous socket error"
and refuses
to communicate.

I do apologise if this is complete Greek to many of the UKHA list - I'm
just
praying that someone, somewhere is using HomeGate (or C-Gate) through a CNI
and can let me know how they have it set up!

Thanks for reading this rather long post - I'll let you know if I get a
solution from Clipsal in the meantime in case it helps anyone else in the
future.

Kind regards,

Michael.


---------------------------------
Want to chat instantly with your online friends? Get the FREE
Yahoo!Messenger

[Non-text portions of this message have been removed]