Jump to content

What does it take to be an IoT engineer?


Recommended Posts

End Game in the IoT

It’s been a long autumn and winter effort completing development of a CAT-M1-based on-farm data logger for release in the southern Spring, now only two days away.

These product development sprints are a long litany of small crises that are surmounted and left behind in the rear-view mirror.

When you’re stuck in the middle of it, it feels like crawling over broken glass.

But we have early orders, some stock on the shelf with more next week, and rudimentary field trails conducted that have already thrown up a weird software bug in the ultra-low power state that this logger depends upon to keep energy consumption within budget. A software work-around nipped that in the bud before it got released into the wild.

Our marketing department have been on the road, talking up the benefits of a completely new Internet-connected data logger that’s attractively priced and robustly packaged. This new product offering has been enthusiastically embraced by our key agents.

Great technology is indistinguishable from magic.

In this case, much of the excitement would appear to be generated by the simplest part of this technological wizardry: the coloured light behind our Green Brain symbol. This indicates CAT-M1 network connectivity, data transfers and GPS fixes to the guys with the muddy boots working under primitive conditions out in the field.

834872259_20190816_165456(1).thumb.jpg.47bca34e2a7b15c2dc3886a0840671c5.jpg

This is MEA’s third IoT development in eighteen months, with two more key projects beginning as soon as this new technology is properly bedded down.

I’ll lead the product development team through the coming Spring and Summer, until my 67th birthday next March.

So, the real end-game in this IoT race is actually to invest the next generation of MEA engineers with the spirit of the sprint, a ‘can-do’ ethos and the sense that with hard work, anything is possible.

Link to post
Share on other sites
  • 4 weeks later...
  • Replies 85
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Hi Andrew, the topic you raise is spot on, and is a core item I will address in my webinar on 5th July. The IoT when considered top-to-bottom - ie from the Cloud down to deloyed Things - encompas

Hi Geoff Three of us at MEA listened to your inaugural talk this morning on the IoT and thoroughly enjoyed it. You handled question time with panache and told us a few things we didn't know

When all is said and done, there has usually been more said than done! This is surely true of the IoT. I agree with IoT’s promise, but see few of its practitioners. Much of the IoT hype

Posted Images

Cash-flow in the IoT.

Even for a mature company like MEA, the expensive business of IoT product development can be a scary process.

It’s always a race against the clock, as one burns cash reserves against the promise of returns from early sales of new-to-market products.

More companies go broke from cash-flow crises than anything else.

Just a few weeks’ delay in product launch can invoke such a cash-flow crisis (unless you have extraordinarily-deep pockets).

This is especially true in a seasonal business such as irrigated agriculture – late to market can be disastrous. What might well have sold a month ago must now wait a further eleven months to be of interest to customers. If – that is – some competitor hasn’t gained the upper-hand by then…

However, when all that risk pays off, it’s a true delight.

Cash flow turns positive and management breathes a sigh of relief.

These last few weeks before product launch of MEA’s CAT-M1 on-farm IoT data logger have had all those elements of tension, suspense, crisis and fear. Last-minute software bugs, production issues, field trial feedback, creation of extra test jigs and finally, ramming product through the new production line – all these things added to the pressure.

As Engineering Director, it’s my job at these times is to stay outwardly calm and cheerful, buffering an engineering staff beset by technical problems from marketing staff beset by an agent network clamouring for product delivery.

Today – just a few weeks after product launch – we’re well on the way to selling out of our entire first production run of 100 units. Funds expended in their manufacture will now flow back into the company coffers.

Now we face new challenges to our cash reserves; we have to swing into full production, investing in greater numbers of units while seasonal demand lasts and before the rapidly dwindling existing stock of these new loggers runs dry.

Such is business.

1497510515_TablegrapeGBL-C.thumb.jpg.0e11ae53ef657c882b1258ac597c6f8f.jpg

A brand-new MEA solar-powered CAT-M1 data logger for soil moisture monitoring, deployed in table grapes in the Victorian ‘Riverina’ region. Neatly installed at the foot of a wooden trellis post (in the foreground), the GBL-C logger is safe from farm machinery and foxes and hares that chew exposed cables.

 

Link to post
Share on other sites
  • 1 month later...

Primitive upgrades in the IoT.

If the first casualty of war is truth, then the first casualty of product launch is confidence.

The harsh reality is that following product launch burgeoning deployments, the passage of time, the machinations of Mother Nature and the compounding of human errors will eventually throw up a bug; it’s a numbers game.

Such bugs end the ‘jubilation phase’ of a successful product launch and call in the ‘humiliation phase’.

In an ideal world there would be no in-field bugs causing customers and agents distress. Lengthy and private field trials over hundreds of farms in multiple crops right across the country would have shaken out all such gremlins.

In the real world of practical IoT engineering, such a leisurely approach to perfection is denied the product development team. Commercial, budgetary and market imperatives intrude.

The first customers become the beta testers.

MEA’s CAT-M1 IoT data logger launched just in time ­ – in early September 2019 ­­– and our prototype stock of 100 units was sold out within three weeks.

Now, that’s a great feeling!

A long and sustained period of intensive product development effort was rewarded by first-to-market status and demand outstripping supply.

As a consequence, the emphasis shifted immediately to boosting production to meet back-orders.

In the meantime, data flowed to Green Brain from 80 sites, and down in the MEA basement those of us in the product development team waited anxiously to learn our fate.

Had we out-witted Murphy’s Laws?

Nope!

Finally, after a lengthy silence from the modem manufacturer and increasingly strident demands in the engineering forums, the chip maker admitted to a firmware bug that’s been the chief cause of our lack of confidence; they acknowledged a combination of events that could lock out connection to the Internet through a failure to safely enter ultra-low power mode.

Weeks after our product launch, they released a new firmware version purporting to have fixed the bug.

Simultaneously, reports began to arrive back from the field showing product lock-up after weeks of perfect operation. Data just stopped flowing from a modest percentage of stations.

AAaaHHhRRrr!

More midnight oil, and we upgraded to the modem manufacturer’s latest firmware – incorporating the critical bug-fix – and we tightened up a few possible edge-cases while we were in there; anything to improve safety and fault recovery.

Here’s where over-air programming (OAP) would have allowed us to seamlessly upgrade all deployed systems without leaving the office.

That developmental luxury had been set aside under time-to-market pressures and slated for Version 2 release.

Without that remote upgrade facility, our techs had to load up the company truck and head out into the vineyards and orchards of our irrigated agricultural districts to begin the laborious task of individually and directly upgrading those first deployed units (photo, below)

The silver-lining in this debacle is that the engineering team now has a stronger case for developing an over-air programming facility in these new loggers, expensive though that development will be.

A week has passed, the truck and its weary tech are back in Adelaide and every deployed CAT-M1 logger is back on the air and bullet-proofed as best we know how.

New stock is due in next week and life will return to normal, whatever that is around here.

image.png.5722f3ada990c913adc9992c5a2fdc67.png

MEA's open-air Green Brain Logger upgrade station somewhere in rural Victoria.
Our reserve stock of 20 units – loaded with the latest firmware – is swapped into field sites and the older versions get to enjoy the sunshine on some local park bench while their heads are upgraded. Then another round begins, with the attraction of over-air upgrades rising by the kilometre.

Link to post
Share on other sites
  • 3 weeks later...

Frustrations in the IoT.

It’s a day marked by high winds and even higher temperatures, with the ‘Fire Danger Index’ ratcheted over to ‘Catastrophic’ and 14 bushfires burning throughout South Australia.

All this is perfect for testing worst-case conditions for an ugly problem that’s taken nearly two months to resolve; ‘noise’ in our CAT-M1 IoT loggers when making ac resistance measurements in soil moisture tension sensors called ‘gypsum blocks’, invented nearly eighty years ago.

Frustratingly, the CAT-M1 network is down again; we later find that Telstra are installing a 5G network in the area and hence the intermittent LTE-M service. I’m having to bite my nails and trust in the data logging function to record the performance of this upgrade versus the faulty ‘control loggers’ mounted alongside it in the MEA Test Yard.

‘Noise’ to an irrigator looking at his soil moisture data  means data bouncing about in some unseemly fashion that frustrates easy interpretation and that destroys confidence in the equipment.

‘Noise’ to an electronics engineer means electrical noise, and I’ve ploughed through endless measurements chasing elusive sources of spikes and other artefacts that can fool modern analog-to-digital converters. Fixes, patches, filters, firmware changes, more careful grounding – nothing makes any difference to the lousy data spewing forth.

I’ve worked on this type of ac measurement through four-generations of gypsum block loggers. The problem is to generate a pure sinewave at the lowest possible cost. In this latest evolution, I’ve managed the sinewave generation, gypsum block excitation, gain block and full-wave rectification in a single quad op-amp. But it’s not working under field conditions…

Finally, I push my test regime up beyond the 53° limit of our ancient environmental oven and the problem shows itself at 64°; it’s temperature-related, and being exacerbated in this new logger operating up to 70° thanks to its built-in solar panel. The digital circuitry doesn’t care, but the analog circuitry does. The sinewave collapses with temperature, and what looks like noise is actually a quantization error brought on by collapsing range, despite being held in check by proper ratiometric measurements against internal reference resistors.

My fix of four extra resistors works in this worst of hot weather, and as a bonus I find that I can now run these sensors over tens of meters of cable; handy for odd deployments of gypsum blocks on particular farms. Sensor output is rock solid.

Now MEA need only endure the product recall of the dozen units released to beta customers.

Sure, I could have generated that sinewave with a digital-to-analog converter for $20, and I’ve done that in the past. But my 20-cent solution will serve the company better as we strive for a mass-market, riding on the coat-tails of the IoT wave.

In the immortal words of Arthur M. Wellington “An engineer can do for a dollar what any fool can do for two.”

Link to post
Share on other sites
  • 3 weeks later...

The IoT under the Microscope.

Terror stalks the floor at MEA: Christmas is only a fortnight away and sales orders for our new CAT-M1 data loggers are raining down from above.

But production has jammed: SD memory cards are failing to pass production testing and the engineer who designed this part of the circuitry is incommunicado somewhere in Europe.

Our production engineer is going quietly mad with fear and frustration.

I need to step in.

It’s now 45 years since I graduated in electronic engineering from the South Australian Institute of Technology so these moments of terror are nothing new, though their impact never seems to diminish.

At these times I follow a standard routine to bring the young engineers through the crisis, while knowing full-well that I can no longer solve many of these problems myself. Designing IoT technology is a team effort. No single one of us on the product development team has all the skills to function alone.

So, I stay outwardly calm and clear some mental and physical space to sit down in a quiet place with our production engineer. I ask to be walked through the history of the problem. Then we take a look at all the circuit schematics and relevant data sheets.

It’s not that I am here to fix the problem myself, but merely to act as a mirror and a sounding board, asking penetrating questions if I find a weakness in the fabric of the case and quietly letting these talented youngsters solve the problem themselves.

The problem itself is simple enough. MicroSD memory cards that worked in previous batches and previous products don’t work in this new product though circuitry remains the same. Even part numbers remain unchanged. Worse, devices from the same manufacturer work from one source but not from another. We scour the computer stores around Adelaide, buying up small handfuls of different memory cards for testing, then ordering up many hundreds of the apparent successes from warehouses interstate. These then fail on arrival to work at all.

Nothing makes any sense.

Just for something to say, I ask to look at the schematic for the jellybean ESD protection part that protects the memory card from damage from static discharge during installation.

Whoa!

I’m no digital genius, but us old analog engineers recognise a low-pass filter when confronted by one; this thing is sitting on the memory card data bus, as it has done in previous products from this modem manufacturer, and has never before caused problems. I ask for it to be removed and tracks bridged over.

Suddenly, all the lights come on and even our worst-case memory cards start passing test.

Once again hardware re-work is needed. This is only possible thanks to a beautiful new microscope, beloved of all of us aging techos squinting at parts having twelve legs in the space of tiny resistors that have only two.

20191211_103117.thumb.jpg.41f0d0509af36eb8cbe64ba460a5cf5a.jpg

The production line grinds back into life and filling back-orders before Christmas is once again a possibility.

Off to the side, we rotate our techs through the microscope desk, laboriously upgrading valuable PCB assemblies with this new fix then feeding them into production.

Should I be feeling professionally remiss that this happened at all?

Nah! Software engineers roll out fixes seemingly forever.  Scaling up production in the IoT will inevitably produce more of these moments of terror, allowing me to invoke yet one more old adage:

“When the going gets tough, the tough get going!”

  • Like 1
Link to post
Share on other sites
  • 1 month later...

Tripwires in the IoT.

Once more to the barricades…

MEA’s new CAT-M1 IoT data loggers – like the majority of Australians – have their own SIM cards and (a meagre 3Mb) data plan.

But with the production line rolling and the number of deployed loggers rising inexorably some way of keeping these bulk data plans in check proved critical. Fortunately, specialist companies provide boxes of 100 SIMs and platforms for generating alerts when things go awry.

Just weeks into the new decade we hit a tripwire: a significant number of loggers are exceeding their data allowance while draining batteries.

At the same time, data flow inexplicably becomes bumpy from all these new loggers. Customer complaints hit our agents who hit our marketing folk who hit up product development for answers and action.

What’s going on?

Once again, we huddle in corners and pore over screens and flowcharts and circuit schematics.

Within the week the source of all these woes comes to light; two hundred loggers locked to UTC time hit up Green Brain at exactly the same moment and jam the Green Brain server CPU to 100%. Late comers who can’t get through and deliver their data get shrugged off and must try again, at the expense of a finite energy budget or no luck at all before communication attempts time out four minutes later.

This feels like a denial of service attack!

But we’re on Google’s IoT platform and the Internet is supposed to be infinitely elastic, surely? There’s no scalability if we are saturating with deployments still down in the hundreds…

It turns out that this problem is something that never occurred under our older Plexus ftp data transfer systems; those were solidly buffered. Green Brain Loggers use newer https secure data transfers. It transpires that Green Brain runs each logger’s database interaction to the bitter end before moving to the next caller. Buried in there is a ‘backup-to-server’ piece of code that’s taking forever. Things only get worse as the day rolls on and the files to be retrieved and appended just get bigger.

The Green Brain boys excise that redundant piece of backup code and once again we’re back on track. CPU activity drops back into the normal range and deployed systems get through to the mothership with metronomic certainty.

Phew!

But something good has come from all this; we’ve discovered a source of universal ‘roaming’ international SIM cards for our CAT-M1 loggers. We get samples in from the USA and they work exactly as described.

Green Brain loggers can now be deployed anywhere in the world after set-up and test in Australia. They simply log onto whatever telco network is providing the strongest CAT-M1 signal when they arrive on site.

Prices are good, service is great and – best of all – we can set up our own trip wires to generate alerts and track deployments and activity on-line.

 

20200204_164353.thumb.jpg.ae93ed9d63ba8033b03c432b61159040.jpges t

Waiting patiently for the trip wires to trip...

Link to post
Share on other sites
  • 2 weeks later...

One Small Anniversary in the IoT.

At 3pm exactly a year ago today (19th Feb 2020) MEA transmitted the first 20 bytes of measurement data on the Myriota satellite network from the MEA Test Garden.

Data consisted of four measurements of soil moisture tension in the soil profile below dry-grown Shiraz grapevines, plus battery voltage.

After the first anxious few months – where I peered at the incoming data on a daily basis – a certain trust developed that data would keep flowing, and other developments took priority.

Along the way though, I checked in on the growing Green Brain data set and sought explanations from the ever-helpful folk at Myriota about spikes, missing data records and long latencies. We were managing four to five readings per day via a single Myriota satellite in polar orbit.

Our understanding of this new IoT technology crept forward with the seasons.

Other test installations followed during March and April 2019, from stations monitoring tank water level, rainfall and micro-climate.

A year later the soil moisture record is sufficiently consistent and detailed to track rain-fed irrigation suitable for sub-surface moisture measurements in dry-land agriculture, should we choose to exploit such a market.

813520872_ShirazFirstAnniversary19022020.thumb.png.4af367b0a95b9b2da69fea2e78d58d0b.png

Link to post
Share on other sites
  • 2 weeks later...

Powering the IoT.

A positive energy budget is a ‘sine qua non’ (absolutely essential condition) in an IoT field station.

Early MEA data loggers deployed in agriculture were battery-powered affairs, but unless the battery capacity is adequate for 3-5 years the logistics of battery swap-outs – with their inherent risk of breaking environmental seals put in place in the factory –  can increase user frustration and shorten product lifetime.

Energy harvesting via solar panels extends product field life indefinitely; we now have thousands of IoT solar-powered sites still in service after up to seven years.

Despite this wealth of experience, each new product release raises our collective anxiety for at least a solid year after field deployment.

Canopy growth, bird netting, dirt build-up, high and low temperatures, white plastic rain covers over table grapes, seasonal changes in solar zenith angle, shorter winter days, periods of extended cloudy weather, poor installation, weak solar panels, excessive loads – all these things call out weaknesses in the energy budget.

And so the arrival of eight CAT-M1 IoT field units back to MEA’s service department triggered immediate self-doubts and a heightened forensic investigation.

In two of the units, the solar panel had come loose from the motherboard; this is a product assembly failure corrected by rapping knuckles and dreaming up post assembly tests.

Four more worked perfectly as designed and operated for week after week in the test yard without a glitch; the only possible explanation would be unknown field conditions, such as canopy over-growth.

But the signature lesson flowed from the last two units, highlighting a design flaw that can only occur if battery voltage falls below about 3.3V for a single-cell Lithium-Ion battery operating in the 3.6V to 4.2V range. The logger refuses to wake up.

Our original intent had been to have Green Brain monitor battery voltages for all deployed units and to send commands to shed load and reduce logging rates to automatically balance the energy budget. Somehow, we never implemented that in the first release.

So we do what we should have done in the first place – implement a hardware belt-and-braces solution to shed load based on battery voltage. Firmware gets tweaked as well.

With the immediate problem solved, we re-examine our diagnostic tools.

We need something better than just watching battery voltage traces, so we incorporate additional solar charge monitoring circuitry. ‘Gas-gauging’ the battery load would also be good using coulomb counters, but this proves difficult to implement quickly and at low cost. We defer that to Release 3.

But we have one more trick to help us extend the energy budget; we can ship field stations at full charge while also testing the charging circuits between solar panel and battery. The first month’s operation is on us!

We build a bulk charger capable of handling 120 logger boards at once (see photo). All this is made possible by diligent hunting on eBay for a low-voltage high-current power supply rated at 8V and 50A, all for $500.

20200221_091040.thumb.jpg.3fdf77077b0edd299e7d90acf1d709a4.jpg

A custom-built ‘bulk charger’ for MEA’s CAT-M1 data loggers handles 30 PCBs at once, with an additional three charger racks still within the capacity of the low-voltage high-current Hewlett-Packard HP 6551A power supply. Full overnight charge takes about eight hours.

Link to post
Share on other sites
  • 3 weeks later...

Edge Cases in the IoT.

Time’s dragging in the MEA labs; we’re grinding out the finishing touches to Version 2 of our GBL (CAT-M1) data logger and it’s painful.

Ah, but it’s always like this!

With some hundreds of these new loggers in service for the past six months, three units have been returned to the product development team exhibiting weirdness.

Yet these pain-points are exactly what we must eliminate here and now, so we’re holding up production of future stock until we resolve these edge-case issues to our satisfaction.

Future ugliness would be our certain fate if we let these glitches go feral.

There are three issues, and it’s testing the ‘cures’ that’s taking up all our time and ratcheting up stress levels as we deal with technical uncertainties under a marketing and management cloud.

Such is an engineer’s daily fare.

To resolve Issue 1, we need a hardware safety mechanism to shed the load under low-battery conditions: small improvements to the battery-monitoring circuit and start-up logic fix this. We are also unconvinced that electronic eFuses fit-the-bill at the minuscule current levels found in IoT devices. We take the opportunity to toss those out and replace them with software-controlled electronic load switches instead. We tick this first box.

Issue 2 fixes the ESD protection circuits of the SD Memory Card; turns out those old ESD devices just weren’t handling the higher-speed data transfers occurring with this most recent modem technology. The fix is hacked onto the PCB and works perfectly in the MEA test yard. But by now we’re rightly worried about higher-temperature operation because there is some indication that that’s what triggers the fault condition. We take our ancient environmental oven apart and update it to a digital PID temperature controller (available on eBay for $23) that allows us to soak test at 70°C ± 0.8°C then ramp down temperature to ambient. The new design checks out perfectly over the full temperature range while the old ‘control’ unit locks up at 48°C.  The new design is approved as ‘tested’.

Issue 3 arose through human error – a production-line failure to securely plug the solar panel into the motherboard on two units during final assembly. We tweak the production line process to catch this condition. Yet what we really need is sharper diagnostic tools for monitoring battery charge current during five different field scenarios. We design this into the hardware and firmware while we have the chance. This charge-current trace will allow our service team to differentiate between solar charging failures and faulty load conditions if battery voltage is declining.

Once all boxes have been ticked and I sign off on changes, we’ll modify the motherboard schematic and PCB, change the Bill of Materials and generate the updated Gerber files.

We’ll be good-to-go.

But by now the COVID-19 pandemic has hit and the Aussie dollar is plunging against the US dollar that is our standard manufacturing exchange currency.

Fortunately, nearly all components for this latest production run were paid for back when our currency was stronger; it’s only the PCB and assembly costs that have to be paid for in our weaker coin.

Despite global uncertainties, forward is the only way for MEA to go: we have back-orders to fill.

image.png.1cfc128c1819b67478d53bb9637e4309.png

Our old environmental oven gets fitted with a new PID Temperature Controller.
Looks ugly, and yet it’s strangely hot!

Link to post
Share on other sites
  • 3 weeks later...

A Virus in the IoT.

Geeks have got it good in this post-normal world: vulnerable old folk like me are sent home and told to stay away from the office.

Are you kidding me?

Home is where my garden is, my own personal sacred site that is at the root of my interest in agricultural technology and irrigation.

Home is also where my favourite lab is.

Here, I have two benches.

One is set up with all the fancy test equipment I need to create and test MEA stuff.

The second one (pictured below) is where I fix my eBay-acquired fine old test instruments from back in the 1960’s and ‘70s when I was undertaking my first electronic engineering degree.

Fixing stuff hones one’s problem-solving skills*. Gear that worked once is a closed problem with a single solution: it should work again.

The quality of thinking that went into these old knob-driven instruments is exactly that of today's Masters. Only the technology has changed, not the engineering mind-set.

And finally, old test equipment is admirably accessible for fixing. It’s also beautifully documented – an education inside shabby covers. I spend as much money on old manuals as I do on Tektronix plug-ins. I particularly love the fold-out schematics which I pore over endlessly until I can finally understand how a circuit really works.

Yesterday I was in one of my usual funks.

In the past seven years I’ve worked on long-haul ZigBee, Bluetooth, satellite, 3G and CAT-M1 IoT products for agriculture: they’re all out there across Australia, contributing to the 3 billion+ data records up there in our Green Brain web app.

Now what?

The remedy for such a bad dose of the blues is a 1960’s day.

So yesterday I played hooky from Slack, Trello, Gantt charts, emails, texts and phone calls back to the office and my far-flung staff.

Instead, I repaired a wonderfully old 1968 Nixie tube 8-digit counter. The 15V supply regulator came back into regulation with the help of a new PNP control transistor. I threw out the old beryllium-filled oven-controlled crystal oscillator and hand-built a modern one (no purists around here – it just has to work!) I pin-pointed a temperature sensitive old TTL decade counter that was shutting down two of the eight time base channels in the ranging function.

Today I awoke – back in my modern IoT world – with a fully-formed concept in my head for how to measure soil-moisture content in irrigated pot-plants in commercial tree nurseries. There's always someone wanting me to work magic for beer-money, and I’d set this problem aside for a rainy day.

It seems that a day among the Nixie tubes is also sub-conscious therapy for an old brain taxed with new IoT problems.

image.png.2f42f62280ee920ffbf08c8eacd958b2.png

My 1960’s ‘funk-fixing’ bench, courtesy of Jim Williams and eBay

*‘The Importance of Fixing’: Jim Williams in ‘The Art and Science of Analog Circuit Design’.

EDN Series for Engineers. Butterworth-Heinemann

Link to post
Share on other sites
  • 3 months later...

Whistling in the IoT Wind.

By a strange twist of fate, I find myself back where I and MEA began in 1984; in the wind energy business.

Over the intervening years renewable energy has gone from ground zero in Australia to mainstream, and I’m no longer regarded as a tree-hugging sandal-wearing bearded fringe-dweller.

Fortunately, this new application is solidly ground-based.

Where once I was conducting field measurements on tall towers on potential wind farm sites, MEA’s latest CAT-M1 data loggers are now magnetically clamped to the base of giant wind turbine generators, back-hauling a clever sensor that’s listening for extraneous acoustic signals that mark hail or lightning damage to million-dollar turbine blades.

The real technological wizardry in this application is not mine; MEA’s job is only to connect this new sensor to the manufacturer's web platform. ‘Ping Monitor’ is a local Adelaide start-up whose intellectual property in the acoustic realm makes all this possible through the development of a specialised microphone-based sensor (Figure 1) backed up by deep understandings embedded in the sensor's algorithms.

The beginnings of this informal partnership between MEA and Ping had its roots in a simple request for me to talk to Ping's CEO about the shift from consulting to manufacturing. Always happy to talk technology and engineering to young folk, I’d kept in touch over the occasional coffee and followed their journey with interest.

Only when their resources became stretched too thinly in connecting their sensor to the cloud did it occur to me that MEA had been working exactly in parallel with them, and that our combined efforts could be win-win for us both.

So began an intensive product-development program that solved Ping-specific connectivity, sensor power and over-air sensor upgrade issues.

Out of this informal partnership popped an especially valuable step forward for MEA; Ping needed a truly international end-to-end connectivity solution and so organised field trials in the US, a major potential market for them.

While MEA acknowledged the need to someday operate our CAT-M1 loggers in the US agricultural market, the product development team had left the actual mechanics of this to some nebulous future date. Getting to market locally took priority.

With the help of a friendly technical wizard in far-off Massachusetts – who laid our test logger out on his window-sill connected by a USB umbilical cable to a PC running TeamViewer – we were able to remotely iron out connectivity and latency issues to drive data back from the US to MEA’s Green Brain server in Australia.

Key to all this was to find a supplier of SIM cards (coincidently, also located in the US) who could handle international roaming for CAT-M1 IoT devices on anyone’s network. This is a sophisticated firm that has solved all the billing, supply and diagnostic tools needed for this complex activity.

Our logger can now scan all CAT-M1 bands and select the strongest signal and lock onto that – no matter who the service provider might be – changing later if required. This all happens seamlessly, thanks to the thousands of engineers whose shoulders we stand upon to make this magic happen.

Perhaps that’s the true strength of the IoT; that human cooperation and ingenuity can combine in this way to make the complex work simply.

Or – to quote Albert Einstein – “Everything should be as simple as possible, but not simpler.”

image.png.6123e50a22896fd02eda8b0d39eab29c.png

Figure 1. The Ping microphonic sensor (right) is magnetically-clamped near the base of a steel wind turbine tower where it ‘listens’ to the acoustic signature of the blades as they swish past. Clever algorithms can then extract information on any damage to the million-dollar turbine blades, thus providing a preventative maintenance tool.
The MEA solar-powered CAT-M1 data logger (left) provides sensor power, sensor over-air-upgrade functionality and CAT-M1 back-haul to the cloud on anybody’s network, anywhere.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...