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
|
Sidebands reversed after Memory Manager Used
Thanks to all who offered advice on how to get my uBITX to display transmit frequency on CW.? ?I went to Memory Manger and changed the settings.? Unfortunately this seems to have seriously messed up my software.?? I cleared the EEPROM, and loaded CEC version 1.20.? It looked good, but the sidebands were reversed -- I had to put 40 meters in USB to copy the sideband signals (which are on LSB).? I even tried to go back to 1.071.? But I have the same problem with the sidebands.? It is as if the BFO is being placed in the wrong spots.? Any suggestions on how to fix this?? It is not a hardware problem -- I had it working fine until I tried to make changes with Memory Manager.?? Thanks 73? Bill N2CQR |
|
Re: bitx v6 is here
Jack, W8TEE
Jerry: I agree that the type specifier should be a capital 'L': ????? ? #define INIT_USB_FREQ? ?(11059200L) and I use them, not for the compiler's benefit, as you're right that the compiler can figure that out. I do it as a form of documentation. Therefore, if I use the constant in a complex expression of mixed data types, the compiler uses the correct data type (e.g., a long, not a long long or an unsigned long) after the parse. (There are tools that let you see the source after the preprocessor pass and it can be helpful there.) Another change I would make on Farhan's new code is to change all of the *.INO files except ubitx_v6.3_code,ino (because it contains setup() and loop() in it) to *.cpp files. If you use a bunch of *.ino files, the compiler must gather all of the files into one "super" ino file before it can compile the code. If you have only one *.ino file, the compiler can perform incremental compiles. The time savings can be substantial. The JackAl code was 11,000+ lines of source code spread over 19 files. The first compile in the morning would take about a minute on a pretty fast machine. Then, since I tend to end up working on just one file most of the day, the compiler can see that the dirty flag is only set on the file I'm editing. Therefore, it only compiles that one file and let's the linker splice the other (previously-compiled) files into the executable. This can cut the compile time by 90%. For me, this could save a half hour each day of unnecessary thumb-twiddling. Making the change involves some work, since it usually means a header file with extern data declarations in it and the actual data defintions in INO file. I did this for Farhan on the V5 code, but he never released it. It probably would have just confused people. Still, if you plan on messing around with the code to any extent, using *.cpp files will end up saving you a lot of time in the long run. Jack, W8TEE
On Saturday, December 14, 2019, 2:34:59 PM EST, Jerry Gaffke via Groups.Io <jgaffke@...> wrote:
Farhan wrote >? If your board has 12 mhz, you have to just edit that one line to change the second IF. That would probably be this line in ubitx_v6.3_code.ino: ? ? #define INIT_USB_FREQ? ?(11059200l) Older code has this line instead: ? ? #define INIT_USB_FREQ? ?(11996500l) Note that the final character is a lower case L (for long integer), not a one. This has caused confusion in the past, would be better to change that letter to upper case, here and many instances elsewhere in the code. Better in my opinion is to remove the L entirely, the compiler is perfectly capable of figuring out how many bits are needed.? I'm seeing two routines in ubitx_v6.3_code.ino, One is named setTXFilters(), this one gets used down in setFrequency() The other is named setTXFilters_v5(), has identical code in the function body, does not get used. I believe v5 and v6 have an identical configuration for the filter relays. However v3 and v4 uBitx hardware will want to replace setTXFilters() with the older version of that routine. Code for the ILI9341 display is in v6, the old v3,v4,v5 code using the LiquidCrystal library for the old 2x16 display has been removed. Would be nice if this was if-def'd so code could be compiled for either. So "you have to just edit that one line" applies to changing the IF frequency,? but you have a fair bit more work to do if planning to use v6 code on v3,v4,v5. Jerry, KE7ER On Fri, Dec 13, 2019 at 06:58 PM, Ashhar Farhan wrote: We have left the old traces, connectors etc in exactly the same place. The software is backwards compatible with the previous versions. If your board has 12 mhz, you have to just edit that one line to change the second IF. -- Jack, W8TEE |
|
Re: bitx v6 is here
Farhan wrote
toggle quoted message
Show quoted text
>? If your board has 12 mhz, you have to just edit that one line to change the second IF. That would probably be this line in ubitx_v6.3_code.ino: ? ? #define INIT_USB_FREQ? ?(11059200l) Older code has this line instead: ? ? #define INIT_USB_FREQ? ?(11996500l) Note that the final character is a lower case L (for long integer), not a one. This has caused confusion in the past, would be better to change that letter to upper case, here and many instances elsewhere in the code. Better in my opinion is to remove the L entirely, the compiler is perfectly capable of figuring out how many bits are needed.? I'm seeing two routines in ubitx_v6.3_code.ino, One is named setTXFilters(), this one gets used down in setFrequency() The other is named setTXFilters_v5(), has identical code in the function body, does not get used. I believe v5 and v6 have an identical configuration for the filter relays. However v3 and v4 uBitx hardware will want to replace setTXFilters() with the older version of that routine. Code for the ILI9341 display is in v6, the old v3,v4,v5 code using the LiquidCrystal library for the old 2x16 display has been removed. Would be nice if this was if-def'd so code could be compiled for either. So "you have to just edit that one line" applies to changing the IF frequency,? but you have a fair bit more work to do if planning to use v6 code on v3,v4,v5. Jerry, KE7ER On Fri, Dec 13, 2019 at 06:58 PM, Ashhar Farhan wrote: We have left the old traces, connectors etc in exactly the same place. The software is backwards compatible with the previous versions. If your board has 12 mhz, you have to just edit that one line to change the second IF. |
|
Re: bitx v6 is here
Jack, W8TEE
SOTABeams has a nice (and small) DSP filter. There's also a really nice DSP package described in Microcontroller Projects for Amateur Radio that lets you define the filter parameters: Oh, never mind...that book's not out yet!?? :>) Jack, W8TEE
On Saturday, December 14, 2019, 12:02:58 PM EST, John AE5X <ae5x@...> wrote:
On Fri, Dec 13, 2019 at 03:41 PM, Dave Dixon wrote: just ordered my V6 looking forward to receiving it next year..Im hunting around for a variable cw filter..any ideas guys.,Dave G0AYDI'll probably be ordering one of these: Here's another option if you want to spend more: John AE5X -- Jack, W8TEE |
|
Let's Minimize the Library problems.
Jack, W8TEE
This is a common problem for many homebrew projects. Frankly, I don't know which library to use either, so let's agree to try and make things simpler: I always use this format for any non-standard library, where non-standard means the library is not distributed as part of the Arduino IDE: ??? #include <XPT2046_Touchscreen.h>??????? // The comment on the line gives the URL where the reader can go and download the library. This simple change would help people find the correct library to use. (I don't know which one is correct, I'm just using Paul's as an example of how to document it in the code.) Jack, W8TEE
On Saturday, December 14, 2019, 1:03:47 PM EST, GM4CID <gm4cid@...> wrote:
Hi, there seem to be several XPT2046_Touchscreen libraries on Github, wondering which one is correct to use ? 73, Bob GM4CID -- Jack, W8TEE |
|
Re: Audio isolation w/ digital modes
#ubitx
The computer? audio controls can easily adjust for moderate mismatches.? Use the $7 sound card direct to the uBITX speaker and mic jack. Your computer's sound control, plus controls in wsjtx/Fldigi, will make all the adjustments.??
I've used 1:1 isolation transformers with DC blocking caps.? And also? i've gone straight to the? sound card.?? Both work. Simplicity suggests go direct to the USB sound card. Adjust levels in the PC/app. No complicated audio i/o interface? is required. Don |
|
Re: Frequency calibration V5
Apparently, V6 firmware can be used on earlier rigs, making a minor adjustment if you have a 12mhz IF.
Searching for "set_calibration" in ubitx_setup.ino for V6, it appears that this new code is using the algorithm of? ?/g/BITX20/message/71281 Which is most welcome. The V6 code adjusts the si5351bx_vco in steps of 875 hz. All three si5351 outputs (and consequently the rig operating frequency) are locked into ratios of that 875mhz VCO. So if operating at 10mhz, the operating frequency is 875mhz/87.5=10mhz, and the calibration granularity is 875hz/87.5 = 10hz. And if operating at 30mhz, then the calibration granularity is 30hz, given the 875hz step size of the code in ubitx_setup.ino. A step size of 875 should be fine for most, but there is nothing special about it. You could change the value of 875 in ubitx_setup.ino to anything you want, and recompile. Larger step sizes will make calibration proceed faster, smaller step sizes will allow you to set the frequency more accurately. Though to be very accurate, you will need to monitor the audio with a scope, and hope any DC blocking caps in the audio chain will pass low enough frequencies.? ? (I haven't looked too hard at the code yet, I assume he is moving the BFO into the center of the IF filter passband so you can hear a proper zero beat at very low audio frequencies.) Calibrate using a signal source at the highest frequency for which it is convenient. Calibrating to WWV at 10mhz will be 10 times more accurate than calibrating to an AM broadcast station at 1mhz. Most AM shortwave broadcasting stations have a carrier within a hz or two of a 5khz increment. If unsure how accurate that station is then verify by checking calibration against a different station. This procedure was outlined in post 35235 over 2 years ago, when the uBitx was first announced. Rather distressing to see all the posts in the forum from folks spending days trying to figure out how to calibrate. Jerry, KE7ER |
|
Re: bitx v6 is here
Laurence Oberman
@David W9PH
toggle quoted message
Show quoted text
If you want to add simple morse decoder without building it 73 KB1HKO On Sat, Dec 14, 2019 at 1:21 PM Ashhar Farhan <farhanbox@...> wrote:
|
|
Re: Which version of the XPT2046_Touchscreen library is used by the V6 ?
Lemme check. It will take me 24 hours as I am out of town right now On Sat 14 Dec, 2019, 11:33 PM GM4CID, <gm4cid@...> wrote: Hi, there seem to be several XPT2046_Touchscreen libraries on Github, wondering which one is correct to use ? |
|
Re: bitx v6 is here
Aah, i havent tried that out. I did try the kx3 cw reader though. Just getting it to read was voodoo. The user interface was erratic, the way settings worked was opaque and the tuning indicator was inaccurate. Maybe I didn't get a proper hang of the thing.? - f On Sat 14 Dec, 2019, 11:14 PM Eric Thielking, <ewthielking@...> wrote:
|
|
Re: Audio isolation w/ digital modes
#ubitx
John Faivre
I put 2 1:1 audio transformers into my V4 and put 2 mono jacks on the back that I run to a $7 usb sound card on my pc. I ran the nano¡¯s usb to a connector on the back for CAT.? I put ferries on the usb and audio lines to the PC. |
|
Re: bitx v6 is here
Respectfully, the on-board decoder on the K3 works well.? On Sat, Dec 14, 2019 at 12:38 PM Ashhar Farhan <farhanbox@...> wrote:
|
|
Re: Audio isolation w/ digital modes
#ubitx
Hello,
After building few Ubitx , my experiment regarding digital mode is to tap the audio prior the LM386 on the R70 resistor.? this option is providing a fix audio level and you dont need to use the volume potentiometer to adjust the level but the volume control from your computer. Ater some quick testing it is quit easyvto find out the suitable decoding level. i add a switch in order to separate the Mic from the digital audio input . in addition i add a 1:1 transformer and a 4,7nf capacitor in serial in order to isolate and adapt the input level for decoding. 73's Didier |
|
Re: bitx v6 is here
By morse reader, I actually meant software that reads out the screen in morse code. I had fooled around with many morse decoders. Nothing really works on the bands. CW skimmer is the only thing that works under contest conditions. So, if you want a morse code decoder that really works well, can adapt to any radio and needs no special hardware, then, spend a month, 20 minutes a day and practice at 30 wpm.? - f On Sat 14 Dec, 2019, 9:56 PM splat1956, <dnrabin7@...> wrote: Hi |
|
Re: bitx v6 is here
On Fri, Dec 13, 2019 at 03:41 PM, Dave Dixon wrote:
just ordered my V6 looking forward to receiving it next year..Im hunting around for a variable cw filter..any ideas guys.,Dave G0AYDI'll probably be ordering one of these: Here's another option if you want to spend more: John AE5X |
|
Re: bitx v6 is here
Hi
This is very exciting. I have been thinking a long time but have not purchased one because I was afraid that the soldering and wiring instructions would be confusing. There have been many posts by confused builders. This sounds great. Is there a morse code decoder built in or coming soon ? Your earlier post said " I have added a morse reader already. I shall finish integration to the user interface soon." Please let us know when that is incorporated. I am unlikely to upgrade the software-firmware once it is working and that would be a very nice feature. Great idea on the calibration with a known station signal for people without test equipment. Thank you very much for this great upgrade ! David W9PH |
|
NIB-uBITx Version 3, Un-Built
I have for sale an AS NEW In Plastic Shipping container uBitx Version 3. It was produced Prior to May, 2018 as it has the TDA2822 Audio Chip soldered to the PCB.
It is Un Built and AS New. Received 01/10/2018. Asking Price : $90.00 and $5.00 for shipping. Total: $95.00 Shipped to US Addresses. If international buyer, then actual shipping cost will be applied. Accept: PAYPAL. Money Order, or Check.? Please allow time for MO/Check to clear bank before shipping. Please send any questions to kevinemtid at sbc global dot net . Thank you Farhan for making a Great Rig! I am still working on my Bitx 40.??Yes I am a bit Behind in my projects!?But I Plan on acquiring a newer version uBitx in the future..? 73, Kevin NZ1I |
|
Re: Frequency calibration V5
I have not used it, so cannot attest to the accuracy.
To help speed up the process you might want to read this thread and try the calibration spreadsheet. /g/BITX20/message/72183?p=,,,20,0,0,0::Created,,calibration+spreadsheet,20,2,0,34330593 A take away from this that using the search function of the messages is one of the best ways to find out if someone else has already gone through the issue.? Being a relatively long time user of this site, and reading most of the messages, I can see that the same problems keep coming up. I would suggest that a new member guide be part of the prerequisite for membership.? Part of that instruction should be the best way to find information on the sire.? This would be both helpful to the new member, and reduce the amount of rehash that seems to go on.? I can state that having to reiterate prior solutions to new members does get old after 3 or 4 times.? Calibration is one of those that keep coming up.? I had to use the search function myself to find the above thread.? It would have sped up the process for Morris if he knew about that feature in Groups.io. Above are my thoughts, yours may be different, and that is OK 73 Evan AC0TU 73 Evan AC9T |
F5NPV
Kevin Gilot NZ1I
to navigate to use esc to dismiss