Dev corner

Calling all engineers, tinkerers, hackers and geeks.

Multiple FLM discovery

In the discussion on nicely designed gauges the request was raised to go beyond single-FLM installations.
If you have more than one FLM installed, you instantly get yourself the question on how to control them together.
Current scripts deal with a single instance only; but as we know Bart, there is already a solution: each FLM advertises its service(s) via Bonjour.
Thus the idea to enhance the single-instance persistence and visualization services with an appropriate FLM discovery; that is: integrate Bonjour into the persistence and visualization services to deal with "any number" of publishing sensor nodes...

This will be the story of this thread, so stay tuned for experiences gained and implementations provided...

A Time series file format for the Fluksometer [solved]

By https://www.flukso.net/files/presentations/flukso.20140425.pdf the FLM grand master introduces and discusses a time series storing concept that shall efficiently be implemented into the FLM world. "Efficiently" here denotes especially the capability to be compressed and easily accessed later on.
I'd like to jump on this train and instantly provide some further requirements that specifically deal with the MQTT capabilities of the FLM, allowing to mesh-up sensor data from different sources.
For "my" persistence in a database I use following table layout:

  1. sensor CHAR(32),
  2. timestamp CHAR(10) // timestamp TIMESTAMP
  3. value CHAR(5)
  4. unit CHAR(5)
  5. UNIQUE KEY (sensor, timestamp)

This layout allows to store the sensor data (value AND unit) together with the sensor's ID and timestamp of event occurrence. There shall be a unit as already with water and gas there are different units to consider beside Watts alone; Temperature (°C, °F) are further candidates.
Alternatively sensor meta data could be stored aside (sensor ID with description, unit, ...), yet a "foreign key" relation shall be introduced based in the sensor ID.
What else can you imagine? Or may an existing format be used, like for example expressed by the SML, the Smart Message Language?

Note: The solution to this thread is TMPO.

Current clamps for fuses or appliances

Just wanted to share...I found a good current clamp that seems to be a good fit for measuring current at individual fuses or appliances:

SCTD010T-5A, 10A or 25A

Energy meter solar panels

Dear all,
I'm trying to read in data from my heat meter (Diehl Sharky 775 ultrasonic compact meter - http://www.diehl.com/de/diehl-metering/produkte-loesungen/pdb-details.ht...), currently installed on my solar panel system tubing.

In their specs, they indicate that radio communication is integrated:
SHARKY
Frequency band 868 or 434 MHz
Type of radio telegram Real Data or Open Metering Standard (OMS)
Transmission data updating Online - no time delay between value measurement and data transmission
Data transmission Unidirectional
Sending interval D-cell: 12 s ( max. 16 years lifetime); with mains unit: 12 s; depending on length of telegram (duty cycle)

I was wondering whether anyone on this forum could give me some leads on where to start my effort to connect this energy meter to my flukso (FLM02B) device, using radio communication. Radio communication, as this would prevent having to open up the energy meter and install a specific pulse output module (which they offer).

Thank you very much in advance for any leads on this matter!
Kind regards,
Geert

Sensor specifications

Hi,

Does anyone known the specifications of the flukso sensors, or where I could find them?

Kind regards;

Michel