If you’ve ever rung our office asking why a quick group rename took two minutes but adding a button to a touchscreen meant we had to schedule a site visit, this article is for you. The short answer is that C-Bus isn’t programmed by one tool — it’s two. C-Bus Toolkit owns the network. PICED owns the smart controllers that sit on top of it. Once you understand who owns what, the whole platform stops feeling mysterious and the workflow makes sense.
We run this split every day across Melbourne installs, so here’s how our team thinks about it when we’re standing in front of a switchboard with a laptop open.
What Toolkit owns
C-Bus Toolkit is the configuration tool for the network itself. Everything physical and logical at the bus level lives here. When we commission a job, Toolkit is the first thing we open because nothing else can reference groups that don’t exist yet.
- The network — scanning the bus, setting the network clock and burden, assigning unit addresses, checking for clashes.
- Output units — relays and dimmers like the L5504D2U, including channel-to-group assignment, ramp rates and trim levels.
- Input units — Saturn, Saturn Zen, Neo and DLT/eDLT switches, key functions, indicator behaviour.
- Applications — Lighting (56), Trigger Control (202), Enable (203) and so on.
- Group Addresses and Tags — the names like “Kitchen Downlights” that every other tool reads.
That last point is the one that matters most. The tags you create in Toolkit are the shared vocabulary. Get them right early and everything downstream is easier.
What PICED owns
PICED stands for Programming Interface for C-Bus Embedded Devices, and the word that matters is embedded. It programs the intelligent controllers — the ones with a processor and storage that do more than switch a load:
- C-Touch / C-Bus Touch screens — the wall-mounted colour touchscreens.
- The Wiser Home Controller — the web-based home gateway and app front end.
- The Pascal Automation Controller (PAC) — a headless logic engine with no screen of its own.
On these devices, PICED is where the user experience and the brains live. You build the touchscreen pages, lay out the buttons and sliders, configure schedules, set up scenes and sequences, and write the conditional automation. None of that exists on the bus — it lives inside the controller, and PICED is how it gets there.
The Logic Engine: where automation actually runs
The part of PICED our techs lean on hardest is the Logic Engine. This is where if/then rules, time schedules, scene sequencing and conditional behaviour are authored. Think “if the front door contact opens after sunset and no one’s home, ramp the entry lights to 80% for two minutes”, or “every weekday at 6:45am, programme the kitchen and ensuite to a soft wake scene”.
Crucially, that logic runs on the controller, not on your laptop and not on the C-Bus units themselves. The PAC and Wiser are popular precisely because they keep this logic running 24/7 without a screen. A C-Touch can do the same, with the added benefit of a local interface. If you want a deeper look at structuring this kind of rule set, we cover it in our C-Bus automation guides.
How the two tools work together
This is the bit that trips people up, so here’s the order of operations we follow on a typical fit-off.
- Build the network in Toolkit. Scan the bus, address the units, assign channels to Group Addresses, and tag everything sensibly.
- Export or reference those tags in PICED. PICED reads the same project context, so your “Living Pendants” group shows up as a selectable item rather than a raw group number.
- Build the interface and logic in PICED. Lay out the touchscreen pages, drop buttons onto your tags, create scenes and schedules, and write Logic Engine rules.
- Download the PICED project to the controller. The C-Touch, Wiser or PAC receives the compiled project and starts running it.
- Keep the project on file. Both the Toolkit and PICED project files are saved for future edits — you cannot reliably reverse-engineer them off the hardware later.
So the relationship is simple: Toolkit defines what exists on the network, PICED defines how the smart controllers present and automate it. They’re complementary, not competing. New to the platform? Start with our C-Bus getting started overview before tackling either tool.
Why some changes are instant and others aren’t
Once you know who owns what, the customer-facing weirdness explains itself. Nine times out of ten when someone rings us frustrated that a “tiny change” needed a return visit, it’s because the change lived on the wrong side of the line.
Quick, often remote
- Renaming a group tag in Toolkit (though the new name won’t appear on a touchscreen until the controller is updated).
- Adjusting a unit’s ramp rate or trim level in Toolkit.
- Tweaking a schedule time on a Wiser via its web interface, where the controller exposes that to the user.
Needs a PICED edit and a controller re-download
- Adding or moving a button on a C-Touch page.
- Creating a new scene that the screen can trigger.
- Changing or adding Logic Engine rules on a PAC.
- Restyling pages, adding a new room, or changing how the interface is laid out.
That re-download step is the reason. A PICED change isn’t live until the compiled project is pushed back to the controller, which generally means a connection to the device — sometimes on site, sometimes remotely if the network interface (a CNI 5500CN, PCI 5500PC or 5500PCU USB) and remote access are set up. This is also why we’re firm about keeping the master project files: edit the project, recompile, download. No file, no clean edit.
A note on the Wiser specifically
The Wiser Home Controller blurs the line a little, which causes confusion. It’s programmed in PICED like the other controllers, but it also publishes a web and app interface that lets the homeowner adjust certain things — schedules, scene activation, favourites — without any tool at all. So some Wiser changes are genuinely self-service, while structural changes (new pages, new logic) still mean a PICED edit and download. We cover the Wiser side in more detail under our C-Bus Wiser articles. For the official line on the hardware and supported tools, Clipsal’s own documentation at clipsal.com is the authoritative reference.
The short version
Toolkit = the network: units, groups, applications, tags. PICED = the smart controllers: touchscreen pages, schedules, scenes and the Logic Engine. Toolkit defines the vocabulary; PICED builds the experience and automation that reference it. Know which tool owns a given job and you’ll always know whether a change is a two-minute tweak or a recompile-and-download.
That’s the mental model our techs carry into every job, and it’s the one we’d hand a fellow integrator on day one. Get the Toolkit foundations clean and your PICED work stays sane.
If you’re a Melbourne C-Bus owner who’s lost your project files, inherited a system with no documentation, or wants a logic change made properly, the DUKE team can help — give us a yell via our contact page and we’ll sort it.
Frequently asked questions
Can PICED program C-Bus output units like dimmers and relays?
No. Output units such as the L5504D2U, plus group addresses, applications and tags, are configured in C-Bus Toolkit. PICED only programs the smart controllers — C-Touch screens, the Wiser Home Controller and the PAC — and references the tags Toolkit created.
Why does adding a touchscreen button require a site visit but renaming a group doesn't?
A button lives in the PICED project on the controller, so adding one means a PICED edit and a re-download to the device. A group rename happens in Toolkit at the network level. Knowing which tool owns the change tells you whether it’s instant or needs a recompile.
Does the C-Bus automation logic run on my laptop or on the controller?
On the controller. The PICED Logic Engine builds if/then rules, schedules and scene sequences that are downloaded to and run on the C-Touch, Wiser or PAC, so automation keeps working 24/7 without any computer connected.
Do I need both the Toolkit and PICED project files kept on record?
Yes. You need the Toolkit file for the network configuration and the PICED file for the controller interface and logic. You can’t reliably reverse-engineer them off the hardware later, so both should be handed over and kept safe for future edits.