tmzf5455/EVCS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Plafond de charge pv_boost 180 -> 250 A (parc assaini, BMS autorise 250)

Browse Source 
Le 180 A venait de nous (monte 130->150->180 le 13/09, §64), pas du BMS qui
autorise 250. Il bridait reellement : PV 10,6 kW, excedent ~187 A que la
batterie prendrait, plafonnee a 180. Parc sain (cellules pack 2 a 3-6 mV) : on
prend toute la marge, direct a 250 sur decision du proprietaire.
golden-acm 20/20 (2 attendus 180->250), mutation : retour 180 -> 2 echecs.
patch rejouable tools/patch-20260920b-boost-250a.mjs.
⚠️ Surveillance pack 2, surtout module rang 5 (K220803C30160323, le plus ancien).
Pack 1 (US5000) hors surveillance continue (2e cable en commande).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GwpFpy2aQ2rJok6tNQSbVj
This commit is contained in:
Tallagrand Thierry
2026-09-20 14:01:16 +02:00
parent 4aaabb7e0f
commit 39a4444fec
3 changed files with 17 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tests/golden-acm/scenarios.mjs
View File

@@ -164,7 +164,7 @@ export const scenarios = [
label: 'Jour, SOC 60 sous 80 : capture PV maximale, 180 A a 51,5 V (releve du 14/09 : la batterie butait sur 150)',
time: h(ETE, '11:00'),
overrides: { ...parcNeuf, soc_percent: '60', pv_power_w: '4000' },
expect: { mode: 'day_pv_boost', profil: 'pv_boost', courantA: 180, tensionV: 51.5 },
expect: { mode: 'day_pv_boost', profil: 'pv_boost', courantA: 250, tensionV: 51.5 },
},
{
id: 'acm-jour-mid',
@@ -219,7 +219,7 @@ export const scenarios = [
overrides: { ...parcNeuf, soc_percent: '60', override_enabled: 'on',
override_profile: 'manual', override_current_a: '12', override_voltage_v: '50.0',
override_until: '2026-07-15 09:00:00' },
expect: { overrideActif: false, mode: 'day_pv_boost', courantA: 180 },
expect: { overrideActif: false, mode: 'day_pv_boost', courantA: 250 },
},
// ------------------------------------------------------------ publication

14
tools/patch-20260920b-boost-250a.mjs Normal file
View File

@@ -0,0 +1,14 @@
// Plafond de charge pv_boost 180 -> 250 A (20/09/2026), parc assaini.
// Le 180 A venait de nous (monte 130->150->180 le 13/09, §64), pas du BMS qui
// autorise 250. Cellules pack 2 a 3-6 mV, parc sain : on prend toute la marge.
// ⚠️ Cellules pack 1 (US5000) hors surveillance continue — proprietaire a
// autorise le 250 direct, surveillance du pack 2 (surtout module rang 5, le
// plus ancien : K220803C30160323).
import { readFileSync, writeFileSync } from 'node:fs';
const f = 'workflows/victron-auto-charge-manager-v1.2.json';
const s = readFileSync(f, 'utf8');
const avant = 'pv_boost: { current_a: 180, voltage_v: 51.5 }';
const apres = 'pv_boost: { current_a: 250, voltage_v: 51.5 }';
if (s.split(avant).length - 1 !== 1) { console.error('motif pv_boost 180 non unique/absent'); process.exit(1); }
writeFileSync(f, s.replace(avant, apres));
console.log('pv_boost 180 -> 250 A applique');

2
workflows/victron-auto-charge-manager-v1.2.json
View File

File diff suppressed because one or more lines are too long