From f568874d707c604ca5be0a92f13920bf1695f57e Mon Sep 17 00:00:00 2001 From: David M Date: Fri, 27 Dec 2024 13:21:47 +0100 Subject: [PATCH] add guides --- .../compatible-devices/apsystems.md | 90 ++++++++++++++++++ .../energy-gateway/compatible-devices/deye.md | 69 ++++++++++++++ .../compatible-devices/fronius.md | 95 ++++++++++++++++++- .../compatible-devices/huawei.md | 85 ++++++++++++++++- .../compatible-devices/overview.md | 67 ++++++------- docs/energy-gateway/compatible-devices/sma.md | 94 +++++++++++++++++- .../compatible-devices/solaredge.md | 78 +++++++++++++-- .../compatible-devices/sungrow.md | 28 +++++- 8 files changed, 560 insertions(+), 46 deletions(-) create mode 100644 docs/energy-gateway/compatible-devices/apsystems.md create mode 100644 docs/energy-gateway/compatible-devices/deye.md diff --git a/docs/energy-gateway/compatible-devices/apsystems.md b/docs/energy-gateway/compatible-devices/apsystems.md new file mode 100644 index 00000000..52ac33c7 --- /dev/null +++ b/docs/energy-gateway/compatible-devices/apsystems.md @@ -0,0 +1,90 @@ +# Modbus TCP Configuration - APsystems ECU + +## Communication Setup Overview + +APsystems inverters use RS-485 communication via RJ45. To connect to a network, a bridge device is needed to convert RS-485 to Modbus TCP. The Waveshare RS485 to ETH converter (RS232/485 to ETH-B) can be used for this purpose and is available from [Waveshare](https://www.waveshare.com/RS232-485-TO-ETH.htm) directly. + +## Prerequisites + +- Mobile device with `EMA Manager` app installed from: + - `App Store` (iOS) + - `Play Store` (Android) +- Access to the `ECU` device +- `WiFi` connectivity +- Waveshare RS485 to ETH converter or equivalent RS-485 to TCP bridge +- RS-485 cable for connection between ECU and converter + +## Configuration Process + +### Initial Connection + +1. Press the `AP` button on the `ECU` +2. Connect to WiFi network: `ECU_R_216xxxx` +3. Use password: `88888888` + +### Modbus Configuration + +1. Launch `EMA Manager` +2. Navigate to: `Local Access` → `Workspace` → `Sunspec Configuration` +3. Enable `Modbus` toggle +4. Save changes and acknowledge any warnings + +### Bridge Setup + +1. Connect the RS-485 cable between your ECU's RS-485 port and the Waveshare converter +2. Configure the converter's network settings according to your local network requirements +3. Make note of the IP address assigned to the converter - you'll need this for testing and monitoring + +## Important Notes + +- `AP mode` remains active for 1 hour +- Press `AP` button again to extend configuration time +- Your specific inverter IDs will differ from documentation examples +- Ensure proper wiring between ECU and RS-485 converter +- Keep the converter in a dry, protected location + +## Testing Connectivity + +After configuring both the ECU and the RS-485 to TCP bridge, you should verify that the connection is working properly. You can follow our [testing guide](https://github.com/srcfl/egw-getting-started/blob/main/test_con.md) to confirm the connection. When testing APsystems ECU devices through the bridge, remember that the default Modbus port is 502, and the Unit ID is typically set to 1. You may need to wait a few minutes after configuration before the Modbus TCP connection becomes active. When testing, use the IP address of your RS-485 to TCP bridge, not the ECU's IP address. + +## Troubleshooting + +### Connection Issues + +If unable to connect to `ECU`: + +1. Verify `AP mode` is active +2. Maintain close proximity to `ECU` during setup +3. Check WiFi password (eight 8s) + +### Application Issues + +If experiencing problems with the app: + +1. Verify connection to `ECU` network +2. Restart `EMA Manager` +3. Update to latest version + +### Modbus Problems + +If Modbus is not functioning: + +1. Confirm `Modbus` toggle is enabled +2. Verify inverter IDs are visible +3. Check RS-485 cable connections +4. Verify bridge device network settings +5. Test connection with monitoring system + +### Bridge Communication Issues + +If the RS-485 to TCP bridge isn't working: + +1. Check power supply to the converter +2. Verify RS-485 cable connections and polarity +3. Confirm network settings on the converter +4. Test network connectivity to the converter's IP address + +## Source + +- Community +- [APsystems ECU Modbus Settings](https://global.apsystems.com/wp-content/uploads/2022/09/APsystems-Energy-Communication-Unit-ECU-R-User-Manual_Rev7.7_2022-08-30.pdf) diff --git a/docs/energy-gateway/compatible-devices/deye.md b/docs/energy-gateway/compatible-devices/deye.md new file mode 100644 index 00000000..dae58188 --- /dev/null +++ b/docs/energy-gateway/compatible-devices/deye.md @@ -0,0 +1,69 @@ +# Modbus TCP Configuration - Deye Inverter + +The following guide describes how to configure the `Modbus TCP` settings for Deye inverters and how to test the connection. + +## Prerequisites + +- Compatible with `SUN-G3-EU-230` Series (300W to 2000W models) +- Network scanning tool (e.g., `Advanced IP Scanner`) +- Web browser +- Network connectivity + +## Configuration Process + +### Locating Your Inverter + +1. Choose one of these methods: + - Use your router's interface + - Use `Advanced IP Scanner` to identify inverter `IP` + +### Accessing Settings + +1. Enter inverter `IP` in browser +2. Login with default credentials: + - Username: `admin` + - Password: `admin` +3. Modify URL to: `http:///config_hide.html` + +### Modbus Configuration + +Configure "Internal server parameters settings": + +1. Set Protocol to `TCP-Server` +2. Set Port to `8899` +3. Enter your server `IP` address +4. Set TCP timeout to `300` + +## Testing Connectivity + +After completing the configuration, you should verify that the Modbus TCP connection is working properly. Follow our [testing guide](https://github.com/srcfl/egw-getting-started/blob/main/test_con.md) to confirm the connection. For Deye inverters, remember to use port 8899 when testing the connection. The Unit ID is typically set to 1, but you may need to try 0 if that doesn't work. + +## Troubleshooting + +### Inverter Discovery Issues + +If you cannot find your inverter: + +1. Verify inverter power status +2. Check network connectivity +3. Try alternative network scanning tools + +### Settings Problems + +If settings are not saving: + +1. Confirm you're using the `config_hide.html` URL +2. Clear browser cache and retry +3. Verify `admin` access rights + +### Modbus Connection Issues + +If Modbus is not working: + +1. Verify port `8899` is accessible +2. Check server address accuracy +3. Test using `Modbus` diagnostic tool + +## Source + +- Community diff --git a/docs/energy-gateway/compatible-devices/fronius.md b/docs/energy-gateway/compatible-devices/fronius.md index f6d5a380..4f011b50 100644 --- a/docs/energy-gateway/compatible-devices/fronius.md +++ b/docs/energy-gateway/compatible-devices/fronius.md @@ -1 +1,94 @@ -# Fronius +# Modbus TCP Configuration - Fronius Inverters + +Fronius inverters can be configured for `Modbus TCP` in two different ways, depending on your model. This guide covers both standard Fronius inverters with `Datalogger` and `GEN24` models. + +## Prerequisites + +Access level requirements vary by model: + +- Standard Fronius with `Datalogger`: `Admin` credentials +- `GEN24`: `Technician` account or `Customer` account with support assistance +- Network connectivity +- Web browser + +## Configuration for Standard Fronius with Datalogger + +### Initial Connection + +1. Connect to inverter's WiFi access point: + - Locate network name containing `Datalogger ID` (240.xxxxx or 239) + - Use default WiFi password: `12345678` + - Access web interface at `192.168.250.181` (or assigned IP) + +### Modbus Configuration + +1. Log in with `Admin` credentials +2. Navigate to `Modbus` settings +3. Configure the following: + - Set "Data export via Modbus" to `tcp` + - Change "Sunspec Model type" to `float` +4. Save configuration + +### Control Priority Setup + +1. Access `DNO Editor` +2. Set "Controlling via Modbus" to priority 1 +3. Adjust priority order if needed +4. Save changes + +## Configuration for GEN24 Series + +### Initial Access Setup + +1. Connect to inverter WiFi (password: `12345678`) +2. Navigate to `192.168.250.181` +3. Access `System` → `Support` +4. Enable both: + - `Remote Access` + - `Support User` + +### Modbus Configuration (Technician Access) + +1. Navigate to `Communication` → `Modbus` +2. Enable "Control via Modbus TCP" +3. Set "SunSpec Model Type" to `float` +4. Enable "Allow Control" + +### Control Priority Setup + +1. Access `Safety and Grid Regulations` +2. Set `Modbus Control` to highest priority +3. Save all changes + +## Important Notes + +- Password management varies by model type +- Multiple inverters require individual configuration +- Document settings for each unit + +## Testing Connectivity + +After configuring Modbus TCP on your Fronius inverter, it's important to verify that the connection is working properly. You can follow our [testing guide](https://github.com/srcfl/egw-getting-started/blob/main/test_con.md) to confirm the connection. For Fronius inverters, use the default Modbus port 502. The Unit ID is typically set to 1, but you might need to check your specific configuration if this doesn't work. Remember that both standard and GEN24 models use the same Modbus TCP port and Unit ID conventions. + +## Troubleshooting + +### Access Issues + +For login problems: + +1. Contact support with model and serial numbers for password resets +2. Verify network settings +3. Double-check IP addresses + +### Configuration Problems + +If experiencing issues: + +1. For `GEN24` models, consult installer or Fronius support +2. Verify all settings are saved properly +3. Check network connectivity + +## Source + +- Community +- [Fronius Inverter Modbus TCP Configuration Guide](https://villageenergy.zohodesk.com/portal/en/kb/articles/enable-modbus-tcp-on-your-fronius-inverter#1_Connect_to_your_Inverters_interface) diff --git a/docs/energy-gateway/compatible-devices/huawei.md b/docs/energy-gateway/compatible-devices/huawei.md index 444d8714..3a69745a 100644 --- a/docs/energy-gateway/compatible-devices/huawei.md +++ b/docs/energy-gateway/compatible-devices/huawei.md @@ -1 +1,84 @@ -# Huawei +# Modbus TCP Configuration - Huawei Inverter + +The following guide describes how to configure the `Modbus TCP` settings for Huawei inverters and how to test the connection. + +## Prerequisites + +### Hardware Requirements + +- Mobile device with `Android 4.0` or later +- Huawei `SDongle` +- Internet connectivity +- `WiFi` capability + +### Software Requirements + +- `SUN2000` App (version `3.2.00.015` or later) +- Available from `Huawei AppGallery` + +## Configuration Process + +### Initial Setup + +1. Install `SUN2000` App from `Huawei AppGallery` +2. Ensure `SDongle` remains powered throughout configuration + +### Connection Setup + +1. Open `SUN2000` App +2. Select `Connect` → `WLAN` +3. Choose inverter's WiFi network +4. Enter password: + - First login: `Changeme` + - Change password after initial login + +### Modbus Configuration + +1. Login as installer (default password: `00000a`) +2. Navigate to: `Settings` → `Communication Configuration` → `Dongle Parameter Settings` → `Modbus-TCP` +3. Select appropriate access mode: + - `Unrestricted`: Allows all LAN devices (one at a time) + - `Restricted`: Requires setting trusted IP address + - `Disabled`: No Modbus access + +## Important Notes + +- Configuration settings persist through power cycles +- New inverters require fresh configuration +- `SDongle` replacement doesn't require reconfiguration +- Keep `SDongle` powered during configuration process + +## Testing Connectivity + +Once you've configured Modbus TCP on your Huawei inverter, it's essential to verify that the connection is working correctly. You can follow our [testing guide](https://github.com/srcfl/egw-getting-started/blob/main/test_con.md) to confirm the connection. For Huawei inverters, note that the default Modbus port is 6607, which differs from the standard Modbus port. The Unit ID is typically set to 1. If you've enabled the restricted access mode, make sure you're testing from an allowed IP address. + +## Troubleshooting + +### Missing Modbus Options + +If Modbus settings are not visible: + +1. Check firmware versions +2. Update app if necessary +3. Verify `SDongle` compatibility + +### Connection Problems + +If unable to connect: + +1. Ensure `SDongle` is powered +2. Stay within WiFi range +3. Verify correct password + +### Access Issues + +If experiencing access problems: + +1. Check IP restrictions if enabled +2. Verify only one client is connecting +3. Confirm network settings are correct + +## Source + +- Community +- [Huawei Inverter Modbus TCP Configuration Guide](https://forum.huawei.com/enterprise/intl/en/thread/modbus-tcp-guide/667250677153415168?blogId=667250677153415168) diff --git a/docs/energy-gateway/compatible-devices/overview.md b/docs/energy-gateway/compatible-devices/overview.md index 867743e1..09a67ae7 100644 --- a/docs/energy-gateway/compatible-devices/overview.md +++ b/docs/energy-gateway/compatible-devices/overview.md @@ -10,18 +10,19 @@ Even if you don't see your specific Inverter model in our compatibility list bel ::: ## List of explicitly supported Energy Meters -_(Last updated 2024-12-19)_ + +_(Last updated 2024-12-27)_ Currenty we only support smart meters via the P1 protocol, e.g. connected to your smart utility meter via the HAN port. Please refer to your utility company for details regarding your specific meter. Any P1 meter that supports telnet shoud be compatible. Please let us know if you have tried one out. -| Meter Make | Status | Protocol | -| ------------------------------------------------------------------------------------------- | ------------- | ----------------------- | -| [Currently One](https://currently.one/) | ✅ Ready | Telnet | -| Jemac P1 | ✅ Ready | REST | -| [Smart Meter WiFi Gateway](https://smartgateways.nl/en/product/smart-meter-wifi-gateway/) | ✅ Ready | Telnet | -| [Home Wizard P1 Meter](https://www.homewizard.com/p1-meter/) | 🔄 Planned | REST | +| Meter Make | Status | Protocol | +| ----------------------------------------------------------------------------------------- | ---------- | -------- | +| [Currently One](https://currently.one/) | ✅ Ready | Telnet | +| Jemac P1 | ✅ Ready | REST | +| [Smart Meter WiFi Gateway](https://smartgateways.nl/en/product/smart-meter-wifi-gateway/) | ✅ Ready | Telnet | +| [Home Wizard P1 Meter](https://www.homewizard.com/p1-meter/) | 🔄 Planned | REST | The compatibility may also depend on the actual utility meter and what version of the P1 protocol it uses. If you have tried something that does not seem to work please let us know and we will add it if possible. @@ -33,32 +34,32 @@ You will need a compatible Inverter to connect your Energy Gateway. We continuously add Inverters and update the table below. -| Inverter Make | Read Status | Control Status | Protocol | Communication Interface | Getting Started | -| ------------- | ------------- | -------------- | ----------------------- | ----------------------- | ------------------- | -| Sungrow | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet/Wi-Fi | Coming soon.. | -| Solaredge | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet/Wi-Fi | [Guide](solaredge.md) | -| Huawei | ✅ Ready | 🔄 Planned | Modbus TCP | Ethernet/Wi-Fi | Coming soon.. | -| Deye | ✅ Ready | 🔄 Planned | Modbus TCP (SolarmanV5) | Wi-Fi | Coming soon.. | -| Fronius | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet/Wi-Fi | Coming soon.. | -| SMA | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet/Wi-Fi | Coming soon.. | -| ferroamp | ✅ Ready | 🔄 Planned | Modbus TCP | Ethernet/Wi-Fi | Coming soon.. | -| APsystems | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | RS-485 | Coming soon.. | -| Enphase | ✅ Ready | 🔄 Planned | Local API | Ethernet/Wi-Fi | [Guide](enphase.md) | -| Sofar-solar | ✅ Evaluating | 🔄 Planned | Modbus TCP | RS-485 | Coming soon.. | -| Growatt | ✅ Evaluating | 🔄 Planned | Modbus TCP | Ethernet/Wi-Fi | Coming soon.. | -| Solplanet | 🔍 Untested | 🔄 Planned | Modbus TCP (SunSpec) | RS-485 | - | -| Kostal | 🔍 Untested | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet | - | -| ABB | 🔍 Untested | 🔄 Planned | Modbus TCP (SunSpec) | RS-485/Ethernet | - | -| Schneider | 🔍 Untested | 🔄 Planned | Modbus TCP (SunSpec) | RS-485 | - | -| Solis | 🔍 Untested | 🔄 Planned | TBD | TBD | - | -| Sol-ark | 🔍 Untested | 🔄 Planned | TBD | TBD | - | -| GoodWe | 🔄 Planned | 🔄 Planned | TBD | TBD | - | -| Fox-Ess | 🔄 Planned | 🔄 Planned | TBD | TBD | - | -| Eg4 | 🔄 Planned | 🔄 Planned | TBD | TBD | - | -| Livoltek | 🔄 Planned | 🔄 Planned | TBD | TBD | - | -| Lenercom | 🔄 Planned | 🔄 Planned | TBD | TBD | - | -| Delta | 🔄 Planned | 🔄 Planned | TBD | TBD | - | -| SAJ | 🔄 Planned | 🔄 Planned | TBD | TBD | - | +| Inverter Make | Read Status | Control Status | Protocol | Communication Interface | Getting Started | +| ------------- | ------------- | -------------- | ----------------------- | ----------------------- | --------------------- | +| Sungrow | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet/Wi-Fi | [Guide](sungrow.md) | +| Solaredge | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet/Wi-Fi | [Guide](solaredge.md) | +| Huawei | ✅ Ready | 🔄 Planned | Modbus TCP | Ethernet/Wi-Fi | [Guide](huawei.md) | +| Deye | ✅ Ready | 🔄 Planned | Modbus TCP (SolarmanV5) | Wi-Fi | [Guide](deye.md) | +| Fronius | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet/Wi-Fi | [Guide](fronius.md) | +| SMA | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet/Wi-Fi | [Guide](sma.md) | +| ferroamp | ✅ Ready | 🔄 Planned | Modbus TCP | Ethernet/Wi-Fi | Coming soon.. | +| APsystems | ✅ Ready | 🔄 Planned | Modbus TCP (SunSpec) | RS-485 | [Guide](apsystems.md) | +| Enphase | ✅ Ready | 🔄 Planned | Local API | Ethernet/Wi-Fi | [Guide](enphase.md) | +| Sofar-solar | ✅ Evaluating | 🔄 Planned | Modbus TCP | RS-485 | Coming soon.. | +| Growatt | ✅ Evaluating | 🔄 Planned | Modbus TCP | Ethernet/Wi-Fi | Coming soon.. | +| Solplanet | 🔍 Untested | 🔄 Planned | Modbus TCP (SunSpec) | RS-485 | - | +| Kostal | 🔍 Untested | 🔄 Planned | Modbus TCP (SunSpec) | Ethernet | - | +| ABB | 🔍 Untested | 🔄 Planned | Modbus TCP (SunSpec) | RS-485/Ethernet | - | +| Schneider | 🔍 Untested | 🔄 Planned | Modbus TCP (SunSpec) | RS-485 | - | +| Solis | 🔍 Untested | 🔄 Planned | TBD | TBD | - | +| Sol-ark | 🔍 Untested | 🔄 Planned | TBD | TBD | - | +| GoodWe | 🔄 Planned | 🔄 Planned | TBD | TBD | - | +| Fox-Ess | 🔄 Planned | 🔄 Planned | TBD | TBD | - | +| Eg4 | 🔄 Planned | 🔄 Planned | TBD | TBD | - | +| Livoltek | 🔄 Planned | 🔄 Planned | TBD | TBD | - | +| Lenercom | 🔄 Planned | 🔄 Planned | TBD | TBD | - | +| Delta | 🔄 Planned | 🔄 Planned | TBD | TBD | - | +| SAJ | 🔄 Planned | 🔄 Planned | TBD | TBD | - | ### Status Legend diff --git a/docs/energy-gateway/compatible-devices/sma.md b/docs/energy-gateway/compatible-devices/sma.md index 6df6fa36..364b17d5 100644 --- a/docs/energy-gateway/compatible-devices/sma.md +++ b/docs/energy-gateway/compatible-devices/sma.md @@ -1 +1,93 @@ -# SMA \ No newline at end of file +# Modbus TCP Configuration - SMA Inverter + +The following guide describes how to configure the `Modbus TCP` settings for SMA inverters and how to test the connection. + +## Prerequisites + +### Required Items + +- WiFi-capable device (smartphone, tablet, or laptop) +- Inverter `serial number` +- `WPA2-PSK` password (located on inverter label) +- `Installer` rights for certain settings + +## Configuration Process + +### Initial Connection + +Choose one of these connection methods: + +#### WiFi Connection + +1. Find network named `SMA19xxxxxxx` +2. Use IP address: `192.168.12.3` + +#### Ethernet Connection + +1. Connect via ethernet cable +2. Use IP address: `169.254.12.3` + +### Settings Configuration + +1. Open web browser +2. Enter appropriate `IP` address based on connection method +3. Log in as `Installer` +4. Select `Edit Parameters` + +### Modbus Setup + +1. Navigate to `Modbus` settings +2. Enable the Modbus feature + +### Grid Connection Configuration + +For standard models: + +1. Go to `System and device control` +2. Find `Grid connection point` +3. Change `Operating mode of active power limitation` to `External` + +For `SBx.x-1AV40/41` models: + +1. Locate `Operating mode active power setting` +2. Set to `External active power setpoint` + +### Finalizing Changes + +1. Always click `Save All` after making modifications +2. Wait for changes to be applied + +## Testing Connectivity + +After enabling Modbus TCP on your SMA inverter, you should verify that the connection is functioning correctly. You can follow our [testing guide](https://github.com/srcfl/egw-getting-started/blob/main/test_con.md) to confirm the connection. For SMA inverters, use the default Modbus port 502. The Unit ID is typically set to 3, which differs from many other manufacturers. Make sure you've completed all the grid connection configuration steps before testing, as these settings can affect Modbus communication. + +## Troubleshooting + +### Modbus Setting Issues + +If unable to change Modbus settings: + +1. Contact your installer +2. Check if settings are locked by `SMA Grid Guard` +3. Verify `installer` access rights + +### Connection Problems + +If experiencing connection issues: + +1. Verify correct WiFi network selection +2. Double-check `IP` address +3. Ensure you're within range of the inverter + +### Missing Settings + +If settings are not visible: + +1. Verify your model number +2. Check for alternative setting names +3. Confirm `installer` access level + +## Source + +- Community +- [SMA Inverter Modbus TCP Configuration Guide](https://villageenergy.zohodesk.com/portal/en/kb/articles/instructions-for-enabling-modbus-tcp-on-sma-inverter-15-11-2023#Preparation_Checklist) diff --git a/docs/energy-gateway/compatible-devices/solaredge.md b/docs/energy-gateway/compatible-devices/solaredge.md index 1fdb0322..d0ecc5d6 100644 --- a/docs/energy-gateway/compatible-devices/solaredge.md +++ b/docs/energy-gateway/compatible-devices/solaredge.md @@ -1,11 +1,71 @@ -# SolarEdge +# Modbus TCP Configuration - SolarEdge Inverter -### Enabling Modbus TCP +The following guide describes how to configure the `Modbus TCP` settings for SolarEdge inverters and how to test the connection. -1. Ensure the inverter is connected to your network either via Ethernet or Wifi -1. Locate the on/off switch on the inverter (usually has a red cap, near the bottom left of the inverter) -1. Push the switch to the left (P) for 1 second, then release -1. Scan the QR code on the right side of the inverter with your phone camera and connect to the WiFi network indicated by the code - - **Note**: You may get a notification that the network not having internet access. If this happens, select "Use network anyways" -1. Open a web browser and navigate to http://172.16.0.1/ -1. Under "Communication Settings" enable the Modbus TCP option and make note of the port shown (usually 502 or 1502) +## Prerequisites + +- Network connectivity (Ethernet or WiFi) +- Physical access to inverter +- Web browser +- Mobile device with camera + +## Configuration Process + +### Physical Access Setup + +1. Locate the `on/off` switch on the inverter + - Usually has a red cap + - Typically found near the bottom left of the inverter +2. Push the switch to the left (`P`) for 1 second +3. Release the switch + +### Network Connection + +1. Locate the `QR code` on the right side of the inverter +2. Scan the `QR code` using your phone's camera +3. Connect to the WiFi network indicated by the code + - Note: You may receive a notification about the network lacking internet access + - If this occurs, select "Use network anyways" + +### Modbus Configuration + +1. Open a web browser +2. Navigate to `http://172.16.0.1/` +3. Find the "Communication Settings" section +4. Enable the `Modbus TCP` option +5. Note the port number shown + - Usually `502` or `1502` + - You'll need this for future reference + +## Important Notes + +- Document the port number for future use +- Maintain network connectivity during configuration +- Ensure proper physical access to inverter switches + +## Testing Connectivity + +After enabling Modbus TCP on your SolarEdge inverter, it's important to verify that the connection is working properly. You can follow our [testing guide](https://github.com/srcfl/egw-getting-started/blob/main/test_con.md) to confirm the connection. For SolarEdge inverters, try both port 502 and 1502, as the port number can vary between models and firmware versions. The Unit ID is typically set to 1. Make sure to document both the working port number and Unit ID for future reference, as you'll need these for any monitoring setup. + +## Troubleshooting + +### Connection Issues + +If unable to connect: + +1. Verify `QR code` scan was successful +2. Check WiFi connection status +3. Confirm correct `IP` address entry + +### Configuration Problems + +If settings don't apply: + +1. Refresh browser page +2. Verify network connection +3. Try alternative browser + +## Source + +- Community +- [SolarEdge Modbus TCP Configuration Guide](https://github.com/binsentsu/home-assistant-solaredge-modbus?tab=readme-ov-file#enabling-modbus-tcp-on-solaredge-inverter) diff --git a/docs/energy-gateway/compatible-devices/sungrow.md b/docs/energy-gateway/compatible-devices/sungrow.md index e38a3a50..c3fd8d86 100644 --- a/docs/energy-gateway/compatible-devices/sungrow.md +++ b/docs/energy-gateway/compatible-devices/sungrow.md @@ -1 +1,27 @@ -# Sungrow +# Modbus TCP Configuration - Sungrow Inverter + +The following guide describes how to configure the `Modbus TCP` settings for Sungrow inverters and how to test the connection. + +## Configuration Note + +Sungrow inverters come with `Modbus TCP` enabled by default. No additional configuration is required to use this feature. + +## Verification + +If you need to verify functionality: + +1. Ensure inverter is properly connected to your network +2. Confirm network connectivity +3. Follow the testing procedure in the Testing Connectivity section below + +## Testing Connectivity + +Even though Modbus TCP comes enabled by default on Sungrow inverters, it's still important to verify that the connection is working properly. You can follow our [testing guide](https://github.com/srcfl/egw-getting-started/blob/main/test_con.md) to confirm the connection. For Sungrow inverters, use the default Modbus port 502. The Unit ID is typically set to 1. Testing the connection can help ensure that your network configuration is correct and that the inverter is properly accessible. + +## Support + +If you experience any issues with `Modbus TCP` communication, contact Sungrow support or your installer for assistance. + +## Source + +- Community