Wiser, CNI and C-Bus problems

Discussion in 'C-Bus Wiser 1 Controller' started by p0rt3r, Nov 3, 2011.

  1. p0rt3r

    Beerygaz

    Joined:
    Dec 25, 2005
    Messages:
    52
    Likes Received:
    0
    Location:
    Johannesburg, South Africa
    Thanks for the suggestions kjayakumar. The CNI isnow in the poper state as reflected by the screenshot. But as you can see, no wiser connection and no C-Gate conneciton is possible.
     

    Attached Files:

    Beerygaz, Nov 28, 2012
    #21
  2. p0rt3r

    jboer

    Joined:
    Apr 27, 2012
    Messages:
    458
    Likes Received:
    35
    Location:
    Sydney
    I may be wrong but it looks like to me that you have the wrong IP listed for your CNI in your Project Database. If the IPs you listed in your first post are correct:

    Wiser: 192.168.1.26
    CNI: 192.168.1.27

    Which I think it is as that is what is in the screen shot of your CNI config.

    Then if you are trying to connect to CBus with Toolkit via a local CGate then it should be trying to connect to 192.168.1.27 in your screen shot it is trying to connect to 192.168.1.26.

    This would cause the issues you are having.

    Try changing the IP in your project database to 192.168.1.27 and reload your wiser and see what happens.
     
    jboer, Nov 28, 2012
    #22
  3. p0rt3r

    Beerygaz

    Joined:
    Dec 25, 2005
    Messages:
    52
    Likes Received:
    0
    Location:
    Johannesburg, South Africa
    jboer, that's not the supported approach. The Wiser is supposed to be permanently connected to the CNI, and when Toolkit tries to connect, it connects through Wiser IP so that the Wiser can disocnnect and pass the Toolkit conneciton through. Then when Toolkit disconnects, it reconnects the Wiser interface. That's the documented behaviour.

    If I try and connect directily to the CNI IP address, I get ~~~ and *** messages back and nothing more (in C-Gate).

    It's like the Wiser has puke dup and is not happy about something. Plan B is to factory reset the Wiser and try again from there, but it's ahassle as it will got back to 192.168.1.1 (which is my router on my network). So I need to pull it out ontoi the bench and isolte it from the rest of the network, etc.
     
    Beerygaz, Nov 28, 2012
    #23
  4. p0rt3r

    jboer

    Joined:
    Apr 27, 2012
    Messages:
    458
    Likes Received:
    35
    Location:
    Sydney
    Fair enough, Ill keep my mouth shut :)

    But basically the wiser isn't allowing any in/out connections?
     
    jboer, Nov 28, 2012
    #24
  5. p0rt3r

    Beerygaz

    Joined:
    Dec 25, 2005
    Messages:
    52
    Likes Received:
    0
    Location:
    Johannesburg, South Africa
    Cracked it. First I thought a factory reset would do the job, but that didn't work. Then I saw I had pushed a project and firmware upgrade to the device with PICED 4.11.1.0, then edited that project and pushed it again with PICED 4.11.0.0. After the reset, opened 4.11.1.0 and uploaded the project again, and voila, everything back to normal.

    So in summary, it looks like editing a project with an older version (even .1 release older) is not a good idea!
     
    Beerygaz, Nov 28, 2012
    #25
  6. p0rt3r

    Conformist

    Joined:
    Aug 4, 2004
    Messages:
    788
    Likes Received:
    74
    Location:
    Adelaide, South Australia
    Hmmm.. This is not good. This should be picked up by PICED and brought to your attention. You should not have to go looking for this.

    I'll get a bug report issued on this.

    Cheers
     
    Conformist, Nov 29, 2012
    #26
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.