Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Wednesday May 24 2023, @10:47AM   Printer-friendly

https://arstechnica.com/cars/2023/05/ev-advocates-join-tech-groups-and-automakers-to-oppose-am-radio-mandate/

Congress wants to force AM into every new car for emergency alerts.

The fight over the future of AM radio got a little more heated this week as organizations representing the auto and technology industries told Congress that its plan to mandate this mode of radio wave reception is poorly conceived and will hinder progress.

AM radio has seen almost every other in-car entertainment option come and go—vinyl, 8-tracks, cassettes, CDs—and it might predate just about everything other than playing "I Spy," but time is catching up with this old broadcast technology. It is starting to get left behind as new models—many of which are electric vehicles—drive off into the sunset, streaming their audio instead of modulating its amplitude.

[...] "As more and more Americans adopt electric vehicles, we must ensure that they are equipped with AM radio. AM radio is—and will remain—an essential communications channel for emergency alerts and for disseminating news and other important information to residents of our district and communities across our country. I am proud to co-lead this bipartisan legislation which would ensure that EVs continue to be equipped with this basic but critical capability," said Rep. Bob Menendez (D-N.J.), another co-sponsor.


Original Submission

 
This discussion was created by janrinok (52) for logged-in users only, but now has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Interesting) by RS3 on Wednesday May 24 2023, @04:32PM (3 children)

    by RS3 (6367) on Wednesday May 24 2023, @04:32PM (#1307949)

    "FCC": Feckless Communications Commission. Our tax dollars at work.

    It's not just shielding- there are many electronic techniques to reduce RFI, including snubbers. It requires an impetus toward RFI reduction from the start of the design process.

    (I'm sure you and others know this- I'm just writing, as often, for those who might not know). In industry / factories, and more and more places, we're using 3-phase motor controllers. Most new clothes washing machines use them, water well pumps, EV motors, on and on. As many of you know, the controllers employ semiconductor switching, which is great, but that fast current switch dI/dt makes big RF noise.

    One great way to reduce the noise: by interesting properties of electromagnetism, you can twist wires and they'll mutually shield themselves- against emitting RFI, and they'll also be better at rejecting incoming electrical noise. Ethernet wire is a great example of this- balanced signal pair (one is an inverted signal of the other's signal), and this works with 3-phase. I've installed motor controller (sometimes called "drives", VFD, etc.) to motor wires that were 3 conductor, twisted and shielded. The main reason in a factory: the RFI can mess with sensors, which are everywhere in most factories.

    Point is, there are fairly easy solutions and it would be great if they'd put more effort into solutions and less effort into PR BS and lobbying.

    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by JoeMerchant on Wednesday May 24 2023, @05:05PM (2 children)

    by JoeMerchant (3937) on Wednesday May 24 2023, @05:05PM (#1307960)

    I agree, there are techniques that _help_, but a 300hp drive motor is a slightly bigger problem than a washing machine.

    In my field we have to comply with pretty strict emissions standards for in-hospital use. Oftentimes we'll employ all those "simple tricks" and go to testing just to find out that we're 3 or 5 dB over limit somewhere on the band, so we apply some "simple tricks" to push down that peak, and another one pops up... and there we are at $1000 per day at the testing facility that we have to reserve months in advance, playing whack-a-mole with emissions spectra.

    The most impressive "design for compliance" I have seen in action is spread spectrum clocks. Instead of having a "ringer" 96MHz oscillator driving your microprocessor's input, use a 92-100MHz spread spectrum oscillator - the peaks, and importantly: their harmonics, just disappear behind the background noise - even in an RF shielded room. Of course, we were using our 96MHz oscillator as the basis of a very precise difference measurement clock, so spread spectrum didn't work for us, and the 3rd harmonic of 96MHz comes in just below the 300MHz "step" in the allowable emissions spectrum, below 300MHz there are much stricter limits than above, and our 288MHz emissions spike would have met the limits if it were at 301MHz... I briefly considered bumping our base clock up to 101MHz to be done with it, but instead a 2nd ferrite clamped on to the accessory cables did the trick. Fun thing was: the device without the accessory cables passed first try, adding a couple of 2 meter antennas outside the shielded box, even if they are shielded and coupled to the box and don't carry any intentional 288MHz content, still doesn't do anything good for radiated power.

    --
    🌻🌻 [google.com]
    • (Score: 2) by RS3 on Wednesday May 24 2023, @05:36PM (1 child)

      by RS3 (6367) on Wednesday May 24 2023, @05:36PM (#1307970)

      I've had PCs that had BIOS settings to spread the master clock a bit. Maybe Award BIOS on Gigabyte MB? I forget now...

      Regarding testing: it's pretty easy and cheap to do your own testing before you take stuff to the test lab. Years ago I worked in EEG and we had to get some stuff qualified. I used several techniques to pre-test the stuff. What we didn't do was test with a patient connected, but knowing a little about HAM and RFI, I don't think the patient inputs would have radiated much RF as sample rates were pretty low; I forget- and it wasn't my area (but should have been) but maybe 20 Hz? IIRC the PC cases were all metal and had the various beryllium copper things everywhere to "seal" up the cases. We passed with flying colors anyway.

      RF is fun stuff. As a kid I used to read the ARRL handbook (still refer to it occasionally) and I was fascinated with (and slightly disturbed by) the sections on RF "leakage" out of fairly well closed up boxes. I think one factor is: like most of life, EEs and system designers are specialized and just don't understand RF stuff much if at all. Companies don't want to hire RF EEs, and those EEs might not understand motor harmonics (but probably would figure it out pretty quickly).

      Yes, ferrite beads do great things. They're everywhere. I always wonder why one thing will have them molded into the cable, but another similar product doesn't have one. I fully understand, but I have to wonder if the one devoid of ferrite ferrule should have had one?

      • (Score: 2) by JoeMerchant on Wednesday May 24 2023, @05:56PM

        by JoeMerchant (3937) on Wednesday May 24 2023, @05:56PM (#1307978)

        >Regarding testing: it's pretty easy and cheap to do your own testing before you take stuff to the test lab.

        Yes... ish. (After a couple of spectacular failures involving cross country travel) We built our own metal room, sealed the seams with conductive adhesive copper tape, installed a wall of RF anechoic cones, bought some decent gear and did a great deal of pre-testing before going to the certified house to obtain our compliance certificates. Our devices contained intentional oscillators for the purposes of making precise measurements, so we never really cleared the limits by wide margins. Our pre-testing did help, but even if we had calibrated our gear, I doubt it would have correlated 1:1 with what got observed at the certified labs.

        >BIOS settings to spread the master clock a bit.

        Yeah, first time I tested anything with a spread spectrum clock was a Palm Pilot in the (obviously) late 1990s - you couldn't tell if that thing was on or off by the RF emissions in a shielded room.

        >Companies don't want to hire RF EEs

        Small ones don't. Brash young startups (cough Tesla cough) probably don't. Once you get big and mature enough, you eventually end up building your own calibrated anechoic chambers and whether your EEs studied RF in school or not, you'll have a couple on staff who know enough to make stuff compliant.

        >I have to wonder if the one devoid of ferrite ferrule should have had one?

        Look to the certifications. Of course, I have never, ever, seen any practical enforcement channels that would realistically catch whether we put those two beads on our accessory cables or not. I suppose basic ISO-9001 style compliance audits _might_ look at the finished product vs the design on file from compliance testing, but in reality - especially smaller company reality - I'd bet it would average 20 years or more (maybe 200 years or more) before such an audit would catch such a non-compliance. More likely would be, if the emissions were truly grievous, that an end-user would complain about the interference and it would bubble up through channels that way - audit of complaints logs is the most common audit activity. Thing about our two ferrite design was: we were only a couple of dB over without them, nothing anybody would notice in practice, particularly when our peak was at 288MHz and compliant with 300MHz+ limits. But, non-conformance is risk and as a business we'd rather not risk our reputation over a couple of bucks per copy on a device we barely sell 100 copies a year of, on a good year! Now, an offshore manufacturer of something like power tools sold in big box home improvement stores? Hell yeah, I bet a lot of them cut that corner.

        --
        🌻🌻 [google.com]