Date   
Re: Known issues on uBITX r4 #ubitx

hirosmb JAZZ <hirosmb@...>
 

Yes, you are right, Raj.

I’ll set up the uBITX as it comes at first.

My only concern was if I need to solder or mod at my first setting-up bcoz v4 is rather new design, I’ll easily get confused what I do is ok or not.

Thanks for ur advice, Raj.

// hiro, JJ1FXF



2018/06/29 17:07、Raj vu2zap <@Raj>のメール:

Hiro,

First connect up the board and get it working in stock condition and when all is
well and running look for mods that you may want to try.

I have posted the audio distortion fix just now. Its very simple to do.

Raj

At 29-06-18, you wrote:
Hi, all.

I’m really new to uBITX and planning to place my order to hfsignals.com very soon.

Then please share its known hardware issues of uBITX r4 that I need to modify or solder.

Thanks in advance and hope to QSO with my uBITX soon.

// hiro, JJ1FXF


Re: Known issues on uBITX r4 #ubitx

 

Hiro,

First connect up the board and get it working in stock condition and when all is
well and running look for mods that you may want to try.

I have posted the audio distortion fix just now. Its very simple to do.

Raj

At 29-06-18, you wrote:
Hi, all.

Im really new to uBITX and planning to place my order to hfsignals.com very soon.

Then please share its known hardware issues of uBITX r4 that I need to modify or solder.

Thanks in advance and hope to QSO with my uBITX soon.

// hiro, JJ1FXF

uBitxr4 audio distortion fix

 

Got back to town and plugged in the uBitxr4 and found the audio distorted.

Poking around the finals I found that the two diodes D15 and D16 gave only a drop of 1.2V total
but the final transistors needed more like 1.5V. i.e. 0.75v each.

I simply cut the track between D5 and D16 and soldered a 100 ohms multiturn preset as shown
in picture below. (Preset leads used is center and one side)

Start with the two soldered connections of the preset set to ZERO ohms.

Power on and tune to a station at low volume and slowly increase the preset till the audio
becomes clear. In my board the RX power consumption increased by 25mA at the best sound.
Just check and see that the output transistors are not getting hot.

My board sounded great with 47 Ohms between D15 D16 and I run at 13.6V. If you run at the
same supply voltage then you can try a fixed resistor. For 12V supply you could try a higher value
like 56/62 or even 68 Ohms.

Cheers

--
Raj, vu2zap
Bengaluru, South India.

Emacs!

Re: Known issues on uBITX r4 #ubitx

hirosmb JAZZ <hirosmb@...>
 

Many, many thanks for ur comments, Andy.

Now I understand that either a cheap speaker or bypassing built-in amp is the solution of the synchronized noise issue.

Since this fix isn’t hard one for me, now I’m placing my order sooner.

Again, thanks, Andy.

// hiro, JJ1FXF



2018/06/29 15:49、Andy V. Borisenko via Groups.Io <rw9rn@...>のメール:

in the message #52671 solution a problem:
"gentlemen, the question is closed.
I connected the cheapest computer speakers with a built-in amplifier and sent a signal to them bypassing the amplifier uBitx.
I got a good audio.
and "A re-setting of the BFO should fix this" did not have to do with it.
You just need not use the audio amplifier in uBitx. he is no good at all.
for me it's a fact!I previously wrote about problems with the audio amplifier v4.
I will build and instal in uBitx a wonderful audio filter and audio amplifier QCX from QRP-Labs.
best regards to all!
Andy V. Borisenko RW9RN"
#52684
"Farhan has an engineering error in the audio amplifier. I do not speak English well enough to explain this in detail. I will say simply: do not use the built-in amplifier in this form. It's easier and cheaper to signal bypass, to an external audio amplifier. this can be done by sending a signal from the yellow (signal) through the condenser 47-100 microfarad and green (ground), to an external audio amplifier."

Re: Known issues on uBITX r4 #ubitx

Andy V. Borisenko
 

in the message #52671 solution a problem:
"gentlemen, the question is closed.
I connected the cheapest computer speakers with a built-in amplifier and sent a signal to them bypassing the amplifier uBitx.
I got a good audio.
and "A re-setting of the BFO should fix this" did not have to do with it.
You just need not use the audio amplifier in uBitx. he is no good at all.
for me it's a fact!I previously wrote about problems with the audio amplifier v4.
I will build and instal in uBitx a wonderful audio filter and audio amplifier QCX from QRP-Labs.
best regards to all!
Andy V. Borisenko RW9RN"
#52684
"Farhan has an engineering error in the audio amplifier. I do not speak English well enough to explain this in detail. I will say simply: do not use the built-in amplifier in this form. It's easier and cheaper to signal bypass, to an external audio amplifier. this can be done by sending a signal from the yellow (signal) through the condenser 47-100 microfarad and green (ground), to an external audio amplifier."

Re: Known issues on uBITX r4 #ubitx

Andy V. Borisenko
 

I want to say that synchronized noise is a problem with an audio amplifier  v4.
tonight I will try to make a video where the built-in audio amplifier is turned off, and the sound goes through an external amplifier.

Re: Known issues on uBITX r4 #ubitx

hirosmb JAZZ <hirosmb@...>
 

Very much appreciated, Andy.

I’d like to compare its before/after.

What do u mean by “no problem of audio”?

Do u mean to say the synchronized noise is the spec of uBITX?

// hiro, JJ1FXF



2018/06/29 15:03、Andy V. Borisenko via Groups.Io <rw9rn@...>のメール:

Hiro
if necessary, I can shoot the video with an external (bypassing the built-in) audio amplifier.
but believe me, there is no problem with audio.

Re: Known issues on uBITX r4 #ubitx

Andy V. Borisenko
 

Hiro
if necessary, I can shoot the video with an external (bypassing the built-in) audio amplifier.
but believe me, there is no problem with audio.

Re: Known issues on uBITX r4 #ubitx

hirosmb JAZZ <hirosmb@...>
 

Do all of the v4 have this distortion issue? Or  only for the certain lots?

Thanks, Andy.

Ur videos helped me to understand what the distortion issue is like.

// hiro, JJ1FXF



2018/06/29 14:47、Andy V. Borisenko via Groups.Io <rw9rn@...>のメール:

I have  v4.
big problems with sound.
if you bypass the built-in audio amplifier, then you can use it.

Re: Known issues on uBITX r4 #ubitx

Andy V. Borisenko
 

I have  v4.
big problems with sound.
if you bypass the built-in audio amplifier, then you can use it.

Re: Known issues on uBITX r4 #ubitx

hirosmb JAZZ <hirosmb@...>
 

IC. I’ll pay my attention to this distorted audio issue for a while.

Any other known hardware problems on uBITX r4, the latest board?

Many thanks, MVS.

// hiro


2018/06/29 13:35、Mvs Sarma <mvssarma@...>のメール:

There are few members who reported  the good functioning of Audio amplifier.
 we need to check whether the element is wrong in design or some pieces went  out with distorted output.


Regards
MVS Sarma
 

On Fri, Jun 29, 2018 at 9:44 AM, hirosmb JAZZ <hirosmb@...> wrote:
Jack,

Thanks for ur quick reply.

I read some articles of mods, but couldn’t recognize which are necessary mods for uBITX r4 board.

Does the r4 board still need to be fixed for the distortion issue?

// hiro



2018/06/29 12:38、Jack Purdum via Groups.Io <jjpurdum@...>のメール:

Most of the mods that have been made are summarized at: ubitx.net

Jack, W8TEE

On Thursday, June 28, 2018, 11:31:43 PM EDT, <hirosmb@...> wrote:


Hi, all.

I’m really new to uBITX and planning to place my order to hfsignals.com very soon.

Then please share its known hardware issues of uBITX r4 that I need to modify or solder.

Thanks in advance and hope to QSO with my uBITX soon.

// hiro, JJ1FXF


Re: Known issues on uBITX r4 #ubitx

MVS Sarma
 

There are few members who reported  the good functioning of Audio amplifier.
 we need to check whether the element is wrong in design or some pieces went  out with distorted output.


Regards
MVS Sarma
 

On Fri, Jun 29, 2018 at 9:44 AM, hirosmb JAZZ <hirosmb@...> wrote:
Jack,

Thanks for ur quick reply.

I read some articles of mods, but couldn’t recognize which are necessary mods for uBITX r4 board.

Does the r4 board still need to be fixed for the distortion issue?

// hiro



2018/06/29 12:38、Jack Purdum via Groups.Io <jjpurdum@...>のメール:

Most of the mods that have been made are summarized at: ubitx.net

Jack, W8TEE

On Thursday, June 28, 2018, 11:31:43 PM EDT, <hirosmb@...> wrote:


Hi, all.

I’m really new to uBITX and planning to place my order to hfsignals.com very soon.

Then please share its known hardware issues of uBITX r4 that I need to modify or solder.

Thanks in advance and hope to QSO with my uBITX soon.

// hiro, JJ1FXF


Re: Noise Burst #bitx40

John
 

Installed raduino v1.27.1 and it works fine. No RF noise burst on transmit. Great piece of software Allard. 
Now looking to do more hacks of the hardware to take full advantage of the software features.
73
--
John VK6JAH

Re: Known issues on uBITX r4 #ubitx

hirosmb@...
 

Jack,

Thanks for ur quick reply.

I read some articles of mods, but couldn’t recognize which are necessary mods for uBITX r4 board.

Does the r4 board still need to be fixed for the distortion issue?

// hiro



2018/06/29 12:38、Jack Purdum via Groups.Io <jjpurdum@...>のメール:

Most of the mods that have been made are summarized at: ubitx.net

Jack, W8TEE

On Thursday, June 28, 2018, 11:31:43 PM EDT, <hirosmb@...> wrote:


Hi, all.

I’m really new to uBITX and planning to place my order to hfsignals.com very soon.

Then please share its known hardware issues of uBITX r4 that I need to modify or solder.

Thanks in advance and hope to QSO with my uBITX soon.

// hiro, JJ1FXF

Re: Enclosure #parts

Bill Watkins
 

http://www.contextengineering.com/

Re: Known issues on uBITX r4 #ubitx

Jack, W8TEE
 

Most of the mods that have been made are summarized at: ubitx.net

Jack, W8TEE

On Thursday, June 28, 2018, 11:31:43 PM EDT, <hirosmb@...> wrote:


Hi, all.

I’m really new to uBITX and planning to place my order to hfsignals.com very soon.

Then please share its known hardware issues of uBITX r4 that I need to modify or solder.

Thanks in advance and hope to QSO with my uBITX soon.

// hiro, JJ1FXF

Known issues on uBITX r4 #ubitx

hirosmb@...
 

Hi, all.

I’m really new to uBITX and planning to place my order to hfsignals.com very soon.

Then please share its known hardware issues of uBITX r4 that I need to modify or solder.

Thanks in advance and hope to QSO with my uBITX soon.

// hiro, JJ1FXF

Compiler warnings

Jack, W8TEE
 

All:

Several people have asked about compiler warnings they are getting, like:

        warning: ISO C++ forbids converting a string constant to 'char*'

A variation on this are the "deprecated" warnings issued by the compiler. Even more confusing is the fact that the warnings they now see were not there before. Usually, this is because of a compiler update. As a general rule, compiler warnings do not prevent the compile from finishing or performing an upload. However, warnings mean something is bending the rules. For anyone who might be interested, this was my answer to one of those people.


Steve:

I think everyone understands what a syntax error is: Not following the rules of the language. Semantic errors are more difficult because the rules are followed, but the context is wrong. For example, we know an English sentence needs a noun and a verb...those are the rules. However, if I say: "The dog meowed.", it obeys the syntax rules, but the semantics are out of context. I'm not sure how far back, but around version 1.65 the GCC compiler started performing some syntax and semantic checking at the "lint" level. My company produced a C compiler back in the '80's and we had a "picky flag" that could be set from 0 to 10. It performed syntax and semantic checks at increasing stringent levels. I never saw any published C code that passed our Picky Level 10. Indeed, that level was so intrusive that we never used it. Most work was done at Picky Level 4. When we were ready for distribution, we cranked it up to level 10. Truth be told, we still didn't bother to fix some of the warnings. Somewhere between 1.65 and 1.85 they kicked the GCC compiler's equivalent of our Picky Flag up a notch, hence warnings now where none existed before. That's a good thing.

However, the bad thing is that there are now a lot of warnings that unnecessarily cause people concern. Even worse, a lot of it comes from libraries, which is NOT your responsibility to fix. The library writer should fix those. When I first compiled the µBITX code, I had probably a hundred such warnings, mainly because I insisted on using only one INO file, making all the other CPP files (plus a header). True, it was a pain in the butt to fix all the warnings, but it was worth it. Why? First, by not using multiple INO files, the compiler cannot perform data type checking. You'd be surprised by how many bugs hide under the blanket of missing type checking. Second, because the compiler no longer has to glom all the source files into one huge file to compile it, it allows the GCC to perform incremental compiles. This is a HUGE win. When I compile the JackAl code for the first time in the morning, it must recompile all files. In the process, it clears the "dirty flag" for each source file. Even with my 8-core, 3.7GHz machine with a mega-munch of memory, the JackAl code takes almost 2 minutes to compile. If I used all INO files, it would always take 2 minutes to compile the source code regardless of how many file changes I made. With incremental compiles, it sets the dirty flag and recompiles only those files that have changed since the last compile. This drops my compile time (on a single-file change) to about 5 seconds. Given that I might do 30-50 compiles a day, you do the math

Kind of a long answer, but it's important that you understand what's going on "under the hood" from time-to-time. Usually, compiler warnings can be ignored, but always keep in mind it still means the compiler saw something it didn't like.

Jack, W8TEE

On Thursday, June 28, 2018, 7:13:32 PM EDT, Steve Smith <steve@...> wrote:


thanks - I erased the EPROM and then calibrated and I am getting real results. These were new part so I am not sure how the EPROM would have had values, but the first few times we loaded the software we did not have an SD card in. Could that have affected it?

Also, thanks for the explanation of the warnings, Jack. I am running version 1.85 of the Arduino IDE on Windows 10. Is there a reason some folks get the warnings and others don't? Is it a setting in the IDE?

73s

Steve

Re: Finished building my uBitX!

Don Stewart
 

Re: RFI from uBitx TX after AGC and other mods installed

Mark M
 

After I sent this it dawned on me to check the 12v supply as well. Sure enough, it's there too. FWIW, I'm powering it off a 20A Astron 13.8v linear power supply and feeding it into my old Heathkit Cantenna dummy load.

I have it installed in one of the amateurradiokits.in cases. The power wiring runs very close to the antenna connection and the final amp transistors. I tried twisting the wires tightly but it didn't make any difference.

If I disconnect the final amp supply line it goes away and there's no noise from the speaker with the AGC board in place.

Anyway, a couple more observations...

Mark AA7TA

On 6/28/18 5:07 PM, Mark M wrote:
Don...
I finally had a chance to start looking into this on my ubitx (I'm seeing the same issue). I managed to borrow a scope and putting it on the 5v supply seems to indicate that you're right. I see up to about 40 mv p-t-p on the 5v line when xmitting SSB with the AGC board not connected at all. It's pretty clean in receive. I'm tapping into the 5v line on the raduino. So that certainly looks like the smoking gun.
Now to figure out how it's getting in there...
Hope this helps...
Mark     AA7TA