Accessing Wiser

I wasted a bit of time because it was a fair while from when I did the PointOne training to actually setting one up...

Once you know you need to do the PICED download (with IP settings) prior to the web configuration its a piece of cake.

Couldn't see that written in the Workbook either

 

Wiser and CNI problem

Hi members, I have similar issues.

I have my wiser setup in Option B setup.
So I go out of my LAN to the LAN ports on the Wiser.

The range of LAN is 192.168.5.X/24
The wiser IP is 192.168.5.201, it has no WAN and also DHCP is off.
The CNI is 192.168.2.2

I have a laptop connected to the LAN of the Wiser and can ping both units.
The Laptop has two static IP address one in 192.168.5.5 and 192.168.2.5

I Connect to the wiser page and could edit the Router Setting.
But I get a unable to connect to Wiser when trying to load the GUI.

At the moment the switch is selected for AP mode.

I tried to connect to the CNI with the IP utility to change its IP in the range of the .5.x network but after it finds it a warning about changing the address will not be accessible on the Subnet and I hit ignore it says saving but it comes back to the page with the same 192.168.2.2 address, and it also pings from that address too.

Any ideas? Will probably try a default in the morning.

 

The Wiser at 192.168.5.201 won't be able to reach the CNI at 192.168.2.2. You mentioned using the C-Bus IP Setup utility to set the IP of the CNI. Changing that to a 192.168.5.x IP address should solve the issue.

 

wiser

Thanks for the reply.

I have had some developments but still am scratching the head.

I was able to plug direct into the inline CNI and change its IP address to 192.168.5.202 so now when I reconnect it and plug a Ethernet cable from my laptop whilst plugged into the LAN port 4 of wiser I can ping both.

I then connect it back into my LAN into the same port where my Laptop come from and I cannot ping either device.

I am connected via my wireless router and cant see the wiser or inline CNI.

Very puzzled at this point.

Should it not be able to be at least pinged if both LANs are connected together?

thanks again for the response.

 

Wiser Connection

Ok so I have solved one piece of the puzzle.

I think my issue was multiple switches.

I do not think that the wiser was able to traverse across another switch before the router.

As on my network I was going out of the modem/router into an 8 port switch and from one of the ports on the 8 port switch to the wiser.

I am now going directly from the 4 port modem/router to the wiser.

I can ping both the CNI and the wiser from a laptop connected wireless on my LAN. HOORAY.

Now I can start programming

 

This post would have saved me about two days of my life when I was first setting up. It should be added to the manual and the error messages don?t really even hint at where the configuration errors occur. It?s great information to the first time user!

I should just add; I think the Wiser unit is a breath of fresh air. It?s opened up a myriad of opportunities for our project. It takes the whole technology to new level and enables greater flexibility and function than we originally thought possible. I for one would put up with the somewhat clunky bits and I don?t mind being a early adopter. Great product, thank you!!

 

Remote Wiser Access

Have set up Wiser as per option B and nearly all good first time.As per earlier post my wiser goes into an 8 port hub and then to the original router and all is good locally.I can access wiser and control c-bus from all p/c,s ipod etc via the locall wireless/wired network but when trying to access from the internet externally it says unable to access wiser.Externally I type in my External IP address:8080/.Is this something to do with port forwarding and do I have to do it on the Router and also the wiser?
Any help appreciated

 

If you've got a router ahead of the Wiser, then yes, you'll want to port forward the set of ports you require (eg: 8080, 8888, 8889, etc) to the Wiser.

 

Thanks for prompt reply-I have already done the port forwarding on the original router which is before the wiser but do I have to do any port forwarding etc in the wiser.
Is there anything in the wiser that could be affecting the remote access.As I said before all local access working superb.
Is there any way (ping etc) that I can check out where the problem is
I am sure there is not much to fix and due to do wiser course as soon as one available
Thanks again

 

I'm not sure I understand your question, but you definitely don't need to double port-forward, ie: both on front router and wiser. I would write down all of my configuration details, check the PICED project IP setup information including gateway info. Yes, ping will help you but only at an IP level.

 

working ok now-just me with port forwarding in the router.I set them all for outgoing rules which is at the top of the page.At the bottom of the page incomong rules and nothing-all blocked.
All good now.
Thanks again

 

I should have left it alone!!

Hi guys. I set my wiser up in a hurry. Just used PICED to dump my tag database and some schedules into the wiser, no wireless or lan connection. Now I have time to polish it up, add iphone app, remote access and intergrate it into my lan.
Glad I saw this thread otherwise I would have wasted days if I just read the manual.
LOaded into PICED that the new ip would be 192.168.1.101 to fit the home router subnet and CNI 192.168.1.102. Problem was the modem/rouer access was 192.168.2.1, so I had to change before I went on the lan. Saved to the wiser. Disabled DHCP on the wiser and connected to the lan. Ran Cbus IP utility to change CNI address but it crashes!!! Message reads "Access violation at address 0052A66F in module cbusutility.exe. Read of address 0000000C.
Any ideas on how to get around this?

 

When posting that you have problems with a particular piece of software it's always important to state the version of the software and the operating system it's running on. The current version of the IP Setup Utility is 1.2.0.

 

Sorry your right. Running XP and downloaded the latest IP utility as I couldn't see what the old version was because it kept crashing. I have now been able to see the CNI and changed its address to 102. Router is 101. Will use PICED to see how I go.

 

A quick summary

This was an extremely useful thread to read, especially considering the wiser instructions say that even with option B you need to use the wifi on the wiser instead of your own, which is not the case.

The only thing missing here is a summary of what you need to do in order to add the wiser to your own subnet (it still took me a while to figure it out properly so I thought step by step instructions would be useful).

1. Change your computers IP to 192.168.2.100/255.255.255.0 and plug the LAN cable into one of the 4 LAN ports on the wiser.
2. Go to http://192.168.2.1/SetupDHCP.htm and change the IP address to one that suits your subnet (mine is 192.168.0.254).
3. Change your computer's IP address back to its previous setting.
4. Open CBus IP Utility and change the IP address of the CNI to one that suits your subnet (mine is 192.168.0.253)
5. Open PICED and create a new project. In the project settings, set the address of the CNI to the address you used in 4).
6. Upload the project to your wiser and check that it works.

Thanks for all the help in this forum.

 

ggrrrrrr I feel so stupid since I am unable to setup a wiser as LAN device.
Can you please post a print screen from wisers' setup page after you setup the new IP in wiser?

 

I can get to it on the LAN no problem, but I've never had any luck getting access to it from the WAN.

 

Guys,

When setting up wiser in option B as a lan device you need to set the wiser router gui to static IP and give it a fixed IP in your networks range..

Otherwise each time you get a power out or the ip licence expires your wiser will possibly change ip address..

I suggest reading my post in the sticky at the top of the wiser forum.. I have not yet failed setting up a wiser with remote access this way, and have now got it down to a pretty fine art i believe..

Cheers..

 

This does not make sense. It would then be installed on your LAN but through the WAN port of the wiser router. This to me means its no truly a "LAN device".

As I have it now, I have a patch cable going from my gigabit switch into one of the LAN ports on the wiser router. With the router assigned a static LAN IP, there is no problems with the power going out as it uses the static LAN 192.168.1.10 IP and not one assigned by the DHCP server.

Again, I have no problems accessing the unit via the LAN, whether wifi or hardwired, from desktop, laptops and android and ios cell phones and tablets.

EDIT: Found this in the install manual, this is exactly how my system is wired with hopefully the correct forwarded ports. http://updates.clipsal.com/clipsalonline/Files/Brochures/W0001133.pdf

 

So I followed Roosta's guide in the sticky and I got it working. I went through line by line and updated things along the way and kept checking it with my phone's android app. Ultimately, after enabling the "Allow acess from Wiser LAN ports" and inputting my router's IP, I was able to connect. I then went back and the Wiser Router back to DHCP with no IP just to see if it continue to work and it did. As I imagine, the WAN IP setting should not have any impact when you are connecting it to via the manual's Option B.

CLIPSAL TEAM: I believe this may be incorrectly labeled in the software as I had no problems connecting to the Wiser from within my LAN via the LAN ports. May it should be "Allow Remote Access"...I dont know.