@hmbay. I will send hardware to lincomatic.
The proposed change is not to delay detecting the error condition, it is to delay writing the error to memory. For example the error must be detected for more than 1 second before it is written to menory.
THANK YOU!!
I have been dreading transitioning this JuiceBox Pro 40 into an OpenEVSE for years. Thank you sooo much for making it this easy. Just this weekend I needed to turn down the current and there wasn't a method still working for the original JuiceBox Pro 40 so I was about to order the Advanced kit and build it out in the frame and you have taken all the hard work out of the project.
Tell Chris H. thanks.
We are now a family of 5 OpenEVSE kits for the four EVs and behind me at this moment my wife is writing the scripts to monitor our Virtual Power Plant to only allow charging when we would otherwise send the excess to the grid. The JuiceBox Pro 40 was going to be a problem in our new energy setup but not any longer. The same RAPI commands will work on all of them. GREAT!! You guys are the best!
@hmbay, v2 is the simpelest and seems to have little variation. We have only had a single report of one connector differance.
v0 has a lot of variation, the v1 board has footprints to solder on screw terminals so it is doable but takes a little more care figuring out what each wire is for.
Regarding: "Just this weekend I needed to turn down the current and there wasn't a method still working for the original JuiceBox Pro 40"
All JuiceBoxes including V0 still have the host or access point mode where you can connect directly to the unit via WiFi and get a web page with settings that you can change like the current level. I have an ancient V0 and it still has this feature. Same with my V1. It's not a feature that was advertised a lot especially if you used the Mobile App to do everything but it has been there the whole time.
@hmbay
One of the last firmware updates I received on the JuiceBox Pro 40A removed the webserver from AP mode. When I connect in AP, there isn't anything running like the old days where there was a webserver which allowed adjustment to current.
@hmbay
One of the last firmware updates I received on JuiceBox Pro 40A removed the webserver from AP mode.
Just wanted to give an update... I've now tested 2 boards (V1.0.3 and V1.1.0) on my V1 JuiceBox Pro 40 (orange & black metal case) and 2 boards on my V2 JuiceBox (purple plastic case) and so far, no joy. 3 of the boards give the Earth Ground Check failed and the last V1.0.3 for V2 was DOA. OpenEVSE is working on it and I'm getting excellent response including their pointing out my stupid wire swap on the sensor coils but it is looking like perhaps there was more variation in the designs than was expected. As I mentioned before, I'm blessed with one JuiceBox from each generation so updating them to work in the modern world was my goal. Thankfully I have a 4th Nissan unit that I've been using while we try to upgrade the others.
The original JuiceBox boards do have version numbers on them and I've sent pictures to Support so that they can compare them to what they test with.
Finally, I've also tested my power configuration with an RV line conditioner (all green) and my main panel is newish (two years old, installed by electrician) so I definitely have ground (in fact 2 ground rods). Anyone else going through this?
@hmbay There is a lot of variation and EMotorWerks/Enel did something I really do not like. They used the same connector in several different functions on both the V1 and V2.
On the V1 the AC test and AC line are the same connector. If they are reversed it looks like the board is DOA. You might want to check this. In addition the GFCI coil and Current coil are the same connector, reversing these causes a GFCI fault and a No Ground error.
On the v2 the DC, Relay, GFCI coil and Current coil are the same connector, mixing these causes a GFCI fault and a No Ground error.
Issues are not that common we have had about 10 actual bad boards in about 500 shipped so far, most of the time issues trace back to swapped connectors.
With the upgrade can I remotely set the current limit? My goal is to remotely turn charging on/off and to toggle between a 40A charge limit and a low (8A?) charge limit depending on external factors.
@Nick Yes you can you can also use home assistant to calculate your external factors and automatically change current. For example you could set the station to use excess solar production.
@Troy v0 is ready we just solder on a bunch of screw terminals to the v1 board. The V0 is an option on the V1 store page.
The pictures in the instructions seem to show everything swapped around which is sightly odd.
With the board orientated I have it all the connections reach ok except for the pink GFI related connection. Should I cut and extend these wires?
I don't think I can rotate the board as the heavy to-car wires are in the way of the bottom side components.
Also is there an antenna you recommend using?
openev. freshdesk. com@redsails. net
I am considering buying the new juicebox retrofit board to get myself started in the OpenEVSE world. I have exactly zero experience with OpenEVSE, and some experience with DIY electronics (ESP-home).
Could someone help me figure out, before I jump in:
* Is that board all-inclusive, or is any additional hardware required?
* Is it compatible with a screen, or at least a button?
* Is it pre-flashed, or do I need to get a programmer too? Which one?
Thanks in advance.