Support
How can we help you today?
OpenEVSE board for juicebox
Just installed the Juicebox V2 board in my 48amp JB unit. Is there a torque spec for the ground screws, especially where they all meet?
Is the temperature sensor required for these retrofit boards for JuiceBox? I have charged it a few time, and only 1-2 hours each time, but I am concerned without the sensor, the unit would overheat and catch fire. Are there any emergency failsafe that would kick in without the temperature sensor being present?
I guess this is the catch-all thread for this. I bought a Juicebox off EBay and an OpenEVSE board. Have installed the board. Had to order a new power cord because it looks like they just cut it off. Hots are 6 AWG. But they don't fit in the GFCI coil. They're both supposed to go through the GFCI coil right? Is there any (reasonably safe) way around that?
I needed a 6 foot cord, so I went with 6 AWG, thinking it'd be safer. Now I've cut the terminals off to put on my own ferrules. Great.
OpenEVSE Support
@Troy We used the same connector and pinout for the I2C on the OpenEVSE and Juicebox boards so all the accessories would be compatible. The kit we sell works for both and includes the correct cable. https://store.openevse.com/collections/all-products/products/temperature-sensor
Only one sensor is needed. Temp 2, provides temperature throttling and shutdown. Temp 1 and 3 and no longer supported. Temp 4 can only provide a value no throttling and shutdown. If you really want Temp 4 it is just a JST SH to JST SH straight through.
Thanks however this is not the board that the juicebox is using, plus there are 2 temp connections, are you talking about connecting to the I2C connector and if so what do you connnect the second temp sensor to?
OpenEVSE Support
@Troy
The connector is JST SH on the sensor side and JST PH on the controller side.
Here is a diagram with the pinout.
https://github.com/OpenEVSE/OpenEVSE_PLUS/blob/master/OpenEVSE_PLUS_v5.5/OpenEVSE_v5.5.jpg
Can someone advise the pinout and what connecter to connect the 2 temp sensors to.
"
Temp 2 is MCP9808 sensor connected to the Controller. When installed it is used for enclosure temperature throttling and Emergency Cutoff.
Temp 4 is MCP9808 sensor connected to WiFi, It is for situational awareness and logging.
"
Thanks in advance.
Troy
OpenEVSE Support
@Jeff James We have seen this a couple times. We have the parts to make an adapter. We will send you one at no cost.
Chris
I just installed the OpenEVSE board for a Juicebox v2. Unfortunately, the pilot connect is very different and incompatible. I have reached out to support, but so far have not heard a response. Anyone else have this issue?
Another question, the pilot wire going to the cable to the car is a heavy gauge, is there really a lot of current that goes through this wire?
I just upgraded a Juicebox v2 this weekend and the pilot connector seems to be incompatible with the board I received. I submitted a ticket, but so far have not heard anything from them.
Both connections are securely connected, I have also changed the stock test wire from one loop to 5 as recommended by your build instructions.
Happy that it is still safe and I can confirm the car charged overnight :)
I have a question about the "Current Scale" and "current offset". I know how to change it and can see the effect however to get the readings close to what my car is showing my current scale is set to 83. Do you have a link to explain the calculations around this or do I need to jump into the code.
OpenEVSE Support
@Troy
Ground Test can be re-enabled. There is a known issue where false positive is detected as the unit loses power when unplugged. It does not affect any functionality.
GFCI Error and GFCI self Test Error are different. GFCI error is an actual ground fault detected. Self test error is the controller tickles the coil before charging to see if it trips on purpose.
Disabling GFCI Test does not disable GFCI it just does not self test GFCI every time before each charge. It is possible the GFCI or test coil came unplugged. We would recommend checking both are securely connected.
Sorry for all the posts - an update.
After I disable the GFCI and Ground test the unit is working as it should.
Can you suggest why this may be the reason?
Do you have some suggestions on what I can do to test that the board is working?
Any reason why it would work okay first and then start showing this fault?
I just restarted the unit and get the following, no count on the GFCI error but it is displayed.
Fault will go away, but will no longer detect car or change from starting
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.