Written by

in

findy Lab compatibleFlagshipIP67

LTE Logger Pro

The flagship findy Lab device — full industrial I/O, LTE Cat 1 bis with 2G fallback, programmable in MicroPython.

4-20 mA2× · I²C ADC · scaling + alarms
Analog IN1× 0–5 V
Pulse / Digital IN2× · counted in deep sleep
Relay2× · switched sensor rails
Sensor power3.3 V · 12 V · 24 V rails
Magnet wake-upreed switch, EXT0
LTE Cat 1 bis+ 2G fallback
GNSSon-board patch + u.FL
Solar / DC in6–30 V DC · ID 290
RS485Modbus · 120 Ω on boardAPI coming
1-Wire3.3 V rail + 4.7 kΩ pull-upAPI coming
BLE + WiFiESP32-WROOM-32UAPI coming
Qty1 pc10–99100–499500+
Price€166.00€124.50€99.60€83.00

+ €25 / device / year — findy IoT Platform, global LTE SIM, OTA updates, support.

Inputs, outputs and connectivity

Everything below is wired on the V.12 board and, unless marked, has a findy Lab API today. Colour indicates type.

Pulse / Digital IN ×2
Counted by the ULP co-processor — works in deep sleep · 10 kΩ · IDs 437 / 439
4-20 mA ×2
5.1 Ω shunt + INA180 → I²C ADC · per-channel scaling + min/max alarms · IDs 520 / 570
Analog IN 0–5 V ×1
3 kΩ / 1 kΩ divider → ADC · ID 582
External power sense
Measures the input voltage · ID 290, mV
Reed / magnet switch
Internal · EXT0 wake-up through the enclosure
RS485 / Modbus API coming
Half-duplex, ADM3485, 120 Ω termination on board
1-Wire ×1 API coming
Dedicated 3.3 V rail + 4.7 kΩ pull-up
External supply / solar
6–30 V DC · reverse protection · 0.5 A / 60 V polyfuse
ESP32-WROOM-32U · Xtensa LX6 dual-core
520 KB SRAM · 4 MB flash
MicroPython v1.25 · ULP co-processor
Quectel EG916Q-GL · Cat 1 bis · 2G · GNSS
External I²C ADC (addr 104) · 4 channels
30,000 sample buffer · RTC · OTA
Relay ×2
Contacts on terminals J13 / J16 · energised during measure() (ID 640)
Peripheral power
Switched sensor rail with warm-up time (ID 587)
Sensor rails 12 V + 24 V
24 V behind a 0.2 A polyfuse
Buzzer
5 kHz, 0.5 s — core.beep()
LTE Cat 1 bis / 2G
Quectel EG916Q-GL · eSIM chip + MicroSIM holder · u.FL · SMS in/out
GNSS
On-board patch antenna + u.FL · getGPS()
Battery 2× MR18650
3.6 V Li-Ion · built-in 4.2 V charger
Inputs
Outputs
Communication
Power
API coming hardware fitted, no findy Lab API yet
39 screw terminals, 13 blocks

3.5 mm pitch, three positions per block, as wired on the V.12 board. Top row left to right, then bottom row.

Input to the logger Supply out to your sensor Bus Reserved on this board Ground / not connected

J1

External supply
1GND
2GND
3+V Ext6–30 V DC input · solar panel or DC supply

J4

Analog
1+3.3 V outPeripheral rail
2GND
3Analog IN0–5 V · ID 582

J7

Channel 1
1Digital / pulse IN 1ULP counted · ID 437
24-20 mA #1 −LoadLow side of the shunt
34-20 mA #1 +LoadLoop return · ID 520

J10

Channel 2
1Digital / pulse IN 2ULP counted · ID 439
24-20 mA #2 −LoadLow side of the shunt
34-20 mA #2 +LoadLoop return · ID 570

J13

Relay 2
1Relay 2Contact
2Relay 2Contact
3Relay 2Contact

J16

Relay 1
1Relay 1Contact
2Relay 1Contact
3Relay 1Contact

J19

Sensor supply
1+24 V outBehind a 0.2 A polyfuse
2GND
3+12 V out

J24

RS485
1RS485 A / BHalf-duplex · API coming
2GND
3RS485 A / B120 Ω termination on board

J22

1-Wire
11-Wire data4.7 kΩ pull-up · API coming
2GND
3+3.3 VDedicated 1-Wire rail

J8 · J9 · J11 · J12

Ground
1–3GNDTwelve ground positions for sensor returns
Relay contacts are yours to wireBoth relays bring their contacts to terminals. The framework energises them during measure() when parameter 640 is set, so they double as switched sensor rails. Contact rating: see the datasheet supplied with the device.
Pulses are counted while the CPU sleepsIN 1 and IN 2 are read by the ULP co-processor. Counts land in IDs 437 / 439 with ring-buffer history in 540 / 541 — no wake-ups spent on counting.
RS485 and 1-Wire are fitted, not yet in the APIThe transceiver, termination and pull-ups are on the board. Until the framework ships drivers, both are read from your own measure() with MicroPython.
One supply, three railsThe 6–30 V input charges the two Li-Ion cells and is measured as ID 290. Sensors get 3.3 V, 12 V or 24 V only for the warm-up time (ID 587) and the measurement.
Full technical specs

Enclosure, battery and pricing as published on findyiot.com; terminals, rails and processor figures read from the V.12 schematic; firmware behaviour from the findy Lab documentation.

Physical
Dimensions121 × 121 × 65 mm
Weight325 g
IP ratingIP67
Temperature−20 °C to +40 °C
EnclosureUV protected
Terminals39 × screw, 3.5 mm pitch
Connectivity
RadioLTE Cat 1 bis + 2G fallback
ModemQuectel EG916Q-GLGNSS variant
Data rate10 Mbps DL / 5 Mbps UL
SIMeSIM chip + MicroSIM holder
GNSSOn-board patch antenna + u.FL
DiagnosticsRSSI, RSRQ, SINR, cell IDIDs 230–238
SMSSend and read via the modem
BLE / WiFiOn the ESP32 moduleNo findy Lab API yet
Power
Battery2× Li-Ion MR18650-26H, 3.6 V
ChargerBuilt-in Li-Ion charger, 4.2 V
External supply6–30 V DCSolar panel or DC · measured as ID 290
Battery life2 years @ 1 report / 24 h
Work current76 mA
Deep-sleep current10 µA
Sleep modemachine.deepsleep(), modem powered down
ProtectionReverse polarity · 0.5 A / 60 V polyfuse
Sensor rails3.3 V · 12 V · 24 V, switched
Processor & IO
CPUESP32-WROOM-32UXtensa 32-bit LX6, dual core
RuntimeMicroPython v1.25
Memory520 KB SRAM · 4 MB flash
ULP co-processorPulse counting on 2 inputs in deep sleep
ADCExternal I²C ADC, address 104, 4 channels
Buffer30,000 samplings
Wake-up period60 / 300 / 900 / 1800 / 3600 sParameter 421
Report periodParameter 422, ≥ 421
WatchdogArmed in boot.py
OTA updateDownload (ID 55) → apply (ID 52)Status ID 53
ProgrammingInternal 5-pin USB header · REPL via mpremote
One file is yours

boot.py and firmware_core.mpy stay as shipped. You edit last.py: what the device measures, what it reports, and how long it sleeps.

last.py — LTE Logger Pro
Report & sleep4-20 mARelay railsPulse counting
datalist = ['582', '290', '421', '443']   # what this device reports

def start(self):
    self.measure()
    self.report(False, datalist)          # alarm=False
    self.prepareSleep(int(core.db.read('421')), True)

fw.start = start
Examples from the findy Lab documentation. Scaling limits and warm-up time are platform parameters, not code.Full API reference →
What you see in the findy IoT Platform

Every card below is a system parameter the framework fills in. The loop value is scaled to your engineering unit by the limits you enter in Settings — no code.

Logger Pro · Site A · Device #0042
Last report: 2 min ago
MeasurementsSettingsCommandsSystem
Analog input 1 · ID 520
12.4
mA · scaled via 553–556
Analog input 0–5 V · ID 582
3.72
V
Pulse count IN 1 · ID 437
18 432
counted through sleep
External power · ID 290
12 640
mV · solar / DC input
LTE RSSI · ID 231
−71
dBm · Cat 1 bis
Last report · ID 443
2 min ago
server-synced timestamp
From sensor to your system

4-20 mA · pulse · 0–5 V sensors

Switched rails, warm-up, ULP counting in sleep

→

LTE Logger Pro

Your measure() runs here — MicroPython v1.25

→

LTE Cat 1 bis / 2G

Global findy SIM, embedded

→

findy IoT Platform

Measurements, settings, commands — by parameter ID

→

Your system

API, webhooks, export

Where Logger Pro fits

Each one runs on the shipped firmware — no RS485 or 1-Wire until the drivers land.

Beginner
4-20 mA pressure transmitter with scaling and alarms
4-20 mAAlarms
Beginner
Water meter pulse counting through deep sleep
PulseULPBattery
Beginner
0–5 V tank level sensor
AnalogLogger Pro
Intermediate
Switched 12 V sensor rail with warm-up
RelayPower
Intermediate
Magnet-triggered field report
Reed switchWake-up
Three ways to use Logger Pro

Ready-made solutions

Complete deployments built on Logger Pro — metering, level and pressure monitoring, environmental sensing — delivered and supported end to end.

View solutions

Have your own system?

We supply the logger and the SIM. You take the data from the platform API into the infrastructure you already run.

Talk to our team →

Write your own logic

You're here. Wire the terminals, edit one file, deploy the next version over the air.

Can't do it? Enterprise team →

More posts