|
Hello.
? I bought my tinySA ULTRA in 2023 to do self-certifications of developed hardware and/or to find out if my hardware will meet requirements for approval.
Though, I did not have any success yet. The ULTRA is calibrated and tested, but I have no idea on how to use it for this purpose in best way.
Is a video tutorial available, showing the usual way/process of doing that?
I am working to 100% on Linux (have a Linux workstation running openSUSE 15.5 x64). It? would be great if a program is available, generating a report with needed details by controlling the tinySA ULTRA over USB and finally generating a printable report for archiving.
It would be great if somebody can help.
Thanks in advance!
|
I also would love some instructions and maybe a script to generate a report on? self-certifications of developed hardware and/or to find out if my hardware will meet requirements for approval.
? I only run under Windows ? Mike ?
-------------------------
Hello.
? I bought my tinySA ULTRA in 2023 to do self-certifications of developed hardware and/or to find out if my hardware will meet requirements for approval.
Though, I did not have any success yet. The ULTRA is calibrated and tested, but I have no idea on how to use it for this purpose in best way.
Is a video tutorial available, showing the usual way/process of doing that?
I am working to 100% on Linux (have a Linux workstation running openSUSE 15.5 x64). It? would be great if a program is available, generating a report with needed details by controlling the tinySA ULTRA over USB and finally generating a printable report for archiving.
It would be great if somebody can help.
Thanks in advance!
|
Hello Mike and Rainer,
Gentlemen, I suggest you search this group with terms like "EMI
testing" as this has been discussed at great length previously.
But the long and the short of this is that EMI/EMC Testing is an
incredibly complicated subject.
If your product is powered by the mains, there are also Conducted
Emission tests that require additional specialised equipment such as
a LISN. Look it up:-)
There have been some very good links to some excellent tutorials and
references on the subject also in this group.
The best thing is to get your product pre-compliance tested by a
registered Test Lab and use their report as your reference.
Pre-compliance testing costs a lot less than a full Compliance Test.
Note where your product fails and by how much.
Then set up your DUT (Device Under Test) in your own lab and do your
own testing.
Note the levels you measure at the failure points noted in the Test
Lab report and these become YOUR test reference levels.
Then modify your design and aim to reduce your failure points by the
amount the Test Lab result notes plus at least a 6dB margin,
preferably a 10dB margin.
When you think your product is right, take it back to the Test Lab
and have another pre-compliance test done.
Repeat this cycle until the pre-compliance test results all pass.
Then you can get your Test Lab to do a full Certification Test.
NOTE: You can NOT certify your own products unless you are a
registered Test Lab and you would not be asking these questions if
you were:-)
It is vital that you understand the complexities of ensuring you
duplicate your test setup on every subsequent test you do.
Photographs of your test setup are your best friend.
You need to ensure your DUT, every piece of test equipment and every
cable is in exactly the same position each time and that every piece
of electronic equipment in or near your lab is in the same on or off
condition. This includes any type of lighting other than basic
filament lamps.
Preferably turn off and unplug any piece of electronic equipment not
required for the testing. As a minimum, unplug any unnecessary
electronic stuff, microwave ovens, printers, desktop computers, TVs,
etc that are on the same power circuit as your lab as even when
these things are "off", they can often have some degree of
electronics running that can contaminate your test results. And
mobile phones are a definite no-no!
The TinySA is a great tool and can save you a lot of money if used
correctly with appropriate accessories like antennas and E and H
field probes to develop your product.
But as noted earlier, you can not certify your own equipment.
So welcome to the wonderful world of EMI/EMC Testing. It is a
fascinating and at times, very frustrating, area of product
development. (Been there, done that!)
Enjoy your research!
HTH...Bob VK2ZRE
On 3/02/2025 10:26 pm, Mike Ward wrote:
toggle quoted message
Show quoted text
I also would love some instructions and maybe a
script to generate a report on?
self-certifications
of developed hardware and/or to find out if my hardware will
meet requirements for approval.
?
I only run under Windows
?
Mike ?
-------------------------
Hello.
?
I
bought my tinySA ULTRA in 2023 to do self-certifications of
developed hardware and/or to find out if my hardware will meet
requirements for approval.
Though,
I did not have any success yet. The ULTRA is calibrated and
tested, but I have no idea on how to use it for this purpose
in best way.
Is
a video tutorial available, showing the usual way/process of
doing that?
I
am working to 100% on Linux (have a Linux workstation running
openSUSE 15.5 x64). It? would be great if a program is
available, generating a report with needed details by
controlling the tinySA ULTRA over USB and finally generating a
printable report for archiving.
It
would be great if somebody can help.
Thanks
in advance!
|
thank you for your help ? Mike ?
-------------------------
Hello Mike and Rainer,
Gentlemen, I suggest you search this group with terms like "EMI
testing" as this has been discussed at great length previously.
But the long and the short of this is that EMI/EMC Testing is an
incredibly complicated subject.
If your product is powered by the mains, there are also Conducted
Emission tests that require additional specialised equipment such as
a LISN. Look it up:-)
There have been some very good links to some excellent tutorials and
references on the subject also in this group.
The best thing is to get your product pre-compliance tested by a
registered Test Lab and use their report as your reference.
Pre-compliance testing costs a lot less than a full Compliance Test.
Note where your product fails and by how much.
Then set up your DUT (Device Under Test) in your own lab and do your
own testing.
Note the levels you measure at the failure points noted in the Test
Lab report and these become YOUR test reference levels.
Then modify your design and aim to reduce your failure points by the
amount the Test Lab result notes plus at least a 6dB margin,
preferably a 10dB margin.
When you think your product is right, take it back to the Test Lab
and have another pre-compliance test done.
Repeat this cycle until the pre-compliance test results all pass.
Then you can get your Test Lab to do a full Certification Test.
NOTE: You can NOT certify your own products unless you are a
registered Test Lab and you would not be asking these questions if
you were:-)
It is vital that you understand the complexities of ensuring you
duplicate your test setup on every subsequent test you do.
Photographs of your test setup are your best friend.
You need to ensure your DUT, every piece of test equipment and every
cable is in exactly the same position each time and that every piece
of electronic equipment in or near your lab is in the same on or off
condition. This includes any type of lighting other than basic
filament lamps.
Preferably turn off and unplug any piece of electronic equipment not
required for the testing. As a minimum, unplug any unnecessary
electronic stuff, microwave ovens, printers, desktop computers, TVs,
etc that are on the same power circuit as your lab as even when
these things are "off", they can often have some degree of
electronics running that can contaminate your test results. And
mobile phones are a definite no-no!
The TinySA is a great tool and can save you a lot of money if used
correctly with appropriate accessories like antennas and E and H
field probes to develop your product.
But as noted earlier, you can not certify your own equipment.
So welcome to the wonderful world of EMI/EMC Testing. It is a
fascinating and at times, very frustrating, area of product
development. (Been there, done that!)
Enjoy your research!
HTH...Bob VK2ZRE
On 3/02/2025 10:26 pm, Mike Ward wrote:
I also would love some instructions and maybe a
script to generate a report on?
self-certifications
of developed hardware and/or to find out if my hardware will
meet requirements for approval.
?
I only run under Windows
?
Mike ?
-------------------------
Hello.
?
I
bought my tinySA ULTRA in 2023 to do self-certifications of
developed hardware and/or to find out if my hardware will meet
requirements for approval.
Though,
I did not have any success yet. The ULTRA is calibrated and
tested, but I have no idea on how to use it for this purpose
in best way.
Is
a video tutorial available, showing the usual way/process of
doing that?
I
am working to 100% on Linux (have a Linux workstation running
openSUSE 15.5 x64). It? would be great if a program is
available, generating a report with needed details by
controlling the tinySA ULTRA over USB and finally generating a
printable report for archiving.
It
would be great if somebody can help.
Thanks
in advance!
|
Hello, Bob.
Thanks for your explaining. I know that this is a complicated thing, but I bought? "tinySA Ultra"? to be able to find out if my developments are in safe distance to allowed limits of electromagnetic noise, or if (and where) my DUT excesses this limits.?
This saves a lot visits for pre-compliance testing and therefore lots of money (-> the reason why I bought the ULTRA for).
As far as I know, it is legal to do a self-declaration that a device is complying, but then it - of course - indeed has to be compliant. But knowing that my DUT is far below allowed limits before even doing a first pre-compliance test is always a good start.
So I would do the testing by either moving to a location some kilometers away from buildings and mobile phone antennas, etc., move to a deep parking house, or similar, ? and do two scans:
One without my DUT turned on (recording the environmental noise), and another one with my DUT turned on (recording environmental noise + DUT's noise). Or I build a Faraday cage using a fine and grounded metal mesh and do the above inside the laboratory. (will also reduce external influence) before.
The difference should be my DUT then, right?? As my developments usually are small devices for automating or recording something, they are often battery operated. If not, a certified power adapter with cable length shorter than 1m makes life also lots easier.
?
This will at least give me information on noise generated by the DUT.?? Doing this math without an automated script is a horrible job, because tinySA (Ultra) by itself is not really easy to use (at least for me).
If additional tests are required (i.e. the Conduction Emitted Tests), this is another part I will have to do separately. But most important is the direct emission to air, because I often use plastic enclosures and digital electronics. Well, I already try to always use Microchip PIC controllers with internal oscillators, this drastically reduces radiation, but it is still digital, with lots of square waves therefore.
?
|
Since you know nothing about this system, you are biting off something WAY OVER YOUR HEAD.? You might be able to do a pre-compliance assessment, but that's all.? And.....you need to learn the ropes of making radiated and conducted emission measurements in a responsible and best -practices manner.? If you are also looking at the EU, there are a whole bunch of additional required tests addressing the susceptibility side of things.? A crash course from one of the few consultants giving classes on the subjects would be HIGHLY RECOMMENDED!!!? You are dealing with legally stipulated limits by the FCC and the EU (and other countries and markets).? Also you need to become up-close-and-personal with the regulations, testing methods, and the various world-wide regulatory agencies. ?
Please walk before you attempt to run.? I've done EMC/RFI professionally for at least 40-years.? The discipline is not trivial.? Again, crawl, then walk, and finally run.
Dave - W?LEV?
Hello, Bob.
Thanks for your explaining. I know that this is a complicated thing, but I bought? "tinySA Ultra"? to be able to find out if my developments are in safe distance to allowed limits of electromagnetic noise, or if (and where) my DUT excesses this limits.?
This saves a lot visits for pre-compliance testing and therefore lots of money (-> the reason why I bought the ULTRA for).
As far as I know, it is legal to do a self-declaration that a device is complying, but then it - of course - indeed has to be compliant. But knowing that my DUT is far below allowed limits before even doing a first pre-compliance test is always a good start.
So I would do the testing by either moving to a location some kilometers away from buildings and mobile phone antennas, etc., move to a deep parking house, or similar, ? and do two scans:
One without my DUT turned on (recording the environmental noise), and another one with my DUT turned on (recording environmental noise + DUT's noise). Or I build a Faraday cage using a fine and grounded metal mesh and do the above inside the laboratory. (will also reduce external influence) before.
The difference should be my DUT then, right?? As my developments usually are small devices for automating or recording something, they are often battery operated. If not, a certified power adapter with cable length shorter than 1m makes life also lots easier.
?
This will at least give me information on noise generated by the DUT.?? Doing this math without an automated script is a horrible job, because tinySA (Ultra) by itself is not really easy to use (at least for me).
If additional tests are required (i.e. the Conduction Emitted Tests), this is another part I will have to do separately. But most important is the direct emission to air, because I often use plastic enclosures and digital electronics. Well, I already try to always use Microchip PIC controllers with internal oscillators, this drastically reduces radiation, but it is still digital, with lots of square waves therefore.
?
|
Hello Rainer,
The problem is you would need to know the Antenna Factor of your
test antennas at all test frequencies to make any meaningful
measurements. Then there is a whole lot of math that needs to be
applied to your results to get "accurate" field strengths of the
emissions.
Also, the TinySA does not include the required 9KHz RBW. It has
10KHz which is close enough for comparative testing but not for
certification.
That is why you need to pay for a pre-compliance test so that you
have something to reference your measurements to.
The TinySA has a nice feature that allows you to specify a Limit
Line to the display which helps with visualising your results.
As for using a certified power adapter to power your DUT, that is
OK, but there is no guarantee your device won't "drive" the power
adapter and hence get back into the mains supply.
The other steps you suggest, Faraday room, etc are all good ideas
and will enhance the repeatability of your test results, but you
need something to reference against.
Without an external reference, your results will, unfortunately, be
meaningless.
Hope this helps. Cheers...Bob VK2ZRE
On 4/02/2025 12:01 am, Rainer Hantsch
wrote:
toggle quoted message
Show quoted text
Hello, Bob.
Thanks for your explaining. I know that this is a complicated
thing, but I bought? "tinySA Ultra"? to be able to find out if
my developments are in safe distance to allowed limits of
electromagnetic noise, or if (and where) my DUT excesses this
limits.?
This saves a lot visits for pre-compliance testing and therefore
lots of money (-> the reason why I bought the ULTRA for).
As far as I know, it is legal to do a self-declaration that a
device is complying, but then it - of course - indeed has to be
compliant. But knowing that my DUT is far below allowed limits
before even doing a first pre-compliance test is always a good
start.
So I would do the testing by either moving to a location some
kilometers away from buildings and mobile phone antennas, etc.,
move to a deep parking house, or similar, ? and do two scans:
One without my DUT turned on (recording the environmental
noise), and another one with my DUT turned on (recording
environmental noise + DUT's noise). Or I build a Faraday cage
using a fine and grounded metal mesh and do the above inside the
laboratory. (will also reduce external influence) before.
The difference should be my DUT then, right?? As my
developments usually are small devices for automating or
recording something, they are often battery operated. If not, a
certified power adapter with cable length shorter than 1m makes
life also lots easier.
?
This will at least give me information on noise generated by
the DUT.?? Doing this math without an automated script is a
horrible job, because tinySA (Ultra) by itself is not really
easy to use (at least for me).
If additional tests are required (i.e. the Conduction Emitted
Tests), this is another part I will have to do separately. But
most important is the direct emission to air, because I often
use plastic enclosures and digital electronics. Well, I already
try to always use Microchip PIC controllers with internal
oscillators, this drastically reduces radiation, but it is still
digital, with lots of square waves therefore.
?
|
Using TRACE/CALC/TABLE TRACE you can enter a 8 point linear approximation of the antenna factor over frequency , save the table to the SD for future loading, and use the trace table to correct the measured data for the antenna factor by subtracting the trace defined by the trace table from the measured trace.
--
Designer of the tinySA
For more info go to
|
Handy AF conversion tool -
?
?
-Charlie
?W5CDT
?
|
Hi, Dave.
Actually I never said that I want to do a certification.??
What I repeatedly said is:? I want to easily and quickly find out if the developed device is exceeding allowed levels somewhere, or how much "safety gap" to this limits I have.
So, yes, what I want to do is a pre-compliance assessment, nothing else,? but this test should be as reliable as possible.
If I see that my device is everywhere in safe distance from allowed limits, this is a? valuable information to me. If I see that the device is exceeding limits, I know that I can save the money for a pre-compliance test and have to solve this issues first.
So it would be a great approach when some software would be available, doing a first (or some) sweep(s) through entire frequency range (recording the environmental noise without having my DUT (Device Under Test) activated.? Then it should do the same with turned on DUT and finally do some math by subtracting the environmental noise from latter, giving? the noise emitted by my DUT. If this is done by software, this will also allow to use a database with allowed limits, so the result will be even more informational.
The current situation is that I cannot even see a difference right now, with the lambda/4 antenna in distance of 10cm above my DUT. This might be a good sign (I expected to find at least a 64MHz peak, 400 Hz (from EL display illumination), and 4 MHz (SPI bus clock), but this noise is either too low at all and therefore vanishes in environmental noise), or my design is really so good that there is "nothing". The other reason for "seeing nothing" can be a wrong configuration of tinySA Ultra.
THIS (and similar things) I would like to find out, possibly described very simplified, but you as an expert for sure understand what I mean.
But today I spent literally 8 hours in trying to get this QtTinySA software running on my Linux machine (openSUSE Leap 15.5) to find out its usability, but as this software totally refuses to start up on my openSUSE Leap 15.5, I am meanwhile inclined to stop spending more time into it.
?
|
Sadly I cannot edit a written reply afterwards, so a little appendix:
As I am no certified lab for doing certifications, even a "self-certification" is no official certification. Understand it as self-done pre-compliance test, nothing else.
|
I often wonder if people expect more from this device than it is capable of. I am not sure exactly what the OP wants to do, but maybe there are other devices or equipment that can do it better. The TinySA Ultra is an amazing piece of equipment and I have used it several times to peak the pipe cap filters for output in the 10 to 12 GHz range for the W1GHZ microwave frequency multiplier designs. This is something I can't do with an HP 435B power meter by itself. The TinySA shows me what frequency the output is at. Tuning these pipe cap filters with a power meter alone sometimes results in tuning to the wrong harmonic. But I wouldn't trust the accuracy of the power output measurement. Once I have the pipe cap filters peaked, I can measure the power for accuracy with the 435B. And I wouldn't trust the frequency measurement to be extremely accurate. I have an EIP frequency counter that will measure frequency accurately down to the Hz in the range of LF to 18 GHz. Also, you can't accurately measure the NF of a microwave preamp with the TinySA.
Zack W9SZ
Since you know nothing about this system, you are biting off something WAY OVER YOUR HEAD.? You might be able to do a pre-compliance assessment, but that's all.? And.....you need to learn the ropes of making radiated and conducted emission measurements in a responsible and best -practices manner.? If you are also looking at the EU, there are a whole bunch of additional required tests addressing the susceptibility side of things.? A crash course from one of the few consultants giving classes on the subjects would be HIGHLY RECOMMENDED!!!? You are dealing with legally stipulated limits by the FCC and the EU (and other countries and markets).? Also you need to become up-close-and-personal with the regulations, testing methods, and the various world-wide regulatory agencies. ?
Please walk before you attempt to run.? I've done EMC/RFI professionally for at least 40-years.? The discipline is not trivial.? Again, crawl, then walk, and finally run.
Dave - W?LEV?
Hello, Bob.
Thanks for your explaining. I know that this is a complicated thing, but I bought? "tinySA Ultra"? to be able to find out if my developments are in safe distance to allowed limits of electromagnetic noise, or if (and where) my DUT excesses this limits.?
This saves a lot visits for pre-compliance testing and therefore lots of money (-> the reason why I bought the ULTRA for).
As far as I know, it is legal to do a self-declaration that a device is complying, but then it - of course - indeed has to be compliant. But knowing that my DUT is far below allowed limits before even doing a first pre-compliance test is always a good start.
So I would do the testing by either moving to a location some kilometers away from buildings and mobile phone antennas, etc., move to a deep parking house, or similar, ? and do two scans:
One without my DUT turned on (recording the environmental noise), and another one with my DUT turned on (recording environmental noise + DUT's noise). Or I build a Faraday cage using a fine and grounded metal mesh and do the above inside the laboratory. (will also reduce external influence) before.
The difference should be my DUT then, right?? As my developments usually are small devices for automating or recording something, they are often battery operated. If not, a certified power adapter with cable length shorter than 1m makes life also lots easier.
?
This will at least give me information on noise generated by the DUT.?? Doing this math without an automated script is a horrible job, because tinySA (Ultra) by itself is not really easy to use (at least for me).
If additional tests are required (i.e. the Conduction Emitted Tests), this is another part I will have to do separately. But most important is the direct emission to air, because I often use plastic enclosures and digital electronics. Well, I already try to always use Microchip PIC controllers with internal oscillators, this drastically reduces radiation, but it is still digital, with lots of square waves therefore.
?
--
|
Zack, he knowns nothing about regulatory testing for either radiated or conducted emission.? He knowns nothing about the regulatory agencies.? He knowns nothing about the prescribed measurement setups.? He knows nothing about a LISN for conducted emissions.? He knows nothing about the clocks and how that influences the max tested frequency for FCC.? 40 GHz for the FCC?? The TINYSA does not even touch that frequency.? He is so far over his head he doesn't realize he is drowning.
Yes, the TINYSAs can be used for pre-compliance evaluations IF YOU KNOW WHAT YOU ARE DOING. ? He does not.? Any of us who have been or are in the EMC/RFI field could teach him, but not here on the www.? He needs first to crawl, then walk, and finally run.? That takes time and is not an "instant" process which the newbies seem to require. ?
Just my opinion having put food on our table and a roof over our heads for 40+ years professionally doing EMC/RFI.
Dave - W?LEV
I often wonder if people expect more from this device than it is capable of. I am not sure exactly what the OP wants to do, but maybe there are other devices or equipment that can do it better. The TinySA Ultra is an amazing piece of equipment and I have used it several times to peak the pipe cap filters for output in the 10 to 12 GHz range for the W1GHZ microwave frequency multiplier designs. This is something I can't do with an HP 435B power meter by itself. The TinySA shows me what frequency the output is at. Tuning these pipe cap filters with a power meter alone sometimes results in tuning to the wrong harmonic. But I wouldn't trust the accuracy of the power output measurement. Once I have the pipe cap filters peaked, I can measure the power for accuracy with the 435B. And I wouldn't trust the frequency measurement to be extremely accurate. I have an EIP frequency counter that will measure frequency accurately down to the Hz in the range of LF to 18 GHz. Also, you can't accurately measure the NF of a microwave preamp with the TinySA.
Zack W9SZ
Since you know nothing about this system, you are biting off something WAY OVER YOUR HEAD.? You might be able to do a pre-compliance assessment, but that's all.? And.....you need to learn the ropes of making radiated and conducted emission measurements in a responsible and best -practices manner.? If you are also looking at the EU, there are a whole bunch of additional required tests addressing the susceptibility side of things.? A crash course from one of the few consultants giving classes on the subjects would be HIGHLY RECOMMENDED!!!? You are dealing with legally stipulated limits by the FCC and the EU (and other countries and markets).? Also you need to become up-close-and-personal with the regulations, testing methods, and the various world-wide regulatory agencies. ?
Please walk before you attempt to run.? I've done EMC/RFI professionally for at least 40-years.? The discipline is not trivial.? Again, crawl, then walk, and finally run.
Dave - W?LEV?
Hello, Bob.
Thanks for your explaining. I know that this is a complicated thing, but I bought? "tinySA Ultra"? to be able to find out if my developments are in safe distance to allowed limits of electromagnetic noise, or if (and where) my DUT excesses this limits.?
This saves a lot visits for pre-compliance testing and therefore lots of money (-> the reason why I bought the ULTRA for).
As far as I know, it is legal to do a self-declaration that a device is complying, but then it - of course - indeed has to be compliant. But knowing that my DUT is far below allowed limits before even doing a first pre-compliance test is always a good start.
So I would do the testing by either moving to a location some kilometers away from buildings and mobile phone antennas, etc., move to a deep parking house, or similar, ? and do two scans:
One without my DUT turned on (recording the environmental noise), and another one with my DUT turned on (recording environmental noise + DUT's noise). Or I build a Faraday cage using a fine and grounded metal mesh and do the above inside the laboratory. (will also reduce external influence) before.
The difference should be my DUT then, right?? As my developments usually are small devices for automating or recording something, they are often battery operated. If not, a certified power adapter with cable length shorter than 1m makes life also lots easier.
?
This will at least give me information on noise generated by the DUT.?? Doing this math without an automated script is a horrible job, because tinySA (Ultra) by itself is not really easy to use (at least for me).
If additional tests are required (i.e. the Conduction Emitted Tests), this is another part I will have to do separately. But most important is the direct emission to air, because I often use plastic enclosures and digital electronics. Well, I already try to always use Microchip PIC controllers with internal oscillators, this drastically reduces radiation, but it is still digital, with lots of square waves therefore.
?
--
|
It always distresses me when people who are obviously very clever and experienced refuse to afford the politeness and assistance that they were no doubt offered when they were beginning in a field. You don't have to be rude in order to prove your superior intelligence. But there, clearly I expect too much of humanity. AI will not doubt do better.
|
But to know the margin to limits you need a way to calibrate your measurement system. The system is not just the TinySA. It includes the antenna as well. This is why several people have recommended getting a scan at a registered test lab. You will then know your margin to the limits, so you can then hopefully correlate your measurements to that. It is not perfect, but I don't think there is any other way to get started.
?
Have you taken a product through the process before? There are multiple standards that cover more than just radiated emissions.
|
I'm not sure what you're referring to? You didn't quote any text and I haven't seen any replies that were particularly rude.
Zack W9SZ
It always distresses me when people who are obviously very clever and experienced refuse to afford the politeness and assistance that they were no doubt offered when they were beginning in a field. You don't have to be rude in order to prove your superior intelligence. But there, clearly I expect too much of humanity. AI will not doubt do better.
|
My apologies! This one /g/tinysa/message/19356"Zack, he knowns nothing about regulatory testing for either radiated or conducted emission. ..."
|
On Tue, Feb 4, 2025 at 07:34 AM, Bob Ecclestone wrote:
the TinySA does not include the required 9KHz RBW.
Perhaps inclusion of EMI filter characteristics is a good suggestion for future improvement of the tinySA firmware.??
Best regards, Don Brant
|
I agree, but I and several others have posted polite messages attempting to enlighten the poster of his severe uphill learning curve and taking ALL engineering and physics (Roger did a better job than I did) out of the attempts at helping the poster.? I even suggested he look for online tutorials but he didn't.? I even suggested, all politely, he search out the FCC and EU regulations.? But he didn't.
So, I cut to the chase.? After doing EMC/RFI for 40+ years, I, and others in my boat, realize what a learning curve he will face to do a responsible job of pre-compliance.? I also became fed up with other posters who didn't know what they were advising and nothing about the field giving the poster advice which amounted to nothing but snake oil.?
So, I cut to the chase and posted the reality of what was being requested.
Dave - W?LEV
It always distresses me when people who are obviously very clever and experienced refuse to afford the politeness and assistance that they were no doubt offered when they were beginning in a field. You don't have to be rude in order to prove your superior intelligence. But there, clearly I expect too much of humanity. AI will not doubt do better.
|
On Tue, Feb 4, 2025 at 10:55 AM, Donald S Brant Jr wrote:
Perhaps inclusion of EMI filter characteristics is a good suggestion for future improvement of the tinySA firmware
Unfortunately this will not possible. As stated the current filters are close enough for pre compliance. For actual compliance measurements I recommend to use a more capable SA. You will have to anyway as the equipment you use for compliance testing has to have a valid tracable calibration certificate.
--
Designer of the tinySA
For more info go to
|
W5CDT
Donald S Brant Jr