Wiser Lock out

Hi guys,

Ive locked myself out of my wiser after resetting it following some connection issues. I cant access the set up gui.
Im broadcasting on the 10.0.xx.xx range.
I can ping my CNI but can't get into the wiser at all.

Thanks in advance

 

If you have reset the Wiser (ie: held down the reset button while it was booting), then it will have reset to its factory default IP address which is 192.168.2.1. You'll need to switch your PC to an IP address in that subnet, eg: 192.168.2.10 and verify that you can ping it.

 

wiser lockout

All good, Ive finally been able to access the wiser gui and reset all my settings.
The Gui now shows a little 3 pin plug icon in green with a c-bus icon and a slash through it.
Im assuming that the wiser will not connect to my c-bus.

Can you provide a fix for this issue?

 

The c-bus icon with a red slash through it tells us that it has no connectivity to C-Bus. I'm guessing that with the change in IP address, your Wiser is no longer able to access its CNI. What you'll want to do is check the following:
a) what does Wiser have as your CNI's IP address
If you go to http://wiserip/index_i.htm and then click on the Wiser tab, it'll show you something like:
CNI Information 192.168.100.51:10001

Once you have that, you'll be able to verify whether your CNI is actually at that IP address (eg: 192.168.100.51) and that port (eg: 10001).

If the value you see there is not what you desire it to be, then you'll need to use PICED to edit your project and set the CNI IP to what it should be. Ensure that the CNI IP is within the accessible subnet of your Wiser.

b) setting CNI IP address
In case your CNI is not at the correct IP address, please download the C-Bus IP Setup utility and use that to change the CNI's IP address.

 

Thanks for your help in this kjayakumar,

Ive changed my wiser ip statically to #.#.#.115 and my wiser cni to #.#.#.116. Ive also updated this in piced.

Im still not getting a cbus connection. I cannot access toolkit through the wiser either.

 

I assume after updating the parameters for the CNI in your PICED project, you then transferred this to the Wiser. If your Wiser is still not getting a c-bus connection, it is worth it to check what the CNI is reporting for its TCP/IP status and also its C-Bus status. If you use a web browser to connect to http://IP_address_of_your_cni/ eg: mine's at 192.168.100.115, it shows:

C-Bus status: Client connected from 192.168.100.100
since > 24 hours ago
Network voltage: 28.9V, measured > 24 hours ago
IP Address: 192.168.100.115
Netmask: 255.255.255.0

That will tell you what's connected to your CNI. Also, you'll want to ensure if you used toolkit to connect to the CNI directly, then you should close the network so that the CNI is made accessible to your Wiser.

 

Wiser lockout

Thanks kjayakumar,

I spoke with Ian from cis this arvo. He reckons its a faulty cni and to send it back.

Again, thanks for your time and help.