Copyright © 2020-2021 Shenzhen CDTech Electronics LTD. All rights reserved. Site Map Powered by iwonder.cn
Resolution is the specification most often set by habit - matching whatever the last project used, or taking the highest pixel count the budget allows. On a machine interface that produces smaller characters, a heavier graphics load and a harder interface choice, with no gain in what the operator can read. The useful specification comes from the smallest detail that must be legible at the working distance.
It changes character size, graphics load and interface cost at the same time.
Pixel count alone is meaningless without the panel's physical size, because legibility depends on the height of a character in millimetres at the viewing distance. Two panels of the same resolution behave differently if one is 7 inches and the other 15 inches. The decision also drives the interface: more pixels at the same refresh rate means a higher pixel clock, which can push a parallel link past its limit and force a serial interface.
Reading the decision in that order - legibility, then graphics load, then interface - keeps the specification tied to the operator's experience rather than to a datasheet.
Height in millimetres is the number that matters.
A character that is legible at 500 mm subtends about a third of a degree; the same angular size at 1.5 m requires roughly three times the physical height. Multiplying the required angular size by the distance and dividing by the typical character-to-height ratio gives a first estimate in millimetres, which converts into pixels once the panel's pixel pitch is known. That single calculation removes most of the argument about resolution.
Where the display is viewed through a protective window or by an operator wearing glasses, add margin. Where a pendant moves the viewing distance during use, size for the furthest position.
Detail content sets a floor that legibility alone does not.
A trend graph needs horizontal resolution to show peaks without aliasing; a coverage or site map needs enough pixels to distinguish adjacent areas; a camera overlay needs enough to place markers accurately. Each of these has a measurable requirement - the minimum feature width in pixels - and taking that requirement seriously is what prevents an interface that reads well in a screenshot and poorly on the machine.
Where several content types share one screen, allocate the space from the information hierarchy first, then choose the resolution that shows the densest view without scaling.
The pixel clock is the product of the totals and the refresh rate.
Increasing resolution raises the horizontal and vertical totals, so the required pixel clock rises even at the same refresh rate. That is what pushes a design from parallel RGB to LVDS or MIPI DSI, or from a single LVDS link to dual. The interface specifications themselves are published by bodies such as MIPI and HDMI.org, and the electrical design of the link is documented widely by component vendors, for example in TI's LVDS application note and in signal-chain material from Analog Devices.
SerDes links carry higher data rates over longer cables and are documented for families such as TI FPD-Link. The cost is two small boards and some latency, which is why resolution decisions are usually made together with the interface plan.
An interface designed for one resolution rarely scales without loss.
Scaling changes the appearance of text and thin lines, and it adds a processing stage with its own latency. Where the host cannot produce the panel's native timing, the result is either a stretched image or a scaled one, and both are worse than designing the interface for the panel. Aspect ratio has the same effect: content composed for 16:9 shown on a wider or narrower panel either letterboxes or distorts.
The practical rule is to choose the panel's native resolution to match the interface's design, and to treat scaling as a diagnostic tool rather than a design method.
A common class buys supply, tooling and interface options.
Panels in widely used resolution classes - 800x480, 1024x600, 1280x800, 1920x1080 and the common FHD variants - are available from more than one source, supported by more host platforms and easier to replace when a generation ends. An unusual resolution may fit the content better, but it narrows the supply base and often requires custom timing work that has to be maintained for the product's life.
Where an unusual resolution is genuinely required, the design should record the timing table and the interface configuration in the project file, because that information is what makes a later replacement possible.
More pixels do not make a decision faster.
Reaction time is governed by how quickly the operator finds the relevant value, which depends on layout, contrast and character size rather than on pixel density. A dense interface with small elements slows recognition; a simpler interface on a lower-resolution panel with large elements is usually faster. The measurement that settles the question is a timed recognition test with the actual screens, not a specification argument.
Where a machine requires fast decisions, resolution should be spent on larger critical values and not on additional information.
Denser pixels can be harder to read outdoors, not easier.
Higher pixel density reduces the pixel aperture, which lowers transmission, and it makes fine detail more vulnerable to the softening caused by anti-glare haze. In bright conditions, a lower-density panel with large characters and a well-bonded anti-glare front can be more legible than a dense panel with the same optical treatment. Where a display must serve both a bright workshop and a dense diagnostic view, separate the two: the operator view can be coarse and the setup view detailed.
The readability requirement remains a contrast requirement in a stated ambient condition, whatever the resolution.
Four typical cases and the resolution logic for each.
| Interface type | Dominant requirement | Resolution logic |
|---|---|---|
| Operator panel, few values | Legibility at 0.5-1 m | Low to mid resolution with large characters |
| Machine control with trend graphs | Horizontal detail on traces | Mid resolution, 1024x600 to 1280x800 class |
| Camera or inspection overlay | Marker accuracy and feature width | Higher resolution with a serial interface |
| Control room display, multi-window | Density and viewing distance | FHD class or above, sized to the distance |
Where the product family shares one interface design, standardising on a single resolution class and varying the physical size is usually cheaper than supporting two.
Six items make it checkable.
The smallest character that must be legible, in millimetres, at the working distance.
The minimum feature width for any graphical content, in pixels.
The panel's physical size and pixel pitch.
The native resolution and aspect ratio, with the host's capability stated.
The interface that the resulting pixel clock requires, and the cable length.
The scaling policy: none, or a stated scaler with its latency budget.
Panels in the common industrial sizes and resolution classes are listed under products and in the industrial LCD display range; the interface and timing consequences of a chosen resolution are part of the specification review CDTech runs before a design is released.
What resolution is best for an industrial display?
The lowest resolution that shows the densest view in the interface without scaling, at the character height the viewing distance requires. Higher pixel counts add interface cost and graphics load, and they can reduce readability in bright light by lowering transmission and softening fine detail.
Is widescreen 4:3 or 16:9?
Widescreen normally means 16:9 or a wider ratio such as 16:10; 4:3 is the older standard-definition ratio. For machine interfaces the practical question is whether the content was composed for the ratio, because a mismatched ratio either letterboxes or distorts.
Does higher resolution improve operator reaction time?
Not by itself. Reaction time depends on how quickly the operator locates the relevant value, which is governed by layout, contrast and character size. A simpler interface with larger elements on a lower-resolution panel is usually read faster than a dense interface on a high-resolution one.
Why does a higher-resolution panel need a different interface?
Because the pixel clock is the product of the horizontal and vertical totals and the refresh rate. Raising resolution at the same refresh rate raises the clock, which can push a parallel link beyond its limit and require LVDS, MIPI DSI or a SerDes link instead.
Send the viewing distance, the smallest character that must be legible and the densest screen in the interface to CDTech; the reply will state the resolution class, the interface it implies and the module options available.
Contact [email protected] or use the contact page.
By continuing to use the site you agree to our privacy policy Terms and Conditions.