Bluesky AC EV Charging
Bluesky AC EV Charging
0
Project description

π Overview
Bluesky AC EV Charging / OCPP 보λλ μ κΈ°μ°¨ μμ μΆ©μ κΈ°μ μ μ Ethernet, Wi-Fi, Bluetooth, 4G ν΅μ κΈ°λ₯κ³Ό OCPP 1.6 κΈ°λ° μ€μ κ΄μ μ°λ κΈ°λ₯μ κ²°ν©ν ν΅μ νλ«νΌμ λλ€. μ΄ μ νμ μΆ©μ κΈ° μ€μΉ μ΄ν νμν λ€νΈμν¬ μ€μ , μλ² μ°κ²°, μν λͺ¨λν°λ§, νμ¨μ΄ μ λ°μ΄νΈκΉμ§ νλμ μ΄μ νλ¦μΌλ‘ κ΄λ¦¬ν μ μλλ‘ μ€κ³λ κ²μ΄ νΉμ§μ λλ€. νΉν νμ₯μμλ μ±μ΄λ λ‘컬 μ€μ λκ΅¬λ‘ μμ½κ² λ€νΈμν¬λ₯Ό ꡬμ±ν μ μκ³ , μ΄μ μΈ‘λ©΄μμλ OCPP κΈ°λ°μΌλ‘ μ€μ μμ€ν κ³Ό μ°λν΄ μΆ©μ κΈ° μνλ₯Ό μμ μ μΌλ‘ κ΄λ¦¬ν μ μμ΄, μμ© μΆ©μ μΈνλΌμ μ ν©ν ꡬ쑰λ₯Ό 보μ¬μ€λλ€.
π Company
https://cnevcharger.com/about-us/

Bluesky(Wenzhou Bluesky Energy Technology Co., Ltd.)λ μ€κ΅ μ μ₯μ± μμ μ°μ λ³Έμ¬λ₯Ό λ μλμ§ μ₯λΉ μ μ‘° κΈ°μ μΌλ‘, 1997λ μ μ€λ¦½λμ΄ 20λ μ΄μ μ°λ£ μ€λΉ λ° μλμ§ κ³μΈ‘ μ₯λΉ λΆμΌμμ μ¬μ μ μ΄μ΄μ¨ κΈ°μ μ λλ€.
μ΄κΈ°μλ μ£Όμ κΈ° μ μ΄ μμ€ν κ³Ό μ°λ£ κ΄λ¦¬ μ루μ μ μ€μ¬μΌλ‘ μ±μ₯νμΌλ©°, νμ¬λ AC/DC μ κΈ°μ°¨ μΆ©μ κΈ°, μΆ©μ μ κ΄λ¦¬ μμ€ν , μ± κΈ°λ° μ΄μ μ루μ κΉμ§ μ 곡νλ EV μΆ©μ μΈνλΌ ν΅ν© μ루μ κΈ°μ μΌλ‘ μ¬μ μμμ νμ₯νμ΅λλ€.
κΈλ‘λ² μμ₯μμλ 30κ°κ΅ μ΄μμ μ νμ 곡κΈνλ©° λ€μν μΈμ¦μ ν보νκ³ μμΌλ©°, μ€κ³λΆν° μμ°, μ€μΉ, μ μ§λ³΄μκΉμ§ μ§μνλ ν΄ν€(End-to-End) κ³΅κΈ μλμ κ°μΆ κ²μ΄ νΉμ§μ λλ€.
π Features
1. OCPP 1.6 κΈ°λ° μ€μ κ΄μ μ°λ
μΆ©μ κΈ°μ μ€μ κ΄λ¦¬ μμ€ν
κ° νμ€ ν΅μ μ μ§μνλ ꡬ쑰μ
λλ€. κ³΅κ° μλ£μμλ μΆ©μ μ ν΄λΌμ΄μΈνΈμ μλ²λ₯Ό ꡬμ±νκ³ , SteVe μλ² + WebSocketμΌλ‘ μλ¨ μ°κ²°κ³Ό heartbeat κΈ°λ° μν νμΈμ ꡬννλ€κ³ μ€λͺ
ν©λλ€.
2. λ€μ€ μ€μ κ²½λ‘ μ 곡: 485 / Bluetooth / λͺ¨λ°μΌ μ±
μ€μ λ°©μμ΄ ν κ°μ§μ λ¬Άμ¬ μμ§ μμ΅λλ€. κ³΅κ° μλ£ κΈ°μ€μΌλ‘ 485 ν΄, Bluetooth ν΄, μ€λ§νΈν° μ± Bluetooth μ°κ²°μ 3κ° κ²½λ‘κ° μ 곡λμ΄ μ€μΉ νμ₯κ³Ό μ μ§λ³΄μ μν©μ λ°λΌ μ μ°νκ² μ κ·Όν μ μμ΅λλ€.
3. μ± κΈ°λ° Wi-Fi λ° OCPP νλΌλ―Έν° μ€μ
Wow Charger μ±μΌλ‘ μΆ©μ κΈ°μ μ°κ²°ν λ€ Wi-Fi SSID/λΉλ°λ²νΈ μ
λ ₯, OCPP μλ² νλΌλ―Έν° μ
λ ₯κΉμ§ κ°λ₯νλ€κ³ μλ΄ν©λλ€. μ΄λ μ€μΉ κΈ°μ¬ μμ΄λ νμ₯ μ€μ μΌλΆλ₯Ό μ¬μ©μ λλ μ΄μμκ° μνν μ μκ² ν΄ μ€λλ€.
4. λ‘컬 λ° μ¨λΌμΈ νμ¨μ΄ μ
κ·Έλ μ΄λ μ§μ
κ³΅κ° μλ£μ λ‘컬 μ
κ·Έλ μ΄λλ 485 μλ¦¬μΌ ν¬νΈ ν΄μ μ¬μ©νκ³ , μ¨λΌμΈ μ
κ·Έλ μ΄λλ νλ«νΌ μ
λ°μ΄νΈ λλ FTP κΈ°λ° νλ‘κ·Έλ¨ μ μ‘μΌλ‘ μ€λͺ
λ©λλ€. λ³λ OCPP 보λ μ
λ°μ΄νΈ μ μ°¨λ μ 곡λμ΄, νλ μ μ§λ³΄μ κ΄μ μμ μ νν μμ€μ μ΄μμ±μ λ³΄μ¬ μ€λλ€.
5. μμ© μ ν μμ€μ μ€μΉΒ·μ‘°λ¦½ λ¬Έμν
CDZ-E λͺ¨λΈ μ€μΉ κΈμλ κΈ°ν, λμ€νλ μ΄, μΉ΄λ 리λ, λ°©μ μ‘°μΈνΈ, λΉμμ μ§ λ²νΌ, μΌμ΄λΈ κ³ μ λ± λ°λ³΅ μμ°κ³Ό νμ₯ 쑰립μ μ μ λ‘ ν μ€λͺ
μ΄ ν¬ν¨λ©λλ€. μ΄λ λ¨μ μμ ν보λ€λ μ νν μλλ₯Ό κ°μ§ κ΅¬μ‘°λ‘ ν΄μν μ μμ΅λλ€.
π Role and Application of the WIZnet's Chip



https://cnevcharger.com/bluesky-ac-ev-charging-explained
μ¬μ©λ WIZnet μΉ©: W5500
- κ³΅κ° μλ£μ μ€λ₯ μ½λ λͺ©λ‘μ **β0xB9 W5500 mac failureβ**κ° μ§μ κΈ°μ¬λμ΄ μμ΅λλ€. μ΄ ννμ ν΄λΉ μΆ©μ κΈ° 보λ λλ κ΄λ ¨ λ€νΈμν¬ λ³΄λμμ WIZnet W5500μ΄ μ€μ λ‘ μ¬μ©λκ³ μμμ λ³΄μ¬ μ£Όλ κ°μ₯ μ§μ μ μΈ κ³΅κ° κ·Όκ±°μ λλ€.
λ€νΈμν¬μμμ μν
- W5500μ Hardwired TCP/IP κΈ°λ° Ethernet 컨νΈλ‘€λ¬λ‘, SPIλ‘ MCUμ μ°κ²°λμ΄ TCP/UDP/IPv4 κΈ°λ° μ μ λ€νΈμν¬ μ°κ²°μ λ΄λΉν©λλ€. μ΄ νλ‘μ νΈ λ§₯λ½μμλ μΆ©μ κΈ°κ° μ€μ OCPP μλ²μ ν΅μ ν λ νμν κΈ°λ³Έ TCP μ°κ²° κ³μΈ΅μ μμ μ μΌλ‘ μ 곡νλ μν λ‘ ν΄μνλ κ²μ΄ ν©λ¦¬μ μ λλ€. WebSocketκ³Ό OCPP μ ν리μΌμ΄μ κ³μΈ΅μ MCU λλ μμ μννΈμ¨μ΄κ° μ²λ¦¬νκ³ , W5500μ κ·Έ μλμ Ethernet/TCP μ μ‘ κΈ°λ°μ λ΄λΉν©λλ€.

π Market & Application Value

(by ChatGPT)
μ μ© μ°μ
λ° μμ₯
μ΄ νλ‘μ νΈλ λͺ
ννκ² EV μΆ©μ μΈνλΌ μμ₯μ 겨λ₯ν©λλ€. IEAμ λ°λ₯΄λ©΄ 2024λ
μ μΈκ³ μ κΈ°μ°¨ νλ§€λ 1,700λ§ λλ₯Ό μ΄κ³Όνκ³ , μ μ°¨ νλ§€μ 20% μ΄μμ μ°¨μ§νμ΅λλ€. μ΄λ μΆ©μ κΈ° νλμ¨μ΄, κ΄μ μννΈμ¨μ΄, μ격 μ μ§λ³΄μ μΈνλΌμ λν μμκ° κ³μ 컀μ§κ³ μμμ μλ―Έν©λλ€.
ꡬ맀 주체
κ°μ₯ νμ€μ μΈ κ΅¬λ§€ 주체λ μΆ©μ κΈ° μ μ‘°μ¬(OEM/ODM), μΆ©μ μ¬μ
μ(CPO), μμ
μ© κ±΄λ¬Ό/μ£Όμ°¨μ₯ μ΄μμ¬, 곡곡 μΆ©μ μΈνλΌ κ΅¬μΆ μ¬μ
μμ
λλ€. μ±μ μμ
μ© λ²μ μ΄ μ격 λͺ¨λν°λ§, κ²°μ , ν΅κ³ κΈ°λ₯μ κ°μ‘°νκ³ μμ΄ B2Cλ³΄λ€ B2B/B2B2C μμ₯ μ ν©μ±μ΄ λμ΅λλ€.
κ²½μλ ₯
μ΄ μ¬λ‘μ κ²½μλ ₯μ μ΄κ³ μ μΆ©μ μ±λ₯μ΄ μλλΌ, νμ€ κΈ°λ° μ°λμ± + μ΄μ νΈμμ± + λ€μ€ ν΅μ κ²½λ‘μ μμ΅λλ€. OCAλ OCPPμ ν΅μ¬ κ°μΉκ° λ²€λμ 무κ΄νκ² μ€μ μμ€ν
κ³Ό μΆ©μ κΈ°λ₯Ό μ°κ²°νλ λ° μλ€κ³ μ€λͺ
ν©λλ€. μ¦, νΉμ μ¬μ
μ μ’
μμ μ€μ΄κ³ ν νλ«νΌ μ°λ κ°λ₯μ±μ λμΈλ€λ μ μ΄ μμ© μμ₯μμ μ€μν©λλ€.
μμ₯μ± νλ¨
μμ₯μ±μ λμ νΈμΌλ‘ νλ¨λ©λλ€. λ€λ§ μ°¨λ³νμ μ΄μ μ μΆ©μ μ±λ₯λ³΄λ€ μ΄μΒ·μ μ§λ³΄μ ν¨μ¨μ μμ΅λλ€. μμ AC μΆ©μ κΈ° μμ₯μ κ²½μμ΄ μΉμ΄νμ§λ§, OCPP, μ± μ€μ , μ격 μ
κ·Έλ μ΄λ, μ μ /무μ νΌν© ν΅μ μ μμ μ μΌλ‘ μ 곡νλ μ νμ μμ
μ© νμ₯μμ μ¬μ ν μ ν¨ν©λλ€.
π External Indicators
1. κ³΅κ° μλ£μ μκ³Ό μ°μμ±
cnevcharger.comμλ λ³Έ νλ‘μ νΈμ μ§μ μ°κ²°λλ μ€μΉ, λ€νΈμνΉ, OCPP, μ± μ€μ , μ
λ°μ΄νΈ λ¬Έμκ° λ€μ κ²μλμ΄ μμ΅λλ€. μ΄λ μΌνμ± νλ³΄λ¬Όμ΄ μλλΌ μ§μ μ΄μ μ€μΈ μ νκ΅° λ¬Έμν νλμΌλ‘ λ³Ό μ μμ΅λλ€. λ€λ§ λλΆλΆμ΄ μ μ‘°μ¬ μ체 κ²μλ¬Όμ΄λΌλ μ μμ λ
립μ μΈλΆ κ²μ¦ κ°λλ λμ§ μμ΅λλ€.
https://cnevcharger.com/bluesky-ac-ev-charging-explained/
2. Youtube
κ²μ κ²°κ³Ό κΈ°μ€μΌλ‘ Bluesky κ΄λ ¨ OCPP μ€λͺ
μμμ μ½ 7.7K μ‘°νμ, μ±λμ μ½ 12.5K~12.6K ꡬλ
μ μμ€μΌλ‘ νμΈλ©λλ€. λν βEV Charger connects to Bluesky CMS via OCPP 1.6Jβ μμμ μ½ 914 μ‘°νμλ‘ λ
ΈμΆλ©λλ€. λν μ€νμμ€ νλ‘μ νΈ μμ€μ νκΈλ ₯μ μλμ§λ§, μ ν μ΄μΒ·μ€μ ν μ½ν
μΈ λ‘μλ μΌμ ν κ΄μ¬μ λ°μλ€κ³ λ³Ό μ μμ΅λλ€.

3. μ€νμμ€ μ°κ³μ±
μ΄ νλ‘μ νΈκ° μ°Έμ‘°ν SteVe OCPP μλ²λ GitHub κΈ°μ€ μ½ 1,016 stars, 466 forks, 69 open issues, 18 pull requests, μ‘°μ§ νλ‘μ 57λͺ
μΌλ‘ νμΈλ©λλ€. μ¦, λ³Έ νλ‘μ νΈ μ체μ GitHub μ μ₯μλ νμ¬ κ³΅κ° μλ£ κΈ°μ€μΌλ‘ νμΈλμ§ μμ§λ§, μ°λ λμμΌλ‘ μ νν μλ²λ EV μΆ©μ μ
κ³μμ μ€μ νμ©λλ μ€νμμ€ κΈ°λ°μ κ°κ³ μμ΅λλ€.
https://github.com/steve-community/steve
4. μ
κ³ νμ€μ±κ³Ό μΈλΆ νμ° κ°λ₯μ±
OCAλ OCPP 1.6μ΄ μ μΈκ³ CS/CSMS μ μ‘°μ¬μ λ리 ꡬνλλ€κ³ μ€λͺ
ν©λλ€. λ°λΌμ μ΄ νλ‘μ νΈλ νΉμ μ¬λ΄ νλ‘ν μ½ μ¬λ‘κ° μλλΌ, νμ°μ±μ΄ λμ κ³΅κ° νμ€ μμ₯μ λ§μΆ° μ€κ³λ μ μμ μΈλΆ κ°μΉκ° μμ΅λλ€.
https://openchargealliance.org/protocols/ocpp-protocols/ocpp-1-6/
π WIZnet Strategic Value
WIZnet Maker μνκ³ κ΄μ μ μλ―Έ
μ΄ UCCλ WIZnet μΉ©μ΄ λ¨μ μΌμ λ
Έλλ TCP μλ² λ°λͺ¨λ₯Ό λμ΄μ, μ°μ
μ©Β·μλΉμ€ν μ₯λΉμ λ€νΈμν¬ λ°±λ³ΈμΌλ‘ μ¬μ©λ μ μμμ λ³΄μ¬ μ€λλ€. EV μΆ©μ κΈ°λ ν΅μ μ₯μ κ° κ³§ μλΉμ€ μ₯μ μ λ§€μΆ μμ€λ‘ μ΄μ΄μ§ μ μλ μ₯λΉμ΄κΈ° λλ¬Έμ, μ΄ λΆμΌ μ¬λ‘λ Maker μνκ³λ³΄λ€λ μ€μ μ°μ
μ μ© λ νΌλ°μ€λ‘μ μλ―Έκ° ν½λλ€.
μ μ¬ νλ‘μ νΈ νμ₯ κ°λ₯μ±
μ μ¬ νμ₯ λΆμΌλ‘λ μλμ§ μ μ₯μ₯μΉ(ESS) ν΅μ κ²μ΄νΈμ¨μ΄, μ°μ
μ© μΆ©μ μ€λΉ, μ€λ§νΈ μ£Όμ°¨Β·κ³ΌκΈ λ¨λ§, λΉλ© μλμ§ κ΄λ¦¬μ© OCPP/OCPI μ°κ³ μ₯λΉκ° μμ΅λλ€. λ€λ§ OCPI, ISO 15118, 보μ μΈμ¦, κ΅κ°λ³ κ³λΒ·κ²°μ κ·μ λμκΉμ§ ν¬ν¨ν νμ₯μ νμ¬ κ³΅κ° μλ£ κΈ°μ€μΌλ‘ νμΈλμ§ μμΌλ―λ‘, ν₯ν μ ν μ λ΅ κ³Όμ λ‘ λ³΄λ κ²μ΄ μ μ ν©λλ€.
π Summary
λ³Έ UCCλ WIZnet W5500 κΈ°λ° μ μ Ethernet ν΅μ μ ν¬ν¨ν EV μΆ©μ κΈ° μμ€ν μ΄ μ€μ μ°μ νκ²½μμ μ΄λ»κ² νμ©λ μ μλμ§λ₯Ό 보μ¬μ£Όλ μ¬λ‘μ λλ€. λ¨μν λ€νΈμν¬ μ°κ²°μ λμ΄, OCPP 1.6 νμ€μ κΈ°λ°μΌλ‘ μ€μ κ΄μ μμ€ν κ³Ό μ°λνκ³ , μ± λ° λ‘컬 μ€μ λꡬλ₯Ό ν΅ν΄ μ€μΉμ μ΄μ, μ μ§λ³΄μλ₯Ό ν΅ν©μ μΌλ‘ μ§μνλ ꡬ쑰λ₯Ό κ°μΆκ³ μμ΅λλ€.
νΉν λ€μ€ ν΅μ μΈν°νμ΄μ€μ μ격 κ΄λ¦¬ κΈ°λ₯μ κ²°ν©ν¨μΌλ‘μ¨, μΆ©μ κΈ° μ΄μμ μμ μ±κ³Ό ν¨μ¨μ±μ λμμ ν보νλ €λ μ€κ³κ° λ보μ λλ€. μ΄λ WIZnet μΉ©μ΄ μ°μ μ© μλΉμ€ μ₯λΉμμλ μ λ’°μ± μλ λ€νΈμν¬ μΈνλΌλ‘ νμ©λ μ μμμ 보μ¬μ£Όλ μ€μ§μ μΈ μ μ© μ¬λ‘μ΄λ©°, ν₯ν μλμ§ λ° μΈνλΌ μ₯λΉ λΆμΌλ‘μ νμ₯ κ°λ₯μ± λν νμΈν μ μμ΅λλ€.
π FAQ
Q1. Bluesky AC EV Charging μμ€ν
μ μ΄λ€ κΈ°λ₯μ μ 곡νλμ?
Bluesky AC EV Charging μμ€ν
μ μ μ Ethernet, Wi-Fi, Bluetooth, 4G ν΅μ μ μ§μνλ©°, OCPP 1.6 κΈ°λ°μΌλ‘ μ€μ κ΄μ μμ€ν
κ³Ό μ°λλ©λλ€. μ΄λ₯Ό ν΅ν΄ μΆ©μ κΈ° μν λͺ¨λν°λ§, μ격 μ μ΄, λ°μ΄ν° κ΄λ¦¬κ° κ°λ₯ν©λλ€.
Q2. OCPP 1.6μ μΆ©μ κΈ°μμ μ΄λ€ μν μ νλμ?
OCPP 1.6μ μΆ©μ κΈ°μ μ€μ μλ² κ° νμ€ ν΅μ νλ‘ν μ½λ‘, WebSocket κΈ°λ° μ°κ²°μ ν΅ν΄ μν μ 보, μΆ©μ μΈμ
, μΈμ¦ λ±μ λ°μ΄ν°λ₯Ό κ΅ννλ©° μμ μ μΈ μ격 μ΄μμ μ§μν©λλ€.
Q3. μΆ©μ κΈ°μ Wi-Fi μ€μ μ μ΄λ»κ² ꡬμ±νλμ?
Wow Charger μ±μ ν΅ν΄ Bluetoothλ‘ μΆ©μ κΈ°μ μ°κ²°ν ν, Wi-Fi SSIDμ λΉλ°λ²νΈλ₯Ό μ
λ ₯νμ¬ κ°νΈνκ² μ€μ ν μ μμ΅λλ€.
Q4. OCPP μλ² μ°κ²° μ€μ μ μ΄λ»κ² μ§νλλμ?
μ± λλ μ€μ λꡬμμ OCPP μλ² URL, ν¬νΈ, μΆ©μ κΈ° ID λ±μ νλΌλ―Έν°λ₯Ό μ
λ ₯νμ¬ μ€μ νλ©°, μ΄ν WebSocketμ ν΅ν΄ μλ²μ μ°κ²°λ©λλ€.
Q5. μΆ©μ κΈ° νμ¨μ΄ μ
λ°μ΄νΈλ μ΄λ€ λ°©μμΌλ‘ μ΄λ£¨μ΄μ§λμ?
νμ¨μ΄ μ
λ°μ΄νΈλ λ‘컬(485 μλ¦¬μΌ ν΄ μ¬μ©) λλ μ격(νλ«νΌ/FTP κΈ°λ°) λ°©μμΌλ‘ μνν μ μμ΄ μ μ§λ³΄μκ° μ©μ΄ν©λλ€.
Q6. OCPP 보λ νλ‘κ·Έλ¨ μ
λ°μ΄νΈλ μ΄λ»κ² νλμ?
μ μ© μ
λ°μ΄νΈ λꡬλ₯Ό μ¬μ©ν΄ 보λμ νλ‘κ·Έλ¨μ μ
λ‘λνλ©°, μ°κ²° μν νμΈ λ° λ¨κ³λ³ μ
λ‘λ μ μ°¨λ₯Ό λ°λΌ μ§νν©λλ€.
Q7. μΆ©μ κΈ° μ€μΉ μ μ£Όμ κ΅¬μ± μμλ 무μμΈκ°μ?
μ€μΉ κ³Όμ μλ λ©μΈλ³΄λ, λμ€νλ μ΄, μΉ΄λ 리λκΈ°, λΉμ μ μ§ λ²νΌ, λ°©μ 컀λ₯ν°, μΌμ΄λΈ κ³ μ μ₯μΉ λ±μ΄ ν¬ν¨λ©λλ€.
Q8. μΆ©μ κΈ°μ μλ² κ° ν΅μ μ μ΄λ»κ² μ μ§λλμ?
Heartbeat λ©μμ§λ₯Ό μ£ΌκΈ°μ μΌλ‘ κ΅ννμ¬ μ°κ²° μνλ₯Ό νμΈνλ©°, μ΄λ₯Ό ν΅ν΄ μλ²λ μΆ©μ κΈ°μ μ¨λΌμΈ μνλ₯Ό μ§μμ μΌλ‘ λͺ¨λν°λ§ν©λλ€.
Q9. WIZnet W5500 μΉ©μ μ΄λ€ μν μ νλμ?
W5500μ TCP/IP κΈ°λ° Ethernet ν΅μ μ λ΄λΉνλ μΉ©μΌλ‘, μΆ©μ κΈ°μ OCPP μλ² κ° μμ μ μΈ μ μ λ€νΈμν¬ μ°κ²°μ μ 곡ν©λλ€.
Q10. μ΄ μμ€ν
μ μ΄λ€ νκ²½μ μ ν©νκ°μ?
μμ
μ© μ£Όμ°¨μ₯, 곡곡 μΆ©μ μΈνλΌ, μΆ©μ μ¬μ
μ(CPO) νκ²½ λ±μμ μμ μ μΈ μ΄μκ³Ό μ€μ κ΄μ κ° νμν κ²½μ°μ μ ν©ν©λλ€.
π Overview
The Bluesky AC EV Charging / OCPP board is a communication platform that integrates wired Ethernet, Wi-Fi, Bluetooth, and 4G connectivity with OCPP 1.6-based central management integration for AC EV chargers. This product is designed to manage the entire operational flowβfrom network configuration and server connection to status monitoring and firmware updatesβafter charger installation. In particular, on-site network setup can be easily performed using an app or local configuration tools, while from an operational perspective, the charger status can be reliably managed through integration with a central system based on OCPP, making it well-suited for commercial charging infrastructure.
π Company
https://cnevcharger.com/about-us/

Bluesky (Wenzhou Bluesky Energy Technology Co., Ltd.) is an energy equipment manufacturer headquartered in Wenzhou, Zhejiang Province, China. Established in 1997, the company has over 20 years of experience in the fields of fuel equipment and energy metering devices.
Initially, the company grew by focusing on fuel dispenser control systems and fuel management solutions. It has since expanded its business into a comprehensive EV charging infrastructure solution provider, offering AC/DC EV chargers, charging station management systems, and app-based operational solutions.
In the global market, Bluesky supplies products to more than 30 countries and has obtained various certifications. It is characterized by its turnkey (end-to-end) capabilities, supporting everything from design and manufacturing to installation and maintenance.
π Features
- OCPP 1.6-based Central Management Integration
This structure supports standard communication between the charger and the central management system. According to publicly available materials, it is described that both the charging station client and server are configured, and a bidirectional connection along with heartbeat-based status monitoring is implemented using a SteVe server and WebSocket. - Multiple Configuration Paths: RS-485 / Bluetooth / Mobile App
The configuration method is not limited to a single approach. Based on public information, three configuration paths are provided: an RS-485 tool, a Bluetooth tool, and a smartphone app via Bluetooth connection, allowing flexible access depending on installation and maintenance scenarios. - App-based Wi-Fi and OCPP Parameter Configuration
After connecting to the charger via the Wow Charger app, users can input Wi-Fi SSID/password and configure OCPP server parameters. This enables users or operators to perform certain on-site configurations without requiring a technician. - Support for Local and Remote Firmware Upgrades
According to public materials, local upgrades are performed using an RS-485 serial port tool, while remote upgrades are conducted via platform updates or FTP-based program transfer. A separate OCPP board update procedure is also provided, demonstrating product-level operability from a field maintenance perspective. - Commercial-grade Installation and Assembly Documentation
The CDZ-E model installation guide includes descriptions assuming repetitive production and on-site assembly, such as PCB, display, card reader, waterproof joints, emergency stop button, and cable fixation. This indicates a structure intended for commercialization rather than a simple prototype.
π Role and Application of the WIZnet's Chip



https://cnevcharger.com/bluesky-ac-ev-charging-explained
WIZnet Chip Used: W5500
- In the publicly available error code list, the entry β0xB9 W5500 mac failureβ is explicitly stated. This serves as the most direct public evidence that the WIZnet W5500 is actually used in the charger board or related network board.
Role in Networking
- The W5500 is a Hardwired TCP/IP-based Ethernet controller that connects to the MCU via SPI and handles wired network communication based on TCP/UDP/IPv4. In the context of this project, it is reasonable to interpret that the W5500 provides a stable TCP connection layer required for communication between the charger and the central OCPP server. The WebSocket and OCPP application layers are handled by the MCU or higher-level software, while the W5500 is responsible for the underlying Ethernet and TCP transport layer.

π Market & Application Value

(by ChatGPT)
Target Industry and Market
This project clearly targets the EV charging infrastructure market. According to the IEA, global EV sales exceeded 17 million units in 2024, accounting for more than 20% of new car sales. This indicates a continuously growing demand for charging hardware, management software, and remote maintenance infrastructure.
Key Buyers
The most realistic buyers are EV charger manufacturers (OEM/ODM), charging operators (CPO), commercial building and parking facility operators, and public charging infrastructure providers. Since the commercial version of the app emphasizes remote monitoring, payment, and analytics, it is more suited for B2B and B2B2C markets rather than B2C.
Competitiveness
The competitiveness of this case lies not in ultra-fast charging performance, but in standards-based interoperability, operational convenience, and multi-communication support. The OCA explains that the core value of OCPP is enabling chargers to connect with central systems regardless of vendor. In other words, reducing vendor lock-in and increasing compatibility with different platforms is a key advantage in the commercial market.
Market Viability
The market potential is considered high. However, the differentiation focus is on operational and maintenance efficiency rather than charging performance. While the AC slow-charging market is highly competitive, solutions that reliably provide OCPP integration, app-based configuration, remote upgrades, and hybrid wired/wireless communication remain highly relevant in commercial deployment scenarios.
π External Indicators
1.Volume and Continuity of Public Documentation
On cnevcharger.com, there are numerous documents directly related to this project, including installation, networking, OCPP, app configuration, and update guides. This suggests that it is not a one-time promotional effort, but rather part of ongoing documentation for an actively maintained product line. However, since most of the content is published by the manufacturer itself, the level of independent external validation is relatively limited.
https://cnevcharger.com/bluesky-ac-ev-charging-explained/
2.YouTube
Based on search results, a Bluesky-related OCPP explanation video has approximately 7.7K views, and the channel has around 12.5Kβ12.6K subscribers. Additionally, the video titled βEV Charger connects to Bluesky CMS via OCPP 1.6Jβ has around 914 views. While this does not indicate the level of influence seen in large-scale open-source projects, it does suggest a moderate level of interest for product operation and configuration-focused content.

3.Open Source Integration
The SteVe OCPP server referenced in this project has approximately 1,016 stars, 466 forks, 69 open issues, 18 pull requests, and 57 organization followers on GitHub. In other words, while the project itself does not appear to have a publicly available GitHub repository based on current information, the server it integrates with is built on an open-source foundation that is actively used within the EV charging industry.
https://github.com/steve-community/steve
4.Industry Standardization and External Scalability
The OCA states that OCPP 1.6 is widely implemented by CS/CSMS manufacturers worldwide. Therefore, this project is not based on a proprietary in-house protocol, but is designed for a broadly adopted open standard market, which gives it strong external value and scalability.
https://openchargealliance.org/protocols/ocpp-protocols/ocpp-1-6/
π WIZnet Strategic Value
Implications for the WIZnet Maker Ecosystem
This UCC demonstrates that WIZnet chips can be used not only for simple sensor nodes or TCP server demos, but also as the network backbone of industrial and service-oriented equipment. Since EV chargers are systems where communication failures can directly lead to service disruptions and revenue loss, this case holds greater significance as a real industrial application reference rather than a typical Maker ecosystem example.
Potential for Expansion into Similar Projects
Potential extension areas include communication gateways for energy storage systems (ESS), industrial charging equipment, smart parking and payment terminals, and OCPP/OCPI-integrated devices for building energy management. However, expansions involving OCPI, ISO 15118, security certification, and compliance with country-specific metering and payment regulations are not confirmed in the currently available materials, and are more appropriately considered as future product strategy directions.
π Summary
This UCC presents a case demonstrating how an EV charging system incorporating WIZnet W5500-based wired Ethernet communication can be applied in real industrial environments. Beyond simple network connectivity, it integrates with a central management system based on the OCPP 1.6 standard and provides a structure that supports installation, operation, and maintenance in an integrated manner through both app-based and local configuration tools.
In particular, the combination of multiple communication interfaces and remote management functions highlights a design approach aimed at securing both operational stability and efficiency of charging infrastructure. This serves as a practical example showing that WIZnet chips can function as reliable network infrastructure even in industrial service equipment, while also indicating potential for future expansion into broader energy and infrastructure domains.
π FAQ
Q1. What features does the Bluesky AC EV Charging system provide?
The system supports Ethernet, Wi-Fi, Bluetooth, and 4G communication, and integrates with central management systems via OCPP 1.6 for monitoring, control, and data management.
Q2. What is the role of OCPP 1.6 in the charger system?
OCPP 1.6 is a standard communication protocol that enables data exchange between chargers and central servers via WebSocket, supporting remote control and monitoring.
Q3. How do you configure Wi-Fi on the charger?
Wi-Fi can be configured ΧΧΧΧ¦Χ’ΧΧͺ the Wow Charger app by connecting via Bluetooth and entering the SSID and password.
Q4. How is the OCPP server configured?
Users input parameters such as server URL, port, and charger ID through an app or configuration tool, enabling WebSocket-based communication.
Q5. How is firmware updated on the charger?
Firmware updates can be done locally via RS-485 tools or remotely via platform or FTP-based updates.
Q6. How do you update the OCPP board program?
The update is performed using a dedicated tool, following step-by-step procedures including connection setup and firmware upload.
Q7. What components are involved in charger installation?
Key components include the mainboard, display, card reader, emergency stop button, waterproof connectors, and cable management parts.
Q8. How is communication maintained between charger and server?
Heartbeat messages are periodically exchanged to ensure connection stability and allow continuous monitoring.
Q9. What is the role of the WIZnet W5500 chip?
The W5500 provides hardwired TCP/IP Ethernet connectivity, ensuring reliable communication between the charger and OCPP server.
Q10. Where is this system typically applied?
It is suitable for commercial parking, public charging infrastructure, and CPO environments requiring stable operation and centralized control.
π Reference Link
https://cnevcharger.com/ru/bluesky-ac-ev-charging-explained/
https://cnevcharger.com/ru/how-to-update-the-ocpp-board-program/
https://cnevcharger.com/the-charging-pile-app-sets-the-wi-fi-connection/
https://cnevcharger.com/charging-pile-ocpp1-6-client-and-server-interaction-implementation/
https://cnevcharger.com/how-to-install-bluesky-cdz-e-ac-charging-pile/
https://cnevcharger.com/how-to-install-bluesky-cdz-e-ac-charging-pile/
