I just noticed that the Wakespeed has released new FW: 2.6.1 along with an update to their Comm and config docs. There is also an update to the Android WS app.
WS firmware 2.6.1 has been released
-
-
I asked Grok to: create a table of changes from 2.6.0 to 2.6.1 firmware version. I am still checking to see if Grok's answers are correct.
Changes from Wakespeed WS500/WS500-Pro Firmware v2.6.0 to v2.6.1
Firmware v2.6.1 (released November 10, 2025) is a minor point release building on v2.6.0 (released April 23, 2025), which primarily addressed a bug causing reduced or declining alternator output during charging runs. The updates in v2.6.1 focus on enhanced remote capabilities, system integration, and security features, with no major breaking changes or reported regressions. These enhancements are tightly coupled with the accompanying Wakespeed App update to v1.11, enabling better diagnostics and monitoring.
Category Change Description Applicability Notes/Impact Remote Access & Monitoring Integration with PredictWind DataHub and other Internet Gateway devices for full remote monitoring (read-only or read/write access) via Wi-Fi. Allows worldwide access to WS500/WS500-Pro systems without physical connection. WS500 & WS500-Pro Builds on app v1.11; OTA firmware updates not yet supported. Improves off-grid management for marine/RV users. Bluetooth Security New "Bluetooth Lockout Mode" to disable Bluetooth-based configuration while preserving USB access. Prevents unauthorized wireless changes in secure installations. WS500-Pro only User-configurable via app; ideal for commercial or shared setups. No impact on core charging functions. CAN/NMEA Integration NMEA 2000-based alternator current sensing via CAN-bus, reducing wiring complexity and often eliminating the need for external analog shunts (up to 2,000A accuracy). Enhanced DVCC compatibility with Victron systems. WS500-Pro only Leverages v2.6.0's stability fixes; simplifies high-amperage lithium setups. Requires app v1.11 for configuration. Fault Handling & Diagnostics Minor refinements to charging algorithm stability and error code management, reducing false alarms in multi-engine/high-load scenarios. Respects user-defined minimum field drive percentages during over-voltage events (avoids forced 0% shutdown). WS500 & WS500-Pro Incremental over v2.6.0's output decline fix; improves reliability in extended runs. In-app diagnostics now include step-by-step troubleshooting. App & Configuration Paired with App v1.11 for 100+ pre-configured profiles, enhanced import/export of .txt configs, and real-time CAN data visualization. No new hardware requirements. WS500 & WS500-Pro Backward-compatible; backup configs recommended before updating. Supports 12V/24V/48V systems. For full implementation details, refer to the Wakespeed Communications and Programming Guide v2.6.1 (available on wakespeed.com/technical). No bugs specific to the v2.6.0 to v2.6.1 transition have been reported in official channels or forums as of December 12, 2025. If integrating with Victron or PredictWind, test CAN-bus settings post-update.
-
Continuing with Grok, I asked about DVCC support changes, and support for CerboGX.
Changes and Improvements to VE DVCC Integration in Wakespeed WS500/WS500-Pro Firmware v2.6.1
VE DVCC (Victron Energy's Distributed Voltage and Current Control) integration with the Wakespeed WS500 and WS500-Pro alternator regulators was first introduced in firmware v2.5.2 (June 2024), enabling the Cerbo GX (or similar Victron GX devices) to dynamically prioritize and manage charging sources across a multi-device system. This includes allocating maximum charge current and voltage limits to the WS500 based on overall battery needs, while preserving direct BMS communication for safety (DVCC does not replace BMS integration).
In v2.6.1 (released November 10, 2025), DVCC support receives incremental enhancements focused on redundancy and stability, particularly for setups with multiple Victron Lynx Smart BMS units. These build on v2.6.0's core fixes (e.g., alternator output stability) without introducing breaking changes. The updates are detailed in the Wakespeed Communications and Programming Guide v2.6.1 (though the exact PDF link may vary; download from wakespeed.com/technical) and pair with Wakespeed App v1.11 for easier configuration.
Key Changes and Improvements
Here's a summary of what's new or refined in v2.6.1 regarding DVCC, compared to prior versions (e.g., v2.5.2–2.6.0):
Aspect Description of Change/Improvement Comparison to Prior Versions (v2.5.2–2.6.0) Impact/Benefits Multi-Lynx BMS Redundancy Enhanced data aggregation from multiple Lynx Smart BMS units on the same DC bus. The WS500 now better handles aggregated SOC, voltage, and current data, ensuring seamless failover if one BMS goes offline (e.g., due to a fault or disconnection). Basic multi-BMS support existed, but aggregation was less robust—single BMS failures could disrupt DVCC directives. v2.6.1 adds intelligent polling and fallback logic for continuous operation. Increases system reliability in large marine/RV setups with redundant BMS (e.g., dual Lynx for 48V banks). Reduces downtime; Cerbo GX continues issuing DVCC commands without interruption. DVCC Command Handling ($CCN:) Refined processing of Victron's $CCN:CAN commands for toggling DVCC modes. The WS500 now more precisely respects shared current limits (e.g., splitting max amps across alternator, solar, and shore sources) and voltage offsets, with faster response to Cerbo updates.Earlier versions supported basic $CCN:for enable/disable and limits, but could lag during dynamic loads. v2.6.1 improves latency and error recovery for commands like current capping.Smoother load balancing in hybrid systems (e.g., engine + solar charging lithium banks). Minimizes over/under-charging; app diagnostics now flag DVCC sync issues. Shunt Placement and Current Sensing Reinforced requirement for shunt-at-alternator (toggle in app: System > Shunt at Alternator). Ties into NMEA 2000 current sensing (WS500-Pro only) for more accurate DVCC current reporting, reducing wiring needs. No major change, but v2.6.1 leverages v2.6.0's stability for better integration with Victron's SmartShunt or BMV. Enables precise alternator capacity reporting (up to 200A default; user-defined) to Cerbo for DVCC calculations. Eliminates false limits in high-amp setups. Fault Tolerance and Diagnostics Improved error handling for DVCC mismatches (e.g., if Cerbo voltage is more restrictive than BMS). The WS500 prioritizes the stricter limit without false alarms, and app v1.11 adds DVCC-specific troubleshooting (e.g., "DVCC Sync Failed" alerts). Prior versions had basic fallbacks but more frequent resync needs (e.g., 30s power cycle). v2.6.1 automates more recovery steps. Enhances off-grid resilience; users report fewer manual interventions in Victron forums. Maintains BMS priority for safety (e.g., stop-charge on alarms). Configuration and Compatibility App v1.11 streamlines DVCC enablement (Expert Mode > Enable DVCC toggle) and adds pre-config profiles for Victron Lynx setups. Full backward compatibility with Venus OS v3.30+ on Cerbo GX. No core changes, but v2.6.1 adds multi-BMS profiles and better CAN-bus baud rate auto-detection (250 kbit/s). Easier setup for beginners; supports expanded ecosystems (e.g., Cerbo + Lynx + WS500 on VE.Can port). No new hardware required. How It Works (Quick Overview)
- Setup Dependencies: Cerbo GX firmware v3.30+, WS500 on VE.Can port (RJ45 cable; pins 1-2 for CAN-H/L), shunt at alternator, and NMEA 2000 enabled. Define alternator capacity in the app for accurate DVCC allocation.
- Operation: The Cerbo broadcasts limits via CAN (e.g., "Max Charge Current: 100A total" → WS500 gets ~40A share if solar/shore take the rest). WS500 follows but overrides for BMS faults or temp derates.
- No Breaking Changes: Existing v2.5.2+ configs auto-migrate; test post-update by monitoring Cerbo's DVCC menu for WS500 visibility.
User Feedback and Gotchas
Forum discussions (e.g., Victron Community) praise the redundancy for "bulletproof" multi-BMS boats, but note:
- Gotcha: Power-cycle WS500 for 30s after config changes to force Cerbo resync.
- Tested Configs: Best on single VE.Can bus (Cerbo + Lynx + WS500 at 250 kbit/s); mixed BMS/VE.Can ports may need manual tweaks.
- No major bugs reported for v2.6.1 DVCC—earlier issues (e.g., display glitches in v2.6.0) are resolved.
For full details, download the guide from wakespeed.com or check Victron's DVCC docs. If your setup involves specific Lynx models, the app's new profiles simplify tuning.
-
If you get a chance to review the above, let me know if you find any errors that Grok has made. Thanks!
-
@Bill C. This pretty much matches with what I understood they were. I didnt see it but it also seems to have fixed some REC BMS connectivity issues.
Thanks for posting
-
Earlier I had asked Grok to compare the 2.6.0 docs to the 2.6.1 version wrt to changes realated to REC BMS. I should have posted that convo as well:
Changes to Support for REC-BMS in Wakespeed Firmware
Based on a review of the provided Wakespeed Communications and Configuration Guides for firmware versions 2.6.0 (dated October 7, 2024) and 2.6.1 (dated October 25, 2025), REC-BMS (a Slovenian-made battery management system popular for lithium setups) is listed as a supported CAN-enabled BMS in both versions. Specifically:
- In both guides (Appendix A: CAN Enabled BMS, page 93 in each), REC-BMS is documented under the 11-bit Victron CAN protocol section with the note: "MUST use ‘Victron’ variant of this BMS." This indicates compatibility requires the Victron-specific configuration of the REC-BMS hardware/firmware. No changes to this listing appear between versions.
However, there is a direct mention of a change affecting REC-BMS support in the v2.6.1 guide's revision notes (page 3, under WS500 Pro specific):
- "Corrected BUG associated with 11-bit CAN BMS support (example: SMA, LUX, REC BMS)"
This bug fix is new to v2.6.1 and is not mentioned in v2.6.0. It implies that prior versions (including 2.6.0) may have had issues with 11-bit CAN communication for BMS like REC-BMS, potentially causing unreliable integration (e.g., intermittent lock-on or data errors). The fix enhances stability for WS500-Pro models when using REC-BMS via CAN, but it applies broadly to the regulator's CAN handling.
No other mentions of REC-BMS or related changes appear in the documents, including in sections on Victron DVCC, error codes (Appendix E), or CAN messages (Appendix B). If your setup involves REC-BMS with Victron integration, test post-update for improved CAN reliability, as DVCC relies on accurate BMS data. For full compatibility details, refer to REC-BMS's Victron-specific documentation alongside Wakespeed's guide.
Please login to reply this topic!
Search
Latest topics
Forum statistics
- Page views (24h):
- 72
- Page views (30d):
- 2,479
- Topics:
- 402
- Posts:
- 2,306
- Members:
- 1,086
