Toolkit not opening network with CNI2?

Best wishes.

 

I had an almost identical problem last year. Kept scratching my head also until i realised that the CNI only allows one connection at a time and we had a C4 controller on the project. Maybe you have something similar??

 

Hi Jonny,

Thanks for the feedback. I was aware that only one connection is allowed at a time to a CNI. That said I wonder why the C-Bus Diagnostic Utility reports "Connection already in use" ?

Doing this at bench at home, there is no other Clipsal device or other product for that matter that would look to control a C-Bus Ethernet network ( C4, Ness etc).

I have ensured that the IP address assigned to the CNI is not in conflict with any other on the network. I have tried two other IP addresses which are no where near other used IP address on my network. Made sure I am using the correct gateway and subnet mask etc.

Ensured TK is trusted by Windows Firewall....

I can see the CNI on the network when I ping all on the network. I can remove the CNI and it disappears and nothing else is on that address. I can ping the CNI and I get a correct response. I can connect to the CNI via the C-Bus IP Utility which doesn't use C-Gate.

I have done a complete install of 1.15.2 with the associated version of C-Gate.

All I have on the bench is the CNI2 other that the 12vDC power supply nothing else is connected to the unit. No C-Bus devices just Ethernet via a switch. Could not be simpler.

 

No question is ever dumb Nick...I power cycled lots of times over the last day or so. Also reset the unit a number of times.

Thanks for hopping in with your suggestion...

 

Problem now is sorted.

I needed a powered C-Bus network on the CNI and it connected with no issue.

I blew the dusted off a faulty relay unit that had a power supply that been in a lightening strike event located a shorted Zener protection diode, lifted that and the C-Bus port woke up again. Connected that to the CNI and viola it connects without any issue.

Thanks to Mr Mark for pointing it out. Thanks also to all that helped out...special call out to DarylMc who went above and beyond to help...cheers DarylMc

I should have remembered my C-Bus training and the requirement for clock and burden. Also I should have never assumed the Ethernet and C-Bus networks were agnostic to each other.

Anyway feedback for anyone else who tries to the same as me.

Cheers,

Ian