diff --git a/Tags-specs/troubleshooting.md b/Tags-specs/troubleshooting.md new file mode 100644 index 00000000..567f04a5 --- /dev/null +++ b/Tags-specs/troubleshooting.md @@ -0,0 +1,61 @@ +# Troubleshooting Solum ZBS243-based pricetags + +While these tags seem to be pretty dependable, there are a few failure modes +* Battery +* EPD Failure +* EPD voltage driver failure +* SPI EEPROM failure +* SOC/Flash failure + +## Battery failure ## +Dying batteries can be hard to diagnose sometimes. The CR2540 has limited pulse/high current-handling capabilities, and when a battery starts to become drained, its internal resistance will start to increase. This is impossible to see with only a high-impedance meter, as the float voltage will still read about 3v. As soon as a tag boots up, it will try to determine battery voltage, and the only way to reliably do this, is by loading the battery down a bit. + +OpenEPaperLink will do this by enabling the radio during the voltage reading. However, if a battery is very bad, the voltage will sag down enough to crash the tag. As a tag doesn't have a brown-out detection circuit that we know of, and doesn't do a power on reset, it's not going to reset/cleanly. The SOC will stay in a partially crashed state, and will consume a few 10's of milliamps. This will drain whatever remains in the battery in a matter of hours. + +If a tag boots up but hangs during the boot/AP searching process, it's most likely a bad battery. If the battery reads >=2.6v during boot, the battery is probably good enough to continue the boot process. + +Please note that the battery will never read more than 2.6v. This is due to the fact that battery monitoring on the SOC itself is currently undocumented; OpenEPaperLink uses the low-voltage-detect function on the EPD to determine the battery voltage. In normal use, the battery is checked once during boot, and after that approximately every 24 hours. This should be more than enough to show if a battery is becoming low. The tag will work properly down to about 2.15v, under load. + +A dead battery can be more than a problem in itself, it can be a symptom of a problematic tag. Some tags have bad EPD driver chips (CoG), or bad a bad EEPROM that can cause a high quiescent current. This can sometimes be spotted by powering a tag with an external power supply, or using a power profiler such as a PPK2. This will drain the battery far faster than usual. If a tag keeps eating batteries, measure the sleep current. It should be around 2µA, or about 7µA on a long term average including check-ins. Any higher may be indicative of another issue. + +## EPD Failure ## +* Simple failure + +Simply put, you'll know if this is the case when an EPD refuses to update. It can sometimes be more subtle, like increased quiescent current, but the far most common failure mode is an entirely dead EPD, combined with a wildly higher current draw (about 100mA) + +* Blurry screen + +A problem seen mostly on the 1.54" displays; sometimes a screen becomes blurry, and will lack the sharpness to display any thin lines. +blurry + +* Burn-in + +When exposed to a lot of light, sometimes the the pigments will 'burn' in place, leaving a 'ghost'-image in place that will not easily go away. + +* Shifted or distorted images + +distortedshifted +Sometimes the EPD has problems keeping track of incoming bits, or has a problem with its X/Y memory address pointer. Most of the times, this is transient, but some panels are more susceptible than others. Most of the time it's just a small shift; usually limited to 8 pixels. In that case, the EPD lost track of an entire byte + +* Other failures + +In some cases, the EPD will load wrong LUT's, have a grey or reddish color cast over it, have missing lines. There are a lot of ways in which a bad EPD will manifest itself. + +## EPD voltage pump failure ## +The EPD uses an external inductor and mosfet to generate the voltages needed for the screen updates. If this fails, expect one or more of the following: +* A warm inductor / mosfet +* Dead EPD +* Entirely black EPD +* High current draw + +blackepd + +These EPD's can be used on another board, and will generally work perfect again! It's a failure of an external component located on the PCB + +## SPI EEPROM failure ## +All but the segmented tags have on-board SPI EEPROM's that can fail. Generally, if the EEPROM fails in a way that can be detected by OpenEPaperLink, the firmware will let you know with a warning on-screen. If the EEPROM fails in a less dramatic way, it can sometimes read back data from wrong sectors. This will show as shifted or corrupted images sent to the screen (the firmware splash-screen should show correctly). + +Additionally, it can sometimes add a higher-than-normal drain on the battery, depleting it rapidly. + +## SOC/Flash failure ## +In rare cases, the SOC can reject all flasher-commands, preventing the tag from getting flashed externally. OTA updates sometimes still work. A problem with the EPD driver can also present itself as a failure to update/flash the SOC; as the SPI lines are shared, a malfunctioning EPD can sometimes cause problems with external flashers.