Releases: SwitchEV/RISE-V2G
Contains several issue fixes
1.2.6 Updated version number from 1.2.5 to 1.2.6
Correctly pausing and resuming a charging session
The mechanism of pausing and resuming a charging session was not working correctly previously. This release includes changes to several files for the EVCC and the SECC that finally implements a correctly running pause and resume. The necessary EVCC's session parameters are saved in the file EVCCConfig.properties. The SECC's session parameters are simply stored inside the session object, which will now not be destroyed upon pausing a charging session.
Have a look at the function isChargingLoopActive() in DummyEVController.java. There, you'll find a commented line
getCommSessionContext().setChargingSession(ChargingSessionType.PAUSE);
which you need to uncomment in order to test a charging pause that is triggered by the EVCC.
1.2.4
This release incorporates the latest pull requests as well as a bug fix related to reading PKCS#8 DER-encoded private key files (in particular: the moSubCA2.pkcs8.der file) with Java 1.8. Also, the SECC will now wait for 5 seconds after sending the final response message before closing the TCP/TLS socket connection. This way, the EVCC has enough time to process the incoming response and close the TCP/TLS beforehand.
See latest commit messages for further details.
(Make sure to use the latest generateCertificates.bat file - if you are using Windows - which was committed after this release!)
Fixes issue #20 and minor fixes after 8th Testing Symposium
After having attended the 8th ISO 15118 & CCS Testing Symposium (www.testing-symposium.net), I fixed some minor bugs (including issue #20 ) and added a few debugging messages. List of bug fixes:
- TargetCurrent in DummyEVController, used in PreChargeReq message, is now set to 2A to comply with IEC 61851-23
- The necessary change from State C to State B during a renegotiation in DC charging is now correctly implemented
- Added the EV setting "voltage.accuracy" to allow for a percentage of deviation from the target current in PreCharge
Fixes issues #18 and #19
Fix for release v1.2
Fix for previous release v1.2. Still missed one additional instantiation of MessageHandler in V2GCommuicationSessionHandlerSECC that needs to be removed.
Performance improvement (MessageHandler)
Improved the performance of RISE V2G by converting the MessageHandler into a Singleton. When instantiating the MessageHandler, the JAXB Context is set which is a pretty time-consuming task. Before the improvement, the MessageHandler was instantiated by the V2GCommunicationSessionHandlerSECC and the V2GCommunicationSessionHandlerSECC class.
Additionally, the MessageHandler was instantiated each time a new communication session was initiated by the EVCC.
Now, MessageHandler is initialized only once at startup of RISE V2G, saving a few seconds processing time on a slow embedded controller.
Credit goes to Advantics for pointing this out! Thanks. :)
Further changes: minor editorial edits and an additional logging message in the ConnectionHandler stating the length of the V2GTP payload as stated by the V2GTP header (helps for debugging purposes).
Maven build now works correctly
This release fixes issue #3 and introduces some slight changes as well:
- Changed package name from org.v2gclarity.risev2g to com.v2gclarity.risev2g
- Changed the names of all properties in the EVCCConfig.properties and SECCConfig.properties file to conform more to the Java style of properties.
- Changed pom.xml files and bin.xml files for Maven
- Added RISE-V2G-Parent project folder for Maven
Bugfix for SalesTariff digest creation
There was a bug when creating the signed SalesTariff in ChargeParameterDiscoveryRes. Before, the SalesTariff XML element was created with the MsgBody namespace, but now (as it is the correct way) it is created using the MsgDataTypes namespace.
Fixes issue #16.
EVCC fully standard compliant - Some minor changes
After having conducted another test of RISE V2G against the test system of VERISCO, I am happy to announce that RISE V2G is fully compliant with the ISO 15118 standard!
See also my blog entry http://v2g-clarity.com/en/blog/bulletproof-iso-15118-implementation-risev2g-tested-by-verisco-test-system/.
Also conducted some minor changes which can be found in the change log commit message of commit d8c9fc7.