A software update won’t be possible because the parameters are hardware-dependent. The device’s components can’t handle this.
@Ake1 could you be more specific on the hardware limitations? The specs for the SolarX are 58v and 80A maximum. Since it uses the same output connector for either the parallel cable or P090D cable, I don’t understand how it could be hardware-limited for one but not the other. Thanks!
Yes I don’t understand either why it couldn’t be fixed with even a dummy signal to the CAN port. I expect it’s the default voltage ratio when no setting is applied rather than any hardware limitation.
I would expect that if you output from the SolarX 4k to a bus bar and then ran the P090D cable connected to the CAN port with a voltage set at 58V and the triple XT60 cable was also connected to the Bus Bar then it would also be 58V because what else is it going to be.
Observing charging of the Apex 300’s i have in my array… they do charge at different rates and they rotated higher to lower charging. So strange.
three is strong textNO CAN (Ethernet ) connection on 3 way XT60 cable. At least on my cable. But on single unit cable there is one (I have both types of cables).
Yep. So if you’re apparently gonna hook the Solar X up to a large panel array, do your homework and check the panels specs carefully so you don’t exceed the amperage. They’ll obviously need to be wired in series so the rated amperage stays the same.
Hello
I have connected the SolarX to my two apex300 with an xt60-f cable, I have checked the connections and it seems that they are fine and when I turn on the SolarX it gives me the application error S013 charging mode error
That S013 error does not appear in the instruction book, how can I fix it? Thank you
How about if you purchased another Solar X and had an array of 3 - Apex 300’s- could you use one Solar X to power Port One and the second Solar X providing power to Port Two of each of the Apex units? (Using the parallel cable coming out of Both Solar X units).
Thanks!
Thank you for your inquiry regarding the charging options for your system. While the theoretical feasibility of using the XT60 charging method exists, we do not recommend it. Instead, we suggest using the P090D cable for the following reasons:
-
Power Limitations: The maximum power that a single Apex300 can receive via the XT60 charging method is 1200W. To achieve this, the input voltage must exceed 453V. However, under normal circumstances, the optimal input voltage you can provide is around 400V, making it challenging to reach the 1.2KW output effectively.
-
Cable Configuration: Our cable is a one-to-three configuration, which means that even if you connect the required number of solar panels under optimal sunlight with an input of 400V, the ideal output power in one-to-three charging mode would be 1KW * 3 = 3KW. The battery mode can output 4KW, resulting in a solar energy loss of 1KW. If fewer than three Apex300 units are connected, this loss could increase, making it less cost-effective for you.
-
P090D Charging Efficiency: When using the P090D cable in battery charging mode, with an input of 320V, the SolarX 4K can achieve an output power of 4KW. In comparison, the XT60 port output power under similar conditions would only be approximately 804.48W. Thus, the efficiency of the P090D charging method is five times greater than that of the XT60 port, which greatly enhances your overall experience.
-
Smart Communication: The P090D charging method allows for communication between the SolarX 4K and the device being charged. This interaction effectively controls the current, provides unilateral or bilateral upgrades, and offers bidirectional power supply and protection. In contrast, the XT60 method lacks this communication, making it less intelligent and less reliable.
-
MPPT Tracking Conflicts: Both the SolarX 4K and Apex300 have MPPT tracking. When both MPPTs operate simultaneously, conflicts can arise. The current solution is to pause the MPPT tracking function of SolarX 4K, which acts as a transformer to ensure that Apex300 can track independently. While this resolves the MPPT conflict, it may not provide an ideal charging effect. Therefore, we recommend using either the P090D or PD150D cables for charging in battery mode to enhance your user experience.
If you have any further questions or need more assistance, please don’t hesitate to reach out!
Thank you for replying. I appreciate all the good information.
So what do you suggest is the best way to get maximum power three Apex 300 units that are set up in parallel to the Bluetti H1 hub?
(3 SolarX using P090A cable to each unit?)
Thanks for your help!
Steve
Hello, all charging ports on the P090D are occupied, so it’s indeed impossible to use 4K and HUBD1 simultaneously when connected to the P090D.
Yes a problem I have seen.
So adding another Solar X into parallel ports the solution? (XT60)
Thanks!
S
Yes, adding another Solar X in parallel to the XT60 ports is a viable solution.
If you have any further questions or need assistance, feel free to ask!
Will each cable out of the Solar X provide up to 1200 watts each in parallel mode? No limit on the Apex 300 up to 1200 watts each port (1,2 solar input).
Thanks,
Hello,
Are you referring to the parallel mode in the advanced settings? Please note that this mode is specifically developed for the B4810 and is not suitable for use with the AP300. Since you are using the HubD1, the 4K can only connect the output to the XT0 port.
If you have any other questions, please feel free to reach out!
Thanks for replying. Not sure what some of what you mentioned means…
But I just want to connect two Solar X to my three apex 300 units running in parallel. See image. One Solar X parallel cable into port one of the apex 300 and another Solar X cable (xt60) into the second port.
The goal to get more solar charging. Shooting for perhaps 7000 watts of input or close.
Thanks -
These ports and get 1200 watts into each port.
Hello,
Please note that the SolarX 4K does not support parallel connections with the Apex 300. Only the newly released B4810 battery pack is compatible for this feature.
