Re: New uBITX Ver. 6 Assembled Today
?There is always the possibility of a bad mic element though I'd think it rare. Double check polarity, etc.? Yes, a nearby receiver may hear a touch of carrier in the background especially if there are a few inches of wire poking out of its antenna connector [which I recommend]. As long as we're speaking of carriers, have you wired in the CW pull-up resistor to the CW wires?? If so, try grounding the end that would have gone to a key. That will hopefully put out tons of carrier!? If that works, then we only have to worry about the mic wiring.?
If you did get carrier for CW, then try de-soldering the mic and separate the mic "hi" away from the earth/ground. Key the radio while listening to your backup receiver on freq and touch the mic "hi" line with a moist finger. You should hear some light buzzing from stray electric mains energy.? If not, that's troublesome. If you do, then check that there is voltage (+/- 12vdc) on this mic "hi" line, which it needs to have. No volts on this? Also troubling.? If Yes, then the element might be bad after all.
How about if we do these things and report back, please?
Ted
K3RTA
|
Oh, boy...oh, boy...oh, boy...!!!
Jack, W8TEE
On Wednesday, January 8, 2020, 11:34:36 PM EST, Hans Summers <hans.summers@...> wrote:
Hi Curt, all
> Oh yes - when the QSX finally comes out - take at look at that.? (But if you
> don't like its user I/O - you cannot change it, unlike the uBITX).?
This is not correct. The QSX user interface CAN be changed. Everything about the user interface is configurable. Display layout, operation of knobs and buttons, etc. You could also build your own totally different front-end hardware and interface it.?
Writing your own code for QSX totally would be very difficult; and the only way would be to physically remove the microcontroller and put in a new blank one, then do all your programming from scratch; someone who is capable of that would be capable of rolling their own entirely (hardware and software) and I would be surprised to hear of anyone actually doing this.?
The QSX does include its own programming language which controls the UI and many other features, and can be modified by the owner. It is powerful and flexible and allows a lot of extensions to the QSX. It makes the QSX very hackable, both in terms of hardware and software. At the same time it shields the owner from the most complex parts of the code, and protects the IP.?
73 Hans G0UPL
http://qrp-labs.com
-- Jack, W8TEE
|
Re: Need to Calibrate the V6
#v6
Thanks Ashhar, us newbies would appreciate this very much!
73
Mick VA3EPM?
|
Re: ubitx #v6 Screen Speed Mod
#v6
I agree with this statement...a lot! I have several Open Source chunks of code out there and I'll be the first to admit that I'm far from being the best coder around. My sentiment is that my code is a set of shoulders everyone can stand on to make my work even better. However, I've had situations in the past where someone has published a change to my code which sets off a Spiderweb Effect--pulling on one filament causes some bad things to happen elsewhere in the code. Had the coder contacts me privately first, I could have explained what was going on before a couple of dozen other readers wander down the wrong lane.
I think most Open Source people have private email addresses on QRZ.com that may be used for such coms. Letting the author of the code have a look at the proposed change may well save a lot of others from unnecessary hair-pulling.
Jack, W8TEE
On Wednesday, January 8, 2020, 11:45:13 PM EST, W2CTX <w2ctx@...> wrote:
This is just a suggestion to the group.? People like Reed have spent time to make ubitx better.? I think these software developers deserve respect.? Lets report issues DIRECTLY to the programmer first before posting to the group.? That gives the programmer a chance to fix or explain the issue.? If a fix is in order the programmer can alert the group.? The reason is that negative reports on the group are remembered longer than kudos? ....... Just my thoughts. rOn > On January 8, 2020 at 11:18 PM Armando Escalante < escalantea@...> wrote: > > > Reed, I have been using your version for a couple of days, all had gone well until now, I just tried to improve the BFO calibration, when I enter the setup and select Calibrate BFO I get what appears to be a corrupt screen. > Top indicates: > Set BFO > A few lines of empty space then > 2 lines above the final Press TUNE to Save I see, in this case: > 11.053ziVv]]_sm=\aR1+];{;Y9+3 > > Afterward, the BFO gets so bad? I can't hear anything intelligible. (used to be fine before this attempt) > > Any ideas? > A > > >
-- Jack, W8TEE
|
Alex,
IF (BIG IF) you plan to purchase and then build the v6 uBitx, My recommendation is to go the KD8CEC and Nextion display for your current build.? You will need to purchase, build or modify a case regardless.? I have also read on UBITX20 of efforts to move the v6 to the CEC/Nextion.? This would suggest that the CEC route might live on.
If you do not want two rigs, then the v6 is the future, as the v5 is no longer offered.
Following are my reasons:
1 - The current state of the CEC path is more developed than the v6, with all kids of software and hardware additions to help with CAT, S meter and other features.? I am sure that the v6 will catch up and probably surpass the prior versions,, just not there yet.
2 - The display is more graphical, in that it is not just numbers and letters.
3 - The screen response time of the CEC/Nextion appears to be much faster, at least as far as I can tell from videos of v6, as again, I do not own a v6, however I have 2 CEC/Nextions built (a v4 and a v5).
4 - I really like the MemoryManager for the CEC/Nextion combination.? Allows to quickly get back to a known state when experimenting.
5 - there is CAT control capability as part of the current CEC release.
I would expect that both are about the same level of complexity to upgrade from a stock v5, though on the CEC side you will need to load two devices with firmware (the display has it's own micro controller).
Check out the HamsKey.com and Ubitx.net web pages for more information.??
FWIW, the above are my opinions. Others can differ as they will have their own experiences that drive them.
73
Evan
AC9TU
|
Re: New uBITX Ver. 6 Assembled Today
Thanks Ted,
I wondering if my mic element isn¡¯t working should I hear a carrier on 40 meter LSB? The mic led lights and the relays switch when I key it, but no audio that I can discern.
:-)
|
Re: [uBITx V6] #v6 Noobie Big Picture Overview doc
#v6
More power to you, Andy! Thanks for everything that you are doing for the hobby and for the youngsters around you.
Very 73,
... Martin VE3OAT
|
Re: Sotabeams DSP cw/SSB filter insertion rf in audio
I think their DSP filter is pretty good, too.
Jack, W8TEE
On Thursday, January 9, 2020, 7:45:54 AM EST, Dennis Zabawa <kg4rul@...> wrote:
I am using the SOTABEAMS Variable filter.? I twisted the ground and power wires together and added a 10nF capacitor to keep the RF gremlins out.
-- Jack, W8TEE
|
Re: Need to Calibrate the V6
#v6
Mick, it would be best if someone (that is, me) made a video where you can hear what it sounds like. Lemme take a stab at it. - f
Some comments for clarification, and a couple questions.
step 2 above: for example I hear WWV on 14.85 MHz but I know it should be at 15.00Mhz so I tune the V6 to exactly 15000 as stated even though at 15000 I cannot hear the signal.
Step 3 above: once I hold the button in ( for about 7 seconds) to get the setup menu I get the selections:
? ? ? Set Freq....
? ? ? Set BFO....
? ? ?I assume for this step you want us to select Set Freq....?
? ? ?Once selected it confirms the Frequency you are tuning ( 15000 in my example )
Now for the question.
In step 4 you say tune for zero beat. For us newbies that term has no meaning. I know what it looks like on an oscilloscope but I¡¯ve never heard what zero beat sounds like. I tuned until I could hear the WWV signal the best. And the numbers displayed while I tuned were around 78000. Again I assume this is correct. They seemed like big numbers but it seemed to work.
I also found after this tuning if I went to the?
Set BFO menu item I could then set the BFO from the 11.053.00 setting to the best audio I could get. I my case it happens to be around 11057.6.
I also noticed if I repeated these steps I could get better results as I closed into the correct settings.
I hope these clarifications are correct and help.
73
Mick VA3EPM?
?
|
Re: Need to Calibrate the V6
#v6
Some comments for clarification, and a couple questions.
step 2 above: for example I hear WWV on 14.85 MHz but I know it should be at 15.00Mhz so I tune the V6 to exactly 15000 as stated even though at 15000 I cannot hear the signal.
Step 3 above: once I hold the button in ( for about 7 seconds) to get the setup menu I get the selections:
? ? ? Set Freq....
? ? ? Set BFO....
? ? ?I assume for this step you want us to select Set Freq....?
? ? ?Once selected it confirms the Frequency you are tuning ( 15000 in my example )
Now for the question.
In step 4 you say tune for zero beat. For us newbies that term has no meaning. I know what it looks like on an oscilloscope but I¡¯ve never heard what zero beat sounds like. I tuned until I could hear the WWV signal the best. And the numbers displayed while I tuned were around 78000. Again I assume this is correct. They seemed like big numbers but it seemed to work.
I also found after this tuning if I went to the?
Set BFO menu item I could then set the BFO from the 11.053.00 setting to the best audio I could get. I my case it happens to be around 11057.6.
I also noticed if I repeated these steps I could get better results as I closed into the correct settings.
I hope these clarifications are correct and help.
73
Mick VA3EPM?
?
|
Re: New uBITX Ver. 6 Assembled Today
On Wed, Jan 8, 2020 at 06:41 PM, Mick wrote:
Unfortunately I don¡¯t have an HF SWR meter to test with.
Free shipping:
* No snark intended; it's just a good buy and is a good part of any ham station's inventory. -Ted ?K3RTA ?
|
Re: New uBITX Ver. 6 Assembled Today
Hi. I tested mine using another radio. Short length of just coax from the recivibg one. Then proper antenna on the other. Transmit abs as the receiving test, radio has little antenna it only gets a week signal but still enough to prove it is transmiting.?
If that test OK, get a friend to give you a shout and work from there.?
Vaughn
I¡¯ve been testing my new v6 it seems to receive well I¡¯ve heard several stations. Unfortunately I don¡¯t have an HF SWR meter to test with. I now suspect I¡¯m not transmitting. I tried listening (using a WebSDR site) to my own transmission ?but I hear nothing. Anyone have any suggestions?
73
Mick VA3EPM
|
I can heartily recommend . Take the yellow wire from the audio header and feed a voltage divider using 5k resistors with the common junction going to the volume control. The audio out from this board can be fine tuned with this board's input trimmer; keeping the trimmer low, raise volume with the regular volume knob to distortion, then back down a little. Then, raise this board's trimmer to distortion again and then back the trimmer down a smidgen. That's your max, should your speaker of choice not explode first.? It will sound good at "normal" listening levels and will wake the dead when necessary.? Consider silencing this amp during TX by tapping the high side of R52 for its B+ to keep stray RF at bay. The tab of this amp's TDA2030A can be chassis grounded :)??
On a V3 or V5/6 board, one could probably use a 2.2k/8k combination but the V4's got not much drive to begin with.
-Ted
? K3RTA
|
Re: Sotabeams DSP cw/SSB filter insertion rf in audio
I am using the SOTABEAMS Variable filter.? I twisted the ground and power wires together and added a 10nF capacitor to keep the RF gremlins out.
|
Re: CW Audio High Pitched and Thin
#cw
HI Andy -
I don't have a document..... I just figured this out myself!?
The Memory Manager software requires the KD8CEC firmware.? The firmware and the Memory Manager software can be found via links on ubitx.net. ?
You can either use Memory Manager or you can use the KD8CEC firmware directly on the radio to adjust the BFO. ? See John vk2eta's note in this thread on that.
Good luck and 73,
Dean
?
|
Re: CW Audio High Pitched and Thin
#cw
Hi Alex,
You connect the radio to the computer via the usb port on the Raduino (the Arduino Nano has a usb port).? You can get the find the links and instructions to load the KD8CEC firmware and memory manager on ubitx.net.?
Good luck,
Dean
KK4DAS
|
Rereading your original post, I am not sure which version of the KD8CEC sketch you are using. Note that the versions with the -S suffix are not appropriate unless you add the second signal analyzer Nano chip. The standard software has everything needed for an S-meter using the spare analog input to the Raduino.
=Vic=
|
Re: [BITxV6] BRICKED recovery help needed
Andy,
Did you have a chance to try the hex file I sent? If so, did the update fix the white screen issue you were seeing?
Reed
|
Re: one_stop_setting debugging
#v6
Dean - I haven't seen a PM in any of my inboxes, but shot you a message using the email you have on record with QRZ.com. Hopefully that puts us in touch.
All - I still plan on picking this endeavor back up, but I'm also still waiting on parts before I can complete my build, at which point I'll finally be able to test/debug the branch properly by myself :P
Reed
|
Re: ubitx #v6 Screen Speed Mod
#v6
Ron (and everybody else) - The absolute best spot to report problems in general is via GitHub's Issues page, since it automatically tracks them, they can be marked as resolved, easily reference them when code changes fix things, etc. Specifically, here: . For issues related to this specific piece of work (the pdq_gfx_update branch), the best spot is to comment on the Pull Request for it, located here: . I don't expect everybody here to necessarily know exactly what bugs are from my branch, and which are inherited from the current master, but if you comment on the PR where you're having the problem, "us coders" can sort it out.
Armando - I just tried changing the BFO a few times on my nano running, and didn't see any graphical glitches. Do you know which version of the software you're running? Specifically, what commit number? I fixed a number of issues related to the setup menus in commit 9ebdf8b213dd6c4996796ec35b294ccc86016c2e a few days ago, so if you grabbed an earlier version of the branch, you might try updating to the current version (f1ea1fd081d128895f336d0ca16de6246a422f2f) and see if your problem "magically" disappears.
Reed
|
Ted
Mick
Vaughn
Vic WA4THR