Since my OpenEVSE charging station will placed at level -3 and my apartment is at level 4, wireless will not be an option, because I will be limited to control when I am near my car using as hotspot the wifi module :(
So to control from my apartment wired connection is the only way
Since I do not have any resistors at home and I need to order something, what do you think about ordering an module 3.3V 5V TTL Logic Level Converter Bi-directional
Since the place where I will put my OpenEVSE will be at level -3 and my apartment is at level 4 (7 floors away) wifi is not an option because I want to control from home. With wifi I'm limited as hotspot near the car.
So, wired is the only option.
Since I have no resistors at home and I need to buy them, instead I was think to buy a module to convert 3.3V <--> 5V.
ex.: 3.3V 5V TTL Logic Level Converter Bi-directional
What do you think?
The signal level converter is probably a better solution than the resistors, however, my only concern would be to check if you need to supply +3.3v to it as I think we don't have any on our setup.
The ebay page isn't clear about it.
This said, I guess you could still add a 3.3v dc/dc converter from the 12v or the 5v.
Am finally preparing to convert my OpenEVSE from the wireless to the Ethernet module. From digging around it appears the the Huzzah ESP8266 WiFi Module includes MQTT support. Am guessing the USR-TCP232-T2 Serial -> Ethernet will not have any such support... does sound like includes a webpage for config though. Can anyone clarify/expand on this... I would love to use MQTT but over a wired connection. Thanks!
I confirm that by removing the wifi module we lose the features it includes like MQTT.
I also confirm that my USR TCP232 module has an onboard webserver but only for its own config (network, serial settings...).
You might explore something like an ethernet capable arduino board on which you would port some code from the openEVSE wifi module github.
Am thinking of using a raspberry pi as an intermediary for the MQTT connection.. it could be the go between for MQTT and RAPI to Open EVSE.. thanks for the confirmation. Am always pushing for wired connections.
I am also controlling my OpenEVSE using this ethernet method, but some proper support and implementation from the OpenEVSE guys on this front would be awesome!
I am using a home automation system to permanently monitor and adjust the charge current of my OpenEVSE.
I wasn't fully satisfied with the wifi option because
As I didn't find any ad-hoc solution to wire the OpenEVSE to my Ethernet network, I gathered info and parts to make mine. Here I decided to share my experience.
I bought a cheap TCP232-T2 module, lost half a day trying to use it setup software which never worked, ended-up using the setup options of the virtual comport appliance instead to set the device to my need:
The "TCP Server" protocol is crucial.
The BaudRate and COM Parameters should match the OpenEVSE ones, generally as pictured.
The network settings are up to your choices.
The OpenEVSE outputs 5V on its serial pins but the TCP232 is designed for 3.3V only so I tinkered a little bit with connectors, wires and resistors I had around.
I reused the Ubec from the Wifi kit. Ground is already connected between the Ubec 0V and the OpenEVSE GND, so no need to wire it.
I 3D-printed an enclosure to insulate and secure the TCP232 in the box.
I routed the ethernet cable through a PG in the box and crimped a RJ45 connector.
The manufacturer of the TCP232 is providing software solutions for windows, but my home automation runs on a raspberry pi under raspbian gnu/linux.
I found the following netcat commands to fulfil my needs:
Get max current "Pilot" setpoint ($GE rapi command):
Set max current "Pilot" setpoint ($SC xx rapi command), example for 10A:
Get actual charge current value ($GG rapi command):
I "pipe" the rapi command to netcat.
Of course you may extend the principle to any rapi command.
The -C option adds CrLf to each command, needed by the TCP232.
The -w 1 sets a timeout of 1s before ending the tcp session.
There are different netcat versions that may not support these options, or have different switches, please check yours.
The IP and port just match the earlier made settings of my TCP232.
I think the most valuable info from my project is there.
I hope my english is OK.
Any mistake in this post? There are better ways to achieve the same goal; Any idea in mind, please comment!
3 people like this idea