Chris Pinter's Top 10 things every engineer should know about radio development.

RE: Chris Pinter's Top 10 things every engineer should know about radio development.

D_Hersey — Sun, 09 Feb 2014 02:53:57 GMT

#3 sometimes in a wired world we have these problems as well, we just use different names, such as 'cross-talk.'

RE: Chris Pinter's Top 10 things every engineer should know about radio development.

DAB — Sat, 08 Feb 2014 19:21:54 GMT

Great post,

It brought back memories from my tech school days when I was studying for my FCC license. Passed level 2, but did not quite pass level 3.

Still, it was challenging and the new technology has added a lot of new features you need to learn.

Thanks

DAB

RE: Chris Pinter's Top 10 things every engineer should know about radio development.

gervasi — Sat, 08 Feb 2014 18:46:27 GMT

Yes. I agree with this post.

#3: A narrow band hopper might take out only a few subcarriers of that wide Wi-Fi signal, but if it's even a few dB over the Wi-Fi signal it will saturate the receiver, an the Wi-Fi signal falls into the noise. The receivers have no spare dynamic range. WiFi chip sets struggle to hit their top data rates even under ideal conditions connected with cables and attenuators.

#7: For antenna matching, if you mess around with the VNA you start to get an intuition about the Smith Chart even if you're not thinking about the actual impedances.

#9: I do not understand Maxwell's equations. I break down all interference into one of four crosstalk paths.

#10: But there are a lots of fully integrated modules. It's important for someone who's worked on them to be involved at some point, but it's way easier than it used to be. Many ICs have a fully-integrated transceiver.