[Ovmsdev] New can logging

[Michael Balzer]

Yes, that solved it, thanks!

Regards,
Michael


Am 28.07.19 um 15:10 schrieb Mark Webb-Johnson:
> 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.
>
> Seems to be just a simple buffer overflow. I’ve committed a fix.
>
> Regards, Mark.
>
> 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.
>
>> On 28 Jul 2019, at 8:52 PM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>>
>> Michael,
>>
>> Not sure what is going on. Here is what I get:
>>
>>     OVMS# log level verbose
>>     Logging level for * set to verbose
>>     OVMS# can log start monitor crtd
>>     CAN logging to MONITOR active: Type:monitor Format:crtd Filter:off Vehicle:
>>     Note: info logging is at debug log level, frame logging is at verbose, and errors as usual
>>     I (58794) canlog-monitor: Now logging CAN messages to monitor
>>     D (58794) canlog-monitor: 1564318162.354891 CXX OVMS CRTD
>>     OVMS# can can1 start active 1000000
>>     Can bus can1 started in mode active at speed 1000000bps
>>     D (68894) events: Signal(power.can1.on)
>>     OVMS# can can2 start active 1000000
>>     Can bus can2 started in mode active at speed 1000000bps
>>     D (73774) events: Signal(power.can2.on)
>>     OVMS# can can1 tx standard 080 01 02 03 04
>>     V (96934) canlog-monitor: 1564318200.493753 1T11 080 01 02 03 04
>>     V (96934) canlog-monitor: 1564318200.494240 2R11 080 01 02 03 04
>>     OVMS# can can1 tx standard 080 010203
>>     V (108364) canlog-monitor: 1564318211.923843 1T11 080 03
>>     V (108364) canlog-monitor: 1564318211.924243 2R11 080 03
>>
>>
>> Did you get a backtrace?
>>
>> Regards,  Mark
>>
>> 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.
>>
>>> On 28 Jul 2019, at 7:27 PM, Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> wrote:
>>>
>>> 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
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-- 
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/a301f4e6/attachment.htm>