Wattcycle 48v v2.5 server rack communications to solar-assistant?

Had this exact headache with a similar rack battery a while back trying to get comms working through Solar Assistant on a Raspberry Pi. The short answer is: it depends entirely on which BMS protocol the Wattcycle is actually broadcasting.

Most of these Chinese-manufactured server rack units claim RS485 with a "standard" protocol but in practice they're often running a proprietary variant of PACE BMS or SEPLOS under the hood. Worth pulling the manual and checking whether it explicitly states JK, Pylontech-compatible, or something else entirely — Solar Assistant supports a decent list but you need the exact match.

A few things worth trying:

• In Solar Assistant, cycle through the battery protocols manually rather than relying on auto-detect. Sometimes it picks the wrong one and just silently fails
• Check your RJ45 pinout very carefully — these rack batteries are notorious for non-standard wiring even when the connector looks identical
• Grab a USB-to-RS485 adapter and use something like PuTTY or minicom on the Pi to sniff the raw serial output before Solar Assistant even comes into the picture

My own setup runs a Victron Cerbo GX rather than Solar Assistant, so I went through the DVCC route, but I know several people on here have cracked Wattcycle comms with SA successfully — I think the thread in the main Solar section mentions a custom config file workaround.

What inverter are you running alongside it? That might affect how Solar Assistant handles the whole communication stack. Also, which version of Solar Assistant firmware are you on? There were some protocol additions in recent builds that might be relevant here.

Would be good to get a definitive answer pinned for this battery — seeing the question crop up fairly regularly.

@OldSparky52 raises the key point — protocol compatibility is basically the whole game here.

With Solar Assistant, the Wattcycle 48v v2.5 might respond to PACE BMS or JBD protocol depending on firmware revision. Worth trying both before you start questioning your life choices at 11pm with a multimeter

Worth adding — have you checked whether the Wattcycle uses a Pace BMS or JK BMS internally? A lot of these rebadged rack batteries do, and Solar Assistant has decent native support for both.

On my cabin setup I'm running Fogstar Drift cells with a JK BMS and the RS485 comms to Solar Assistant were pretty painless once I had the right USB-RS485 adapter (the cheap ones caused endless headaches — ended up going with a proper FTDI chipset one).

Check Solar Assistant's device list first — if your exact model isn't there, look for the underlying BMS brand instead. Sometimes you just select that and it works straight away.

Also double-check your baud rate settings. Default is often 9600 but some units ship at 115200.

@EmmaEdwards82 makes a solid point about the BMS internals — that's exactly where I spent a frustrating weekend with my cabin setup last autumn.

What finally cracked it for me was grabbing a cheap USB-to-RS485 adapter and connecting directly to the battery's comms port, then running screen at 9600 baud to see what was actually being spat out. The raw protocol tells you everything — Pace BMS has a distinctive packet header that's pretty unmistakable once you've seen it.

Solar Assistant's device list is your friend here too. If Wattcycle isn't listed directly, try "Pylon compatible" as a fallback — a surprising number of these Chinese rack batteries respond correctly to that handshake even when they're not labelled as such.

Victron kit plays nicely once comms are sorted, but getting to that point is half the battle.

@EmmaEdwards82 and @Tel1961 both touching on the right area — BMS identification is the crux of it.

One thing I'd add from my own narrowboat setup: even once you've identified the BMS, the RS485 pinout on these rebadged units is frequently wrong in the documentation. I wasted an embarrassing amount of time before I actually probed the RJ45 pins manually with a multimeter and compared against the Pace BMS reference pinout floating around on GitHub.

Solar Assistant's device list does include several Pace variants — worth trying each one systematically if you're unsure of the exact revision. The v2 and v2.5 Wattcycle units seem to behave differently in my experience, possibly different BMS revisions mid-production run.

Also double-check your USB-to-RS485 adaptor — cheap CH340-based ones can cause intermittent dropouts that look like protocol mismatches but aren't.