Support

Hi,

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

1. I was having random disconnections
2. I try to avoid using radiowaves when possible

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.

Hardware choice

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.

Wiring

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.

Box Setup

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.

Software

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):

echo '$GE' | netcat -C -w 1 192.168.1.51 10000

Set max current "Pilot" setpoint ($SC xx rapi command), example for 10A:

echo '$SC 10' | netcat -C -w 1 192.168.1.51 10000

Get actual charge current value ($GG rapi command):

echo '$GG' | netcat -C -w 1 192.168.1.51 10000

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.

The end

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!

Yup working a treat - managed to adapt my code easily too!

Thanks again for your instructions. :)

I will use Step Down for 3.3V.

Once I have it done, I will post the results.

BR,

Pedro

Hi ,

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

BR,

Pedro

Hi Glebiys,

I didn't change anything on the openevse firmware. I'm just using the original RAPI commands.

I didn't test any other ethernet module than the TCP232-T2.

It seems to me that the module from your link is ethernet to SPI, not UART; but I might be wrong as I don't read Russian.

Guillaume G.

Hi Anthony,

As I remember, the 5V/3.3V support is about the power supply, not about the logic signals, double check in the pdf manual if available.

I don't sell the enclosure, but you can find the stl file attached here. I de-soldered the front pins on my TCP232 board to fit it in the enclosure.

The PG choice might depend on you cable diameter and your location, but this one looks quite OK I guess: https://www.banggood.com/Waterproof-12mm-M12X1_5-IP68-Cable-Gland-Compression-TRS-Stuffing-Locknut-p-986732.html

Hi,

I don't sell the enclosure, but find it here attached as a STL file. I removed the front pins from mine to fit it in.

I used a PG I had lying around, but this one looks OK too.

Thanks for the update - glad you got it sorted. I checked and it seems I have a genuine module. *phew*