Date   

Re: Just finished my first uBitx

Jeff Debes <jeff.debes@...>
 

Looks great!


On Sep 4, 2020, at 7:38 AM, Mick <Mgsebele@...> wrote:

Very nice Chris!
Thanks for sharing.
I. Was wondering what metal break did you use? 
--
 

73
Mick VA3EPM 


--
jeff.debes@...


WARNING -- Promotional material

Jack, W8TEE
 

All:

A number of things:

1. I have gone through the entire book and reformatted all of the source code listings. I also increased the font size used in the listing by 25% so even us old people can read it more easily. As a result, the new version of the book is approximately 50 pages longer than before. Although the cost of the book has increased because of the higher page count, there's no reason for you to pay more because of my mistake. The price remains the same for both the printed and eBook versions. Amazon tells me that the new version of the book will be available on orders on and after Monday, Sept 7, 2020.

2. I have removed the index from the printed book. The reason is because my index numbers do not exactly match their printed version. However, the 850+ index entries help to make the book useful, so I am ordering printed copies and will re-paginate the index after I have received a copy of the new book. I will then post the new index on the SoftwareControlloredHamRadio (SCHR) site when it is done. You can then download the index and use it with the printed book. (I would think eBook users would also find it useful when used in conjunction with the Kindle word search facility.) I will send out a notice when the index is done, but only to members of the SCHR group. That will lessen the bandwidth that the message takes.

3. All of the Exercises are also complete for all chapters. They, too, can now be downloaded from the SCHR site. Please: Try to answer the questions before looking at my answer, for several reasons: 1) testing yourself as you read through the book is the only way to accurately assess how you are progressing, 2) it's good practice for you to select data types and make up variable names, 3) if you have trouble answering a question, it tells you that you should review that aspect of the text, and 4) you could end up with a better answer than I give! Finally, there are a couple of Exercises where I don't give any answer because I really want you to answer them yourself.

I appreciate that I am intruding on members of other groups who could care less about this topic, and I hope that the tag line helps them avoid it. However, I cannot see any other way to inform interested members of the changes. I will only be using SCHR from now on for notices.

Thanks for your forebearance!

Jack, W8TEE

--
Jack, W8TEE


Re: Just finished my first uBitx

Chris WB4ULK
 

I used a 30” hand break from Hazard Freight. 😂


Re: A strong recommendation

Pirok-W4UNX
 

Got mine!


On Wed, Aug 26, 2020 at 12:58 PM Ben Holmes <judosandan@...> wrote:
Appreciate the recommendation... ordered.



--
Jason Pirok
W4UNX


Re: V6, V61, V6.2 -- confused!

Bill Cromwell
 

Hi,

Lots of room for confusion. The uBitX hardware maybe should be named by "model" number which is more clear and is also traditional. Currently model 6. Model numbers do not seem to have decimal points.

The software that controls the radios should maybe retain the version numbers. Version 6.1 would be a version of the software intended for model 6. They love it call it firmware but it is not *burned* in. Software versions may or may not have decimal points.

Sometimes the different models have rather minor differences and software versions are interchangeable across several models. Other models have more important differences and cannot be used with the software from other versions. There are also options that have names and most of those require different versions of software. Different displays are prolific and there are various AGC and other options.

There is quite a variety of choices in the garden. The models are essentially model 3, model 4, model 5, and model 6.

If that doesn't cause enough confusion and headaches the list and the website includes older models named BitX that are single band units and are very different from the uBitX (microbitx). Even old hands get confused about those two very different types of radios so you are in good company.

I hope this helps.

73,

Bill KU8H

bark less - wag more

On 9/3/20 7:24 PM, David KK7SS wrote:
Total newbie to uBITx.. !!
I see references to 6, 6.1 and 6.2..
Anyone care to enlighten me as to what's going on?
Which is the latest hardware and the best place to get it?
tnx
--
Dave KK7SS


Re: Just finished my first uBitx

Mick
 

Very nice Chris!
Thanks for sharing.
I. Was wondering what metal break did you use? 
--
 

73
Mick VA3EPM 


Re: VK4PP ultimate add-on boards #ubitx

Cor Beijersbergen
 

And his logbook on QRZ.com shows a contact in July this year, so he is still active indeed.

 

From: BITX20@groups.io <BITX20@groups.io> On Behalf Of Glenn
Sent: Friday, 4 September 2020 03:50
To: BITX20@groups.io
Subject: Re: [BITX20] VK4PP ultimate add-on boards #ubitx

 

I think Nick, VK4PP may have changed his email address.

According to QRZ.COM he is still active, currently building a linear.

vk3pe


Re: V6, V61, V6.2 -- confused!

Reed N
 

I'm not entirely sure what you're asking, but I can explain some of the numbers.

v6 is the general name for the latest uBiTX revision, which comes with a ILI LCD touch screen.

v6.1 is the name of Ashhar's latest software on GitHub (the previous version was v6.3.1, confusingly)

v6.2 is the PCB version printed on the main v6 board.

So lots of numbers, but they all are referencing different things. If you buy a v6 from HFSignals, you'll get a v6.2 running v6.1 :P


Reed


Re: VK4PP ultimate add-on boards #ubitx

Gerry Kavanagh
 

He did, but that post dates from 2 years ago. People often make promises with the best of intentions, and for whatever reason don't make good on them. Eventually it just slips out of mind and nothing further rhappens.
You could try messaging him to find out.


Re: uBITX v6 to WSJT-X running on Raspberry Pi 3B - "Target VFO unaccessible.." #ubitxv6 #wsjt-x #raspberrypi3b

Ashhar Farhan
 

it is probably time to write a separate module for ubitx for hamlib. does anyone here know the hamlib folks?
- f

On Fri, Sep 4, 2020 at 5:33 AM AndyH <awhecker@...> wrote:
Stephen,

   This is a problem with V2.2.2 of WSJT-X (possibly related to Hamlib 4.0) and I had the same challenge with my µBITX.  I dropped back to V2.2.0 and FT-817 control works perfectly.  As an alternative, supposedly we can stay with V2.2.2 and change the FT-817 to FT-857.  I've not yet tried that option.

    More here:  https://wsjtx.groups.io/g/main/topic/bug_hamlib_cat_rig_not/75122237?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75122237

73, Andy, KG5RKP

On Wed, Sep 2, 2020 at 06:21 PM, Stephen KO4CVU wrote:
This problem may be indirectly related to Aaron's situation. I am running WSTJ-X on a Raspberry Pi 3B. The firmware on the uBITX is Reed's R1.5.0. I have been very successful receiving without CAT control but now I'd like to transmit. I am reasonably sure that I finally found the correct identification for the USB serial port on the Pi that I have the cable from the uBITX plugged in to. I say this because the display on the uBITX flashes when I click on the "Test CAT" button from the Configuration>Radio window in the WSJT-X software. Using the FT-817 as the radio with default data bits, default stop bits and default Handshake as shown in Reed's v6 Manual ((R1.5.1), I get the error message "Rig Failure Hamlib error: Target VFO unaccessible while getting current frequency." I have tried various combinations of data bits and stop bits but continue to get the same message. I have also tried setting the radio choice to FT-857 and then I get "Rig failure Hamlib error: Protocol error while testing getting current VFO." I have tried various combinations of data bits and stop bits with this choice, too. I would appreciate any suggestions about what to try next.  Thanks, Stephen, KO4CVU
P.S. Fldigi works great running on the Pi, but that software can be configured to use the PTT circuit on the uBITX via the Nexus DR-X cross patch which I have mounted on top of the Pi.


Re: Just finished my first uBitx

Ashhar Farhan
 

Great music too!


On Fri, Sep 4, 2020 at 11:30 AM Chris WB4ULK via groups.io <chood73=yahoo.com@groups.io> wrote:
I documented my build here:

http://www.chrishoodblog.com/ubitx-hf-radio-project-pt1/


Re: Just finished my first uBitx

Chris WB4ULK
 


Just finished my first uBitx

Chris WB4ULK
 

Man these are GREAT projects! Reminds me of the old Heathkits.


Re: Nieuw TFT-bestand voor Nextion Enhanced 3.2 met CEC 1.2 #nextion

Rene <rmvanb@...>
 

Yes its working now. Thx when my extion comes in from Ali, a am gonna try. But Ali is verry slow, 8 till 16 weeks...pfffff


Re: V6, V61, V6.2 -- confused!

Evan Hand
 

David,
I do not really know the answer to your question.  I do know that HFSignals.com is the manufacturer, so I would assume that the latest revision of the board would come from them.  I believe that is 6.2.

The software also has been revised.  That is available on github.
https://github.com/afarhan/ubitxv6

The last version of the software is 6.3.1

Hopefully, Ashhar Farhan or another representative of HFSignals can give better information.

73
Evan
AC9TU


Re: VK4PP ultimate add-on boards #ubitx

Glenn
 

I think Nick, VK4PP may have changed his email address.

According to QRZ.COM he is still active, currently building a linear.

vk3pe


Re: uBITX v6 to WSJT-X running on Raspberry Pi 3B - "Target VFO unaccessible.." #ubitxv6 #wsjt-x #raspberrypi3b

AndyH
 

Stephen,

   This is a problem with V2.2.2 of WSJT-X (possibly related to Hamlib 4.0) and I had the same challenge with my µBITX.  I dropped back to V2.2.0 and FT-817 control works perfectly.  As an alternative, supposedly we can stay with V2.2.2 and change the FT-817 to FT-857.  I've not yet tried that option.

    More here:  https://wsjtx.groups.io/g/main/topic/bug_hamlib_cat_rig_not/75122237?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75122237

73, Andy, KG5RKP


On Wed, Sep 2, 2020 at 06:21 PM, Stephen KO4CVU wrote:
This problem may be indirectly related to Aaron's situation. I am running WSTJ-X on a Raspberry Pi 3B. The firmware on the uBITX is Reed's R1.5.0. I have been very successful receiving without CAT control but now I'd like to transmit. I am reasonably sure that I finally found the correct identification for the USB serial port on the Pi that I have the cable from the uBITX plugged in to. I say this because the display on the uBITX flashes when I click on the "Test CAT" button from the Configuration>Radio window in the WSJT-X software. Using the FT-817 as the radio with default data bits, default stop bits and default Handshake as shown in Reed's v6 Manual ((R1.5.1), I get the error message "Rig Failure Hamlib error: Target VFO unaccessible while getting current frequency." I have tried various combinations of data bits and stop bits but continue to get the same message. I have also tried setting the radio choice to FT-857 and then I get "Rig failure Hamlib error: Protocol error while testing getting current VFO." I have tried various combinations of data bits and stop bits with this choice, too. I would appreciate any suggestions about what to try next.  Thanks, Stephen, KO4CVU
P.S. Fldigi works great running on the Pi, but that software can be configured to use the PTT circuit on the uBITX via the Nexus DR-X cross patch which I have mounted on top of the Pi.


V6, V61, V6.2 -- confused!

David KK7SS <d3j452@...>
 

Total newbie to uBITx.. !!
I see references to 6, 6.1 and 6.2..
Anyone care to enlighten me as to what's going on?
Which is the latest hardware and the best place to get it?
tnx

--
Dave KK7SS


Re: uBITX v6 to WSJT-X running on Raspberry Pi 3B - "Target VFO unaccessible.." #ubitxv6 #wsjt-x #raspberrypi3b

Evan Hand
 

Did a quick search and found the following.  This may not be the actual web site that I used, however, it is one very similar.  
https://dl1gkk.com/setup-raspberry-pi-for-ham-radio/

The key things that need to be done are the installation of Flrig and Fldigi (I assume you already have the WSJT-X installed.  Those two allow connection to the uBITX.

Again, I will go back and setup my Pi station.
73
Evan
AC9TU


Re: uBITX v6 to WSJT-X running on Raspberry Pi 3B - "Target VFO unaccessible.." #ubitxv6 #wsjt-x #raspberrypi3b

Evan Hand
 

Stephen,
I have used my Raspberry Pi 4 to run the WSJT-X with the uBITX, so it is possible.  I will go back an dig up the details.  One thing I do remember is that you still need a separate dongle for it to work.  that is the same one I used for the Windows version.

It may take a couple of days to recreate what I did, as I have dismantled my Pi station (Using a Windows 10 laptop now).

73
Evan
AC9TU

7361 - 7380 of 88165