{"id":1995,"date":"2020-12-24T17:57:26","date_gmt":"2020-12-24T23:57:26","guid":{"rendered":"https:\/\/scadametrics.com\/blog\/?p=1995"},"modified":"2022-10-15T15:37:20","modified_gmt":"2022-10-15T21:37:20","slug":"ethermeter-auto-detection-of-meter-types","status":"publish","type":"post","link":"https:\/\/scadametrics.com\/blog\/?p=1995","title":{"rendered":"Water Meter Auto-Detection Simplifies EtherMeter\u00ae Commissioning!"},"content":{"rendered":"
\"James

Jim ‘Slim’ Mimlitz, SCADAmetrics<\/p><\/div>\n\n\n\n

METER AUTO-DETECTION INTRODUCED…<\/strong><\/p>\n\n\n\n

North-American encoder-type water meters communicate using one of three protocol families: Neptune<\/strong>, Elster<\/strong>, and Sensus<\/strong> (..which is generally comprised of all makes, except Neptune and Elster). Furthermore, various meter makes\/models have their own additional idiosyncrasies.<\/p>\n\n\n\n

In the past, there were two EtherMeter tuning parameters which often required adjustment to help the EtherMeter communicate optimally with each make\/model of water meter: PWRn<\/strong> and CLKLOWn<\/strong>. Within the EtherMeter Compatibility Matrix<\/strong> document, we enumerated the recommended values of PWRn and CLKLOWn for each make\/model water meter.<\/p>\n\n\n\n

Today, I am pleased to announce that all EtherMeters shipped on or after 08 Nov 2020<\/strong> will contain a sophisticated meter auto-sensing routine<\/em><\/strong>, which simplifies EtherMeter commissioning!<\/p>\n\n\n\n

\n\n\n\n
\"\"
SCADAmetrics EtherMeter<\/figcaption><\/figure>\n\n\n\n
\n\n\n\n

As a consequence, the PWRn<\/strong> and CLKLOWn<\/strong> settings are now retired, and replaced with a single setting:<\/p>\n\n\n\n

TYPEn<\/strong><\/p>\n\n\n\n

TYPEn<\/strong> can be set to either AUTO<\/strong> (default) or PULSE<\/strong>; which means that if the EtherMeter is connected to an encoder-type water meter, then you won’t have to change this setting! The EtherMeter will determine the required encoder protocol \u2014 quickly and automatically! However, if the user prefers to disable the auto-detection logic (not recommended), he may still do so and explicitly set TYPEn<\/strong> to NEPTUNE<\/strong>, SENSUS<\/strong>, or ELSTER<\/strong>.<\/p>\n\n\n\n

ENHANCED ELSTER\/HONEYWELL AUTO-DETECTION…<\/strong><\/p>\n\n\n\n

Another new user-friendly feature was introduced in this firmware release, which pertains to Elster (Honeywell) water meters. When an Elster meter is detected, the EtherMeter now automatically extracts the Units (UNITn) and Multiplier (EXPn) settings from the meter, as this information is conveyed via the Elster protocol.<\/p>\n\n\n\n

PULSE METERS STILL REQUIRE SETUP…<\/strong><\/p>\n\n\n\n

When connecting to pulse-type meters<\/strong>, EtherMeter setup is now more intuitive, where the user sets the EtherMeter for pulse as follows:<\/p>\n\n\n\n

SET TYPEn PULSE<\/strong><\/p>\n\n\n\n

UPDATED DOCUMENTATION…<\/strong><\/p>\n\n\n\n

The User Manual<\/a><\/strong> and Compatibility Matrix<\/a><\/strong> have been updated to reflect and document these improvements.<\/p>\n\n\n\n

\n\n\n\n

Are you interested in how SCADAmetrics’ EtherMeter technology can lend a competitive advantage to your automation system’s metering operations? It just got a little easier! Give us a call! We\u2019ll be glad to discuss the details!<\/p>\n","protected":false},"excerpt":{"rendered":"

METER AUTO-DETECTION INTRODUCED… North-American encoder-type water meters communicate using one of three protocol families: Neptune, Elster, and Sensus (..which is generally comprised of all makes, except Neptune and Elster). Furthermore, various meter makes\/models have their own additional idiosyncrasies. In the past, there were two EtherMeter tuning parameters which often required adjustment to help the EtherMeter …<\/span> Read More →<\/span><\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":1746,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,8,4,7],"tags":[269,268,267],"class_list":["post-1995","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-applications","category-general","category-meteringtechnology","category-troubleshooting","tag-encoder-auto-detection","tag-encoder-type-water-meters","tag-meter-auto-detection"],"_links":{"self":[{"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1995","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1995"}],"version-history":[{"count":24,"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1995\/revisions"}],"predecessor-version":[{"id":2381,"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1995\/revisions\/2381"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/1746"}],"wp:attachment":[{"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1995"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1995"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scadametrics.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}