{ "generated": "2026-09-29T21:14:37.409Z", "site": "https://edgetech.eu", "products": [ { "kind": "electronics", "slug": "evse-c-3x32a", "url": "https://edgetech.eu/electronics/evse-c-3x32a", "markdown": "https://edgetech.eu/electronics/evse-c-3x32a.md", "title": "Edge EV Charger controller", "partNumber": "EVSE-C-3x32A", "summary": "AC charge controller board for one Mode 3 charge point, up to 3×32 A (22 kW), with integrated relay drive, per-phase current and voltage metering, and Modbus RTU control. The board inside most EdgeTech-based chargers since 2021.", "status": "shipped", "pending": false, "price": 125, "priceNote": "per unit excl. VAT, ask for a quote above 5 units", "currency": "EUR", "vatIncluded": false, "leadTime": null, "ce": "https://mycharger.edgetech.nl/CE_ChargerController.pdf", "specs": [ { "name": "Charging", "value": "IEC 61851-1 Mode 3, 1-phase or 3-phase, 6–32 A continuous, max 3×32 A (22 kW)", "id": "charging" }, { "name": "Advertised maximum", "value": "16 A without jumper, 32 A with jumper; remotely limited per second over Modbus (register 0x0201)", "id": "current-limit" }, { "name": "Microcontroller", "value": "ATmega328PB, 16 MHz, bare-metal C firmware (open source)", "id": "mcu" }, { "name": "Metering", "value": "ACS71020 per-phase current and voltage, session and lifetime energy in 1/256 kWh steps. Not MID certified.", "id": "metering" }, { "name": "Switching", "value": "Integrated relay drive for the charge contactor; stuck-relay detection; earth, neutral and L1 self-test at every boot", "id": "switching" }, { "name": "Fieldbus", "value": "Modbus RTU slave over RS485, 9600 8N1 (19200 with EVSE-SC-02), default address 1, shipped at address 10", "id": "bus" }, { "name": "Failsafe", "value": "No Modbus message for 2 s → safe mode; internal temperature 62 °C → limit to 10 A, higher → charging off", "id": "failsafe" }, { "name": "DC leakage protection", "value": "6 mA DC-to-PE sensor (EVSE-X-DCD, IEC 62752) included with every controller; trip reported as error bit 5 (value 32)", "id": "dc-leakage" }, { "name": "Cable and lock", "value": "Fixed cable or Type 2 socket; PP resistor read for cable rating; lock actuator output with lock/unlock feedback", "id": "cable" }, { "name": "Signalling", "value": "Onboard RGB LED or NeoPixel strip (36 LEDs); CP disconnect for EV wake-up per IEC 61851-23 Ed. 2", "id": "signalling" }, { "name": "Supply", "value": "90–300 V AC, 50 Hz, 3 W", "id": "supply" }, { "name": "Dimensions", "value": "168 × 122 × 25 mm", "id": "dimensions" }, { "name": "Enclosure rating", "value": "IP00 (bare board, for installation in an enclosure), Class I", "id": "protection" }, { "name": "CE", "value": "Declaration 2022-001 EVSE-C-01: LVD 2014/35/EU, EMC 2014/30/EU, RoHS 2011/65/EU, IEC 61851-22", "id": "ce" } ], "interfaces": [ "Modbus RTU RS485", "RGB LED / NeoPixel", "cable lock", "CP disconnect", "SPI ISP for firmware" ], "standards": [ "IEC 61851-1", "IEC 61851-23 Ed. 2 (wake-up)", "IEC 62752 (with EVSE-X-DCD)", "Modbus RTU" ], "configurable": [], "faq": [ { "q": "Can I control the charge current from my own controller?", "a": "Yes. Write the maximum current in amps to Modbus register 0x0201 at least once per second. Writing 0 stops charging. If the board receives nothing for 2 s it falls back to its static limit." }, { "q": "Is the built-in meter MID certified?", "a": "No. The metering is accurate enough for load balancing and consumption overviews, but it is not a legal billing meter. Add an external MID meter if you bill by kWh." }, { "q": "Does it support ISO 15118 or Plug & Charge?", "a": "Not today. The board does basic PWM signalling per IEC 61851-1. ISO 15118 is on the roadmap as an add-on module; see the standards page." }, { "q": "Is the firmware open?", "a": "Yes. Firmware, register list, 3D brackets and the wiring diagram are on GitHub at edge-tech-eu/SmartEVSE." } ], "body": "## What it is\n\nOne board, one charge point. The EVSE-C-3x32A talks to the car over the control pilot, drives the contactor, measures current and voltage on each phase, and reports everything over Modbus RTU. Put it in an enclosure with a contactor, an MCB, an RCD and (for DC leakage) the EVSE-X-DCD module, and you have a Mode 3 AC charger.\n\nIt runs on its own, at a static limit of 16 A or 32 A. Connected to a site controller it becomes a dynamically limited charge point: the controller writes a new current limit every second, and the board falls back to a safe state if those writes stop.\n\n## What is on the board\n\n- Control pilot generation and measurement (states A, B, C, D per IEC 61851-1), proximity pilot reading for cable rating.\n- Relay drive for a 3-phase contactor, with stuck-relay detection and a boot-time self-test on earth, neutral and L1.\n- Per-phase current and voltage measurement with an ACS71020, giving session energy, lifetime energy and per-phase session energy.\n- RS485 transceiver, Modbus RTU slave.\n- Lock actuator drive with feedback, for socket variants.\n- CP disconnect output. Used to wake cars that go into deep sleep after a long pause, per IEC 61851-23 Edition 2. Shipped in firmware 2.10.17.\n- Temperature sensor. Above 62 °C the board limits to 10 A; above that it stops.\n- LED output: the onboard RGB LED, or a strip of up to 36 NeoPixels.\n- SPI header. The site controller can reflash the board's firmware in the field.\n\n## Integration notes\n\n- The controller must answer Modbus requests within 40 ms. This rules out RS485-over-Ethernet converters and wireless Modbus. Use a bus topology with shielded signal cable, three cores of at least 0.75 mm², not Ethernet cable.\n- Boards ship at Modbus address 10. Address 1 is a discovery address that only answers after a state change.\n- All analog registers are in 1/256 units: 5632 in a current register means 22.0 A.\n- A 1-phase to 3-phase switch during a session upsets most cars. Stop the session, wait 10 s, switch, restart.\n\nThe protocol is open and documented: [Modbus registers](/docs/modbus-registers). Load-balancing behaviour: [Load balancing](/docs/load-balancing).\n\n## Buying\n\n€ 125 per board excl. VAT and shipping. Above 5 units, ask for a quote. Volume customers get the board on a reel-to-enclosure basis with their own firmware defaults (address, LED type, lock type, 1P/3P) preloaded. [Contact us](/contact)." }, { "kind": "electronics", "slug": "evse-x-dcd", "url": "https://edgetech.eu/electronics/evse-x-dcd", "markdown": "https://edgetech.eu/electronics/evse-x-dcd.md", "title": "DC-leakage sensor", "partNumber": "EVSE-X-DCD", "summary": "The 6 mA DC-to-PE leakage sensor that is part of every EdgeTech charger and every electronics set. Separate hardware, not a separate product: it lets a Type A RCD be used upstream instead of a Type B (IEC 62752).", "status": "shipped", "pending": false, "price": null, "priceNote": "included with every charge controller", "currency": "EUR", "vatIncluded": false, "leadTime": null, "ce": null, "specs": [ { "name": "Standard", "value": "IEC 62752 / UL 2231 residual DC detection", "id": "standard" }, { "name": "Trip level", "value": "> 6 mA DC", "id": "trip" }, { "name": "Disconnect time", "value": "≈ 300 ms, via the charge controller relay", "id": "response" }, { "name": "Wiring", "value": "Neutral and all phases through the toroid; protective earth stays outside", "id": "wiring" }, { "name": "Configuration", "value": "None. No adjustable parameters.", "id": "config" }, { "name": "Failsafe", "value": "Loss of communication with the charge controller blocks charging; trip reported as error bit 5 (value 32) in the error byte of register 0x0103", "id": "failsafe" }, { "name": "When required", "value": "Every Mode 3 charge point on a Type A RCD (NEN 1010 / IEC 60364-7-722)", "id": "required" } ], "interfaces": [ "connector to EVSE-C-3x32A" ], "standards": [ "IEC 62752" ], "configurable": [], "faq": [ { "q": "Do I still need a Type B RCD?", "a": "No. With the EVSE-X-DCD detecting DC residual current above 6 mA, the charge point may be protected by a Type A RCD (30 mA) upstream, which is what NEN 1010 asks for." }, { "q": "Can two charge controllers share one module?", "a": "No. One module per charge controller. A two-socket cabinet uses two controllers and two modules." } ], "body": "## What it is\n\nA residual DC current detector that is delivered with every EVSE-C-3x32A and built into every finished charger. The car's onboard charger can leak DC current back into the installation; a normal Type A RCD does not see it and can be blinded by it. IEC 62752 asks the charge point to detect DC leakage above 6 mA itself, and this module does that.\n\nThe module has no settings. When it trips, the charge controller opens the contactor within about 300 ms, sets error bit 5 (value 32), and the MyCharger app or your own controller sees the fault in the socket status.\n\n## Installation\n\nRoute neutral and all connected phases through the toroid. Do not route the protective earth through it. Connect the module to the DCD header on the charge controller. If the controller loses communication with the module, charging is blocked until it is restored, so the module must be present when the DCL_MUST_BE_PRESENT setting is on, which is the shipped default." }, { "kind": "electronics", "slug": "evse-sc-01", "url": "https://edgetech.eu/electronics/evse-sc-01", "markdown": "https://edgetech.eu/electronics/evse-sc-01.md", "title": "Edge Load Balancer", "partNumber": "EVSE-SC-01", "summary": "First-generation site controller. Measures the main connection with three CT clamps and dynamically limits up to 4 Edge charge controllers over Modbus so the site never exceeds its main fuse. WiFi to the EdgeTech platform and the MyCharger app.", "status": "shipped", "pending": false, "price": 145, "priceNote": "per unit excl. VAT, ask for a quote above 5 units", "currency": "EUR", "vatIncluded": false, "leadTime": null, "ce": "https://mycharger.edgetech.nl/CE_SiteController.pdf", "specs": [ { "name": "Charge points", "value": "Up to 4 EVSE-C-3x32A on one RS485 bus", "id": "charge-points" }, { "name": "Site measurement", "value": "3 CT clamps (C1, C2, C3), standard up to 3×40 A; 50 A and 63 A clamps available", "id": "measurement" }, { "name": "Load balancing", "value": "Per-second current limit per charge point, site limit configurable up to the main fuse, minimum 6 A per car, start threshold 8 A", "id": "algorithm" }, { "name": "Fieldbus", "value": "Modbus RTU master, RS485, 9600 8N1", "id": "bus" }, { "name": "Connectivity", "value": "WiFi IEEE 802.11 b/g/n, 2.4 GHz only; MQTT over TLS with a per-device pre-shared key", "id": "wifi" }, { "name": "Module", "value": "Particle P1 WiFi module (STM32F2, 1 MB flash), hardware revision site-wifi-p1-revc", "id": "module" }, { "name": "Supply", "value": "90–300 V AC, 50 Hz, 300 mA / 3 W, powered from the consumer unit", "id": "supply" }, { "name": "Dimensions", "value": "90 × 54 × 58 mm, DIN-rail enclosure (3 modules)", "id": "dimensions" }, { "name": "Enclosure rating", "value": "IP00, Class I; install inside the consumer unit behind a fuse", "id": "protection" }, { "name": "CE", "value": "Declaration 2022-001 EVSE-SC-02: LVD, EMC, RoHS, EN 301 489-1/-17, EN 300 328, EN 62311", "id": "ce" } ], "interfaces": [ "Modbus RTU RS485 master", "WiFi 2.4 GHz", "3× CT clamp input" ], "standards": [ "Modbus RTU", "EN 300 328", "EN 301 489" ], "configurable": [], "faq": [ { "q": "Should I buy the SC-01 or the SC-02?", "a": "SC-02 if the site has a DSMR/ESMR 5 smart meter with a free P1 port; it needs no clamps and sees export as well as import, so solar charging works properly. SC-01 if there is no P1 port, or the main connection is above 3×63 A." }, { "q": "Does it work with solar panels?", "a": "Partly. The CT clamps measure magnitude reliably but the direction of current under PV export is not always detected correctly, so surplus-solar charging is unreliable on the SC-01. Use the SC-02 for solar sites." } ], "body": "## What it is\n\nA DIN-rail module for the consumer unit that watches the main connection with three current clamps and tells each charge controller, every second, how much current it may draw. Four charge points on a 3×25 A connection can all be plugged in; the load balancer splits what is left after the house or building has taken its share.\n\nThe module connects over WiFi to the EdgeTech platform, which gives users the MyCharger app (start/stop, off-peak charging, consumption overview, automatic invoicing) and gives installers remote diagnostics and firmware updates.\n\n## Load-balancing behaviour\n\n- Reads the three clamps continuously and computes the available headroom per phase against the configured site limit.\n- Writes a new maximum current to each charge controller once per second. If a controller does not hear from the site controller for 2 s it drops to its safe limit.\n- Never lets a car go below 6 A (the IEC 61851 minimum); a car is only started when at least 8 A is available. If more cars are plugged in than can be served at 6 A, the last ones wait.\n- Optional site-wide 1-phase mode for small connections.\n\nDetails and the configuration keys: [Load balancing](/docs/load-balancing).\n\n## Limits\n\n- 3×40 A standard clamps; 3×63 A needs the large clamps. Above 3×63 A, use the SC-02 with a P1 meter or the GridShield controller with a kWh meter.\n- WiFi is 2.4 GHz only. Sites with poor WiFi coverage in the meter cupboard need a repeater or an access point nearby.\n- Maximum 4 charge controllers. For more, use the SC-02 (up to 10)." }, { "kind": "electronics", "slug": "evse-sc-02", "url": "https://edgetech.eu/electronics/evse-sc-02", "markdown": "https://edgetech.eu/electronics/evse-sc-02.md", "title": "Edge Smart Load Balancer", "partNumber": "EVSE-SC-02", "summary": "Current-generation site controller. Reads the DSMR/ESMR 5 smart meter through its P1 port, so it needs no clamps, sees import and export per phase, and dynamically limits up to 10 Edge charge controllers. Solar-surplus charging, WiFi, MyCharger app.", "status": "shipped", "pending": false, "price": 145, "priceNote": "per unit excl. VAT, ask for a quote above 5 units", "currency": "EUR", "vatIncluded": false, "leadTime": null, "ce": "https://mycharger.edgetech.nl/CE_SiteController.pdf", "specs": [ { "name": "Charge points", "value": "Up to 10 EVSE-C-3x32A on one RS485 bus (8 recommended for sites with many simultaneous sessions)", "id": "charge-points" }, { "name": "Site measurement", "value": "P1 port of a DSMR 5.0 / ESMR 5.0 smart meter (Netherlands, Belgium); per-phase import and export power, per-phase voltage and current", "id": "measurement" }, { "name": "Load balancing", "value": "Per-second current limit per charge point; site limit, solar mode and 1P/3P per socket configurable; minimum 6 A per car, start threshold 8 A", "id": "algorithm" }, { "name": "Solar charging", "value": "Surplus mode charges only on export; solar-assist mode tops up from the grid. Uses meter export values, not clamps.", "id": "solar" }, { "name": "Fieldbus", "value": "Modbus RTU master, RS485, 19200 8N1 (switches fresh charge controllers from 9600 automatically)", "id": "bus" }, { "name": "Connectivity", "value": "WiFi IEEE 802.11 b/g/n, 2.4 GHz only; MQTT over TLS with a per-device pre-shared key", "id": "wifi" }, { "name": "Module", "value": "Particle P1 WiFi module, hardware revision site-p1-smartmeter", "id": "module" }, { "name": "Supply", "value": "From the P1 port (meter must supply ≥ 250 mA) or 5 V via micro-USB", "id": "supply" }, { "name": "Dimensions", "value": "88 × 90 × 25 mm, mounted next to the meter, not inside the consumer unit", "id": "dimensions" }, { "name": "Setup", "value": "WiFi credentials via the Mode pinhole (hold 3 s) and the MyCharger app; restart by unplugging the RJ12 for 3 s", "id": "setup" }, { "name": "CE", "value": "Declaration 2022-001 EVSE-SC-02: LVD, EMC, RoHS, EN 301 489-1/-17, EN 300 328, EN 62311", "id": "ce" } ], "interfaces": [ "P1 (RJ12) DSMR/ESMR 5", "Modbus RTU RS485 master", "WiFi 2.4 GHz", "micro-USB power" ], "standards": [ "DSMR 5.0 / ESMR 5.0 P1", "Modbus RTU", "EN 300 328", "EN 301 489" ], "configurable": [], "faq": [ { "q": "Which smart meters work?", "a": "Any DSMR 5.0 or ESMR 5.0 meter with a P1 port, which is every meter installed in the Netherlands since about 2016, and Belgian Fluvius meters. Older DSMR 4 meters send too slowly and do not power the port. Austrian meters use a different, encrypted P1 and are not supported." }, { "q": "The P1 port is already used by another device.", "a": "Use a powered P1 splitter. The SC-02 needs at least 250 mA from the port; if the meter cannot supply it, power the SC-02 over micro-USB." }, { "q": "Can it drive third-party chargers?", "a": "Not directly. It drives Edge charge controllers over Modbus. To limit third-party chargers or a heat pump, use the GridShield receiver, which has Modbus, relay and SG-Ready outputs." } ], "body": "## What it is\n\nThe site controller EdgeTech ships today. Plug it into the P1 port of the smart meter and it knows, every second, what the whole installation draws or exports on each phase. From that it gives each charge controller a current limit, once per second, over RS485.\n\nBecause it reads the meter instead of clamps, it sees the direction of current. That makes solar-surplus charging work: the car is charged from what the roof produces, and the grid limit is respected at the same time.\n\n## What the P1 telegram gives us\n\nThe SC-02 uses these fields from the DSMR/ESMR 5 telegram, at 1 s intervals: per-phase instantaneous power delivered and returned, per-phase voltage and current, and the meter's cumulative registers for consumption reporting. The full list of OBIS codes is on the [P1 telemetry](/docs/p1-telemetry) page.\n\n## Solar modes\n\n| Mode | Behaviour |\n|---|---|\n| Off | Charge at the maximum the site allows, regardless of PV |\n| Solar assist | Prefer PV surplus, top up from the grid so the car always charges at ≥ 6 A |\n| Solar only | Charge only on PV surplus; pause below 6 A surplus (3-phase: 3×6 A) |\n\nSwitching a session between 1-phase and 3-phase to widen the solar window is done per socket with a 10 s pause, the same behaviour EdgeTech contributed to evcc.\n\n## Limits\n\n- 2.4 GHz WiFi only; limited to 100 platform messages per day per device to keep the shared platform quiet.\n- The RS485 bus runs at 19200 baud; charge controllers at 9600 are switched automatically on first contact.\n- Up to 10 charge controllers on one bus. Above that, split the site over two SC-02 units on two P1 splitter ports, or use GridShield." }, { "kind": "electronics", "slug": "matter-set", "url": "https://edgetech.eu/electronics/matter-set", "markdown": "https://edgetech.eu/electronics/matter-set.md", "title": "Matter over Thread set", "partNumber": "MATTER-SET", "summary": "The wireless smart set: our charge controller with a Thread module, a P1 meter reader on the smart meter, a Matter controller that runs the load balancing, and an optional SG-Ready module for a heat pump. All Matter 1.4 over Thread. Not CSA-certified; certification on the customer's request.", "status": "on-order", "pending": false, "price": null, "priceNote": "on request; per module and as a set", "currency": "EUR", "vatIncluded": false, "leadTime": null, "ce": null, "specs": [ { "name": "Charger Thread module", "value": "Attaches to the EVSE-C-3x32A over RS485; Matter Energy EVSE device type (0x050C) with Energy EVSE (0x0099), Energy EVSE Mode (0x009D) and Electrical Power Measurement (0x0090) per phase; Device Energy Management (0x0098) present as a stub", "id": "charger-module" }, { "name": "P1 Thread meter reader", "value": "On the P1 port of a DSMR 5 meter; Electrical Power Measurement per phase, export negative, 1 s", "id": "p1-reader" }, { "name": "Matter controller (hub)", "value": "Thread border router and Matter controller; runs the per-second load balancing; three hardware sizes depending on the site", "id": "hub" }, { "name": "SG-Ready module (optional)", "value": "Two relays on a heat pump's SG-Ready contacts as two Matter On/Off Plug-in Units (0x010A)", "id": "sg-ready" }, { "name": "Certification", "value": "Not CSA-certified. Certification is expensive and is done on the customer's request and cost.", "id": "certification" }, { "name": "Load balancing", "value": "On the hub, through UserMaximumChargeCurrent; the same rules as the wired variant (6 A minimum, fail-safe fallback)", "id": "control" }, { "name": "Third-party controllers", "value": "To be confirmed: Home Assistant Matter server works in our lab; consumer ecosystems do not commission the Energy EVSE device type yet", "id": "ecosystems" } ], "interfaces": [ "Thread", "Matter 1.4", "RS485 to the charge controller", "P1" ], "standards": [ "Matter 1.4 Energy EVSE", "Matter Electrical Power Measurement", "Thread 1.3/1.4", "IEEE 802.15.4" ], "configurable": [], "faq": [ { "q": "Why not certified?", "a": "CSA certification costs more than most projects justify. The set works with our own controller out of the box. When a customer needs the Matter logo, we run the certification for that product on request." }, { "q": "Does it still connect to the platform and the app?", "a": "To be confirmed. The hub has an MQTT bridge, so the same platform, app and chat can be offered; whether the wireless set ships cloud-connected or local-only is a decision still open." } ], "body": "## What it is\n\nThe smart set without the RS485 bus to the meter cupboard. The charge controller gets a Thread module and becomes a Matter Energy EVSE device; a small reader on the smart meter's P1 port becomes a Matter power meter; a controller box runs the load balancing and talks to both. A heat pump joins with the SG-Ready module.\n\nEverything is standard Matter 1.4 over Thread, so the devices show up in a Matter controller like any other device, with real device types and clusters, not a vendor bridge.\n\n## What we say and do not say\n\nWe say \"Matter over Thread\". We do not name the radio modules or the controller hardware inside; they are components, and they change. We say \"not certified\", and we offer certification on request." }, { "kind": "electronics", "slug": "gridshield", "url": "https://edgetech.eu/electronics/gridshield", "markdown": "https://edgetech.eu/electronics/gridshield.md", "title": "GridShield controller and receiver", "partNumber": "GS-C-01 / GS-R-02", "summary": "ElaadNL-compliant GridShield over LoRa point-to-point: one hardware, two roles, sold as two products. The controller measures the main connection and sends the reduce signal; the receiver limits chargers over RS485 and other loads with two relays. Tested against ElaadNL's implementation in both directions. For neighbourhood congestion and for buildings, car parks and sites without a data cable.", "status": "shipped", "pending": false, "price": 370, "priceNote": "controller + receiver set excl. VAT; per variant on request", "currency": "EUR", "vatIncluded": false, "leadTime": null, "ce": null, "specs": [ { "name": "Roles", "value": "Controller (GS-C-01): measures the main connection, broadcasts the available capacity. Receiver (GS-R-02): acts on the broadcast. Same hardware and firmware, configured per role; the controller has a larger antenna and possibly a different casing.", "id": "roles" }, { "name": "Protocol", "value": "GridShield (ElaadNL), LoRa point-to-point at 868 MHz; no LoRaWAN, no gateway, no subscription", "id": "protocol" }, { "name": "Interoperability", "value": "Tested against ElaadNL's GridShield implementation in both directions: EdgeTech controller with ElaadNL receivers, ElaadNL controller with EdgeTech receivers", "id": "interop" }, { "name": "Controller inputs", "value": "3 CT clamp inputs, or a Modbus kWh meter over RS485", "id": "inputs" }, { "name": "Receiver outputs", "value": "RS485 Modbus (EdgeTech or compatible chargers), 2 relays (SG-Ready heat pump or any load), open-collector output", "id": "outputs" }, { "name": "Range", "value": "Hundreds of metres in the open; several receivers per controller, several chargers per receiver", "id": "range" }, { "name": "Supply", "value": "3.8–32 V DC via the Modbus connector or USB-C", "id": "supply" }, { "name": "Dimensions", "value": "35 × 105 × 11 mm board", "id": "dimensions" }, { "name": "On loss of signal", "value": "Receiver falls back to a configured safe limit after a configurable timeout", "id": "failsafe" } ], "interfaces": [ "LoRa 868 MHz point-to-point", "3× CT clamp", "Modbus RTU RS485", "2× relay", "open collector", "USB-C" ], "standards": [ "GridShield (ElaadNL)", "Modbus RTU", "SG-Ready", "EN 300 220" ], "configurable": [], "faq": [ { "q": "What is GridShield?", "a": "ElaadNL's mechanism for protecting a grid connection or a neighbourhood cable. A controller at the connection measures the load and broadcasts the remaining capacity; every receiver behind it scales its loads down. It is meant as a last resort that keeps the fuse and the transformer inside their limits when everything else has failed." }, { "q": "Do I need a LoRaWAN subscription?", "a": "No. Controller and receivers talk directly on 868 MHz. There is no gateway, no network server and no subscription." }, { "q": "Can one unit be both?", "a": "The hardware can; a unit is configured for one role. Order a controller for the connection and a receiver per cluster of loads." } ], "body": "## Two scales, one product\n\n**Neighbourhood.** A grid operator or ElaadNL uses GridShield as the last-resort signal on a shared cable or transformer: when the neighbourhood as a whole uses too much, every GridShield receiver scales down its chargers and heat pumps. EdgeTech's receiver is compliant with that signal and has been tested against ElaadNL's implementation in both directions.\n\n**Building, car park, site, home.** The same pair works locally. The controller measures the main connection with clamps or a kWh meter and broadcasts headroom; receivers at the chargers, the heat pump or any other load act on it. No data cable, hundreds of metres of range, nothing to subscribe to.\n\n## How it works\n\n1. The controller measures the main connection, or receives the grid operator's signal.\n2. It broadcasts the available current per phase over LoRa point-to-point.\n3. Each receiver limits what it controls: EdgeTech or compatible chargers over Modbus, a heat pump over the SG-Ready contacts, anything else over the relays.\n4. A receiver that misses broadcasts for longer than its timeout falls back to its safe limit.\n\n## Where it fits\n\nTemporary charge points on construction sites and events; charge points spread over holiday parks and marinas; car parks where the meter is in another building; existing installations with third-party chargers or heat pumps that need a grid limit without rewiring; and any site a grid operator asks to be GridShield-ready." }, { "kind": "electronics", "slug": "iso15118-module", "url": "https://edgetech.eu/electronics/iso15118-module", "markdown": "https://edgetech.eu/electronics/iso15118-module.md", "title": "ISO 15118 communication module", "partNumber": "PLC-15118", "summary": "An add-on for the smart charger: HomePlug GreenPHY on the control pilot for ISO 15118 digital communication with the vehicle. With 15118-20 vehicles it shows the state of charge while charging on AC and identifies the vehicle for authorisation. Expensive, on request; V2G under investigation.", "status": "on-order", "pending": false, "price": null, "priceNote": "on request (expensive)", "currency": "EUR", "vatIncluded": false, "leadTime": null, "ce": null, "specs": [ { "name": "Function", "value": "ISO 15118 digital communication over the control pilot (HomePlug GreenPHY), next to the IEC 61851 PWM signalling", "id": "function" }, { "name": "State of charge on AC", "value": "Available with ISO 15118-20 vehicles; -2 vehicles do not report SoC on AC", "id": "soc" }, { "name": "Vehicle identification", "value": "EVCCID at SLAC, or the vehicle certificate with Plug & Charge; usable for card-less authorisation and billing", "id": "vehicle-id" }, { "name": "Fallback", "value": "Analog IEC 61851 per ISO 15118-3 when the vehicle does not speak 15118", "id": "fallback" }, { "name": "V2G / bidirectional", "value": "Under investigation. Needs a bidirectional on-board charger in the vehicle, a grid-code path for feed-in and 15118-20 bidirectional power transfer. Nothing claimed until investigated.", "id": "v2g" }, { "name": "Plug & Charge", "value": "Needs a certificate backend (CPO / PKI); to be confirmed", "id": "pnc" } ], "interfaces": [ "Control pilot PLC (HomePlug GreenPHY)", "connection to the charge controller" ], "standards": [ "ISO 15118-2", "ISO 15118-3", "ISO 15118-20" ], "configurable": [], "faq": [ { "q": "Which vehicles report state of charge on AC?", "a": "Only vehicles with ISO 15118-20. Older vehicles with -2 or without digital communication do not. Ask for the current list before you promise SoC to a customer." } ], "body": "## Why it exists\n\nTwo things a plain Mode 3 charger cannot do: know how full the battery is, and know which car is plugged in. With ISO 15118 on the pilot, both become possible, and a charger can start for a known vehicle without a card and stop when the battery is at the level the user asked for.\n\n## Status\n\nA working design on the roadmap, delivered as a product when a customer orders it. Price on request; it is the most expensive option on the charger. V2G is a separate investigation, technical and regulatory, and is not part of this module today." }, { "kind": "electronics", "slug": "nfc-reader", "url": "https://edgetech.eu/electronics/nfc-reader", "markdown": "https://edgetech.eu/electronics/nfc-reader.md", "title": "NFC card reader", "partNumber": "NFC-RDR", "summary": "An optional card reader for the charger. Two modes: a Dutch laadpas over OCPP for public and semi-public charging with roaming billing, or any NFC card as a local lock and unlock with a whitelist managed by the owner.", "status": "on-order", "pending": false, "price": null, "priceNote": "on request", "currency": "EUR", "vatIncluded": false, "leadTime": null, "ce": null, "specs": [ { "name": "Modes", "value": "Laadpas over OCPP 1.6J (authorisation and billing by a back-office), or local whitelist (no back-office)", "id": "modes" }, { "name": "Cards", "value": "ISO/IEC 14443 (MIFARE / NFC-A); UID-based; specification of the reader module to be confirmed", "id": "cards" }, { "name": "Whitelist", "value": "Managed by the owner in the app; number of cards to be confirmed", "id": "whitelist" }, { "name": "OCPP path", "value": "Depends on OCPP 1.6J being finished into a product for your project (working implementation, not yet deployed)", "id": "ocpp" } ], "interfaces": [ "connection to the charge controller or site controller" ], "standards": [ "ISO/IEC 14443", "OCPP 1.6J (mode 1)" ], "configurable": [], "faq": [], "body": "## Where it fits\n\nFlats and VvE car parks where each user pays for their own kWh; company car parks that should not charge the neighbours' cars; Plaza Charge poles; and any charger that must accept a public charge card.\n\n## The card-less alternative\n\nWith the ISO 15118 module the vehicle identifies itself, and no card is needed. For most sites the NFC reader is the cheaper answer." }, { "kind": "chargers", "slug": "simple-charger", "url": "https://edgetech.eu/chargers/simple-charger", "markdown": "https://edgetech.eu/chargers/simple-charger.md", "title": "Simple charger", "partNumber": "EDGE-CH-S", "summary": "Our electronics in a generic grey box with a fixed charging cable. Mode 3, up to 3×32 A, DC-leakage sensor included, open Modbus protocol. Option: three-colour status lights. The charger for installers and wholesalers who want a reliable unit without a brand story.", "status": "shipped", "pending": false, "price": null, "priceNote": null, "currency": "EUR", "vatIncluded": false, "leadTime": "Produced to order; confirmed with the quotation", "ce": null, "specs": [ { "name": "Electronics", "value": "EVSE-C-3x32A charge controller with DC-leakage sensor; optional site controller (wired or Matter) for load balancing", "id": "electronics" }, { "name": "Power", "value": "1-phase 16 or 32 A, or 3-phase up to 32 A (22 kW)", "id": "power" }, { "name": "Cable", "value": "Fixed Type 2 cable; length options to be confirmed", "id": "cable" }, { "name": "Enclosure", "value": "Generic grey box; dimensions and IP rating to be confirmed", "id": "enclosure" }, { "name": "Option: status lights", "value": "Three-colour indication of the charging state", "id": "lights" }, { "name": "Protection", "value": "6 mA DC-leakage sensor on board (IEC 62752); Type A RCD and MCB upstream", "id": "protection" }, { "name": "CE", "value": "Declared by EdgeTech for the standard unit", "id": "ce" } ], "interfaces": [], "standards": [], "configurable": [ { "name": "Phases", "options": "1-phase 16/32 A, 3-phase 32 A" }, { "name": "Site controller", "options": "None (stand-alone), SC-01 clamps, SC-02 P1, Matter over Thread" }, { "name": "Status lights", "options": "With or without" }, { "name": "NFC reader", "options": "With or without" } ], "faq": [ { "q": "What is the difference with the display charger?", "a": "The box and the electronics are the same; the display charger has a transparent lid with a display behind it. Everything else, including the app, is identical." } ], "body": "## What you get\n\nA finished, tested charger with the same boards that sit inside thousands of OEM chargers, in a box that does not pretend to be anything else. Installers hang it, plug in the RS485 or pair the Matter set, and the platform does the rest." }, { "kind": "chargers", "slug": "display-charger", "url": "https://edgetech.eu/chargers/display-charger", "markdown": "https://edgetech.eu/chargers/display-charger.md", "title": "Charger with display", "partNumber": "EDGE-CH-D", "summary": "The same grey box and electronics as the simple charger, with a transparent lid and a display behind it. Shows charging state, current and energy at the charger.", "status": "shipped", "pending": false, "price": null, "priceNote": null, "currency": "EUR", "vatIncluded": false, "leadTime": "Produced to order; confirmed with the quotation", "ce": null, "specs": [ { "name": "Electronics", "value": "As the simple charger", "id": "electronics" }, { "name": "Display", "value": "Behind a transparent lid; shows state, current per phase, session energy; content to be confirmed", "id": "display" }, { "name": "Status lights", "value": "Optional, as the simple charger", "id": "lights" } ], "interfaces": [], "standards": [], "configurable": [ { "name": "Phases", "options": "1-phase 16/32 A, 3-phase 32 A" }, { "name": "Site controller", "options": "None, SC-01, SC-02, Matter over Thread" }, { "name": "NFC reader", "options": "With or without" } ], "faq": [], "body": "## Who it is for\n\nSites where the user wants to see what the charger is doing without opening the app: company car parks, VvE garages, and installers who prefer to read the state at the box." }, { "kind": "chargers", "slug": "customized-charger", "url": "https://edgetech.eu/chargers/customized-charger", "markdown": "https://edgetech.eu/chargers/customized-charger.md", "title": "Customized charger", "partNumber": "EDGE-OEM-AC", "summary": "The grey box with your own front, with or without lights or display: a white-label charger under your name, with the MyCharger app under your name if you want it. The same electronics, the same platform, your brand. From this step it is a short way to your own enclosure and electronics through engineering.", "status": "shipped", "pending": false, "price": null, "priceNote": null, "currency": "EUR", "vatIncluded": false, "leadTime": "First batch 8–12 weeks after design freeze (indicative); repeat batches 4–6 weeks", "ce": null, "specs": [ { "name": "Charge points per unit", "value": "1 or 2, each on its own EVSE-C-3x32A and EVSE-X-DCD", "id": "charge-points" }, { "name": "Power", "value": "1-phase 16 A or 32 A, or 3-phase up to 32 A (22 kW) per charge point", "id": "power" }, { "name": "Connector", "value": "Type 2 socket with lock, or fixed Type 2 cable (5 m or 7.5 m)", "id": "connector" }, { "name": "Protection", "value": "DC leakage 6 mA (IEC 62752) on board; upstream Type A RCD 30 mA and MCB per charge point supplied by the installer or built in", "id": "protection" }, { "name": "Load balancing", "value": "Dynamic per-second limiting with EVSE-SC-02 (P1) or EVSE-SC-01 (clamps), or wireless with GridShield", "id": "load-balancing" }, { "name": "App and platform", "value": "MyCharger app (iOS, Android): start/stop, off-peak schedules, solar modes, consumption overview, automatic invoicing. Installer diagnostics and OTA updates.", "id": "platform" }, { "name": "Signalling", "value": "RGB status LED or NeoPixel light ring, colours configurable", "id": "signalling" }, { "name": "Authorisation", "value": "Plug and charge, app start, scheduled. RFID on request.", "id": "authorisation" }, { "name": "Metering", "value": "On-board metering (not MID). MID meter as an option for billing.", "id": "metering" }, { "name": "CE", "value": "Charge controller and site controller carry their own EU declarations of conformity (LVD, EMC, RoHS, IEC 61851-22, RED). The assembled unit is declared by the party placing it on the market; we supply the technical file.", "id": "ce" }, { "name": "Manufactured", "value": "Boards and assembly in the Netherlands / EU", "id": "made-in" } ], "interfaces": [], "standards": [], "configurable": [ { "name": "Enclosure", "options": "Your own enclosure, or one of the reference enclosures (wall box, single pole, double pole)" }, { "name": "Branding", "options": "Front label, LED colours, app name and icon (white-label MyCharger), splash and support contact" }, { "name": "Charge points", "options": "1 or 2 per unit; up to 10 per site controller" }, { "name": "Connector", "options": "Socket with lock; fixed cable 5 m or 7.5 m" }, { "name": "Phases", "options": "1-phase 16/32 A, 3-phase 32 A; per-socket 1P/3P switching for solar" }, { "name": "Site measurement", "options": "P1 (SC-02), CT clamps (SC-01), GridShield wireless, or none" }, { "name": "Firmware defaults", "options": "Modbus address, lock type, LED type, CP disconnect behaviour, min/max current" }, { "name": "Metering", "options": "On-board, or external MID meter" }, { "name": "Platform", "options": "EdgeTech-hosted platform, or your own instance of the charging platform (on-premise deployable)" } ], "faq": [ { "q": "What is the minimum order?", "a": "There is no hard minimum for the reference enclosures. A custom enclosure or a white-labelled app is worth it from roughly 50 units a year; below that we recommend the reference build with your label." }, { "q": "Who signs the CE declaration of the finished charger?", "a": "The company that places the charger on the market under its name. EdgeTech supplies the declarations of the boards, the technical documentation of the reference build, and if wanted, does the assembled-unit testing with you." }, { "q": "Can we run the backend ourselves?", "a": "Yes. The charging platform is a Quarkus application with file-based databases that deploys on a single Linux host inside your network. It was built for telecom customers who run their own vulnerability scans and cannot depend on external services." } ], "body": "## What you get\n\nA charger that is already in the field in several thousand charge points under other brands: the same charge controller, DC leakage module and site controller, assembled and tested, with your name on it.\n\nYou do not need to know anything about control pilots, contactors, DC leakage, Modbus or over-the-air updates. You need to know what enclosure you want, how many charge points, and whether you want the app under your own name.\n\n## The reference build\n\n| Part | Function |\n|---|---|\n| EVSE-C-3x32A | Charge controller: pilot, contactor, metering, Modbus |\n| EVSE-X-DCD | 6 mA DC leakage detection |\n| Contactor 4P 40 A | Switching, driven by the controller |\n| Type 2 socket with lock, or fixed cable | Vehicle connection |\n| EVSE-SC-02 (per site) | P1 site controller: load balancing, WiFi, platform |\n| Enclosure | Wall box or pole, IP54 or better |\n\nEvery part in this table is specified, sourced and tested. The bill of materials, wiring diagram and assembly instructions are part of the technical file you receive.\n\n## Lead times\n\nIndicative. First batch 8 to 12 weeks after the design is frozen, of which most is enclosure tooling and the assembled-unit tests. Repeat batches 4 to 6 weeks. Boards are stocked; the enclosure is usually the long pole.\n\n## From white-label to your own\n\nMost OEM customers start with the reference build. When volumes grow, they take the [engineering](/engineering) route and design their own enclosure and electronics around the same boards. The boards, firmware and platform stay the same, so nothing in the field has to change." }, { "kind": "chargers", "slug": "plaza-charge", "url": "https://edgetech.eu/chargers/plaza-charge", "markdown": "https://edgetech.eu/chargers/plaza-charge.md", "title": "Plaza Charge", "partNumber": "PLAZA", "summary": "Many cars charged overnight from a regular 3×25 A connection. Up to 12 plugs per pole, placed between 4 + 4 parking spaces. Every car gets a guaranteed minimum of 17.25 kWh in 12 hours, roughly 100 km, and more when fewer cars are connected. Very cheap, slow, and enough for the next day.", "status": "on-order", "pending": false, "price": null, "priceNote": "on request, per pole", "currency": "EUR", "vatIncluded": false, "leadTime": "On request", "ce": null, "specs": [ { "name": "Plugs per pole", "value": "Up to 12, between 4 + 4 parking spaces", "id": "plugs" }, { "name": "Grid connection", "value": "Regular low-amperage connection, 3×25 A as the reference case", "id": "connection" }, { "name": "Guaranteed minimum", "value": "17.25 kWh per car in 12 hours with 12 cars connected (3 × 25 A × 230 V × 12 h / 12); more with fewer cars or a larger connection", "id": "guarantee" }, { "name": "Use", "value": "Overnight top-up for residents, employees, fleets; not fast charging", "id": "use" }, { "name": "Sites", "value": "Car parks, VvE garages, company lots, and DC fast-charging sites that want cheap overnight AC charging for taxis, vans and buses", "id": "sites" }, { "name": "Metering and authorisation", "value": "Per plug; NFC reader as the standard authorisation; details to be confirmed", "id": "metering" } ], "interfaces": [], "standards": [], "configurable": [], "faq": [ { "q": "Is 17 kWh enough?", "a": "For most commuters, yes. 17 kWh is about 100 km. A car that needs more one night can take more when its neighbours are full or absent; the guarantee is the floor, not the ceiling." } ], "body": "## The idea\n\nCharging infrastructure is expensive because it is sized for the fastest case. Plaza Charge is sized for the common case: a car parked for the night on a connection the building already has. One 3×25 A connection, twelve plugs, and the load balancing spreads the current so every car is ready for the next day.\n\n## Details to come\n\nCurrent per plug, phases, how the twelve plugs share the feed, pole dimensions, price per pole and lead time are being finalised. Ask for this and we will send the current specification." }, { "kind": "chargers", "slug": "diy-kit", "url": "https://edgetech.eu/chargers/diy-kit", "markdown": "https://edgetech.eu/chargers/diy-kit.md", "title": "DIY smart charging kit", "partNumber": "EDGE-DIY-KIT", "summary": "Everything to build one smart, load-balanced charge point: charge controller with DC-leakage sensor, P1 site controller, cabling, brackets and the app. Kept for installers and wholesalers who assemble their own; whether it stays on the site as a product is not yet decided.", "status": "shipped", "pending": true, "price": 350, "priceNote": "per kit excl. VAT, ask for a quote above 5 kits", "currency": "EUR", "vatIncluded": false, "leadTime": "From stock", "ce": null, "specs": [ { "name": "Contents", "value": "1× EVSE-C-3x32A, 1× EVSE-X-DCD, 1× EVSE-SC-02, RS485 cable, P1 cable, 3D-printed mounting brackets, wiring diagram", "id": "contents" }, { "name": "Not included", "value": "Enclosure, contactor, MCB, Type A RCD, socket or cable. The wiring diagram lists suitable parts.", "id": "not-included" }, { "name": "Power", "value": "1-phase 16/32 A or 3-phase up to 32 A, set by jumper and configuration", "id": "power" }, { "name": "Load balancing", "value": "Dynamic against the main fuse and solar surplus via the P1 port", "id": "load-balancing" }, { "name": "App", "value": "MyCharger (iOS, Android) with a free trial of the platform subscription; 60 days", "id": "app" }, { "name": "Installation", "value": "By or under supervision of a qualified electrician; NEN 1010 applies. Dutch manual and a video walk-through are provided.", "id": "install" } ], "interfaces": [], "standards": [], "configurable": [], "faq": [ { "q": "Is this legal to install myself?", "a": "In the Netherlands, work in the consumer unit and a new circuit for a charge point must be done or checked by a qualified electrician under NEN 1010. The kit is designed to make that job short. It is not a consumer plug-in product." }, { "q": "Which enclosure should I use?", "a": "Any IP54 enclosure with room for the 168 × 122 mm controller, a 4-pole contactor and the socket or cable gland. The open-source repository has 3D brackets for common enclosures." }, { "q": "Can I skip the site controller and just use the charge controller?", "a": "Yes. The charge controller runs stand-alone at 16 A or 32 A. Without the SC-02 there is no load balancing, no solar mode and no app." } ], "body": "## What it is\n\nThe same boards that go into commercial chargers, packed for one installation, with the brackets, cables and documentation you need to put them in an enclosure of your choice.\n\nThe kit exists because the first EdgeTech customers were installers who wanted to build their own charge points instead of buying a black box. The build instructions, brackets and wiring diagram are open on GitHub, and this kit is the fastest way to get the matching hardware.\n\n## What you build\n\n1. Mount the charge controller and the DC leakage module in the enclosure with the brackets.\n2. Wire the contactor, the socket or cable, and the supply. Route N and phases through the DCD toroid.\n3. Mount the SC-02 next to the smart meter, connect the P1 cable and the RS485 cable to the charge controller.\n4. Set the jumper for 16 A or 32 A. Power up: the controller self-tests earth, neutral and L1 and blinks green.\n5. Install MyCharger, pair the SC-02 over WiFi, set your main fuse and solar mode.\n\nThe Dutch installation and user manual is at [mycharger.edgetech.nl](https://mycharger.edgetech.nl/Handleiding_SlimLaden.pdf). The DIY build guide is on GitHub at [edge-tech-eu/SmartEVSE](https://github.com/edge-tech-eu/SmartEVSE/blob/main/DHZ-laadpaal.md)." } ] }