Wed Mar 15, 2017 1:17 pm
Is the chademo protocol documentation specific enough like the following? I do all the code myself, so I would have to know the communications required in detail for it to work.
The CAN packets can be between 1 and 8 bytes. Could I expect to see something as specific as the following in that $150 documentation?:
car sends (let's pretend hex):
10 03 4f 3f
Oh, the documentation says 10 03 means "message x", and 4f 3f means "data".
I must wait "x" units of time before answering with my own data packet....
I send:
45 5d 34 4a 5f a2
Car sends:
5e
I must wait "y" units of time
I send:
89 75 43
...
etc..
And, does the documentation tell me how the encoding is done for things like "what is your max voltage", "what is your charge rate", etc? If the chademo protocol isn't very specific so that I can't translate what they are saying into C, it would be a waste of $150 for me to get it.
.