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: 5, Interesting) by owl on Wednesday May 24 2023, @02:15PM (32 children)

    by owl (15206) on Wednesday May 24 2023, @02:15PM (#1307906)

    and adding to some cars already out there via a firmware update.

    Which just goes to show that the "removal" wasn't much of a removal if a firmware update can restore AM radio. All the hardware was already present, they just flipped a switch and turned off the "AM Radio" UI on the touchscreen.

    Which also meant it would have been zero cost on their part to have just left things alone.

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

    Total Score:   5  
  • (Score: 2) by JoeMerchant on Wednesday May 24 2023, @02:40PM (13 children)

    by JoeMerchant (3937) on Wednesday May 24 2023, @02:40PM (#1307911)

    >Which also meant it would have been zero cost on their part to have just left things alone.

    Just because the software supports it, and the hardware can implement an AM receiver, does not mean that the customer experience is going to be satisfactory.

    Even if It works great when you've parked your Ford in the middle of a corn field in central Illinois, nearest powerline or other vehicle being miles away, listening to Chicago stations after sunset - things will be different on the 110/I290 at rush hour, surrounded by Teslas in stop-and-go traffic with electric trains sparking by. Ford might point at others as the sources of interference some of the time, but odds are the Ford itself will be interfering with your AM listening enjoyment in some driving scenarios.

    --
    🌻🌻 [google.com]
    • (Score: 4, Insightful) by owl on Wednesday May 24 2023, @03:10PM (12 children)

      by owl (15206) on Wednesday May 24 2023, @03:10PM (#1307922)

      All of which is already occurring today in any car where the driver has tuned to an AM station. At least in markets with a higher level of Tesla (and the like) purchases than most. Around me I see Tesla's all the time. So anyone tuning AM is already hearing static caused by Tesla's.

      And, of course, this is nothing new. I remember late 1970's cars, with only AM radios, and the reception was already full of static and pops and glitches anyway (and, if you knew what you were listening for, you could estimate engine RPM by the tone of the alternator whine). AM and static have been a pairing for as long as AM has existed.

      Why the sudden desire on the part of car makers to drop AM (other than possibly to "ape teslla") none of us know -- but static and interference on AM stations has been a constant forever, so 'static' alone is not likely the real reason why.

      • (Score: 2) by JoeMerchant on Wednesday May 24 2023, @03:28PM (11 children)

        by JoeMerchant (3937) on Wednesday May 24 2023, @03:28PM (#1307927)

        I think the situation is: while AM static of the 1970s was annoying, AM static of the 2030s is likely to render the band unusable, unintelligible, absolutely worthless.

        Being able to drop "AM compatibility" from their list of design criteria will enable future automakers to make even more profit on the cars they will be selling. You can't claim AM compatibility when your own vehicle is rendering the radio output useless any time the vehicle is moving.

        --
        🌻🌻 [google.com]
        • (Score: 3, Interesting) by RS3 on Wednesday May 24 2023, @03:31PM (10 children)

          by RS3 (6367) on Wednesday May 24 2023, @03:31PM (#1307928)

          AFAIK FCC required spark-ignition engines to use resistor plugs and plug wires to reduce EMI. Is this whole thing about EVs not complying with RF emissions, and EV makers and industry groups fighting RF shielding and general RF noise reduction?

          • (Score: 2) by owl on Wednesday May 24 2023, @03:45PM (1 child)

            by owl (15206) on Wednesday May 24 2023, @03:45PM (#1307932)

            That's what it sounds like. They don't want to adequately shield/filter their noise, and the FCC's not on the ball to force the issue.

            • (Score: 2) by RS3 on Wednesday May 24 2023, @04:16PM

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

              So who's in charge of FCC? Who should be holding their feet to the fire?

              If my hunch is right, that EV makers (and others) don't want to bother with fixing RFI problems, it's obviously not just AM radio that suffers. CB radio, HAM, and probably many others I haven't thought of yet.

              My fear is: if this problem isn't clamped down on soon, by the time various people groups collaborate and demand action, it will be too late- too many electrically noisy cars out there, too expensive to fix.

              This feels far too much like the whole FAA / Boeing / MCAS / many deaths problem. Govt. agencies not doing their jobs but still raking in pay and great benefits including long-term pensions.

          • (Score: 2) by JoeMerchant on Wednesday May 24 2023, @04:15PM (7 children)

            by JoeMerchant (3937) on Wednesday May 24 2023, @04:15PM (#1307943)

            I believe that's it, and I believe this go-around they have some legitimate concerns about the costs involved to shield a "modern, efficient" EV powertrain from causing AM interference.

            Anything is possible, I'm sure they can make an EV that's absolutely radio-silent on the whole AM band, but that would eat into profits because nobody is actually going to pay extra just because they can listen to AM radio.

            --
            🌻🌻 [google.com]
            • (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.

              • (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]
            • (Score: 2) by owl on Wednesday May 24 2023, @04:34PM (2 children)

              by owl (15206) on Wednesday May 24 2023, @04:34PM (#1307950)

              Thing is, EM noise such as this is not often isolated to a single band (other than the base frequency of the switching PSU that is). This kind of EM noise is most often wideband interference. AM radios may not be the only thing impacted. A lot of other RF might also be impacted (think CB, or police/fire/rescue bands or other RF bands). AM here may just be the "canary in the coal mine" that is actually warning of a far larger amount of interference that will happen. And as another poster here pointed out, after a certain tipping point of enough EV's without proper shielding/suppression installed on the road, it will be so expensive to turn back that no one in a position to do so will likely be willing to make that call.

              • (Score: 0) by Anonymous Coward on Wednesday May 24 2023, @05:04PM (1 child)

                by Anonymous Coward on Wednesday May 24 2023, @05:04PM (#1307959)

                > A lot of other RF might also be impacted ...

                Also think electronic medical devices - insulin pumps, pacemakers, the list keeps on growing.

                If cars produce RF that kills someone, the FCC and the car maker will get a wake up call!

                • (Score: 3, Interesting) by JoeMerchant on Wednesday May 24 2023, @05:10PM

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

                  First: it will have to be proven, and that can take expensive years when someone the size of Ford is fighting the other side in our adversarial system.

                  By the time that proof comes through, there should be dozens to hundreds of additional deaths, if the proof was really true.

                  Such is our system.

                  Want to find some nasty RF interference for your implantable medical device? Look no further than the theft prevention tags / deactivation pads / sensors at store entrances and exits. They ring around 80-125KHz, which is a very common frequency range for pacemakers and other implantable devices to run their wireless control interfaces.

                  --
                  🌻🌻 [google.com]
  • (Score: 4, Insightful) by DannyB on Wednesday May 24 2023, @02:43PM (17 children)

    by DannyB (5839) Subscriber Badge on Wednesday May 24 2023, @02:43PM (#1307912) Journal

    Speculation.

    Is it possible that the "hardware already present" was modern SDR? They didn't just flip a switch, but rather downloaded an "AM Radio App" which could configure the SDR hardware and demodulate AM radio. Of course, it would need to filter out the noisy spark plug interference, which is especially bad on EVs.

    --
    People today are educated enough to repeat what they are taught but not to question what they are taught.
    • (Score: 2) by owl on Wednesday May 24 2023, @03:00PM (15 children)

      by owl (15206) on Wednesday May 24 2023, @03:00PM (#1307916)

      Is it possible that the "hardware already present" was modern SDR?

      Which, therefore, means: the hardware was already present. Even SDR needs hardware -- the actual analog sampler circuits that digitize the incoming waveforms so the SDR code can then filter and demodulate the signals.

      I.e., they did not need to replace the "radio hardware" with new hardware that contained additional circuits capable of tuning and demodulating the AM bands. Al the hardware necessary was already present.

      Which looks exactly like what I said in the first comment. The "hardware" (note -- generic hardware, not anything specific) was already present.

      • (Score: 2) by RS3 on Wednesday May 24 2023, @03:23PM (14 children)

        by RS3 (6367) on Wednesday May 24 2023, @03:23PM (#1307924)

        Do SDRs have wide enough RF front end bandwidth to go from AM to FM and beyond?

        • (Score: 3, Insightful) by owl on Wednesday May 24 2023, @03:47PM (2 children)

          by owl (15206) on Wednesday May 24 2023, @03:47PM (#1307934)

          That depends upon the SDR hardware.

          Clearly in this specific example, given that a "software update" restores AM radio, the SDR hardware must have been capable of receiving both AM and FM bands. Because if they had used SDR hardware that could not sample the AM band, they could not restore AM radio via just a software update.

          • (Score: 2) by RS3 on Wednesday May 24 2023, @04:07PM (1 child)

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

            Thank you. I was posing a semi-rhetorical question. I'm not up on the latest in RF front-ends, if they still need tuning circuits, or are they wide enough bandwidth to take in pretty much anything from DC to light and heterodyne to some IF frequency.

            One of my arguments in this whole dog and pony show is that it will cost MORE to redesign radio receivers to remove AM circuits. IE, cheaper to keep things as they have been.

            There's more afoot here. Whenever some industry group collaborates on something like this you know it's all about profit, never about people, product or service quality. (I think I'm becoming my dad, which isn't such a bad thing after all.)

            • (Score: 2) by owl on Wednesday May 24 2023, @04:49PM

              by owl (15206) on Wednesday May 24 2023, @04:49PM (#1307955)

              I'm not up on the latest in RF front-ends, if they still need tuning circuits, or are they wide enough bandwidth to take in pretty much anything from DC to light and heterodyne to some IF frequency.

              That partly depends upon how much you want to pay.

              Here's a common SDR dongle used by hobbists: RTL-SDR [radioreference.com].

              Depending on the tuner chip in a specific dongle, the lower end frequency gores down to 22Mhz. So not down to DC at the $20 price range. And not suitable for receiving AM either at this price range.

              One of my arguments in this whole dog and pony show is that it will cost MORE to redesign radio receivers to remove AM circuits. IE, cheaper to keep things as they have been.

              The fact that Ford can restore existing car's AM reception with a software update means the BOM for the car has the AM capable hardware parts already present. Now, whether they could remove the AM capable hardware, without also removing FM radio too, none of us know. But a "software update" to restore means they had not yet redesigned the radio circuits to drop the hardware that can receive the AM bands. Of course this could simply mean that they had not yet redesigned the hardware to reduce the BOM by dropping the chip capable of receiving the AM bands.

              There's more afoot here. Whenever some industry group collaborates on something like this you know it's all about profit, never about people, product or service quality. (I think I'm becoming my dad, which isn't such a bad thing after all.)

              A "follow the money" analysis will often find an actual reason for some imposed change from some "entity". Even if they don't overtly advertise that reason.

        • (Score: 2) by DannyB on Thursday May 25 2023, @05:40PM (10 children)

          by DannyB (5839) Subscriber Badge on Thursday May 25 2023, @05:40PM (#1308154) Journal

          First of all, please forgive any poor description that follows. I am NOT an RF guy.

          I've watched SDR videos on YouTube. I've used a cheap dongle to play with SDR myself.

          What you will typically see (either on videos, or if you try it for yourself) is that the software display shows quite a bit of spectrum. You can see where in the spectrum signals are located. Then move your little 'red line' to that part of the spectrum and hear it, or decode it if it is a digital transmission. So the hardware doesn't "tune" to a specific frequency. All of these frequencies across a wide range are seen in software and visualized on the display. You simply pick out what part of what you are seeing that you wish to listen to.

          However you can see the constantly changing signal energy in all of the adjacent bands simultaneously.

          --
          People today are educated enough to repeat what they are taught but not to question what they are taught.
          • (Score: 2) by RS3 on Thursday May 25 2023, @06:11PM

            by RS3 (6367) on Thursday May 25 2023, @06:11PM (#1308166)

            I haven't dug into SDRs (yet) but did a quick search. It looks like there are several topologies, ranging from mostly digital sampling / processing, to much analog tuning / amplification / filtering then digital sampling. It'd take more research to find out what is more common in typical SDRs.

            In other words, you may have a "digital" UI, but using DAC (digital to analog) the system can control analog tuning circuits. You'll always get a more sensitive receiver if you can do better RF tuning and amplification, rather than wide-band amplification and then filter. Reason: amplifiers also amplify electrical noise, including their own noise. The more tuning and tuned filtering you use, the more you literally tune out (filter) the unwanted spectra. Some noise will still be present in the desired tuning frequency, but the signal-to-noise will be much better.

            Antenna size and tuning are a huge factor too.

            Even with all of that analog tuning / filtering you'll still get adjacent frequencies. The better the filter, usually the more "narrow" its bandpass (unless you're designing for a wide bandpass or "mesa" (tabletop) frequency response because you need a bunch of frequencies at once, such as spread-spectrum systems).

            Transistors are getting better and better, less inherent noise, so we can do more amplification with less tuning circuits and let the DSP handle much of the tuning and signal "detection" (word used long ago to describe the process of extracting the useful information out of a modulated RF signal).

            Being a bit pedantic, SDR could also be partially a "software controlled radio" where again, software controls some of the (legacy) analog circuitry.

            (I purposely didn't get into low-level specifics like "local oscillator", frequency synthesis, PLL, varactor diodes, heterodyning, IF amplification, ..., but I can talk mov, jsr, ret, push, jnz, pop, and nop if you like. nop is my personal favorite.)

          • (Score: 2) by RS3 on Thursday May 25 2023, @06:16PM (8 children)

            by RS3 (6367) on Thursday May 25 2023, @06:16PM (#1308167)

            Augmentation: in pure theory, SDR is almost infinite bandwidth, and all done by sampling / DSP. But you'd need some unearthly sample rates, and even unsolarsystemly DSPs to do it. Although not quite DC to light, commonly available SDRs have very impressive tuning bandwidths. I need to do some more market research / studying...

            • (Score: 3, Interesting) by DannyB on Thursday May 25 2023, @08:20PM

              by DannyB (5839) Subscriber Badge on Thursday May 25 2023, @08:20PM (#1308200) Journal

              There are some videos about how the SDR actually works.

              It's been a while since I toyed with it. So my memory may be fuzzy.

              Something beats or somehow lowers the frequency range to something acceptable to a DAC. But I don't think it is superhet, which I remember fondly from the 1970s in my teens.

              Something is done involving phase shifting the original wave by two different phase shifts, and doing something something involving some ugodly complex math, and then getting something useful. So it is almost all done digitally. There is little analog. Certainly not a 'radio' in any conventional old fashioned sense -- that happens to be controlled by a microprocessor.

              It really is a "software radio".

              There are several different user interfaces that work with various SDR dongles you can buy on Amazon. Some of the software are open source.

              Typically you can see a large part of the spectrum. Then pick (not "tune") some small piece. You can then select whether to demodulate and how to demodulate, and other options and whizbang like single sideband and other things I don't understand. You can then listen to the demodulated signal (AM, FM, etc) or treat it as a digital signal, and decode it according to various protocols, such as digital TV, packet radio, etc.

              --
              People today are educated enough to repeat what they are taught but not to question what they are taught.
            • (Score: 3, Informative) by DannyB on Thursday May 25 2023, @08:30PM (6 children)

              by DannyB (5839) Subscriber Badge on Thursday May 25 2023, @08:30PM (#1308202) Journal

              In case it helps, here are some things I had bookmarked long ago:

              https://www.youtube.com/watch?v=fOlz0OcZPjc [youtube.com]

              https://www.youtube.com/watch?v=qCiyN9llVGA [youtube.com]

              https://www.youtube.com/watch?v=9PwQmDcSUow [youtube.com]

              https://www.youtube.com/watch?v=PN0hFGfv-4g [youtube.com]

              --
              People today are educated enough to repeat what they are taught but not to question what they are taught.
              • (Score: 2) by RS3 on Friday May 26 2023, @12:31AM (3 children)

                by RS3 (6367) on Friday May 26 2023, @12:31AM (#1308238)

                Thank you for those java tutorials that happened to use an SDR for the project. :)

                Seriously, thank you. Very interesting. I see that below 30 MHz or so the CPU can do most of the processing- very little analog hardware involved. I'm not sure how sensitive it is.

                I was thinking of receivers more in the GHz range, where you can't sample fast enough to do purely software radio without more analog hardware- amplifier, mixer which gives the "heterodyne" or down-shifted lower frequency that you can then sample and do DSP.

                Here's an interesting project (C++): https://gist.github.com/threeme3/dc6e02a3a1c2ba49e717ac622719e720 [github.com]

                • (Score: 3, Informative) by DannyB on Friday May 26 2023, @02:29PM (2 children)

                  by DannyB (5839) Subscriber Badge on Friday May 26 2023, @02:29PM (#1308316) Journal

                  You must remember the wisdom of SN that Java is very slow.

                  Despite the runtime having what may be the most advanced JIT compiler on the planet, the product of more than two decades of intensive research after IBM opened it up as open source to researchers long ago.

                  Back in September 2019 they removed the maximum heap limitation of 16 Terabytes of RAM. So now the only practical limit -- that I can find anywhere -- is the Linux user space limit of 128 TB. If you use one of these two GCs in Java:
                  * Oracle's ZGC
                  * Red Hat's Shenandoah GC
                  Then even with these enormous heap spaces, you still get a max GC pause time of 1 ms.

                  Another thing about real GC, as opposed to reference counting (hereinafter referred to as "fake" GC), is that you've moved all of the memory management out of the main workload and on to other cpu cores. Thus the primary application doesn't spend any cpu cycles on memory management. You don't have these points where a single dispose triggers an avalanche of deallocation and destructors. The primary Java workload can just malloc away as if memory is infinite, and malloc is designed to be very cheap. The clean up GC crew runs on other cores. Thus Java programmers have no concern about silly things like memory or cpu cycles, or efficiency.

                  Here is the Java Hello World, Enterprise Edition. [github.com] A program truly worthy of being a Java program. One criticism I could offer is that it did not use XML configuration files so that some things could be reconfigured without changing the source code. Things like the actual "hello world" message, or which output class to use. After all, there could be many different possibilities for where you want the Java hello world to go.

                  Here is the Java FizzBuzz Enterprise Edition. [github.com]

                  --
                  People today are educated enough to repeat what they are taught but not to question what they are taught.
                  • (Score: 2) by RS3 on Friday May 26 2023, @06:35PM (1 child)

                    by RS3 (6367) on Friday May 26 2023, @06:35PM (#1308351)

                    Wow thank you for all of that. It's too easy for us humans to hold onto memories of past experiences. I don't think I ever commented that java is slow, but if I was ever to make such a comment, it would be in the context of that specific experience. IE, perhaps java could be fast and efficient, but perhaps that particular java code, or the environment it's running on, is the problem.

                    I'm open-minded enough to know my experience is specific. Most of what little experience I've had with java stuff has been on MS Windows machines. And some years ago, not with gobs of RAM, probably single core CPUs, etc. I don't think I've run, or am not aware of running a java app for at least 8 years now...

                    One sore spot I remember: something I was trying to do that was java code, required a very specific runtime version. If you updated the runtime, as we're supposed to always do, the program would refuse to run. I had several situations where that happened, but one I remember specifically: a Cisco GUI for programming Cisco routers. Cisco IOS CLI is its own world, and I needed to significantly reprogram a Cisco router at the time. Well, needless to say, I didn't have enough time to learn everything about IOS programming and the many many pratfalls of entering things in the wrong order (oh, the router would route, but much more slowly than potentially possible if you knew the far too many secrets to Cisco programming). So I hoped the GUI java app would do the job.

                    Oh yeah- another problem was it would only run through IE, and a very specific version of IE. Hours and hours wasted just trying to get a Windows machine set up with the correct IE and java runtime, make sure to disable _all_ automagic updaters, and even then (days later) something else didn't work (I forget what...)

                    Purely Cisco's fault, of course. But also: you had to have a very specific java app to go with your specific router, and not all routers were supported with a GUI java app.

                    I ended up using a commercially available router with built-in web-based GUI and it worked swimmingly and have never looked back at Cisco IOS (sho run...)

                    All that is to say: why would a java runtime update break a java application? They don't honor backward compatibility / support older APIs?

                    • (Score: 2) by DannyB on Saturday May 27 2023, @10:47PM

                      by DannyB (5839) Subscriber Badge on Saturday May 27 2023, @10:47PM (#1308569) Journal

                      If you have a Java program that requires a very specific runtime version, then I would blame the developer. It seems that the developer would have to go out of their way to make a Java program depend on a specific runtime.

                      As for browsers, it was a bad idea to allow any third party executable extensions such as:
                      * Java Applets
                      * Flash
                      * Microsoft ActiveX
                      * Microsoft Silverlight

                      I have also seen web sites that were written to very specific browsers and versions.

                      In the early 2000s a lot of sites coded to specifically IE, and then IE 6.

                      --
                      People today are educated enough to repeat what they are taught but not to question what they are taught.
              • (Score: 2) by RS3 on Friday May 26 2023, @12:42AM (1 child)

                by RS3 (6367) on Friday May 26 2023, @12:42AM (#1308239)

                Ah yes, that 4th one is very interesting. Notice that it covers 10MHz - 3.5GHz, but the bandwidth is only 30.72MHz. That means the RF analog circuits can handle the entire range (and likely much lower), but the sampling / DSP can only do up to 30.72MHz, so you basically tune somewhere and you have a 30.72MHz range, or "window" into that frequency span (often called a "band"). That matches up with what I was saying before, and makes sense based on what reasonably cheap hardware can do these days. Maybe someday we'll be able to sample and DSP in the GHz ranges! Not likely soon.

                • (Score: 2) by RS3 on Friday May 26 2023, @12:48AM

                  by RS3 (6367) on Friday May 26 2023, @12:48AM (#1308240)

                  A bit more research says the "LimeSDR Mini" has Bandwidth: 61.44 MHz, which is 2x 30.72, so maybe the spec. in the YT video meant the bandwidth is ±30.72MHz. Hmmm- that may be for the LimeSDR, not "Mini"... Either way it's quite useful.

    • (Score: 3, Touché) by crm114 on Wednesday May 24 2023, @04:49PM

      by crm114 (8238) Subscriber Badge on Wednesday May 24 2023, @04:49PM (#1307956)

      LOL

      "Spark plug interference, which is especially bad on EVs"

      which do not have spark plugs. Loved the sarcasm!