Comments (1)
Hello,
I just tested this and it didn't throw any validation errors at all:
func test(chargePointID string) {
cProfile := types.ChargingProfile{}
cProfile.ChargingProfileId = 1
cProfile.StackLevel = 0
cProfile.ChargingProfilePurpose = types.ChargingProfilePurposeChargePointMaxProfile
cProfile.ChargingProfileKind = types.ChargingProfileKindAbsolute
phases := 3
cProfile.ChargingSchedule = types.NewChargingSchedule(types.ChargingRateUnitAmperes,
types.ChargingSchedulePeriod{
StartPeriod: 0,
Limit: float64(10),
NumberPhases: &phases,
})
err := centralSystem.SetChargingProfile(chargePointID, func(confirmation *smartcharging.SetChargingProfileConfirmation, err error) {
if err != nil {
logDefault(chargePointID, smartcharging.SetChargingProfileFeatureName).Errorf("error on request: %v", err)
} else {
logDefault(chargePointID, smartcharging.SetChargingProfileFeatureName).Infof("status: %v", confirmation.Status)
}
}, 0, &cProfile)
if err != nil {
fmt.Println(err)
}
}
Is the error being returned on CSMS side or by the charging station? Also, can you confirm what error is being returned specifically?
from ocpp-go.
Related Issues (20)
- Fix vet report HOT 2
- Issue with DataTransfer on both ocpp 1.6 and 2.0.1 HOT 2
- Send Command To Charging Station
- I call remote start transaction but got error "ocpp message (2193907606): InternalError - An internal error occurred and the receiver was not able to process the requested Action successfully" HOT 1
- SecurityEventNotification.req HOT 13
- Decouple websocket server and message processing HOT 7
- Parses an OCPP-J message,Occurrence anomaly HOT 4
- Is their any way to bypass the SubjectAlternateName check while using tls? HOT 1
- Fetch chargePointId inside SetBasichandler HOT 6
- Fetch raw ocpp message HOT 4
- Bug with validation for connectorId of GetCompositeSchedule.conf #275
- shoudl idTag validator be altered? HOT 3
- Configurable session timeout HOT 1
- Authorize request missing connectorId? HOT 4
- Websocket Disconnect Handler not called HOT 1
- [中文] help! websocket write: broken pipe, and ws.cleanupConnection() Unlock() not work HOT 1
- [ENG] help! websocket write: broken pipe, and ws.cleanupConnection() Unlock() not work HOT 3
- ocpp16.ChargePointConnectionHandler unreliable or racy HOT 6
- Question on error handling
- CS confuses error responses between requests in case of timeout HOT 11
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ocpp-go.