Three routes, and you only need one of them
Bar display work starts from one of three positions. Find yours and take the links in that card; the other two will not be useful to you yet.
- 14 engineering articles on this page, each answering one question
- Covering cut-glass versus native bar panels, interfaces, sunlight and multi-unit networks
- Every article linked at the point where you would need it
Choose the format
The opening is a strip and the question is whether a native bar panel exists, whether a cut panel will do, and what each choice costs in yield and tooling.
Interface and drive it
A strip format usually means a small controller and a modest bus, and the interface choice is made before the panel rather than after it.
Deploy it in the open
The unit is going where people and daylight are, often as one panel in a row of many, and the problems shift to readability, timing and total cost.
Making a stretched panel survive
A bar panel is a long thin piece of glass in a frame that wants to move. Two things decide whether it survives: the mechanics and the customisation.
Torsion is the failure mode nobody models
Long aspect ratios amplify small uneven loads. A frame that is flat on the bench can twist enough in service to stress the glass, the bonding and the driver connections, and the symptom appears months later.
The customisation checklist, before tooling
Cutout tolerance, FPC routing and the bonding plan are the three items that decide whether a custom bar display is repeatable. All three can be settled on paper; none of them can be fixed cheaply after the tool is cut.
What actually decides whether a bar display works
Four things decide the outcome, and none of them is the resolution on the datasheet.
Whether the format is native or cut
A cut panel is a standard panel with the edges removed, which changes yield, edge quality and the minimum order. A native bar panel costs more per unit and removes that risk. The decision belongs early, because it decides the tooling.
The aspect ratio against the content
A strip forces the content to be written for it. Layouts designed for 16:9 and letterboxed into a bar waste most of the panel, and no amount of brightness fixes a design that was never meant for the format.
The mechanical load path along the long axis
Mounting points that work on a square panel concentrate stress on a bar. Fixing the frame at the ends and leaving the middle unsupported is the most common cause of warping and delamination.
Time alignment across a network
One bar display is a display. Forty of them in a row is a timing problem, and drift between units shows up as tearing content that looks like a hardware fault.
Where to go from here
If your question is not really about the format, one of these is closer to it.
Bar display questions
The five questions that arrive most often before a bar display project starts.
Should we cut a standard panel or buy a native bar display?
What interface does a small bar TFT need?
Why do long display panels warp?
How bright does an outdoor bar display need to be?
Can several bar displays be synchronised?
Send us your display requirement
Give us the opening dimensions, the resolution you need, the interface your controller supports, whether the unit is indoors or in daylight, and the annual volume. With those five we can tell you whether a native bar panel exists or whether the format has to be cut.
Request a bar display review