Timedata InfluxDB Question

stefan.feilmeier · November 1, 2020, 11:05am

Hi Vincenzo,

welcome to the Community.

By default the writes to InfluxDB are truncated to one value per second. You should be able to adjust implementation for your use-case here:

github.com

OpenEMS/openems/blob/develop/io.openems.edge.timedata.influxdb/src/io/openems/edge/timedata/influxdb/InfluxTimedataImpl.java#L111


			this.collectAndWriteChannelValues();
			break;
		}
	}

	protected synchronized void collectAndWriteChannelValues() {
		long timestamp = System.currentTimeMillis() / 1000;

		if (++this.cycleCount >= this.config.noOfCycles()) {
			this.cycleCount = 0;
			final Builder point = Point.measurement(InfluxConnector.MEASUREMENT).time(timestamp, TimeUnit.SECONDS);
			final AtomicBoolean addedAtLeastOneChannelValue = new AtomicBoolean(false);

			this.componentManager.getEnabledComponents().stream().filter(c -> c.isEnabled()).forEach(component -> {
				component.channels().forEach(channel -> {
					switch (channel.channelDoc().getAccessMode()) {
					case WRITE_ONLY:
						// ignore Write-Only-Channels
						return;
					case READ_ONLY:
					case READ_WRITE:

Apart from that: I am working on a “Simulator” which might be exactly what you need. It is already functional, but unfortunately still lacks proper documentation and a nice UI.

To try if it suits you, you would have to

Activate the “Controller Api REST/JSON Read-Write” in OpenEMS. (I usually use the Talend API Tester chrome extension)
Then send a executeSimulation JSONRPC-Request (see the example here), that defines the simulated Components, simulated data and simulation parameters.
- components keeps the configuration for each Component, just like Apache Felix Configuration Admin would do
- clock defines the duration of the simulation.
  - To simulate a real-time execution set the timeleapPerCycle to 1000 (i.e. 1 second) and executeCycleTwice to false.
  - (The settings in the example (timeleapPerCycle:900000, executeCycleTwice:true) are for a simulation of 15 minutes values, e.g. for industrial peak-shaving applications)
- profiles: define the input data. This is the data you currently provide via a datasource.
- collect: defines the channels that you would want to record.
The simulation will then run for a while… watch the logs to see the progress
Once it’s finished it returns a JSONRPC-Response, that holds the collected channel data as a JSON
The Simulator-App also behaves like a Timedata service in OpenEMS, so you can also see the simulated results in OpenEMS UI.

Looking forward to hearing from you about this. I am curious to know if it works for you.

Regards,
Stefan