Installation
- Tiva Flash utilities and drivers can be found in the repository under Tiva_Flash_Utilities
- To update the Nextion firmware over USB you need at least firmware v2.0 and the Nextion Editor. On the Syntherrupter, go to Settings->USB FW Update. Connect the Syntherrupter to your PC. More infos about updating the Nextion firmware with the Nextion Editor can be found in their documentation, chapter 2.1 and chapter 4
- If you have Nextion Editor v1.61.1 or higher you need to update your Tiva firmware to v3.1.0 or higher before you can update the Nextion firmware.
Notes
- Since the amount of coils that can be controlled by the Syntherrupter has to be set at compile time I attached Tiva binaries for 1-6 coils.
- Multiple Nextion/TJC displays are supported. Chose the firmware according to your model number. If the Nextion version doesn't work, try the TJC version; some displays are not marked correctly. More infos in this forum post.
- If you flash the Tiva for the first time or increase the coil number always check ALL settings. You should check it after each update, too. Just in case...
- Nextion firmware versions 3.0.1 or higher are not compatible with Tiva firmware lower than v3.0.1.
- Nextion and Tiva firmware versions 3.1.0 or higher are not compatible with any previous versions.
- Nextion and Tiva firmware versions 4.0.0 or higher are not compatible with any previous versions.
New "visible" features
- A new release? Again? Litterally one day after the last one?
- Yeah, see we're talking about a beta. I fixed some bugs and a release is more or less 3 clicks (mostly automated). So... why shouldn't I? No one is forced to update so frequently if (s)he doesn't want to. And spoiler: no one does.
New "invisible" features
- Fixed some bitshifts in the Nextion firmware that could have caused issues with very large numbers (f.ex. ontime >32ms)
- Fixed the backgrounds. Actually the backgrounds were working as expected (stopping the outputs) - except for the one from the new ADSR Settings page which hadn't been configured yet. But the text components that should behave in the same way all had a bug. In theory it shouldn't have worked at all on any page but strange enough it did in most cases? Which makes no sense to me but that's no problem. It's fixed now. For sure. This bug is the main reason for the release because its safety related and I don't want to keep that update hidden because I released an update yesterday.