Sort the toolchain before you wire anything. The pCO5 board is cheap and the universal inputs read temperature without add-on modules, which is exactly why it turns up in student projects — but the development environment that writes its application, 1Tool, is not a free download. CAREL distributes it through its own organization and authorized partners, usually tied to a training course. Every hardware decision downstream depends on whether you can get that license inside your project deadline.
Toolchain Access Before Anything Else
Treat license acquisition as step zero, not a formality to sort out after the panel is built. Work the request in this order:
- Read the full part number and hardware revision off the label on the pCO5 board. The 1Tool device catalog is version-dependent, and an older installation may not list your board.
- Contact the CAREL sales organization covering your country — in Thailand that means the regional CAREL office or its appointed distributor, not a generic web form. Ask three specific questions: is an academic or evaluation license available, is completion of the 1Tool training course mandatory before release, and which 1Tool version supports the board part number you read in step 1.
- State the scope in the request: single board, bench setup, no commercial distribution of the application, project end date. A limited-scope academic license is a different conversation from an OEM development license.
- Ask in the same message whether a pre-compiled standard application exists for your application type. If it does, you may not need 1Tool at all — see the next section.
- Ask what the loader utility is called for your board and where to get it. The compiler and the downloader are separate tools; a 1Tool license does not automatically put the download utility on your machine.
Do not move on until you have either a license confirmation with a version number, or a written no. A "maybe, after training" answer is a no for a project with a fixed submission date.
What Actually Runs on the Board
Three separate layers live in a pCO-family controller, and confusing them is the most common reason a beginner burns a week:
- BIOS / firmware. Vendor-supplied, board-specific, upgraded with a loader utility. It provides the I/O driver layer, the serial ports, and the terminal handling. You never write this.
- Application. The compiled control program — logic, I/O configuration, alarm handling, parameter set. This is the only layer 1Tool produces.
- Terminal masks and language files. The screens on the user terminal, built inside the same application project.
The consequence matters for your fallback plan: which physical channel is an NTC input and which is a 0–10 V input is decided inside the application. Without 1Tool you cannot re-map a universal input, add a PID loop, or change a control sequence. What you can do with a vendor-supplied standard application is set parameters from the service and manufacturer menus on the terminal — setpoints, differentials, probe offsets, alarm limits, and often the probe type selection where the standard application exposes it.
Confirm what is on your board before you assume it is blank: power it up and open the service menu on the terminal. It reports the BIOS version and the loaded application code and version. If an application is already resident and it covers your control sequence, your project may be a parameterization and data-logging exercise rather than a programming one.
Fallback Decision: Gated Toolchain vs Open Toolchain
Make this call the day the distributor answers, not two weeks later. The comparison that decides it:
| Criterion | CAREL pCO5 | General-purpose PLC with analog/RTD input |
|---|---|---|
| Hardware cost | Low; universal inputs read temperature with no expansion module | Low to moderate; often needs a temperature or analog input card |
| Programming software | 1Tool, gated behind CAREL and its partners, typically training-linked | Vendor IDE, commonly free or low-cost download for small CPU ranges |
| Time to first line of logic | Weeks, dependent on a licensing decision outside your control | Same day |
| Application scope | Purpose-built for HVAC and refrigeration control sequences | General logic, motion, sequencing, whatever the project requires |
| Documentation you can cite | Vendor manuals, mostly distributed with the toolchain | Public manuals and instruction references |
| Reusable skill | Narrow, valuable inside the refrigeration and HVAC OEM sector | Broad, transfers across industries |
If the deliverable is a control system that measures and regulates temperature, and the grade depends on working logic, the toolchain availability outranks the hardware price every time. Keep the pCO5 if — and only if — the licensing answer comes back yes, or if your sequence is fully covered by a standard application you can parameterize.
Bench Setup and Power-Up Checks
Once the software path is settled, build the smallest bench that proves the chain end to end.
- Take the supply voltage, supply type, and terminal assignments from the label on the board and the hardware manual for that exact part number. Do not energize from a supply you have not matched to the label.
- Land one temperature probe on one universal input, and one relay output to a lamp or an indicator. That is enough to prove input scaling and output control.
- Connect the user terminal (built-in or remote) before first power-up. Without it you have no way to read the service menu or confirm a download.
- Power up. The terminal should reach a running screen and report BIOS and application versions in the service menu. A terminal that stays blank or shows a connection message is a wiring or addressing problem, not a software problem — fix it here.
Do not proceed to a download until the terminal communicates reliably. The download path and the terminal path share the same service connection on most pCO hardware, so an unstable terminal link predicts a failed transfer.
Application Download and I/O Commissioning
- Build the application in 1Tool and compile it. A clean compile is the first gate; unresolved I/O assignments show up here, not on the board.
- Transfer the compiled files using the CAREL loader utility over the service port, or from a removable memory key if your board revision supports one. Confirm the utility version matches the board family before you start — a mismatched loader is the usual cause of a transfer that stalls partway.
- After the transfer, cycle power and read the application code and version from the service menu. If the version string did not change, the download did not take. Re-run it before touching anything else.
- Commission inputs one at a time. Compare the value on the terminal against a reference thermometer at ambient, then at a second point (ice bath or warm water). If the reading is stable but offset, use the probe offset parameter. If the reading is nonsensical, the channel is configured for the wrong probe type in the application.
- Commission outputs by forcing each one from the manual override or test screen and confirming the physical relay and the field device. Only after every point is proven individually should the control logic be allowed to drive them.
End-to-End Verification
Run the loop closed and record it. Set the setpoint below the current process value so the controller must act, and log the following in one continuous test:
- Terminal shows the correct application version and no active alarms at start.
- Measured temperature tracks the reference instrument within your project's stated tolerance across the full test range.
- The output energizes when the process value crosses setpoint plus differential, and de-energizes at setpoint, with the minimum on/off timers honored — watch the timer countdowns on the terminal, not just the relay.
- Force an alarm condition (disconnect the probe at the terminal block). The controller must report a probe fault, drive the output to its defined fault state, and clear the alarm when the probe is reconnected.
- Remove supply power mid-cycle and restore it. After restart the controller must come back with the same parameter set and resume control without manual intervention. Confirm the parameter values on the terminal against your commissioning sheet — a parameter set that did not survive the power cycle was written to RAM, not to retained memory.
The power-cycle-and-recheck at the end is the step that separates a demonstration from a working controller. Do not sign the project off before it passes twice in a row.
Frequently Asked Questions
How do I get CAREL 1Tool as a student?
Request it through the CAREL office or authorized distributor covering your country, stating that it is for a single-board academic project with a fixed end date. Access is normally granted through CAREL's own channels and is commonly tied to completing their 1Tool training course, so ask up front whether training is mandatory and how long it takes.
How do I program a pCO5 without 1Tool?
You cannot write or modify the application logic without it. What you can do is load a vendor-supplied standard application for your machine type and configure it from the service and manufacturer menus on the user terminal — setpoints, differentials, probe offsets, and alarm limits are all parameter-level changes that need no development tool.
How do I check which application and firmware are already on my pCO5?
Power the board with the user terminal connected and open the service menu. It reports the BIOS version and the loaded application code and version. Record both before any download so you can prove the transfer succeeded by the version string changing.
How do I decide between the pCO5 and a general-purpose PLC for a temperature project?
Decide on toolchain availability, not hardware price. If the licensing answer is not a firm yes within your schedule, move to a PLC whose IDE you can download today and that accepts a temperature or analog input card — the pCO5's cost advantage disappears the moment the project stalls waiting for software.
How do I confirm a temperature input is scaled correctly?
Compare the terminal reading against a reference instrument at two separated points, such as an ice bath and warm water. A consistent offset is corrected with the probe offset parameter; a reading that is unstable or wildly wrong means the channel is configured for the wrong probe type in the application and must be changed in 1Tool.