By now, sbitx/zbitx software has grown wild and unwieldy. changing one thing affects another.? The trouble with?modem_poll is an example of this.? The modem_poll searches for the MODE field, that is, an iteration of around 100 fields, comparing strings, one character at a time. the modem_poll calls functions lookup the fields through this linear search in many places, and it also calls on millis() function to get the timings. The millis() in turn is a system call that can take about 1 micosecond to execute as it calls clock_getttime(), a system call. I am trying to see what all can be left or taken out of the modem_poll as it is not just the CW modes but other modes too need to be tested when changing just the CW polling ticks.? I am at work, having just recovered from a nasty bout of food poisoning. I will have an update for this. I am glad that Erik found a fix, It would have been even better if he had forked the code on github and generated a pull request (A 12? minute tutorial video is here?). This will be fun for everybody and less work for me! - f?? On Wed, Apr 9, 2025 at 5:35?PM Frank KG9H via <kg9hfrank=[email protected]> wrote:
|