TI BQ7961x系列 Automotive Battery Monitor 数据手册:精确监控与保护

需积分: 12 12 下载量 46 浏览量 更新于2024-07-14 1 收藏 2.8MB PDF 举报
BQ7961x系列,如BQ79612-Q1、BQ79614-Q1和BQ79616-Q1,是由Texas Instruments (TI)推出的一款高性能的12S、14S和16S汽车级电池监控器、均衡器以及集成硬件保护器。这些数据手册针对的是先进的信息,适用于预生产阶段的产品,可能会在未经通知的情况下进行更改。 该系列的主要特点包括: 1. **严格的汽车应用认证**:BQ7961x芯片经过了AEC-Q100认证,这是一种专门针对汽车电子产品的质量标准,确保了它们在极端环境下的可靠性和性能。产品能够在-40°C到+125°C的宽温范围内稳定工作,并满足设备温度等级1的要求,适应汽车电池系统的严苛条件。 2. **多功能性**:作为一款精确的电池监控器,它能够监测电池电压,提供关键的电池状态信息,有助于确保电池系统的健康运行。同时,它具备均衡功能,可以检测并管理电池单元之间的电压不平衡,以延长电池寿命并防止热失控。 3. **通信接口**:支持UART(通用异步收发器)或SPI(同步串行接口),使得芯片与微控制器(MCU)之间可以方便地进行数据交换,便于系统集成和远程控制。 4. **电压隔离和模块化设计**:内置隔离组件,保护系统免受电气干扰,确保了安全性和可靠性。此外,其模块化设计允许灵活配置,适合不同的电池模块和连接需求。 5. **电容式水平转换差分接口**:这种接口技术提高了信号传输的抗噪声能力和电气隔离,增强了系统的信号质量和抗干扰能力。 6. **可选环路连接**:提供了额外的连接选项,可以根据实际应用需求选择是否使用,以优化电路布局和效率。 7. **重要注意事项**:文档末尾的注意事项强调了产品的可用性、保修政策、安全性关键应用的使用限制、知识产权声明以及其他重要免责声明,用户在使用前应仔细阅读。 BQ7961x是一款专为汽车电池系统设计的集成解决方案,它结合了高精度的电压测量、均衡控制和硬件保护功能,旨在提升电动汽车和混合动力汽车电池的性能和寿命。对于任何涉及这类电池管理系统的设计工程师或维护人员来说,理解并掌握这款芯片的工作原理、接口和操作方式是至关重要的。

SELECT DISTINCT c.ID AS id, c.NAME AS contName, c.CONTRACT_NO AS contractNo, c.INSTANCE_ID AS instanceId, c.UNDERTAKE_DEPT_ID AS remindDeptId, c.UNDERTAKE_DEPT_NAME AS sendDeptName, c.CREATE_USER_ID, c.CREATE_USER_NAME AS contractOpteraterName, c.PLAN_STATE AS planState, c.PLAN_STATE_NAME AS planStateName, aw.INSTANCE_ID AS inId, aw.CREATE_TIME AS sendTime FROM ( SELECT c.* FROM ( SELECT c.* FROM ( SELECT c.ORIGINAL_CONTRACT_ID, MAX(CREATE_TIME) CREATE_TIME FROM CONTRACT_DRAFT.C_CONTRACT_INFO c WHERE c.ORIGINAL_CONTRACT_ID IS NOT NULL AND c.ORIGINAL_CONTRACT_ID != '' GROUP BY c.ORIGINAL_CONTRACT_ID ) t LEFT JOIN CONTRACT_DRAFT.C_CONTRACT_INFO c ON t.ORIGINAL_CONTRACT_ID = c.ORIGINAL_CONTRACT_ID AND t.CREATE_TIME = c.CREATE_TIME UNION ALL SELECT c.* FROM CONTRACT_DRAFT.C_CONTRACT_INFO c WHERE ( c.ORIGINAL_CONTRACT_ID IS NULL OR c.ORIGINAL_CONTRACT_ID = '' ) AND c.ID NOT IN ( SELECT c.ORIGINAL_CONTRACT_ID FROM CONTRACT_DRAFT.C_CONTRACT_INFO c WHERE c.ORIGINAL_CONTRACT_ID IS NOT NULL AND c.ORIGINAL_CONTRACT_ID != '')) c WHERE c.deleted_flag = 0 AND c.BELONG = 1 AND sysdate > c.end_date AND c.plan_state IN (4100, 4110, 4120, 4200, 4210, 4220, 5100, 5110, 5120) ) c INNER JOIN (SELECT INSTANCE_ID,create_time,state FROM CONTRACT_DRAFT.C_ACTIVITY_WORKITEMS WHERE state = 'Waiting') aw ON c.INSTANCE_ID = aw.INSTANCE_ID LEFT JOIN (SELECT deleted_flag,CONT_ID FROM CONTRACT_DRAFT.C_GET_PAY_PLAN WHERE deleted_flag = 0 ) g ON c.ID = g.CONT_ID LEFT JOIN CONTRACT_DRAFT.C_OUR_ENTITY_INFO oe ON c.OUR_ENTITY_ID = oe.ID AND oe.DELETED_FLAG = 0 ORDER BY aw.CREATE_TIME DESC 优化

2023-07-08 上传

优化这段代码:if (icbcDtlRsp.getBillSta().equals("CS01") && icbcDtlRsp.getRangeStage().equals("TF0101")) { //CS01已出票 & TFO101待收票---010004出票已登记 ecdsDrftInf.setDrftSndStat(getValueOrDefault(ECDSConstants.DRAFT_STATUS_CPYDJ, ecdsDrftInf.getDrftSndStat())); // 票据发送人状态 ecdsDrftInf.setDrftRcvStat(getValueOrDefault(ECDSConstants.DRAFT_STATUS_CPYDJ, ecdsDrftInf.getDrftRcvStat())); // 票据接收人状态 ecdsDrftInf.setDrftCurrStat(getValueOrDefault(ECDSConstants.DRAFT_STATUS_CPYDJ, ecdsDrftInf.getDrftCurrStat())); // 人行当前状态 } else if (ecdsDrftInf.getDrftOrgStat().equals(ECDSConstants.DRAFT_STATUS_CPYDJ) && icbcDtlRsp.getBillSta().equals("CS01") && icbcDtlRsp.getRangeStage().equals("TF0302")) { //CS01已出票 & TF0302已锁定--- 020001承兑待签收 ecdsDrftInf.setDrftSndStat(getValueOrDefault(ECDSConstants.DRAFT_STATUS_TSCDDQS, ecdsDrftInf.getDrftSndStat())); // 票据发送人状态 ecdsDrftInf.setDrftRcvStat(getValueOrDefault(ECDSConstants.DRAFT_STATUS_TSCDDQS, ecdsDrftInf.getDrftRcvStat())); // 票据接收人状态 ecdsDrftInf.setDrftCurrStat(getValueOrDefault(ECDSConstants.DRAFT_STATUS_TSCDDQS, ecdsDrftInf.getDrftCurrStat())); // 人行当前状态 } else if (ecdsDrftInf.getDrftOrgStat().equals(ECDSConstants.DRAFT_STATUS_CPYDJ) && icbcDtlRsp.getBillSta().equals("CS02") && icbcDtlRsp.getRangeStage().equals("TFO101")) { //CS02已承兑 & TFO101待收票---020006承兑已签收 ecdsDrftInf.setDrftSndStat(getValueOrDefault(ECDSConstants.DRAFT_STATUS_TSCDYQS, ecdsDrftInf.getDrftSndStat())); // 票据发送人状态 ecdsDrftInf.setDrftRcvStat(getValueOrDefault(ECDSConstants.DRAFT_STATUS_TSCDYQS, ecdsDrftInf.getDrftRcvStat())); // 票据接收人状态 ecdsDrftInf.setDrftCurrStat(getValueOrDefault(ECDSConstants.DRAFT_STATUS_TSCDYQS, ecdsDrftInf.getDrftCurrStat())); // 人行当前状态 }

2023-06-01 上传

优化这个sql select FLOW_COMMON.c_business_id as business_id, (select max(f.end_time) from flow_hi_track f where f.business_id = FLOW_COMMON.c_business_id and f.action_type != 'CLAIM' ) as deal_time from template_flow_common FLOW_COMMON right join template_hollycrm1680160914000 hollycrm1680160914000 on FLOW_COMMON.c_business_id = hollycrm1680160914000.c_business_id where FLOW_COMMON.tenant_id = 'T000' and FLOW_COMMON.valid = 1 and lower(FLOW_COMMON.c_state) != 'draft' and ( ( FLOW_COMMON.c_flow_id in ('FLOW20230330152148238756') and (FLOW_COMMON.c_processing_group in ('1650685461842100265') ) or FLOW_COMMON.c_cur_assignee = '1639203916409208891' ) or FLOW_COMMON.c_creator = '1639203916409208891' or FLOW_COMMON.c_flow_id in ('FLOW20230330152148238756') or FLOW_COMMON.c_business_id in ('1650765461521956870', '1650765461521956870', '1650817085812506712', '1650831863482155082', '1654094763571281921', '1654001405104488514', '1654294361434751036', '1654445890410119245', '1654441313937915946', '1654433554383241232', '1653329109050196051', '1655380751421538376', '1655380751421538376', '1654732194700066894', '1654765190966673497', '1655862681678118938', '1654732194700066894', '1654732194700066894', '1654732194700066894', '1654441313937915946', '1656855682290286598', '1654732194700066894', '1654732194700066894', '1654732194700066894', '1656106327421747261') or (FLOW_COMMON.c_processing_group in ('1650685461842100265')) ) and FLOW_COMMON.c_workorder_type = 'C0018' and FLOW_COMMON.c_business_type = 'C00180008,C001800080001,C0018000800010001' LIMIT 572540,10;

2023-07-25 上传

springboot+MyBatis连接MySql数据库遇到问题:### Error querying database. Cause: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure The last packet successfully received from the server was 11,751 milliseconds ago. The last packet sent successfully to the server was 11,858 milliseconds ago. ### The error may exist in file [/app/tomcat/webapps/project/WEB-INF/classes/mapper/PersonWeekMapper.xml] ### The error may involve com.xmsme.mapper.PersonWeekMapper.selectPersonWeekList-Inline ### The error occurred while setting parameters ### SQL: SELECT count(0) FROM (SELECT WEEK.id, WEEK.sub_time, WEEK.need_thing, WEEK.plan_content, WEEK.target_content, WEEK.sub_time AS update_time, WEEK.create_time, WEEK.week_start, WEEK.user_id, WEEK.week_end, readInfo.id AS readId, readInfo.read_status AS readStatus, updateor.nick_name FROM t_person_weekly AS WEEK LEFT JOIN sys_user sUser ON sUser.user_id = WEEK.user_id LEFT JOIN t_read_info readInfo ON readInfo.business_id = WEEK.id AND readInfo.read_type = 'PER' LEFT JOIN sys_user updateor ON updateor.user_id = WEEK.update_by LEFT JOIN sys_user_role uRole ON uRole.user_id = WEEK.update_by LEFT JOIN sys_user_post uPost ON uPost.user_id = WEEK.user_id LEFT JOIN t_project_person person ON person.user_id = WEEK.user_id LEFT JOIN t_project_person Pperson ON Pperson.project_id = person.project_id WHERE 1 = 1 AND WEEK.is_del = 0 AND WEEK.draft = 'N' AND Pperson.user_id = ? GROUP BY WEEK.id) table_count ### Cause: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure The last packet successfully received from the server was 11,751 milliseconds ago. The last packet sent successfully to the server was 11,858 milliseconds ago. ; Communications link failure The last packet successfully received from the server was 11,751 milliseconds ago. The last packet sent successfully to the server was 11,858 milliseconds ago.; nested exception is com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure The last packet successfully received from the server was 11,751 milliseconds ago. The last packet sent successfully to the server was 11,858 milliseconds ago.

2023-07-22 上传