-
Notifications
You must be signed in to change notification settings - Fork 161
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
RAPI Command Serial Numbers #143
Comments
IMHO, this info should be handled by the WiFi module. The EVSEs aren't involved in OCPP at all. You should just use the MAC address as the serial number. |
OCPP requires the serial number for the station, connector and energy
meter.
The energy meter is physically built into the controller and should have a
serial number even if there is no WiFi or OCPP. It does not make sense to
store this number on WiFi when the hardware is physically on the controller.
The connector serial number should also be burned to the controller, again
the charge connector is physically part of the controller should have a
serial number even if there is no WiFi or OCPP.
The chassis serial number is arbitrary and can be store wherever. But every
station chassis should have a serial number even if it does not have WiFi.
…On Sat, Oct 2, 2021, 7:42 PM lincomatic ***@***.***> wrote:
IMHO, this info should be handled by the WiFi module. The EVSEs aren't
involved in OCPP at all. You should just use the MAC address as the serial
number.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#143 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN5QH52VDQVWHWWAUF7QU3UE6KFXANCNFSM5ET6YMQA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
FYI, the ATMEGA 328 may has a unique ID we can use: https://www.thethingsnetwork.org/forum/t/arduino-has-a-unique-id/21415 |
I looked into this... interesting idea. The first 6 bytes are ASCII, followed by 4 hex bytes. It's guaranteed to be unique only in the 328PB, but some people are using it, anyway. In the 328P, the first of the hex bytes is always FF |
There's a library for this: https://github.com/ricaun/ArduinoUniqueID |
Will give it a go on the boards I have, but that being said I believe the primary focus of this is new boards so I would assume we can build these with the 328PB @chris1howell ? |
The PB is functionally identical. The pinouts are almost identical, but therre's a pin or two that need to be strapped. Also, you need to either get a newer copy of avrdude, or modify the config to work w/ its chip id, which is different. the PB is generally cheaper, BTW. I'll upload code in a bit.. implemented a $GI command to get the ID |
In #144 I have a config that builds with the latest Arduino will see which avrdude is used. |
code with $GI |
Gave this a try |
Oops, sorry about that. I just pushed a fix that changed it from $SI to $GI. Glad that it's giving different values on different boards. I guess the question is how unique they really are. Anyway, let's just try using this for now. |
Sorry, I just noticed that the response is echoing the command in your examples above.. it shouldn't be responding $OK $GI. |
RAPI command to SET and GET Serial Numbers required by OCPP.
station chassis
connector
meter
Proposed format
SET command write once only if EEPROM serial numbers are blank. EEPROM could also be written directly with programmer.
$SS station connector meter
GET
$GS
$OK station connector meter
The text was updated successfully, but these errors were encountered: