BITX20@groups.io

[email protected]

All,

   So the reason I wanted to upload sketches is as follows:
I find the tuning of the uBITX troublesome.  Say I'm at the top of 40M and I want to get down to the CW segment:  I spin the knob, and down she goes.  But before I get to where I'm going, it shifts into this "hyper-tune" mode, and all the sudden I'm down at 6MHz.

I'd like it to act more like my old SB-34 transceiver.  This has a mechanical vernier mechanism.  The "fine" vernier area is about 15 kHz wide.  You tune fairly fast to get more or less where you're going, you pass it, and then when you reverse the knob, it starts tuning really slow.  As long as you're in the slow-tune area, it tunes fine & slow.

  When you get to the end of the 15kHz fine tune area, it starts tuning fast again.

By "fast", I mean a convenient speed for scanning across the segment, looking for signals.  By "slow", I mean a speed that's good for zero-beating an SSB signal, or zeroing in on a CW signal.

I have no use at all for the "hyper speed" tuning mode.  If I wanted to move a MHz or more, I'd just change bands or punch in the frequency.

                 - Jerry KF6VB

Mark - N7EKU

#88351

Hi Jerry,

Are you happy with how Reed's firmware works for tuning?? I don't know if the tuning is different on that version or how it works.

I have made changes to the tuning myself as I really didn't like the "hyper mode" speed change either (I was always overshooting where I wanted to go).? Just personal preferences I think.? If you want to try mine, it's an easy cut/paste operation, and I can post the changes here.? Just let me know.

73, ? Mark

#88358

Hi Jerry,

The only function that should really need adjusting is . If you revise it to the below, it will be fully linear:
int enc_read(void) {
? int ret_val = enc_count;
? enc_count = 0;
? return ret_val;
}
The 200ms thing you saw in the routine is only used for the momentum parameter. Alternatively, you can adjust the momentum scale factors (lines 116 and 119, currently 40 and 20's) to adjust the amount of momentum.

There's also a scale factor applied to the tuning in . Change the 50 to whatever frequency step size you'd prefer. I don't think there's sub-Hz tuning capability right now, since most frequency stuff uses integers, but that's not impossible either, with sufficient will power :P

As for getting the behavior you described for your SB-34, it's definitely possible to do that in software, but that's a bit more work than just removing the momentum stuff in there right now.

Reed

[email protected]

#88360

On 2021-05-14 19:35, Reed N wrote:
Hi Jerry,Hi Reed,

int enc_read(void) {
  int ret_val = enc_count;
  enc_count = 0;
  return ret_val;That's exactly what I did.  In addition, I toned down fastTune() by
a factor of 20 or so.  And I changed the minimum step size to ( I think )
25Hz.

               - Jerry


}
The 200ms thing you saw in the routine is only used for the momentum
parameter. Alternatively, you can adjust the momentum scale factors
(lines 116 and 119, currently 40 and 20's) to adjust the amount of
momentum.
There's also a scale factor applied to the tuning in menu_main.cpp at
line 104 [2]. Change the 50 to whatever frequency step size you'd
prefer. I don't think there's sub-Hz tuning capability right now,
since most frequency stuff uses integers, but that's not impossible
either, with sufficient will power :P
As for getting the behavior you described for your SB-34, it's
definitely possible to do that in software, but that's a bit more work
than just removing the momentum stuff in there right now.
Reed
Links:
------
[1] 
[2] 
[3] /g/BITX20/message/88358
[4] /mt/82833757/243852
[5] /g/BITX20/post
[6] /g/BITX20/editsub/243852
[7] /g/BITX20/leave/10189903/243852/952924773/xyzzy

开云体育

Tuning