Emoncms, getting it to do what you want it to do

[Craig Kirkpatrick]

Alan was asking how to do basic math within Emoncms.  I decided to start a new thread to discuss tips and tricks with Emoncms.

First I'll say that there is still a lot for me to learn.  But certainly I can help with basics like how to do math, how to get 237 as a temperature to read as 23.7, and things like that.

I read thru Chris' guide, and it is quite good, maybe just needs adding this part about how to create the feeds and do the math you need in the process.  Find the link for the OpenEVSE WiFi Beta here:  http://openevse.dozuki.com/c/OpenEVSE_Communications  It is a great place to start.

The picture above is an example that is pretty useful and I think it is what Alan was missing.  I created this back in June and this data is logged to the Emoncms.org server and I need to move it to http://data.openevse.com/emoncms  soon.

First thing to note is the interval in the lower right that is 10s, that is really unnecessary and is better for the server filling up with data if it is 60s since things just don't happen too fast in an EVSE and storing data once per minute is fine and will keep Chris from needing new TB hard drives too soon.

You get to this screen by clicking the wrench icon on the input, and in this example it is the OpenEVSE_AMP input.  Here is where math can be done.  I added the five steps.  The first one is multiplying AMPS by 0.9342 so that the AMPS I log in Emoncms are calibrated to another meter I use.  Next is logging AMPS to something that will be stored over time in the server at suggested 60s intervals.  Next is multiplying by 0.24 and that may seem puzzling but since AMPS is really milliamps this is how to get Watts assuming 240V.  Next I want to keep Watts logged over time.  Finally there is a handy operation to take realtime Watts and integrate it over time to get kWh, choose "Power to kWh".

Then in dashboards I can show amperage graphs, I could show a graph of Watts over time, and I can display the accumulated kWh as a text readout.

Let me know what questions you may have.

Craig K.

[Alan Kirk]

Is the OpenEVSE Emoncms setup different from the Emoncms Energy setup?  My pea-size brain is struggling with what I see on your illustration and what I see when I open my OpenEVSE account.  Let me think on what you have provided and see what I am doing wrong. 

If I go to my Inputs I have four, Amps, Pilot, Temp and Volts. If I select the Wrench in the Amps line I get Node0: OpenEVSE_AMPS and I can play with Add Process but this feels like I am editing the Amps Input.  How do I create a Watts entry for my Node:0 ? 

Also, this is the only place I see the time increment setting, which is currently 10 sec.  When I select 60 and Add, I am told" Error already exist". 

Sounds so basic but I haven't found the right recipe for my pea-brain!

And if I wanted to talk to my EVSE via WiFi which is at address 192.168.1.2, using Putty, how do I set Putty up?  RAW Telnet Rlogin?  I tried them all and I don't have something configured correctly as they all come back with Communication Failure.

[Craig Kirkpatrick]

Alan you are in a good starting spot.  I don't know if someone already setup the feeds and dashboard or if you are just beginning with the inputs.

If I assume you are just beginning with the inputs then clicking on the wrench for the OpenEVSE_AMPS lets you setup what are called feeds.  Simply understand that inputs are realtime data off of your OpenEVSE and are not stored anywhere unless you create feeds that log the data.  And in the process of logging the data you can apply some multipliers like in my example.  You'll do no harm if you just delete any feeds you have and then try to mimic the five steps I showed that process the AMPS input.  Then you'll end up with Watts and accumulated kWh.  Then we can move onto creating a way to display it in the dashboard.

Don't worry about the 60s versus 10s right now.  It won't be a problem.  Or if you wanted to delete that feed step you could re-create it with 60s.

You cannot hurt the AMPS input.  It is there, it will stay there no matter what.  But you need to get FEEDS from that input to do anything at all with Emoncms.

Node numbers are for geeks like me who own eight Huzzah modules and want to have more than one of them uploading data at a time.  If you only have one then Node 0 is the default.

Making progress,

Craig K.

On Sunday, October 25, 2015 at 3:38:33 PM UTC-7, Alan Kirk wrote:

Is the OpenEVSE Emoncms setup different from the Emoncms Energy setup?  My pea-size brain is struggling with what I see on your illustration and what I see when I open my OpenEVSE account.  Let me think on what you have provided and see what I am doing wrong. 

If I go to my Inputs I have four, Amps, Pilot, Temp and Volts. If I select the Wrench in the Amps line I get Node0: OpenEVSE_AMPS and I can play with Add Process but this feels like I am editing the Amps Input.  How do I create a Watts entry for my Node:0 ? 

Also, this is the only place I see the time increment setting, which is currently 10 sec.  When I select 60 and Add, I am told" Error already exist". 

Sounds so basic but I haven't found the right recipe for my pea-brain!

On Sunday, October 25, 2015 at 2:48:00 PM UTC-7, Craig Kirkpatrick wrote:

[Alan Kirk]

OK,  I made some soup!  Using your example I have created the desired feeds.  Good progress!  Thanks

On Sunday, October 25, 2015 at 2:48:00 PM UTC-7, Craig Kirkpatrick wrote:

[Craig Kirkpatrick]

Alan, Super!  I think this was the missing piece in your puzzle.  The rest Chris did a great job showing all of the steps in his Dozuki guide I provided the link.

One thing to remember is you can create more than one dashboard to display the feeds.  So if you don't like what you create at first just begin another dashboard, eventually choosing what you like the most and delete the others or just don't publish them.  I keep two dashboards for an OpenEVSE, one that is a panel of energy and power and temperatures, the other plotting temperatures over time vs the Watts over time so I can see how power drives the creation of the heat observed both in infrared and the ambient air in the box.  Remember I am the temperature monitoring geek :-)   

-Craig K.

[Alan Kirk]

Is there a way to edit the Input entries or do I have to just redo the entries.  In my haste I think I forgot to change one of the Logging intervals to 60 sec.  I just redid that entry but thought there may have been an edit feature I missed.

On Sunday, October 25, 2015 at 2:48:00 PM UTC-7, Craig Kirkpatrick wrote:

[Craig Kirkpatrick]

I've usually just made a new feed from the input and then deleted the feed that I setup wrong. I can't remember an easier way to edit a feed.
When it comes to the inputs themselves, they get created by the node writing data to the server, so those would change in the Huzzah firmware. I don't think you meant actually changing the inputs.

[Alan Kirk]

Yep, You are right, just wanted to edit the items on the Input page.  Next problem, how does one change the scale values on the Dashboard graphs?  I did it once before but can't for the life of me reconstruct that part of my memory!

[Craig Kirkpatrick]

You edit the dashboard, then click the graph you want to edit, then you will see a button near the top with a wrench symbol and the word Configure.  In that menu you can change scale factors and choose colors and things.

.

[Alan Kirk]

That is what I remembered!  Now when I select the Configure button I get a requestor with a dropdown and can select from the 6 or so Feeds.  I don't get the page where scaling can be applied. 

Tried with Temp and that is configurable!.  It's the kWh that I wanted to change the scale on and it doesn't seem to work the same. 

More suggestions needed.

On Sunday, October 25, 2015 at 2:48:00 PM UTC-7, Craig Kirkpatrick wrote:

[Craig Kirkpatrick]

Alan, it makes sense to graph Watts or kW but it doesn't make sense to me to plot kWh.  To me what makes sense is just a readout of the accumulated kWh.  Am I missing something?  Maybe?

[Alan Kirk]

You missed nothing!  I picked the kWh from the pull-down when I was setting up the Feeds.  Apparently you can't scale that on the graphs as it is what it is, very very small.  kWh makes sense if one is trying to track the energy going into the EV but I was doing kWh based on the scaled data from Amps, which was in kW.  So my graph was showing MW, I think!  I need to get one of those Tesla's to get the graph showing something!  All is working well now. 

[Craig Kirkpatrick]

I could imagine a kWh per day bar-chart sort of display.  That would be lovely.  I'll try to create one in the next day or two.

Just plotting kWh vs time is what I was thinking would not make sense since it would just keep growing over time.

[chris1howell .]

I have kWh on a chart on my Home Dashboard...

http://data.openevse.com/emoncms/chris1howell/

--
You received this message because you are subscribed to the Google Groups "OpenEVSE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openevse+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Craig Kirkpatrick]

Sexy dashboard!

That is what I was thinking would be nice is a bar chart display of kWh per day or per week.

I really admire that you have the state-of-charge data from the EV and I guess next to that miles of driving range.  Very nicely done!

Something I set on the back burner is the open energy monitor device.  Was thinking this morning I need to give more attention to getting mine working so I can measure voltage at my breaker panel and pull that into my other dashboards.  At first mine would report data for about five minutes and then stall, so I sort of set it aside, but need to get it working.

[Alan Kirk]

Got to get my Emoncms post over here, away from the WiFi post where they may get lost! 

Chris pointed out that the Temp is reported in deci-degres C so using the multiply (x) operator from the Input wrench tool and inputting 0.18 (0.1x9/5), then the + operator inputting 32 and then the log input operator will get to degrees F.  I'm working on kWh reporting and it looks like the charting (bar graph) keeps the previous accumulation, which I would have thought would have been cleared at the end of a day.  My implementation shows the same value for two days but I only charged on the first of those two.  Again, what am I doing wrong?

e:  prt sc from my OpenEVSE Emoncms Input screen

On Sunday, October 25, 2015 at 2:48:00 PM UTC-7, Craig Kirkpatrick wrote:

[Craig Kirkpatrick]

Alan, I'll say I think what is needed is to add another feed.  I haven't bothered with a bargraph of kWh per day but it is actually pretty interesting to graph so you can see the seasonality of power usage.

Here is what I think you need to do.  And if it works like I am thinking it won't go back and create your past months, just logging kWh/day from today forward since it is a new feed.  Like I said, I haven't been using this so I'm experimenting but it seems to make sense. 

Look at the new step 6 that takes kWh and should give a daily sum instead of an ever increasing accumulation.

Problem is it will take a few days to tell if it works since it has to create the new feed data once per day.

[chris1howell .]

Mine looks just like that except "log to feed" is last, I am not sure it matters.

[Craig Kirkpatrick]

I think by creating the KWHDAY it is forcing log to feed.  A similar thing I use with temperatures is using the MAX function, and I don't need to add a log to feed after capturing MAX, it just does it already.

[Alan Kirk]

OK, I'll give that a try wand see what it looks like tomorrow.  Here is my Input edit screen which will feed my Charge Power Dashboard.

On Sunday, October 25, 2015 at 2:48:00 PM UTC-7, Craig Kirkpatrick wrote:

[Craig Kirkpatrick]

Alan, Hmmm, take a look at mine again.  I did not replace step five, I added step six.   Look back in this thread a bit for my screen shot on that. You still want to integrate kWh over time and that will take the function that does it in step 5.  Then basically step 6 is the KWH to KWH/D slicing up so you just see the new increment in KWH per day rather than some continuously growing number of kWh.  I hope I'm making sense.

[Craig Kirkpatrick]

Well after a day I don't have much to go on yet, but I noticed the KWHDAY seemed to take the half day of data yesterday and extrapolate it to 24 hours.  I'll keep an eye on it to be sure it makes sense after some more days.

I gave some thought about taking historical feed data of kWh and getting the sort of bar chart we want and I figured out how to do it.  I was able to take my data on the other server from June and I was able to get the sort of bargraph that we are looking for.  The key to getting the bargraph to show a per day readout and not an ever increasing slope is to set delta to 1 in the bargraph configuration.

Shown below is the bargraph data first without delta set, and second with delta set to 1. 

So it seems it is not really necessary to create that kwh/day feed which was in step 6 I described yesterday since the bargraph visualization will let you do it within the graphing tool.  Nifty.

-Craig K.

[Alan Kirk]

I did a 5kWh charge with new calibration values for my setup.  The OpenEVSE operated as expected, shutting down at 5002 Wh.  I am still working on the Emoncms didn't have a lot of good luck there.  Not knowing for sure what the WhAccumulator did, I stuck one in my Input data stream as seen in the screen print.  Something has gone awry as the feed value at step 4 is now 0(didn't get a shot of that).  I thought it should have be watts.  I'm missing something simple.

On Sunday, October 25, 2015 at 2:48:00 PM UTC-7, Craig Kirkpatrick wrote:

[Craig Kirkpatrick]

Your step 4 is overwriting your AMP feed with Wh.  I really do not know what the Wh Accumulator does since I use the Power to kWh tool.  Also your step 6 is overwriting the same feed as step 5.

Don't worry about seeing the AMP feedvalue show as 0.00.  That just means you are looking at while the car is not charging.  Some things will have greater than zero, like kWh and anything you try to capture a MAX feed.

My suggestion is to re-create what I posted yesterday afternoon with the six steps, and take note of creating new feed names where needed.

[Alan Kirk]

I fixed my problems and things are looking good.  Here is a screen shot with real values.

I am still playing with the Power to kWhD entry and visualization as a bar graph.  I am  going for a 3kWh limit today.

e: Ops!  As I was writing the original text the 3kWh limit was reached, the EVSE turned the EV power off then turned it back on.  That was what I experienced last week with a 5kWh limited charge and when I got back to the EV in over 24 hours I had a 100% charge.  Yesterday on the 2kWh limited charge the EVSE went to Sleep and stayed there until I pushed the button, maybe 30 minutes later. Hmmm!  Screen Shot of the Amps.  The left blip is from walking from the EV to the EVSE to set the Charge Limit, then the 3kWh charge, the shut down and then the unrequested start till I disconnected the EV.

[Craig Kirkpatrick]

Alan, good catch on recording that event where your EV resumed charging after a charge limit all by itself.

I'm about 99% certain this is not a firmware problem.  

I have also seen events where one of my OpenEVSEs transitions by itself from pilot state B momentarily to pilot state A and then back to B again.  I've only ever seen this with the Huzzah module in place.

Transitioning briefly to state A looks to the OpenEVSE as if the car was unplugged, which resets the charge limit, and since the car is still plugged in it happily resumes charging since it still has some hunger for more charging and it is still plugged in.

When I first saw this back in early July I experimented with changing the firmware thresholds for detecting pilot state B vs A so it was more reliable with the Huzzah module in place.  My experiments supported the theory that the extra load on the 5V causes the A/D in the processor to mis-interpret the 9V pilot as having crossed over the threshold to closer to 12V.  Really the solution to this is not a firmware tweak of the pilot thresholds but instead a more solid supply of 5V to both the main processor and the Huzzah.

I think what is in order is for me to update my OpenEVSE to the latest development code restoring the default pilot thresholds, then try to reproduce what you observed with the charge limit ending and charging beginning autonomously, then add a regulator converting 12V to supply Huzzah's 5V, finally see if in that condition I can still reproduce the weird behavior.

I was already meaning to do most of this with that OpenEVSE unit.  Now that you have some solid evidence it is the right time for me to begin this experiment.

By the way, it looks like your Power to kWh/d is doing what you want it to do.  And I had some grumblings about how the kWh to kWh/d was working since it seemed to extrapolate the limited data over the 24 hour period.

Now that you are using per day kind of things in Emoncms you will want to be sure to set your time zone in Emoncms.  You can set it to "America/Los Angeles" in the account setting screen.

Thanks again for capturing the event at the end of the charge limit.

[Alan Kirk]

My EVSE Temp was nominal at about 80F raising to mid 90's.  I still have the R28 resistor in place.  My internal temp got to 105 yesterday and everything seemed to run OK so while the Power Supply could still be an issue I would think the internal temp variation would show up problems (resets) more often.  I noted the time between Sleep and the restart was several minutes.  It would appear to be much longer than a PS induced reset. 

On another front, how does one query the EVSE via the WiFi connection?  I think one should be able to use PuTTY but I haven't figured out how to configure it.  This may be a topic for another post to start.

I've attached my cut at the charge energy and a this mornings events combined

[Craig Kirkpatrick]

Alan, temperatures up to 50C = 122F are perfectly within the operating specifications of the most limited component which is the power supply.  Chris had a summer full of data with the threshold raised to 60C = 140F charging safely so the development code D3.10.3 has the ambient temperature where we begin throttling the pilot signal to the EV set at 60C.  Above 60C we cut the pilot signal amperage in half, reaching even higher 63C we cut it to a quarter, continuing to get hot enough at 66C it is game over and we tell the EV to quit and give it about five seconds and then force open the contactor no matter what.  The temperature recording from the RTC on the LCD gives 1/4C resolution, makes for nice smooth graphs.  The alternate ambient sensor MCP9808 and also the infrared sensor TMP007 give a really nice 1/10 degree resolution.  All of the sensors are plenty accurate and we are really happy that the RTC sensor gives equivalent accuracy to the MCP9808.

About the power supply glitch that lets the OpenEVSE think it saw an EV disconnect, that would not happen at the beginning of that 5 minute gap, but instead it happened 5 minutes after the charge limit finished and then the EVSE and the EV thought everything was good to begin normal charging again.  I can usually see about one of these anomalous EV unplug events per night.  What first alerted me to the hiccup was knowing I had about 2000Wh on the charge record only to find it reading 0Wh in the morning - and that only happens if the EVSE thinks the car was unplugged and then plugged in again.

I think it is possible to add the functionality you describe, having the Huzzah module publish a web page within your network so that you could have a nice graphical access to the commands and data available within OpenEVSE, think of it as an enhance graphical interface to OpenEVSE not limited to the button and LCD interface.  Folks smarter than I am need to begin that code.  I see no reason it cannot be done.  Heck we've come a long way since a year ago when we first were able to get a reading of amperage on the LCD.

When you feel comfortable to share your dashboards, you can check to be sure the feeds that are used are public, check that the dashboards are public and published.  Then you can give out the URL for people to look at your dashboards online, they can zoom in, do whatever they want to do without effecting the work you did or the view you get.  Here are mine after I moved them to http://data.openevse.com/emoncms/CraigOpenEVSE   It begins with my default dashboard but you can check out the other dashboards.  It is a good way to share creative ideas for dashboard stuff.

-Craig K.

[Alan Kirk]

I've made my Emoncms Inputs public but for the life of me I do not see a user specific URL to publish it.  The one I have is http://data.openevse.com/emoncms/input/view but suspect that only works from my computers.

That time stamp feature would be great so I want to encourage you!  Now that you are unemployed and resting on your Laurels:) .

Of course I still don't know how to get at the RAPI via the WiFi.  I know its address but don't know how to set up PuTTY correctly, Help!

[Craig Kirkpatrick]

Alan, oops, I should have mentioned, just take http://data.openevse.com/emoncms/  and append your login name.  Mine is CraigOpenEVSE so that explains my URL.

I work a lot in Chrome browser, and when I want to check what others will see on my dashboard I use another browser like Safari to look at Emoncms.  That way I do not need to logout first from Emoncms in order to see the public view.

I like the time/date of boot feature idea.  Another interesting idea is a record of hours of uptime, do it like incrementing an eeprom value once per hour, but upon boot copy the eeprom value to a ram variable that can be read out via rapi and then reset the eeprom hour counter to zero.  Hourly writes to an eeprom address are safe within the ten year operational life expectation - or maybe we let management decide how long an OpenEVSE's lifetime should be.

I don't know of a way to send rapi commands and queries to OpenEVSE thru the Huzzah module at this point in time.  It will take some development work.  We got sort of side-tracked debugging reliability with Huzzah and that stalled new development.  I'm paying a lot of attention to helping with Huzzah so we can jump start new development since there are a ton of great things we can do with it moving forward.

I laughed out loud, "resting on my Laurels" since my wife's name is Laurel.  Yes I'm enjoying my sabbatical, my euphemism for unemployment, getting to focus on hobbies and learning new things.

-Craig K.

[Alan Kirk]

OK  Here is my Emoncms site http://data.openevse.com/emoncms/agkirk

Hope it works.  e: I tried it and it works just like you said.

Maybe the RAPI via WiFi does not exist.  It has to be bi-directional now, since it talks to the router (and I hope listens).  Maybe everyone is using wire!

[Craig Kirkpatrick]

Good.  I can see it.  Still think maybe there is something wrong with a few of the graphs, maybe they are looking at old feeds you deleted.  I'm watching your temperature in degrees F, getting sort of on the high side, should throttle the current if it reaches 140F.  Could be fun to watch, but world series baseball games begins soon.  :-)

[Craig Kirkpatrick]

Alan, I forgot to touch on RAPI over WiFi.  It does not exist yet with the Huzzah module implementation on OpenEVSE.  The keyword is yet.  I see no reason it cannot be done over time.

Actually Sam had RAPI over WiFi working with some work that he did with the OpenWRT pocket routers if you remember that effort from about a year ago.   What is nice about the Esp8266 Huzzah is its size and low power requirement and also it is dirt cheap.  Integrating the OpenWRT required another little transformer to power it, so it was a bit clumsy even though it did work nicely.

By the way, with the recent development firmware you were within about two degrees F of the OpenEVSE throttling current at 140F to reduce the source of heat.  Middle of summer it would have throttled at 129F, beginning of summer before we knew what thresholds made sense it would have throttled at a very safe 122F.  Even when the throttling occurs everything should  behave normally to the casual user; return to the car later and it is fully charged and no worries at all.  It is only if the heating does not respond to the throttling that the OpenEVSE will end up in an error state, making it obvious that it is time to open up the enclosure to take a look at possible causes.

[chris1howell .]

Are you sure it does not exist yet...? I'll show it off next week.

Emoncms and RAPI are pretty flexible. It is really easy to read the inputs and write values. I am working on learning PHP and MySQL so I can build a fancy configuration interface on the Emoncms server.

[Craig Kirkpatrick]

Very nice.  I'm eager to see it!

[chris1howell .]

Its nothing fancy right now, just a python script that reads all the inputs. I have an API_Update flag that signals to OpenEVSE to pull down config settings. I'll get the API setup and let the pros take it from there.

[Alan Kirk]

This is the first time I have observed the internal temperature rise like this.  I'm making a WAG that this is related to the low sun angle hitting the display window and the RTC chip is getting the full effect of that heating.  I was not charging after the 0900 hrs slot.  One woud think it was some form of thermal runaway as it has continued into the evening.  Don't know what caused it. 

Is there a way to clear past data in Emoncms?

On Sunday, October 25, 2015 at 2:48:00 PM UTC-7, Craig Kirkpatrick wrote:

[Alan Kirk]

My Dashboard bar graphs for kWhDs don't appear to be correct in that they don't reflect the 30 Oct energy used correctly.  If I go to Emoncms VIS and select a bar graph and kWhD feed it looks right.  I'm missing something simple in setting up the Dashboard, I think.

Also, when I post it seems the entire chain of post gets added.  Some users don't seem to have this problem.  Is there some box I should be checking to rid myself and other of this annoyance?

[Craig Kirkpatrick]

Alan, I'm glad to read it was just the sun shining on your EVSE. I had that happening to my OpenEVSE on my driveway on the north side of my house for a month around the summer solstice.

I'm not sure what's up with your kWh/day bar graph. I started using the approach of letting the bar graph do its own delta of kWh in order to see a bargraph of kWh per day and it is working nicely. What I can do later today is setup another bargraph to show the kwhday feed that I setup a few days ago and compare the two approaches to getting bargraphs looking like we want them to look.

You asked about resetting or wiping old feed data and I don't know how to do it other than deleting the feed and starting over again with a new feed doing the same thing. When I first taught myself Emoncms and learned by too many mistakes I just created a new login once I thought I knew what I was doing. Then I could begin with a blank slate. Creating a new login has its own difficulty in that you'll end up with a new write key that you'll need to get into the Huzzah module.

I do not understand your latest question. I simply do not understand what you are asking. Give it another try and I'll see if I catch what you mean.

[Craig Kirkpatrick]

Ah, ok, now I get what you meant. You are talking about replies in this forum where it shows all of the quoted text below what you write.
Really I don't think it is a problem and I don't perceive you are doing anything wrong. Sometimes I'll select a bunch of old quoted text below my reply and just delete it, usually when I want to be ultra clear about which thing I'm replying to. Usually the browser someone uses to read this forum does a nice job of hiding the quoted text and giving the option to open it when you want to read it. So on my end I don't see any problem in the way you post thing here.

[Alan Kirk]

I did this

and got this

The old values are starting to look better.  I left the Delta blank.

I'm charging now and my input page looks like this

Wasn't fast enough!  It was a 3kWh charge and it is already over.  Too much fun!  Oh! But wait, it started again

[Craig Kirkpatrick]

That is looking pretty believable, and since you already feed kwhd you would not want the graph set to delta, so you are doing it right and it looks good.

Me on the other hand I have a different feed function I thought would work to take kWh and give kWh/day but just now when I tried to bargraph it it was 1000% bogus.  I'll stick with bargraph delta of kWh since that is working nicely for me.  I may delete my kwhkwhd to what you are doing as kwhd but honestly I'd say there is a bug in Emoncms code that what I was trying did not work.  No big deal though since I have it working with the bargraph delta of kWh.

I suppose it is a good thing that you can repeat the little problem of the charge limit resuming charging all by itself.  That way when we have a firmware to test you can give it a try to see if that little problem goes away.  Chris and I are pretty sure a slight adjustment of the decision thresholds in the firmware that tell us the EV disconnected may remedy the problem.

[Alan Kirk]

The sunlight has walked up to the EVSE and the Temp right along with it. This puts that issue to bed.
I know it has no real basis but any chance a 2 kWh charge vs 3 kWh would create the problem? A previous 2 kWh didn't trigger the 100 % charge!

[Craig Kirkpatrick]

I went ahead and tested 2k and 3k on the bench and they both work fine. So it is not a firmware problem.

[Bobby Chung]

Hi Everyone, 

Thanks to everyone's hard work, I have everything up and running and so far it's working great!  Check out my site.

http://data.openevse.com/emoncms/bobbychung/

I have everything button up and will be testing it out for the next few weeks/months.  One thing that I've done differently is I have another mod on my 50A Deluxe kit that allows me to do level 1 charging as well.  The mod involved adding a cheap inverter that you find for the 12V plug in the car.  That inverter happens to have a 5V regulator that supplies power to a USB port so I'm powering the Huzzah module with that which doesn't draw any current from the controller's power supply (this completely isolates the two except for a common ground).  Hopefully this helps in making sure the wifi module is stable. 

Bobby

[Craig Kirkpatrick]

Good looking dashboard you have there.  Well done.

[Alan Kirk]

Bobby, Nice dashboard!  Is it possible to post your feed details?

[Johnathan Vail]

Glad I found this group. I think I understand the processing now.  Still don't know where the magic numbers come from for the scaling, etc.  Here's what I have:

http://data.openevse.com/emoncms/dashboard/view&id=99

Current is like 3500 for about 14 A on the LCD, 0 for 0 and about 155 for the occasional noises on the Volt.

Temperature is all over, usually close to 0 but never negative or the absurd large unsigned-sign numbers even though I was getting the too cold "over temperature" bug on the OpenEVSE.  

Voltage always seems to be -1 although it is getting data.

So far the only number that makes sense is Pilot...

I am SO close to getting this sorted.  What are the scaling numbers and do I need to do my own calibration?    If I know 3500 is about 14 amps i could do the 2 point slope but it seems like I shouldn't have to.  Also temperature should be calibrated already but not sure what numbers I am getting in the feed.

Thanks for any help

[Alan Kirk]

Here is what I have for my Dashboard Inputs and Feeds and their Setups:  My Dashboard has its issues so this is not the best solution but maybe it will help.  The .9388 constant corrects my current measurement and the .241 is my input AC value for Watts.  the Temp correction factors are (9/5)/10 the C measurement and 32 degree offset for F.

:

[Johnathan Vail]

Thanks.  I am starting to figure it out.  You got the .9388 by calibrating with an external current meter or somewhere else?  

I notice that the current in the data is a little high compared to what is displayed on the screen.  Is the data value we get a raw value and the displayed value using a current calibration in the firmware?

And to what you have the temperature value is in deci-degrees C (C/10)?  Do you see yours go negative?

Thanks for the examples.  Now that I understand it a little better I want to get the accumulated watts going.

jv

--
You received this message because you are subscribed to a topic in the Google Groups "OpenEVSE" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openevse/znVgOiQZIVg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openevse+u...@googlegroups.com.

[Alan Kirk]

I measured the current into my EVSE with a Fulke 321 clamp-on current meter.  The AC voltage varies with time-of-day and home location so it will be the biggest contributor of error.  The energy my Dashboard  calculated is within 3% of what my Nissan Leaf accepts as a charge when viewed on the dash and with Leaf Spy Pro. 

The data is a RAW measurement that is messaged by the EVSE firmware for the LCD display. 

I live in the California desert so have not seen the negative temp problem but I believe it has been corrected within the past week.

Try different Input setups and erase/delete often!  I still haven't got everything on my energy page working.

[Keith Thomas]

Thats what I am trying to figure out, how are other displaying accurate voltage mine wont show anything but -1

[chris1howell .]

OpenEVSE does not have s sensor to measure voltage. I have voltage on my dashboard coming from another device the Open Energy Monitor.

[Alan Kirk]

I recently took another look at the kWh being measured via Emoncms and noted the Emoncms was about 3.5% higher than the recorded kWh into the battery.  Made a correction to my Emoncms Inputs to calibrate its measurements.  After a day or two of refection I realized I had failed to account for the conversion efficiency of the EVs charger and the original Emoncms data may have been closer than I thought.  Does anyone have an  idea of the Leaf's charger efficiency? 

[Keith Thomas]

On Friday, February 19, 2016 at 6:24:30 AM UTC-8, Chris wrote:

OpenEVSE does not have s sensor to measure voltage. I have voltage on my dashboard coming from another device the Open Energy Monitor.

Just looking at that site, looks interesting. may have to converse with you on that also. Kind of looks confusing as to what I wold need and how to connect it to the panel. 

[chris1howell .]

Yeah, it was a lot of work to get the EMON TX and raspberry pi setup. If you look at my solar chart it is down a bit too...

But... I have designed a beter version with 3 CTs, temperature sensor and Voltage with the same WiFi chip and code as OpenEVSE. It is about the size of a deck of cards. I should have it ready in a month or two...

--

You received this message because you are subscribed to the Google Groups "OpenEVSE" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openevse+u...@googlegroups.com.

[Cory Clemmer]

Chris, if you need any hardware testers for your emontx clone, just let me know.

[bab...@gmail.com]

Did anyone ever get a chance to replicate Bobbys dashboard feeds? I love that layout but i am having troubles with the max current setting and some of the energy consumed feeds.  would love some help if anyone is willing!

[Bobby]

Thanks. Probably the best way is for you to use the above link and select the log in icon of the house and log in as me. Hopefully no one will change my credentials so here is my info. Bobbychung, thisistemporary. I'm going to change this tomorrow night.

[Danny ter Haar]

On Wednesday, August 17, 2016 at 7:30:39 PM UTC-7, Bobby wrote:

Thanks.  Probably the best way is for you to use the above link and select the log in icon of the house and log in as me.  Hopefully no one will change my credentials so here is my info.  Bobbychung, thisistemporary.  I'm going to change this tomorrow night.

That looks so slick!

Is there a way you can "download" all those settings and upload under my own account ?

Very _very_ slick, hat off! 

[lincomatic]

Very nice! Yeah, we need a way to copy someone else’s settings!

[Darock999]

Awesome, thanks so much Bobby.  I have gone in and matched my dashboard/inputs/feeds to yours and i am now just going to have to burn some electrons tonight to see some data come in! :)

[Cory Johnson]

Hello,

I am trying to duplicate this, and was wondering if there is any detailed setup for what is shown here:

http://data.openevse.com/emoncms/bobbychung&id=247

Thanks!

[Danny ter Haar]

On Wednesday, December 7, 2016 at 5:20:56 PM UTC-8, cmgj wrote:

Hello,

I am trying to duplicate this, and was wondering if there is any detailed setup for what is shown here:

http://data.openevse.com/emoncms/bobbychung&id=247

Thanks!

+1

[lincomatic]

One thing emoncms is sorely in need of is  way to export & import configs

 

From: open...@googlegroups.com [mailto:open...@googlegroups.com] On Behalf Of Danny ter Haar
Sent: Wednesday, December 7, 2016 8:04 PM
To: OpenEVSE
Subject: Re: Emoncms, getting it to do what you want it to do

 

--

[Bobby]

I just temporarily changed my password to just 'password' so people can access my inputs, feeds and dashboard it.

Bobby

[Cory Johnson]

Thank you.  I will take some screen shots!

--

You received this message because you are subscribed to a topic in the Google Groups "OpenEVSE" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openevse/znVgOiQZIVg/unsubscribe.

To unsubscribe from this group and all its topics, send an email to openevse+unsubscribe@googlegroups.com.

[Danny ter Haar]

On Thursday, December 8, 2016 at 8:00:18 AM UTC-8, Bobby wrote:

I just temporarily changed my password to just 'password' so people can access my inputs, feeds and dashboard it.

Bobby

If somebody would post _how_ to copy his design over to your own dashboard,
that would be awesome !

[Cory Johnson]

There really isn't way to copy...but I may post some instructions if I get time.

--

You received this message because you are subscribed to a topic in the Google Groups "OpenEVSE" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openevse/znVgOiQZIVg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openevse+unsubscribe@googlegroups.com.