-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start Transcation and get the error message of farmation violation #697
Comments
So the log is from the CS that is implemented with this library? |
Actually I am a sale and I dont know the code, but software works well.
Ali Al-Alak ***@***.***> 于2024年12月17日周二 05:23写道:
… So the log is from the CS that is implemented with this library?
What software is running on the CP and are we sure that works properly?
Based on the log the BootNotification response seems correctly formatted.
—
Reply to this email directly, view it on GitHub
<#697 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BNX2G3TAUMGVF24OIPS264D2F5AD5AVCNFSM6AAAAABTWOOPHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBWHAYTQOJRGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Have you tested with other CSMS software? |
we can connect with othet CSMS software, only this software we can't connect
Ali Al-Alak ***@***.***> 于 2024年12月17日周二 下午4:20写道:
… Have you tested with other CSMS software?
It does not seem that anything is wrong with this package nor your
implementation of it (based only on the logs of course).
—
Reply to this email directly, view it on GitHub
<#697 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BNX2G3WLNHGBIGTUYPL3MZ32F7NDJAVCNFSM6AAAAABTWOOPHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXG43TINRRGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
and here is the new log of today's connection attempt from their server
today. I also attached the log from our side as an image below
{"export": true, "action": "default_action", "app": "cp", "cp": "xZLQKgJQ",
"error": "ConnectionClosedOK(Close(code=1000, reason=''), Close(code=1000,
reason=''), True)", "event": "Connection Closed", "timestamp":
"2024-12-17T09:29:47.995758Z", "lineno": 690, "pathname":
"/app/controller/ChargePoint.py"}
{"export": true, "action": "default_action", "app": "cp", "cp": "xZLQKgJQ",
"event": "Connection Disposed", "timestamp": "2024-12-17T09:29:48.031477Z",
"lineno": 680, "pathname": "/app/controller/ChargePoint.py"}
{"export": false, "action": "default_action", "app": "cp", "event": "Charge
point xZLQKgJQ connected", "timestamp": "2024-12-17T09:29:48.714010Z",
"lineno": 48, "pathname": "/app/central_cp.py"}
INFO:ocpp:xZLQKgJQ: receive message
[2,"eb81347f-e1ce-42ee-b089-2fc4e002790e","BootNotification",{"chargePointVendor":"SimpleCharge","chargePointModel":"MultiSocketCharger","chargePointSerialNumber":"24250232","firmwareVersion":"1.24.0819.WL","iccid":"","imsi":""}]
{"export": true, "action": "default_action", "app": "cp", "cp": "xZLQKgJQ",
"charge_point_vendor": "SimpleCharge", "charge_point_model":
"MultiSocketCharger", "charge_point_serial_number": "24250232",
"firmware_version": "1.24.0819.WL", "iccid": "", "imsi": "", "event":
"BootNotification", "timestamp": "2024-12-17T09:29:49.163567Z", "lineno":
53, "pathname": "/app/controller/ChargePoint.py"}
INFO:ocpp:xZLQKgJQ: send
[3,"eb81347f-e1ce-42ee-b089-2fc4e002790e",{"currentTime":"2024-12-17T15:29:49.163Z","interval":60,"status":"Accepted"}]
INFO:ocpp:xZLQKgJQ: receive message
[4,"eb81347f-e1ce-42ee-b089-2fc4e002790e","FormationViolation","Unable to
process action",{}]
Ali Al-Alak ***@***.***> 于 2024年12月17日周二 下午4:20写道:
… Have you tested with other CSMS software?
It does not seem that anything is wrong with this package nor your
implementation of it (based only on the logs of course).
—
Reply to this email directly, view it on GitHub
<#697 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BNX2G3WLNHGBIGTUYPL3MZ32F7NDJAVCNFSM6AAAAABTWOOPHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXG43TINRRGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Your devs need to look at the stacktrace and confirm the underlying exception, but I expect it is because the string is not being encoded according to the JSON standard see https://docs.python.org/3/library/json.html#json.loads |
we are a charger company, so do you mean our clients who are operating the
platform should correct their code of their platform?
drc38 ***@***.***> 于 2024年12月18日周三 上午3:44写道:
… Your devs need to look at the stacktrace and confirm the underlying
exception, but I expect it is because the string is not being encoding
according to the JSON standard see
https://docs.python.org/3/library/json.html#json.loads
—
Reply to this email directly, view it on GitHub
<#697 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BNX2G3WNUI3IVRJ26DHNQH32GB5JVAVCNFSM6AAAAABTWOOPHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBZGQ2TSNJRGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
First, thanks for your great work, We are a charger company and we cannot connect with clients server, the log they sent is below.
INFO:websockets.server:connection open
{"export": false, "action": "default_action", "app": "cp", "event": "Protocols Matched: ocpp1.6", "timestamp": "2024-12-06T07:44:35.343238Z", "lineno": 29, "pathname": "/app/central_cp.py"}
{"export": false, "action": "default_action", "app": "cp", "event": "Charge point xZLQKgJQ connected", "timestamp": "2024-12-06T07:44:35.343863Z", "lineno": 45, "pathname": "/app/central_cp.py"}
INFO:ocpp:xZLQKgJQ: receive message [2,"dabbadd0-3b86-48a0-9c11-8de787bab0ac","BootNotification",{"chargePointVendor":"SimpleCharge","chargePointModel":"MultiSocketCharger","chargePointSerialNumber":"24250139","firmwareVersion":"1.24.0819.WL","iccid":"","imsi":""}]
{"export": true, "action": "default_action", "app": "cp", "cp": "xZLQKgJQ", "charge_point_vendor": "SimpleCharge", "charge_point_model": "MultiSocketCharger", "charge_point_serial_number": "24250139", "firmware_version": "1.24.0819.WL", "iccid": "", "imsi": "", "event": "BootNotification", "timestamp": "2024-12-06T07:44:36.083071Z", "lineno": 55, "pathname": "/app/controller/ChargePoint.py"}
INFO:ocpp:xZLQKgJQ: send [3,"dabbadd0-3b86-48a0-9c11-8de787bab0ac",{"currentTime":"2024-12-06T13:44:36.083Z","interval":60,"status":"Accepted"}]
INFO:ocpp:xZLQKgJQ: receive message [4,"dabbadd0-3b86-48a0-9c11-8de787bab0ac","FormationViolation","Unable to process action",{}]
The text was updated successfully, but these errors were encountered: