Activity for OpenV2G

Sebastian Bode modified ticket #32

Sebastian Bode — Mon, 26 Oct 2026 09:52:13 -0000

Integer underflow in decodeInteger32/64

Sebastian Bode modified ticket #32

Sebastian Bode — Mon, 26 Oct 2026 09:51:41 -0000

Integer underflow in decodeInteger32/64

Sebastian Bode modified ticket #32

Sebastian Bode — Mon, 26 Oct 2026 09:51:09 -0000

Integer underflow in decodeInteger32/64

Sebastian Bode posted a comment on ticket #32

Sebastian Bode — Mon, 26 Oct 2026 09:50:20 -0000

Fixed in revision r127 and released in OpenV2G 0.9.7. The unsigned subtraction in the original range check caused decoding of −1 to fail. The correct check is uint32 <= INT32_MAX (and analogously for 64-bit values), so that the minimum signed value is also accepted. The signed-value reconstruction was adjusted to avoid overflow. Thanks for reporting this issue! Release: https://sourceforge.net/projects/openv2g/files/release/OpenV2G_0.9.7/

OpenV2G released /release/OpenV2G_0.9.7/README.txt

OpenV2G — Mon, 26 Oct 2026 09:47:03 -0000

OpenV2G released /release/OpenV2G_0.9.7/OpenV2G_0.9.7.zip

OpenV2G — Mon, 26 Oct 2026 09:47:03 -0000

Sebastian Bode committed [r129] on Code

Sebastian Bode — Mon, 26 Oct 2026 09:41:21 -0000

release: tag version 0.9.7

Sebastian Bode committed [r128] on Code

Sebastian Bode — Mon, 26 Oct 2026 09:40:35 -0000

docs: update release notes for version 0.9.7

Sebastian Bode committed [r127] on Code

Sebastian Bode — Mon, 26 Oct 2026 09:38:17 -0000

Fixes https://sourceforge.net/p/openv2g/tickets/32/

Siebren W created ticket #32

Siebren W — Sun, 25 Oct 2026 17:39:23 -0000

Integer underflow in decodeInteger32/64

Peter Lawrence posted a comment on ticket #29

Peter Lawrence — Sat, 25 Oct 2025 18:08:15 -0000

Sorry for the delay in responding. Thank you for mulling over this particular library usage artifact. The approach that I wound up using was to omit all the init_ calls and use memset exclusively. As long as link-time optimization is employed, the executable is smaller without the init_ code (without any code changes to the OpenV2G library), and a single memset effectively does a superset of init_ functionality in less code space. The memset is cheap in terms of CPU usage, and it ensures that only...

Daniel Peintner modified ticket #29

Daniel Peintner — Tue, 21 Oct 2025 08:49:59 -0000

corruption unless complete zero-ize of struct iso1EXIDocument output

Daniel Peintner posted a comment on ticket #29

Daniel Peintner — Tue, 21 Oct 2025 08:49:30 -0000

Since I have not received any feedback, I assume that the answer was/is satisfactory. In summary, it is simply the case that arrays (for character strings, bytes, etc.) must be initialized manually. However, this is also standard practice in C.

Daniel Peintner posted a comment on ticket #29

Daniel Peintner — Wed, 24 Sep 2025 10:04:46 -0000

Hi, I checked your code and I think there is one missing piece. OpenV2G does not (properly?) initialize datastructures for bytes and string (internal struct in struct) and expects the user to set the data. Hence according to my testing memset(&exiOut, 0, sizeof(exiOut)); is not needed. Remving it does not show any problem with your code. IF you initialize byte and string arrays.. like you do in exiOut.V2G_Message.Header.SessionID.bytesLen = 8; memset(exiOut.V2G_Message.Header.SessionID.bytes, 0xA5,...

Daniel Peintner posted a comment on ticket #29

Daniel Peintner — Fri, 19 Sep 2025 07:27:55 -0000

Hi, Thank you for reporting the problem. For now I did not have more time than running your demo. I can't really understand why the init_ methods don't work as expected for union. I'll have to take a closer look at the code. for example https://sourceforge.net/p/openv2g/code/HEAD/tree/trunk/src/iso1/iso1EXIDatatypes.c#l44 sets the XXX_isUsed to zero which should prevent to run into other union memory parts. 🤔 Mhhh, I hope I can find time to look into soon... unless you beat me with the explanation....

Anonymous created ticket #29

Anonymous — Sun, 14 Sep 2025 22:03:34 -0000

corruption unless complete zero-ize of struct iso1EXIDocument output

OpenV2G released /release/OpenV2G_0.9.6/README.txt

OpenV2G — Tue, 14 Jan 2025 13:55:03 -0000

OpenV2G released /release/OpenV2G_0.9.6/OpenV2G_0.9.6.zip

OpenV2G — Tue, 14 Jan 2025 13:55:03 -0000

Daniel Peintner committed [r126] on Code

Daniel Peintner — Tue, 14 Jan 2025 13:52:06 -0000

refactor: add tag 0.9..6

Daniel Peintner committed [r125] on Code

Daniel Peintner — Tue, 14 Jan 2025 13:50:00 -0000

refactor: iso90

Daniel Peintner committed [r124] on Code

Daniel Peintner — Tue, 14 Jan 2025 13:38:17 -0000

docs: update docs for version 0.9.6

Daniel Peintner committed [r123] on Code

Daniel Peintner — Tue, 14 Jan 2025 13:30:05 -0000

fix: overflow when decoding large integer numbers

Daniel Peintner committed [r122] on Code

Daniel Peintner — Tue, 14 Jan 2025 11:34:22 -0000

docs: update

Daniel Peintner posted a comment on ticket #27

Daniel Peintner — Fri, 22 Nov 2024 15:57:03 -0000

Hi, The code uses ANSI-C and should run an almost any platform. Anyhow, I think it is best to just try it out. wr.t. IDE you are free to choose your prefered IDE. We provide makefiles also. -- Daniel

Daniel Peintner posted a comment on a wiki page

Daniel Peintner — Fri, 22 Nov 2024 15:55:07 -0000

You can use your prefered IDE. There is a make file also.

Parth Tivedi created ticket #27

Parth Tivedi — Thu, 21 Nov 2024 09:47:35 -0000

Compiler or IDE required to compile and run the code

Parth Tivedi posted a comment on a wiki page

Parth Tivedi — Thu, 21 Nov 2024 09:42:15 -0000

Hi Daniel, Thanks for making this work open source. I have download this code. but will you please mentioned which IDE or Compilrer required to compile this code? On which platform this code is written for?

Daniel Peintner posted a comment on ticket #26

Daniel Peintner — Tue, 09 Jul 2024 12:08:59 -0000

The XSDs we used for ISO2 version in OpenV2G where an intermediary version on the way to -20. It was used for TestFests only (as far as I know). Hence, I don't know whether this kind of schema can be acquired at ISO. The final version ISO 15118-20:2022 can be acquired at ISO, as usual. Note: openV2G implementation for ISO 15118-20:2022 will not be available as Open Source.

Jeffrey Johannessen posted a comment on ticket #26

Jeffrey Johannessen — Mon, 08 Jul 2024 18:13:07 -0000

Daniel, thanks for the information. How would I go about acquiring the XSD file?

Daniel Peintner posted a comment on ticket #26

Daniel Peintner — Tue, 02 Jul 2024 11:57:59 -0000

Hi, Sorry, we are not allowed to share XSDs that are part of the standard and need to be acquired. Unfortunately, there is no easy way to get the XSDs out of the source code (at least not in a 100% manner) -- Daniel

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Tue, 02 Jul 2024 08:00:39 -0000

duplicate of https://sourceforge.net/p/openv2g/tickets/26/

Daniel Peintner posted a comment on ticket #25

Daniel Peintner — Tue, 02 Jul 2024 07:54:45 -0000

OpenV2G uses static memory allocation (no malloc is used) with a fixed set of entries for arrays etc. Everyone using the library (source code) can configure it according to the needs, see #define XYZ_ARRAY_SIZE 5 entries in https://sourceforge.net/p/openv2g/code/HEAD/tree/trunk/src/iso1/iso1EXIDatatypes.h Defining the possible maximum for each would result in a huge static memory allocation. I hope this helps to understand the rational. -- Daniel

Jeffrey Johannessen posted a comment on discussion Open Discussion

Jeffrey Johannessen — Fri, 28 Jun 2024 20:41:08 -0000

Hi, I am working with Vector to develop a charging simulator based on their Emobility Charging System. The system works with ISO15118-20 and ISO15118-2:2013. It does not work with the 2018 draft for ISO15118-2. In order to develop the simulator, they need the XDS files for the draft version. Unfortunately, our latest EV offering was developed using the open V2G platform; we must be able to test this but cannot since the charging simulator does not support openV2G. Would it be possible to get the...

Anonymous created ticket #26

Anonymous — Fri, 28 Jun 2024 20:35:39 -0000

XSD Schema Files for Draft 2018 ISO15118-2

Anonymous created ticket #25

Anonymous — Tue, 25 Jun 2024 17:44:40 -0000

ChargeParameterDiscoveryRes - Schedule array size greater than 5

Jordan Sautreau modified a comment on discussion Open Discussion

Jordan Sautreau — Mon, 27 May 2024 12:42:12 -0000

Hi Daniel, I am using iso1 codec. The issue is not encoding/decoding directly but on computing the signature. The payload is encoded and received by a server using exificient. When receiving the request, the server decodes successfully the request. Then it has to encode the payload (without the signature) to check if the signature is correct. So it encodes back the content to compute a hash. That is when we face the issue because the payload is different (1 byte more for each root certificate) so...

Jordan Sautreau posted a comment on discussion Open Discussion

Jordan Sautreau — Mon, 27 May 2024 12:32:39 -0000

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Mon, 27 May 2024 12:07:28 -0000

Do you have an example XML (or EXI) message that you would like to encode and can point us to to where something goes wrong. Honestly I doubt that there is a problem since it is used for a very long time now without any issues. Note: please also let us know what codec you are using (e.g. iso1) etc Thanks!

Jordan Sautreau posted a comment on discussion Open Discussion

Jordan Sautreau — Fri, 24 May 2024 12:11:37 -0000

Hello, We have found an issue in the encoding. It indeed adds a byte because of the encoding on 7 bits and 1 bit more to indicate if the encoding is done or not. For example, if the serial number is 9: This is 0b00001001 in binary. So we need 4 bits to encode it. Then openv2g considers that we need a byte, then 8 bits. As the bits are encoded 7 by 7, openv2g considers that we need 2 bytes to encode this number. We have patched this and tested it sucessfully. We might share a fix proposal for this...

Daniel Peintner posted a comment on ticket #24

Daniel Peintner — Tue, 12 Mar 2024 07:14:52 -0000

Hi, Is there any protocol version after urn:iso:15118:2? As mentioned on our homepage the most recent versions will not be available as Open Source anymore. see https://openv2g.sourceforge.net/ -- Daniel

Anonymous created ticket #24

Anonymous — Mon, 11 Mar 2024 13:54:19 -0000

Questions About the ISO15118 Protocol

Daniel Peintner modified ticket #22

Daniel Peintner — Wed, 14 Feb 2024 14:56:06 -0000

Invalid test data used in main_example.c?

Daniel Peintner posted a comment on ticket #22

Daniel Peintner — Wed, 14 Feb 2024 14:55:49 -0000

fixed with https://sourceforge.net/p/openv2g/code/121/

Daniel Peintner committed [r121] on Code

Daniel Peintner — Wed, 14 Feb 2024 14:55:09 -0000

fix: use minimum length of 7

Gravis posted a comment on ticket #23

Gravis — Tue, 06 Feb 2024 17:11:12 -0000

Yes, it's in src/test/main_example.c. Not to worry though because I'm not using it for production purposes, I'm merely debugging my own dynamic EXI encoder by comparing outputs. Comparing the I/O for the example code seemed like a nice starting point and thusly I'm running into bugs in the example code.

Daniel Peintner posted a comment on ticket #23

Daniel Peintner — Tue, 06 Feb 2024 08:20:31 -0000

Your statements are correct. The struct is not properly initialized. Having said that, the code you are referring to is from the "test" folder which is meant to provide a simple overview and examples how to use the code... As such main_example.c illustrates both sides EV and charging side. This is NO code you should/can ever use in production! Anyhow, it should be fixed. Thanks for reporting.

Gravis created ticket #23

Gravis — Thu, 01 Feb 2024 12:34:06 -0000

Uninitialized data in main_example.c

Gravis modified a comment on ticket #22

Gravis — Mon, 08 Jan 2024 14:10:25 -0000

I hadn't even considered a fix because I wasn't 100% sure it was wrong or if I had missed something. I think a simple string like "abcdefg" would suffice. However, if what meant to ask if I was going to provide a patch for input validation, I'm not.

Gravis posted a comment on ticket #22

Gravis — Mon, 08 Jan 2024 11:24:34 -0000

I hadn't even considered a fix because I wasn't 100% sure it was wrong or if I had missed something. I think a simple string like "abcdefg" would suffice.

Daniel Peintner posted a comment on ticket #22

Daniel Peintner — Mon, 08 Jan 2024 10:34:23 -0000

You are correct, the test example is simply wrong. Note: I think this limitation evolved over time and the example did not reflect it accordingly. FYI: the EXI codec does not check for min/max character lengths. Do you plan to provide a fix (increasing size to min 3 and add proper characters)?

Gravis created ticket #22

Gravis — Thu, 04 Jan 2024 17:16:56 -0000

Invalid test data used in main_example.c?

Daniel Peintner modified ticket #21

Daniel Peintner — Wed, 03 Jan 2024 11:38:01 -0000

encode_iso1PGPDataType always fails

Daniel Peintner posted a comment on ticket #21

Daniel Peintner — Wed, 03 Jan 2024 11:37:48 -0000

I think you should be able to close it yourself but I can do it for you.

Gravis posted a comment on ticket #21

Gravis — Sat, 23 Dec 2023 15:39:21 -0000

Oops.... spoke too soon. I see it now. Just close this ticket.

Gravis created ticket #21

Gravis — Sat, 23 Dec 2023 15:35:35 -0000

encode_iso1PGPDataType always fails

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Wed, 13 Dec 2023 09:24:42 -0000

Do you miss anything? OpenV2G supports ISO IEC 15118 (Edition 1). Note: the V2G implementation for ISO 15118-20:2022 will not be available as Open Source. If you are interested in a commercial license solution, please contact us via exi.ct@siemens.com.

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Wed, 13 Dec 2023 09:21:32 -0000

XML schema attributes are optional by default.

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 06:03:09 -0000

Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ``` ``` but in the c file, openv2g define iso1CertificateChainType as below: ``` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 06:01:55 -0000

i have an question, that is openv2g is fully meet iso15118-2014 ?

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 06:01:24 -0000

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 06:00:54 -0000

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 06:00:18 -0000

Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: but in the c file, openv2g define iso1CertificateChainType as below: struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 05:59:57 -0000

Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ``` ``` but in the c file, openv2g define iso1CertificateChainType as below: ` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 05:59:36 -0000

Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ` ` but in the c file, openv2g define iso1CertificateChainType as below: ` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 05:59:15 -0000

Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ` ` but in the c file, openv2g define iso1CertificateChainType as below: ``` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 05:58:38 -0000

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 05:58:37 -0000

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 05:57:52 -0000

Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: but in the c file, openv2g define iso1CertificateChainType as below: struct iso1CertificateChainType { /* attribute: Id {http://www.w3.org/2001/XMLSchema,ID} */ struct...

BinWatson posted a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 02:41:33 -0000

i have an question, that is openv2g is fully meet iso15118-2015 ?

BinWatson posted a comment on discussion Open Discussion

BinWatson — Wed, 13 Dec 2023 02:39:23 -0000

Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: xsd but in the c file, openv2g define iso1CertificateChainType as below: c struct iso1CertificateChainType { /* attribute: Id {http://www.w3.org/2001/XMLSchema,ID}...

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Wed, 08 Nov 2023 09:30:47 -0000

Hi, Correct, I think you "found" the answer. The data exchange uses the EXI [1] format. Since we use the schema-informed EXI mode you need to understand the way EXI grammars are created and work. Anyhow, the OpenV2G project is exactly about that. Using the C structs you do not need to understand the internals. -- Daniel [1] https://www.w3.org/TR/exi/

BinWatson modified a comment on discussion Open Discussion

BinWatson — Wed, 08 Nov 2023 02:21:29 -0000

Hi, I may have fix this issue from https://www.w3.org/TR/exi-primer/#encoding: Note that AT(category) is accepted before AT(date) even though their order is reversed in the schema. This is because attributes in schema-informed grammars must be sorted lexicographically, first by local name and then by namespace URI. Attribute sorting reduces the number of options which, in turn, greatly simplifies grammar creation and improves compactness. Since this automaton does not include transitions on AT()...

BinWatson posted a comment on discussion Open Discussion

BinWatson — Wed, 08 Nov 2023 02:20:59 -0000

BinWatson posted a comment on discussion Open Discussion

BinWatson — Tue, 07 Nov 2023 10:25:05 -0000

Hi, In the function encode_iso1ExiDocument ```c int encode_iso1ExiDocument(bitstream_t stream, struct iso1EXIDocument exiDoc) { errn = writeEXIHeader(stream); if(errn == 0) { /* DocContent[START_ELEMENT({urn:iso:15118:2:2013:MsgDataTypes}AC_EVChargeParameter), START_ELEMENT({urn:iso:15118:2:2013:MsgDataTypes}AC_EVSEChargeParameter), START_ELEMENT({urn:iso:15118:2:2013:MsgDataTypes}AC_EVSEStatus), START_ELEMENT({urn:iso:15118:2:2013:MsgBody}AuthorizationReq), START_ELEMENT({urn:iso:15118:2:2013:MsgBody}AuthorizationRes),...

Gravis created ticket #20

Gravis — Sun, 30 Jul 2023 16:01:52 -0000

Resource exhaustion code paths in genated code.

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Mon, 24 Jul 2023 08:35:03 -0000

Hi, There is the possibility to encode EXI messages in byte-aligned mode (see https://sourceforge.net/p/openv2g/code/HEAD/tree/trunk/src/codec/EXIOptions.h#l57) as described by the EXI specification (see https://www.w3.org/TR/exi/#key-bytealignment) Anyhow, this is NOT following the rules for ISO 15118 which require bit-aligned encoding. Hence, this might be of interest for debugging purposes only. -- Daniel

Gravis posted a comment on discussion Open Discussion

Gravis — Fri, 21 Jul 2023 13:20:43 -0000

I'm working toward making an MCU-based solution to communicate ISO 15118-2 messages (TCP included) and one hurdle to this making compact code for EXI messages (your generated code is built for speed not reduced size). The EXI spec seems to indicate that there is the option for byte-alignment for certain parts. My question is if the generated code is utilizing this byte-alignment (I'm not an EXI expert) and if not, does the spec allow for it (I couldn't find anything definitive)?

Gravis posted a comment on discussion Open Discussion

Gravis — Wed, 19 Jul 2023 18:26:16 -0000

Thank you. This explains a lot of things.

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Wed, 19 Jul 2023 07:10:40 -0000

Hi, The iso2 was an intermediary step to iso dash 20 ( aka "-20"). Hence they have never been part of of an official specification an were completely replaced by -20. The XDS files are usually part of the ISO specification. The ones for version: 15118-20-ed-1 can be found here: https://standards.iso.org/iso/15118/-20/ed-1/en/ -- Daniel

Gravis posted a comment on discussion Open Discussion

Gravis — Wed, 19 Jul 2023 07:06:43 -0000

So I have an interest in the updated ISO 15118-2 from 2016 (aka Iso2) and have been unable to locate the xsd files. If someone could point me in the right direction, that would be great.

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Mon, 06 Mar 2023 14:58:52 -0000

Hi, I ask you to investigate a bit yourself. I assume you are writing to a byte array that is not large enough. I guess somehow here https://sourceforge.net/p/openv2g/code/HEAD/tree/trunk/src/test/main_databinder.c#l61 or similar code. This is the last time I answer questions were you just share some error codes. Please try to understand that is just guessing. -- Daniel

amy posted a comment on discussion Open Discussion

amy — Mon, 06 Mar 2023 10:42:17 -0000

error comming from writeBits() api as error code EXI_ERROR_OUTPUT_STREAM_EOF -11 file name : OpenV2G_0.9.5/src/codec/BitOutputStream.c

amy posted a comment on discussion Open Discussion

amy — Mon, 06 Mar 2023 10:42:16 -0000

error comming from writeBits() api as error code EXI_ERROR_OUTPUT_STREAM_EOF -11 file name : OpenV2G_0.9.5/src/codec/BitOutputStream.c

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Mon, 06 Mar 2023 10:29:37 -0000

This means that the encode was asked to encode something that is not valid. OpenV2G allows for encoding only valid XML portions. In most of the cases the C structs take care that the content is valid but there are still situation where this is not possible. e.g., the codec expects element a, b or c. IF none is given.. the codec will fail with -109. There are many more such cases. I suggest you to use the debugger and see what causes the issue.

amy posted a comment on discussion Open Discussion

amy — Mon, 06 Mar 2023 09:52:19 -0000

I got error code as "#define EXI_ERROR_UNKOWN_EVENT -109" from "encode_iso1ExiDocument()" api file name : OpenV2G_0.9.5/src/iso1/iso1EXIDatatypesEncoder.c

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Mon, 06 Mar 2023 09:35:53 -0000

Hi, I guess you need to share more details. * Source Code as images, grrr * What is the error code.. the number tells you the reason, see https://sourceforge.net/p/openv2g/code/HEAD/tree/trunk/src/codec/ErrorCodes.h * Which file are you using? * .... -- Daniel

amy posted a comment on discussion Open Discussion

amy — Mon, 06 Mar 2023 07:40:57 -0000

Hi , I am doing the encoding and decoding few request and response using https://sourceforge.net/projects/openv2g/files/ here I have to encode CertificateUpdateReq and I am using "serialize1EXI2Stream()" API, but I am getting error. here I have attached the method which I have doing for encode.

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Wed, 01 Mar 2023 14:14:54 -0000

Note: If you are interested in a commercial license, please contact us via exi.ct@siemens.com. To facilitate communication please use your company email address for requesting a quotation.

Godfrey posted a comment on discussion Open Discussion

Godfrey — Thu, 16 Feb 2023 01:05:07 -0000

Hello liu We are trying best to contact. But no reply and little progress got. Can you tell me which V2G project for 15118-20 you are using? Regards Godfrey

zuxiang liu posted a comment on discussion Open Discussion

zuxiang liu — Tue, 14 Feb 2023 00:35:58 -0000

Hello Godfrey, Had you got info from exi.ct@siemens.com？ I had not got any reply that i had sent 5 emails to exi.ct during the past 2 months. It is a disaster if no persons works for exi.ct@siemens.com. I still hope this opeV2G project is active even though i still switch to another V2G project for 15118-2.0.

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Wed, 18 Jan 2023 13:05:05 -0000

Hi, This aspect relates to the EXI specification. If you want to know/understand all the details I urge you to read the spec. see https://www.w3.org/TR/exi/ The openV2G library is exactly about not knowing all the details and simply using the provided interfaces. To put it simple. The document grammar is about encoding valid XML/EXI documents. Not all elements are valid root elements. SessionSetupReq is a valid element while ChargingComplete is apparently not. The fragment grammar is the entry point...

Godfrey posted a comment on discussion Open Discussion

Godfrey — Wed, 18 Jan 2023 08:07:32 -0000

Hi Daniel Thank you for your reply. I take two examples in ISO15118-2 and OpenV2G code to express my puzzlement. 1. SessionSetupReq only appear once in the xsd file, but this field exist in the document and fragment struct both. 2. ChargingComplete appeared twice in the xsd file, this field only exist in fragment struct. I can't see the difference between this field and other fields. Can you give me some more help, thank you! Regards Godfrey

Godfrey posted a comment on discussion Open Discussion

Godfrey — Wed, 18 Jan 2023 01:42:10 -0000

Hi Daniel Thank you, I've recieved your message. Can you tell me the product name of the EXI solution for ISO15118-20. Is it also called OpenV2G? I'll let the buyer of our company to contact Siemens. Regards Godfrey

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Tue, 17 Jan 2023 14:31:29 -0000

Hi, EXI differs between "documents" and "fragments". see https://www.w3.org/TR/exi/#streams [Definition:] EXI documents are EXI bodies with a single root element that conform to the Built-in Document Grammar (See 8.4.1 Built-in Document Grammar) or Schema-informed Document Grammar (See 8.5.1 Schema-informed Document Grammar). [Definition:] EXI fragments are EXI bodies with zero or more root elements that conform to the Built-in Fragment Grammar (See 8.4.2 Built-in Fragment Grammar) or Schema-informed...

Daniel Peintner posted a comment on discussion Open Discussion

Daniel Peintner — Tue, 17 Jan 2023 14:26:08 -0000

Hi Godfrey, I sent you a private message. -- Daniel