Troubleshooting guide: [Product or feature]

One entry per problem, named by its symptom. Replace the blue placeholders and delete the grey notes as you go.

Applies to

[Models, versions or platforms]

Written for

[Users / support agents / IT staff]

Owner

[Name or team]

Last reviewed

[Date]

Contact support

[Phone, email or form, and hours]

Before you start. Warnings that apply to every entry go here, before any step: [switch off and unplug before you touch internal parts]; [back up before a reset or reinstall].

Symptom index

One row per entry, most common problems first, in the words your readers use. Quote messages exactly.

What you see

Go to

Most common cause

[Symptom or exact message]

[Entry title]

[Cause]

[Symptom or exact message]

[Entry title]

[Cause]

[Symptom or exact message]

[Entry title]

[Cause]

Problem: [Symptom in the reader's words]

Symptom

[What the reader sees, hears or gets; quote any message exactly]

Applies to

[Models, versions or platforms]

Before you start

[Safety, data loss, what to have ready]

Quick check: [one check that rules out half the causes at once]

  • If it passes: [go to the cause it points to]

  • If it fails: Start at cause 1.

Cause 1: [most likely cause, or the quickest to check]

  • Test: [what to do, and what to look for]

  • If yes: [the fix], then confirm the fix.

  • If no: Go to cause 2.

Cause 2: [next most likely cause]

  • Test: [what to do, and what to look for]

  • If yes: [the fix], then confirm the fix.

  • If no: Go to cause 3.

Cause 3: [least likely cause, or the slowest and riskiest to check]

  • Test: [what to do, and what to look for]

  • If yes: [the fix], then confirm the fix.

  • If no: Go to “Still not working?”

Confirm the fix: [what working looks like]

Still not working? [When to stop, and why: safety, data or warranty]. Contact support with: [model, serial number, version, the exact message, the causes you checked].

Copy this section for each problem. Keep the same parts in the same order, so readers learn where to look. Put quick, safe checks first; anything that erases settings or data goes last, with a line saying what it erases.

See a filled-in entry

Problem: labels print blank or too faint (Tagwell T2). Before you start: the printhead can be hot right after printing; switch off and wait five minutes before you touch it.

Quick check: hold Feed for three seconds to print a test label. If it prints dark and sharp, go to cause 4. If it's blank or faint, start at cause 1.

Cause 1: the roll is loaded backwards. Before you reload anything, scratch a blank label with a fingernail: the printing side shows a dark mark. Mark facing away from the printhead: reload the roll, then print a test label. Mark facing the printhead: the roll and the label type are fine; go to cause 3. No mark on either side: go to cause 2.

Cause 2: the labels are the wrong type. The Tagwell T2 prints only on direct thermal labels. Check the part number against the list inside the cover; if it isn't listed, replace the roll and print a test label.

Cause 3: the darkness setting is too low. In the Tagwell app, open Settings › Print. If Darkness is below 10, set it to 15 and print a test label. If it was already 10 or more, go to Still blank or faint?

Cause 4: the app is printing the wrong size. In the shipping software's print settings, choose 4 × 6 in and set the margins to 0.

Still blank or faint? Stop: opening the printhead assembly voids the warranty. Contact support with the serial number, the label part number, photos of a blank and a test label, and the causes you checked.

From an invented label printer. The quick check splits the problem in half, and each check rules a cause in or out before anything is replaced or adjusted.

Troubleshooting table

For problems with one likely cause and a fix that fits in a sentence. A row that needs more gets a full entry.

What you see

Why it happens

What to do

[Symptom or exact message]

[Cause]

[Fix]

[Symptom or exact message]

[Cause]

[Fix]

[Symptom or exact message]

[Cause]

[Fix]

Decision tree

For problems where the next step depends on the answer. Every path ends in a fix or in Contact support.

Step

Check

If yes

If no

1

[Question the reader can answer by looking]

[Go to 2]

[Fix, or go to a later step]

2

[Question]

[Fix, then go to the last step]

[Go to 3]

3

[Question]

[Fix, then go to the last step]

[Go to the last step]

4

[Is it working now?]

Done

[Contact support with what to send]

Error messages

In code order, each message quoted exactly as it appears on screen. Say what went wrong and how to fix it.

Message

What it means

What to do

[“Code: exact message”]

[What went wrong]

[How to fix it]

[“Code: exact message”]

[What went wrong]

[How to fix it]

[“Code: exact message”]

[What went wrong]

[How to fix it]

Contact support

  • When to contact us: [after which checks, or straight away for safety problems]

  • What to send: [model, serial number, version, the exact message, photos or screenshots, the causes you checked]

  • How: [phone, email or form, with hours and response times]

Before you publish

  • Every entry is named by a symptom in the reader's words

  • Error messages are quoted exactly, with their codes

  • Checks run from quick and safe to slow and risky

  • Every check says where to go next, for yes and for no

  • Steps that erase settings or data say so before the step

  • Every entry ends with how to confirm the fix and when to contact support

  • Someone who didn't write it has followed one entry on a real problem