Files
V2GDecoderC/Port/dotnet/test1_pure_decoded.xml
chiDT d5263abab0 feat: Perfect C# structure alignment with VC2022 for exact debugging
Major architectural refactoring to achieve 1:1 structural compatibility:

🏗️ **VC2022 Structure Replication**
- Iso1EXIDocument: 1:1 replica of VC2022 iso1EXIDocument struct
- DinEXIDocument: 1:1 replica of VC2022 dinEXIDocument struct
- Iso2EXIDocument: 1:1 replica of VC2022 iso2EXIDocument struct
- All _isUsed flags and Initialize() methods exactly matching VC2022

🔄 **VC2022 Function Porting**
- ParseXmlToIso1(): Exact port of VC2022 parse_xml_to_iso1()
- EncodeIso1ExiDocument(): Exact port of VC2022 encode_iso1ExiDocument()
- Choice 76 (V2G_Message) encoding with identical logic
- BulkChargingComplete ignore behavior preserved

 **Call Sequence Alignment**
- Old: EncodeV2GMessage() → direct EXI encoding
- New: EncodeV2GMessage() → Iso1EXIDocument → EncodeIso1ExiDocument()
- Exact VC2022 call chain: init → parse → encode → finish

🔍 **1:1 Debug Comparison Ready**
- C# exiDoc.V2G_Message_isUsed ↔ VC2022 exiDoc->V2G_Message_isUsed
- Identical structure enables line-by-line debugging comparison
- Ready for precise 1-byte difference investigation (41 vs 42 bytes)

📁 **Project Reorganization**
- Moved from csharp/ to Port/ for cleaner structure
- Port/dotnet/ and Port/vc2022/ for parallel development
- Complete build system and documentation updates

🎯 **Achievement**: 97.6% binary compatibility (41/42 bytes)
Next: 1:1 debug session to identify exact byte difference location

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-10 22:01:08 +09:00

25 lines
869 B
XML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" encoding="UTF-8"?>
<CurrentDemandRes>
<ResponseCode>FAILED_ChargingProfileInvalid</ResponseCode>
<DC_EVSEStatus>
<NotificationMaxDelay>66</NotificationMaxDelay>
<EVSENotification>None</EVSENotification>
<EVSEStatusCode>EVSE_EmergencyShutdown</EVSEStatusCode>
</DC_EVSEStatus>
<EVSEPresentVoltage>
<Multiplier>-3</Multiplier>
<Unit>s</Unit>
<Value>16944</Value>
</EVSEPresentVoltage>
<EVSEPresentCurrent>
<Multiplier>-2</Multiplier>
<Unit>V</Unit>
<Value>3086</Value>
</EVSEPresentCurrent>
<EVSECurrentLimitAchieved>False</EVSECurrentLimitAchieved>
<EVSEVoltageLimitAchieved>False</EVSEVoltageLimitAchieved>
<EVSEPowerLimitAchieved>False</EVSEPowerLimitAchieved>
<EVSEID>81 0 @<40></EVSEID>
<SAScheduleTupleID>4</SAScheduleTupleID>
</CurrentDemandRes>