TinkerBlock UNO kit/When it does not work/21. Troubleshooting the kit
When it does not work · 21 of 21

Troubleshooting the kit

Six things that go wrong with the kit, and the checks for each in the order that finds the cause fastest. Most are a sketch naming the first of a socket's two pins, a cable not latched, a module on an I2C socket, or a shield pin out of its hole. Problems with the UNO itself have their own checklist.

Check in order

From the symptom to the cause
No PWR lamp
The symptom
No PWR lamp with the UNO's ON lit means no 5 V after the shield's fuse. Find the short, unplug, and give the 1 A fuse time to cool and reset.

Each symptom has a chain of checks, cheapest and commonest first, and the first box is the answer more often than the rest together. A fault in the board itself (no port, an upload that fails without the shield, the UNO's ON lamp dark) belongs to the UNO's own checklist.

No PWR lamp

The PWR lamp sits on the sockets' 5 V, after the shield's fuse. Look at the UNO's ON lamp first: dark means the board has no power at all, and that is the UNO checklist's first item. ON lit and PWR dark means the 5 V stops at the shield. Unplug the USB cable and look along both edges for a pin folded under instead of in its hole. Then pull every module out and plug in again: if PWR comes back, one module or cable was shorting 5 V to GND. The fuse, an nSMD100 holding about 1 A, resets by itself once the short is gone and it has cooled. The shield has the details.

A module that does nothing

Check the number in the sketch against the socket. A module is on the second pin printed beside its socket: D2/D3 is D3, D6/D7 is D7, A0/A1 is A1, A2/A3 is A3. A sketch that names the first does exactly what it says to a pin the module is not on.

Then the cable: unplug the USB cable and push both plugs fully home until the latch holds. Then the module on its own: every module's page under TinkerBlock starts with a first sketch. Run it, with the pin changed to the socket's second pin. If the module works alone, it is fine and the fault is in the lab's sketch or another module's socket.

Some modules show their own state. The push button's red lamp lights with every press, with no code involved; lit and the sketch sees nothing means the fault is the pin number. The IR transmitter has a red lamp that lights with its infrared LED.

Wrong readings on an I2C socket

The four SDA/SCL sockets put a module on SCL, which is A5, and the shield pulls SCL up to 5 V through 4.7 kΩ for I2C. A module that is not I2C gets that pull-up as part of its circuit. The push button there reads HIGH whether pressed or not: its 10 kΩ pull-down against the 4.7 kΩ leaves the released pin at about 3.4 V. An analogue sensor reads high. An output such as the IR transmitter switches on until the sketch drives A5 LOW. Move the module to the socket its lab names; only the IR transmitter belongs on an I2C socket in this kit.

It resets when the bar goes bright

The WS2812 bar at full white draws about 180 mA by its data sheet's 12 mA per colour, the largest load in the kit and well under the UNO's 0.5 A USB fuse on its own. A reset as it lights is usually a supply that sags: a long or thin USB cable, or an unpowered hub. Try another cable and a port on the computer itself, and lower the brightness in the sketch.

The hidden load is the passive buzzer. Held HIGH it makes no sound and its coil draws about 200 mA, so a sketch that leaves its pin HIGH adds that to everything else, silently. A sketch that plays it should leave the pin LOW with noTone().

Upload fails with the shield on

The shield routes nothing to D0 or D1, the serial lines an upload uses, so it does not get in an upload's way by design. Take it off and upload again. If that fails too, the fault is the board, the cable, the driver or the Tools menu: the UNO checklist. If it works without the shield, a shield pin is bent or touching its neighbour, or the shield's reset button is stuck down; look before you seat it again.

The LED stopped fading

tone() takes the UNO's Timer2, and Timer2 also makes the PWM on D3 and D11. While the passive buzzer plays, analogWrite on the XL LED in the D2/D3 socket no longer fades it. Either fade the LED while nothing is playing, or, if the WS2812 bar is not plugged in, move the LED to the D4/D5 socket, which puts it on D5, a ~ pin on Timer0. tone(), Servo and the timers they take has the whole table.

When it does not work

None of these symptoms matches

Take the shield off and upload Blink to the bare UNO. If the L lamp blinks, the board, cable and driver are fine. Put the shield back with no modules, check the PWR lamp, then add one module at a time with its own first sketch until the fault comes back.

It worked in one lab and not the next

Compare the two labs' tables. The last chapter moves four modules into sockets that earlier labs used, and a sketch from one lab reads the pins of its own table only. A module left in the wrong socket is the commonest cause.

A module is warm

Unplug the USB cable at once. A warm passive buzzer has had its pin held HIGH, which draws about 200 mA through its coil with no sound. Anything else warm means a short: a plug forced in at an angle, or a damaged cable. Check it before plugging in again.

Where this goes next

More modules that plug into the same sockets, each with its own page and first sketch.

Every TinkerBlock module →

Edit this page — content/books/tkbu/troubleshooting.mdx

Community

Questions about this product

See what other owners have asked, and read their solutions.

Ask a question ↗

TinkerBlock UNO R3 Starter Kit, 12 Modules

Loading discussions…

Discuss this article

Ask about this page. The answer stays here, on the page it belongs to, for whoever hits the same wall next.

Browse Modules and blocks on the forum →