Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

Number of power supplies and burdens?

SpaceLogic C-Bus Forum

Schneider Electric forum about the C-Bus platform to get support and share knowledge including Network Automation Controller (NAC), Application Controller (AC) at selection, installation and troubleshooting sides.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • EcoStruxure Building
  • Light and Room Control
  • SpaceLogic C-Bus Forum
  • Number of power supplies and burdens?
Options
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
sesa96364
sesa96364 Schneider Alumni (Retired)
9
KCWong
Lieutenant JG KCWong Lieutenant JG
4
DarrenMullighan
Ensign DarrenMullighan Ensign
1
laurence_crowhu
Ensign laurence_crowhu
1
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to SpaceLogic C-Bus Forum
Solved
ETsang
Ensign ETsang Ensign
Ensign

Posted: ‎2014-03-03 08:13 PM

0 Likes
3
1299
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2014-03-03 08:13 PM

Number of power supplies and burdens?

I used C-Bus calculator and C-Bus Toolkit to calculate the number of power supplies and burdens for a network, why does my C-Bus network still have problems?

Reply
  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
sesa96364
sesa96364 Schneider Alumni (Retired)
Schneider Alumni (Retired)

Posted: ‎2014-03-05 07:39 PM

0 Likes
1
1260
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2014-03-05 07:39 PM

you are correct, This is a good rule of thumb for general C-Bus network design.

The calculator gives you a result based only on some straight forward maths. It calculates the current consumption of all units, the current available by all power supplies in the database, then tells you whether the power supplied is enough and indicates whether you need a burden.

The difference between the calculated result and the real world result varies due to location of power supplies, number of burdens, voltage at the unit and problems such as network loops and interference. Problems typically only occur on large networks.

A few rules for a C-Bus network are as follows:

  • no more than 100 units
  • no more than 2A of power supplies in total
  • no more than 1km of cable
  • 3 clocks enabled per network
  • minimum 20V at each unit
  • use burdens on small networks, not on large networks

Network Layout:

When designing the layout its common to locate all the power supplies in distribution boards and run cable out to all other units on the network. A cable will usually daisy chain many units together along a single run. The units that are located further away from the power supplies will have a lower voltage. As the voltage get lower and unit counts increase the signal quality drops and this can result in communications problems between units on a network.

The ideal scenario involves distributing the power supplies evenly across the C-Bus network. C-Bus is very robust when it comes to communications using long runs of cable and varying numbers of units & power supplies. The problems only occur when you break any of the rules. As you creep past the limits the system will most likely still work however problem will occur intermittently and become more obvious as you creep further.

Two examples of a problems that I have seen on a large networks:

Problem:

Occasionally a key unit would blink its LED's indicating that the C-Bus network had lost its clock. Otherwise everything was reported to be operating correctly.

Investigation:

It was found that the unit that was in control of the clock was changing continuously. The cause was an excessive amount of burden on the network which caused a communications failure. One of the units with clock enabled would think there was no clock and enable its clock, at a later time another unit would take it back. This occurred as a result of the network being commissioned in sections, a small network was first created and programmed that required 2 burdens. As more units were added the burden became unnecessary and as more units were added the excessive burden caused communications failures.

Solution:

The solution was to remove burdens since the network was large enough to not need it.

Problem:

3 key units in a warehouse were not always turning the lights on and off however there were no other problems on the network

Investigation:

By looking at the voltage reported by each unit on the network we could see that all units were reporting steady voltages of about 30V except for the 3 key units which reported about 20V. Since the key units were located in a warehouse the length of cable between them and the rest of the C-Bus network was quite long resulting in a voltage drop. The voltage at the units became borderline and they were not always able to communicate with the rest of the network.

Solution:

Add a power supply near the key units to boost the voltage. This means there was a slightly better distribution of power supplies across the network.

Regards,

Matt

See Answer In Context

Reply
Replies 3
Anonymous user
Not applicable

Posted: ‎2014-03-05 04:30 PM

1 Like
0
1260
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2014-03-05 04:30 PM

I wonder what kind of problem do you have ? normally you can give one network burden and 3 C-Bus clocks into your single C-Bus network

Reply
sesa96364
sesa96364 Schneider Alumni (Retired)
Schneider Alumni (Retired)

Posted: ‎2014-03-05 07:39 PM

0 Likes
1
1261
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2014-03-05 07:39 PM

you are correct, This is a good rule of thumb for general C-Bus network design.

The calculator gives you a result based only on some straight forward maths. It calculates the current consumption of all units, the current available by all power supplies in the database, then tells you whether the power supplied is enough and indicates whether you need a burden.

The difference between the calculated result and the real world result varies due to location of power supplies, number of burdens, voltage at the unit and problems such as network loops and interference. Problems typically only occur on large networks.

A few rules for a C-Bus network are as follows:

  • no more than 100 units
  • no more than 2A of power supplies in total
  • no more than 1km of cable
  • 3 clocks enabled per network
  • minimum 20V at each unit
  • use burdens on small networks, not on large networks

Network Layout:

When designing the layout its common to locate all the power supplies in distribution boards and run cable out to all other units on the network. A cable will usually daisy chain many units together along a single run. The units that are located further away from the power supplies will have a lower voltage. As the voltage get lower and unit counts increase the signal quality drops and this can result in communications problems between units on a network.

The ideal scenario involves distributing the power supplies evenly across the C-Bus network. C-Bus is very robust when it comes to communications using long runs of cable and varying numbers of units & power supplies. The problems only occur when you break any of the rules. As you creep past the limits the system will most likely still work however problem will occur intermittently and become more obvious as you creep further.

Two examples of a problems that I have seen on a large networks:

Problem:

Occasionally a key unit would blink its LED's indicating that the C-Bus network had lost its clock. Otherwise everything was reported to be operating correctly.

Investigation:

It was found that the unit that was in control of the clock was changing continuously. The cause was an excessive amount of burden on the network which caused a communications failure. One of the units with clock enabled would think there was no clock and enable its clock, at a later time another unit would take it back. This occurred as a result of the network being commissioned in sections, a small network was first created and programmed that required 2 burdens. As more units were added the burden became unnecessary and as more units were added the excessive burden caused communications failures.

Solution:

The solution was to remove burdens since the network was large enough to not need it.

Problem:

3 key units in a warehouse were not always turning the lights on and off however there were no other problems on the network

Investigation:

By looking at the voltage reported by each unit on the network we could see that all units were reporting steady voltages of about 30V except for the 3 key units which reported about 20V. Since the key units were located in a warehouse the length of cable between them and the rest of the C-Bus network was quite long resulting in a voltage drop. The voltage at the units became borderline and they were not always able to communicate with the rest of the network.

Solution:

Add a power supply near the key units to boost the voltage. This means there was a slightly better distribution of power supplies across the network.

Regards,

Matt

Reply
ETsang
Ensign ETsang Ensign
Ensign

Posted: ‎2014-03-05 11:39 PM

0 Likes
0
1260
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2014-03-05 11:39 PM

Thanks Matthew~ I see Toolkit is reporting the voltage is a bit low on some units. I'll try relocating a power supply to another distribution board

Reply
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of