Netwrk Burden

Why is it that Toolkit can not see my physical burden. I have moved it from the PC interface to Network Bridge, with no luck. Do I have to inform toolkit it is a Physical Burden?

 

So ashleigh, Are you implying that you must remember that physcial burdens are attached?

 

You can do either of the following, remembering that you should only ever have 1 burden on the network:

• Remember that the physical burden is attached; or
• Use a software selectable burden in the unit at Unit Address 001.

 

When you say toolkit can't see the burden, do you mean that toolkit can't scan your network? Or it says zero burden on the first unit count page? If there is no burden, hardware or software, you can never scan your network and see any hardware. There is no other thing indicating the presence of a burden. As far as the informative page is concerned, it never works for me, so I guess that is a "to do" page. The display of network power or burden is always false, just ignore that page.

 

Toolkit can only see C-Bus Devices that are connected to the network because they return a "information message" to Toolkit when it sends out a Scan request. The hardware burden is a capacitor and a resistor, and nothing more... Toolkit can't detect it because there's nothing inside the burden to tell Toolkit it even exists.

A Network Burden is not always "required", either in Hardware or Software. I have seen many projects (especially older ones) where there's no burden at all and yet no problems with scanning or operation. But this depends on the impedance of the network itself (large networks are usually OK), however this is almost impossible to guesstimate. Therefore, it's always recommended to have 1 "real" burden enabled anyway.

I was going to say the same thing - that page is almost always incorrect. Almost all of the info presented there is basically a guess, including the issue of whether of not a Burden is required.

 

short cut for burden

Also a nice trick to use when you get caught without a burden or more
importantly a network clock generator is>>>
--------------------------------------------
NOTE: I do not recommend you do this on a fully populated and programmed
network as the existing programming of units will change.
--------------------------------------------

Take a PCI and a "Learn capable" Output Unit with a built-in power supply
( dimmer or relay, whatever) , connect them to gather and then put them
into "learn mode".

learn mode for noobs>>
push down, ( and keep holding down ) a numbered button on the output unit,
after approx 10 seconds the unit and C-Bus lights will start slowly
alternating, "like a pedestrian crossing signal", as soon as that happens,
take your finger off the button. ( if you get fast flashing LEDS, something
went wrong and its best to switch the power off /on to the unit ot reset it).

Now leave the units as is for approx 1 minute or so. Part of the learn mode
process is looking at the network ( your 2 units ) to see if it needs a clock or
a burden, if it does it enables either or both.

most people are impatient so thay do not leave it in learn mode long enough
to see this feature happen.

after the minute push and hold the same button for approx 2 seconds until
the leds stop flashing...

I have helped many, many people out of trouble with this process, due to lost
burdens or PCI's that do not have a clock enabled.

 

Paste from a post about this time last year

If you do not have a plug in burden (plug in burdens are the way to go, the electrical characteristics of the discrete devices are better than surface mount components {that's my opinion} when one is plugged into a unit you can see it and don't have to guess whether one exists on the network or not etc), anyway where was I, if you do not have a plug in burden you can put your 'powered' output unit into learn mode and the burden will enable itself.

You can buy burdens in packs of 10. Money well spent...

 

Learn mode tells you when you can stop waiting: While the clock / burden resolution is happening, the C-Bus and unit LEDs flash together. When the unit determines that the burden/clock can't be resolved, the leds will flash quickly, and when the unit determines that the network can communicate, the LEDs will flash alternately. No need to wait once the alternate flash begins.

Don