Scott Williams, a guest who previously discussed the business of consulting, now dives into the technical side. Topics include an electronics project for bottle and can management, using Raspberry Pi CM4 for quick prototyping, the challenges of cameras in products, deciding between microcontrollers and microprocessors, selecting the right components, creating a bin sensor, evaluating tech stack components and IoT platforms, and the unpredictability of product design.
ZenTronics prioritizes refining processes and improving project documentation over rapid expansion.
ZenTronics selects components based on familiarity, reusability, and specific requirements.
Efficient integration of existing sensors and systems is a priority for ZenTronics in their projects.
Deep dives
Consultancy focus and growth
The consultancy firm, ZenTronics, has seen growth in their team, expanding from six to eight members. However, they plan to focus on refining their processes and improving project documentation rather than further rapid expansion. They prioritize providing valuable services rather than just selling time.
Factors in choosing components
When selecting components for projects, ZenTronics considers factors such as familiarity, reusability, and the specific requirements of the project. They tend to rely on microcontrollers like the ESP32 for Wi-Fi applications and Nordic for Bluetooth applications. They also use SDMs for other applications and prioritize the use of real-time operating systems to optimize performance and efficiency.
Navigating technical decisions
ZenTronics strives to make ethical and informed decisions. They prioritize effective communication with clients, guiding them through technical concepts and trade-offs. They aim to select components based on the project's specific needs and avoid making choices solely based on personal comfort or familiarity.
Considerations in integrating sensors and systems
Projects often involve integrating sensors and systems already available in the market. ZenTronics focuses on effective integration, choosing components that are compatible and establishing drivers, templates, and examples that can be reused from project to project. This approach allows for efficiency and time savings while ensuring the project's success.
Importance of not reusing entire blocks in electronic design
In the podcast episode, the speaker emphasizes the importance of not reusing entire blocks when designing electronic components. While components like buck converters may be reused, each application has unique requirements, such as different input voltage and output current. Copy-pasting entire blocks is not only unethical, but it also lacks engineering discipline and traceability. Designing components on a case-by-case basis allows for greater customization and ensures proper design and documentation practices.
Challenges and considerations in choosing IoT platforms
The podcast episode discusses the process of evaluating IoT platforms. With a plethora of options available, including big players like AWS and more niche platforms like ThingsBoard, choosing the right IoT platform requires careful consideration. Factors such as support, scalability, and the specific needs of the project need to be evaluated. While big platforms offer more features and support, niche platforms may provide more tailored solutions for specific hardware requirements. The podcast highlights the importance of finding a platform that can be easily integrated, ensuring a seamless transition from hardware to software for a successful project delivery.
Chris listened to the episode and wondered if Scott would get more pulled into management of the day-to-day
There’s a new program in Victoria (Australia) to enforce deposit/rebates on bottles and cans. This opened up an opportunity for an electronics project.
Bin management is another common IoT project
Industrial – Site Hive is a long-time customer in the construction space
Consumer goods
Scott said he’s likely to reach for a Raspberry Pi CM4 for quick prototyping/POC
Wht about the high density Hirose connectors?
Does Xentronics “go down the stack” by using tools like Buildroot / Yocto?
Cameras make products much more difficult. Raspberry Pi cameras have a CSI interface but aren’t “standard” per se.
When starting projects, Xentronics is likely to pull out ESP32 for WiFi, Nordic for Bluetooth, STM32 for generic processing
Bare metal vs RTOS? Normally they start in the RTOS space to add things later
