Date   

Re: QCX+ with speaker

ajparent1/KB1GMX
 

Trystan,

Yes the Opamp can push out a few milliwatts.  On a noisy windy location
outdoors its not enough, in my lab ok.  Helps if there is a 32 ohm to 8ohm
matching transformer, that actually helps some but not a great amount.

That and yes there are others that do no appreciate CW [what's beeping?]!

Allison
-------------------------------
Please reply on list so we can share.
No private email, it goes to a bit bucket due address harvesting


Re: QCX S/W 1.04, PCB Rev 5, 40M Band : Looking for a diagnostic insight #40m #qcx

N3MNT
 

Many time unstable readings when adjusting Pots are caused by poor connections ( insulation on wires) at T1.


Re: QCX+ with speaker

ajparent1/KB1GMX
 

Jim Netwal,

Let me help you.  The QCX plus is the same design as QCX different mechanical
layout but same circuit.  Hans has said this, maybe you didn't read it.

So that being the case it behaves exactly the same and generally the QCX is a
headphones radio.

Can the box fit a speaker, yes.  You will have to make an audio power amp up
so it can drive a speaker.  There is room enough for that too.

Allison
-------------------------------
Please reply on list so we can share.
No private email, it goes to a bit bucket due address harvesting


Re: No TX, No RX, no LCD #chat

ajparent1/KB1GMX
 

As Fred said some of the ICs use 3.3V, some 5V and a few 12-13V

Likely cause is IC11 voltage regulator in backward or a short from pins 1 to 3.
POOF, happens then.

The parts that do not like more than 5V (give or take 10%):
Microprocessor, (5V max)
SI5351 NPLL (3.3V)
FST3253 (5V)
74ACT00 (5v)

Soldering in the 5351 and FST3253 is SMT tech and if you skills are not up
to it try it, or build another as lack of SMT removal skills will generally
destroy the board..

Allison
-------------------------------
Please reply on list so we can share.
No private email, it goes to a bit bucket due address harvesting


Re: QCX S/W 1.04, PCB Rev 5, 40M Band : Looking for a diagnostic insight #40m #qcx

ajparent1/KB1GMX
 

The audio system is DC coupled so any error always start at the input and
progress to the first error point.  If the voltages are off it will not work well.

With a common every day multimeter measure the junction of R1 and R2.
It should be 2.5V (pllus or minus a small amount).

IF not make sure the right resistors were inserted and check soldering.

IF Good then test pins 7 and 9 of IC4, if the same as the first measurement (2.5V) your good.
If not solder the leads of T1.

Go to pins 2,3,5,6 if IC5, the voltages should be exactly the same to the limits of
your meter (+-1 digit).

IF good then proceed, if not check your assembly, likely soldering.

Check IC 5 pins 1 and 7 they should be the same votlage and around 2.5V.

IF not are, same dance check your work and soldering.

IF they are we can talk later.

One last thing make sure no resistors are resting against another part,
no solder whiskers causing a short.

Also make sure the Volume pot, three leads actually connect to the board!

Enough for a start.  No scope needed yet.

Allison
-------------------------------
Please reply on list so we can share.
No private email, it goes to a bit bucket due address harvesting


Re: QCX+ with speaker

Trystan G0KAY
 

As I said, "Incidentally, some miniature 2" and smaller speakers have a sweetspot (free air resonance) at 700Hz and incredibly sensitive."

In other words, you do not need an amp if you want to run an internal speaker. I'm listening to a station, on my QCX, no amp, into a 40mm speaker and I have my volume turned down a lot otherwise it would be far too loud. The QCX as it is has plenty of audio gain. 


Re: Fuse settings question

chmims <chmims@...>
 

Thanks for the info.  I ran the command and now hfuse set to 0xD1.

73 Charles KG5ZLH


QCX S/W 1.04, PCB Rev 5, 40M Band : Looking for a diagnostic insight #40m #qcx

ed.j.tink@...
 

I recently completed assembling a QCX for the 40m band and have an issue with audio amplification. Polling to see if anyone may have some advice where to specifically look.

The digital, LCD and transmit sections appear fully functional. The device draws about 110 ma at 12.13 V on receive and 470 ma at 12.09 V measured at the power supply.

For adjustment and alignment, I get two peak BPFs at 28 bars and 08 in the top left (2^8 * 28 = 7168) but the I-Q balance, Lo and Hi Phase are bouncing between 00 and 01 -- obviously in the noise level. I can hear the respective 700, 600, and 800 Hz tones but they are very, very faint at full gain.

Once (out of many power ups) the audio worked as expected. The tones were loud, I adjusted the I-Q balance and the Lo Phase to minimums (around 9 and 7 I think) but the volume dropped off again when I got to the Hi Phase adjustment.

I was very meticulous and systematic about sorting the parts, triple checking part locations and I also went through the "General checklist" in the (very well done) QCX Troubleshooting PDF. In the interim, I am trying to locate/acquire an oscilloscope in order to continue troubleshooting.

Cheers,

Ed

I have to locate an oscilloscope, however, any insights would be very much appreciated.







Re: Fuse settings question

Arv Evans
 


On Sun, May 24, 2020 at 12:59 PM Alan G4ZFQ <alan4alan@...> wrote:
>'How do I permanently change the H fuse to D1
> from D9?'

Charles

As I posted last week https://groups.io/g/QRPLabs/message/46807

##*Write fuses NOTE not normally required, only if values read are not
correct!*
C:\A>avrdude -u -c usbasp -p m328p -P usb -B 0.5 -U lfuse:w:0xF7:m -U
hfuse:w:0x
D1:m -U efuse:w:0xFC:m

Really I guess that -U hfuse... is all you need but the full command
will do no harm.

73 Alan G4ZFQ




Re: Fuse settings question

Alan G4ZFQ
 

'How do I permanently change the H fuse to D1 from D9?'
Charles

As I posted last week https://groups.io/g/QRPLabs/message/46807

##*Write fuses NOTE not normally required, only if values read are not correct!*
C:\A>avrdude -u -c usbasp -p m328p -P usb -B 0.5 -U lfuse:w:0xF7:m -U hfuse:w:0x
D1:m -U efuse:w:0xFC:m

Really I guess that -U hfuse... is all you need but the full command will do no harm.

73 Alan G4ZFQ


Re: Fuse settings question

Charles Mims <chmims@...>
 

I guess I need to rephrase my original question 'How do i prevent this from happening again?'  to 'How do I permanently change the H fuse to D1 from D9?'

Charles
KG5ZLH


On Sun, May 24, 2020 at 1:54 AM Alan G4ZFQ <alan4alan@...> wrote:
> This CQX 20 hat been been revived after using avrdude  to install
> T1.05.hex and T1.04.eep.
>
> This command  % avrdude -u -c usbasp -P usb -B 0.5 -U hfuse:r:-:h -U
> lfuse:r:-:h -U efuse:r:-:h'
> returns Fuses OK (E:FC, H:D9, L:F7

Charles,

Yes, the chip is not bricked.
But unless the H fuse is changed to D1 it will need the .eep file for
the next update.

73 Alan G4ZFQ




Re: No TX, No RX, no LCD #chat

fred.g3srf@...
 

If you do indeed have 13 volts on all IC's, then you have found your fault. You may as well just order a new kit as you will have problems replacing all the IC's that don't like excessive voltage applied and that is pretty well all of them.


Re: No TX, No RX, no LCD #chat

Bill Cromwell
 

Heh,

I did not even know there is a chat. Don't look for me there any time soon.

73,

Bill KU8H

On 5/24/20 11:40 AM, Arv Evans wrote:
"Do not reply to this message to post to the chat. You can participate in chats
only through the group's website."  seems rather restrictive and excludes those
who use an email handler and do not directly log into groups.io <http://groups.io>.
My guess is that:
1. The LCD is not being initialized due to a connection error.
2. Soldering the MCU has an error causing the MCU to stop.
3. The whole unit is dead!
There are a number of persons on this group who are very knowledgeable and
seem willing to work with you to suggest actions and solutions.  They may, or
may not, be willing to change methods and work via a chat tool.  Usually remote
troubleshooting involves time for testing, comparing, and this involving time zone
offsets.
Arv
_._
On Sun, May 24, 2020 at 8:41 AM <yannick.hariga@gmail.com <mailto:yannick.hariga@gmail.com>> wrote:
A new chat has been created:
Hey all!
After some months I tried getting my QCX ready for 20m.
Troubleshooting didn't result any positive solutions. Here, some of
the problems:
* No RF power (TX not working)
* Nothing to hear (RX not working)
* After soldering at the ATMEGA (the big one under the LCD), the
LCD just has light on but nothing is displayed
I have 13 Volts on all ICs and I do not find the problems!
I would be really glad about some help!
Thanks a lot in advance and 73s!
Yannick, DK1YH/ON1YH
View/Join This Chat <https://groups.io/g/QRPLabs/chat/6068>
Do not reply to this message to post to the chat. You can
participate in chats only through the group's website.
--
bark less - wag more


Re: No TX, No RX, no LCD #chat

yannick.hariga@...
 

Thanks guys for all those replies. 

I'll try on resolving those problems

Thank you so much
Have a nice end of the weekend!


Re: No TX, No RX, no LCD #chat

Arv Evans
 

"Do not reply to this message to post to the chat. You can participate in chats 
only through the group's website."  seems rather restrictive and excludes those 
who use an email handler and do not directly log into groups.io.  

My guess is that:
  1. The LCD is not being initialized due to a connection error.
  2. Soldering the MCU has an error causing the MCU to stop.
  3. The whole unit is dead!
There are a number of persons on this group who are very knowledgeable and 
seem willing to work with you to suggest actions and solutions.  They may, or 
may not, be willing to change methods and work via a chat tool.  Usually remote 
troubleshooting involves time for testing, comparing, and this involving time zone 
offsets.

Arv
_._




On Sun, May 24, 2020 at 8:41 AM <yannick.hariga@...> wrote:

A new chat has been created:

Hey all!

After some months I tried getting my QCX ready for 20m. Troubleshooting didn't result any positive solutions. Here, some of the problems:

  • No RF power (TX not working)
  • Nothing to hear (RX not working)
  • After soldering at the ATMEGA (the big one under the LCD), the LCD just has light on but nothing is displayed
I have 13 Volts on all ICs and I do not find the problems!

I would be really glad about some help!

Thanks a lot in advance and 73s!
Yannick, DK1YH/ON1YH

View/Join This Chat

Do not reply to this message to post to the chat. You can participate in chats only through the group's website.


Re: Fuse settings question

Arv Evans
 

Exactly!


On Sun, May 24, 2020 at 8:26 AM jjpurdum via groups.io <jjpurdum=yahoo.com@groups.io> wrote:
Jim:

How do you know the QCX is not programmed in C? Actually, there could be a Serial.begin(9600) in it for debugging purposes. I use scaffolding code all the time:

#define DEBUG
// ...a bunch of statements, then in setup()...

   #ifdef DEBUG
      Serial.begin(9600);
   #endif
// ...the rest of the sketch

When I'm debugging the code, I leave the #define for DEBUG active. When I'm done and ready for distribution, I comment out DEBUG , which means all of my calls to the Serial object are not compiled into the sketch. If I later find I missed a bug, I remove the comment characters for the DEBUG symbolic constant, recompile, and all my debug code is back in the executable without typing a single new line.

I'm pretty sure the QCX does use C and likely some assembler as well.

Jack, W8TEE

On Sunday, May 24, 2020, 9:54:29 AM EDT, James Daldry W4JED <jim@...> wrote:


Hi, Arv

The QCX is not an Arduino. The QCX is not an Arduino. The QCX is not an Arduino. Should I write it a few more times?

The QCX is not programmed in C. There has been no Serial.begin(9600) code written into it. Your "simple" string has to be written a half-byte at a time to the LCD. The code to make the comparison and goto a do-nothing loop will be probably 20 bytes. _THERE_  _ISN'T_  _20_  _BYTES_  _TO_  _SPARE_.

Jim W4JED

On 5/23/20 8:28 PM, Arv Evans wrote:

Larry

if (a != b) { Serial.println ("security code violated");
exit(1);  // product validation is simple!
}

Possibly was in the code from the time when an Ebay vendor tried to sell U3 
boards and expected QRP-Labs to support their marginal products.

Arv
_._

On Sat, May 23, 2020 at 6:02 PM Larry Howell <larry.howell.47@...> wrote:
Arv,
Any non-trivial decryption would require additional flash resources that do not exist.  I'm sure Hans is down to counting bits at this point.
Larry AC8YE

On Sat, May 23, 2020 at 7:54 PM Arv Evans <arvid.evans@...> wrote:
If I were trying to protect my proprietary software from being plagiarized
I would probably copy a key (maybe the CPU serial number) into the .eep 
file and then include code in flash memory to test for a match between 
CPU serial number and that key in the .eep space.  There are several other 
ways to do this.  Multiple tests could be done, or even encrypt the 
embedded key and test for proper decryption.  

Arv
_._


On Sat, May 23, 2020 at 5:07 PM Ham Radio <bernard.murphy@...> wrote:
The documentation on the QRP-LABS site should be updated regarding checking the HI fuse for X’D1’ for the first re-flash of the firmware.

If the HI  fuse is not correct, is the micro totally bricked or can the problem  be fixed using the  .eep file?
--
73, Bernie, VE3FWF


Re: Fuse settings question

Arv Evans
 

Jim

The QCX uses the same microcontroller as is used in an Arduino.  
The QCX is programmed in C-language.  I suspect that Hans does 
insert a few bytes of machine code as a way to make the code 
more compact, but only Hans could say yes or no to that.

Over the years I have used various means to make proprietary code 
so that it could not be copied.  There are numerous ways to do this.
Using the CPU internal serial number seems to be the most reliable,
but it also works to provide a read and comparison of some keyword 
and a compare to lock up the system if software has been copied, 
tampered with, or replaced.  It would even be possible to use the client's 
purchase number or date and encrypt this as a keyword to make the 
key client-specific.  

Agreed that the QCX is not an Arduino.  It has no bootloader, thus it 
requires that code installs use the SPI programming port bits MOSI, 
MISO, CLK, and RST. 
 
Point I was trying to make is that the QCX is not an Arduino and that 
there is more to security than simply installing a new operating system.  
Since it has no bootloader the usual bootloader process of setting 
fuses and installing .hex code does not work.  In addition I was trying 
to talk around the security method that Hans uses without giving away 
his secrets.

Arv
_._



On Sun, May 24, 2020 at 7:54 AM James Daldry W4JED <jim@...> wrote:

Hi, Arv

The QCX is not an Arduino. The QCX is not an Arduino. The QCX is not an Arduino. Should I write it a few more times?

The QCX is not programmed in C. There has been no Serial.begin(9600) code written into it. Your "simple" string has to be written a half-byte at a time to the LCD. The code to make the comparison and goto a do-nothing loop will be probably 20 bytes. _THERE_  _ISN'T_  _20_  _BYTES_  _TO_  _SPARE_.

Jim W4JED

On 5/23/20 8:28 PM, Arv Evans wrote:

Larry

if (a != b) { Serial.println ("security code violated");
exit(1);  // product validation is simple!
}

Possibly was in the code from the time when an Ebay vendor tried to sell U3 
boards and expected QRP-Labs to support their marginal products.

Arv
_._

On Sat, May 23, 2020 at 6:02 PM Larry Howell <larry.howell.47@...> wrote:
Arv,
Any non-trivial decryption would require additional flash resources that do not exist.  I'm sure Hans is down to counting bits at this point.
Larry AC8YE

On Sat, May 23, 2020 at 7:54 PM Arv Evans <arvid.evans@...> wrote:
If I were trying to protect my proprietary software from being plagiarized
I would probably copy a key (maybe the CPU serial number) into the .eep 
file and then include code in flash memory to test for a match between 
CPU serial number and that key in the .eep space.  There are several other 
ways to do this.  Multiple tests could be done, or even encrypt the 
embedded key and test for proper decryption.  

Arv
_._


On Sat, May 23, 2020 at 5:07 PM Ham Radio <bernard.murphy@...> wrote:
The documentation on the QRP-LABS site should be updated regarding checking the HI fuse for X’D1’ for the first re-flash of the firmware.

If the HI  fuse is not correct, is the micro totally bricked or can the problem  be fixed using the  .eep file?
--
73, Bernie, VE3FWF


Re: No TX, No RX, no LCD #chat

@CurtisM
 

Yannick

There is a potentiometer near the display, it must be carefully adjusted to get characters onto the display. That is needed to make adjustments for the rig.
Beyond this the rig has hundreds of solder connections. I had no receive, but using the test generator and my fingers I found a solder joint I missed. First you need a display, after the pot check each display solder connection, and same for control IC. Reflow them if you see nothing suspicious.

Curt


Re: No TX, No RX, no LCD #chat

N3MNT
 

Replying here so it may help others as well.
If you have 13V on your IC that is your issue.  Start with the 5V regulator.  If you do not have 5V on the output of the regulator nothing will work.  If you do actually have 13V on the pwr pin of all the ICs, you may have also damaged them.


Re: No TX, No RX, no LCD #chat

George Korper
 

Hi Yannick,
Welcome aboard.

Please do this next, go to:
https://www.qrp-labs.com/qcx/qcxtrouble.html

Then if that doesn't help, you need to start checking all the voltages
suggested in the manual. 

Since you didn't mention any smoke, that is a good thing. I wouldn't turn it on again
without a current limited supply or a fuse, and without a dummy load. 

Then it is just a painstaking process, but you will have a lot of information to bring back here. 

Good luck,
George
K3GK