Toolkit not opening network with CNI2?

A head scratcher...

Got a CNI2 which Toolkit 1.13.2 won't recognise.

I have used the Control System IP Utility to configure the CNI2 without any issue. Scans fine, I can set IP, gateway, port address etc no issue. However when I set the these parameters in Toolkit and try to connect to the CNI2 it just times out with the "PCI failed to reset" message.

I have double checked the IP address, subnet, gateway, port address (10001). The IP address selected is not being used by any other device on the network.

Is there any gotchas with the CNI2? Only ever used the CNI before. Is the CNI installation manual the same for the CNI2? I don't have the installation manual that came with the CNI2 anymore.

Spinning my wheels on this one....

Thanks,

Ian

 

Hello Ian

https://updates.clipsal.com/ClipsalOnline/Files/Brochures/W0001407.pdf

Did you try power cycle the CNI?
Any other devices already using CNI?

Probably not this but I see you are using a fairly old Toolkit version.
There is some troubles if you mix and match some of the latest couple of Toolkit and CGate versions.
Check compatibility matrix if necessary.
http://www2.clipsal.com/cis/technical/downloads/c-bus_toolkit

I don't know if it affects everyone but Toolkit crashes if you scan a new network for me.
I have to add the new project manually.

What is the network?
Is it new hardware or a CNI which has been running for a while?

Good luck

 

Hi Daryl,

Thanks for your feedback.

Yes power cycled CNI, PC, LAN switch. Did all that basic stuff.

I downloaded 1.15.2 TK this morning but have not yet run that up to check. I am a bit old school if it ain't broke don't fix it. 1.13.2 worked fine on the last project and still is. I tend not to just update unless I can see a direct benefit, I am sure there are many here that will see flaw with this.

I have ascertained that the CNI2 is Ok as it is working fine using the IP Utility. So it is most likely a Toolkit and C-Gate and CN2 combination thing so I will run up 1.15.2 in the morning.

The network is fairly basic. TP-Link Archer 9 Modem/Router > TP-Link 8 port gig switch the CNI2 and laptop are connected to the switch. Works flawlessly with the IP Utility as I have stated earlier.

Will feedback how I get on for others...

 

Not so much a problem with old Toolkit I just wanted to mention different CGate and Toolkit versions can have problems working together.

 

Cheers Daryl will look into that too...

 

Which should not be an issue if you run the Toolkit installer.
Also consider Firewall.

 

Cheers...

 

Update.......

Installed TK 1.15.2 still no joy connecting.

Ensured Toolkit is on Windows Firewall OK to trust list and checked both private and public settings.

The IP Utility connects in milliseconds without any issue. I can configure the CNI2 no issue..

C-Bus Diagnostic reports RX: "Connection already in use<CR>"

Back to scratching my head....

 

Is it a new CNI?

 

No manufacturing date 29 April 2015

 

Can you telnet to 127.0.0.1 20023?
Then type "project list"
Then "net list"

That should show if CGate has loaded a project and opened a network.

 

I receive an " Invalid Command" message....

 

syntax error?
It does that first time every time.
Just try again

 

Hi Daryl,

Nope just keeps spitting out invalid command..... tried a number of times before posting again....

Just confirming 127.0.0.1 20023? After the prompt...

Also tried 127.0.0.1 20023 no joy...

 

for windows telnet
o 127.0.0.1 20023

other telnet programs
open 127.0.0.1 20023

 

I see what you did now.
o 127.0.0.1 20023

cgate will have to be running eg toolkit open or cgate service running.

 

Understood, yes Toolkit/c-gate was running....

The "o" open was the key am using Microsoft telnet

Now get "201 Service ready: Clipsal C-Gate v2.11.1 build 3243 #cmd -syntax=1.0

When I type "project list" it returns "124 no projects found"

 

net list

 

I think I am leading you astray here.
I should have just asked have you been playing with CGate config files lately.

Also I was wondering if there could be something else on the network using the CNI.
On my own network I just made 2 separate connections to my interface just to test the response.
It didn't complain so maybe not that.

Just a couple of things to mention.
It is known for people to have problems installing Toolkit to some location on PC other than default install location.

I'd check the power supply on CNI volts and polarity.
Check CNI indicator leds
That CNI looks to have a reset button maybe try that if you have not already.

 

See my answers below..