How-to
How to Make Arrow Bitmap Buttons in WinCC Touch Panels
Short answer
Export each arrow as a 24-bit BMP at the button's exact pixel size, 64×64 px on a 320×240 TP177B, put it on a Button or an invisible button over a Graphic, and wire Press to SetBit and Release to ResetBit on discrete bits V100.0 to V100.3. The dot you see is a bitmap much larger than the button being clipped, not a broken import.
On this page
- Why does the imported bitmap show up as a dot in the button?
- What pixel size should the arrow buttons be on a 320x240 panel?
- How do I draw arrows the built-in tools can't make?
- How do I wire the button so a touch sets a V-memory bit?
- Which V-memory bits should the four arrows write?
- How do I test the arrows before downloading to the panel?
- How do I build the same button in WinCC Unified?
- Questions asked
Four arrow buttons on a WinCC panel are two small problems with direct fixes. Export each arrow as a 24-bit BMP at the button's exact pixel size, 64×64 px on a 320×240 TP177B, put it on a Button object or on an invisible button laid over a Graphic, and wire Press to SetBit and Release to ResetBit on discrete V-memory bits. The dot you see inside the button is not a failed import: it is a bitmap far bigger than the button, clipped to the button rectangle.
Why does the imported bitmap show up as a dot in the button? #
Because the bitmap is many times larger than the button and the panel draws it clipped to the button rectangle: a 1024×1024 CAD export inside a 64×64 px button shows only its top-left corner, and on a plain background that corner reads as a dot.
The arithmetic makes it obvious. A 1024×1024 export holds 1,048,576 pixels; the button shows 64 × 64 = 4,096 of them, which is 4,096 ÷ 1,048,576 ≈ 0.4% of the image, one corner of a mostly empty drawing sheet. Per axis the button covers 64 of 1024 pixels, 6.25%, so even a perfectly drawn arrow loses fifteen sixteenths of its length in each direction.
Decision: export or resample the bitmap to the exact button size before importing, in the paint tool's resize dialog if the CAD package cannot export at size. Do not ask the button to shrink the picture for you.
What pixel size should the arrow buttons be on a 320x240 panel? #
Use 64×64 px per arrow: four in a row take 4 × 64 = 256 px of the 320 px width, 96×96 px when only two arrows share the screen, and nothing smaller than 32×32 px because a fingertip cannot reliably hold that target.
The TP177B is a 5.7-inch STN panel, and that pixel budget is shared by every object on the screen. The hit-target floor is the fingertip, the same constraint behind sizing HMI touch buttons in a dense matrix: keep each arrow at the working size and spend the spare pixels on gaps between directions rather than on bigger art.
How do I draw arrows the built-in tools can't make? #
Draw them outside WinCC, in CAD or any paint program, and export one 24-bit BMP per direction at the exact button size, mirroring the clockwise arrow horizontally to get the counter-clockwise one.
The drawing objects in the engineering tool will not produce a clean chevron at runtime, so do not fight them: draw a curved chevron with a tail for clockwise, mirror it for counter-clockwise, left and right as plain arrows. Export 24-bit BMP at the size from the previous section; on this class of panel, JPEG decompression slows screen redraw, which makes JPEG the wrong format here. Make a second, brighter or outlined copy of each arrow for the pressed state, and drop the files into the project's graphics folder so they compile into the project.
How do I wire the button so a touch sets a V-memory bit? #
Put a Button on the screen, make it invisible if a Graphic underneath carries the picture, then bind the Press event to SetBit and the Release event to ResetBit on a Bool tag addressed to the V-memory bit — that is the whole mechanism.
- In the tag table, create four Bool tags on the WinCC flexible SIMATIC S7-200 connection, one per direction, at V100.0 through V100.3 (example names: btn_left, btn_right, btn_cw, btn_ccw).
- From Simple Objects, drop a Graphic on the screen, resize it to the arrow's footprint, and browse to the arrow BMP in its picture property.
- Drop a Button on top at the same footprint and set its background to invisible in the appearance properties, so only the arrow underneath shows.
- In the button's events, bind Press to SetBit and Release to ResetBit on btn_left.
- Copy the pair three times, swap in the other three bitmaps and tags, then compile and transfer to the panel.
One object instead of two also works: a Button whose graphic property points at the arrow BMP, whose pressed-graphic property points at the brighter copy, with the caption empty and Click bound to SetBit. It is more compact and less free with styling; the overlay construction is the one to pick when a later migration matters.
Press-to-set and release-to-reset is the same command pair WinCC scripting uses, where difference between SetBit and ResetBit in a scripted faceplate decides whether a latched command ever clears. One caution on layering: an invisible button still catches touches, and so does anything else invisible left on the screen, so when a press fires the wrong action, start by finding the hidden object behind the wrong button action. And treat these arrows as operator controls only: a jog held by a touchscreen bit is not a safety function, and stopping must never depend on a touch release.
Which V-memory bits should the four arrows write? #
One discrete bit each — V100.0 left, V100.1 right, V100.2 clockwise, V100.3 counter-clockwise — anywhere in the CPU 216's bit-addressable range of V0.0 to V5119.7, never a packed word that the ladder has to unpack.
Coil each bit in the STEP 7-Micro/WIN program so the motion logic lives in the PLC, not in the panel, and keep the V-words (VW) for counts and analog values; 2.5 KB of the V-memory is retentive. The panel reaches the CPU over the SIMATIC S7-200 driver on PPI or MPI, with the panel configured as an OP at address 1 and the CPU at address 2. If one arrow genuinely must command two bits, jog plus a fast/slow select for instance, that is done with one HMI button reading and writing two PLC bits, not with bit packing.
How do I test the arrows before downloading to the panel? #
Compile the project, run the WinCC flexible simulation on the engineering PC, and watch the bits in a STEP 7-Micro/WIN status chart: each bit must flip to 1 the instant the arrow is touched and back to 0 the instant it is released.
Walk all four directions and watch each bit, not just the first one. A bit that sticks at 1 has a Release event without ResetBit on the same tag; fix it in the engineering tool, then add a short off-delay on the jog output in the PLC (a 1 s example value) so a release that never arrives, from a dropped connection or the panel losing power mid-press, clears itself. If the axis answers the mouse instantly but starts late on touch, that is press detection rather than your wiring, the same failure mode as touch jog buttons starting late while the mouse works fine.
How do I build the same button in WinCC Unified? #
Drop a Button (RT Unified), load the arrow as its background graphic, set the scaling mode under Properties > General > Content > Background graphic - scale, empty the caption, and set the tag to 1 in the click event.
Unified's object model renders graphics as HTML/SVG, so PNG and SVG import directly and the exact-size export rule matters less, though a same-size file still draws sharpest. Set the background color transparent when only the arrow shape should show, empty the caption, and use the button's toggle mode when an arrow must latch instead of following the finger; the click event writes the tag value 1 and the release logic disappears.
Questions asked
Can I use JPG or PNG files instead of BMP?
On a TP177B-class panel, stay with 24-bit BMP: the legacy raster engine spends longer decompressing JPEG, and that shows up as slow screen changes. If your arrows exist only as JPG, open each one in the paint tool, resample it to the exact button size, and save it as a 24-bit BMP before importing. On Unified Comfort panels, PNG is fine.
How do I change the title shown at the top of the screen?
The title is a property of the screen, not of the button. Open the screen in the editor and change its title text there. Anything fancier, like a colored bar carrying the machine name, is just a text object you place once in a header area of the screen and copy to the other screens.
Why does a bit stay at 1 after I lift my finger?
Usually the Release event is not firing ResetBit on the same tag, or the button sits in a toggle mode that flips the bit instead of following the finger. Check the event list first. Then add a PLC off-delay on the jog output so a release that never arrives, from a dropped connection or the panel losing power mid-press, clears itself instead of latching motion.
Will these buttons survive migrating the project to TIA Portal?
The Graphic plus invisible Button overlay is the construction that survives a WinCC flexible to WinCC Comfort/Advanced upgrade most cleanly, so build it that way if a migration is on the horizon. A single button with imported graphics can come across too, but re-check the pressed-state graphic afterwards, because that property is the one most often reset by the migration.
Do all four arrows fit on one 320x240 screen?
Yes, in a single row. Four 64 px arrows take 256 px, leaving 320 minus 256 equals 64 px to split into three gaps of about 21 px between directions. Vertically the row consumes 64 px of the 240 px height, so 176 px remain above it for status readouts and the screen title.