On Sat, 12 Dec 2020 at 17:28, Michael Balzer <dexter@expeedo.de> wrote:
with log level verbose for canlog, you can simply activate CAN logging via:
can log start monitor crtd
…that will log all frames, if that's too much, add a filter like this:
can log start monitor crtd 600-7ff
To see what was happening I had to "log level verbose canlog-monitor"
I see this being transmitted:
V (62436161) canlog-monitor: 1607847148.142477 1T11 6F1 03 22 dd bc 00 00 00 00
There is no reply.
The other app I looked at does this on the LM327 as setup before sending the request:
2020-11-15 10:34:35.115 --> ATCEA07⏎ "extended address" 0x07
2020-11-15 10:34:35.127 <-- OK⏎⏎>
2020-11-15 10:34:35.127 <-- OK⏎⏎>
Looking at the LM327 data sheet this configures an "extended address" which is sent after the 0x6F1
I'm not sure if that 0x03 in what OVMS is sending is that byte, and I need to somehow replace it wih 07, or if I have to get another inserted?
Perhaps this is old hat to those more experienced than me.
From the data sheet and the trace it seems I'm also responsible to customise the flow control messages :-
2020-11-15 10:34:35.129 --> ATFCSH6F1⏎ Flow control header
2020-11-15 10:34:35.141 <-- OK⏎⏎>
2020-11-15 10:34:35.143 --> ATFCSD07300800⏎ Flow control data
2020-11-15 10:34:35.156 <-- OK⏎⏎>
2020-11-15 10:34:35.157 --> ATFCSM1⏎ Flow control mode
2020-11-15 10:34:35.170 <-- OK⏎⏎>
2020-11-15 10:34:35.141 <-- OK⏎⏎>
2020-11-15 10:34:35.143 --> ATFCSD07300800⏎ Flow control data
2020-11-15 10:34:35.156 <-- OK⏎⏎>
2020-11-15 10:34:35.157 --> ATFCSM1⏎ Flow control mode
2020-11-15 10:34:35.170 <-- OK⏎⏎>
I think that comes down to a flow control being "06 F1 07 30 08 00"
Here's the page in the LM327 to help understand what it does: