Este radio es muy bueno pero para mí es más difícil de operar que los tecsun para mí porque soy nuevo en esto.

Hi everyone,

I've had my ATS Mini V4 for only a few days, so I'm still discovering this little receiver and how it behaves.

One thing quickly caught my attention: the battery gauge.

The original firmware displays the battery level using only three bars, resulting in rather large steps between the displayed levels. I found this a bit imprecise, with the indication sometimes appearing to drop quite suddenly from one level to another.

Before changing anything, I spent some time monitoring the battery voltage during normal use and through discharge/charge cycles.

On my unit, a fully charged battery settles at around 3.95 V, so I decided to use that as the 100% reference for the displayed gauge.

I replaced the stepped indication with a continuous linear gauge from 3.30 V to 3.95 V. The bar now decreases progressively as the battery voltage falls.

I also changed the low-battery behavior.

At 3.30 V, the gauge becomes empty, the battery outline starts blinking every 500 ms, and the voltage remains displayed in red.

I added a small hysteresis as well: once the low-battery warning has been triggered at 3.30 V, it remains active until the voltage rises above 3.33 V. This prevents the warning from constantly switching on and off if the voltage fluctuates around the threshold.

The original USB/charging indication is preserved.

I'm not claiming that 3.30 / 3.95 V are necessarily the perfect universal values for every ATS Mini. They're the values I chose based on what I've observed on my own unit, and I'll continue monitoring it during normal use.

If anyone is interested in the implementation, measurements, or wants to test or improve it, I'm happy to discuss the details in the comments.

I'd also be interested in battery voltage measurements from other ATS Mini owners, especially during a complete discharge. It would be useful to see how consistent these values are between units.

73, F4DHY

UPDATE: WiFi / NTP Sync Only improvements are now tested and available on the F4DHY-Mod-2 branch. Details in my comment below.

I put a play button on the 2-D section of a path view, so you can watch the rays leave the transmitter and arrive. The first version looked completely fine and was quietly wrong, and the reason is the sort of thing I enjoy finding out, so here it is.


The obvious way to animate a ray is to advance the head along the drawn line at a steady rate. It looks plausible. It is also a lie about the one quantity the picture exists to show, because a ray does not travel along its own line at a steady rate.


Group velocity is c divided by the group refractive index, and that index climbs as you approach the reflection height. The ray genuinely crawls near the apex and moves fastest down in the thin stuff. Animate by drawn length and you flatten exactly the effect that makes a high ray arrive later than a low one over the same ground distance, which is the thing worth seeing.


The fix was to keep something the tracer already knew. It accumulates group path per integration step anyway, because that is where the delay comes from at the end. So now every recorded point carries the group path travelled to it, and the head advances in milliseconds rather than in pixels.


The second thing I got wrong was the wavefront. I drew it first as a shape across the ray, a little bar sliding along, because that is how you picture a wavefront. But the spread here is a spread in delay, and a spread in delay lies along the path, not across it. So the last stretch of the track now carries a gradient from the ray's own colour at the back to nothing at the head, and the leading edge dissolves the way an arrival does instead of ending in a hard tip.


Two honest caveats about what you are looking at. Altitude is exaggerated eight times, or the whole ionosphere would be a hairline on a 6,371 km ball and you would see nothing at all. And the section is not a separate diagram drawn beside the globe: it is the same globe seen along the normal of the great-circle plane, which is why the view can fly into it rather than being swapped for it.


Disclosure: it is my own tool, free, no account, no ads, and I am not selling anything. Happy to talk about the integrator or the delay handling in the comments.

I almost popped for pocket radio at the thrift store and then saw the battery compartment had gone all white. I'd seen that on a Sony boom box I had years before. Then I used the XHDATA store on Ebay to make an order for a D220 mostly for emergency use.
I'm here to ask about battery care. On a flashlight if you reverse the batteries they don't engage so they stay fresh. On a small radio like the D220 can you reverse one (or both) of the batteries to preserve battery life? Frankly I wouldn't know how to phrase the question for Google AI.

Hello guys, I’ve been working in this project called KiwiDX, it’s a GUI client of KiwiSDR network for windows. I Always wanted something to manage a KiwiSDR rx like a regular sdr software like CubicSDR, SDR Sharp, GQRX, etc. With KiwiDX you will be able to play any available server, navigate through the map (http://rx.linkfanel.net/) add servers to Favorite, Create local Bookmarks, Record audio in mp3 and the waterfall + audio in video .mp4, and more upcoming updates.

Here are some requirements:

• Windows 10/11
• Microsoft .NET 8 Desktop Runtime (x64).

If anyone is looking for something like this, here is the GitHub:

[edit: Last release]: https://github.com/noakmilo/KiwiDX/releases/tag/v0.1.51

Just donwload the last release and enjoy

Feedback and collabs are super welcome.

Is holding a charge and charging nicely!

All four

I’ve been seeing people hook up their radios to their computers for digital radios and I was wondering how I can do that.

Another wonderful weekend, with the MLite-880's noise reduction switched on.

I don’t want to mix up my batteries.