OCPP1.6: size of integer for transaction_id

[laurst]

OCPP1.6: size of integer for transaction_id

[tommymalmqvist]

Hi @laurst this is nagging me so I'll fix it :) Thanks tho, totally missed this.

[SirVer]

I do not need it. I agree 32bit is the right choice here Am 24.10.2023 um 09:39 schrieb Tommy Malmqvist ***@***.***>: @SirVer No, 1.6 has not defined it. Do you need 64-bit for 1.6? Else I think it'll be more safe to use 32-bit if there are many Pole's running on 32-bit. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[tommymalmqvist]

Hi @laurst, thank you for your input. You are actually correct, the specification states 32-bit so I'd happily take a PR :)

From the specification:

Integer
32 bit (31 bit resolution, 1 sign bit)
No leading 0’s No plus sign
Allowed value examples: 1234, -1234
Not Allowed: 01234, +1234

[laurst]

That was quick, thanks! I have to ask though, in which document do you see this specified? I've searched in both the 1.6 edition 2 spec, the erratas, the json spec, and I might be dense but I didn't see it.

[tommymalmqvist]

file: OCPP-2.0.1_part2_specification.pdf

2.1.3. Primitive Datatypes

[SirVer]

@tommymalmqvist This seems to be only for 2.0.1, is this also specified for 1.6?

[tommymalmqvist]

@SirVer No, 1.6 has not defined it. Do you need 64-bit for 1.6? Else I think it'll be more safe to use 32-bit if there are many Pole's running on 32-bit.