From 416f25eca884ac8750e60d9d937c07698f0a36c8 Mon Sep 17 00:00:00 2001 From: Michael Ingraham <34340210+meingraham@users.noreply.github.com> Date: Sun, 8 Sep 2019 15:38:02 -0400 Subject: [PATCH] Updated Smart Meter Interface (markdown) --- Smart-Meter-Interface.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/Smart-Meter-Interface.md b/Smart-Meter-Interface.md index abbad4f5..1aaf1fc6 100644 --- a/Smart-Meter-Interface.md +++ b/Smart-Meter-Interface.md @@ -12,7 +12,6 @@ The Smart Meter Interface provides a means to connect many kinds of meters to Ta - Binary MODBUS telegram used by many power meters - Binary RAW telegram decodes all kinds of binary data eg EMS heater bus - Counter interface (uses Tasmota counter storage) for e.g., reed contacts either in polling or IRQ mode -- PZEM-004T (v1) ASCII There are many different meters that use the same protocol. There are multitudes of variants and use cases. A meter can be defined by using compilation time `#define` pragmas. This requires recompiling the firmware to make modifications. @@ -39,13 +38,12 @@ Declare a script `>M` section with the number of connected meters (n = `1..5`) - `c` = Counter type - `e` = EBus binary coding - `m` = MODBus binary coding - - `p` = PZEM - `r` = Raw binary coding (any binary telegram) - `` - counter flag - 0=without pullup - 1=with pullup - `` - parameters according to meter type - - for `o,s,e,m,p,r`: serial baud rate + - for `o,s,e,m,r`: serial baud rate - for `c`: - positive value = counter poll interval - negative value = debounce time (milliseconds) for irq driven counters