-
Hi, This is my first post here. A while ago I requested AmberElectric to assess the viability of installing Tesla using my actual data and received a well-formatted document. My question is if AmberElectric can open-source this project so we can change contribute and use AmberElectric API to allow anyone to plug their own data at any time and most importantly learn how that modelling works. I personally want to model my data myself but I am completely newbie and have lots of most-likely dumb questions like: Do you use SmartShift smarts while modelling or do you simply add exported electricity to the battery until fully charged and then apply discharge when my data shows grid import? If I will try to model myself so I understand how it works precisely: Should I take into account the price quoted for installation and calculate the price of each full cycle by dividing battery cost by the amount of how many cycles Tesla supports over a lifetime? What is the minimum battery must hold and what is max in percentage? I assume the battery can not be discharged to 0% or charged to 100% How much should I take out when charging and discharging - is it a 10% loss each way? How to calculate a full cycle - if the battery is 50% charged, we add 50% to it and discharge 50% - should it be counted as 1/2 of a full cycle? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
Hey Igor,
Yep, we run Smartshift for each an every 5 minute interval to generate the report. It takes around 24 hours to crunch the numbers for a 12-month period per customer on a fairly beefy machine. So at this stage, we're unlikely to put it behind an API (DOS risk) or open source it at this point. Just from a maintenance and documentation POV, it would require more resources than we have. That said, if we can make it a couple of orders of magnitude faster and less resource hungry, we might change our mind.
I didn't write the tool that generates these reports, but as far as I know, we don't (mainly, because we don't know that data). Smartshift has internal constraints on charge and discharge cycles and tries to limit it to 1 full cycle per day.
Max is 100%. Minimum is 20% for a Powerwall (well, that's what the model uses—you can set your blackout limit to a lower number if you choose)
I don't think we model that. If you really wanted to, you can use https://sam.nrel.gov/software-development-kit-sdk/pysam.html - though not sure that they have a Powerwall model. We're using that package in an internal simulation tool at the moment—is it complete overkill for our needs? Probably, but it meant I didn't have to write the logic for charging a battery.
It's throughput, so yes, so that would be 1/2 a full cycle. Smartshift is a linear optimisation model, so you could use something like EMHASS to come up with your own version: https://emhass.readthedocs.io/en/latest/ A bunch of people have some success with using that instead of Smartshift here. |
Beta Was this translation helpful? Give feedback.
-
Yes - but there are other options with no battery, normal retailers offer a fixed (low) FIT and VPPs offer a more reasonable fixed FIT.I agree it really schedule when the FIT regime changed so significantly after we bought solar. So I've since bought batteries and likely to get sting yet again down the track. The big question is what happens to prices and FIT even the gig coal generator closes. Lots of projects on the go but they will take time to get working. In the mean time I'm punting prices will rise further - but as always there's no guarantees.Sent from my Galaxy
-------- Original message --------From: chiefcomm ***@***.***> Date: 19/9/23 11:59 am (GMT+10:00) To: amberelectric/public-api ***@***.***> Cc: iMortlake ***@***.***>, Comment ***@***.***> Subject: Re: [amberelectric/public-api] Battery assessment tool (Discussion
#155)
Oh yes "cheated" is a good word :-) The export market in NSW spends so much time negative that Solar panels are beneficial only if you have a battery or an EV to suck up the excess and/or shift as much electric use during daylight hours and move usage outside the peaks.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Hey Igor,
Yep, we run Smartshift for each an every 5 minute interval to generate the report. It takes around 24 hours to crunch the numbers for a 12-month period per customer on a fairly beefy machine. So at this stage, we're unlikely to put it behind an API (DOS risk) or open source it at this point. Just from a maintenance and documentation POV, it would require more resources than we have.
That said, if we can make it a couple of orders of magnitude faster and less resource hungry, we might change our mind.