Rob said:
Graham - I mentioned the processor as all higher speed short switching time
signals on the data/address buses etc are internal to the package - this
must surely be an advantage as far as emissions are concerned.
It is indeed. I prefer this route too when possible.
While I may only be scratching the surface, many of us work at different
levels using different approaches. I've been through the EMC testing loop
with around 10 different products over a 6 year period and managed to kludge
my way though successfully with all of them. I've tried reading through
books on the subject most of which barely mention practicalities - at the
end of the day the local test lab owner with his 25+ years of experience is
a great source of practical methods. Members of this NG also share their
knowledge.
Having a good source of practical knowledge is a great help.
I was lucky enough to find a tame consultant back in 1987 when I first got
involved ( in this case with submitting products for testing to the American FCC
part 15 subpart J - computing devices rule ).
You intimate that you have a in-depth knowledge of this field, do you have
any practical advice to offer? Thanks for the reply.
It's reasonable. A few thoughts at random Keep any fast signal traces short *and
minimum LOOP AREA*. Use RCs if the signal edges aren't needed to be ultra fast.
Some recent microcontrollers now have 'controlled slew rate' I/O pins - use
them. Watch for noise emanating from the power leads ! One could write a sermon
? on *proper* grounding and enclosure design.
Have you considered immunity too ?
I doubt you're likely to have too much trouble with emissions from the sound of
it though.
The fun'll start with any interface cables no doubt.
The reason I mentioned that 2 layer boards is only scratching the surface is
that it's perfectly possible to make a 2 layer board that performs badly and a
single sided one that performs well ! Philips have written some decent
Application notes about doing single sided well for comsumer apps.
Graham