![]() ![]() After enabling power sharing the response contains a lot of “participant_dins” in a a new entry called “load_sharing_config”, see the following two outputs (click on “Before …” and “After …”):īefore enabling power sharing $.The master can display some fundamental data of the slave, but I am not sure if all data, that are normally available via the “main” API, are visible or not:.It is not possible to add a not existing second TWC with some “fantasy” credentials (this process terminates with an error message… so you really need a second device for the configuration):.After around 30 minutes the connection to the installation/service AP of the master is still alive, but changing the current setting results in an error (a normal “ping” is working).After around 10 minutes the installation/service AP of the master is not visible, but an existing connection is still alive and it is possible to change the current setting with the protocol buffer.After around 5 minutes the installation/service AP of the slave is not visible/accessible.For some minutes the installation/service AP is available for both TWCs. ![]() The same API is not available anymore for the slave TWC.The normal API fo the master TWC is (after a short timeout) permanently available (…/api/1/vitals|wifi_status|version|lifetime).Observed behavior after activating power sharing: Enter the maximum current for both TWCs (minimum is 2x 6 A → 12 A).Login to the master and enter the SSID and password of the second one (which will be the slave).Activate the installation/service wireless access point on both TWCs.However, due to the additional weight compared to the 3, it cannot go as far as a 3 can on the same charge.When load sharing is enabled, I’m interested to know whether the internal AP stays active all the time, or whether it times out like before, which might add further information on keeping the AP alive for other reasons.Īs stated above, I have two TWC Gen3 which were until now not configured for power sharing and both are running on firmware v22.33.1įor the case that the master/slave configuration procedure is not known, here in short: Since the Model Y shares the vast majority of its components with the 3, it’s apparent that its charging times will be similar. Tesla Model Y Long Range, 326 mile range: Destination / Wall Connector: 44 miles added per hour up to 8 hours.NEMA 14-50 Home: 30 miles added per hour up to 12 hours.Home 120V: 3 miles added per hour up to 118 hours.Interestingly, the Model 3 in Long Range form can charge to 353 miles one hour faster than a Standard Range Plus can to 263 on a Wall Connector. This yields much quicker charging times if you use a Destination Charger or Wall Connector. If you purchase a Model 3 equipped with the Long Range battery option, it comes with an 11.5kW onboard charger. Tesla Model 3 Long Range, 353 mile range: Destination / Wall Connector: 30 miles added per hour up to 9 hours.NEMA 14-50 Home: 30 miles added per hour up to 9 hours.Home 120V: 3 miles added per hour up to 87 hours.The less powerful onboard charger leads to slightly longer charging times, but it’s still ample for most drivers. Unlike every other modern Tesla equipped with an 11.5kW onboard charger, the Model 3 Standard Plus comes with a 7.7kW onboard charger. Tesla Model 3 Standard Range Plus, 262 mile range:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |