diff --git a/0_D0002_18/MW3_15U_5406_1.47.bin b/0_D0002_18/MW3_15U_5406_1.47.bin
new file mode 100644
index 0000000..5c97d83
Binary files /dev/null and b/0_D0002_18/MW3_15U_5406_1.47.bin differ
diff --git a/0_D0002_18/MW3_15U_5406_1.47.bin.DIGEST b/0_D0002_18/MW3_15U_5406_1.47.bin.DIGEST
new file mode 100644
index 0000000..c195d20
--- /dev/null
+++ b/0_D0002_18/MW3_15U_5406_1.47.bin.DIGEST
@@ -0,0 +1 @@
+102c8a22c5d5348d2c336486ae81ead386b307e51ae8369e45c15c153eece3bb  MW3_15U_5406_1.47.bin
diff --git a/0_D0002_18/MW3_15U_5406_1.49R.bin b/0_D0002_18/MW3_15U_5406_1.49R.bin
new file mode 100644
index 0000000..5ce4ecd
Binary files /dev/null and b/0_D0002_18/MW3_15U_5406_1.49R.bin differ
diff --git a/0_D0002_18/MW3_15U_5406_1.49R.bin.DIGEST b/0_D0002_18/MW3_15U_5406_1.49R.bin.DIGEST
new file mode 100644
index 0000000..b5ffe6f
--- /dev/null
+++ b/0_D0002_18/MW3_15U_5406_1.49R.bin.DIGEST
@@ -0,0 +1 @@
+46f0c17a9e75ee98ae1941b8f7a9b9f264915f87d71e119ce50a5792ab3c6c7f  MW3_15U_5406_1.49R.bin
diff --git a/0_D0002_18/MW3_15_0501_1.21.bin.DIGEST b/0_D0002_18/MW3_15_0501_1.21.bin.DIGEST
new file mode 100644
index 0000000..ec5007a
--- /dev/null
+++ b/0_D0002_18/MW3_15_0501_1.21.bin.DIGEST
@@ -0,0 +1 @@
+c43a676513cd40874709ea8f3fc02905148a889247fd228a1cee7bd37930db68  MW3_15_0501_1.21.bin
diff --git a/0_D0002_18/MW3_15_0501_1.23.bin.DIGEST b/0_D0002_18/MW3_15_0501_1.23.bin.DIGEST
new file mode 100644
index 0000000..d5cfd3a
--- /dev/null
+++ b/0_D0002_18/MW3_15_0501_1.23.bin.DIGEST
@@ -0,0 +1 @@
+aba5ff99c67d47a9b230c3662405204d1c03ee6dbdb926147fe6389e3c6be5e7  MW3_15_0501_1.23.bin
diff --git a/README.md b/README.md
index 29404a4..131f77d 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@
 
 If you brick your device that's your problem. ;)
 
-Installed on a Deye SUN600G3-EU-230 and it worked fine.
+Installed on a Deye SUN600G3-EU-230 and it worked fine (5406 in the filename).
 
 My feeling is that the firmware files and IP info can be released out into the wild as it's not hidden and the fact
 that there is specifically no HTTPS connection used would suggest that the manufacturer does not care about securing those files.
@@ -20,11 +20,21 @@ It looks like behind this IP is the firmware update Server of Deye. At least I g
 Based on a few forum entries and the answer from Deyes support the Inverters should auto-update to the latest version
 when being up and running for 30 minutes.
 
+## Filenames
+
+| Filename | Brand          |
+|----------|----------------|
+| 0501     | Solis Ginglong |
+| 5406     | Deye           |
+
 ## URL Structure
 
 ```bash
 http://47.254.36.66/0_D0002_18/MW3_15U_5406_1.471.bin
+http://47.254.36.66/0_D0002_18/MW3_15U_5406_1.49R.bin
 http://47.254.36.66/0_D0002_18/MW3_16U_5406_1.53.bin
+http://47.254.36.66/0_D0002_18/MW3_15_0501_1.21.bin
+http://47.254.36.66/0_D0002_18/MW3_15_0501_1.23.bin
 ```
 
 You can use the DIGEST files to verify that those files here are the same as the ones on the server.
@@ -34,6 +44,24 @@ shasum -c MW3_15U_5406_1.471.bin.DIGEST
 shasum -c MW3_16U_5406_1.53.bin.DIGEST
 ```
 
+or verify all DIGEST files
+
+```bash
+for filename in *.bin.DIGEST; do
+    shasum -a 256 -c $filename
+done
+```
+
+Create your own DIGEST files
+
+```bash
+for filename in *.bin; do
+    # create a file called $filename.DIGEST
+    shasum -a 256 $filename > $filename.DIGEST
+done
+```
+
+
 ## Call for help
 
 If you have more information or insights into the firmware update process, alternative URLs or other information let me know.