Replies: 1 comment
-
|
urn:din:70121:2012:MsgDef： urn:tesla:din:2018:MsgDef： |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are currently working on a charging station project, and the test subject is a Tesla Model Y from the United States.
The V2G communication data is as follows.
Based on the data, this car supports both the 'urn:din:70121:2012:MsgDef' and 'urn:tesla:din:2018:MsgDef' protocols.We have tested both protocols.
When the 'urn:tesla:din:2018:MsgDef' protocol is selected, after we send the supportedAppProtocolRes, the car also sends an ACK indicating that the data has been successfully received. However, there are no subsequent V2G requests."
When the 'urn:din:70121:2012:MsgDef' protocol is selected, the V2G communication progresses to 'ServiceDiscoveryRes'. After we send the ServiceDiscoveryRes, there are no subsequent V2G requests."
The data can be opened with Wireshark. If the V2G messages cannot be decoded, you can use the plugin included in the attachment
We have been stalled at this point for a long time and hope to get some help，Thank you very much！
logs.zip
Beta Was this translation helpful? Give feedback.
All reactions