Toolkit / DMX Unit bug ?

Discussion in 'C-Bus Toolkit and C-Gate Software' started by Barshack, Aug 14, 2012.

  1. Barshack

    Barshack

    Joined:
    Dec 15, 2010
    Messages:
    22
    Likes Received:
    0
    Location:
    Ketchum, Idaho, USA
    If you view the attached screenshot, you will see several DMX units in my configuration. Whenever I launch Toolkit, the Groups on the DMX units displayed "unknown", yet all groups have been previously defined. If I open a unit, all the mapping appear correctly (see lower part of the screen shot). If I select APPLY, the fields fill in correctly and remain displayed until the next time I launch Tookit. I suspect this is a bug in 1.12.1, but could not find any mention of it on the forums, so I thought I would make this post.
     

    Attached Files:

    Barshack, Aug 14, 2012
    #1
  2. Barshack

    daniel C-Busser Moderator

    Joined:
    Jul 26, 2004
    Messages:
    770
    Likes Received:
    21
    Location:
    Adelaide
    Hi Barshack,

    Feedback from the Toolkit team as follows:

    This is nothing to worry about. This is just data that is not loaded from the project. When you edit an individual unit it loads all the data and then will display correctly. The DMX gateway uses a different mechanism from most other units to get the data from the units to display on the grid, a mechanism which we have not correctly handled. This has been reported as a bug (#24040) internally.

    PS - regarding your other question, what is the difference between "CNI" and "Wiser" interface types?

    None, our marketing department wanted us to create a special 'Wiser' configuration even though it is exactly the same internally as CNI.
     
    Last edited by a moderator: Aug 20, 2012
    daniel, Aug 20, 2012
    #2
  3. Barshack

    Barshack

    Joined:
    Dec 15, 2010
    Messages:
    22
    Likes Received:
    0
    Location:
    Ketchum, Idaho, USA
    Continued.....

    Hi Daniel

    First, How can I track bugs ?

    Second, please mention to your marketing team that by having two distinct options, some people (me), would expect that there are some differences. Perhaps they should combine the options and label it "CNI/Wiser". While I found documentation for CNI connection in the help file, I didn't see any documentation for the Wiser connection. The other visual difference is that CNI requires an IP address and Wiser connection is alpha numeric, which might mean you can enter a URL and have it resolved via DNS. (I have not tried as it doesn't apply to my configuration.)

    This reason I bring this up is that I was recently troubleshooting a problem where toolkit was unable to connect to the network, and spent several cycles trying both CNI and Wiser type network connections. It would have saved time if there was only one option.

    Marketing guys are always well intended, but sometimes they confuse the techs !!!

    I prefer salmon to kipper.

    Lenny
     
    Barshack, Aug 20, 2012
    #3
  4. Barshack

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,427
    Likes Received:
    64
    Location:
    Adelaide
    This is not entirely correct.

    The "Wiser" type was created because there was confusion when people were trying to connect to their network via a Wiser, but putting the address of the Wiser's CNI.

    When connecting to a Wiser, you use the port number of the Wiser's CNI, but the IP address of the Wiser. The Wiser then passes through this connection to its CNI. People were using the "CNI" connection type in Toolkit, and thinking that they had to put the IP address of the CNI, which won't work, because the Wiser is already using the CNI. Barshack : I believe you yourself had exactly this problem.

    By offering a connection type of "Wiser", it is intended to be more obvious that you use the IP address of the Wiser, not that of the Wiser's CNI.

    Nick
     
    NickD, Aug 21, 2012
    #4
  5. Barshack

    daniel C-Busser Moderator

    Joined:
    Jul 26, 2004
    Messages:
    770
    Likes Received:
    21
    Location:
    Adelaide
    You are right, that is a bit of a dog's breakfast. The underlying C-Gate interface supports domain name resolution and IP addresses alike for any TCP/IP connection, so there is no technical reason to have these constraints in the Toolkit UI (#24045).

    After digging into this more we do need to keep two separate types for Wiser and CNI, but I think we can do better. We already have some open issues to improve the whole experience (#17446, #23698, #23946).
     
    Last edited by a moderator: Aug 21, 2012
    daniel, Aug 21, 2012
    #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.
Similar Threads

  1. Toolkit Bug: Network setup

  2. Toolkit Scan New Bug

  3. I found a bug in ToolKit.

  4. Toolkit 1.7.1x Bug

  5. Toolkit 1.8.2 Bug

  6. Toolkit 10 bug

  7. DMX - 550DMX - Documentation shows DMX Desk?

  8. LED Strip light / DMX gateway / DMX driver

Loading...