What C-Bus Toolkit is, in plain English
Toolkit is the software that reads and writes the programming inside a C-Bus system. If you have inherited a system, this is the name you will keep hearing, so it is worth understanding what it does and what it does not.
What it is
C-Bus Toolkit is the commissioning and programming application for C-Bus, published by Clipsal, part of Schneider Electric. It is what an installer uses to set the system up in the first place: to find every unit on the network, give each one an address, decide which key controls which group of lights, and build the scenes.
It is available at no cost from the manufacturer. That surprises people who assume the barrier to fixing their orphaned system is expensive licensed software. It is not. The software is free.
What it actually does
- Scans the network
- Interrogates the live bus and reports every unit connected to it, what type each is, and how it is currently configured. This is the feature that rescues systems with no files.
- Programs units
- Assigns addresses and decides what each key and each output channel does. This is how a replacement switch is given the identity of the one it replaced.
- Builds scenes and groups
- Defines what 'goodnight' means, which channels it touches and at what levels.
- Holds the project file
- Your system's master record lives in a Toolkit project file, including the human names someone typed in at commissioning.
- Monitors traffic
- Shows the messages moving on the network in real time. This is how an intermittent fault or a phantom command gets caught.
The honest part: free does not mean easy
Toolkit is professional commissioning software, not a consumer app. It assumes you understand C-Bus addressing, application numbers, group addresses and how units relate to each other. There is no undo button that reaches out into the building, and a wrong write to a live network can leave you worse off than when you started: a house where the lights no longer respond at all is a normal outcome of an inexpert session.
Two specific traps worth knowing about, because they are the ones that turn a curious afternoon into an emergency. Writing a changed address to a unit while other units still refer to the old one breaks every scene that touched it. And erasing or overwriting a unit's configuration before you have a good scan saved means the information you needed to put it back has just gone. Neither is dramatic on screen. Both are expensive.
What it means for an inherited system
Toolkit's scanning ability is the reason a system with no files is recoverable. It can interrogate your live network and rebuild a project file that accurately describes what is installed. What it cannot recover is the naming: it will find a unit and know it drives four channels, but it will not know that channel two is the kitchen. That mapping comes from someone walking your house with the software running. See the lost project file page for what that recovery involves.
Nothing on this page asks you to take anything apart. Every check here is done by looking, or by pressing buttons that are already on the outside of a wall plate. Opening the hinged door of your switchboard to see the breakers is normal and fine. Removing the panel behind them is not, and neither is unscrewing a wall plate or lifting the cover off an enclosure.
In Australia it is illegal to work on fixed wiring without an electrical licence, and the reason is not paperwork: the terminals behind a C-Bus wall plate can be sitting at mains voltage. Anything past the faceplate is a job for a licensed electrician, ideally one with C-Bus accreditation.
Should you get it yourself?
If you are technically confident and want to understand your system, downloading Toolkit and using it in read-only fashion to scan and look is a reasonable thing to do, and it will teach you more about your house than anything else on this site. Connecting requires a PC interface, which is explained in what a PC interface actually does.
Writing changes to a live system you did not build is where we would stop you. Not because of the software licence, but because the cost of a mistake is a house with no working lights and a bigger recovery job than the one you started with. Scan, save, look, and hand what you found to someone who does this for a living.
Want the scan done properly and the file handed to you?
We recover programming from live networks routinely, including on systems nobody has touched in fifteen years. You end up owning the project file at the end, which is the point.