By Eamonn Ryan derived from a SAIRAC Johannesburg Centre TechTalk on 12 February
In the February SAIRC Johannesburg Centre TechTalk presented by Robert Fox, SAIRAC national president with over 31 years of experience, he discusses the critical differences between open-source and proprietary solutions for HVAC systems. As a senior cost and design estimator at Club Refrigeration, Fox has extensive insight into both the challenges and benefits associated with each system. This is Part 5 of a ten-part series.

Fox offers a balanced perspective on the learning journey for HVAC controls programming. Wirestock/Freepik.com
Lastly, Fox discussed the different paths to learning HVAC control programming for those looking to enter the industry:
- Formal training: Many companies sponsor training courses for their employees through controls providers. These programs typically come with a cost but provide structured learning.
- Self-study: For those new to the industry, self-study is another option. Fox mentioned that online tutorials and resources are abundant, though there is a mix of high and low-quality content.
- Colleges and bootcamps: Colleges and coding bootcamps offer specialised programs where students can learn the basics of programming, including HVAC control programming. These programs can provide a more in-depth understanding of coding concepts.
- Programming concepts: Fox points out that if someone has never done programming before, learning controls programming could be challenging. Having a solid foundation in programming concepts is essential, especially when dealing with graphical programming and code integration.
The roadmap to learning HVAC controls programming emphasises the importance of a strong programming foundation, whether through formal training or self-study. With the right tools and knowledge, HVAC professionals can create robust and scalable solutions for their clients.
Proprietary systems are typically well-tested and proven in real-world applications, which makes them a safer choice for critical systems. Fox emphasises that such systems are generally more reliable and require less effort to develop.
One of the major benefits of proprietary products is the availability of technical support. If something goes wrong, you can quickly reach out to the supplier’s support team, which is invaluable in time-sensitive situations.
Proprietary companies often have dedicated R&D departments that work on continuous improvements and product testing, ensuring that the products are up-to-date and function reliably.
The fact that these systems are well-documented and widely used means that they come with a degree of trust. Fox points out that in critical applications, such as controlling a high-value stock, relying on a proprietary product reduces the risk of failure.
Final thoughts on programming
Fox closes by encouraging anyone looking to get into programming to have fun experimenting and coding. While there is a lot of useful material available online, Fox warns that not all of it will work as expected, and much of it is untested. This trial-and-error process can be frustrating but is ultimately part of the learning experience.
He also reiterates that while proprietary solutions offer significant benefits, especially in terms of reliability and support, open-source solutions provide opportunities for hands-on learning and skill development. The key takeaway is that both approaches have their place in the HVAC industry, but their suitability depends on the project at hand.
Fox offers a balanced perspective on the learning journey for HVAC controls programming and the decision-making process between proprietary and open-source hardware and software. He stresses the importance of building a solid programming foundation through self-study and formal training while also weighing the benefits and risks associated with each approach to hardware and software in real-world applications. The choice between proprietary and open-source solutions is ultimately driven by the nature of the application, the associated risks, and the level of support required.