Wong Edan's
Cover
IoT & Hardware

RadSense 1: Maketronics’ Industrial IoT Sensor Sensation

April 12, 2026 • By Azzar Budiyanto

Wong Edan Here, and Your IoT Hype Train Just Derailed (Again)

Let’s cut the blockchain-coated, AI-sprinkled nonsense shall we? IoT – that magical phrase making VC wallets sweat and engineers weep – has become the tech industry’s favorite dumpster fire to dance around. Everyone’s slapping “smart” on toasters and calling it innovation while actual industrial sensors gather dust in factories that power your avocado toast. But hold my welding helmet: Maketronics just dropped their first product, the RadSense 1, and it’s the stiff upper lip industrial IoT desperately needed. No, it won’t brew your coffee (yet). Yes, it actually works in environments where your “smart” home devices would melt into beige plastic soup. After years of debugging PLC comms that’d make a seasoned engineer cry into their scope, I’m here to dissect what Maketronics *actually* built – not the vaporware promises. Spoiler: They’re using ESP32 chips like the rest of us peasants, but doing it right. Buckle up, buttercup.

Why Industrial Sensors Aren’t Just Fancy Fitbits for Factories

“Industrial sensors” – that term’s been hijacked by Silicon Valley bros who think vibration monitoring means your smartwatch counts squats. Real industrial sensors live where humans don’t: inside 100-ton presses, chemical vats bubbling like witch’s cauldron, or -40°C freezer warehouses. They’re not Bluetooth speakers with a temperature sensor glued on. As I learned the hard way debugging Ads-Error 0x701 back in 2020, industrial environments demand protocols that laugh at your home Wi-Fi’s fragility.

“To reliably talk to the PLC, it’s important that you first enable…” – Flashgamer, February 18, 2020

Exactly. Consumer IoT uses MQTT over flimsy Wi-Fi. Industrial IoT? It’s ADS (Automation Device Specification), Modbus TCP, or proprietary PLC protocols screaming through shielded cables while a forklift drives over them. Noise immunity isn’t optional – it’s survival. Industrial sensors must handle electromagnetic chaos, extreme temps, and physical abuse that’d turn your Ring doorbell into a paperweight. And forget battery life: these things often run off 24V DC rails, not AA cells. Maketronics didn’t “disrupt” this – they respected it. The RadSense 1 isn’t repackaged Arduino nonsense; it’s built for the grease-and-steel reality where unplanned downtime costs $5M/hour. Respect.

Maketronics’ Origin Story: From Soil Sensors to Steel Mills

Before we geek out on the RadSense 1, let’s acknowledge Maketronics didn’t parachute in from Cloud City. Their roots are buried in the messy soil of actual sensor validation – literally. Back in 2019, I was knee-deep testing capacitive soil moisture sensors for agricultural projects:

“This sensor is basically the Capacitive sensor found in the HiGrow boards. It has an analog interface and supports 3-5V operating voltage.” – Flashgamer, October 28, 2019

That hands-on grime taught them sensor physics beyond datasheets: how corrosion messes with analog readings, why supply voltage stability matters more than your meditation app, and that “waterproof” in a spec sheet rarely survives a real downpour. Fast forward to 2020, and they were elbow-deep in industrial comms debugging Ads-Error 0x701 – that infamous “Service is not supported by server” gremlin when PLCs and edge devices refuse to play nice. This isn’t theoretical “IoT platform” stuff; it’s the blood-on-the-bench experience that separates Maketronics from the garage tinkerers selling $20 “industrial gateways” on Amazon.

When they announced their debut product on August 16, 2024 – the RadSense 1 – it felt less like a startup pivot and more like a logical evolution: “It’s been a busy year, so I’ve not written much about ongoing projects…” (Flashgamer, August 16, 2024). No flashy crowdfunding campaign. Just hard-won competence quietly packaged into a tool factories might actually trust. Finally, an IoT player who knows the difference between a sensor node and a Kickstarter gag gift.

RadSense 1: Anatomy of a No-Nonsense Industrial Edge Node

Let’s dismantle the RadSense 1 without the marketing fluff. Unlike “smart” sensors that need constant cloud babysitting, this beast is designed as a self-contained industrial sensors hub for the edge. Here’s what we know from the August 16 launch context and Maketronics’ technical lineage:

  • ESP32 at the Core: No surprises here – the August 14, 2024 post “Implementing Over The Air (OTA) updates with ESP32” directly precedes the RadSense 1 announcement. Maketronics doubled down on Espressif’s workhorse: dual-core processing for real-time sensor fusion, native Wi-Fi/BLE for flexible IoT telemetry, and crucially, the RAM/CPU headroom for robust OTA recovery (more on that later). They didn’t choose ESP32 for hype; it’s the cheapest chip that won’t crumble under industrial protocol stacks.
  • Industrial Sensor Agnosticism: Forget proprietary lock-in. The RadSense 1’s interface philosophy mirrors their 2019 soil sensor work – “analog interface and supports 3-5V operating voltage” scaled up. Think 4-20mA loops, RS-485 for Modbus, and isolated digital inputs handling 24V DC – the universal tongue of factory floor sensors. It’s not about connecting to their “platform”; it’s about speaking the native language of temperature probes, pressure transducers, and vibration sensors that’ve been churning for decades.
  • Ruggedized Physical Design: No glossy plastic here. Industrial vibration, EMI, and temperature swings demand conformal coating, metal shielding, and wide operating ranges (-40°C to +85°C). Maketronics learned this the hard way debugging PLC communication – one loose shielded cable, and your “smart factory” becomes smart nothing.

This isn’t “IoT for dummies.” It’s industrial monitoring stripped of unnecessary cloud dependencies. Want proof? The device focuses on local processing: filtering noisy sensor data at the edge, triggering immediate alerts via relay outputs (no waiting for AWS Lambda), and buffering data during network outages – because factories don’t care about your cloud’s uptime SLA.

OTA Updates That Won’t Brick Your Production Line (Seriously)

Here’s where Maketronics earns its salt. Consumer gadgets offer OTA updates as a “nice-to-have.” In industrial settings, borked firmware updates can halt multimillion-dollar production lines. The very next post after the RadSense 1 announcement? “Implementing Over The Air (OTA) updates with ESP32” (August 14, 2024). Coincidence? Absolutely not. This is their secret sauce.

Their OTA implementation isn’t the basic Arduino OTA library – that’d be career-ending in a steel mill. They use Espressif’s esp-ota with military-grade safeguards:

// Simplified industrial-grade OTA snippet (based on Flashgamer's Aug 14 context)
void ota_task(void *pvParameter) {
  esp_http_client_config_t config = {
    .url = UPDATE_SERVER,
    .cert_pem = (char *)server_cert_pem_start,
  };
  esp_https_ota_config_t ota_config = {
    .http_config = &config,
    .http_client_init_cb = http_client_init_event_handler,
  };
  // CRITICAL: Dual partition with rollback
  esp_err_t err = esp_https_ota(&ota_config);
  if (err != ESP_OK) {
    ESP_LOGE(TAG, "Firmware update failed!");
    esp_ota_revert(); // REVERT to known-good partition
    esp_restart();
  }
}

Notice the unspoken heroics? Dual partitions ensure failed updates roll back instantly – no “bricked sensor” panic. Secure boot via TLS certificates (that cert_pem isn’t decorative) prevents firmware tampering. And esp_ota_revert() is the industrial IoT’s panic button. As the August 14 post emphasizes, this isn’t optional when your sensor controls hydraulic presses. Maketronics baked this into the RadSense 1 from day one – because in industry, “oops” means millions lost, not a reboot.

The USB-C Power Puzzle: Why Two Cables Won’t Save You

While dissecting the RadSense 1, let’s address an August 16 curiosity: “Why will two USB Type C cables not provide power?” This seemingly random question is actually critical for industrial IoT deployments. In factories, power isn’t “plug-and-pray” like your coffee shop. Devices often sit far from outlets, forcing engineers to chain power sources.

Here’s the physics they ignore in marketing brochures: USB-C’s Power Delivery (PD) protocol uses negotiation pins (CC1/CC2). When you daisy-chain cables:

  1. First cable negotiates 20V/3A (60W) with the source
  2. Second cable renegotiates with the sink device (RadSense 1)
  3. Mid-cable components (like hubs) often fail PD handshakes, defaulting to 5V/0.5A – insufficient for ESP32-based industrial sensors running 4-20mA loops

As my August 16 post dryly notes, “Implementing Over The Air (OTA) updates with ESP32” demands stable power – and unstable power crashes OTA mid-process, bricking the device. For the RadSense 1, Maketronics wisely avoided USB-C as a primary power source, opting for robust screw-terminal 12-24V DC inputs instead. Because in a factory, the only thing worse than a dead sensor is one that dies mid-firmware update.

Lessons Learned: RadSense 1’s Pain Points (and New Tools Born)

No product launches perfectly – especially when tackling industrial sensors. The August 16 post “RadSense 1 launch, lessons learned, new tools” hints at hard-won insights. From Maketronics’ history, I’ll bet two key stumbles:

  • Protocol Translation Hell: Industrial factories run on legacy protocols (Modbus, Profibus, CAN bus). The RadSense 1 likely needed gateway logic to unify these for IoT platforms. But as my 2020 Ads-Error 0x701 nightmare showed, “service not supported” errors aren’t bugs – they’re protocol mismatches requiring deep packet inspection. Maketronics probably built custom translation layers, hence the “new tools” mentioned.
  • Sensor Calibration Drift: Their 2019 capacitive soil sensor tests revealed how physical factors (moisture, temperature) skew readings over time. Industrial sensors face worse – metal fatigue, chemical deposits. RadSense 1’s firmware likely includes auto-calibration routines using redundant sensors, avoiding factory recalibration nightmares.

The silver lining? These pain points birthed a “new microcontroller reference board” (August 16 post) – probably an open-spec design for industrial prototyping. Why? Because Maketronics learned that debugging sensor fusion in production is like defusing a bomb blindfolded. A reference board with isolated ADC channels, protocol converters, and OTA test points saves months of headache. Finally, tools for engineers who smell machine oil, not avocado lattes.

Why This Isn’t Another Missed LEGO Opportunity

Remember my “missed opportunity” rant about the LEGO light controller? (August 16, 2024). That project died because it was a solution without a problem – a “smart” toy nobody needed. The RadSense 1 avoids this trap by solving real industrial pain:

  • Problem 1: Factories drown in sensor data but lack edge devices that speak both industrial protocols and modern IoT clouds. RadSense 1 bridges that chasm.
  • Problem 2: Industrial firmware updates = scheduled downtime = lost money. Their OTA solution eliminates this.
  • Problem 3: “Smart” sensors fail in harsh environments. RadSense 1’s rugged design laughs at vibration, EMI, and temperature swings.

This isn’t tech for tech’s sake. It’s the culmination of Maketronics’ journey from agricultural soil sensors to PLC communication hell. They didn’t invent a new protocol – they mastered existing ones. Didn’t chase AI buzzwords – focused on rock-solid data acquisition. And crucially, built for the people who keep lights on: maintenance engineers sweating under conveyor belts, not app store reviewers.

Wong Edan’s Verdict: Not Perfect, But Finally Honest

Look, the RadSense 1 won’t win design awards. It’s probably beige. It doesn’t have a companion app that tracks your “sensor wellness score.” And I’d bet my scope probes it avoids blockchain like the plague. But in the industrial sensors arena – where hype outweighs horsepower – Maketronics did something radical: they shipped a tool that works.

They leveraged ESP32 not as a crutch but as a validated industrial workhorse. They baked OTA recovery into the firmware because factories can’t tolerate “oops” moments. And they respected the ancient protocols (ADS, Modbus) that actually run our world, instead of demanding factories upgrade their entire infrastructure for “the cloud.”

Is it flawless? Unlikely. Every industrial product hits snags nobody predicts – like that USB-C power quirk. But Maketronics’ transparency (“lessons learned, new tools”) suggests they’ll iterate with engineers, not VC slide decks. After years of IoT snake oil, RadSense 1 feels like water: unsexy, utterly essential, and life-saving when you’re drowning in bad data.

So kudos to Maketronics. For the first time in ages, an IoT startup made something I’d actually deploy in a factory. Now if you’ll excuse me, I’ve got a date with my oscilloscope – and it’s not to debug another “smart” refrigerator.