npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

node-red-contrib-cumbre-pulsos-flow

v1.0.23

Published

Control de flujo basado en pulsos

Readme

Pulsos a flujo

Llega reporte TCP type CT32.

Esto ocurre cada cierto lapso de duracion indeterminada. Cada pulso corresponde a 100 litros. Por cada reporte se debe informar de la cantidad de litros por segundo. En cada reporte llega un numero mayor al anterior, por lo que hay que tomar la diferencia con el anterior

ENTRADA: nowPulsos

SALIDA lt/s (litros por segundo)

lastReporte = null (type timestamp) lastPulsos = null (type int)

Es primer reporte? no: delta = (timestamp - lastReporte) * 1000 // tenemos segundos pulsos = nowPulsos - lastPulsos r = pulsos / delta // tenemos pulsos por segundo salida = r * 100 // tenemos litros por segundo lastReporte = ts lastPulsos = nowPulsos

Modificar NR-pulsos para mejorar el muestreo de datos

Cada vez que llega un reporte conteniendo pulsos, informar (en el output del nodo) los l/s acumulados desde un instante en el tiempo immediatamente superior o igual a un intervalo T (unidad en segundos a configurar por formulario del nodo). Este intervalo T es relativo al instante del reporte arrivado, por ejemplo:

Dado T=60secs

  • reporte a las 13:00:00 => encontrar l/s desde 12:58:50 a 13:00:00, si el reporte mas cercano y superior a T fue a las 12:58:50. Seria los l/s en 1min con 10 secs.

Restricción no usar DB.

https://www.pivotaltracker.com/story/show/169339742/comments/208063232