Indeed, but I guess that is not happening anymore. I got in touch with someone who flashed OpenEVSE firmware using the provided web frontend of the box with :
Is that that simple? But the box stopped reporting any ampere values at all. I am not sure about how safe that approach ist.
Is there a way back? Mhmhm…
Thanks,
PNT
ESP32 only reports stuff, so it is rather safe to flash it. Charging controller an
He lost ampere indication, because of Kinetos using separate energy meter for that. Maybe the board still has CT header for this case and he can connect a CT.
That is a main reason why i want to make a backup before flashing.
Hello!
@Shockwave I have the same wallbox. I already flashed the ESP32 with the newest huzzah firmware, sadly I forgot to backup the stock firmware. Can you please send me your dump of the original firmware?
Regards
Stefan
Hi, i make the same mistake… No Backup / Dump
Anyone has the original Firmware? This will Help a Lot.
Thank you.
So, for some time the weather was cold and I decided to not touch my Kinetos.
After the reset to defaults (when it stopped detecting the car), EVSE stopped communicating with that modbus energy meter. Most probably, Kinetos had special RAPI parameter that needed to be set, but was undocumented just like everything. I decided to at least try to flash ESP32 over the air to see what comes out of it. Since I did that from phone while watching tv, I did not make any backups and even chose olimex firmware to make sure that ESP32 gets bricked… 
Success - I still have a good offline charger. I quickly ran through schematics and that box and since this RS485 meter looks to be connected to EVSE and not ESP32, I looked on the board and tested resistance on seemingly CT input (last 2 pins on top, labeled C-,C+) and since it was 22R, I decided to install CT and order Olimex ESP32 gateway and desolder that old board and connect Olimex with jumper wires. After Olimex arrives, I’ll backup and flash EVSE to see if it works fine with original firmware and if anything does not work, I’ll just buy original OpenEVSE board and convert that to genuine OpenEVSE station. Shame that Olimex is not producing OpenEVSE boards.
My Olimex gateway arrived early and I decided to flash it and try to connect it, as I saw jumpers on TX/RX and i managed to guess right - I connected to RX/TX/GND/3V3 pins and changed pin 5V to 3V3 on Olimex board and things work just fine. Olimex with external antenna even has good Wifi reception where original board was offline. The only thing that nowhere did I see flash size, up until the flashing. Just have to figure out a good place for this board.
And yet, we can take a good idea from Kinetos, but implement it better - voltage measuring (i.e. usage of a meter or something in that style).
Here is my home voltage graph of all three phases for this day:
Our standard (EU EN 60038) allows for 230V/400V with ±10% deviation, therefore power may deviate by 10% and ±10% is not exactly precise even for home use statistics.
I would implement PZEM style device that would be cost effective and functional at the same time. PZEM-6L24 for 3 phases or just PZEM-004T for single phase.
When it gets warmer, I will probably try to connect that meter to my HomeAssistant, though I have no hopes, since it was branded Bond Electronics and nothing can be found on the internet about it.
So.. a tiny progress.
Got a pack of small current transformers and connected one to the C+ and C- pins on the board and got a working current detection with reasonable precision.
I have not flashed the EVSE yet and to most of the commands I get a respoonse of “RAPI_RESPONSE_BLOCKED”.
So far only the light colour does not work and I haven’t tested RFID, nor I plan to implement it.
Seems like I am the only one fiddling with this crazy box.
Did anyone connect a AVR programmer to this Kinetos, to reflash the EVSE? The markings on the programming sockets are misleading at best.
Currently I am struggling with EVSE answering with RAPI_RESPONSE_BLOCKED to every RAPI SET command and I have lost ammeter settings and cannot set them. I am quite close to just getting an OpenEVSE board and throwing that “‘Bond Electronics” trash in the bin. The only thing stopping me is shipping from US. OpenEVSE could partner with Olimex on this one.
That’s quite odd. The current is controlled by car and EVSE just “advertises” the capability.
Do you have a “single board (Bond electronics)” or “dual board "(AUEM)” version?
You can upgrade built in ESP32 with a bit customised OpenEVSE wifi firmware, to keep all functions.
I had to chenge some parts and compile myself after connecting Olimex board for testing.
EVSE firmware is upgradeable only on 2 board version, because germans decided to goof around with ISP pins on “Bond electronics” version. Your problem sounds like either car fault or EVSE settings.
Nope, Auem must be 2 boards. Try to remove that plastic cover. Please be sure to switch off power before!
Yep, one of the first iterations and more compatible with OpenEVSE. There is a modification in source code for this esp32 board as well. Not sure what brings this error. Maybe wrong CT configuration.
Where can i find the fixed firmware?
At github there are other esp boards only
So, in short - your device has 2 boards - ESP32 and Atmega. You have to at least flash that ESP32 board (the one your LAN connects to) with latest git version that you will have to compile, as there are no precompiled binaries for unsupported boards. You have to choose board type at compilation. To match that W32 kinetos auem. Later, you can flash main controller, but that requires programmer - AVRDude type.
Thx. The kinetos has a modbus rccb. Is there something I have to configure?
Modbus rccb? Haven’t heard of that. I’ve seen modbus energy meter, but that will not work - originally openevse uses CT for energy measuring.
