[{"data":1,"prerenderedAt":489},["ShallowReactive",2],{"guide-zh-jk-bms-log-messages-explained":3,"guides-zh":430},{"id":4,"title":5,"body":6,"date":408,"description":409,"extension":410,"keywords":411,"meta":419,"navigation":420,"path":421,"related":422,"seo":426,"stem":427,"updated":428,"__hash__":429},"guides_zh\u002Fguides\u002Fjk-bms-log-messages-explained.md","JK BMS 日志消息详解：Boot、Time calibration、保护",{"type":7,"value":8,"toc":396},"minimark",[9,26,35,40,48,51,54,90,93,96,99,198,201,211,297,303,306,309,352,355,384,387,393],[10,11,12,13,17,18,21,22,25],"p",{},"JK BMS 的日志消息是一些简短的固定字符串，例如 ",[14,15,16],"code",{},"Boot","、",[14,19,20],{},"Time calibration"," 或 ",[14,23,24],{},"Cell 01 over charge protection","。本文解释每一条的含义，以及哪些说明确实存在问题。这些名称来自固件使用的消息表，列在开源项目 esphome-jk-bms 中。",[10,27,28,29,34],{},"如果你只想知道自己文件的答案，把它拖进",[30,31,33],"a",{"href":32},"\u002Flogs","日志分析页","即可，页面会替你把消息分组。下面各节解释的就是它在分组时依据的内容。",[36,37,39],"h2",{"id":38},"jk-bms-日志消息从哪里来","JK BMS 日志消息从哪里来",[10,41,42,43,47],{},"这些消息是详细日志的文本列。BMS 每发生一个事件就写一行，每一行都带有当时电池组的快照：MOS 状态、最高和最低单体、电压、电流、容量和温度。如何导出文件、如何阅读其他列，见",[30,44,46],{"href":45},"\u002Fguides\u002Fjk-bms-detail-log","如何导出并读懂 JK-BMS 详细日志","。",[10,49,50],{},"这些文字并不标准。同一类事件在不同地方写法不同，所以分析页是按模式而不是按完整字符串来匹配消息的。有必要时，下文会特别说明。",[36,52,53],{"id":53},"电源和时钟消息",[55,56,57,67,73,79,85],"ul",{},[58,59,60,62,63,47],"li",{},[14,61,16],{},"：BMS 已启动。电压和电流列都是零，它们似乎是在测量任何数据之前写入的。见",[30,64,66],{"href":65},"\u002Fguides\u002Fjk-bms-reboots-power-events","读懂重启和电源事件",[58,68,69,72],{},[14,70,71],{},"Shutdown","：BMS 自行关机。",[58,74,75,78],{},[14,76,77],{},"Enter sleep","：BMS 进入了休眠模式。休眠选项在设置里的智能休眠字段中。",[58,80,81,84],{},[14,82,83],{},"Reset Watch-Dog","：内部看门狗重启了 BMS。与上面三条不同，这是一个故障。偶尔一次值得留意，反复出现就值得排查。",[58,86,87,89],{},[14,88,20],{},"：app 连接并设置时钟时记录。它标记的是你自己的连接会话，不是故障。分析页默认隐藏这些行。",[10,91,92],{},"日期早于 2021 年的行，通常是 2020-01-01，是在时钟设置之前写入的。它们是真实事件，只是时间未知。",[36,94,95],{"id":95},"开关消息",[10,97,98],{},"这些消息记录了是谁打开或关闭了充电或放电，因此能解释为什么 MOS 状态发生了变化而没有任何保护动作。",[55,100,101,116,131,154,167,192],{},[58,102,103,17,106,17,109,17,112,115],{},[14,104,105],{},"APP open charge",[14,107,108],{},"APP close charge",[14,110,111],{},"APP open discharge",[14,113,114],{},"APP close discharge","：你或其他人使用了 JK app。",[58,117,118,17,121,17,124,17,127,130],{},[14,119,120],{},"Remote open charge",[14,122,123],{},"Remote close charge",[14,125,126],{},"Remote open discharge",[14,128,129],{},"Remote close discharge","：通过远程命令完成的同样操作。",[58,132,133,17,136,17,139,17,142,145,146,149,150,153],{},[14,134,135],{},"RS485 charge on",[14,137,138],{},"RS485 charge off",[14,140,141],{},"RS485 discharge on",[14,143,144],{},"RS485 discharge off","，以及对应的 ",[14,147,148],{},"CAN"," 消息：总线上的逆变器或控制器切换了 MOS。",[14,151,152],{},"RS485 power off"," 是单独的一条消息。",[58,155,156,159,160,163,164,166],{},[14,157,158],{},"Button to turn it off"," 和 ",[14,161,162],{},"APP to turn it off","：BMS 被电源按键或 app 关闭。随后不久出现的 ",[14,165,16],{}," 是预期之内的，不是意外重启。",[58,168,169,17,172,17,175,178,179,17,182,17,185,159,188,191],{},[14,170,171],{},"Manually enable the emergency mode",[14,173,174],{},"Manually turn off the emergency mode",[14,176,177],{},"Turn off the emergency mode automatically","：紧急模式的变化。",[14,180,181],{},"Button Emergency On",[14,183,184],{},"Button Emergency Off",[14,186,187],{},"Remote Emergency On",[14,189,190],{},"Remote Emergency Off"," 意思相同，只是写明了来源。",[58,193,194,197],{},[14,195,196],{},"Button Forced Heating","：用按键强制打开了加热功能。",[36,199,200],{"id":200},"保护触发与解除",[10,202,203,204,159,207,210],{},"触发表示 BMS 切断了充电或放电。大多数触发在数值恢复后都有对应的解除行。解除的措辞各不相同：\"is released\"、\"released\" 或 \"Release\"，以及 \"over-temperature\" 或 \"over temperature\"。这就是 ",[14,205,206],{},"Charge over temperature protection is released",[14,208,209],{},"Discharge over-temperature protection is released"," 看起来不一致的原因。",[55,212,213,240,261,278],{},[58,214,215,216,159,219,222,223,159,226,229,230,21,232,235,236,47],{},"电压：",[14,217,218],{},"Cell overcharge protection",[14,220,221],{},"Battery overcharge protection","，",[14,224,225],{},"Cell undervoltage protection",[14,227,228],{},"Battery undervoltage protection","。有些文件会写出单体编号，例如 ",[14,231,24],{},[14,233,234],{},"Cell 03 over discharge protection","。分析会读取 01 到 32 的单体编号。最常见的情况见",[30,237,239],{"href":238},"\u002Fguides\u002Fjk-bms-cell-overcharge-protection-tripping","单体过充保护为何反复触发",[58,241,242,243,17,246,249,250,159,253,256,257,47],{},"电流：",[14,244,245],{},"Charge overcurrent protection",[14,247,248],{},"Discharge overcurrent protection","，以及分级的 ",[14,251,252],{},"Discharge OCP II",[14,254,255],{},"Discharge OCP III","。限值和延时见",[30,258,260],{"href":259},"\u002Fguides\u002Fjk-bms-ocp-scp-settings","过流与短路设置",[58,262,263,264,17,267,17,270,273,274,277],{},"短路：",[14,265,266],{},"Charge short circuit protection",[14,268,269],{},"Discharge short circuit protection",[14,271,272],{},"Discharge level 2 short circuit protection","。分析页把这些评为严重。",[14,275,276],{},"SCP Release Failed"," 表示 BMS 无法解除短路保护，同样按严重处理。",[58,279,280,281,17,284,17,287,17,290,159,293,296],{},"温度：",[14,282,283],{},"Charge over temperature protection",[14,285,286],{},"Charge low temperature protection",[14,288,289],{},"Discharge over temperature protection",[14,291,292],{},"Discharge under temperature protection",[14,294,295],{},"MOS over temperature protection","，各自都有解除消息。",[10,298,299,300,302],{},"直到文件末尾都没有解除的触发仍处于未关闭状态。",[14,301,16],{}," 会结束所有未关闭的事件段，因为 BMS 已经丢失了状态。",[36,304,305],{"id":305},"故障消息",[10,307,308],{},"故障不是普通的保护动作。它们说明 BMS 或其接线出了问题，分析页把它们评为严重。",[55,310,311,326,335,341],{},[58,312,313,159,316,319,320,159,323,47],{},[14,314,315],{},"Abnormal current sensor",[14,317,318],{},"Abnormal coprocessor communication","：内部故障。它们的解除行是 ",[14,321,322],{},"Abnormal release of current sensor",[14,324,325],{},"Abnormal cancellation of coprocessor communication",[58,327,328,159,331,334],{},[14,329,330],{},"Charge MOS abnormal",[14,332,333],{},"Discharge MOS abnormal","：BMS 检测到某个 MOS 有问题。",[58,336,337,340],{},[14,338,339],{},"Discharge On Failed","（放电开启失败）：BMS 试图打开放电，但没有成功。仅凭这条消息看不出原因。请查看它前后的行，仍在生效的保护就是一种可能的解释。",[58,342,343,346,347,351],{},[14,344,345],{},"Cells Count Incorrect","：BMS 看到的串数与设置不符。请与",[30,348,350],{"href":349},"\u002F","编辑器","中的串数对照。",[36,353,354],{"id":354},"配置消息",[55,356,357,369,375],{},[58,358,359,17,362,17,365,368],{},[14,360,361],{},"Factory setting LION",[14,363,364],{},"Factory setting LFP",[14,366,367],{},"Factory setting LTO","：设置被重置为对应电芯类型的出厂设置。你的所有数值一次性发生了变化，所以请逐项检查。",[58,370,371,374],{},[14,372,373],{},"Unknown Log Code [0]","：不是真正的事件。它似乎是开启定时数据存储时 BMS 写入的周期记录，分析页默认隐藏它。如果你的文件里有成千上万条，请检查数据存储周期。",[58,376,377,17,380,383],{},[14,378,379],{},"Unknown Log Code [5]",[14,381,382],{},"[10]"," 和其他数字：消息表中没有命名的代码。分析页会把它们列为未知，也无法说明它们的含义。",[36,385,386],{"id":386},"更快地阅读",[10,388,389,390,392],{},"手工阅读很长的文件很慢。",[30,391,33],{"href":32},"会把消息归入各个类别（电源、开关、各类保护、故障、配置），把触发与解除配对，并统计每节单体的触发次数。在你要求之前，它会隐藏时钟同步和周期记录。一切都在浏览器中运行，文件不会上传。",[10,394,395],{},"先看故障和严重级别的行，再看反复出现的触发。",{"title":397,"searchDepth":398,"depth":398,"links":399},"",3,[400,402,403,404,405,406,407],{"id":38,"depth":401,"text":39},2,{"id":53,"depth":401,"text":53},{"id":95,"depth":401,"text":95},{"id":200,"depth":401,"text":200},{"id":305,"depth":401,"text":305},{"id":354,"depth":401,"text":354},{"id":386,"depth":401,"text":386},"2026-10-02","每条 JK BMS 日志消息的含义：Boot、Time calibration、APP open charge、保护触发与解除，以及 Discharge On Failed。","md",[412,413,414,415,416,417,418],"jk bms 日志消息","jk bms time calibration","jk bms app open charge","jk bms unknown log code","jk bms discharge on failed","jk bms reset watch-dog","jk bms 事件日志详解",{},true,"\u002Fguides\u002Fjk-bms-log-messages-explained",[423,424,425],"jk-bms-detail-log","jk-bms-reboots-power-events","jk-bms-ocp-scp-settings",{"title":5,"description":409},"guides\u002Fjk-bms-log-messages-explained",null,"CMWY2X3yNl7WaJ1Jgolb6DVQ5bwnjmudwg0x7AZqgXk",[431,436,440,443,446,450,454,455,459,462,466,470,473,477,481,485],{"path":432,"title":433,"description":434,"date":435,"updated":428},"\u002Fguides\u002Fjk-bms-bluetooth-browser","在浏览器中通过蓝牙修改 JK BMS 设置","在 Chrome 或 Edge 中连接 JK BMS，读取全部设置，应用预设，再按安全顺序写回并逐项回读校验。无需 JK app。","2026-10-04",{"path":437,"title":438,"description":439,"date":408,"updated":435},"\u002Fguides\u002Fjk-bms-balance-settings","JK BMS 均衡设置：均衡启动电压、触发压差和均衡电流","详解 JK BMS 均衡设置：均衡启动电压、均衡触发压差、最大均衡电流和均衡开关，适用于磷酸铁锂、三元和钛酸锂。",{"path":238,"title":441,"description":442,"date":408,"updated":428},"JK BMS 单体过充保护反复触发：原因与解决方法","JK BMS 单体过充保护每分钟触发又解除？了解充电器设得过高为何导致这种情况、如何与弱单体区分，以及怎样解决。",{"path":45,"title":444,"description":445,"date":408,"updated":435},"如何导出并读懂 JK-BMS 详细日志（Detail Log）","JK-BMS 详细日志包含什么、如何从 app 导出、如何读懂其中的事件，以及日志分析页能告诉你哪些保护动作和故障信息。",{"path":447,"title":448,"description":449,"date":408,"updated":435},"\u002Fguides\u002Fjk-bms-export-import-settings","JK BMS 设置导出与导入：.jkcfg 文件完全指南","如何用 JK BMS app 导出和导入保护板设置，.jkcfg 文件里有什么，为什么手动改会损坏，以及如何在浏览器里安全编辑。",{"path":451,"title":452,"description":453,"date":408,"updated":435},"\u002Fguides\u002Fjk-bms-lifepo4-settings","磷酸铁锂 JK BMS 参数设置：8S、16S，280Ah 与 314Ah 电芯","磷酸铁锂电池组的 JK BMS 参数设置：8S 和 16S、280Ah 与 314Ah 电芯的单体电压、均衡、电流和温度推荐值，分三种损耗等级。",{"path":421,"title":5,"description":409,"date":408,"updated":428},{"path":456,"title":457,"description":458,"date":408,"updated":435},"\u002Fguides\u002Fjk-bms-nmc-lto-settings","JK BMS 三元锂与钛酸锂设置：安全的单体参数","JK BMS 三元锂 NMC 与钛酸锂 LTO 电池组设置：单体过压、欠压、均衡、温度和倍率的三档数值，以及编辑器如何识别电芯类型。",{"path":259,"title":460,"description":461,"date":408,"updated":435},"JK BMS 过流保护设置：OCP 与 SCP 参数指南","详解 JK BMS 过流保护设置：充放电 OCP 电流上限、延时、恢复时间与短路保护 SCP，附推荐范围和逆变器选型方法。",{"path":463,"title":464,"description":465,"date":408,"updated":435},"\u002Fguides\u002Fjk-bms-parameters-explained","JK BMS 参数详解：按分组逐项讲解每个设置","一篇看懂 JK BMS 参数：单体 OVP、OVPR、UVP、UVPR、均衡、SOC、RCV 与 RFV、电流和温度保护，附磷酸铁锂常用范围。",{"path":467,"title":468,"description":469,"date":408,"updated":435},"\u002Fguides\u002Fjk-bms-password","JK BMS 密码：默认密码、修改与重置指南","JK BMS 的密码其实有两个：蓝牙连接密码和设置密码。本文介绍出厂默认值、修改方法、密码无效时的排查，以及忘记密码怎么办。",{"path":65,"title":471,"description":472,"date":408,"updated":435},"JK BMS 重启与充电 MOS 关闭：在日志中读懂电源事件","JK BMS 重启，或充电 MOS 自己关闭？学会读懂详细日志中的 Boot 行和 MOS 状态，分清正常重启与真正的故障。",{"path":474,"title":475,"description":476,"date":408,"updated":435},"\u002Fguides\u002Fjk-bms-sending-failure","JK BMS 发送失败（Sending failure）：原因与逐步解决方法","JK BMS 导入设置时提示发送失败？了解固件拒绝参数的原因（电压顺序链、写入顺序、短路延时），并按步骤解决。",{"path":478,"title":479,"description":480,"date":408,"updated":435},"\u002Fguides\u002Fjk-bms-soc-calibration","JK BMS SOC 校准：解决电量漂移、跳变和复位问题","JK BMS SOC 校准详解：SOC 为什么会漂移或跳变，SOC-100% 电压和 SOC-0% 电压的作用，以及如何设置并重新校准电池组。",{"path":482,"title":483,"description":484,"date":408,"updated":428},"\u002Fguides\u002Fjk-bms-weak-cell-log","用 JK BMS 日志找出弱单体：触发、压差与均衡","在 JK BMS 详细日志中找出弱单体：哪节单体先触发、触发时压差有多大，以及这是均衡漂移还是单体已损坏。",{"path":486,"title":487,"description":488,"date":408,"updated":435},"\u002Fguides\u002Fjk-bms-wire-resistance","JK BMS 线阻：均衡线阻异常报警的排查与修复","JK BMS 线阻详解：均衡线阻异常报警的含义、正常数值范围、常见原因，以及如何修好一根有问题的均衡线。",1791151319671]