Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- BITX20
- Messages
Search
SolderSmoke Podcast #230 is available
N2CQR was down for maintenance? A few words about April 1 The Ingenuity helicopter China lands on Mars Brood X Cicadas arriving in NOVA? Pete's Bench The Dentron Project The Spillsbury Tindall SBX-11A KK4DAS and the Simple SSB Group Build TenTec mods Shack Mystery solved.? Maybe? Changing the channels at age 9? Bill's Bench Why LSB below 10 MHz? The "SSB Legend" Rig WU2D RTL-Dongle Up converter Understanding the Gilbert (Jones) Cell SDRSmart? RTL-SDR.com V3 Dongle? VK3HN and 2 meter SSB Jack NG2E, MMM and the 10 minute transmitter KD4EBM sends me SST by Wayne Burdick. DX!?? A new computer? Mailbag:? MM0ACN VK2EMU N5VZH VE3KZJ HS0ZLQ AD0JJ VK8MC KK0S VE3VVH KB3SII WA9WFA M0NTV W2DAB |
Re: CW Mistakes
The v6 voltage divider pulls at different strengths for dot and dit. If you try and send a symbol that is the stronger pull, there's a small window on the way up and down where the voltage will be at the value where the weaker pull usually rests.
I have two keys, and if I try and send only dits, if I send enough of them on either, I eventually get a dit-dah like you described. However, I've never had an accidental dit after sending only dots. |
Re: CW Mistakes
Hi Reed,
toggle quoted message
Show quoted text
The wrong *time*? I am confused. Is it a successive-approximation A-D? I just hauled the Bencher out to the garage and cleaned the contacts with De-Oxit and lacquer thinner. Now seems to be working fine. Time to take off the dummy load and make some contacts! - Jerry On 2021-05-15 10:49, Reed N wrote:
Yep. That's because the hardware implementation is a voltage divider, |
Re: CW Mistakes
It seems that - just occasionally - when you hit the "dit" paddle, the thing will go
toggle quoted message
Show quoted text
"dit dah", instead of just "dit". - Jerry KF6VB On 2021-05-15 08:25, jerry@... wrote:
Hello all, |
CW Mistakes
Hello all,
Practicing CW with the v6, a dummy load, and a Bencher paddle.... I seem to be making more mistakes than with other systems ( e.g. a Kenwood TS590S ) and the same paddle. There's something strange going on with the "feel" or timing or something. Can anybody supply a clue? - Jerry KF6VB |
Mark - N7EKU
I made a few changes to the firmware which some may like, so I am posting my changes here.? Also, there is a small bug in the sideband selection code that seems also to exist in the v5 and v6 stock firmware, so you may want to change that.
Change to ubitx_v4.3_code.ino: * McNabb (N7EKU) ?*?? Change to smaller speed steps (was 50, 500, 10000) ?*?? Change to bigger trigger, s, action (was 0, 2, 4) ?*?? Fix sideband selection (frequency should have >= condition) ?*/ void doTuning(){ ? int s; ? unsigned long prev_freq; ? s = enc_read(); ? if (s != 0){ ??? prev_freq = frequency; ??? if (s > 6) ????? frequency += 1250l; ??? else if (s > 2) ????? frequency += 100l; ??? else if (s > 0) ????? frequency +=? 10l; ??? else if (s < -6) ????? frequency -= 1250l; ??? else if (s < -2) ????? frequency -= 100l; ??? else ????? frequency -= 10l; ??? if (prev_freq < 10000000l && frequency >= 10000000l) ????? isUSB = true; ???? ? ??? if (prev_freq >= 10000000l && frequency < 10000000l) ????? isUSB = false; ??? setFrequency(frequency); ??? updateDisplay(); ? } } Change to ubitx_menu.ino: //# Menu: 1 /* ?* McNabb (N7EKU) Menu 1 Change ?*?? Change title from "Band Select" to "Speed Tune" ?*?? Change step change from 0.2MHz to 0.1MHz ?*?? Reduce knob sensitivity (knob < -2 and > 2 instead of < 0 or > 0) ?*/ int menuBand(int btn){ ? int knob = 0; ? int band; ? unsigned long offset; ?// band = frequency/1000000l; ?// offset = frequency % 1000000l; ?? ? ? if (!btn){ ?? printLine2("Speed Tune??? \x7E"); ?? return; ? } ? printLine2("Speed Tune:"); ? //wait for the button menu select button to be lifted) ? while (btnDown()) ??? active_delay(50); ? active_delay(50);?? ? ? ritDisable(); ? while(!btnDown()){ ??? knob = enc_read(); ??? if (knob != 0){ ????? /* ????? if (band > 3 && knob < 0) ??????? band--; ????? if (band < 30 && knob > 0) ??????? band++; ????? if (band > 10) ??????? isUSB = true; ????? else ??????? isUSB = false; ????? setFrequency(((unsigned long)band * 1000000l) + offset); */ ????? if (knob < -2 && frequency > 3000000l) ??????? setFrequency(frequency - 100000l); ????? if (knob > 2 && frequency < 30000000l) ??????? setFrequency(frequency + 100000l); ????? if (frequency >= 10000000l) ??????? isUSB = true; ????? else ??????? isUSB = false; ????? updateDisplay(); ??? } ??? checkCAT(); ??? active_delay(20); ? } ? while(btnDown()) ??? active_delay(50); ? active_delay(50); ? ? printLine2(""); ? updateDisplay(); ? menuOn = 0; } The changes I made were mainly to tame the automatic tune speed up so it doesn't react so fast, and to also allow more fine grained tuning (10Hz) and to make the knob a bit less sensitive to small movements.? I also changed the "Band Change" menu selection to "Speed Tune" since it really doesn't change to specific bands, and I slowed the tune rate there also. With these changes, I find the auto speed up is now easy to use and I can still make small frequency adjustments.? I like the auto speed change feature so that I don't have to change the speed steps all the time, but the stock firmware settings were too fast for me :-/ The sideband selection problem I noticed when moving quickly across 10MHz the sideband changed fine, but when moving slowly at a 10Hz rate it didn't change reliably from LSB to USB and back.? With the change I made, it works fine all the time now. I can post compiled firmware in the files section here if requested. Cheers, Mark PS:? According to John/VK2ETA, both RX and TX can be improved by increasing the SI5351 clock driver power from 4ma (as in v3 code) to 8ma (as in v5 code.? Make the change in ubitx_si5351.ino if desired. |
Sidebands on uBITXv6
All,
So with all the fun with playing with the firmware on my uBITXv6, I blew away the factory calibration, and had to redo it. I used the BFO alignment aid ( what a wonderful tool! ) and my radio is receiving fine...except: 1. I tune in an LSB signal on 40M. Loud and clear. 2. Punch the "USB" button on the screen. Mode now USB. 3. NO CHANGE to the received signal! What's going on? I would expect ...the received signal to go away ( if the display shows CARRIER frequency ) or ...The received signal to turn into Donald Duck quacking ( if the Display shows the frequency actually being received ) The plot thickens: The received signal DOES go away if you nudge the tuning knob. Nudge it back to where it was, and the received signal is still gone. Change to the correct sideband, nudge the tuning knob, and it comes back. ...So the sideband is only selected if there is a frequency change. - Jerry KF6VB |
Re: CNC encoder for ubitx
why does this group have people smarter than?me? On Sat, May 15, 2021 at 1:56 PM Raj vu2zap <rajendrakumargg@...> wrote:
|
Re: CNC encoder for ubitx
You would get 2.4 Farhan!
toggle quoted message
Show quoted text
One turn of tune shaft should turn encoder 10 times to get 240. At 15/05/2021, you wrote: Why not pulley-and+thread the existing encoder to a smaller shaft? If the drum Diameter on the encoder is 10 times the diameter of your tuning shaft, you will be 240 pulses instead of 24. |
Re: Question about voltage regulator
Hello,
What I saw is actually a tough one, but doesn¡¯t interfere with the operation. Besides I did the test to remove it and put 2 separate power supplies of 5V and 12V, my parasitic noise does not leave. If you want for low noise regulator mountings, I found regulators based on LT3045. There are many models. Example: cdt |
Re: CNC encoder for ubitx
Why not pulley-and+thread the existing encoder to a smaller shaft? If the drum Diameter on the encoder is 10 times the diameter of your tuning shaft, you will be 240 pulses instead of 24. On Sat 15 May, 2021, 8:22 AM Arv Evans, <arvid.evans@...> wrote:
|
Re: micro bitx kit from 2018
#ubitx
Trystan
I am thinking there is a large population of v3 and v4, I wonder if they might outnumber the later versions. Our local club did a group build, more than 2 dozen. Actually my v4 was originally decently clean on about half of the bands each in cw and ssb. Improving it was much of the adventure, but honestly much more global interest in customizing them. I appreciate for some places on the globe hams use it as a primary rig. I have better rigs that sometimes sit for weeks at a time while I make contacts and or improve the ubitx.? Occasionally I call someone dx even on ssb with the ubitx, and if I give my call twice they can be quite annoyed when we double, when they copy me the first time. A rig whose circuit boards cost maybe 3 or 4 loads of fuel for our automobile is quite a treasure. But surprising how much time many of us have invested in hardware and code, and have vastly spread the knowledge.? 73 Curt |
Re: CNC encoder for ubitx
Optical encoders that drive a small computer like an Arduino should be easy to handle in software.? It the number of states per revolution is too high, just use a software divider to lower the number of states. If the number of mechanical states is too low, it should be easy to make a state multiplier for 2X, 3X, etc.? Arv _._ On Fri, May 14, 2021 at 7:33 PM Jack, W8TEE via <jjpurdum=[email protected]> wrote:
|
Re: CNC encoder for ubitx
Jack Me too.? It sounds like fun! Arv _._ On Fri, May 14, 2021 at 7:41 PM Jack, W8TEE via <jjpurdum=[email protected]> wrote:
|
Re: Tuning
On 2021-05-14 19:35, Reed N wrote:
Hi Jerry,Hi Reed, int enc_read(void) {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 } |
Re: Sidetone
All,
toggle quoted message
Show quoted text
Well, I have a solution to the loud sidetone. Sort of. In cwKeydown() I replaced the call to tone() with a call to analogWrite(). By specifying a really low value ( 1 ) , I was able to get a CW sidetone I could live with - on the highest bands. On 80M, I could hardly hear it at all. That's because on the lower bands, the natural gain of the radio is higher, and so you turn the volume down. I could put in logic to change the volume depending on the frequency. It would only need two or three volumes - one for anything below 20M, the other 20M & up. Changing the tone is a bit more complex. There is a setup register in the CPU that you write to set the PWM frequency. But it's completely doable, without a whole lot of code. There are 1962 bytes left on the chip. - Jerry KF6VB On 2021-05-14 19:10, jerry@... wrote:
All, |
Re: Tuning
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 |
to navigate to use esc to dismiss