Toolkit remote connect

Discussion in 'C-Bus Wiser 1 Controller' started by Yoshi, Nov 4, 2010.

  1. Yoshi

    Yoshi

    Joined:
    Nov 17, 2006
    Messages:
    103
    Likes Received:
    0
    Hello,

    I have two questions regarding remote connection to Wiser.
    Wiser was installed in Option A and a Colour C-Touch was also installed in the network.
    I installed a Web Cam at same LAN.

    I can connect a Wiser both locally and remotely.
    I can get a picture via Wiser also locally and remotely.
    I can update Project to Wiser and Colour C-Touch from remote site.

    Question 1,
    I can not connect CNI via Wiser from remote site.
    I checked Enable Toolkit Control in Project Detailes.
    I arranged Remote Wiser Properties as below.
    URL/IP Address : infos2.dyndns.org
    Port : 8336

    This is steps of my trying.
    Try to get global IP address using ping command of Windows.
    As global IP address is 210.139.185.224.
    Start Toolkit->Find C-Bus Networks->Open Set Default Interface->Select IP Address(CNI)->Add 210.139.185.224 : 10001->Scan.
    After the scanning, "No network could be found, please check Default Interface that you have selected" is shown.

    Please teach me if my operation is missing.

    Question 2,
    I can get Web Cam picture from remote site via Wiser.
    Port number of Web Cam is 80.
    I arranged 8500 to Forwarded Port of Web Camera Widget.
    I try to connect Web Cam directly from remote site.
    I type below in URL part of IE.
    http://infos2.dyndns.org:8500/
    I can not connect Web Cam.
    Unfortunately, Port Fowarding function of Wiser does not have port changing function.
    If I can arrange below configuration of Wiser, I can connect Web Cam directry.
    Incoming Port 8500 change to Local Port 80 for Local IP (Web Cam)

    Please also give me advice.
     
    Yoshi, Nov 4, 2010
    #1
  2. Yoshi

    tobex

    Joined:
    Nov 3, 2006
    Messages:
    728
    Likes Received:
    0
    Location:
    Sydney, Australia
    You may find that 10001 is an internal offset for the port configuration. I used 14000 as my port setup.

    When I use toolkit I address xxx.xxx.xxx.xxx:14000

    This is with 5500CN and not with WISER so it may be different in this case.
     
    tobex, Nov 4, 2010
    #2
  3. Yoshi

    Newman

    Joined:
    Aug 3, 2004
    Messages:
    2,203
    Likes Received:
    0
    Location:
    Adelaide, South Australia
    When remotely connecting to a C-Bus network using the CNI connected to the Wiser, you need to use the IP Address of the Wiser, not the IP Address of the CNI.

    This is because the CNI can only have 1 connection to it, and this is always in use by the Wiser. When Toolkit wishes to access the C-Bus network, the Wiser will hand the connection over to Toolkit.
     
    Newman, Nov 4, 2010
    #3
  4. Yoshi

    Yoshi

    Joined:
    Nov 17, 2006
    Messages:
    103
    Likes Received:
    0
    Hello tobex and Newman,

    Thank you very much for your comment.

    I tried to connect Wiser many times via port 10001 and 14000 of Wiser IP.
    Sometime I got a result of scannoing that is "0 Units Found".
    I tried to open my Project but any units did not appear in window.

    Any suggestion is helpful for me.

    Thank you very much.
     

    Attached Files:

    • wi2.png
      wi2.png
      File size:
      71.9 KB
      Views:
      689
    • wi3.png
      wi3.png
      File size:
      72.8 KB
      Views:
      696
    • wi.png
      wi.png
      File size:
      83.9 KB
      Views:
      690
    Yoshi, Nov 4, 2010
    #4
  5. Yoshi

    tobex

    Joined:
    Nov 3, 2006
    Messages:
    728
    Likes Received:
    0
    Location:
    Sydney, Australia
    I don't have a WISER. My comment only refers to CNI direct connection not to WISER. Since the CNI is busy with Wiser connection then the expert already made a suggestion above.

    Can check the

    * Policy rule (from 1 - 10) I don't know what the policy rules imply in terms of remote socket

    * Make sure the port routing is enabled but I dont know if it needs to be TCP or UDP

    * Make sure you have the latest firmware

    This link offers some advice.

    http://www.clipsal.com/trade/__data/page/81/W0001133.pdf PAGE 40
     
    Last edited by a moderator: Nov 5, 2010
    tobex, Nov 4, 2010
    #5
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.