Skip to main content

2 posts tagged with "Integrations"

Updates about drivers, connections and data exchange.

View all tags

More freedom in your choice of equipment with the Driver Factory

From weeks to minutes

Before
Developing a driver: weeks
Now
MinutesThe software prepares the driver, then we test it remotely on your installation together. Goal: testing within about 1 working day.

In short

For you
Choose the equipment that suits your project, even if there is no driver yet.
What you do
Request the driver under Driver requests in Watt and attach the device's register map.
Note
Early access, and aimed at devices with a Modbus interface.
01Why

No more delays because of a missing driver

As an installer you want to choose the equipment that best suits your project. If a device isn't supported by the EMSemsEnergymanagementsysteem dat energieverbruik en opwek bewaakt en optimaliseert binnen een installatie. yet, that can delay your project.

That's why we built the DriverdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s. Factory. A large part of developing new driversdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s. is now automated. Where this used to take weeks, the software now prepares a driverdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s. within minutes.

02What does this mean for you?

Three benefits in your daily work

More freedom in equipment

You depend less on existing driversdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s. and can more often use devices from different manufacturers: batteries, inverters, energy meters and chargers.

Shorter wait for connections

New driversdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s. are ready for a field test much sooner.

Insight into progress

Under DriverdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s. requests in Watt you request a driverdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s., add documentation and follow its development.

Follow driver requests
03How does it work?

From request to working connection

  1. 01

    Request the driver

    Enter the exact model and attach the communication manual or Modbus register map for that model and firmware. A product brochure is not enough.
  2. 02

    The Driver Factory assesses and builds

    First it checks whether the device is already supported. If there is enough register information, the driver is built and tested.
  3. 03

    Follow it in Watt

    You can see which steps have been completed and the stage of your request.
  4. 04

    Test the connection

    “Driver ready” does not yet mean the device works on your installation. We plan the field test together.
How to follow your requestFor each request, Watt shows which step has been reached.
  1. SubmittedYour request and documentation have been received
  2. StartedCheck whether the device is already supported
  3. Building driverThe Driver Factory builds from the register map
  4. ValidatingThe driver is tested in software
  5. PublishingThe driver is ready for a field test

Publishing means the driver is ready, not yet that it runs on your installation.

Good to know

The automated build route is aimed at Modbus (TCP or RTU). A device that only offers another protocol is not automatically suitable. Not every request leads straight to a driverdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s.: sometimes more information is needed, only reading data seems possible, or our team needs to review it. See which information you need to provide.

04Availability

Now in early access

The DriverdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s. Builder is available for accounts where it has been enabled. Want to connect a new device or use the DriverdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s. Builder? Get in touch and we'll discuss the options.

You choose the equipment. We help you connect it.

Read in the documentation how to submit and follow a driverdriverSoftwarecomponent die beschrijft hoe een apparaat werkt en communiceert, inclusief beschikbare data en commando’s. request.

Read about driver requestsSupported devices

Faster data exchange for external energy control

Faster than aFRR requires

In short

New
Installation data goes to an external party as often as every second.
Why
Fast applications such as aFRR need up-to-date data.
Safe
The Envi.Base keeps guarding your control strategies and power limits locally.
01How does it work?

Data goes out, control comes back

Two flows run between your installation and the market party. The Envi.Baseenvi.baseDe energiecontroller van Envitron die apparaten uitleest, aanstuurt en data opslaat achter de hoofdaansluiting. is always in between.

→ Data going out

The Envi.Baseenvi.baseDe energiecontroller van Envitron die apparaten uitleest, aanstuurt en data opslaat achter de hoofdaansluiting. collects the data from your equipment and shares it with the market party, so that party always knows the state of your installation.

Technical: Firehose

← Control coming back

The market party asks your battery to charge or discharge. The Envi.Baseenvi.baseDe energiecontroller van Envitron die apparaten uitleest, aanstuurt en data opslaat achter de hoofdaansluiting. only carries this out within your configured limits and what the equipment can do.

Technical: Third-party Storage Control
02What is aFRR?

Helping to keep the grid in balance

aFRR is reserve power that the grid operator deploys automatically to balance supply and demand on the electricity grid. A battery is well suited to this, because it can adjust quickly.

To do so, the market party needs up-to-date data from your installation at least every four seconds within the intended application. Envitron delivers it as often as every second.

Outside aFRR activations, the same battery can also be available for local optimisation or other energy trading, depending on configuration and agreements.

Read more about aFRR on our website

03Checklist

What should you think about?

Every project is different. Go through these questions to see what your installation needs.

  1. 01

    Your installation

    Is a battery connected to the Envi.Base, and does it suit the application you have in mind?
  2. 02

    The market party

    Do you already work with a party, or are you still looking for one? We already work with several market parties and are happy to help.
  3. 03

    The connection

    Is there already a validated connection between Envitron and that party? If not, we'll look at what's needed together.
  4. 04

    The control strategies

    What should stay active alongside the external control, for example local optimisation or your power limits?
Unsure about any of these points?

Get in touch and we'll go through them together for your project.

Useful to have at hand
  • Type of battery and inverter
  • Your market party, if already known
  • The application you have in mind
Get in touch
04Frequently asked questions

Short answers to the most common questions

Does the market party then decide everything about my battery?

No. The market party decides the desired control within the agreements made. The Envi.Baseenvi.baseDe energiecontroller van Envitron die apparaten uitleest, aanstuurt en data opslaat achter de hoofdaansluiting. remains locally responsible for your control strategies and power limits and takes the situation on site into account.

Can my battery do anything else besides aFRR?

Yes, depending on your configuration and the agreements. Outside aFRR activations the battery can, for example, be available for local optimisation or other energy trading, if the active control strategy allows it.

Is this only meant for aFRR?

No. The infrastructure was deliberately set up more broadly, so you can also use it for other applications that need fast external data exchange.

Can I take part in aFRR tomorrow?

The technology on Envitron's side is available. Actual deployment also needs a suitable, validated connection with your market party. Go through the checklist above or get in touch.

05For the technically minded

Read more in the documentation

FirehoseData going out: set up streams and connectorsFirehose payloadMessage format and measurement fieldsThird-party Storage ControlControl coming back through an external party

Fast data going out. Control stays local.

Get in touchMore about aFRR