www.brultech.com

Things are working for me. But, I am still working out the kinks.

I had to comment out some of the ecmreadext fields (ch1whd and back).

I am not sure why these fields were not found. Are these GEM fields that the ECMs do not record?

Bob

BobinTN wrote:Things are working for me. But, I am still working out the kinks.

I had to comment out some of the ecmreadext fields (ch1whd and back).

I am not sure why these fields were not found. Are these GEM fields that the ECMs do not record?

Bob

I had an issue with that also when adding it to the GEM. I had to switch it to "_dwh" instead of "_whd".

Thanks for the fix. I added those attributes back in to btmon.

Is their a document that explains what those values mean and how to use them?

I am trying to record kwh usage over a 24 hour period, week period, month period for each of my circuits. I am struggling with the syntax of SQL and/or influxDB queries.

The _dwh. Is that daily watt hour useage?
Bob

BobinTN wrote:Thanks for the fix. I added those attributes back in to btmon.

Is their a document that explains what those values mean and how to use them?

I am trying to record kwh usage over a 24 hour period, week period, month period for each of my circuits. I am struggling with the syntax of SQL and/or influxDB queries.

The _dwh. Is that daily watt hour useage?
Bob

_dwh is delta watt hours, it's the difference in watt hours between posts.

You can get that value in 2 different ways.

1. Sum the dwh for the 24 hour period, divide that by 1000.
2. Take the wh at the start of the day, subtract it at the end of the day.

_w = Watts
_a = Amps
_wh = Watt Hours
_dwh = Delta Watt-Hours (_wh - last _wh)

Not sure what these two do, I think they're in case of polarity issues:
_nXX = Negative
_pXX = Positive

Everything is running pretty well. ECM1240(device) to wifi(newtork) to desktop(server) to btmon(as service recieving data) to influxdb(database storage) to Grafana (Data Analysis Graphics).

I am having a problem with the btmon.py service (using NSSM). Though the btmon service keeps running, data stops being collected. I think the issue is with btmon because when I restart the service, the data starts getting passed into the InfluxDB database.

Is anybody else having a problem where btmon stops passing data but continues running?

I can write a python script that monitors the last time data was written to influxdb database, if time since last write it too great, then re-start btmon service.

But I do not want to re-create the wheel or go off in the wrong direction to fix.

Any ideas?

making things work and making things bombproof that work non-stop for years are different beasts...

with btmon/influxdb/grafana, sure like you say the btmon crashes every so often and the service can be restarted using various stuff

I seem to like your self lose data, ? once/twice a year, your idea to independantly test influxdb and give btmon a kick up the er, okay restart sounds like a fair idea. even having an option to restart btmon say once a month wouldnt be a bad idea either

As for why it stops logging I have no idea, prob happy enough with level of robustness so it dont warrant no 'stewards inquiry'

Does BTMon.py show packets coming in and being processed still?

Try btmon in verbose mode and log the output so you can see what happens when it goes down.

EDIT: Also, copy/paste your btmon config file

Hello.
I would suggest to take a look at Ignition Maker from Inductive automation.
it is a free version of very powerful SCADA .
Regards