Output module Power Supplies

Discussion in 'General Discussion' started by industeq, Oct 30, 2009.

  1. industeq

    industeq

    Joined:
    Feb 8, 2009
    Messages:
    95
    Likes Received:
    0
    Location:
    Stafford, TX (Houston) USA
    I have 8 output modules (4~8 Channel dimmers & 12 Channel relays) and 3 have a 200Ma power supply.
    That equals to 600Ma but when the tool kit scans the project network it comes up with the below:

    Current Consumption 338Ma
    Current Supply 1800Ma
    Impedance 2669 Ohms
    Units Calculated 25
    Units not calculated 0
    Results 1 Burden required


    Now why is it showing 1800Ma?
    200 more and I peaked the 2 amp of the cat5 wiring.


    Thanks
    Alan Dobbs
    Industeq, Inc
     
    industeq, Oct 30, 2009
    #1
  2. industeq

    Newman

    Joined:
    Aug 3, 2004
    Messages:
    2,203
    Likes Received:
    0
    Location:
    Adelaide, South Australia
    When Toolkit scans a network, it cannot tell whether an output unit does, or doesn't, include a 200mA network power supply. It also doesn't know the exact catalogue number of your equipment, so it makes it's best guess. In your case, it assumes that all output units are the 'non-P' variants, i.e. the ones with built-in 200mA supplies.

    If you manually correct the catalogue numbers of all your equipment, the power supply calculation will turn out correct.
     
    Newman, Oct 30, 2009
    #2
  3. industeq

    industeq

    Joined:
    Feb 8, 2009
    Messages:
    95
    Likes Received:
    0
    Location:
    Stafford, TX (Houston) USA
    I was under the assumption once it scanned the network it would get the module ID and complete information (Type, with/wo PS. mfg date, etc).
    The field in the toolkit ?Catalog Number? is a default # it seem now that I look closer. Hence the ?F10 Scan Barcode?.

    I was curious why you would need bar code scanner when the toolkit scans the network to get the information, now the C-bus / Toolkit puzzle is making more sense.


    Regards
    Alan Dobbs
    Industeq, Inc.
     
    industeq, Oct 31, 2009
    #3
  4. industeq

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,397
    Likes Received:
    26
    Location:
    Adelaide, South Australia
    Alan, the other reason for the bar code scanner is that you can scan the boxes of the units you are going to install on a site, and build your complete database before you even connect to a network.

    Pre-planning like this + marking up the units (writing some info on them) can streamline an install.

    different installers have different install processes they use, the TK software tries to accommodate as many ways as possible. What it can't do though is retrieve every single characteristic from *some* devices. Most yes, but there are a few curly ones still there. We are working on a solution to that as well... it will rattle through the system eventually.
     
    ashleigh, Nov 1, 2009
    #4
  5. industeq

    industeq

    Joined:
    Feb 8, 2009
    Messages:
    95
    Likes Received:
    0
    Location:
    Stafford, TX (Houston) USA
    I fully understand, having a global market with each county having different codes & regulation then creating programming code and a feasible global product is easier said than done.
    All the reading on the USA and Australia Clipsal sites I did not see anything about the TK fetching the default modules / all data. But this is the the great part is the expertise of the C-Bus forum.
    Unfortunately I am a newbie (2009) with Clipsal, but prefer over the USA mainstream Lutron for home automation. So far being self taught the Toolkit is so simple for the basic on/off but missing a few minor details in the ?Help? file as in this thread.

    Thanks
    Alan Dobbs
     
    industeq, Nov 1, 2009
    #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.