Is it better to commit one cannon early or wait for both to coordinate?
These answers restate the rules implemented by our open-source engine, which follows the WXF laws and is regression-tested against the official 110-diagram repetition casebook. Where an answer refers to a specific position, that position lives on the linked reference page, where the build verifies it against the engine before publishing.
Direct answer
Commit one cannon early, almost always the central one, to create a real threat and make your opponent respond on your terms. Hold the second back until it has a specific job, joining a battery, swinging to a new file, or supporting a chariot, rather than moving it just because it is available.
Why an early single cannon almost always earns its move
The starting position hands the first cannon a threat for free, so using it immediately is essentially never a wasted tempo. The second cannon has no such free threat waiting; sending it out before it knows where it is going is exactly the kind of premature development that leaves chariots and horses stuck at home.
Recognising when the second cannon is actually needed
Wait until you can identify a concrete target, a battery forming, a weak point in the opponent's structure, or a file worth contesting, before committing it. A second cannon developed on general principle, rather than toward a plan, is exactly the kind of move that looks active and accomplishes little.
Related questions
Does this contradict keeping both cannons for an attack?
No, keeping both means not trading them away; this is about the order and timing of when each one actually moves. See should I keep both cannons for the trading question.
What if my opponent develops a second cannon quickly?
Check whether it is aimed at something real. A second cannon move with no target is not a threat just because it looks similar to one that is.
.