Irrigation controllers: Qwen zone maps vs /for/landscapers

Qwen Image 3 2K/4cr owns the labeled program; /for/landscapers is beds and mowing, not this OEM panel.

An irrigation-controller listing is a program: station names, zone map, start times, the strings on the fascia you actually ship. The specifier will read those labels. A cinematic yard at golden hour is a different product with no stations in it. Letter the program. Proof the words. Do not buy a glow-up to replace a panel.

The labeled program is the product

Controller pages fail when the zones fuse. If “drip — beds” becomes a pretty puddle with no station number, the drawing is a texture, not a program. The job is a map a contractor can check: Zone 1 turf, Zone 2 drip, Zone 3 rotors, the exact names on the wiring sheet.

Photograph a live panel if you have one and label it in the editor. If you do not, generate the diagram with the words in the brief, then proof at 100%. The deliverable is a still someone can pause.

Do not prompt a video model to “show our controller programming a smart yard.” It will invent motion and invent legends. A video meter is a terrible typography engine.

Generate an image from text is the named agent door for the lettered still. Quote every string a specifier will proof. Prompt rewriting helps scene language. It is not a licence to rename Zone 2.

Qwen Image 3 letters the zone map

Qwen Image 3 Text to Image is the stills row when the letters have to read. Catalog facts: Qwen’s third-generation image model, strong prompt adherence, complex text rendering in Chinese and English, intelligent prompt rewriting on by default, 4 credits, 2K max, qualities 1K and 2K. No audio. No duration. Aspects include 1:1, 16:9, 9:16, and 21:9.

Write the exact strings. If a station name or a model code must stay verbatim, say so in the prompt and inspect the still. Set 1K while the words are in draft. Set 2K when the map is the map. There is no 4K chip on this row. If the section is a wide callout for a spec PDF, lock 16:9 here. Do not lock 1:1 “for social” and crop a zone off later.

Four credits is the price of a readable program, not a video bargain. Generating the same map “inside Veo” is unreadable type at a video rate, plus a yard that is not your controller.

A photograph of the live fascia is the honest plate when you have it. Qwen is for the labeled diagram. Quote the strings. “A stylish smart-yard UI” is a plausible button you cannot ship. One wrong character in a station name is a regenerate. Do not ask Qwen to invent the physical controller body as a substitute for the pack shot.

/for/landscapers is beds and mowing

Landscapers is the yard’s version of the glow-up: same-angle before and after, install time-lapse, hardscape reveal. That playbook is plantings, beds, mowing.

An irrigation-controller OEM is not a landscaping company. You are publishing a program. Do not rewrite the landscaper feed as a panel diagram. A locked-angle patio is not a zone map.

If a crew needs motion of their install, they upload their photo of that yard. Captioning an OEM Qwen board as “this week’s irrigation tune-up” is a different property.

A constructed technician walking “what you should program for this lawn” is a mouth you do not need. Keep lips off the spec. The board is the expert. If a human must speak, that human is on payroll and on a different take.

Garden centers and contractors are still not this panel

Garden centers sell the season: jobs to do this fortnight, a planting demo on the bench, glasshouse when a delivery lands. Useful if you are a retailer moving hose and timers this week. It is not a substitute for a lettered OEM program. Seasonal prettiness does not typeset station 3.

Contractors are process transparency: demo-day time-lapse, behind-the-walls, a homeowner walkthrough. That is a jobsite. An irrigation OEM is not a general contractor. You are not filming a tear-out. You are publishing the controller. Do not rewrite the contractor page as a system cutaway.

Motion, if any, is later. Most catalog weeks do not need the fascia to spin. If a dealer GIF still wants a slow hold, photograph the real panel, then run image-to-video on that file. Prompt the camera. Do not prompt the zones. Iterate the Qwen board at image prices. Do not debug station math on a video meter.

FAQ

Can Veo letter the zone map if I list every station in the prompt?

No. Veo will invent plate math. Letter the program on Qwen Image 3 at 4 credits, 2K, and proof the characters. Motion, if any, is a later still-to-motion pass of the real panel photo.

Why not use the landscaper /for page as the OEM brief?

Because /for/landscapers is beds, mowing, and a same-angle glow-up. This page is the labeled controller program. Do not rewrite that page as a factory film, and do not paste a zone map into a mulch reel.

Should the image prompt invent “typical zones” if I only said “smart irrigation”?

No. The model will fill something that looks like a program. That something is not your catalog row. Write the station names, or generate Qwen stills that already contain them.

Do I always need to animate the panel?

No. The labeled 2K program in a PDF and a feed already does the OEM job. Animate the approved fascia still only when a short hold helps a dealer recognise the body. Identity of the casting is that job. The math stays on the slide.