Hello again everyone,
I hope you're all doing well.
I have a client for whom I've installed a Felicity IVEM5048 and coupled it with a Felicity 48V170Ah, LPBA48 8.7 KWH battery. Everything from configuration settings to priority, etc., are all good and I've personally tested them out. There is one problem, however, that is very peculiar and can't help but think that it is firmware related.
You see, when I plugged in the BMS, it showed me that everything is connected and is able to read the battery accordingly (I was seeing the percentage on the Inverter's screen, as well as that tiny "C" letter next to the battery indicating that the Inverter is successfully communicating with the battery in question). Note that due to some of the manuals that I've read, and to avoid all possible conflicts, I've set the address on the battery to "0100" (in reverse, so 0010, meaning "2" in binary). So far, so good. Then, I went about to configure the WiFi dongle to the client, and came across a very strange bug. The WiFi dongle just refused to communicate with the inverter. The application on which I was testing this out was SmartESS. I made sure that the configuration was correct, and noticed that the "Net" and "SRV" lights were lit, indicating communication with the server, and that internet connection was OK. The "COM" light, however, was acting crazy. In the first 5 minutes or so, it would act just fine, but then it would turn off. All communication between the dongle and inverter is cut off for some reason. After a couple of hours of trial and error, I decided that maybe the cable is faulty, and decided to try out a new dongle and cable (RJ45 to RS485). The WiFi dongle is a WiFi Plug Pro Rev 03. I got another one, but reacted the same way (and don't worry, I know better than to blindly link those things to accounts without making sure that they are working properly). I tried with a WiFi Plug Pro Rev 05 just in case, despite knowing that their pinouts are different, but the dongle wouldn't even turn on then. So, as I was about to give up, I decided to remove the BMS cable, and convert everything manually to user-defined, with proper Absorption and Floating voltages. Wouldn't you know, the WiFi Dongle suddenly started working! I tested it for a good 30 minutes to make sure, and it was reporting everything as it should at long last. When I connected the BMS cable back in, WiFi dongle became unresponsive again, as in the COM light turned off, and it was as if there was no longer communication between the inverter and dongle.
From what I've noticed, the pins connected on the RJ45 for the WiFi Dongle communication are: 1, 2, 4(or 5, can't remember exactly) and 8.
The RJ45 to RJ45 connector between the Inverter and the battery was your basic IEEE standard cable that followed the color code (on both sides): WO, O, WG, B, WB, G, WBr, Br.
What could the problem be exactly? Do I need to prepare my own cable with only pins 5 and 6 connected so that there are no other conflicts during the BMS communication? Because in another application, I noticed that pins 5 and 6 (and 7 or 3 for GND, again can't remember exactly) are enough for a BMS communication on the battery to any other inverter, so long as the pinouts on the latter are defined (and yes, I've successfully tested this on a Growatt Inverter with Felicity LiFePo4).
Please do let me know what course of action to take, and thank you again.
I hope you're all doing well.
I have a client for whom I've installed a Felicity IVEM5048 and coupled it with a Felicity 48V170Ah, LPBA48 8.7 KWH battery. Everything from configuration settings to priority, etc., are all good and I've personally tested them out. There is one problem, however, that is very peculiar and can't help but think that it is firmware related.
You see, when I plugged in the BMS, it showed me that everything is connected and is able to read the battery accordingly (I was seeing the percentage on the Inverter's screen, as well as that tiny "C" letter next to the battery indicating that the Inverter is successfully communicating with the battery in question). Note that due to some of the manuals that I've read, and to avoid all possible conflicts, I've set the address on the battery to "0100" (in reverse, so 0010, meaning "2" in binary). So far, so good. Then, I went about to configure the WiFi dongle to the client, and came across a very strange bug. The WiFi dongle just refused to communicate with the inverter. The application on which I was testing this out was SmartESS. I made sure that the configuration was correct, and noticed that the "Net" and "SRV" lights were lit, indicating communication with the server, and that internet connection was OK. The "COM" light, however, was acting crazy. In the first 5 minutes or so, it would act just fine, but then it would turn off. All communication between the dongle and inverter is cut off for some reason. After a couple of hours of trial and error, I decided that maybe the cable is faulty, and decided to try out a new dongle and cable (RJ45 to RS485). The WiFi dongle is a WiFi Plug Pro Rev 03. I got another one, but reacted the same way (and don't worry, I know better than to blindly link those things to accounts without making sure that they are working properly). I tried with a WiFi Plug Pro Rev 05 just in case, despite knowing that their pinouts are different, but the dongle wouldn't even turn on then. So, as I was about to give up, I decided to remove the BMS cable, and convert everything manually to user-defined, with proper Absorption and Floating voltages. Wouldn't you know, the WiFi Dongle suddenly started working! I tested it for a good 30 minutes to make sure, and it was reporting everything as it should at long last. When I connected the BMS cable back in, WiFi dongle became unresponsive again, as in the COM light turned off, and it was as if there was no longer communication between the inverter and dongle.
From what I've noticed, the pins connected on the RJ45 for the WiFi Dongle communication are: 1, 2, 4(or 5, can't remember exactly) and 8.
The RJ45 to RJ45 connector between the Inverter and the battery was your basic IEEE standard cable that followed the color code (on both sides): WO, O, WG, B, WB, G, WBr, Br.
What could the problem be exactly? Do I need to prepare my own cable with only pins 5 and 6 connected so that there are no other conflicts during the BMS communication? Because in another application, I noticed that pins 5 and 6 (and 7 or 3 for GND, again can't remember exactly) are enough for a BMS communication on the battery to any other inverter, so long as the pinouts on the latter are defined (and yes, I've successfully tested this on a Growatt Inverter with Felicity LiFePo4).
Please do let me know what course of action to take, and thank you again.