Topics

UBITX6 Will Not Select 17 Meters

k7ome@...
 

Not that I particularly wanted to use 17 but all the other bands select just fine. Anybody else seeing this issue?

Gary Anderson
 

https://groups.io/g/BITX20/message/74007

Jim Sheldon
 

There's an error in the original factory programming code.  You need to change line 746 in the ubitx.h file to read exactly like the following
 else if (!strcmp(b->text, "17"))  The error has the 17 as 18 in the original source code.  Change that 18 to 17, recompile & upload the program.  The 17 meter button will then operate.

Unfortunately, the way the original is set up, and already calibrated, if you re-compile the program you will have to re-set your frequency calibration AND BFO setting as it will revert to the defaults in the original source code.

BFO setting -- 11.055.0 is a good place to start (each V6 radio is slightly different.  Mine actually came out 11.055.4 when the BFO was set to the proper point on the filter).

Jim, W0EB

------ Original Message ------
From: k7ome@...
Sent: 1/5/2020 10:22:30 AM
Subject: [BITX20] UBITX6 Will Not Select 17 Meters

Not that I particularly wanted to use 17 but all the other bands select just fine. Anybody else seeing this issue?

k7ome@...
 

Thank you, Jim!   I figured it was something like that.  I just got the radio and haven't had time to dig into the code yet but I can make the changes you recommended.  

Many thanks to all who replied....

John Spasojevich
 

Any word on if this will be corrected on the units shipping late January?

John AG9D

On Sun, Jan 5, 2020, 1:57 PM <k7ome@...> wrote:
Thank you, Jim!   I figured it was something like that.  I just got the radio and haven't had time to dig into the code yet but I can make the changes you recommended.  

Many thanks to all who replied....

Reed N
 

@John,

Ashhar hasn't made any code changes to his branch recently, so as of right now, I wouldn't count on it. However, at the beginning of this year he said he was traveling, and there's still 2 weeks before the 20Jan2020, so it's definitely possible that they might have a new official version before then.
https://github.com/afarhan/ubitxv6


Reed

Andy_501
 

YUP ditto here also.

On 2020-01-05 10:22 a.m., k7ome@... wrote:
Not that I particularly wanted to use 17 but all the other bands select just fine. Anybody else seeing this issue?

Dave Dixon
 

yeah same here the rest of the bands work fine just no 17 mtrs..dave G0AYD.

On Sun, 5 Jan 2020 at 23:12, Andy_501 <andrew.webb.501.ve4per@...> wrote:

YUP ditto here also.

On 2020-01-05 10:22 a.m., k7ome@... wrote:
Not that I particularly wanted to use 17 but all the other bands select just fine. Anybody else seeing this issue?

Erwin Serlé
 

@Jim Sheldon, in this case it would be advisable to read and note the original calibration settings before doing the actual install of a new firmware.

Also as far as I understood the findings of KD8CEC a new firmware does not change the stored calibration values.

The KD8CEC Memory Manager software could be used to read the original values before doing any changes.

--
PE3ES - F4VTQ - Erwin
73

Jim Sheldon
 

Erwin Serle,
Did you not read my posts all the way.  I thought that was what I said the person should do.  Besides, KD8CEC and Nextions don't work with the V6 Raduino which uses an ILI9341 TFT Touch screen display, NOT a NEXTION as it comes from the factory.

Jim Sheldon

------ Original Message ------
From: "Erwin Serlé via Groups.Io" <waterwin2@...>
Sent: 1/6/2020 6:02:37 AM
Subject: Re: [BITX20] UBITX6 Will Not Select 17 Meters

@Jim Sheldon, in this case it would be advisable to read and note the original calibration settings before doing the actual install of a new firmware.

Also as far as I understood the findings of KD8CEC a new firmware does not change the stored calibration values.

The KD8CEC Memory Manager software could be used to read the original values before doing any changes.

--
PE3ES - F4VTQ - Erwin
73

Ashhar Farhan
 

The changes have been pushed. The new boards will have the fixes.

- f

On Mon 6 Jan, 2020, 7:43 PM Jim Sheldon, <w0eb@...> wrote:
Erwin Serle,
Did you not read my posts all the way.  I thought that was what I said the person should do.  Besides, KD8CEC and Nextions don't work with the V6 Raduino which uses an ILI9341 TFT Touch screen display, NOT a NEXTION as it comes from the factory.

Jim Sheldon

------ Original Message ------
From: "Erwin Serlé via Groups.Io" <waterwin2@...>
Sent: 1/6/2020 6:02:37 AM
Subject: Re: [BITX20] UBITX6 Will Not Select 17 Meters

@Jim Sheldon, in this case it would be advisable to read and note the original calibration settings before doing the actual install of a new firmware.

Also as far as I understood the findings of KD8CEC a new firmware does not change the stored calibration values.

The KD8CEC Memory Manager software could be used to read the original values before doing any changes.

--
PE3ES - F4VTQ - Erwin
73

Steve Sawicki
 

Good Day Erwin,
I am beginning to believe that  my trust and belief in the UBITX  concept has been shaken and  was a bit  ahead of reality.
Yes the "V6" that I ordered is actually a V5 with a  touch screen display that was rushed  with "production" and shoddy packaging (I spent $209)  with discovering that the "Kit" was assembled in a rush with many missing items (yes I have a good junk box) that was able to compensate for missing and bent metal.
But the item that I was surprised and disappointed  me  that right out of the box was that the Firmware has a BUG with 17 meters  and will require a  new load is extremely troubling.
I have been trying to fallow the various routes to HOW to DO correct the BUG and unfortunately it has me totally confused I attempted to understand how to implement the "KD8CEC Memory Manager software" with total confusion.
It is my personal belief that  after spending the monies to  buy the product that the producer should provide a CLEAR and EASY SOLUTION that can be easily implemented by the average individual.
Yes I have a "assembled " V6  that at this point have put it on the shelf until the smoke clears .
Regards.
Steve
AB2ET/4
 

Steve Sawicki
 

So how about the existing boards that we received at Christmas time, I believe that ALL should hear as to what will be for them.
Regards.
Steve
AB2ET/4

Reed N
 

@Steve,

The "17m won't work" isn't that 17m doesn't work, it's that the quick select button for 17m doesn't work. If you don't want to update the software, you don't have to - just tune to 17m manually. Inconvenient, yes. Radio-breaking flaw, no. However, this particular issue is one that you can fix right now yourself. Ashhar said, "The changes have been pushed", so if you go to https://github.com/afarhan/ubitxv6, download the repo (green button on the right, choose download zip), and upload the revised code to your Arduino nano, the 17m button should work as expected. If you don't know how to program an Arduino, there are tons of tutorials online, and I'm sure you can find that information with a quick search for "how to program an Arduino nano".

I (and I expect many others) bought the uBitx specifically because it can be reprogrammed and easily modified. It's a bit rough around the edges, but I fully expected that coming in. If I wanted a high quality radio that "Just Worked" out of the box, I'd buy from the big three - Yaseu, Icom, or Kenwood - since they have large teams of experts designing and testing their radios extensively, whereas HFSignals is tiny by comparison. It sounds like your expectations may have been different, which is unfortunate. The uBitx is designed to be a decent radio with a strong emphasis on cost and hack-ability, not a best quality or polished final product. To quote the "About" page https://www.hfsignals.com/index.php/about-hfsignals/:

 With the BITX40, we hope to recover that ground and encourage more and more people to get on air, modify, experiment, build and learn. ... The HF Signals kits are supplied as-is without any promise that they will work to any particular specification. That said, thousands of BITX transceivers supplied by HF Signals work across the world. There is an active and very informative forum for learning and getting help that is entirely driven by the builder community.
The BITX and uBITX lines both have had a number of issues - just scroll through this forum and you'll find lots of problems, but also lots of solutions. It's constantly improving because people donate their time, but that doesn't mean everything is perfect out of the box. In particular, the v6 is a brand new release, which means you're on the bleeding edge - the new software hasn't seen as much testing and improvement as the software for earlier version. I fully expect that by this time next year, most of these issues will be fully resolved or worked around, if you don't mind waiting.


Reed

Bob Bennett
 

Farhan,
   I assume you will sell the boards separately?

Bob  NZ2Z

On Jan 6, 2020, at 11:01 AM, Ashhar Farhan <farhanbox@...> wrote:


The changes have been pushed. The new boards will have the fixes.

- f

On Mon 6 Jan, 2020, 7:43 PM Jim Sheldon, <w0eb@...> wrote:
Erwin Serle,
Did you not read my posts all the way.  I thought that was what I said the person should do.  Besides, KD8CEC and Nextions don't work with the V6 Raduino which uses an ILI9341 TFT Touch screen display, NOT a NEXTION as it comes from the factory.

Jim Sheldon

------ Original Message ------
From: "Erwin Serlé via Groups.Io" <waterwin2@...>
Sent: 1/6/2020 6:02:37 AM
Subject: Re: [BITX20] UBITX6 Will Not Select 17 Meters

@Jim Sheldon, in this case it would be advisable to read and note the original calibration settings before doing the actual install of a new firmware.

Also as far as I understood the findings of KD8CEC a new firmware does not change the stored calibration values.

The KD8CEC Memory Manager software could be used to read the original values before doing any changes.

--
PE3ES - F4VTQ - Erwin
73


--
Bob
NZ2Z

k7ome@...
 

FWIW I did make the correction to 17 meters and now it works fine.  While I was in there I took out all the CAT related code as I don't plan to use this radio with a computer and I figured that would save a little space for future enhancements.

This should probably be in a different thread but:  is there any info on the status of the Morse reader code?  Finishing that is more than I can handle but I did see that the 'F' was mis-coded as an 'L' ....

Reed N
 

Good catch on the "F", K7OME. Looks like it should be an 0xE2 instead. Best thing to do there would be to do one (or more) of the following:
a) make the fix, and create a pull request for it (best)
b) create an "issue" on github documenting the problem (decent)
c) mention it in a thread here (as you did, which is okay, but not ideal :P)


Reed

k7ome@...
 

Reed,

I'm the newest of noobs on this whole groups thing, I don't know what a pull request is or where to create one.  Pretty much the same for github.   I'm not sure its worth losing much sleep over it though because if anyone ever does get the Morse reader working that F problem will show up right away ...

Ray

Reed N
 

Ray,

I went ahead and made the issue for you just now: https://github.com/afarhan/ubitxv6/issues/4


Reed

Andy_501
 

Ditto here Ray also.

maybe once we stumble onto a basic tutorial on using Arduino coding we will get familiar enough to understand what appears now to be baffle-gab hihi

Andy

On 2020-01-06 19:58, k7ome@... wrote:
Reed,

I'm the newest of noobs on this whole groups thing, I don't know what a pull request is or where to create one.  Pretty much the same for github.   I'm not sure its worth losing much sleep over it though because if anyone ever does get the Morse reader working that F problem will show up right away ...

Ray