[Ovmsdev] New can logging

[Michael Balzer]

Mark,

is there a bug in the new can monitoring or am I doing something wrong?

monitor mode:

    OVMS# can log start monitor crtd
    CAN logging to MONITOR active: Type:monitor Format:crtd Filter:off Vehicle:RT
    Note: info logging is at debug log level, frame logging is at verbose, and errors as usual
    I (83919) canlog-monitor: Now logging CAN messages to monitor
    D (83919) canlog-monitor: 1564312407.926444 CXX OVMS CRTD
    OVMS# can can1 tx standard 080 010203
    ets Jun  8 2016 00:22:57

    rst:0x8 (TG1WDT_SYS_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT)
    configsip: 0, SPIWP:0xee
    clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
    mode:DIO, clock div:2
    load:0x3fff0018,len:4
    load:0x3fff001c,len:4952
    load:0x40078000,len:7416
    load:0x40080000,len:8344
    entry 0x4008037c
    W (86) boot: PRO CPU has been reset by WDT.
    W (86) boot: WDT reset info: PRO CPU PC=0x4008aab8
    W (86) boot: WDT reset info: APP CPU PC=0x4009621a


vfs mode:

    OVMS# can log start vfs crtd /sd/logs/can.crtd
    ets Jun  8 2016 00:22:57

    rst:0x8 (TG1WDT_SYS_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT)
    configsip: 0, SPIWP:0xee
    clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
    mode:DIO, clock div:2
    load:0x3fff0018,len:4
    load:0x3fff001c,len:4952
    load:0x40078000,len:7416
    load:0x40080000,len:8344
    entry 0x4008037c
    W (86) boot: PRO CPU has been reset by WDT.
    W (86) boot: WDT reset info: PRO CPU PC=0x4008aab8
    W (86) boot: WDT reset info: APP CPU PC=0x400838cc


Regards,
Michael

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20190728/ea935f06/attachment.html>