Solid steps forward! I already had the non-defaulting values for the cals, but the submenuing idea makes a lot of sense. I'll get that added to my master soon :)
Reed
|
?Well, last week, I ordered a nice case to house one of my BITX40's. ?It arrived yesterday or today, really fast service from India. ? Well packed and as per shown on the website. Amateuradiokits.in.? Think that's the URL. ?I am very likely to order other items in the future. ?He has great cases for the uBITX series also.
?Wayne WA2YNE
|
What does the setup do as far as keyers are concerned? I made up two TRS jacks one ties in via 10 kohm input to keyer and 2nd the 2.2 kohm input line. These appear to be two iambic inputs but the cable that is set for the 2.2 kohm input also serves as direct PTT on the mic input jack. The set up options show two iambic choices and standard straight key. Does straight key setting work from both mic jack and/or key morse jack J4 ?
73 Andy
via my shoephone
Sent from
Thanks for the reminder Curt, thought I had checked that but apparently not, plugging in the straight key did the trick and I found the wiring diagram for the iambic key. uBitx is working good now in all modes, all that's left is to try it out on all the bands. 73 John W5GFI
|
Thanks for the reminder Curt, thought I had checked that but apparently not, plugging in the straight key did the trick and I found the wiring diagram for the iambic key. uBitx is working good now in all modes, all that's left is to try it out on all the bands. 73 John W5GFI
|
?The ones I purchased came with nuts and washers. ?If they don't look for another vendor. Always a good idea to have spares on hand.
?Wayne WA2YNE
And look they come with the nuts for mounting??
|
And look they come with the nuts for mounting??
|
Re: Need to Calibrate the V6
#v6
Hi Morris,
When it says "tune" it actually means tuning the BFO, not the tuner. You'll want to push the tuner knob in and then hold it in for a LONG time. This should pop up the setup menu, at which point you can select the BFO tuning menu. Once there, you'll want to turn the tuning knob until the tall green blob is centered between the red as best you can. The image you captured looks like it's off to the left, which means you have more low frequencies than you should.
Reed
|
Re: ubitx #v6 Screen Speed Mod
#v6
Hi Gary,
This isn't part of my pdq_gfx_update branch, but you can see the implementation I plan to use here:
The memset is required in my implementation only because I didn't think to manually set the terminator. If I did manually set a null terminator after inserting the "."s, the memset at the start could be skipped.
Reed
|
Re: ubitx #v6 Screen Speed Mod
#v6
You're wrong and it's still not safe. When globals are initialized at their global definition, they are only initialized once at load time. So, when you call the frequency format routine the first time (e.g., 7123456), all works as it should. Now call it the second time with the new frequency 21123456. Now b[] has:
"712345621123456"
but it still works because you over-allocated buffer space. Each time you call it, however, you extend the string. Eventually, on the 5th call, you will overflow the string space and all bets are off. This can be one of those test-it-three-times-and-it's-okay bugs that are difficult to find because the stack is usually blow away when the bug finally manifests itself.
If you're really worried about the few bytes used by memset(), why the hell are you using a 30-byte buffer space when 9 will work? Using the smaller buffer space would have produced the error for you and the second call. However, because it's a memory-overwrite, you still may not even know it's happened.
Jack, W8TEE
On Friday, January 17, 2020, 12:23:03 PM EST, Gary Anderson <gary.ag5tx@...> wrote:
Thanks Jack and Reed. When I created the global buffers in my test code:
char b[30] = {'\0'};
char c[30] = {'\0'};
The function is only called with initialized buffers from what I saw in a quick look at the V6 code.
Rgds,
Gary
-- Jack, W8TEE
|
Re: Need to Calibrate the V6
#v6
I am trying to use the BFO tuning aid. What exactly does the part of the website mean that says to tune until the noise is centered between the two red lines? I have noise all the way across with a dip partway across. I would assume that the dip is to be centered between the two lines but tuning does not move that 'notch'. Tuning changes the relative height of the noise on the right and the left. Does someone have a screen grab?
After I wrote the above I started up the radio again and went to the web page again and twiddled the knob some more and I just snapped an image. What does that image indicate?
Morris K7LSV
On Fri, Jan 10, 2020 at 2:27 PM < k7ome@...> wrote: Thanks Reed!? I did add that issue on Github as you suggested.? I'll get this figure out some day ....
|
Re: ubitx #v6 Screen Speed Mod
#v6
Thanks Jack and Reed. When I created the global buffers in my test code:
char b[30] = {'\0'};
char c[30] = {'\0'};
The function is only called with initialized buffers from what I saw in a quick look at the V6 code.
Rgds,
Gary
|
Re: ubitx #v6 Screen Speed Mod
#v6
I agree with Jack. Memset is an important part of that implementation.
b and c are global reusable char array buffers in the code.
Reed
|
Re: one_stop_setting debugging
#v6
Hi Reed,
Okay, I'm using it now and all seems to be good and stable, I will continue to use it today and report back later if I run into any problems.
Joel
N6ALT
|
The item is traceable on ebay.ca also. I saw just now.
|
Please see item number?291604842607? on ebay.com.
Around 18 months back i bought 10 lot? at 7.5$
|
Re: ubitx #v6 Screen Speed Mod
#v6
Well, you may not see any reason to have it, but I do. Local buffer space is allocated on the stack, which means it contains garbage when the buffer space is created. The strcat() functions work by locating the first NULL character in the string space and appending after that. Given that the buffer can contain almost anything when created, the first NULL could be 50 bytes away from buff[0], which means that you probably just clobbered whatever was "behind" buff on the stack, which could well be the stack pointer. If that happens, your program wanders into Never-Never Land and who knows what happens next. You can leave the memset() call out of the code, but chances are 1 in 256 it won't work properly.
Also, in the code below, where is variable b defined?
Jack, W8TEE
On Friday, January 17, 2020, 9:59:20 AM EST, Gary Anderson <gary.ag5tx@...> wrote:
I see no reason to do the memset in this function.? Removed it.? Less program space used and less processing cycles. Added a rounding option, that is commented out.? More program space and processing cycles :) Wrote a simple sketch that ran through a list of frequencies and then printed buff to STDOUT. I will get a GitHub account so I can play better in the future.
void formatFreq(long f, char *buff) {
? // tks Jack Purdum W8TEE
? // replaced fsprint commmands by str commands for code size reduction
? // AG5TX
? // resolved issue with format below 1 MHz, there is an issue below 100 Hz
?
? // rounding uses more bytes of program storage space and adds processing cycles
? // uncomment if you want this feature
?
? // round up for when only 2 digits after decimal point are used
? /*
? if(f%10 >= 5) {
? ? f += 5;
? }
? */
?
? ultoa(f, b, DEC);
? int g = strlen(b);
?
? for (int i = g; i < 8 ; i++){
? ? ?strcat(buff, " ");
? }
?
? strncat(buff, b, g-3);
? strcat(buff, ".");
? strncat(buff, &b[g-3], 2); // could set last arg to 3 for 3 digits after dec point, just don't round up.
}
-- Jack, W8TEE
|
Re: ubitx #v6 Screen Speed Mod
#v6
I see no reason to do the memset in this function.? Removed it.? Less program space used and less processing cycles. Added a rounding option, that is commented out.? More program space and processing cycles :) Wrote a simple sketch that ran through a list of frequencies and then printed buff to STDOUT. I will get a GitHub account so I can play better in the future.
void formatFreq(long f, char *buff) {
? // tks Jack Purdum W8TEE
? // replaced fsprint commmands by str commands for code size reduction
? // AG5TX
? // resolved issue with format below 1 MHz, there is an issue below 100 Hz
?
? // rounding uses more bytes of program storage space and adds processing cycles
? // uncomment if you want this feature
?
? // round up for when only 2 digits after decimal point are used
? /*
? if(f%10 >= 5) {
? ? f += 5;
? }
? */
?
? ultoa(f, b, DEC);
? int g = strlen(b);
?
? for (int i = g; i < 8 ; i++){
? ? ?strcat(buff, " ");
? }
?
? strncat(buff, b, g-3);
? strcat(buff, ".");
? strncat(buff, &b[g-3], 2); // could set last arg to 3 for 3 digits after dec point, just don't round up.
}
|
Re: one_stop_setting debugging
#v6
Hey Joel, I got enough parts that I could finally got back to this. I believe I found the source of the weirdness you saw. The issue was primarily three-fold:
- Per /g/BITX20/message/74892, the screen was rendering bad stuff when below 1MHz (1000kHz)
- In my code, if you set the radio to a frequency outside of the bands Ashhar had coded (3.5MHz-35MHz), it would load 0, not a safe default as I had intended. If you tuned into an AM station (1000kHz, for instance) and then turned the radio off, this would fall out of the hard coded range, triggering the bug.
- I wasn't loading the saved oscillator cal properly at boot, so you'd need to recal the oscillator every time (not ideal!)
When combined, these result in the display doing wonky frequency things while the VFO is WAY off from where you'd want it (0Hz isn't a popular ham band, and especially not so when uncalibrated :P). I think I have all of that stuff sorted now, so if you're willing to give the one_stop_settings branch another go to sanity check me before I merge it into my own master, I'd appreciate it. Of course, anybody else on this thread is also welcome to give it a go :) Reed
|
well a few things to check.? since SSB is working, you must have the 4.7k resistor installed, otherwise PTT would not work.?
of course check your wiring to the key jack.? a short circuit across the interface, when you find it on the board, should get you transmitting on CW.?
when this key interface is closed, the raduino should switch the rig into CW - you should see this on the display somehow.? note that in the settings (I am not familiar with CEC) there should be a setting that configures either manual key or paddle - see which yours is set for.?
also, paddle mode does require some additional resistors to provide different pull-up voltages for dit and dah - this info is on the web somewhere.
73 Curt
|
Re: uBitx microphone wire up
I can answer you, the mike has 2 connections, the ptt switch has 2 connections, for the mic one of the connections on the base goes to the metal body of the mic and should be connected to ground/earth/0 volts.
one side of the ptt switch goes to the ptt pin the other side goes to earth/ground etc so two wires go to one connection the earth/ground connection.
that¡¯s why you only need 3 wires total for mic and ptt.
I don¡¯t think I can add any more to that, that would explain it any better.
I think you are trying to overthink the problem, the wiring diagram shows only 3 wires from the main board, one of them earth/ground, that one MUST be the common element .
Howard G4GPF
|
Mick
Joel Caulkins/N6ALT