Beiträge von dannyb28

    Hi Chris,


    Thanks very much for getting back to me. Your experience is really interesting, particularly that you never got the Enyaq working reliably but your Polestar 4 now works successfully with the same Sigenergy EVDC V2X setup.


    I've found the records from my original test on 23 July when my Enyaq was running 6.0.0. That test was actually carried out on a friend's Sigenergy system, also using the 12 kW DC bidirectional charger.


    V2H established and discharged at 82% SOC for 1 minute 44 seconds, transferring 0.04 kWh. Unfortunately, I then deliberately pressed Stop because I believed I'd proved it was working!


    I really wish I'd left it running longer. I had no reason at the time to think that another few seconds might have been important.

    The reason that's particularly frustrating is that I've now done extensive repeat testing on my own Sigenergy system. The car consistently completes the handshake, establishes V2H and genuinely discharges for approximately 1 minute 50–55 seconds, with DC export from the car reaching as high as 12.5 kW. It then stops.


    Sigenergy consistently records these current sessions as:

    "Vehicle actively stop discharging."

    I've reproduced it at different power levels and at SOC as low as 43%, so it isn't simply because the battery is nearly full.


    I've noticed another potentially important behaviour. V2H only seems to establish when the vehicle's requested/target SOC is higher than its current battery SOC. For example, with the battery at 90% and the charge target deliberately set to 80%, the DC/V2X discharge wouldn't establish at all. Raise the target above the current SOC and it will establish, start exporting power, and then the vehicle terminates it roughly 1m50–1m55 later.

    My working theory — and it is only a theory until Škoda/Sigenergy examine the protocol logs — is that the car may initially establish the connection expecting a DC charging session, permits reverse power flow, and then subsequently terminates when the session state/energy direction doesn't meet whatever condition it's expecting.

    Mine is a Model Year 2027 Enyaq Coupé vRS, registered in 2026, and it's one of the newer cars with the 230V three-pin/V2L socket in the boot.


    I've approached both Sigenergy and Škoda with all of this evidence and asked them to investigate the protocol logs.


    I've also arranged a test drive of a Hyundai IONIQ 5 tomorrow. Assuming the dealership is happy for me to do it, I'm going to connect that to my Sigenergy system and see whether it can maintain V2H. If it does, that should at least demonstrate that the same Sigenergy installation can sustain V2H with another vehicle and narrow down where the compatibility problem lies.


    I've also seen Škoda's own V2H demonstration material showing it working on an earlier software generation with Škoda's supported DC equipment. Whether there's a charger compatibility issue, software issue or potentially some difference with UK vehicles I'm not sure yet.


    Your older Enyaq experience is therefore particularly interesting, because it suggests this may go further back than 6.0.1.

    I'd definitely be interested in having a chat and comparing exactly what your Enyaq used to do before you moved to the Polestar.


    Cheers,

    Danny Glasgow, Scotland

    Hi Chris, hope you don't mind me contacting you about your post regarding V2H with your Enyaq and Sigenergy DC charger.


    I've got a MY27 Enyaq Coupé vRS with a Sigenergy DC bidirectional charger and I'm seeing remarkably similar behavior to what you described.


    V2H establishes successfully and the car starts discharging, reaching around 4.5–4.7 kW, but then almost without fail at around 1 minute 40–1 minute 55 seconds I can physically hear the HV contactor in the car open and the discharge stops.


    Sigenergy records the session as “Vehicle actively stop discharging.” One recorded session lasted 1m54s and another 1m50s.


    Interestingly, I previously tested V2H successfully before my car's software was updated, whereas I'm now running 6.0.1 and having this problem. Škoda and Sigenergy are both investigating.


    I came across your post describing your Enyaq stopping V2H after roughly 90 seconds and thought the similarity was too close to ignore.


    Did you ever get to the bottom of yours or find a solution? In particular, did Sigenergy or Škoda ever identify why the vehicle was terminating the discharge session, or make any software/configuration change that fixed it?


    Any information would be hugely appreciated, even if you never managed to resolve it.


    Cheers,

    Danny – Glasgow, Scotland