<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I tried some more. It seems that the problem is with logging errors in crtd format. I didn’t see it because my bus had no errors.<div class=""><br class=""></div><div class="">Seems to be just a simple buffer overflow. I’ve committed a fix.</div><div class=""><br class=""></div><div class="">Regards, Mark.</div><div class=""><br class=""></div><div class="">P.S. I have a relatively big update to can logging going through testing. Some standardisation of functionality for incoming data (such as whether to transmit or simulate it), and a can log playback system.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 28 Jul 2019, at 8:52 PM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net" class="">mark@webb-johnson.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Michael,<div class=""><br class=""></div><div class="">Not sure what is going on. Here is what I get:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">OVMS# log level verbose</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">Logging level for * set to verbose</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">OVMS# can log start monitor crtd</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">CAN logging to MONITOR active: Type:monitor Format:crtd Filter:off Vehicle:</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">Note: info logging is at debug log level, frame logging is at verbose, and errors as usual</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">I (58794) canlog-monitor: Now logging CAN messages to monitor</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">D (58794) canlog-monitor: 1564318162.354891 CXX OVMS CRTD</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">OVMS# can can1 start active 1000000</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">Can bus can1 started in mode active at speed 1000000bps</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">D (68894) events: Signal(power.can1.on)</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">OVMS# can can2 start active 1000000</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">Can bus can2 started in mode active at speed 1000000bps</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">D (73774) events: Signal(power.can2.on)</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">OVMS# can can1 tx standard 080 01 02 03 04</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">V (96934) canlog-monitor: 1564318200.493753 1T11 080 01 02 03 04</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">V (96934) canlog-monitor: 1564318200.494240 2R11 080 01 02 03 04</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">OVMS# can can1 tx standard 080 010203</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">V (108364) canlog-monitor: 1564318211.923843 1T11 080 03</span></font></div><div class=""><font face="Andale Mono" size="1" class=""><span style="font-style: normal;" class="">V (108364) canlog-monitor: 1564318211.924243 2R11 080 03</span></font></div></div></blockquote><div class=""><div class=""><br class=""></div><div class="">Did you get a backtrace?</div><div class=""><br class=""></div><div class="">Regards, Mark</div><div class=""><br class=""></div><div class="">P.S. The data bytes in ‘can tx’ need to be space separated. Without that, it messed up the data, but still works for me.</div><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 28 Jul 2019, at 7:27 PM, Michael Balzer <<a href="mailto:dexter@expeedo.de" class="">dexter@expeedo.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Mark,<br class="">
<br class="">
is there a bug in the new can monitoring or am I doing something
wrong?<br class="">
<br class="">
monitor mode:<br class="">
<blockquote class=""><tt class="">OVMS# can log start monitor crtd </tt><br class="">
<tt class="">CAN logging to MONITOR active: Type:monitor Format:crtd
Filter:off Vehicle:RT</tt><br class="">
<tt class="">Note: info logging is at debug log level, frame logging is at
verbose, and errors as usual</tt><br class="">
<tt class="">I (83919) canlog-monitor: Now logging CAN messages to monitor</tt><br class="">
<tt class="">D (83919) canlog-monitor: 1564312407.926444 CXX OVMS CRTD</tt><br class="">
<tt class="">OVMS# can can1 tx standard 080 010203</tt><br class="">
<tt class="">ets Jun 8 2016 00:22:57</tt><br class="">
<br class="">
<tt class="">rst:0x8 (TG1WDT_SYS_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT)</tt><br class="">
<tt class="">configsip: 0, SPIWP:0xee</tt><br class="">
<tt class="">clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00</tt><br class="">
<tt class="">mode:DIO, clock div:2</tt><br class="">
<tt class="">load:0x3fff0018,len:4</tt><br class="">
<tt class="">load:0x3fff001c,len:4952</tt><br class="">
<tt class="">load:0x40078000,len:7416</tt><br class="">
<tt class="">load:0x40080000,len:8344</tt><br class="">
<tt class="">entry 0x4008037c</tt><br class="">
<tt class="">W (86) boot: PRO CPU has been reset by WDT.</tt><br class="">
<tt class="">W (86) boot: WDT reset info: PRO CPU PC=0x4008aab8</tt><br class="">
<tt class="">W (86) boot: WDT reset info: APP CPU PC=0x4009621a</tt><br class="">
</blockquote>
<br class="">
vfs mode:<br class="">
<blockquote class=""><tt class="">OVMS# can log start vfs crtd /sd/logs/can.crtd</tt><br class="">
<tt class="">ets Jun 8 2016 00:22:57</tt><br class="">
<br class="">
<tt class="">rst:0x8 (TG1WDT_SYS_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT)</tt><br class="">
<tt class="">configsip: 0, SPIWP:0xee</tt><br class="">
<tt class="">clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00</tt><br class="">
<tt class="">mode:DIO, clock div:2</tt><br class="">
<tt class="">load:0x3fff0018,len:4</tt><br class="">
<tt class="">load:0x3fff001c,len:4952</tt><br class="">
<tt class="">load:0x40078000,len:7416</tt><br class="">
<tt class="">load:0x40080000,len:8344</tt><br class="">
<tt class="">entry 0x4008037c</tt><br class="">
<tt class="">W (86) boot: PRO CPU has been reset by WDT.</tt><br class="">
<tt class="">W (86) boot: WDT reset info: PRO CPU PC=0x4008aab8</tt><br class="">
<tt class="">W (86) boot: WDT reset info: APP CPU PC=0x400838cc</tt><br class="">
</blockquote>
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</div>
_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class=""><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>