Why is my Meadow app always named “App.dll”?
The Meadow Core stack has a hard-coded requirement for Meadow Apps on the F7 platform to be named either “App.dll” or “App.exe”. This requirement is actually a bit of a legacy carryover from the beta days. Originally, when the Meadow stack only targeted the…
Creating Lightweight HMI with MicroLayout
If you’re working on an IoT project with a display, then you’re almost certainly wanting to show information to a user. Drawing that information using drawing primitives can be both cumbersome and non-portable. We at Wilderness Labs have released our MicroLayout library to help…
Meadow App Settings
It’s pretty common for an IoT application to need to read persistent but changeable settings at startup. Meadow applications have long supported the app.config.yaml file for settings to control behavior of the Resolver.Log, the device’s lifecycle behavior (e.g. restarting on an uncaught exception) or…
Meadow and RS485 (and Modbus RTU oh my!)
If you’re building an industrial embedded application, you’re probably aware of the RS485 standard. It’s been an industry standard for decades and it persists because it’s both simple and works very well over long distances and in EM-noisy environments. The Wilderness Labs Project Lab…
Device Logs over UDP
Developing applications requires debugging and in most embedded projects this means writing to a logger. Meadow is no different here. If you’re familiar with Meadow development, you’re probably familiar with calling the various methods on Resolver.Log but you might wonder why we recommend you…
