Ok,
QMX+ just arrived in Italy,? Monday2Monday with a bank holiday between, not bad. I have the full package so I will start assembling the dummy load and GPS? but I wanted to setup the testbed too.
Now, any suggestion to get rid of relays to interface power supply switching on off , encoders, paddle and all? Any quick schematic with MOSfets? I am mostly a digital guy.
Drive will be 3.3V logic (teensy or AmicaNode MCU v2).
TIA
Giuseppe Marullo IW2JWW - JN45RQ
|
Giuseppe, your query is a bit confusing.? What kind of "burn in" testing are you thinking of doing?? It does not really need a full set of automated burn-in testing.
Note that you can't power-on the QMX+ by externally manipulating the power, you need to physically press the "on" button - unless you also 'hack' leads from the QMX encoder switch to an externally controlled switch.? Is this what you want to do??
Stan
|
Stan,
Giuseppe isn’t doing burn-in testing, he’s doing stress testing by interrupting the battery supply at millisecond intervals as well as the paddle and mic inputs I believe. He’s investigating the effects of unwanted interruptions that are suspected of causing various failures. Normal power on/off is not part of his test process.
Tony
toggle quoted message
Show quoted text
Giuseppe, your query is a bit confusing.? What kind of "burn in" testing are you thinking of doing?? It does not really need a full set of automated burn-in testing.
Note that you can't power-on the QMX+ by externally manipulating the power, you need to physically press the "on" button - unless you also 'hack' leads from the QMX encoder switch to an externally controlled switch.? Is this what you want to do??
Stan
|
Sorry Stan,
I would like to control the power externally, provide and cut
power in a automated way through the activation of a relay. I was
thinking to substitute the relay with a "power" mosfet and that
where I need some quick example for something easy to procure
using usual Digikey or Mouse (better Digikey for me, to Italy no
shipping charges over 50EUR if I remember well).
I would also mimic the encoder's operation with some relays, and
again if I could do using some mosfets driven by 3.3v logic and
possibly optocouplers.
I would start easy and see how difficult it gets to add different
test cases.
Hope it is more clear.
Giuseppe Marullo
IW2JWW - JN45RQ
On 11/5/2024 12:27 AM, Stan Dye wrote:
toggle quoted message
Show quoted text
Giuseppe, your query is a bit confusing.? What kind of "burn
in" testing are you thinking of doing?? It does not really need
a full set of automated burn-in testing.
Note that you can't power-on the QMX+ by externally
manipulating the power, you need to physically press the "on"
button - unless you also 'hack' leads from the QMX encoder
switch to an externally controlled switch.? Is this what you
want to do??
Stan
|
Tony,
> by interrupting the battery supply at millisecond intervals
ms is a bit "optimistic" with a relay, but I will see what I can
do. Fastest thing I have is an Artix? (300+MHz) but I don't want
to play with that, hope it is not needed.
>mic inputs I believe
No mic unless you know something about Hans...nah don't even think
about it.
Let's stick with Amica 8266 something, or Teensy.
Teensy is faster and has several 10bit ADC no wifi, just
ethernet. Amica is cheaper with only 1 ADC no ethernet BUT wifi.
I am interested in interrupting the power while performing
several tasks, it will depend how deep will be this rabbit hole.
Should I find something (magic smoke) I would quickly cash the
offer of Hans and possibly he will carry on these kind of tests
from there.
Else, we could have some degree of assurance that some abuse
could be well tolerated.
>Giuseppe isn’t doing burn-in testing, he’s doing stress
testing
Sorry about the burn-in testing definition, but I don't know how
to define it, in a way is like when you "cook" a high end audio
amplifier for 48h and triple check every thing works as it should.
Stress to me is when you push something near or over the limit
(like when you hammer some IT stuff with a IXIA or Spirent), I am
not.
I expect every radio I own pass with flying colors if I pull the
plug (and this could cause micro interruptions to a degree), no
matter what.
Of course, not 1000 times a second, I would like to simulate what
happens when you trip into a power cord and the radio is doing
something (or nothing).
Any recommendations for DC current monitoring to feed a 3.3V 10
bit ADC?
Giuseppe Marullo
IW2JWW - JN45RQ
On 11/5/2024 12:52 AM, Tony Scaminaci
wrote:
toggle quoted message
Show quoted text
Stan,
Giuseppe isn’t doing burn-in testing, he’s doing
stress testing by interrupting the battery supply at millisecond
intervals as well as the paddle and mic inputs I believe. He’s
investigating the effects of unwanted interruptions that are
suspected of causing various failures. Normal power on/off is
not part of his test process.
Tony
Giuseppe, your query is a bit confusing.? What kind of
"burn in" testing are you thinking of doing?? It does not
really need a full set of automated burn-in testing.
Note that you can't power-on the QMX+ by externally
manipulating the power, you need to physically press the
"on" button - unless you also 'hack' leads from the QMX
encoder switch to an externally controlled switch.? Is
this what you want to do??
Stan
|
Hi Giuseppe,
Why not start out by wiggling the power plug by hand during receive and then during transmit? There have been a few reports of momentary power interruptions causing failures. Another simple test would be to just pull the power plug out during receive and then during transmit. If none of these simple tests causes a failure, then you could move on to more sophisticated testing apparatus.
Relay contacts do bounce which would mimic a user inadvertently hitting the power connector and causing a momentary interruption.?
Tony On Mon, Nov 4, 2024 at 6:48?PM Giuseppe Marullo[iw2jww] via <giuseppe= [email protected]> wrote:
toggle quoted message
Show quoted text
Tony,
> by interrupting the battery supply at millisecond intervals
ms is a bit "optimistic" with a relay, but I will see what I can
do. Fastest thing I have is an Artix? (300+MHz) but I don't want
to play with that, hope it is not needed.
>mic inputs I believe
No mic unless you know something about Hans...nah don't even think
about it.
Let's stick with Amica 8266 something, or Teensy.
Teensy is faster and has several 10bit ADC no wifi, just
ethernet. Amica is cheaper with only 1 ADC no ethernet BUT wifi.
I am interested in interrupting the power while performing
several tasks, it will depend how deep will be this rabbit hole.
Should I find something (magic smoke) I would quickly cash the
offer of Hans and possibly he will carry on these kind of tests
from there.
Else, we could have some degree of assurance that some abuse
could be well tolerated.
>Giuseppe isn’t doing burn-in testing, he’s doing stress
testing
Sorry about the burn-in testing definition, but I don't know how
to define it, in a way is like when you "cook" a high end audio
amplifier for 48h and triple check every thing works as it should.
Stress to me is when you push something near or over the limit
(like when you hammer some IT stuff with a IXIA or Spirent), I am
not.
I expect every radio I own pass with flying colors if I pull the
plug (and this could cause micro interruptions to a degree), no
matter what.
Of course, not 1000 times a second, I would like to simulate what
happens when you trip into a power cord and the radio is doing
something (or nothing).
Any recommendations for DC current monitoring to feed a 3.3V 10
bit ADC?
Giuseppe Marullo
IW2JWW - JN45RQ
On 11/5/2024 12:52 AM, Tony Scaminaci
wrote:
Stan,
Giuseppe isn’t doing burn-in testing, he’s doing
stress testing by interrupting the battery supply at millisecond
intervals as well as the paddle and mic inputs I believe. He’s
investigating the effects of unwanted interruptions that are
suspected of causing various failures. Normal power on/off is
not part of his test process.
Tony
Giuseppe, your query is a bit confusing.? What kind of
"burn in" testing are you thinking of doing?? It does not
really need a full set of automated burn-in testing.
Note that you can't power-on the QMX+ by externally
manipulating the power, you need to physically press the
"on" button - unless you also 'hack' leads from the QMX
encoder switch to an externally controlled switch.? Is
this what you want to do??
Stan
|
In my mind, what you want to do is better described as resiliency testing. Can QMX survive normal user abuse? For example, there have been reports of the rig locking up and becoming unresponsive, forcing the user to pull the power without the normal controlled shutdown. We know that any configuration changes made by the user would be lost since changes are only saved during the normal shutdown process. However, could this emergency power cycle subsequently cause any other issues at the next power up?
Also, there are theories floating around about the 1 ms SMPS correction rate being too slow to respond to momentary power glitches. So some of your testing would involve interrupting the power in the multiple ms range. Switches tend to bounce for at least a few ms although I’ve witnessed bouncing as long as 20 ms. Can the SMPS algorithm correctly respond to switch bounce conditions without any damage??
Tony
toggle quoted message
Show quoted text
On Mon, Nov 4, 2024 at 7:47?PM Tony Scaminaci via <tonyscam= [email protected]> wrote: Hi Giuseppe,
Why not start out by wiggling the power plug by hand during receive and then during transmit? There have been a few reports of momentary power interruptions causing failures. Another simple test would be to just pull the power plug out during receive and then during transmit. If none of these simple tests causes a failure, then you could move on to more sophisticated testing apparatus.
Relay contacts do bounce which would mimic a user inadvertently hitting the power connector and causing a momentary interruption.?
Tony On Mon, Nov 4, 2024 at 6:48?PM Giuseppe Marullo[iw2jww] via <giuseppe= [email protected]> wrote:
Tony,
> by interrupting the battery supply at millisecond intervals
ms is a bit "optimistic" with a relay, but I will see what I can
do. Fastest thing I have is an Artix? (300+MHz) but I don't want
to play with that, hope it is not needed.
>mic inputs I believe
No mic unless you know something about Hans...nah don't even think
about it.
Let's stick with Amica 8266 something, or Teensy.
Teensy is faster and has several 10bit ADC no wifi, just
ethernet. Amica is cheaper with only 1 ADC no ethernet BUT wifi.
I am interested in interrupting the power while performing
several tasks, it will depend how deep will be this rabbit hole.
Should I find something (magic smoke) I would quickly cash the
offer of Hans and possibly he will carry on these kind of tests
from there.
Else, we could have some degree of assurance that some abuse
could be well tolerated.
>Giuseppe isn’t doing burn-in testing, he’s doing stress
testing
Sorry about the burn-in testing definition, but I don't know how
to define it, in a way is like when you "cook" a high end audio
amplifier for 48h and triple check every thing works as it should.
Stress to me is when you push something near or over the limit
(like when you hammer some IT stuff with a IXIA or Spirent), I am
not.
I expect every radio I own pass with flying colors if I pull the
plug (and this could cause micro interruptions to a degree), no
matter what.
Of course, not 1000 times a second, I would like to simulate what
happens when you trip into a power cord and the radio is doing
something (or nothing).
Any recommendations for DC current monitoring to feed a 3.3V 10
bit ADC?
Giuseppe Marullo
IW2JWW - JN45RQ
On 11/5/2024 12:52 AM, Tony Scaminaci
wrote:
Stan,
Giuseppe isn’t doing burn-in testing, he’s doing
stress testing by interrupting the battery supply at millisecond
intervals as well as the paddle and mic inputs I believe. He’s
investigating the effects of unwanted interruptions that are
suspected of causing various failures. Normal power on/off is
not part of his test process.
Tony
Giuseppe, your query is a bit confusing.? What kind of
"burn in" testing are you thinking of doing?? It does not
really need a full set of automated burn-in testing.
Note that you can't power-on the QMX+ by externally
manipulating the power, you need to physically press the
"on" button - unless you also 'hack' leads from the QMX
encoder switch to an externally controlled switch.? Is
this what you want to do??
Stan
|
Yes of course but, then?
If I pull by hand it would not be reproducible, I could have a very bad style pulling the plug, being always lucky and another ham could ha a completely different experience. Everythime it would be different and I will break something mechanically. Probably is better to capture what really happens with a DSO on the power socket of a QMX+ simulating the load when in rx and in tx for the first ms. Then I could think what pulling the plug could be for a QMX and see if I could reproduce it with my hw.
>Relay contacts do bounce which would mimic a user inadvertently hitting the power connector and causing a momentary interruption. Sure but they looks similar? I don't know, but mosfets could be better, faster and no bouncing. Or not?
Giuseppe Marullo IW2JWW - JN45RQ
Tony
toggle quoted message
Show quoted text
On November 5, 2024 2:46:57 AM GMT+01:00, Tony Scaminaci <tonyscam@...> wrote:
Hi Giuseppe,
Why not start out by wiggling the power plug by hand during receive and then during transmit? There have been a few reports of momentary power interruptions causing failures. Another simple test would be to just pull the power plug out during receive and then during transmit. If none of these simple tests causes a failure, then you could move on to more sophisticated testing apparatus.
Relay contacts do bounce which would mimic a user inadvertently hitting the power connector and causing a momentary interruption.?
Tony On Mon, Nov 4, 2024 at 6:48?PM Giuseppe Marullo[iw2jww] via <giuseppe= [email protected]> wrote:
Tony,
> by interrupting the battery supply at millisecond intervals
ms is a bit "optimistic" with a relay, but I will see what I can
do. Fastest thing I have is an Artix? (300+MHz) but I don't want
to play with that, hope it is not needed.
>mic inputs I believe
No mic unless you know something about Hans...nah don't even think
about it.
Let's stick with Amica 8266 something, or Teensy.
Teensy is faster and has several 10bit ADC no wifi, just
ethernet. Amica is cheaper with only 1 ADC no ethernet BUT wifi.
I am interested in interrupting the power while performing
several tasks, it will depend how deep will be this rabbit hole.
Should I find something (magic smoke) I would quickly cash the
offer of Hans and possibly he will carry on these kind of tests
from there.
Else, we could have some degree of assurance that some abuse
could be well tolerated.
>Giuseppe isn’t doing burn-in testing, he’s doing stress
testing
Sorry about the burn-in testing definition, but I don't know how
to define it, in a way is like when you "cook" a high end audio
amplifier for 48h and triple check every thing works as it should.
Stress to me is when you push something near or over the limit
(like when you hammer some IT stuff with a IXIA or Spirent), I am
not.
I expect every radio I own pass with flying colors if I pull the
plug (and this could cause micro interruptions to a degree), no
matter what.
Of course, not 1000 times a second, I would like to simulate what
happens when you trip into a power cord and the radio is doing
something (or nothing).
Any recommendations for DC current monitoring to feed a 3.3V 10
bit ADC?
Giuseppe Marullo
IW2JWW - JN45RQ
On 11/5/2024 12:52 AM, Tony Scaminaci
wrote:
Stan,
Giuseppe isn’t doing burn-in testing, he’s doing
stress testing by interrupting the battery supply at millisecond
intervals as well as the paddle and mic inputs I believe. He’s
investigating the effects of unwanted interruptions that are
suspected of causing various failures. Normal power on/off is
not part of his test process.
Tony
Giuseppe, your query is a bit confusing.? What kind of
"burn in" testing are you thinking of doing?? It does not
really need a full set of automated burn-in testing.
Note that you can't power-on the QMX+ by externally
manipulating the power, you need to physically press the
"on" button - unless you also 'hack' leads from the QMX
encoder switch to an externally controlled switch.? Is
this what you want to do??
Stan
|
Yes, I agree that using a FET driven by an audio generator would be reproducible. You could use an audio frequency generator starting at 1 Hz and increment the frequency in 1 Hz steps provided that you can automatically stop the test when a failure occurs at some frequency. The question is, how would you detect a failure and immediately terminate the frequency increments? We don’t know what the failure modes are so what would you measure?
It would be interesting to correlate a specific pulse frequency to a specific failure.
Tony? On Mon, Nov 4, 2024 at 8:09?PM Giuseppe Marullo[iw2jww] via <giuseppe= [email protected]> wrote:
toggle quoted message
Show quoted text
Yes of course but, then?
If I pull by hand it would not be reproducible, I could have a very bad style pulling the plug, being always lucky and another ham could ha a completely different experience. Everythime it would be different and I will break something mechanically. Probably is better to capture what really happens with a DSO on the power socket of a QMX+ simulating the load when in rx and in tx for the first ms. Then I could think what pulling the plug could be for a QMX and see if I could reproduce it with my hw.
>Relay contacts do bounce which would mimic a user inadvertently hitting the power connector and causing a momentary interruption. Sure but they looks similar? I don't know, but mosfets could be better, faster and no bouncing. Or not?
Giuseppe Marullo IW2JWW - JN45RQ
Tony
On November 5, 2024 2:46:57 AM GMT+01:00, Tony Scaminaci < tonyscam@...> wrote:
Hi Giuseppe,
Why not start out by wiggling the power plug by hand during receive and then during transmit? There have been a few reports of momentary power interruptions causing failures. Another simple test would be to just pull the power plug out during receive and then during transmit. If none of these simple tests causes a failure, then you could move on to more sophisticated testing apparatus.
Relay contacts do bounce which would mimic a user inadvertently hitting the power connector and causing a momentary interruption.?
Tony On Mon, Nov 4, 2024 at 6:48?PM Giuseppe Marullo[iw2jww] via <giuseppe= [email protected]> wrote:
Tony,
> by interrupting the battery supply at millisecond intervals
ms is a bit "optimistic" with a relay, but I will see what I can
do. Fastest thing I have is an Artix? (300+MHz) but I don't want
to play with that, hope it is not needed.
>mic inputs I believe
No mic unless you know something about Hans...nah don't even think
about it.
Let's stick with Amica 8266 something, or Teensy.
Teensy is faster and has several 10bit ADC no wifi, just
ethernet. Amica is cheaper with only 1 ADC no ethernet BUT wifi.
I am interested in interrupting the power while performing
several tasks, it will depend how deep will be this rabbit hole.
Should I find something (magic smoke) I would quickly cash the
offer of Hans and possibly he will carry on these kind of tests
from there.
Else, we could have some degree of assurance that some abuse
could be well tolerated.
>Giuseppe isn’t doing burn-in testing, he’s doing stress
testing
Sorry about the burn-in testing definition, but I don't know how
to define it, in a way is like when you "cook" a high end audio
amplifier for 48h and triple check every thing works as it should.
Stress to me is when you push something near or over the limit
(like when you hammer some IT stuff with a IXIA or Spirent), I am
not.
I expect every radio I own pass with flying colors if I pull the
plug (and this could cause micro interruptions to a degree), no
matter what.
Of course, not 1000 times a second, I would like to simulate what
happens when you trip into a power cord and the radio is doing
something (or nothing).
Any recommendations for DC current monitoring to feed a 3.3V 10
bit ADC?
Giuseppe Marullo
IW2JWW - JN45RQ
On 11/5/2024 12:52 AM, Tony Scaminaci
wrote:
Stan,
Giuseppe isn’t doing burn-in testing, he’s doing
stress testing by interrupting the battery supply at millisecond
intervals as well as the paddle and mic inputs I believe. He’s
investigating the effects of unwanted interruptions that are
suspected of causing various failures. Normal power on/off is
not part of his test process.
Tony
Giuseppe, your query is a bit confusing.? What kind of
"burn in" testing are you thinking of doing?? It does not
really need a full set of automated burn-in testing.
Note that you can't power-on the QMX+ by externally
manipulating the power, you need to physically press the
"on" button - unless you also 'hack' leads from the QMX
encoder switch to an externally controlled switch.? Is
this what you want to do??
Stan
|
Hi Tony,
>The question is, how would you detect a failure and
immediately terminate the frequency increments?
You don't. I could setup a screen recording where? I see some
serial terminals (or a little application) that dumps what I am
doing: date/time and how I drive the power, plus a webcam with the
display of the QMX+ and/or maybe a dump from the SWR meter (from a
serial port).
After the test is complete, I could see if the magic smoke is
still there, and if not I will get pop-corns and enjoy the movie.
IF you really want to be badass, you could recognize when the LCD
screen goes south (and/or when it stops responding to encoders)
and stop the test. You can youse Sikuli, OpenCV or whatever floats
your boat:
Enjoy, I did a lot of BAD stuff with this kind of tools.
Word of caution: it can become addictive BUT don't try to get
illegal copies of paid tools, one example for all: Macro
Scheduler.
Stick to Sikuli X, Auto Hot Key, OpenCV or similar that are not
commercial (a lot of what you find online cracked is dangerous).
Before you ask: Yes, it can operate FT8 better than you, LOL.
Giuseppe Marullo
IW2JWW - JN45RQ
|
Please forgive it, if this is a silly question, but what is a "Nemeiys"? Might that be "Nemesis"? It could very well simply be a word I've never run into before... Every time I look it up, I get "Did you mean Nemesis?", except for the entries that point out the 98 anagrams it breaks into.
-=-=-=-=-=-=-=-=- 73, Gwen, NG3P
|
Gwen,
?"fat fingers", sorry. 狈é尘别蝉颈蝉:
狈?μεσι?,?狈é尘别蝉颈蝉
PEBKAC
|
Giuseppe, I got a laugh out of PEBKAC.
PICNIC works also - Problem In Chair Not In Computer
73 de Lee KX4TT
On Tuesday, November 5, 2024 at 10:14:14 AM EST, Giuseppe Marullo[iw2jww] <giuseppe@...> wrote:
Gwen,
?"fat fingers", sorry. 狈é尘别蝉颈蝉:
狈?μεσι?,?狈é尘别蝉颈蝉
PEBKAC
|