FAQ
Measurements & calibration issues
Measurements Giving Wrong Values
High Analog Zero Offset (in volts range)
Ensure that the red DIP-switch positions correspond to the settings on the Configuration page.
Small, Significant Analog Zero Offset
If analog inputs are not 0V, calibrate the Uberlogger using the Calibration button. Please note that the values will always fluctuate around ±0.02V for 12-bit resolution and ±0.01V for 16-bit resolution.
Temperature Sensor Discrepancies
The Uberlogger reads the supplied NTC thermistors (10 kΩ at 25 °C, β = 3950) through a fixed on-board voltage divider and converts the measured resistance to a temperature using a single nominal NTC curve. The same curve is applied to every channel and each individual sensor is not calibrated. As a result, some difference between channels is normal and expected rather than a fault.
Unequal readings between two sensors at the same temperature
Two NTCs held at the same temperature can legitimately read slightly differently because of the sensors' own manufacturing tolerance (both the 25 °C resistance and the β value vary part-to-part). Because the Uberlogger does not calibrate each sensor individually, this tolerance shows up directly as a small offset between channels — typically a fraction of a degree near room temperature, and more towards the ends of the measuring range.
If you need channels to agree closely, characterise each one in a stable, well-stirred reference (for example a stirred ice-water bath at 0 °C) and subtract the per-channel offset in your analysis.
Accuracy is worse far from room temperature
The conversion uses a single β value, which matches the sensor best around 25 °C and drifts further from the true value towards the extremes of the supported range (roughly −40 °C to +120 °C). In addition, NTC channels always sample at 12-bit resolution and the thermistor is highly non-linear, so the effective resolution (°C per measurement step) is finest in the middle of the range and coarsens at the very hot and very cold ends. Larger differences between sensors at temperature extremes are therefore expected.
Unequal readings between two open-air sensors
Open-air beads each measure their own micro-climate. Draughts, sunlight or other radiation, and nearby warm objects (including the user's hand or the Uberlogger itself) easily create real differences of a degree or more between two sensors only centimetres apart. The small bead also has thermal mass, so give the readings time to settle after a change before comparing them. A slight self-heating offset can also occur in completely still air because a small current flows through the sensor.
Check the basics first
- Confirm the channel is set to NTC mode in the configuration and that the matching left DIP switch is set UP (see Configuration).
- Keep the NTC leads short and avoid extending or splicing them — extra lead resistance is read as extra sensor resistance and biases the reading slightly colder.
- Make sure the connector is fully seated in the socket.
- For an absolute accuracy check, compare against a reference thermometer in the same well-stirred medium rather than in open air.
Digital Input Issues
Digital Inputs Not Triggering
Digital inputs require a minimum of 2.0V to trigger a state change.
Calibration Issues After Zero Calibration
Zero Calibration Results Seem Off
Make sure all NTCs and analog wires are disconnected. Set all analog inputs to the analog input mode and select a range of -10V / +10V. Then, recalibrate the Uberlogger. If the issue persists, please contact support.
Wi-Fi issues
Unable to Connect to Uberlogger in Hotspot Mode
- Check Proximity: Ensure you are within range of the Uberlogger's hotspot signal. Walls or obstacles can degrade signal quality.
- Reboot the Uberlogger: Power-cycle or reset the Uberlogger to refresh its settings and try connecting again.
- Check for Interference: If you are in an area with multiple Wi-Fi networks, check if the Uberlogger hotspot channel is not interfering with another network. You can change the network channel as described here.
- Hidden SSID: If the
Uberlogger-XXXXXXXXnetwork does not appear in your Wi-Fi list at all, the hide-SSID option may be enabled. Add the network manually and type the SSID, or hold the "mode" button for 5 seconds to restore the broadcast (visible) defaults.
Unable to Connect the Uberlogger to a Local Access Point
- Check Access Point Frequency: Ensure the access point is operating on the 2.4 GHz band, as 5 GHz networks are not supported.
- Check RSSI Signal: Verify that the RSSI (Received Signal Strength Indicator) of the access point is strong enough. The signal strength should be better than -80 dBm.
- Confirm Password: Ensure the correct password is entered for the local access point.
- Change Wi-Fi Channel: Ensure the Wi-Fi channel set on the access point is compatible with the Uberlogger.
- Reboot Both Devices: Power-cycle both the Uberlogger and the local access point, and try reconnecting after a minute.
- Guest and Enterprise Networks: Uberlogger does not support guest networks that require login portals or networks with enterprise-level certificates.
- Check for MAC Filtering: If the local access point has MAC address filtering enabled, add the Uberlogger's MAC address to the whitelist.
Browser keeps asking for a login
If the web interface login is enabled, the browser shows a native dialog asking for a username and password. The username is fixed as admin — only the password is user-configurable. Make sure the caps lock is off and that you are typing the password exactly as configured (passwords are case-sensitive).
If you have forgotten the web interface password, press and hold the "mode" button for 5 seconds. This clears all credentials (web interface password, hotspot password and Wi-Fi client password) and restores the open hotspot defaults; the status LED blinks to confirm. If the login still persists, power-cycle the device, restore default settings via the Configuration page (only possible if you can still log in), or contact customer support.
Forgot the Wi-Fi hotspot password
If you configured a WPA2/WPA3 password for the Uberlogger hotspot and can no longer connect, press and hold the "mode" button for 5 seconds. This resets the Wi-Fi configuration back to defaults (open hotspot, channel 1, no client mode) so you can rejoin and reconfigure the password.
Red LED flashing & error codes
Overview of codes
In case of an error, the red LED on the Uberlogger will flash, and you can see the error code on the configuration page. Below is the list of error codes and their meanings.
The codes are bit values, so when more than one error is active at the same time the reported number is the sum of the individual codes (for example 12 means errors 4 and 8 are both active).
| Error Code | Meaning | Solution |
|---|---|---|
| 1 | Unable to open the log file. | Check the SD card for errors on your PC and that it is not full. |
| 2 | Data overrun — samples were produced faster than they could be stored. | Use a lower sample rate or a faster SD card. If it persists, contact support. |
| 4 | No response from the internal support chip. | Power-cycle the device. If it persists, contact customer support and report the code. |
| 8 | Faulty data received from the internal support chip. | Power-cycle the device. If it persists, contact customer support and report the code. |
| 16 | Unable to write to the SD card. | Check free disk space and the card. If it persists, reformat or try another card. |
| 32 | Synchronization error with the internal support chip. | Power-cycle the device. If it persists, contact customer support. |
| 64 | Internal SPI communication error. | Power-cycle the device. If it persists, contact customer support. |
| 128 | Unable to mount the SD card. | Try reading the SD card on a PC and reinsert it into the Uberlogger. If it fails, try another SD card. |
| 256 | Timeout waiting for the internal support chip. | Power-cycle the device. If it persists, contact customer support. |
| 512 | No free space on the SD card. | You need at least 200 kB of free space. Remove files from the SD card to free up space. |
| 1024 | Unable to open a file on the SD card. | Check the SD card for errors and reinsert it, or try another card. |
| 2048 | Unable to close a file on the SD card. | Check the SD card for errors and reinsert it, or try another card. |
| 4096 | Maximum file size reached. | The maximum file size of 4 GB has been exceeded. Use a smaller file split size so files are rotated before reaching the limit. |
Customer Support
If you cannot solve the issue using the above FAQ, you can contact customer support by visiting www.uberlogger.com/contact.