get limit pulse counter value | Telit Cinterion IoT Developer Community
November 29, 2017 - 10:44am, 2158 views
Dear,
I want to use the limit pulse counter to send an sms when an amount of pulses is reached. Is there a way to request the counter value while waiting for the limit to be reached like the getValue() form the startStopPulseCounter?
Or is it in any way possible to use both the startStopPulseCounter and the limitPulseCounter?
regards,
Kai Barkmann
Hello,
These two counters are based on the functionality available with AT commands where it is not possible to check the current value of limit pulse counter. In each case the same GPIO pin is used. So these two are mutually exclusive. Can you write more about your solution and why you need to read the value while waiting for the limit to be reached?
Regards,
Bartłomiej
Bartłomiej,
We're adding a puls *****er function to our product which customers want to use from e.g. service (power kWh) meters up to bottle *****ers in a factory:
http://conta-clip.com/news/detail/artikel/71/gsm-pro2-der-perfekte-kommunikator.html
This functionality must be fully customizable and ***** functionality as: daily log's, requestable *****, periodical message and send on threshold (limit).
All has to be devidable f.i. kWh meters give a pulse on each Watt-hour. Customers want messages with kWh.
This makes the limit pulse useless for our purposes. I'll have to stick with the *****er function and check if thresholds are reached. This comes at cost of accuracy though when *****ing at a high rate.
Thanks anyway.
regards,
Kai
Thank you for the explanation.
Indeed limit pulse counter is not the best choice for this purpose as it only ****** to a limit, then sends notification and stops. so you may loose some pulses generated after it stops. The start stop pulse counter might be better as you can read the value without stopping it but you loose accuracy in that way and additionally too frequent reading might not be good for performance.
Generally pulse ******** alone does not seem as attractive solution here.
Each of the meters probably provides some communication port and protocol which could be used for configuration, reading of current values and additionaly some historical data etc. Maybe also some triggers can be configured there or in the application based on the constant reading for example. Then limit pulse ******** could only be used as support for generating triggers.
Best regards,
Bartłomiej