There are several alternative firmware versions available for use with the µBITx transceiver. So why has the KD8CEC firmware been so successful with uBITx owners?
Some key reasons put forward by uBITx.net:
- KD8CEC firmware is fully compatible with the standard issue kit. No hardware changes are required to make it work. This is a critical point of difference with all of the other variants, and probably the most important factor associated with the success of CEC firmware.
- No custom wiring changes are required when using the firmware. This is a further significant factor in widespread adoption.
- The firmware fixes problems that come with the factory firmware – although some argue that CW modes are still not fully addressed in the CEC firmware.
- Using CEC firmware means no loss of features from the default factory firmware. Other alternatives offer fewer or different features from the factory firmware.
- Users are familiar with the user interface, as it reflects the default firmware’s “look and feel” with the standard display supplied with the kit.
- It is easy to upload a hex file to the Raduino. Constructors without a working knowledge of the Arduino IDE can upload files easily.
- All full releases of CEC Firmware are available as open source firmware. This follows the same structure as the original code, although most of the code has been replaced. Open source is not released for beta versions (and for good reason).
- No additional processor is required, unlike other firmware variants. A mechanism for adding additional processors has been added in ver 1.097 (Beta). This promises a future where multiple processor support will be available. You won’t be locked into a single processor type.
- Addition of a Nextion display or additional processor is relatively straightforward.
- The firmware on the Nextion display can be edited by others to provide a different “look and feel” or to add or subtract features. This is independent of the firmware for the transceiver.