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
Re: bitx v3 rx linearity?
Gordon Gibby
toggle quoted message
Show quoted text
|
Re: bitx v3 rx linearity?
Probably due to biasing of Q70. Try change R50 to 180K and/or R51 to
2.2K, that should change the
toggle quoted message
Show quoted text
Q70 collector voltage and give you more amplitude before clipping. Raj At 17/02/2019, you wrote: Hi! |
Re: BITX 40
#bitx40
#bitx40help
Yes, good. I overlooked a failing solder joint onto my bnc connector and it was terrible trying to trace that down.
Can you check the reference clock crystal on the raduino, Y1 at 25MHz? What test equipment do you have? |
Re: bitx v3 rx linearity?
Hi! Sorry, was the ubitx 4. oops! Anyway - I checked at the two mixer stages. TP17/TP20 are fine. TP21 is where the distorted sine wave shows up. -adrian On Sat, 16 Feb 2019 at 15:37, Evan Hand <elhandjr@...> wrote: The only difference between a v3 and v4 is the audio section.? Where exactly are you measuring the distortion? |
bitx v3 rx linearity?
hi!
I'm poking at my ubitx 3.0. It hasn't behaved well at all on either transmit or receive. It turns out it was very not calibrated and balanced for transmit, so I've fixed that. However, receive is .. not very nice. Ignoring the audio amplifier section (I've tried it with an LM386 amplifier), I've noticed that the receive side is misbehaving a bit. If I inject a sine wave? from an RF generator everything seems OK until the final mixing section. At which point the sine wave really isn't a sine wave any more; the bottom half of the sine wave is truncated. This gets fed to the audio section and .. well, it doesn't sound great. Is this something others have seen on their v3 receive paths? -adrian (kk6vqk) |
Re: suggestions for a graphics display
Among the various experiments, and understanding the requirements set by Farhan I can suggest these two options: 1) 0.96 - 1.3 inch IIC Serial OLED Display 128X64 I2C SSD1306 2) Nokia 5110 84x84 pixel display. 3) ILI9341 display driven by additional arduino nano. The first two have wholesale prices of a couple of dollars, and are simple to use and program. Obviously if you need something better (colors etc ...) you need other displays but the problem is the inability to exploit it fully with the arduino 328p. Possibly you could build an "intelligent display" using a 2.2-inch SPI display and 65000 colors ILI9341 driven by an arduino that exposes via liea I2C serial commands "similar to the nexion" towards the main arduino on which the Raduino code runs. This way I think the costs could go: $ 4 on the display and about $ 2 for a dwarf arduino. Best 73 de Giuseppe, IK8YFW |
Re: suggestions for a graphics display
Jack, and others... After a bit of research, it seems that there are older and newer devices listed as 128 X 64 displays.? The older ones look like a traditional 1602 style LCD while the newer ones are smaller, more square, and are OLED technology.? The OLED ones seem to use I2C bus while the older units connect about the same as a 2-line 1602 character display.? Admittedly the small displays have limited area for viewing and may be more difficult for us old timers to see, but being pixel-based instead of character based they do have quite a bit of flexibility in what and how information is shown.? Arv _._ On Sat, Feb 16, 2019 at 9:09 AM Jack Purdum via Groups.Io <jjpurdum=[email protected]> wrote:
|
Re: uBitx VFO VFO frequency deviation 700 Hz at 80 meters; 1400 Hz at 40 meters ...
#calibration
#radiuno
#ubitx
toggle quoted message
Show quoted text
On Feb 16, 2019, at 11:03 AM, Ted via Groups.Io <k3rta@...> wrote:
|
Re: Finished and back on the air!
#bitx40
Sunday 3pm & 7pm Your Local Time
Starting at 3pm & 7pm EST? 7.177 and 7.277 up or down as conditions requires? QRO only as conditions require. -- David ?N8DAH |
Re: Finished and back on the air!
#bitx40
toggle quoted message
Show quoted text
|
Re: suggestions for a graphics display
Jack Purdum
Farhan, Arv: It would be interesting to know how many people use the ?BITX in an environment where "off-the-grid" power is used. I have no idea. Clearly, I'm aiming at regular power sources. The 128x64 OLED LCD display range from 0.96" to 1.3" and are under $10. I don't know their power requirements, but I would guess they are fairly small. That said, their pico acres don't give you much room to display information after the operating frequency is displayed. I've not used any of the e-ink displays, so I can't comment on them. I do know that the ?BITX and JackAl together draw about 0.8A on receive and about 2A on transmit with a 12V supply...not exactly sipping at the power trough, but then its feature set isn't aimed at lower power consumption. Arv: you're absolutely right on the CAT interface. Its command-style structure could stand some improvement. It's also one of those topics that has the potential of running off the rails unless there is some discipline. There was a time prior to X3J11 where C seemed headed down that same path. I'm not a big fan of committees (I had a sign in my office for years that read: God so loved the world He didn't send a committee), but perhaps a sub-group could discuss this. Jack, W8TEE
On Saturday, February 16, 2019, 10:48:56 AM EST, Arv Evans <arvid.evans@...> wrote:
Farhan You have echoed my feelings about CAT interface, except that i would think it needs to evolve instead of being thrown away.? CAT as a link interface may be adequate.? It is how we use the data that is woefully outdated.? Maybe this warrants a specific thread, or possibly a new discussion group that is focused on bringing CAT into the modern world? The 128 x 64 LCD displays are easy to control.? If the supply is stable they could be a good near-term solution. Arv _-_ Sent from my Verizon, Samsung Galaxy smartphone -------- Original message -------- From: Ashhar Farhan <farhanbox@...> Date: 2/15/19 7:29 PM (GMT-07:00) Subject: Re: [BITX20] suggestions for a graphics display Jack, The tft displays are a plenty, however, their supply is erratic and the quality ranges from superb to unknown. There is the matter of noise emission and current consumption too. After aruging for every milliamp on the RF side, it would be a travesty to give up all of it on the display. Doug and others, I am continuing to investigate the e-ink. I have two displays, both from waveshare with me. One is a 2.9 inch display and the other is a 1.54 inch display. Lets see, it appears to be that if the display coulf offer 3 updates of tuning frequency per second, we'd be home. Arv, Thanks for the sugesstion for CAT. A CAT lile protocol that does more is needed. Given the plethora of modes that we run these days, CAT should have retired 20 years ago. It can't even send morse code or turn the beam, leave alone 'decode psk31 at 1200 hz'.? Given my personal inclination, i am still tempted for the geneic 128x64 monochrome LCD display where i can switch the backlight off and on. The display is available to builders in Bangladesh as well as Sacramento. Unfortunately, it is not pimped enough. It is bland. Somewhat like the K3 display. Let me play with the tft displays today and measure the current and noise. - f On Sat 16 Feb, 2019, 7:44 AM Arv Evans <arvid.evans@... wrote:
|
Re: uBitx VFO VFO frequency deviation 700 Hz at 80 meters; 1400 Hz at 40 meters ...
#calibration
#radiuno
#ubitx
^? This is this is why, when possible, I like to have the second receiver on AM and listening to WWV on both radios. That way, I'm actually comparing their approximately 800 cycle (?) tone with my received audio on the uBitx. That way, and with the uB near carrier zero-beat, there's still a working audio note well within human hearing so I can listen for the difference between the two in terms of only a couple cycles per second. If you can pick that out, meaning if you have a musical ear, it's just one other option to try.
Ted |
Re: Finished and back on the air!
#bitx40
?Looks very good. ?Hope you catch that Sunday net. ?I'd want to try catching the Noontime Net, out of New Mexico, which I caught before. ? ?I hope to get mine done enough for a few pictures this month, or at least early next month ?Wayne WA2YNE ?Imperial Texas |
Re: suggestions for a graphics display
开云体育Farhan You have echoed my feelings about CAT interface, except that i would think it needs to evolve instead of being thrown away.? CAT as a link interface may be adequate.? It is how we use the data that is woefully outdated.? Maybe this warrants a specific thread, or possibly a new discussion group that is focused on bringing CAT into the modern world? The 128 x 64 LCD displays are easy to control.? If the supply is stable they could be a good near-term solution. Arv _-_ Sent from my Verizon, Samsung Galaxy smartphone -------- Original message -------- From: Ashhar Farhan <farhanbox@...> Date: 2/15/19 7:29 PM (GMT-07:00) Subject: Re: [BITX20] suggestions for a graphics display Jack, The tft displays are a plenty, however, their supply is erratic and the quality ranges from superb to unknown. There is the matter of noise emission and current consumption too. After aruging for every milliamp on the RF side, it would be a travesty to give up all of it on the display. Doug and others, I am continuing to investigate the e-ink. I have two displays, both from waveshare with me. One is a 2.9 inch display and the other is a 1.54 inch display. Lets see, it appears to be that if the display coulf offer 3 updates of tuning frequency per second, we'd be home. Arv, Thanks for the sugesstion for CAT. A CAT lile protocol that does more is needed. Given the plethora of modes that we run these days, CAT should have retired 20 years ago. It can't even send morse code or turn the beam, leave alone 'decode psk31 at 1200 hz'.? Given my personal inclination, i am still tempted for the geneic 128x64 monochrome LCD display where i can switch the backlight off and on. The display is available to builders in Bangladesh as well as Sacramento. Unfortunately, it is not pimped enough. It is bland. Somewhat like the K3 display. Let me play with the tft displays today and measure the current and noise. - f On Sat 16 Feb, 2019, 7:44 AM Arv Evans <arvid.evans@... wrote:
|
Re: Sweeperino?
开云体育Working, tnx .
Now I try to make PCB Board.
?
73 Matjaz S56ZVD
? Sent: Friday, February 15, 2019 5:45 PM
Subject: Re: [BITX20] Sweeperino? ?
Karl's answer will fix your issues. You must have both INO files in the
same directory. If you do not see the primary file names on tabs in the IDE, you
do not have them in the same directory.
?
Jack, W8TEE
? On Friday, February 15, 2019, 11:31:44 AM EST, matjaz via Groups.Io
<matjaz_zejn@...> wrote:
?
?
Hey, tnx for ansver and instruction how to. Karl Heinz tnx , I try with Si5351a.ino in the same place. Still recevied mistake. This is original file from Made by Afarhan. Include file with errors. By and 73 Matjaz? S56ZVD On Fri, 15 Feb 2019 14:53:18 +0000 (UTC), "Jack Purdum via Groups.Io" <jjpurdum=[email protected]> wrote: > Matjaz: > The Arduino GNU compiler performs type checking on function arguments, > which means it needs to have what is called a function prototype. For > example, suppose you write a function named MySquare() that takes an > integer variable as its argument: > int MySquare(int number){ return number * number;} > > The compiler needs to know things about this function before it can > properly compile the program. To fix this, add this line at the very top > of your program: > long MySquare(int number); // This is a function prototype for MySquare() > When the compiler reads the function prototype, it takes the attributes > of the function (e.g., it returns a_ long_, it takes an _int _as an > argument, and its ID is _MyFunction_) and stores that information in > something called a symbol table. Later in the program when you use this > function, the compiler can look in the symbol table to check that you're > passing the correct data type to it (_int_) and assigning what is > returned from the function into a matching (_long_) data type The error > in yellow below is an example of the compiler not finding a function > prototype. > The first error means that the definition of _xtal_freq_calibrated _was > not found in the compiler's symbol table by the time it reached that > point in the program. If this is someone else's code that you copied, > this could be as simple as misspelling the variable name. Whatever the > reason, it's caused by that variable not being in the symbol table. To > more fully understand these types of errors, try reading: > What is Scope? [1] > > WHAT IS SCOPE? > > What is Scope? > > and see if that helps. > Jack, W8TEE > (aka econjack) > >??? On Friday, February 15, 2019, 9:25:09 AM EST, matjaz via Groups.Io > wrote:? > >? Hello, > I try to compile antuino, but recevied many errors. > > Best regards > > Matjaz > > C:antuinoantuino-masterantuino_analyzer_27mhz_v2antuino_analyzer_27mhz_v2.ino: > In function 'int calibrateClock()': > > antuino_analyzer_27mhz_v2:62: error: 'xtal_freq_calibrated' was not > declared in this scope > >? prev_calibration = xtal_freq_calibrated; > >? ^ > > antuino_analyzer_27mhz_v2:65: error: 'si5351aSetFrequency_clk1' was not > declared in this scope > >? si5351aSetFrequency_clk1(10000000l); > >? ^ > > C:antuinoantuino-masterantuino_analyzer_27mhz_v2antuino_analyzer_27mhz_v2.ino: > In function 'void takeReading(long int)': > > antuino_analyzer_27mhz_v2:300: error: 'si5351aSetFrequency_clk2' was not > declared in this scope > >? si5351aSetFrequency_clk2(local_osc); > >? ^ > > antuino_analyzer_27mhz_v2:304: error: 'si5351aSetFrequency_clk0' was not > declared in this scope > >? si5351aSetFrequency_clk0(newfreq); > >? ^ > > antuino_analyzer_27mhz_v2:311: error: 'si5351aSetFrequency_clk1' was not > declared in this scope > >? si5351aSetFrequency_clk1(newfreq); > >? ^ > > C:antuinoantuino-masterantuino_analyzer_27mhz_v2antuino_analyzer_27mhz_v2.ino: > In function 'void setup()': > > antuino_analyzer_27mhz_v2:326: error: 'xtal_freq_calibrated' was not > declared in this scope > >? EEPROM.get(MASTER_CAL, xtal_freq_calibrated); > >? ^ > > antuino_analyzer_27mhz_v2:352: error: 'si5351aOutputOff' was not declared > in this scope > >? si5351aOutputOff(SI_CLK0_CONTROL); > >? ^ > > C:antuinoantuino-masterantuino_analyzer_27mhz_v2antuino_analyzer_27mhz_v2.ino: > In function 'int menuSelectAntAnalyzer(int)': > > antuino_analyzer_27mhz_v2:535: error: 'si5351aOutputOff' was not declared > in this scope > >? si5351aOutputOff(SI_CLK0_CONTROL); > >? ^ > > C:antuinoantuino-masterantuino_analyzer_27mhz_v2antuino_analyzer_27mhz_v2.ino: > In function 'int menuCalibrate2(int)': > > antuino_analyzer_27mhz_v2:594: error: 'si5351aOutputOff' was not declared > in this scope > >? si5351aOutputOff(SI_CLK0_CONTROL); > >? ^ > > C:antuinoantuino-masterantuino_analyzer_27mhz_v2antuino_analyzer_27mhz_v2.ino: > In function 'int menuSelectMeasurementRx(int)': > > antuino_analyzer_27mhz_v2:614: error: 'si5351aOutputOff' was not declared > in this scope > >? si5351aOutputOff(SI_CLK0_CONTROL); > >? ^ > > C:antuinoantuino-masterantuino_analyzer_27mhz_v2antuino_analyzer_27mhz_v2.ino: > In function 'int menuSelectNetworkAnalyzer(int)': > > antuino_analyzer_27mhz_v2:633: error: 'si5351aOutputOff' was not declared > in this scope > >? si5351aOutputOff(SI_CLK1_CONTROL); > >? ^ > > exit status 1 > 'xtal_freq_calibrated' was not declared in this scope > > On Fri, 15 Feb 2019 18:05:46 +0530, "Ashhar Farhan" > wrote: >> Of all, this should be your first project. It will all the others.- f >> On Fri 15 Feb, 2019, 5:56 PM gerrykav via Groups.Io >> >> Links: >> ------ >> [1] mailto:[email protected] [3] >> [2] /g/BITX20/message/65375 [4] >> [3] >> > mailto:[email protected] > [5]?subject=Re:%20Re%3A%20%5BBITX20%5D%20Sweeperino%3F >> [4] >> > mailto:farhanbox@... > [6]?subject=Private:%20Re:%20Re%3A%20%5BBITX20%5D%20Sweeperino%3F >> [5] /mt/29791995/180494 [7] >> [6] /g/BITX20/post [8] >> [7] [9] >> [8] [10] >> [9] [11] >> [10] [12] >> [11] [13] >> [12] /g/BITX20/wiki/home [14] >> [13] /g/BITX20/editsub/180494 [15] >> [14] mailto:BITX20+[email protected] [16] >> [15] /g/BITX20/leave/defanged [17] > >??? > > Links: > ------ > [1] > [2] mailto:farhanbox@... > [3] mailto:[email protected] > [4] /g/BITX20/message/65375 > [5] mailto:[email protected] > [6] mailto:farhanbox@... > [7] /mt/29791995/180494 > [8] /g/BITX20/post > [9] > [10] > [11] > [12] > [13] > [14] /g/BITX20/wiki/home > [15] /g/BITX20/editsub/180494 > [16] mailto:[email protected] > [17] /g/BITX20/leave/defanged > [18] /g/BITX20/message/65380 > [19] > mailto:[email protected]?subject=Re:%20Re%3A%20%5BBITX20%5D%20Sweeperino%3F > [20] > mailto:jjpurdum@...?subject=Private:%20Re:%20Re%3A%20%5BBITX20%5D%20Sweeperino%3F > [21] /mt/29791995/180494 > [22] /g/BITX20/post > [23] > [24] > [25] > [26] > [27] > [28] /g/BITX20/wiki/home > [29] /g/BITX20/editsub/180494 > [30] mailto:BITX20+[email protected] > [31] /g/BITX20/leave/defanged |
to navigate to use esc to dismiss