#chargecontroller
Live, measured metrics for the hashtag #chargecontroller from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #chargecontroller
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.online (Mastodon public tags API) · fetched 2026-11-18 02:52 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-11-18 02:52 UTCNo related tags with measured usage found for #chargecontroller.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-18 02:52 UTCEverything below is measured over the latest 19 public posts (spanning ~52227 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (17) · German (1) · British English (1)
Avg boosts / post: 0.3
Top of the latest posts
I got a deal on this on Ebay a while back. It's a decent MPPT charge controller, a bigger one than what I had. It will do 25 A. You can tweak settings over MODBUS, and I have a Perl script I used for the other controller to change voltages
I am puzzled why they say not to use the load terminals? And almost every battery I've ever seen has two connections Positive and Negative, no input and output. I can obviously connect the load in parralel with the battery connection. Any c
I'm developing an MPPT solar chargecontroller. My partner thinks this image of the board is already a work of art in itself. I tend to agree. #solar #PV #ChargeController #MPPT #DIY #electronics #microcontroller #PIC
#chargecontroller across platforms
every network with a public tag surfaceFollow #chargecontroller straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/chargecontroller