ralferoo / open-evse Goto Github PK

What steps will reproduce the problem?
1. Reboot device
2. cycle programing button
3.

What is the expected output? What do you see instead? The backlight to remain 
on or change color, when charging the backlight goes out completely, still able 
with a light to see text.


What version of the product are you using? On what operating system? OpenEV Ver 
3 board with sw ver 3.3.4


Please provide any additional information below.
Using the 220 volt contactor/relay

SYMPTOMS/ENVIRONMENT:
After plugging vehicle into the open-evse (v4 hardware & v1.0.9 firmware), the 
state is perpetually "EV Connected - EVSE Ready".  The EVSE will not advance to 
the "Charging" state.

Additional symptoms are the boot up sequence takes about 10 seconds (as opposed 
to about 1 second normally) and it causes the pilot pwm frequency to be ~60Hz 
instead of 1kHz (seen with a DMM or oscilloscope).

ISSUE:
This occurred after programming a virgin atmega328p using the ICSP and the 
Arduino IDE by following the instructions at 
https://code.google.com/p/open-evse/wiki/LoadingFirmware and 
http://blog.lincomatic.com/?p=10.

The reason for this occurring is that following this specific programming 
process, the AVR fuses are not set causing the micro-controller's clock to run 
too slow.

WORKAROUND:
Follow the instructions specifically for setting the fuses on 
https://code.google.com/p/open-evse/wiki/AVRDUDE

What steps will reproduce the problem?
1. Enable the AdaFruit RGBLCD definitions in the source code.
2. Compile and load the Hex file into the EVSE
3. Do not plug in the LCD to the i2c header
4. Power on the EVSE

What is the expected output? What do you see instead?
Car should charge in spite of not having a display operating. EVSE does not 
communicate with vehicle and does not charge the car.

Please use labels and text to provide additional information.
Workaround: Compile the source code with RGBLCD definitions disabled if you are 
not using an LCD display. Otherwise, connect the LCD prior to powering up the 
system.

What is the part number and supplier of RELAYPTH3?

While assembling the OpenEVSE LCD - DIY Kit, there was a misalignment in the 
definition of the resistors R1, R2, and R3.

On the board, the following values are declared:
R1=220, R2=330, R3=220 [ohm]
The resistors received in the kit are:
two resistors colored (yellow-white-white-gold-brown.
one resistor colored (brown-blue-black-gold-brown).

What is the correct value and position on the board? (is there an error in the 
bard?)
Anyone who has a working system and can share the correct placement with us?

Thanks, Yoni.

Link to the relevant guide:
https://code.google.com/p/open-evse/wiki/OpenEVSE_DIY_LCD_spec

What steps will reproduce the problem?
Simply check communication after fixing PCB reset issue (missing connection)
1. avrdude -c usbtiny -p m328p

What is the expected output? What do you see instead?
avrdude: Device signature = 0x1e9514
avrdude: Expected signature for ATMEGA328P is 1E 95 0F

What version of the product are you using? On what operating system?
V.4

Please provide any additional information below.
Corrected PCB bug of missing Reset connection to Pin1 Atmel328p

Firmware seems not loaded (board is not working yet

I am building a triphase portable EVSE with a type 2 socket, using the open 
EVSE that cannot be praised enough.
I have one question though: where should I connect the pp-contact of the 
socket? I guess it should be connected to ground, but could someone confirm 
this? It might be a good idea to mention this in the manual. I also noticed 
that in most projects, the pp is not connected at all. 
Many thanks,
Filip

What steps will reproduce the problem?
early Open EVSE boards with no vias (small gold colored circles) next to the 
large tab of the regulator.

What is the expected output? What do you see instead?
Regulator should not be so warm

To allow the regulator to disipate more heat into the ground plane, scrape away 
the coating to expose the copper layer above the large tab of the regulator. 
Then solder the ground plane and allow it to flow to the large tab.

The regulator will run much cooler.

Expose Copper
<a href="http://www.flickr.com/photos/60192309@N05/6887966107/" 
title="2012-02-16_09-09-44_661 by chris1howell, on Flickr"><img 
src="http://farm8.staticflickr.com/7185/6887966107_7464d897c9_z.jpg" 
width="640" height="360"></a>

Solder to tab
<a href="http://www.flickr.com/photos/60192309@N05/6887959063/" 
title="2012-02-16_09-09-57_873 by chris1howell, on Flickr"><img 
src="http://farm8.staticflickr.com/7064/6887959063_e2dd245600_z.jpg" 
width="640" height="360"></a>

What steps will reproduce the problem?
Elapsed timer gone when charging is complete

What is the expected output? What do you see instead?
Elapsed Timer should stop counting up when charging is complete and continue to 
display the total elapsed time of the charge until the charge cable is 
unplugged.

SYMPTOMS/ENVIRONMENT:
When attempting to upload the open_evse.pde to an open-evse V4 board (from OSH 
PARK direct purchase) with the Arduino IDE and a USBtinyISP, the following 
avrdude error occurs:
"initialization failed, rc=-1"

ISSUE:
It appears that the "RST" trace from pin 5 of the ISP1 header (J1) to pin 1 of 
IC1 is missing.  This was evident in the board file: "Open EVSEv4.brd" and may 
have occurred because of the label mismatch (RST vs RESET) in the schematic: 
"Open EVSEv4.sch".

WORKAROUND:
After adding a jumper in place of the missing trace, upload was successful.

What steps will reproduce the problem?
1. Turn on EVSE with CLI enabled and LCD atttached, no HV
2. Verify LCD says "L1:12a"
3. In CLI change amps to 16, save. CLI doesn't change. Power cycling will show 
the new setting.

What is the expected output? What do you see instead?
LCD display of amp setting should change as it is changed in CLI.

What version of the product are you using? On what operating system?
1.0.3

Please provide any additional information below.

What steps will reproduce the problem?
1. Connect Smart ED to EVSE
2. Set EVSE on via RAPI "FE"
3. Set EVSE sleeping "FS"
4. Set EVSE on via RAPI "FE" within 60 sek

Smart ED LED on Charging Socket flasching red.
I think the problem is that the EVSE goes to status disabled and disconnects 
the reails.

What is the expected output? What do you see instead?

when EVSE is set to sleeping, don´t open the relais and set state to disabled. 
Sleeping means, that the it is possible to start the charging immediately.
Maybe it is useful to make a new Command on Rapi -> "Soft Stop"


What version of the product are you using? On what operating system?
OpenEVSE Plus DIY


Please provide any additional information below.

What steps will reproduce the problem?
1. Charge car.
2. Unplug car.
3. Note watts and cumulative watts.
4. Press button for sleep or menus.
5. Return from menus or sleep.

What is the expected output? What do you see instead?

Expected:
Don't know exactly, where's instructions? but guess that the last charge should 
go to zero while the cumulative increments by last amount.  Or last charge 
remains until next charge but doesn't get added to cumulative every time you 
press the button to initiate sleep or menus.

See:
Last charge remains and gets added to cumulative every time I enter and leave 
sleep or menus.

What version of the product are you using? V2.5, firmware 3.9.0

On what operating system? mac OSX

Please provide any additional information below.

The Tesla Roadster is sensitive to voltages on the lower end off the J1772 
State Voltages.

What steps will reproduce the problem?
1. Turn off any adafruit or i2c display defines (IOW, only anticipate CLI usage 
with no display)
2. Attempt to compile the code
3. g_psEnabled[] is not defined in any scope yet used in CLI::GetInput

I believe if one moves 

prog_char g_psEnabled[] PROGMEM = "enabled";
prog_char g_psDisabled[] PROGMEM = "disabled";

to AFTER
#endif // LCD16X2

but BEFORE
//-- end global variables

void EvseReset();

(sorry I didn't attach a diff; I'll git it into that later)