Support

Better, but I still have to ask, "why the huge max A display". I don't really see the need for any display of this number, but maybe it would be handy to have there somewhere. However it definitely does NOT have to be the biggest of all the screen info. Something small would be much better IMO and use the space for other more useful info.

And let's get the touch screen usable. Now that would be useful.

That's why I like OpenEVSE. :-)

I'm kimble4, I kept the large max current display because it suits my use case: A portable unit that can be plugged into supplies of different capabilities, so it makes sense that it's really clear what the limit is currently set to.

One thing I've thought about is a vibration sensor to detect a person tapping on the front of the case - I've seen that done on a solar inverter as a simple way to wake the backlight and cycle through display modes (which is all most people are going to want to do most of the time) without having to compromise the waterproofing.

@kimble4, I'm not just trying to be negative. Well done for making the mods to suit you. I would like to think I will find the time to get into that myself.

For my use case, the max. current is of little interest, although I do understand it could be different for others, but having it so large makes no sense to me. As long as you can read the data, I would have thought it better to make that smaller and instead have more info on the screen.

Also, there is no indication what that value is. When first seeing the new large display, I was not alone in querying what that figure was, thinking it was likely to be the current charge rate - a far more important value as far as I'm concerned. Good interface design means the user being able to understand what the display is showing with no ambiguity.

The new screen is a 'work in progress' I know and I look forward to seeing how it progresses and hope to be able to provide some development input when I can.

Is it possible to modify the old enclosure to install this new 3.5" display?

I assume this is documented somewhere but I can't seem to find it anywhere.  What is the binary file for this development firmware to display actual charge power.  Is it openevse_wifi_tft_v1_dev.bin ?  And is that all that is needed to update via the OpenEVSE web interface locally?  Thanks.

I assume it is listed in some documentation somewhere but I can't seem to find it anywhere.  What is the binary for the new display firmware referenced here that will show the charging power?  Is it openevse_wifi_tft_v1_dev.bin ?  Is that the only file needed to update the firmware from the OpenEVSE firmware update page when doing a local firmware update?  Thanks.

I tested Kim's version on my client's unit two weeks ago, and while it will display the current amps (in the small field), the screen blanks (goes black) after a couple of minutes and can't be restored without a power cycle, so I re-flashed to the older firmware.

With both versions, the web page will reflect a change to Max Current, but the change isn't reflected on either the TFT display nor the app's Setpoint field for quite a while.  I can move the slider to change Max Current, but there's no indication that anything is changed at the unit side.  

In the example image below, see the Max Current field, the Setpoint display, and the unit display.  The three do not agree.

The backlight timeout is set by the value of TFT_BACKLIGHT_TIMEOUT_MS in platformio.ini  If you comment this out it should stay on permanently.  Regardless, the backlight should wake up whenever the EVSE state changes (eg. plugging or unplugging the vehicle), and stay on as long as the charging current is more than TFT_BACKLIGHT_CHARGING_THRESHOLD amps.

I've seen the same thing as Al, sometimes the display seems to "go to sleep" and turn off. For me, though, it's woken up when I've plugged in the car, so I thought it was intentional. The screen updates have been working quite reliably lately although, as I posted in this thread some time ago, sometimes something seems to "hang" and the current not update. I've seen this both with the stock 6.1.1 and with the updated display version as in the photo above. (I'm not sure whether the time was still updating, if this happens again I'll check.)