Using filtering in obd.monitor

Hi,

I am just trying the obd.monitor command (http://docs.autopi.io/commands/obd/#obd-monitor).
It seams that it works fine. I can use limit and duration. That works how I expect it.
There is a filtering attribute, how can I use this? I would like to record all messages the start with e.g. 5c5.

I used the command
obd.filter add type=pass pattern=5C5 mask=FFF

if I execute the command the system stops responding.
e.g. obd.filter list returns
reply message received within timeout of 30 secs - please try again and

before the obd.filter add function it responded. The same thing is with
obd.query DISTANCE_SINCE_DTC_CLEAR (before it works, afterwards it doesn’t)

After reboot the AutoPi everything works fine and the obd.filter list command returns

_stamp: ‘2019-04-06T18:18:47.330709’
values: []

What’s my mistake?

Kind regards
Ludi

Hi @Ludi,

Are you running the latest release of the AutoPi Core?

best
Peter

Hi Peter,

I updated the system on 2019-04-05. 2019-04-09_10-17-20

It should be the latest version.
Kind regards
Ludi

Hi @Ludi,

We’ve tried to reproduce this. This are the results:

peter@xxx RPi 3 $ obd.filter list
_stamp: '2019-04-09T09:18:55.745742'
values: []

peter@xxx RPi 3 $ obd.filter add type=pass pattern=5C5 mask=FFF
_stamp: '2019-04-09T09:19:49.302295'
values:
    - pattern: 5C5
    type: PASS
    mask: FFF

peter@xxx RPi 3 $ obd.filter list
_stamp: '2019-04-09T09:19:56.017772'
values:
  - pattern: 5C5
    type: PASS
    mask: FFF

We also just released a hot fix (where this was tested on).

Can you see if that also fixes your issues.

best
Peter

I just tried it with the new version, it does not work.

here is my output

local user@Local device $ obd.monitor auto_format=false limit=10 wait=true duration=10
_stamp: '2019-04-09T11:52:38.055918'
_type: raw
values:
  - _stamp: '2019-04-09T11:52:37.095876'
    value: 2D3 00 00 08 BB F1 7D C1 74
  - _stamp: '2019-04-09T11:52:37.198566'
    value: 4F9 44 D4 00 02 00 00 00
  - _stamp: '2019-04-09T11:52:37.290387'
    value: 357 4D 48 08 09 05
  - _stamp: '2019-04-09T11:52:37.388867'
    value: 285 00 00 00 00 00 00 75 FC
  - _stamp: '2019-04-09T11:52:37.493094'
    value: 29A 00 00 00 00 00 00 05 A1
  - _stamp: '2019-04-09T11:52:37.594907'
    value: 1B6 00 01 FF F0 03 FE 00 00
  - _stamp: '2019-04-09T11:52:37.697412'
    value: 1C3 00 00 00 00 00 00 FF C3
  - _stamp: '2019-04-09T11:52:37.802766'
    value: 15A 3E A0 00 1B FF 00
  - _stamp: '2019-04-09T11:52:37.899518'
    value: 15B 32 03 20 C0 00
  - _stamp: '2019-04-09T11:52:37.999991'
    value: 15C 1A 3E 33 93 20 00 20 00
    
    
    
    
local user@Local device $ obd.filter list
_stamp: '2019-04-09T11:53:58.070428'
values: []


local user@Local device $ obd.filter add type=pass pattern=15C mask=FFF
_stamp: '2019-04-09T11:56:25.231399'
values:
  - mask: FFF
    pattern: 15C
    type: PASS


local user@Local device $ obd.filter list
error: >-
  No reply message received within timeout of 30 secs - please try again and
  maybe increase timeout value

first I used the obd.monitor to detect a message, afterwards I used obd.filter list, than obt.filter add (15C), and than again obd.filter list.

obd.monitor auto_format=false limit=10 wait=true duration=10 returns
No reply message received within timeout of 30 secs - please try again and maybe increase timeout value

what happens if you add the $timeout=60 parameter to the obd.filter list?

Hi,

I just executed obd.filter list timeout=60
And the same error message will be shown after 30 seconds. It seams that the timeout does not work.

Before executing the command obd.filter add … the list command returns the result within 2 seconds.

Hi @Ludi,

Do you have a chance to get the logs from the device?

Just send the directly to me, then we’ll have a look at it.

best
Peter