Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:blog [2026/08/03 11:00] – mastertailer | en:blog [2026/08/31 20:35] (current) – [New Product News] darkgrue | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Blog and News ====== | ||
| + | ===== August 30, 2026: Launch Imminent! ===== | ||
| + | |||
| + | ==== New App Development Changes ==== | ||
| + | |||
| + | Code-L, our application developer, has been busy updating The Tail Company app during this time. | ||
| + | |||
| + | * Over-The-Air (OTA) update support has been rewritten, and now supports linking OTA files to hardware versions, and having a minimum app version. | ||
| + | * Also, Android Wear support is currently being worked on. Unfortunately, | ||
| + | * Lastly, internal state management for the app has been completely overhauled, everything that holds state is now a singleton class with a state variable. | ||
| + | * New product support is already included. | ||
| + | * New look and feel! | ||
| + | |||
| + | |||
| + | ==== New Firmware Development Changes ==== | ||
| + | |||
| + | Development of TailControl, | ||
| + | |||
| + | But as the new product development progressed, it became clear that managing the problems created by being pinned to an older Arduino and ESP-IDF would not just create problems in the future, as support libraries moved forward with their own development, | ||
| + | |||
| + | * Migrated from the PlatformIO Espressif 32 development platform to pioarduino. This moves us from the Espressif IoT Development Framework (ESP-IDF) v4.4.7 and Arduino v2.0.17 core to ESP-IDF v5.5.2.260206 and Arduino v3.3.7. This gives us access to latest Arduino Core and ESP-IDF, support for newer Espressif hardware, and active maintenance and updates for the development platform. | ||
| + | * Migrated EarGear 2 to the new channel-based I2S driver. The new driver has better resource management, enhanced power management, simplified duplex communication, | ||
| + | * Removed dependency on the JLed library and replaced it with a small custom class built directly on Arduino v3's native API that is initialized later in the system setup, rather than immediately. | ||
| + | * Experimental support for RGB lighting on most products. | ||
| + | * Many bugfixes. | ||
| + | |||
| + | |||
| + | ==== Ever wondered how firmware actually gets developed before a product ships? ==== | ||
| + | |||
| + | Meet the DesqTail - my desktop development platform, and the secret weapon behind our firmware workflow. | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | The concept is borrowed from aerospace engineering, | ||
| + | |||
| + | The philosophy is powerful: simulate reality as closely as possible, without the cost and risk of doing it in the air. | ||
| + | |||
| + | I apply that same philosophy to firmware development through full Hardware-in-the-Loop (HIL) testing. Rather than writing code and hoping it behaves correctly when it finally lands on production hardware, the DesqTail puts real hardware on my desk - running real firmware, in real time. Every product platform we build can be exercised right here, in a controlled environment, | ||
| + | |||
| + | The advantages compound quickly: | ||
| + | |||
| + | * Speed - No waiting for test hardware to be assembled or shipped. Iteration cycles shrink from days to minutes. | ||
| + | * Cost - Catching a firmware bug on the desktop is orders of magnitude cheaper than catching it in the field. | ||
| + | * Confidence - Full HIL means the firmware isn't being tested in isolation or simulation. It's talking to the actual peripherals, | ||
| + | |||
| + | What makes the workflow particularly effective is the immediate feedback loop. While the physical model sits right in front of me - behaving exactly as it would in a deployed unit - I can simultaneously observe live diagnostic output inside the IDE. If something misbehaves, I see it in hardware and in code at the same moment. There' | ||
| + | |||
| + | It's the iron bird principle, scaled down to a workbench - and it changes everything about how reliable firmware gets made. | ||
| + | |||
| + | |||
| + | ==== New Product News ==== | ||
| + | |||
| + | There' | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | I've had the pleasure of working closely with Master Tailer on this, and I'm directly involved in the entire product design and development - something I hadn't had the opportunity to do until now. | ||
| + | |||
| + | We've iterated rapidly through a number of different designs quickly. Each new iteration really jumped the design forward and added new features, which was really exciting. We're going into the start of the Kickstarter strong: firmware is feature-complete, | ||
| + | |||
| + | We're really excited about this, and hopefully you will be too! | ||
| + | |||
| + | Tail Co has also added [[https:// | ||
| + | |||
| + | And don't forget [[https:// | ||
| + | |||
| + | |||
| + | ==== Keep up With The Tail Co ==== | ||
| + | |||
| + | Make sure to avail yourself of the many Tail Company resources, from the Telegram [[https:// | ||
| + | |||
| + | RAWR! | ||
| + | |||
| + | Your Friendly Lurking Horror,\\ | ||
| + | **Dark Grue** | ||
| - | ====== Blog and News ====== | ||
| ===== March 1, 2025: TailControl Love Is in The Air! ===== | ===== March 1, 2025: TailControl Love Is in The Air! ===== | ||
