Date   

Re: Content flagged as objectionable

Arv Evans
 

Al

I try to catch these and ban them every time they appear but apparently one sneaked through. 
This one is interesting because they actually joined the BITX group in order to send their spam
advertisement.

I will take care of this today.    Thanks for bringing it to my attention.

Arv
_._
_._


On Wed, May 20, 2020 at 12:41 PM Groups.io <noreply@groups.io> wrote:
Hello,

awhecker@... wishes to inform you that the following message:

https://groups.io/g/BITX20/message?id=166269430

is objectionable. They entered the following reason why it should be considered objectionable:

----
spam
----

Please take a moment to review and take action as you feel appropriate for your group.


Cheers,
The Groups.io Team


Re: Is there a complete v1->v2->v3->v4->v5->v6 hardware version history?

Evan Hand
 

Ashhar Farhan, if you do not know I do not know who would. 

Dan,
From what I have been able to find on the net, there were a number of "clones" of the HF Signals version of the uBITX.  Most were copies of the original BITX20 single band radios.  I would not purchase one that is not from HF Signals, as the information is hard to find.  This means that you want a v3 or later microBITX.

The differences between the versions are best recorded on ubitx.net.  Without going into detail, most of the differences were to fix audio issues and key clicks (v3->v4) and then spurs and harmonics issues (v4->v5) and finally to include a touch screen interface (not sure I would call it graphics, as the display is text-based)(v5-v6).  The v6 is also the first version that you can order a "full" kit that includes the enclosure from HF Signals.  There are still some enclosures for the v3-5 that you can buy, though I believe that these will get harder to find as they are no longer in production.

If you do purchase any version prior to 5, you should do a harmonics and spurs test to verify compliance with the FCC (by your call I looked up that you are in the USA).  Ubitx.net has the fixes listed there as well.

Hope this helps you with your purchase choices.  They are MY preferences/thoughts, you will need to verify for yourself.
73
AC9TU
Evan


Re: #ubitxcw #ubitxv6 More signal out on 10 meters than other bands? #ubitxcw #ubitxv6

Evan Hand
 

I have been using that mic without the capacitor.  When I checked, there was one on the board in the mic.

You just need to make the connection with either a 3.5 mm TRS plug to 4 pin jack, or cut off the 4 pin plug and connect a 3.5 mm TRS plug.  The tip is the mic, the ring is PTT and sleeve goes to the ground/common for both.

For my rigs, the mic gain is set between 4 and 5 on the dial.  That seems to provide the correct amount of output without distortion.  

Good luck and happy QSOs.
73
Evan
AC9TU


Re: Is there a complete v1->v2->v3->v4->v5->v6 hardware version history?

Ashhar Farhan
 

I dont think there was a v2. Was there?


On Thu 21 May, 2020, 1:01 AM , <pulco.ant@...> wrote:
Hello. I'm sorry to be *that guy* but I have tried multiple searches here and turned up very brief snippets. What am I missing?

I found a V2.2 for sale and I'm trying to learn the hardware differences between models.

73
Dan 
AG7GM


Re: hfsignals safety

Ashhar Farhan
 

i am mucking around with this. hopefully the bug is now gone. we are setting up a backoffice to smoothen the order tracking etc.

- f

On Wed, May 20, 2020 at 10:07 AM Reed N <greenkid336600+groupsio@...> wrote:
Looks like the cert is valid for admin.hfsignals.com and hfsignals.com, but NOT www.hfsignals.com, and thus creates a nice big warning. Pretty sure this is an issue with the cert setup, and not an actual website hack.


Reed


Is there a complete v1->v2->v3->v4->v5->v6 hardware version history?

Dan D'Eon
 

Hello. I'm sorry to be *that guy* but I have tried multiple searches here and turned up very brief snippets. What am I missing?

I found a V2.2 for sale and I'm trying to learn the hardware differences between models.

73
Dan 
AG7GM


Re: #ubitxcw #ubitxv6 More signal out on 10 meters than other bands? #ubitxcw #ubitxv6

Stephen KO4CVU
 

Evan,
As you suggested, I connected an audio (cassette player) source in series with a 1 mfd electrolytic capacitor to the microphone input. (I had recorded my voice speaking “Test Test” with my call sign on the tape.) The current consumption will exceed 1 amp on both the 10 meter and 80 meter bands at the peak volumes on the tape. Looks like a bad Baofeng microphone but I won’t know for sure until I receive the CB microphone with pre-amp. I ordered the one you suggested in your previous message the other day. Am I correct in thinking that I will need the 1 mfd capacitor with it also? I will let you know whether the new microphone solves the problem or not. 
Thank you for your help.
Stephen, KO4CVU


Re: Nextion Display on uBITX #ubitx #nextion

Bill Cromwell
 

Hi,

If you a CW user you may prefer to install the CEC software or Reed's software. I have worked on several uBitX radios for others and the stock software has been unsatisfactory in various degrees. The original V6 software rendered CW completely unusable but I think that has been fixed now.

By all means try your radio 'as shipped' and if you are satisfied continue to enjoy it. My V3 has very few mods with the CEC software being the biggest change.

73,

Bill KU8H

On 5/20/20 9:46 AM, Aaron K5ATG via groups.io wrote:
Thanks, everyone for the replies and the explanations.
I agree I want to give the stock configuration a go for a while. I want to learn the characteristics of the radio before I start changing it.
--
bark less - wag more


Re: uBitx V6 GNDREF Connection #v6 #ubitxv6 #ubitx-help

Reed N
 

I see GNDREF on T1, T2, T3, and T4 in the v6 schematic, but I went ahead and tested continuity on TP1, and sure enough, it conducts to GND at DC. Only paths are through caps (open at DC) and T2 inductor to GNDREF, so I guess I was wrong!


Reed


Re: uBiTX #v6 - First steps after assembly #v6

Reed N
 

Hi Urs,

Evan Hand kindly pointed out that the correct resistor value is just 125, not 125k. If you heard tones, it doesn't matter that much to be on the conservative side, but good to set the record straight.

If you look at https://github.com/reedbn/ubitxv6/blob/input_output_debug/ubitxv6.ino#L188 you can see what tones should play under which conditions. I forgot about the SPI touch. Ground the SPI MISO to stop the touch button from thinking it's pressed, since then it will read all 0s. Alternatively, you can delete the "checkTouch" call and hard code that value to NotPressed.


Reed


Re: Nextion Display on uBITX #ubitx #nextion

Aaron K5ATG
 

Thanks, everyone for the replies and the explanations. 
I agree I want to give the stock configuration a go for a while. I want to learn the characteristics of the radio before I start changing it. 


Re: uBitx V6 GNDREF Connection #v6 #ubitxv6 #ubitx-help

Evan Hand
 

I went back and checked the v3, v4, v5, and v6 schematics.  All are the same with only 2 GNDREF points on T2 and T4.  In the case of T4, it would need to be at the same level as the rest of the board ground in order for the radio to work (Both of the IF amps need it for either input or output).  For T2, the antenna connection is drawn connected to the common ground, not GRNREF.  Based on this, I do not see any distinction between them.  It may have been a holdover from a pre-v3 design, or a simple typo with the copy-paste function when Ashhar Farhan created the schematics.  I have not taken my units apart to look, however, I am confident that the shield connection of the antenna goes to the common ground for the board.

May I ask the reason for your question?  It is better to know how the answer would be used to ensure that we can give you the information that you want.

73
Evan
AC9TU


Re: Nextion Display on uBITX #ubitx #nextion

Evan Hand
 

Reed,

Thank you for the summary and all of the posts you make on this board.  I can say I read everyone from you and get insights from all.  

I do have 3 Nextion uBITX, 2 v4, and 1 v5 with various size screens.  Your comments as far as the Nextion devices are correct, and I agree that you should start with the stock stuff, get it going, and then start the upgrade journey from there. 

Again Thank You!
73
Evan
AC9TU


Re: uBiTX #v6 - First steps after assembly #v6

Urs, dl1kdx
 

Hi Reed,

here my test results valid for stock Nano and replacement:

1. Booting the Nano gives 1320 Hz tone out of the speaker.
2. Rotating the Encoder leads to scratching noise on the speaker.
3. Short pressing (< 3 secs) the Encoder has no impact on audio.
4. Long pressing (> 3 secs) gives 440 Hz tone for 5 secs with a delay of 3 secs.

So it would mean the rotating part of the encoder is faulty? Unfortunately I don't have a spare one on me.

73 de Urs


Re: V6

Reed N
 

Requires a very small amount of assembly. See https://www.hfsignals.com/index.php/ubitx-v6-assembling-the-full-kit/


Reed


Re: uBiTX #v6 - First steps after assembly #v6

Reed N
 

Hi Urs,

I've added some colors to the raduino schematic. The black/brown/orange/yellow of the encoder is on top, and while the speaker wire is also brown, I've colored the cw_tone trace purple. It's probably not great to drive the speaker by itself directly from the microcontroller, since it has such a low resistance, so if you can throw a 125k resistor in series with the speaker to limit the current on the D6 pin to 40mA, your nano will thank you.


Reed


Re: uBiTX #v6 - First steps after assembly #v6

Urs, dl1kdx
 

Rotary Encoder wiring:

Black - GND
Red - Button
Brown, Yellow - Phase A, B

Right?


Re: Nextion Display on uBITX #ubitx #nextion

Reed N
 

Hi Aaron,

Disclaimer: I don't have a Nextion screen, but have done my fair share of research on them.

First, some history. The v5 and older uBiTX models only had a 2-line text LCD, so this wonderful community decided to step it up a notch and add a nice touch screen (the Nextion), and KD8CEC's software added a bunch of additional functionality, like the memory manager. This was all possible because all of the screen rendering and graphical resources were stored on the Nextion itself, so the Arduino Nano just had to know how to send and receive serial commands. The Nextion is actually programmed separately, and has it's own coding and microprocessor to run the menus, and turn the raw touch inputs into meaningful desired action inputs. Furthermore, there are larger and smaller Nextion screens available, so if you want a different size, you can have it. If you're getting the stock v6 case, this probably isn't something important to you, since it'd would be difficult to resize the screen opening.

The uBiTX v6 added an ILI9341+XPT2046 touch screen. However, unlike the Nextion, this screen does NOT store ANY of the graphical resources, and does NOT store or render stuff automatically. This means that the Arduino Nano has to, in addition to running the radio, drive the screen output, and receive and process the raw touch inputs. The Arduino Nano was released in 2008 (source: https://blog.arduino.cc/2008/05/15/arduino-nano-all-in-one-design-for-breadboard-use/), so at 12 years of age, it's fair to say it's long in the tooth as far as microcontrollers go, especially when trying to drive a color touch screen with 320*240*8*3=1,843,200bits of data to present. For comparison, the newest Arduino Nanos have just 262,144 bits (32,768 bytes) of flash memory, and only 30720 bytes of that is available for normal use! It's actually quite remarkable that the Arduino Nano works as well as it does in the uBiTX v6 - big kudos to Ashhar for making it work. That said, the relative lack of flash space and general processing power on the Arduino Nano means that you literally can't make the screen presentation match the speed or style of the Nextion, nor can you fit as many features, since those take up programming space too. I was able to squeeze in a bit more functionality in my branch (see full thread: https://groups.io/g/BITX20/topic/r1_4_0_software_release/73992676), but ultimately there's just not enough space for all the features a person might want.

I'd recommend you give the stock software and then my software a go first. It costs you nothing, and if it's good enough for what you need, great! If not, then there are a couple options worth considering:
1) Buy a Nextion and install the KD8CEC software on the Arduino Nano. This solution is tried and true, and you can find several posts on here with people who have already done this conversion with their v6's
2) Buy a better microcontroller option. JACKAL is a Teensy 3.6-based upgrade path, with some additional hardware features too. TSW has their Teensy 4.0 adapter board, which leaves your system mostly stock. Both of these options include software that takes advantage of the much more powerful microcontrollers to give you additional features, and revised screen graphics. You can also spin up an ESP32 for the task like Ramón EA4GZI, although at the present you'll have to sort out the wiring yourself.


Reed


Re: uBiTX #v6 - First steps after assembly #v6

Urs, dl1kdx
 

Hi Reed,

thanks for your great advice. I will figure it out and give update later.

To clarify the connectivity:
1. Speaker connects straight to D6 and GND.
2. Encoder's A & B connects to A0 & A1.
3. Encoder's button to A2.
4. Encoder to GND.

Could you please name the encoder's colors according to the pics above?

73 de Urs


Re: Nextion Display on uBITX #ubitx #nextion

Rene
 

Hallo Aaron, ik heb mezelf ook een Nextion 3.2-scherm besteld. Door veel problemen met mijn Bitx V6 en druk bezig met constructies aan mijn huis kan ik momenteel geen tijd aan de radio besteden. Wat ik heb gelezen en wat ik heb gezien en begrepen, is de software en dingen die u op het scherm efficiënter kunt zien. Ziet er ook beter uit. Dus over een maand of 2 i am gonna try to instal this screen. Also i believe that cat control by usb is working good. There is more then enough to find on rhis forum and on HF Signals. 
Greetz,
Rene
Netherlands