CBUS Toolkit can't scan network

[BradJ]

Hi,

I decided to try out the new CBUS Toolkit, but it doesn't seem to like talking to CBUS through my Minder connection.

This is what CGate shows when I get toolkit to search for networks. I've tried forcing the comms settings to COM 2 (where Minder is), but it still complains in a similar manner. Is it because I am trying to communicate via Minder? Think its time to get a CNI.

Clipsal C-Gate(TM) v2.1.0 (build 2016)
License file not found.
Total network licenses: 0
20050101-125610 800 cgate - C-Gate started.
20050101-125612 803 cmd1 - Host:/127.0.0.1 opened command interface from port: 3
261
20050101-125620 751 //portprobe1 - Tag information changed at tag address: //por
tprobe1/Installation oldtag: null newtag: null
20050101-125628 751 //topology1 - Tag information changed at tag address: //topo
logy1/Installation oldtag: null newtag: null
20050101-125628 742 //topology1/NET0 - Network created type=serial address=COM2
20050101-125629 824 //topology1/NET0 - unknown response: ~~~ ***
20050101-125648 751 //portprobe1 - Tag information changed at tag address: //por
tprobe1/Installation oldtag: null newtag: null
20050101-125710 804 cmd1 - Host:/127.0.0.1 closed command interface from port: 3
261

[Duncan]

Hi,

I decided to try out the new CBUS Toolkit, but it doesn't seem to like talking to CBUS through my Minder connection.

This is what CGate shows when I get toolkit to search for networks. I've tried forcing the comms settings to COM 2 (where Minder is), but it still complains in a similar manner. Is it because I am trying to communicate via Minder? Think its time to get a CNI.

Clipsal C-Gate(TM) v2.1.0 (build 2016)
License file not found.
Total network licenses: 0
20050101-125610 800 cgate - C-Gate started.
20050101-125612 803 cmd1 - Host:/127.0.0.1 opened command interface from port: 3
261
20050101-125620 751 //portprobe1 - Tag information changed at tag address: //por
tprobe1/Installation oldtag: null newtag: null
20050101-125628 751 //topology1 - Tag information changed at tag address: //topo
logy1/Installation oldtag: null newtag: null
20050101-125628 742 //topology1/NET0 - Network created type=serial address=COM2
20050101-125629 824 //topology1/NET0 - unknown response: ~~~ ***
20050101-125648 751 //portprobe1 - Tag information changed at tag address: //por
tprobe1/Installation oldtag: null newtag: null
20050101-125710 804 cmd1 - Host:/127.0.0.1 closed command interface from port: 3
261


C-Bus Toolkit is NOT compatible with Minder.. you need a V2 or later C-Bus PCI. Sorry.

[BradJ]

Will a new Ethernet CNI be OK?

[Duncan]

Will a new Ethernet CNI be OK?


Yes, absolutely.

[BradJ]

Actually, before I spend the $$$'s on the CNI I'd better check.

CNI or PCI?

I'd rather get the CNI, because I'm already wired for it and I would think there's less chance of wiring / performance related issues, but what about software support? Will the CNI work with all clipsal CBUS software products that support a CBUS interface? I know you can't guarantee all products in the future, but does Clipsals way forward intend to support both CNI & PCI, or will I find newer products will come out with only PCI support, or will I find PCI is supported first and CNI later (i.e. likely much later).

The CNI is reasonably big biscuits, particularly when I thought I had my CBUS connection sorted via Minder, so I want to make sure I am making the right decision.

Thanks,
Brad.

[Duncan]

Hi Brad,

A CNI is a very safe choice and offers flexibility over a PCI. All of our software will always support both CNI's and PCI's thanks to the extensive work we've completed in C-Gate (the Java abstraction layer for communication from PC -> C-Bus). I cant conceive of a situation where a software package would come out that supported PCI's and not CNI's.

Hope this helps.