toggle quoted messageShow quoted text
Jack I like the way you implemented changing frequency steps right there on the screen, it is clean and efficient. I hate to have to dive into menus to fine useful functions that I use frequently, and changing tuning steps is one of those I use on my other rigs.
On Sep 24, 2019, at 09:27, Jack, W8TEE via Groups.Io <jjpurdum@...
Agree, and I have some interesting things I want to try with the 4.0 Teensy. For a while, JackAl used a software timer to track the rate at which the user was "spinning" the frequency knob. If the rate when above some user-defined threshold, we upper the increment factor by 10x. It worked fine, but seemed awkward to us. Because we use a touchscreen with the JackAl, we just put a "floating" cursor above the current frequency (shown here above the '3' digit) and the user can tap the '<' or '>' to move the
frequency increment value. Not the best solution, perhaps, but it works. Plus, if you don't like it, you have the source code to change it if you want.
On Tuesday, September 24, 2019, 6:26:37 AM EDT, John Scherer <jrsphoto@...
Hey Jack! Easier? Sure, ok. But its not always about what easy, is it. If it were, we would just buy all of our ham gear and be done with it. That being said, whats mentioned above isn't that difficult. I used and attiny85 that I programmed with the ArduinoIDE. Works like a champ. The one thing I would love to add is, when I change the step size in the uBitx, I would like to have the radio change the divisor on the fly. For 10 Hz step, divide by 2, for the others by 4. The goal would be for about 2.4 kHz span per one knob revolution when 10 Hz is selected, and about 12 kHz when 100 Hz is selected.
My reasons for going to a higher PPR optical encoder over the mechanical encoder that most use was all about the feel. Most optical encoders have bearings and makes for very smooth operation. The encoder in my uBitx is 128ppr and the Nano just isn't up to that task. It could likely be made to work but I'm no expert with the code or ISR's. I also have the BITeensio board and I can tell you that with its Teensy 3.6 processor and a few simple mods to their encoder routines, I was able to read my 1024 ppr encoders (overkill for sure) as fast as I could spin it, without missing a beat. Point being, we really need a faster processor in the raduino, something like the Teensy 4 would be pretty interesting. The Teensy 4 could open the door for having some fun with digital audio filters, better spectrum display, etc.