From 17ce711e4950d25515143498e770f06cf7ead681 Mon Sep 17 00:00:00 2001 From: zhaojie <1710884619@qq.com> Date: Mon, 9 Mar 2026 22:23:00 +0800 Subject: [PATCH] Add web session analysis platform with follow-up topics --- .gitignore | 9 + LICENSE | 21 + README.md | 357 ++ UB IOV Support_TR.csv | 5901 +++++++++++++++++++++++++++++ __init__.py | 54 + config/__init__.py | 8 + config/llm_config.py | 44 + data_analysis_agent.py | 628 +++ main.py | 74 + prompts.py | 147 + require.md | 447 +++ requirements.txt | 55 + utils/__init__.py | 16 + utils/code_executor.py | 456 +++ utils/create_session_dir.py | 15 + utils/data_loader.py | 90 + utils/execution_session_client.py | 219 ++ utils/execution_worker.py | 321 ++ utils/extract_code.py | 38 + utils/fallback_openai_client.py | 230 ++ utils/format_execution_result.py | 25 + utils/llm_helper.py | 91 + webapp/__init__.py | 4 + webapp/api.py | 242 ++ webapp/session_manager.py | 66 + webapp/static/app.js | 299 ++ webapp/static/index.html | 88 + webapp/static/style.css | 278 ++ webapp/storage.py | 311 ++ webapp/task_runner.py | 147 + 30 files changed, 10681 insertions(+) create mode 100644 .gitignore create mode 100644 LICENSE create mode 100644 README.md create mode 100755 UB IOV Support_TR.csv create mode 100644 __init__.py create mode 100644 config/__init__.py create mode 100644 config/llm_config.py create mode 100644 data_analysis_agent.py create mode 100644 main.py create mode 100644 prompts.py create mode 100644 require.md create mode 100644 requirements.txt create mode 100644 utils/__init__.py create mode 100644 utils/code_executor.py create mode 100644 utils/create_session_dir.py create mode 100644 utils/data_loader.py create mode 100644 utils/execution_session_client.py create mode 100644 utils/execution_worker.py create mode 100644 utils/extract_code.py create mode 100644 utils/fallback_openai_client.py create mode 100644 utils/format_execution_result.py create mode 100644 utils/llm_helper.py create mode 100644 webapp/__init__.py create mode 100644 webapp/api.py create mode 100644 webapp/session_manager.py create mode 100644 webapp/static/app.js create mode 100644 webapp/static/index.html create mode 100644 webapp/static/style.css create mode 100644 webapp/storage.py create mode 100644 webapp/task_runner.py diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..5f24365 --- /dev/null +++ b/.gitignore @@ -0,0 +1,9 @@ +__pycache__/ +*.pyc +.DS_Store +.env +.env copy +outputs/ +runtime/ +*.log +log.txt diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..5d9664b --- /dev/null +++ b/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2025 Data Analysis Agent Team + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/README.md b/README.md new file mode 100644 index 0000000..54adba9 --- /dev/null +++ b/README.md @@ -0,0 +1,357 @@ +# 数据分析智能体 (Data Analysis Agent) + +🤖 **基于LLM的智能数据分析代理** + +[![Python Version](https://img.shields.io/badge/python-3.8%2B-blue.svg)](https://python.org) +[![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE) +[![OpenAI](https://img.shields.io/badge/LLM-OpenAI%20Compatible-orange.svg)](https://openai.com) + +## 📋 项目简介 + +![alt text](assets/images/40d04b1dc21848cf9eeac4b50551f2a1.png) +![alt text](assets/images/d24d6dd97279a27fd8c9d652bac1fdb2.png) +数据分析智能体是一个功能强大的Python工具，它结合了大语言模型(LLM)的理解能力和Python数据分析库的计算能力，能够： + +- 🎯 **自然语言分析**：接受用户的自然语言需求，自动生成专业的数据分析代码 +- 📊 **智能可视化**：自动生成高质量的图表，支持中文显示，输出到专用目录 +- 🔄 **迭代优化**：基于执行结果自动调整分析策略，持续优化分析质量 +- 📝 **报告生成**：自动生成包含图表和分析结论的专业报告(Markdown + Word) +- 🛡️ **安全执行**：在受限的环境中安全执行代码，支持常用的数据分析库 + +## 🏗️ 项目架构 + +``` +data_analysis_agent/ +├── 📁 config/ # 配置管理 +│ ├── __init__.py +│ └── llm_config.py # LLM配置(API密钥、模型等) +├── 📁 utils/ # 核心工具模块 +│ ├── code_executor.py # 安全的代码执行器 +│ ├── llm_helper.py # LLM调用辅助类 +│ ├── fallback_openai_client.py # 支持故障转移的OpenAI客户端 +│ ├── extract_code.py # 代码提取工具 +│ ├── format_execution_result.py # 执行结果格式化 +│ └── create_session_dir.py # 会话目录管理 +├── 📄 data_analysis_agent.py # 主智能体类 +├── 📄 prompts.py # 系统提示词模板 +├── 📄 main.py # 使用示例 +├── 📄 requirements.txt # 项目依赖 +├── 📄 .env # 环境变量配置 +└── 📁 outputs/ # 分析结果输出目录 + └── session_[时间戳]/ # 每次分析的独立会话目录 + ├── *.png # 生成的图表 + ├── 最终分析报告.md # Markdown报告 + └── 最终分析报告.docx # Word报告 +``` + +## 📊 数据分析流程图 + +使用Mermaid图表展示完整的数据分析流程： + +```mermaid +graph TD + A[用户输入自然语言需求] --> B[初始化智能体] + B --> C[创建专用会话目录] + C --> D[LLM理解需求并生成代码] + D --> E[安全代码执行器执行] + E --> F{执行是否成功?} + F -->|失败| G[错误分析与修复] + G --> D + F -->|成功| H[结果格式化与存储] + H --> I{是否需要更多分析?} + I -->|是| J[基于当前结果继续分析] + J --> D + I -->|否| K[收集所有图表] + K --> L[生成最终分析报告] + L --> M[输出Markdown和Word报告] + M --> N[分析完成] + + style A fill:#e1f5fe + style N fill:#c8e6c9 + style F fill:#fff3e0 + style I fill:#fff3e0 +``` + +## 🔄 智能体工作流程 + +```mermaid +sequenceDiagram + participant User as 用户 + participant Agent as 数据分析智能体 + participant LLM as 语言模型 + participant Executor as 代码执行器 + participant Storage as 文件存储 + + User->>Agent: 提供数据文件和分析需求 + Agent->>Storage: 创建专用会话目录 + + loop 多轮分析循环 + Agent->>LLM: 发送分析需求和上下文 + LLM->>Agent: 返回分析代码和推理 + Agent->>Executor: 执行Python代码 + Executor->>Storage: 保存图表文件 + Executor->>Agent: 返回执行结果 + + alt 需要继续分析 + Agent->>LLM: 基于结果继续分析 + else 分析完成 + Agent->>LLM: 生成最终报告 + LLM->>Agent: 返回分析报告 + Agent->>Storage: 保存报告文件 + end + end + + Agent->>User: 返回完整分析结果 +``` + +## ✨ 核心特性 + +### 🧠 智能分析流程 + +- **多阶段分析**：数据探索 → 清洗检查 → 分析可视化 → 图片收集 → 报告生成 +- **错误自愈**：自动检测并修复常见错误（编码、列名、数据类型等） +- **上下文保持**：Notebook环境中变量和状态在分析过程中持续保持 + +### 📋 多格式报告 + +- **Markdown报告**：结构化的分析报告，包含图表引用 +- **Word文档**：专业的文档格式，便于分享和打印 +- **图片集成**：报告中自动引用生成的图表 + +## 🚀 快速开始 + +### 1. 环境准备 + +```bash +# 克隆项目 +git clone https://github.com/li-xiu-qi/data_analysis_agent.git + +cd data_analysis_agent + +# 安装依赖 +pip install -r requirements.txt +``` + +### 2. 配置API密钥 + +创建`.env`文件： + +```bash +# OpenAI API配置 +OPENAI_API_KEY=your_api_key_here +OPENAI_BASE_URL=https://api.openai.com/v1 +OPENAI_MODEL=gpt-4 + +# 或者使用兼容的API（如火山引擎） +# OPENAI_BASE_URL=https://ark.cn-beijing.volces.com/api/v3 +# OPENAI_MODEL=deepseek-v3-250324 +``` + +### 3. 基本使用 + +```python +from data_analysis_agent import DataAnalysisAgent +from config.llm_config import LLMConfig + +# 初始化智能体 +llm_config = LLMConfig() +agent = DataAnalysisAgent(llm_config) + +# 开始分析 +files = ["your_data.csv"] +report = agent.analyze( + user_input="分析销售数据，生成趋势图表和关键指标", + files=files +) + +print(report) +``` + +```python +# 自定义配置 +agent = DataAnalysisAgent( + llm_config=llm_config, + output_dir="custom_outputs", # 自定义输出目录 + max_rounds=30 # 增加最大分析轮数 +) + +# 使用便捷函数 +from data_analysis_agent import quick_analysis + +report = quick_analysis( + query="分析用户行为数据，重点关注转化率", + files=["user_behavior.csv"], + max_rounds=15 +) +``` + +## 📊 使用示例 + +以下是分析贵州茅台财务数据的完整示例： + +```python +# 示例：茅台财务分析 +files = ["贵州茅台利润表.csv"] +report = agent.analyze( + user_input="基于贵州茅台的数据，输出五个重要的统计指标，并绘制相关图表。最后生成汇报给我。", + files=files +) +``` + +**生成的分析内容包括：** + +- 📈 营业总收入趋势图 +- 💰 净利润率变化分析 +- 📊 利润构成分析图表 +- 💵 每股收益变化趋势 +- 📋 营业成本占比分析 +- 📄 综合分析报告 + +## 🎨 流程可视化 + +### 📊 分析过程状态图 + +```mermaid +stateDiagram-v2 + [*] --> 数据加载 + 数据加载 --> 数据探索: 成功加载 + 数据加载 --> 编码修复: 编码错误 + 编码修复 --> 数据探索: 修复完成 + + 数据探索 --> 数据清洗: 探索完成 + 数据清洗 --> 统计分析: 清洗完成 + 统计分析 --> 可视化生成: 分析完成 + + 可视化生成 --> 图表保存: 图表生成 + 图表保存 --> 结果评估: 保存完成 + + 结果评估 --> 继续分析: 需要更多分析 + 结果评估 --> 报告生成: 分析充分 + 继续分析 --> 统计分析 + + 报告生成 --> [*]: 完成 +``` + +## 🔧 配置选项 + +### LLM配置 + +```python +@dataclass +class LLMConfig: + provider: str = "openai" + api_key: str = os.environ.get("OPENAI_API_KEY", "") + base_url: str = os.environ.get("OPENAI_BASE_URL", "https://api.openai.com/v1") + model: str = os.environ.get("OPENAI_MODEL", "gpt-4") + max_tokens: int = 4000 + temperature: float = 0.1 +``` + +### 执行器配置 + +```python +# 允许的库列表 +ALLOWED_IMPORTS = { + 'pandas', 'numpy', 'matplotlib', 'duckdb', + 'scipy', 'sklearn', 'plotly', 'requests', + 'os', 'json', 'datetime', 're', 'pathlib' +} +``` + +## 🎯 最佳实践 + +### 1. 数据准备 + +- ✅ 使用CSV格式，支持UTF-8/GBK编码 +- ✅ 确保列名清晰、无特殊字符 +- ✅ 数据量适中（建议<100MB） + +### 2. 查询编写 + +- ✅ 使用清晰的中文描述分析需求 +- ✅ 指定想要的图表类型和关键指标 +- ✅ 明确分析的目标和重点 + +### 3. 结果解读 + +- ✅ 检查生成的图表是否符合预期 +- ✅ 阅读分析报告中的关键发现 +- ✅ 根据需要调整查询重新分析 + +## 🚨 注意事项 + +### 安全限制 + +- 🔒 仅支持预定义的数据分析库 +- 🔒 不允许文件系统操作（除图片保存） +- 🔒 不支持网络请求（除LLM调用） + +### 性能考虑 + +- ⚡ 大数据集可能导致分析时间较长 +- ⚡ 复杂分析任务可能需要多轮交互 +- ⚡ API调用频率受到模型限制 + +### 兼容性 + +- 🐍 Python 3.8+ +- 📊 支持pandas兼容的数据格式 +- 🖼️ 需要matplotlib中文字体支持 + +## 🐛 故障排除 + +### 常见问题 + +**Q: 图表中文显示为方框？** +A: 系统会自动检测并使用可用的中文字体（macOS: Hiragino Sans GB, Songti SC等；Windows: SimHei等）。 + +**Q: API调用失败？** +A: 检查`.env`文件中的API密钥和端点配置，确保网络连接正常。 + +**Q: 数据加载错误？** +A: 检查文件路径和编码格式，支持UTF-8、GBK等常见编码。 + +**Q: 分析结果不准确？** +A: 尝试提供更详细的分析需求，或检查原始数据质量。 + +**Q: Mermaid流程图无法正常显示？** +A: 确保在支持Mermaid的环境中查看（如GitHub、Typora、VS Code预览等）。如果在本地查看，推荐使用支持Mermaid的Markdown编辑器。 + +**Q: 如何自定义流程图样式？** +A: 可以在Mermaid代码块中添加样式定义，或使用不同的图表类型（graph、flowchart、sequenceDiagram等）来满足不同的展示需求。 + +### 错误日志 + +分析过程中的错误信息会保存在会话目录中，便于调试和优化。 + +## 🤝 贡献指南 + +欢迎贡献代码和改进建议！ + +1. Fork 项目 +2. 创建功能分支 +3. 提交更改 +4. 推送到分支 +5. 创建Pull Request + +## 📄 许可证 + +本项目基于MIT许可证开源。详见[LICENSE](LICENSE)文件。 + +## 🔄 更新日志 + +### v1.0.0 + +- ✨ 初始版本发布 +- 🎯 支持自然语言数据分析 +- 📊 集成matplotlib图表生成 +- 📝 自动报告生成功能 +- 🔒 安全的代码执行环境 + +--- + +
+ +**🚀 让数据分析变得更智能、更简单！** + +
diff --git a/UB IOV Support_TR.csv b/UB IOV Support_TR.csv new file mode 100755 index 0000000..994caa0 --- /dev/null +++ b/UB IOV Support_TR.csv @@ -0,0 +1,5901 @@ +TR Number,Source,Date creation,Issue Start Time,Type of problem,TR Description,处理过程,TR tracking,TR Level,TR Status,Module（模块）,Wilfulness（责任人）,Date of close TR,Vehicle Type01,VIN/sim,SIM,Notes,Attachment,Created by,App remote control version,HMI SW,父记录,Has it been updated on the same day,Operating time,问题关闭日期 +TR320,Telegram bot,02/01/2025,,Remote control ,After TBOX december update remote control stopped working ,"0319：等待OTA +0102: +1. APP中无法正确显示汽车的状态和位置。 +2. 远控无法使用 +3. 导航无法在 GU 上运行 +0108：TSP: 内外网都无法使用，排查OTA平台升级状态","24/04: TBOX SW has been upgraded with DMC SW OTA. No issues since upgrade => TR closed +1704: Source version for OTA not right +03/04: there is still no connection to the server. Wait for downloading. +march 06：waiting ota +08/01: TSP : the apn1 &apn2 don't work +02/01: + 1. The status and location of the car is not displayed correctly in the application. +2. The remote startup function does not work +3. Navigation does not work on the GU",Low,close,TBOX,Evgeniy,24/04/2025,EXEED RX（T22）,LVTDD24BXRG023494,,,,Evgeniy,,,,,,112 +TR342,Telegram bot,02/01/2025,,Remote control ,The customer can't use remote control,"0211:长时间未等到用户反馈，默认关闭，新问题则提交新工单进行处理 +没有问题发生详细时间","Feb 11：If user feedback is not received for a long period of time, it will be closed by default, and new issues will be submitted to a new work order for processing. +08/01 TSP has not recieved the remote command at the time of picture on 02.01 . Collect the customer’s operating scenario, operating time after reproducing the remote control problem",Low,close,local O&M,Evgeniy,11/02/2025,EXEED VX FL（M36T）,LVTDD24B9RD030308,,,"image.png,image.png",Evgeniy,,,,,,40 +TR343,Telegram bot,02/01/2025,,PKI problem,The customer can't use navi. ,"0218 关闭问题，IHUID修改问题 +0211：专题群讨论","11/02:make a group to anlayse the reason +07/01: please change the hu-sn on tsp. replace it using the hu-sn in the ihu-system +02/01: After checking I found problems with PKI ",Low,close,local O&M,Evgeniy,18/02/2025,EXEED RX（T22）,LVTDD24B1RG031497,,,"image.png,image.png,image.png",Evgeniy,,,,,,47 +TR344,Telegram bot,02/01/2025,,OTA,There is impossible to put settings in Navi after OTA update. After customers put "settings" - application crashed. ,,"02/11 该问题已经SOTA修复，问题关闭 +02/06 项目定的方案走主机OTA更新，座舱的应用包已提交给主机集成，@待会后少龙更新OTA时间计划 +01/21 东软正在排查OTA系统是否修改Jar包混肴逻辑 +02/05 已更换东软提供的新jar包以及jar包的集成方式，测试验证后OTA更新",Low,close,DMC,张少龙,11/02/2025,EXEED VX FL（M36T）,"LVTDD24B2RD089359 +LVTDD24B3PD625958 +LVTDD24B6RD032517 +LVTDD24B7PD635067 +LVTDD24B3PD626379 +LVTDD24B7PD635067",,"TGR0000145, TGR0000159, TGR0000205",,Evgeniy,,,,,,40 +TR345,Telegram bot,02/01/2025,,Remote control ,The customer can't use remote control,0319：等待OTA0108：图片显示时间，还未收到远控指令，等待收集信息,"13/05: upgrade success- close +24/04: upgrade downloaded. Still wait for upgrade. +1704: downloaded but not installed +03/04: OTA upgrade downloaded. Wait for upgrading. +08/01 TSP: TSP has not recieved the remote command at the time of picture. Collect the customer’s operating scenario, operating time after reproducing the remote control problem",Low,close,local O&M,Evgeniy,13/05/2025,EXEED RX（T22）,LVTDD24B6RG020639,,,image.png,Evgeniy,,,,,,131 +TR346,Telegram bot,02/01/2025,,Remote control ,The customer can't use remote control,"0201：Tbox日志无法下载 +0108：唤醒失败，Tbox在1月2日无注册记录","24/04: upgrade TBOX SW OTA. No issues since the upgrade => TR closed +08/01: wake up failed. tbox has no login record on 01.02. +02/01: Opetation date/time: 02.01.2025 16:26. TBOX LOG from tsp can't download",Low,close,local O&M,Evgeniy,24/04/2025,EXEED RX（T22）,LVTDD24B7RG033223,,,image.png,Evgeniy,,,,,,112 +TR358,Telegram bot,03/01/2025,,APN 2 problem,"After 1st of January the customer can't use any applications in car, but with WIFI everything ok.",,,Low,close,local O&M,Evgeniy,21/01/2025,EXEED VX FL（M36T）,LVTDD24B9PD578824,,,"img_v3_02i6_fc34b5b6-46d9-4812-b442-b89b5469d6hu.jpg,img_v3_02i6_1ec7ce4b-4beb-4693-908b-ff2f75c80dhu.jpg",Evgeniy,,,,,,18 +TR359,Telegram bot,03/01/2025,,doesn't exist on TSP,Local produced car don't exist on TSP platrom. ,,"Feb 27:waiting infromation +03/01: Asked autosales team to invite customers for collecting TBOX info",Low,temporary close,local O&M,Evgeniy,27/02/2025,EXEED VX FL（M36T）,"XEYDD14B1RA006337, +XEYDD14B1RA004158",,,,Evgeniy,,,,,,55 +TR360,Telegram bot,03/01/2025,,Navi,Navi doesn't work ,"0107：Cabin-team has fixed it , pls ask the customer to retry",03/01: Operation date 03.01 / time on the screen,Medium,close,local O&M,Evgeniy,26/02/2025,JAECOO J7（T1EJ）,LVVDD21B6RC065115,,,"image.png,image.png",Evgeniy,,,,,,54 +TR361,Telegram bot,06/01/2025,,Navi,Navi doesn't work ,,0107：Cabin-team has fixed it ,Medium,close,生态/ecologically,何韬,08/01/2025,EXEED VX FL（M36T）,LVTDD24B5RD075097,,,b5c001dd-c234-4610-a809-1169d5205350.jpeg,Evgeniy,,,,,,2 +TR362,Telegram bot,06/01/2025,,Navi,Navi doesn't work ,,0107：Cabin-team has fixed it ,Medium,close,生态/ecologically,何韬,10/01/2025,JAECOO J7（T1EJ）,LVVDD21B4RC077618,,,,Evgeniy,,,,,,4 +TR363,Telegram bot,06/01/2025,,Navi,Navi doesn't work ,,0107：Cabin-team has fixed it ,Medium,close,生态/ecologically,何韬,10/01/2025,JAECOO J7（T1EJ）,LVVDD21B9RC053170,,,image.png,Evgeniy,,,,,,4 +TR364,Telegram bot,06/01/2025,,Navi,Navi doesn't work ,,0107：Cabin-team has fixed it ,Medium,close,生态/ecologically,何韬,10/01/2025,JAECOO J7（T1EJ）,LVVDB21B6RC071017,,,,,,,,,,4 +TR365,Mail,06/01/2025,,Network,"VK services such as music, video, Navi etc. do not work because of the internet connection issue. However, the internet traffic is available and OK in MNO. Status in Simba is also OK. Customer was checking the apps operation using the internet shared via hot spot from a smartphone and confirmed that everything worked well.",,"14/01: customer's feed-back ""Cheked it out. VK services started working"". TR closed. +09/01 ：According to TBOX LOG ，TBOX feedback device were assigned two IP address,based on the info provived by TBOX already raised a ticket to MTS for further checking. +10/01:As per MTS feedback as below: +The technicians have found out that your device is running two active sessions in the same APN at the same time. Two static IP addresses are assigned at once. This is a feature of the device itself, the MTS network is not related to this error. +10/01：As per the requirements from PDC, SIMBA had reset the SIM card, pls contact the owner to retry it . +13/01：The traffic record is normal on MNO platform .Need to ask for the latest feedback from the customer，if customer feedback have no issue on network, SIMBA recommand to close this ticket",Low,close,local O&M,,14/01/2025,JAECOO J7（T1EJ）,LVVDD21B8RC053161,,ohrana737@mail.ru,"LOG_LVVDD21B8RC05316120250110051751.tar,Screenshot_error_message.jpg,Simba_status.JPG",Vsevolod,,,,,,8 +TR366,Telegram bot,06/01/2025,,Remote control ,"Commands are not executed in remote control app. Last apn1&2 on Jan, 6th. However, there was no more apn2 since Jan, 6th although SIMBA is OK.",,"14/01: customer's feed-back remote control started working again after updating of firmware. +08/01: Operation time&date: Jan, 8th at 16:41 (Moscow time), error message attached. Tbox log will be provided as soon as it's available. + +10/01:Please confirm with the car owner whether the location has MTS network coverage?The sim card state and package are all vailable. + +13/01：The traffic record is normal on MNO platform .Need to ask for the latest feedback from the customer，if customer feedback have no issue on network, SIMBA recommand to close this ticket",Low,close,MNO,胡纯静,14/01/2025,EXEED RX（T22）,LVTDD24B1RG023450,,TGR0000107,"LOG_LVTDD24B1RG023450_27_01_2025.tar,Simba_status.JPG,Picture_3.jpg",Vsevolod,,,,,,8 +TR367,Telegram bot,08/01/2025,,Application,"VK video app stopped working. A message ""check your network connection"" comes up. VK video app is up to date. Others apps such as VK music, weather, Navi etc. work well. Customer was trying to launch the app with an internet newtwork shared via smartphone - it does not work either. MNO and SIMBA are OK.",09/01 视频账号需重新登陆,"16/10: on the request to relogin in VK app, the issue has been fixed.",Low,close,生态/ecologically,颜廷晓,16/01/2025,EXEED VX FL（M36T）,LVTDD24B5RD069476,,TGR0000131,,Vsevolod,,,,,,8 +TR370,Telegram bot,10/01/2025,,Network,VK apps do not work. Message "Check network connection". Customer was checking with network shared from smartphone - all the apps work well. SIMBA is OK. MNO: apn2 activated but there is no apn2 available.,"0311：下次例会分享进度 +0227：需要属地运维抓取日志","11/03：Sharing progress at next regular meeting +05/03: customer was asked to log out of VK video app and re-log in. Wait for feedback if app started working. +Feb 27：need logs +10/01: tbox log attached +10/01:Pls collect the latest tbox log +13/01：The traffic record is normal on MNO platform , if customer feedback have no issue on network, SIMBA recommand to close this ticket",Medium,close,local O&M,Vsevolod,18/03/2025,JAECOO J7（T1EJ）,LVVDD21B8RC054021,,TGR0000129,"LOG_LVVDD21B8RC054021_10_01_2025.tar,Picture_1.jpg,Picture_2.jpg",Vsevolod,,,,,,67 +TR371,Mail,10/01/2025,,Remote control ,Remote control doesn't work + bad status,,"26/02: solved +14/01 Collect the customer’s operating scenario, operating time @Evgeniy",Low,close,local O&M,Evgeniy,26/02/2025,EXEED RX（T22）,LVTDD24B6RG023539,,+79044989820 bound,"LVTDD24B6RG023539.tar,image.png,image.png",Evgeniy,,,,,,47 +TR372,Telegram bot,10/01/2025,,Network,No any TBOX connect since 06.01.2025,0211:无信息更新,"13.02 Solved by SW updated at dealer centre +11/02：no anyinformation upadated +Waiting for feedback +01/14 anything is ok on tsp +Collecting data from customer",Low,close,local O&M,Kostya,13/02/2025,EXEED RX（T22）,LVTDD24B1RG023450,,TGR0000016,,Kostya,,,,,,34 +TR374,Mail,13/01/2025,,Remote control ,The customer can't use remote control since 05.01.2025,"0319：等待OTA0226：问题依旧未解决 +0114：收集客户的操作场景、重现问题的操作时间，收集客户数据","13/05: downloaded, not installed - temporary close +1704: downloaded, not installed +03/04: OTA upgrade downloaded. Wait for upgrading. +Feb 26: still doesn't work +14/01 Collect the customer’s operating scenario, operating time after reproducing the problem +Collecting data from customer",Low,temporary close,local O&M,Evgeniy,13/05/2025,EXEED RX（T22）,LVTDD24B1RG019902,,,image.png,Evgeniy,,,,,,120 +TR375,Mail,13/01/2025,,doesn't exist on TSP,"Vehicle is not in the TSP platform however it has VK services available in IHU. Thus, customer can't activate remote control as well as VK services",,"13/02: Vehicle had manually been imported in the TSP platform with VIN XEYDD14B1RA004189. +20/01: the vehicle had been produced in China. +01/14 this car doesnt exist on TSP& MES, can you confirm whether it was produced in Russian",Low,close,local O&M,,13/02/2025,EXEED VX FL（M36T）,"LVTDD24B9RDB34557 +XEYDD14B1RA004189",,,"Picture_3.JPG,Picture_2.JPG,Picture_1.JPG",Vsevolod,,,,,,31 +TR376,Mail,13/01/2025,,Remote control ,Remote control stopped working. A message "Time for respond from server has expired. Please try again later" comes up when calling an operation. TSP is OK: last login and frequency data on 13/01. MNO is also OK.,,"13/02: customer's feedback: remote control started working without any porblems. TR closed. +14/01 Collect the customer’s operating scenario, operating time after reproducing the problem +13/01: tbox log is attached.",Low,close,local O&M,Vsevolod,13/02/2025,EXEED RX（T22）,LVTDD24B5RG023693,,Customer phone number: +79251338221,"LOG_LVTDD24B5RG023693_13_01_2025.tar,Picture_1.JPG",Vsevolod,,,,,,31 +TR377,Telegram bot,13/01/2025,,Activation SIM,Failed relogin HU via App QR scan,,21.01: Customer feedback - everything works now,Low,close,生态/ecologically,冯时光,21/01/2025,EXEED VX FL（M36T）,LVTDD24B4PD577306,,TGR0000183,e5486d85-ef3a-4b9a-8ad9-5f02e93aff03.png,Kostya,,,,,,8 +TR378,Mail,13/01/2025,,Remote control ,"Remote control stopped working. There were no more apn1 available since Jan, 1st. ",0319：等待OTA0224：在41辆车计划清单中，等待用户进站升级。,"24/04: no issues => TR closed +03/04: OTA upgrade completed successfully on March, 31th - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +05/03: wait for OTA update to be released in march. +24/02: customer is in the list of 41 car to be upgraded with new TBOX SW at dealer. +11/02: should we wait for the new OTA in march to be applied to fix the remote control issue? @喻起航 +16/01：The cause of the problem is network congestion. Please send the user OTA upgrade to resolve the problem。 +14/01: operation date&time - on 14/01 at 13:15, command name - engine start. Tbox log attached + +MNO Investigation conclusion（15/01）：There are no prohibitions or restrictions on the use of APN1 from MTS side.The device establishes a session through APN1 on Jan 14, however, the device does not actively use APN1, we recommend that the device side continue to check. You can see the detailed investigation results in the attachment.",Low,close,local O&M,Vsevolod,24/04/2025,EXEED RX（T22）,LVTDD24B3RG016340,,Customer phone number: +79315051488,"image.png,LOG_LVTDD24B3RG016340_14_01_2025.tar,Picture_2.jpg,Picture_1.jpg",Vsevolod,,,,,,101 +TR379,Telegram bot,13/01/2025,,Remote control ,"The customer can't use remote control, no any data about car in app +MNO - OK, both APNs are ok +TSP Low frequency Data - Not since 11 jan +TSP high frequency Data - Not since 11 jan +Last Tbox connect - 11 jan",,"12.02 No feedback after asking -> closed +14/01 TSP: No login tsp records on 13 &14 Jan, all remote command on 13&14 Jan fialed Because TBOX wake-up failed. real-data reported normally. +Perhaps the customer's parking location is poor, or it could be an old issue with T22 that requires an OTA upgrade @Kostya",Low,close,local O&M,Kostya,13/02/2025,EXEED RX（T22）,LVTDD24B7RG023517,,TGR0000178,,Kostya,,,,,,31 +TR380,Mail,13/01/2025,,Remote control ,The customer can't use remote control since 11.01.2025 + wrong status of car ,0217：经后台查询，因用户车辆当时处于信号不好的地点，车辆未收到远控指令，后续查看功能可正常使用，建议用户再观察使用，若还有问题，建议再次反馈且提供相关日志。,"Feb 26: problem solved +14/01 TSP: tsp hasnot recieved remote command records on 11 Jan, all remote command 13 Jan fialed Because TBOX wake-up failed. real-data reported normally. +Perhaps the customer's parking location is poor, or it could be an old issue with T22 that requires an OTA upgrade @Evgeniy",Low,close,local O&M,Evgeniy,26/02/2025,EXEED RX（T22）,LVTDD24B4RG032014,,bound +79255388020,,Evgeniy,,,,,,44 +TR381,Mail,13/01/2025,,Remote control ,Vehicle data is not reflected in remote control app. MNO is OK. Last tbox login is on 13/01 as well as frequency data.,,"17/02: customer's feedback: remote control work well. No issue found => TR closed. +13/02: customer asked if the issue is still valid. Wait for a feedback. +20/01: what are the next steps to fix the customer's issue? MNO status - the only apn available is apn1 for the reason of the traffic used up. +14/01 TSP: tsp has not recieved the reflected request on 13 Jan @Vsevolod +13/01: tbox log is attached to the TR",Low,close,local O&M,Vsevolod,17/02/2025,EXEED RX（T22）,LVTDD24B1RG013498,,Customer phone number: +79803429000,"LOG_LVTDD24B1RG013498_14_01_2025.tar,Picture_1.JPG",Vsevolod,,,,,,35 +TR387,Mail,14/01/2025,,Remote control ,The customer can't use remote control,"0506：TSP未查询1月至5月远控记录，建议用户重新尝试 +0427:等待属地与客户联系确认是否可用 +0425:等待属地与客户联系确认是否可用 +0424:等待属地与客户联系确认是否可用 +0423：平台查询日志上传为1月14，建议用户重新尝试后，如不可用远控，再提供远控操作及日志 +0421：TSP核实车控时间后，转TBOX分析日志 +0417：添加0226的截图。 +0415：等待用户反馈 +0410：等待用户反馈 +0325：继续等待 +0320：继续等待 +0318：等待最新日志 +0312:提供新抓取日志发生时间 @赵杰 +0311：转国内分析 @刘海丰 +0304;需要前方运维抓取日志 +0226：用户反馈始终无法正常运行 +0217：经后台查询，因用户车辆当时处于信号不好的地点，车辆未收到远控指令，后续查看功能可正常使用，建议用户再观察使用，若还有问题，建议再次反馈且提供相关日志。","13/05: customer can't use any functions. he installed another alarm security system with remote control -temporary close +06/05:TSP did not query remote control records from January to May, users are advised to try again.@Evgeniy +27/04:Waiting for the territory to contact the customer to confirm availability +25/04:Waiting for the territory to contact the client to confirm availability +24/04:Waiting for location to contact customer to confirm availability. +23/04：The platform query log was uploaded on January 14th. It is recommended that users try again and provide remote control operations and logs if remote control is not available. +21/04: TSP verifies car control time and then transfers to TBOX to analyse logs +17/04: added screenshot from 26.02. +10/04:Still Waiting. +01/04:Still Waiting. +25/03:Still waiting +20/03:Still waiting +18/03:Provide the remote control occurrence time in the newly captured logs.@Evgeniy +12/03:Provide the remote control occurrence time in the newly captured logs.@Evgeniy +11/03 : turn to analysis. +04/03 :need tbox log +26 /02: still doesn't work +14/01 TSP: tsp waited feedback timeout Because of waking up TBox spends too much time +14/01: operation data/time - 14.01 8:04",Low,temporary close,local O&M,Evgeniy,13/05/2025,JAECOO J7（T1EJ）,LVVDD21B3RC077416,,bound 79606323647,"image.png,LVVDD21B3RC077416.tar,Screenshot_20250110_080433_com.ru.chery.od.myOmoda.jpg",Evgeniy,,,,,,119 +TR388,Telegram bot,14/01/2025,,Remote control ,Remote control issue - commands are not exucuted. TSP is OK as well as MNO - apn1 is OK.,"0429：等待用户进站 +0427：等待用户进站 +0425：等待用户进站 +0424：等待用户进站 +0422:等待属地确认 +0421： +4月16日的两次空调控制都是车辆不在线，唤醒短信下发成功后，tbox无响应，35s超时 +4月17日的三次空调控制都是车辆不在线，唤醒短信下发成功后，tbox无响应，35s超时 +4月18日的空调控制成功了，4月18和4月19日和4月21日都发生了，没有下发远控发动机的指令，但是tbox上报了远控发动机执行成功的指令。建议告知用户近几次远控地，信号稳定性不佳，建议提供远控地经纬度信息供排查 +0417：等待用户反馈相关远控信息 +0410：等待用户反馈 +0407：已告知用户执行发动机启动并提供相应数据。等待反馈。 +0401：建议用户在信号好的地方，尝试重启车辆后，重试远控 +0327: TSP显示近三天TBOX有登录记录，仅查询到一条空调远控，但提示超时。 +0326：客户回来说远控仍然不能用。 +0325：再次询问客户问题是否仍然存在。等待反馈。 +0224：再次询问客户问题是否仍然存在。 +0217 计划暂时关闭此问题","29/04：waiting customer go to dealer +27/04：waiting customer go to dealer +25/04：waiting customer go to dealer +24/04：waiting customer go to dealer +22/04: Awaiting feedback on progress. +21/04: +On the 16th o+f April two air conditioning control are vehicle is not online, wake up text message sent successfully, tbox no response, 35s timeout +On the 17th of April, the vehicle was not online on all three occasions of air conditioning control, and after the wake-up message was sent successfully, the tbox did not respond and the 35s timeout was exceeded. +The air conditioning control on 18 April was successful, it happened on 18 April and 19 April and 21 April, there was no remote engine command issued, but tbox reported a successful remote engine execution. It is recommended that the user be informed of the last few remote control locations where the signal stability is poor, and it is recommended that latitude and longitude information of the remote control locations be provided for troubleshooting. + +17/04: repeat request sent to customer to call a command and provide then the respective data.@Vsevolod Tsoi +10/04：Still waiting +07/04: customer was asked to execute the engine start and provide the respective data. Wait for feedback. +01/04：Users are advised to try to retry the remote control after restarting the vehicle in a place with a good signal.@Vsevolod Tsoi +27/03：TSP shows that TBOX has logged in records in the past three days, and only one air-conditioning remote control was queried, but it prompted timeout. +26/03: customer is back saying that remote control still doesn't work. +25/03: customer is asked again it the problem still takes place. Wait for feedback. +24/02: repeat request sent to customer whether the issue is still valid. +13/02: customer asked if the issue is still valid. Wait for a feedback. +21/01: operation date&time - on 17/01 at 7:23; picture of an error message attached. +14/01: customer is asked to provide the needed data for analysis",Low,temporary close,local O&M,Vsevolod,13/05/2025,CHERY TIGGO 9 (T28)）,LVTDD24B3RG087859,,"TGR0000191, TGR00001013 ",file_327.jpg,Vsevolod,,,,,,119 +TR392,Telegram bot,15/01/2025,,Network,"11/02:still waiting +20/01 Normal on platforms waiting for feedback from customer @Константин +19/01 :the traffic record of this sim is normal, we recommand to close this ticket +17/01 ：The Vehicle is in hiberation mode and will not be attached to the network. As per our observed the SIM card was offline.Pls double check with the owner the vehicle status currently.thanks +16/01 (SIMBA):pls ask customer to try it again ，network should be normal now.(this car was active at 2025-01-07 13:21:30 , at that time ,MTS network suffered DDOS attack,So the package was delayed for two days) +The customer can't use remote control -> No any network data on MNO platform, only 2g network on HU, No Tbox Login after 2024 11 12 (december) -> +was activated 16:22:57 09-01-2025 according MNO +2025-01-07 13:21:30 according TSP/Simba +PKI tbox certificate creating time 2024-11-27 08:53:43 +""Vehicle is in hiberation mode"" - Can't collerct tbox log",0211:等待客户反馈,"13.02 Solved, waited for feedback - time out - closed",Low,close,local O&M,Kostya,13/02/2025,CHERY TIGGO 9 (T28)）,LVTDD24B0RG090671 sim:79863995436,79863995436,"TGR0000142 +TGR0000121 +TGR0000162 +TGR0000161",,Kostya,,,,,,29 +TR395,Mail,16/01/2025,,Remote control ,"Remote control issue - commands are not executed. Following the MNO investigation the status is as follow: apn2 had been desactivated on 07/01 for the reason of exeeding traffic limit but on other side we see well that apn2 continued working since this date. Last tbox login - 2025-01-16 10:11:39; last frequency data - 2025-01-16 10:11:35. Operation date&time - 13/01/2025 at 23:22 Moscow time, command - engine start, screenshot of the error message attached as well as tbox log.","0506:TSP见用户近期远控解锁已成功，建议关闭此问题 +0429:等待用户反馈 +0427:等待用户反馈 +0425:等待用户反馈 +0424:等待用户反馈有效信息 +0421：等待用户反馈 +0417：等待用户反馈信息 +0415：等待用户反馈 +0410：等待用户反馈 +0408: TSP分析无异常，TBOX登录记录正常，请提供具体远控操作及时间转TBOX分析 +0401：等待中 +0325：等待执行操作的反馈，然后提供相应的数据。 +0320：等待客户反馈操作时间及具体操作 +0318：等待取新日志@Vsevolod Tsoi +0312：重新获取日志并提供时间点@Vsevolod +0306 转国内分析 +0217 计划暂时关闭此问题","05/05：TSP sees that the user's recent remote unlocking has been successful, it is recommended to close this issue.@Vsevolod Tsoi +29/04:Awaiting feedback on progress. +27/04:Awaiting feedback on progress. +25/04:Awaiting feedback on progress. +24/04:Awaiting feedback on progress. +21/04: Awaiting feedback on progress. +17/04: customer has been asked for some details and executing of an operation with respective data.@Vsevolod Tsoi +10/04:waiting for feedback. +08/04:TSP analysis shows no abnormalities, TBOX login records are normal. Please provide specific remote control operations and time for TBOX analysis +07/04: command - unlock the car at 6:08. TBOX log attached. +01/04:Still Waiting. +25/03: wait for feedback on the executing of an operation and providing then the respective data. +20/03:Waiting for customer feedback on operation time and specific operation. +19/03: customer is asked to execute an operation as well as providing the respective data for investigation. Wait for feedback. +12/03: Retrieve logs and provide point-in-time. @Vsevolod +12/03: Retrieve logs and provide point-in-time. @Vsevolod +06/03: customer's feedback: the issue is still valid. Client is asked to reproduce the problem and then provied the needed input data for investigation. +05/03: repeat request to customer to provide feedaback. +0227 Plan to close the issue temporarily +13/02: customer is asked to provide a feedback if the problem is still valid. Wait for a feedback. +20/01: customer's feed-back: mobile network is OK. Customer was rebooting the network setting on our request. +17/01 Tsp: tsp has not recieved the remote control command at 13/01/2025 at 23:22 Moscow time, pls check the network of his mobile",Low,temporary close,TBOX,Vsevolod,13/05/2025,JAECOO J7（T1EJ）,LVVDD21B9RC053203,,voyt056@gmail.com,"LOG_LVVDD21B9RC053203_07_04_2025.tar,LOG_LVVDD21B9RC053203_16_01_2025.tar,Error_message.jpeg,Picture_2.JPG,Simba_status.JPG,Picture_1.JPG",Vsevolod,,,,,,117 +TR396,Mail,16/01/2025,,Remote control ,"Remote control issue - commands are not executed. MNO investigation: apn1&2 are available. Last tbox login - 2025-01-16 12:44:44; last frequency data - 2025-01-16 11:23:49. Operation date&time - 03/01/2025 at 14:30 Moscow time, command - engine start, screenshot of the error message and tbox log are attached.","0311:等待顾客回复 +0225：向用户询问问题是否依旧存在 +0217 计划暂时关闭此问题","20/30: customer's feedback: the problem is solved. +19/03: customer is asked again to provide a feedback. +25/02: repeat request sent to customer wether the issue is still valid. +13/02: customer asked if the problem is still valid. Wait for feedback. +23/01: Input data such as the operation time, date etc. was on 13/01 at 14:30 and not on 13/01 at 23:52 on which you provided the feed-back. Please check it again @林小辉 +017/01 Tsp: tsp has not recieved the remote control command at 13/01/2025 at 23:22 Moscow time, pls check the network of his mobile",Low,close,local O&M,Vsevolod,20/03/2025,JAECOO J7（T1EJ）,LVVDB21B0RC080599,,"lelya71@inbox.ru, phone number 79276589759","LOG_LVVDB21B0RC080599_16_01_2025.tar,Picture_1.jpeg",Vsevolod,,,,,,63 +TR402,Mail,17/01/2025,,Remote control ,Remote control issue - commands are not executed. MNO status: apn1&2 are availabel. Last tbox login on 17/01; last frequency data on 17/01. Operation date&time 03/01/2025 at 9:28. Pictures are attached as well as tbox log from 16/01.,0227 计划暂时关闭此问题,"19/03: customer is asked again wether the issue still exists. Wait for feedback. +05/03: repeat request to customer whether the issue is valid. +0227 Plan to close the issue temporarily +13/02: customer is asked for providing the info whether the issue is still valid. Wasit for feedback. +17/01 tep waited response timeout, waking up TBox spends too much time at 03/01/2025 at 9:28 +but excuting remote control command successfully at Jan 3, 2025 17:38",Low,temporary close,local O&M,Vsevolod,27/02/2025,JAECOO J7（T1EJ）,LVVDB21B1RC075802,,"zdorov_sergey@mail.ru, phone number 79081505465","LOG_LVVDB21B1RC075802_16_01_2025.tar,Picture_3.JPG,Picture_4.jpeg,Picture_1.JPG,Picture_2.JPG",Vsevolod,,,,,,41 +TR403,Telegram bot,17/01/2025,,Problem with auth in member center,Issue with coming up of QR-code to login in HU when entering to personal account. An error message "QR code is not valid". Customer was trying with internet network shared from smartphone => same result. No data exchange is available in PKI neither tbox or DMC login.,@胡纯静 apn1& apn2 流量都无法使用，T平台显示已激活,"20/01: customer's feed-back: after firmware update issue with QR-code has been fixed. +19/01 :the traffic record of this sim is normal, we recommand to close this ticket +18/01 apn1& apn2 don't work",Low,close,local O&M,胡纯静,20/01/2025,EXEED RX（T22）,LVTDD24B4RG013561,,TGR0000154,"file_300.jpg,file_216.jpg,file_302.jpg,file_301.jpg,file_215.jpg",Vsevolod,,,,,,3 +TR405,Mail,20/01/2025,,Network,"There is bad connection of network no network/3g.When connecting wifi everything is ok. Network indication. Constantly jumps from 3G to no network. At the same time the network on other devices in the same place works without problems. No errors, T-BOX and multimedia updated to the latest versions. Registration is passed. ",,"23/01: customer's feed-back - internet network started working again - problem is fixed. TR is closed. +1/21：Please ask customer to try it again and feedback the latest status .as monitor from backend the sims two APNs are available now.",Low,close,local O&M,Evgeniy,23/01/2025,EXEED VX FL（M36T）,LVTDD24B4RD062289,,,"LOG_LVTDD24B4RD06228920250120141741.tar,photo_2025-01-18_18-44-40.jpg,photo_2025-01-18_18-44-35.jpg,photo_2025-01-18_18-44-06.jpg",Evgeniy,,,,,,3 +TR406,Mail,20/01/2025,,Remote control ,"2/2 pls upgrade ota @Evgeniy +23/01：软件版本为旧版本，建议点对点OTA升级解决问题 +TR406- T22-tBOX 版本18.14.01_22.39.00 +The customer can't use remote control",0319：等待OTA0217 建议属地运维进行OTA升级操作,"Apr 17: after OTA works well- solved +03/04: OTA upgrade completed successfully on April, 1st - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +Feb 17 Recommended OTA upgrade operation by local O&M @Evgeniy +22/01: operation time 19/01 22:26 +20/01: waiting for screenshot+operation time",Low,close,OTA,Evgeniy,17/04/2025,EXEED RX（T22）,LVTDD24BXRG012480 ,,bound +79164620901,"image.png,LOG_LVTDD24BXRG01248020250120144246.tar",Evgeniy,,,,,,87 +TR407,Mail,20/01/2025,,Remote control ,Remote control issue - commands are not executed in the remote control app,"0305：客户未接听电话 +0225：如果问题仍然有效，将在本周内与客户联系。 +0217：经后台查询，因用户车辆当时处于信号不好的地点，车辆未收到远控指令，后续查看功能可正常使用，建议用户再观察使用，若还有问题，建议再次反馈且提供相关日志。","13/03: TR closed. +05/03: customer doesn't respond on the calls. +25/02: we will get in contact with customer within this week if the issue is still valid. +Feb 17：After the background inquiry, because the user's vehicle was in a bad signal location, the vehicle did not receive the remote control command, the follow-up view function can be used normally, it is recommended that the user again to observe the use, if there are still problems, it is recommended to feedback and provide relevant logs again. +21/01: what are the next steps to do? Another execution of an operation and then collecting the respective data for investigation? +21/01: tsp waited feedback timeout Because of waking up TBox spends too much time 【longer than 35 second】 +20/01: operation date&time - 29/12 at 22:06, tbox log attached as well as the screeenshot of an error message",Low,close,local O&M,Vsevolod,13/03/2025,JAECOO J7（T1EJ）,LVVDD21B3RC077562,,,"image.png,LOG_LVVDD21B3RC077562_20_01_2025.tar,Picture_1.jpeg",Vsevolod,,,,,,52 +TR408,Telegram channel,21/01/2025,,Problem with auth in member center,"Issue with log in the HU: after scannning of QR-code by customer to log in IHU, he received a notification in mobile remote control app on his smartphone that the autentification in member center has successefully been completed. However, there was any autentification in the IHU (see pictures attached). All the apps such as VK services, Navi and weather work well.",,"23/01: issue has been fixed. Cause was an additional space being present in the end of IHU ID. +23/01:Please provide relevant logs. I initially suspect that it is caused by network issues. Can you ask the user to click the refresh button to re-obtain the QR code to see if this can solve the problem?",Medium,close,生态/ecologically,刘康男,23/01/2025,JAECOO J7（T1EJ）,LVVDD21B9RC076643,,TG: @gav_n_o,"Picture_1.JPG,Picture_2.JPG",Vsevolod,,,,,,2 +TR409,Mail,21/01/2025,,Remote control ,Remote control issue - commands are not executed. Last tbox log in 2025-01-21 13:30:54; frequency data 2025-01-21 13:30:48; Both apn1&2 are active.,,"14/02: customer's feed-back: remote control started working. Problem is fixed. +13/02: customer asked whether the issue still tales place. Wait for feedback. +21/01: required data is asked for the investigation",Low,close,local O&M,Vsevolod,14/02/2025,EXEED RX（T22）,LVTDD24B8RG019153,,,Picture_1.jpg,Vsevolod,,,,,,24 +TR410,Mail,21/01/2025,,Remote control ,Remote control issue - vehicle data is not displayed in real time in the remote control app. Last login 2025-01-21 14:31:11; frequency data 2025-01-21 14:32:53. Apn1&2 are available and operational in MNO.,0217 计划暂时关闭此问题,"17/02: following customer's feedback ""there is no longer issue with remote control"". TR closed. +13/02: status in TSP: last high frequency data 2025-02-13 06:46:26; last tbox login 2025-02-13 06:38:40. MNO: apn1&2 are available and active. Customer asked if the issue is still valid. Wait for feedback. +21/01: required data is asked for the investigation",Low,close,local O&M,Vsevolod,17/02/2025,EXEED RX（T22）,LVTDD24B0RG009099,,,"Picture_2.jpg,Picture_1.JPG",Vsevolod,,,,,,27 +TR411,Mail,21/01/2025,,Remote control ,Remote control issue: vehicle data is not displayed in remote control app as well as commands are not executed. Last tbox log 2025-01-21 06:34:17; apn1 is available and active in MNO.,"0319：等待OTA +0217 计划暂时关闭此问题 +0225：2月19日16：12启动发动机，附图，APP端显示车门打开，但车辆实际已锁定","24/04: no issue since upgrade => TR closed. +03/04: OTA upgrade completed successfully on April, 1st - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +06/03: log upload is still in process. +25/02: command name - engine start on 19/02 at 16:12. Picture attached. Wrong vehicle condition in the app: door is shown as opened however the car is locked. +13/02: customer asked for the execution of remote engine start command providing then the required data for investigation. Wait for feedback. +22/01 tsp waited feedback timeout Because of waking up TBox spends too much time pls check the tbox-log @何文国 +21/01: operation date&time - on 21/01 at 17:19 - engine start, at 17:22 - AC activation Pictures attached. tbox log is still in process",Low,close,TBOX,Vsevolod,24/04/2025,EXEED RX（T22）,LVTDD24BXRG033460,,,"Picture_4.JPG,Picture_1.jpg,Picture_3.jpg,Picture_2.jpg",Vsevolod,,,,,,93 +TR412,Mail,21/01/2025,,Remote control ,21/01 TSP:客户反馈的时间点tbox没有登录记录 请查下TBOX日志 @何文国,"0319：等待OTA +0217 计划暂时关闭此问题","13/05: solved- close +24/04: upgrade successfylly completed on April, 22th. If no issues after one week, close TR. +17/04: downloaded, but no installed +03/04: OTA upgraded downloaded. Wait for upgrading. +23/01：21 only 18:11 (Beijing time) there is an air conditioning remote control, the execution was successful, before did not receive remote control instructions +21/01 no login records at that time pls check tbox-log @何文国 +21/01: customer can't use remote control + doesn't see any info about car. Operation time 21.01 12:22",Low,close,local O&M,Evgeniy,13/05/2025,EXEED RX（T22）,LVTDD24B6RG019748,,bound +79179060320,"LOG_LVTDD24B6RG01974820250121161220.tar,image.png",Evgeniy,,,,,,112 +TR413,Mail,21/01/2025,,VK ,The customer can't enter to VK video,,"Feb 26: solved +11/02： waiting customer's feedback +10/02L: cus +02/07 @Evgeniyhave done cloud processing，Now users can check whether the problem is solved and whether VK video is normal and can be used +02/06 pls ask the owner to relogin his VK-account on iHU @Evgeniy + collect the hu-log ",Low,close,local O&M,Evgeniy,26/02/2025,EXEED VX FL（M36T）,LVTDD24B0RD065593,,bound +79883182020,image.png,Evgeniy,,,,,,36 +TR414,Mail,22/01/2025,,Remote control ,Remote control issue: vehicle data is not displayed in remote control app as well as commands are not executed in the remotre control app. Last tbox log 2025-01-22 07:32:46; no apn1 available since 16/01/2025.,"0319：等待OTA +0217 计划暂时关闭此问题 +0205：请提供问题日志 +辛巴已经找运营商看过了，APN1没做任何限制，请@何文国排查TBOX日志 +0225：日志上传中","24/04: no claimes since upgrade => TR closed +03/04: OTA upgrade completed successfully on March, 31st - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +06/03: log upload is still in process. +10/03: recent tbox log attached. +05/03: upload of logs is in progress. +25/02: logs is in process of uploading. +06/02 collect the tbox-log pls @Vsevolod +23/01 APN1 doesn't work @胡纯静 +23/01: time&date - at 18:02 on 22/01, command name - open the trunk, screenshot of the error message attached. +22/01: required data is requested for investigation (date&operation time etc.)",Low,close,TBOX,Vsevolod,24/04/2025,EXEED RX（T22）,LVTDD24BXRG021292,,,"LOG_LVTDD24BXRG021292_10_03_2025.tar,Picture_4.jpg,Picture_3.jpg,Picture_2.jpg,Picture_1.jpg",Vsevolod,,,,,,92 +TR415,Mail,22/01/2025,,Remote control ,Wrong vehicle data is displayed in the remote control app. No commands are executed.,"0319：等待OTA +0217 计划暂时关闭此问题 +0205：请提供问题日志 +辛巴已经找运营商看过了，APN1没做任何限制，请@何文国排查TBOX日志 +0225：车辆处于休眠状态达3 周。请求经销商以收集日志。","24/04: no claimes since upgrade = TR closed +03/04: OTA upgrade completed successfully on March, 31st - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +24/03: customer's feedback: everythng works well besides Navi that is not able to detect right positon of the car - see picture attached +13/03: logs attached and customer is also asked wehther the issue is still valid. +25/02: vehicle is in the hibernation mode for 3 weeks. Request to send to dealer for collecting the log. +06/02 collect the tbox-log pls @Vsevolod +23/01 apn1 doesnt work @胡纯静 +23/01: commands name - open the door/engine start; date&time on 22/01 at 19:50. Screenshots of the error message attached. +22/01: required data is requested for investigation (date&operation time etc.)",Low,close,TBOX,Vsevolod,24/04/2025,EXEED RX（T22）,LVTDD24B9RG013653/89701010050605376664,,13/02: vehicle is still in the hibernation mode.,"Picture_4.jpg,LOG_LVTDD24B9RG013653_13_03_2025.tar,Picture_2.jpg,Picture_3.jpg,Picture_1.jpg",Vsevolod,,,,,,92 +TR416,Mail,23/01/2025,,Remote control ,The customer can't see status of car and can't use remote control.,"0401:TSP尝试远程抓取日志失败，提示车辆已进入深度睡眠。建议使用物理钥匙启动发动机后，等待一会再尝试远控. +0318：等待日志 +0311：使用物理仍无法使用，取Tbox日志 +0304：建议用户使用物理钥匙进行启动发动机，再次进行远程操作尝试 +0228:TBox 进入深度睡眠模式，唤醒失败 +0217:无进展 +0211:会后更新进展 +1/24 MNO已分析流量没有限制，请TBOX分析日志","Apr 17: no feedback ->temporary close +01/04: TSP attempts to remotely capture logs failed, indicating that the vehicle has entered deep sleep. It is recommended to use the physical key to start the engine and wait for a 15 minutes before attempting remote control. +25/03: waiting invitation to the dealer for log +18/03：Need to catch new logs and detail time.@Evgeniy +Mar 11:need the tbox logs +March 04: The user is advised to use the physical key to start the engine and try the remote operation again +Feb 28: TBox enters deep sleep mode, fail to wake up. +Feb 26: still has problem +23.01: operation date 23.01 time - see video ",Low,temporary close,TBOX,Evgeniy,17/04/2025,EXEED VX FL（M36T）,LVTDD24BXPD619459/89701010064499968536,,,"image.png,image.png,tboxlog.tar,IMG_7650.MP4",Evgeniy,,,,,,84 +TR417,Mail,23/01/2025,,Remote control ,Remote control issue - customer can't start the engine remotely via app.,"0325:等待反馈 +0320:等待反馈 +0318：等待反馈 +0311：等待经销商反馈 +0225：经销商至今没有反馈。 +0213：要求经销商写入 TboxPIN码。 +0206: 要求经销商使用诊断工具重写 TBOX 的 PIN 码，确保与 EMS PEPS的 PIN 码一致。 +密码：26506882 +0124：TPS：tsp 在 14/01 16:04 未收到遥控器，请客户尝试，收集客户的操作场景、重现问题后的操作时间 +2025 年 1 月 14 日 @ 16:12:27 启动发动机，但返回 “EMS 验证失败”。 +0123：最后一次 tbox 登录 2025-01-23 10:38:40；最后一次高频数据 2025-01-23 10:45:02；apn1&2 在 MNO 中可用。操作时间和日期 - 14/01 16:04；截图和 tbox 日志附后","25/03: still no feedback. +20/03: still no feedback. +18/03: still no feedback.@Vsevolod Tsoi +05/03: still no feedback. +25/02: no feedback from dealer so far. +13/02: request sent to dealer for writing the pin-code for Tbox. +11/02: still procesing +06/02 ask the dealer to Use the diagnostic tool to rewrite the PIN code for TBOX, ensuring it matches the PIN code with EMS PEPS @Vsevolod +pin-code:26506882 +24/01: TPS: tsp has not recieved the remote control at 16:04 on 14/01, pls ask the customer try, Collect the customer’s operating scenario, operating time after reproducing the problem @Vsevolod +and the starting engine has been excuted at Jan 14, 2025 @ 16:12:27, but return “EMS Authentication failed ” +23/01: last tbox login 2025-01-23 10:38:40; last high frequency data 2025-01-23 10:45:02; apn1&2 are available in MNO. Operation time&date - at 16:04 on 14/01; screenshot attached as well as tbox log",Low,temporary close,local O&M,Vsevolod,01/04/2025,EXEED VX FL（M36T）,LVTDD24B0PD584060,,,"iChery20250206-162300.mp4,LOG_LVTDD24B0PD584060_23_01_2025.tar,Picture_2.jpg,Picture_1.JPG",Vsevolod,,,,,,68 +TR422,Telegram bot,23/01/2025,,Remote control ,Remote control: commands are not executed via remote control app. An error message "time for a response from the server has expired. Please try again later" comes up when executing the command.,"0422:14天未反馈，暂时关闭该问题 +0421：等待用户反馈 +0417：等待用户反馈 +0415：等待用户反馈 +0410：等待用户反馈 +0407：等待用户反馈 +0403：请提供用户远控区域的位置及经纬度，方便排查地区真实网络环境 +0403:TBOX分析，未收到唤醒短信，16:20车辆已点火唤醒,TSP见16:20TBOX登录记录，未见16:10登录记录，MNO反馈唤醒短信发送失败，短信延迟发送，后续短信功能正常，建议用户重新启动车辆后重新尝试远控。@Vsevolod Tsoi +0401：远控时间为3月18日16:10，TSP已见该时间段有TBOX登录记录，远控发动机失败（16:12），获取车辆位置失败(16:12)，已查SIM卡及流量状态正常，等待TBOX分析结果。 +0320：转Tbox分析。远控时间为3月18日16:10，日志已附，请走合规流程申请日志并分析。@王桂玲 +0318：等待用户进站抓取日志 +0311：等待用户反馈 +0304:转TSP分析，tsp 查询35s超时 +0211:tbox反馈需sim排查 +0127:远控等待TBOX响应超时，请王桂玲分析TBOX日志","22/04：No feedback for 14 days, issue temporarily closed +17/04: no feedback so far. +15/04: still waiting for feedback +10/04: still waiting for feedback +07/04: still waiting for feedback from customer on operation and their respective data. +03/04:Please provide the location and latitude/longitude of the user's remote control area to facilitate the investigation of the real network environment in the area.@Vsevolod Tsoi +03/04:TBOX analysis, did not receive wake-up SMS, 16:20 vehicle has ignition wake-up, TSP has seen 16:20 TBOX login record, did not see 16:10 login record, MNO feedback wake-up SMS sending failure, SMS delayed sending, subsequent SMS function is normal, suggest the user to restart the vehicle and then re-try to remote control.@Vsevolod Tsoi +01/04: remote control time is 16:10 on 18 March, TSP has seen TBOX login record in this time period, remote control engine failed (16:12), get vehicle position failed (16:12), have checked SIM card and traffic status is normal, waiting for TBOX analysis results. +20/03:Turn to Tbox analysis +19/03: command name - engine start on March, 18th at 16:10. Tbox log attached. +18/03: Waiting customer go to the dealer for checking. +06/03: customer asked again to execute several commands in different areas of his region. Wait for feedback. +0306：suggest customer try again +11/02:need simba to analyse +27/01 tsp waited feedback timeout Because of waking up TBox spends too much time. +23/01: last tbox login 2025-01-23 16:38:23; high frequency data +2025-01-19 16:22:29; apn1&2 are availabel and active in MNO. Operation time&date - on 23/01 at 16:37, command - engine start, screenshots attached as well as tbox log.Please provide the location and latitude/longitude of the user's remote control area to facilitate the investigation of the real network environment in the area.",Medium,temporary close,MNO,林兆国,22/04/2025,EXEED VX FL（M36T）,LVTDD24B5PD638355,,,"LOG_LVTDD24B5PD638355_19_03_2025.tar,Picture_2.jpg,Permitions.JPG",Vsevolod,,,,,,89 +TR423,Mail,23/01/2025,,Remote control ,The customer can't use remote control + wrong status of car + bad location ,"0217 计划关闭此问题 +0205：请提供问题日志 +MNO侧和运营商网络都没有对APN1进行过任何操作。需要TBOX侧进一步排查分析。@何文国","26 Feb: solved +06/02 collect the tbox-log pls @Evgeniy +27/01 tsp: apn1 didnt work since 19.01 .pls check on MNO side @胡纯静",Low,close,TBOX,Evgeniy,26/02/2025,EXEED RX（T22）,LVTDD24B9RG011756,,bound +79536011490,"image.png,image.png",Evgeniy,,,,,,34 +TR424,Mail,24/01/2025,,Remote control ,Remote control: commands are not executed via remote control app. An error message "Response from server was not successful. Time for response has expired" comes up when executing the command. TSP status: last tbox log - 2025-01-24 17:02:25; high frequency data - 2025-01-24 17:02:23. Apn1&2 are available and active in MNO.,"0306；等待oj反馈关闭问题 +0227：计划 28 日讨论此问题进行关闭 +0217 计划关闭此问题","06/03: feedback from O&J team: the issue is solved. +06/03: request sent to O&J team to figure out the status. +Feb 27:a talk with oj team in Feb 28's meeting +17/02: a request sent to O&J app team to check. Wait for a feedaback. +27/01 tsp hasnot recieved remote command at that time, pls ask app-team to check on app side +24/01: operation date&time - on 23/01 at 21:21; command name - engine start, screenshot attached as well as tbox log.",Low,close,local O&M,Vsevolod,06/03/2025,JAECOO J7（T1EJ）,LVVDB21B7RC070328,,,"LOG_LVVDB21B7RC070328_24_01_2025.tar,Picture_1.jpeg",Vsevolod,,,,,,41 +TR425,Mail,24/01/2025,,Remote control ,"Remote control: commands are not executed via remote control app. An error message ""Response from server was not successful. Time for response has expired"" comes up when executing the command. TSP status: last tbox log - 2025-01-24 17:02:15; high frequency data - +2025-01-24 17:12:57. Apn1&2 are available and active in MNO.",0217 计划关闭此问题,"25/02: O&J app's feedback: there was no any feedback from customer more than 7 days. Issue us codsidered as closed. +25/02: status of request in O&J - done. Wait for feedback from O&J team if the issue can be closed. +17/02: request sent to O&J app for investigation. +27/01 tsp hasnot recieved remote command at that time, pls ask app-team to check on app side +24/01: operation date&time - on 23/01 at 22:41; command name - engine start, screenshot attached as well as tbox log.",Low,close,local O&M,Vsevolod,25/02/2025,JAECOO J7（T1EJ）,LVVDD21BXRC054389,,,"LOG_LVVDD21BXRC054389_24_01_2025.tar,Picture_3.jpg,Picture_1.jpg,Picture_2.jpg",Vsevolod,,,,,,32 +TR426,Mail,27/01/2025,,Remote control ,Remote control doesn't work + wrong status of car ,"0217 计划关闭此问题 +0205：app下发车控，tsp未收到车控指令，请APP和TSP排查 +MNO侧和运营商网络都没有对APN1进行过任何操作。需要TBOX侧进一步排查分析。@何文国","Feb 26: solved +06/02 collect the tbox-log pls @Evgeniy +6/2 MNO：MNO and MTS side have no restriction and issue on APN1 , need device side to further check +27/01: tsp: tsp didnt recieved the remote command at that time, and apn1 didnt work since 23.01 .pls check on MNO side @胡纯静 +27/01: operation date&time - on 27/01 at 00:09",Low,close,TBOX,林小辉,26/02/2025,EXEED RX（T22）,LVTDD24B8RG019850,,bound +79131489742,"LOG_LVTDD24B8RG01985020250127114825.tar,image.png,image.png",Evgeniy,,,,,,30 +TR427,Telegram channel,27/01/2025,,Remote control ,"Remote control: remote engine start command is not executed via remote control app. An error message ""Operation failed. Please make a request on the issue via feed-back form"" comes up when executing the command. TSP status: last tbox log - 2025-01-27 09:15:26; high frequency data - +2025-01-27 09:15:24. Apn1&2 are available and active in MNO.",0217 计划关闭此问题,"25/02: remote control started working. Wait for feedback from customer if the issue can be closed. +17/02: customer asked if the issue stiil valid. If so, required data will be provided for investigation. +27/01 pls collect the Operation time of the problem",Low,close,local O&M,Vsevolod,27/02/2025,EXEED VX FL（M36T）,LVTDD24B7PD606426,,,Video_1.mp4,Vsevolod,,,,,,31 +TR429,Mail,28/01/2025,,Remote control ,Remote control issue: remote engine start does not work via app. Last tbox log - 2025-01-28 06:40:09; high frequency data - 2025-01-28 06:40:00; Apn1&2 are OK in MNO.,0217 计划关闭此问题,"07/04: still wait for feedback. +25/03: repeat request to customer to execute an operation and provide then the respective data for investigation. Wait for feedback. +19/03: client is asked for feedback whether the problem is still valid. If so, required data for investigation will be requested. +Feb 27:still waiting customer's feedbcak +03/02: customer is asked again to provide the needed input data. Wait for a feed-back (by email). +2/2 TSP :Tsp has not received the command from app at that time .PLS Collect the customer’s operating scenario, operating time after reproducing the problem @Vsevolod +28/01: command name - engine start, time&date - on 26/01 at 15:34, screenshot attached. Tbox log is in process.",Low,temporary close,local O&M,Vsevolod,27/02/2025,JAECOO J7（T1EJ）,LVVDB21B0RC071563,,dasha-0215@mail.ru,"LOG_LVVDB21B0RC071563_28_01_2025.tar,Picture_1.jpeg",Vsevolod,,,,,,30 +TR430,Mail,28/01/2025,,Remote control ,"Remote control issue - engine is not started remotly via app => error message ""respond from the server was not successful. Time for response has expired"". TSP stauts: last tbox login 2025-01-29 10:40:05, high frequency data - 2025-01-29 10:42:37. MNO status: apn1&2 are available and active.","0422：属地会后确认 +0421：等待日会结果反馈，无异议后关闭 +0417:一致协商确定下次日会没有反馈，关闭该问题。 +0416：用户反馈在别处测试，远控生效 +0410：等待用户反馈 +0407：等待用户反馈 +0401：会后联系用户确认状态及详细位置信息 +0327: TBOX日志分析 短信延迟 9:40收到短信唤醒.建议用户在信号好的地方重启车机，并尝试远控.建议提供具体的住址信息。 +0325：会后转TBOX分析@刘海丰 +0325:客户又来询问何时能解决问题。因此，问题仍然存在。远控时间：3月25日 9:24 。新的相关日志附后。 +0226： +经TBOX日志查询，TBOX没有收到短信唤醒 +0225：转tbox进行分析@刘海丰 +0218 转国内分析","22/04：after meeting check +21/04: Awaiting feedback on the outcome of the day session, to be closed without objection. +17/04:Unanimous consultation determined that there would be no feedback the following day to close the issue.@Vsevolod Tsoi +16/04: customer's feedback: tried to execute the engine start having the car in another place => execution completed successfully. +10/04: still wait for feedback. +07/04: still wait for feedback. +01/04:Contact the user after the meeting to confirm the status and detailed location information +27/03:TBOX log analysis: SMS delayed 9:40 received SMS.Users are advised to restart the car in a place with good signal and try remote control. +25/03: engine start was executed once again on March, 25th at 12:18. tbox log attached. +25/03: customer is back asking when the problem is going to be solved. So, problem is still valid. Command name - engine start on March, 25th at 9:24. New respective log attached. +18/02: command name - start of the engine on 18/02 at 10:36 (8:36 Moscow time), screenshot attached as well as tbox log. +17/02: customer asked if the issue is still valid. If so, the required data fro investigation will be requested +2/2 Tsp has not received the command from app at that time .PLS Collect the customer’s operating scenario, operating time after reproducing the problem @Vsevolod +29/01: command - engine start, date&time - 28/01 at 12:20 (Moscow), screent shot of an error message attached as well as tbox log",Low,temporary close,local O&M,Vsevolod,24/04/2025,JAECOO J7（T1EJ）,LVVDD21B5RC053182,,,"LOG_LVVDD21B5RC053182_25_03_2025_V2.tar,LOG_LVVDD21B5RC053182_25_03_2025.tar,LOG_LVVDD21B5RC053182_18_02_2025.tar,Picture_2.JPG,LOG_LVVDD21B5RC053182_29_01_2025.tar,Picture_1.jpg",Vsevolod,,,,,,86 +TR431,Mail,29/01/2025,,Problem with auth in member center,Customer can't log in member center with QR code coming up in IHU. Error message "Found QR code is not conform". Customer was reseting IHU for factory settings => no result. Desactivating remote control (unbinding the vehicle) in the remote control app => no result. IHU reboot => no result. Automatic synchronization of time and date is ON. Vehicle status in the TSP: last tbox login - 2025-01-29 13:47:16; high frequency data - 2025-01-29 13:47:06. MNO status: apn1&2 are active.,"0401：继续等待 +0325：等待OJ反馈 +0320：等待OJ团队反馈 +0318：等待属地运维反馈错误提示 +0311：周五跟进 +0225：O&J 反馈无法支持 +0217：同TR433 ，待属地运维修改数据后恢复正常即可关闭 +0211：等待属地app运维反馈app报错原因","08/04: remote control started working => solved. +07/03: customer's feedback: he had wrong VIN number in his registration document that ofcourse had been used for remote control => this has been corrected. Right VIN is LVVDD21B3RC053732. So, current VIN needs to be deleted in the mobile app and then new one should be bound. Wait for feedback. +27/03:Still waiting. +25/03: stiill wait for the feedback on error code from O&J team. +20/03：Waiting for feedback from O&J on error code. +1803：Waiting for feedback from local O&M on error code. +0304：Discussion at Friday's meeting +25/02: feedabck from O&J team: they cannot support in the issue from their side. +11/02:Waiting for feedback from territorial app ops on why the app is reporting errors +06/02: current status - sim card acitivated, all apps work well. The only issue is that the customer tries to to enter to the member center with QR code coming up when opening the personal account in IHU. When scanning QR code an error message comes up ""Found QR code is not conform"". But actually log in had already been done. +06/02 CABIN: pls ask O&J-app-team to check the err-message on the first picture. +2/2 TSP: APN1& APN2 work well, and the car was bound on tsp. pls check the reason ",Low,close,O&J-APP,Vadim,08/04/2025,JAECOO J7（T1EJ）,LVVDD21B2RC052622 => right one LVVDD21B3RC053732,,,"IMG_5032.MP4,Picture_3.JPG,Picture_1.jpeg,Picture_2.jpeg",Vsevolod,,,,,,69 +TR432,Mail,30/01/2025,,Remote control ,Remote control issue - engine is not started remotly via remote app. TSP status: last tbox login - 2025-01-24 09:27:48; frequency data - 2025-01-30 11:14:53. MNO: apn1 - OK.,0319：等待OTA0217 计划关闭此问题,"24/04: no issues since the upgrade => TR closed +03/04: OTA upgrade completed successfully on April, 2nd - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +06/03: no apn1 available since Feb, 4th. Would ti mean that this car needs to be updated with new OTA in march ? +06/02 collect the tbox-log pls @Vsevolod +5/2 MNO：MNO and MTS side have no restriction and issue on APN1 , need device side to further check +2/2 tsp: the APN1 didnt work, pls check on MNO side @胡纯静 +30/01: command name - engine start, date&time - 30/01 at 7:05 Khabarovsk time (14:05 Moscow). Screenshot attached. tbox log upload is in process.",Low,close,MNO,Vsevolod,24/04/2025,EXEED RX（T22）,LVTDD24B3RG019934,,,Picture_1.jpg,Vsevolod,,,,,,84 +TR433,Telegram bot,03/02/2025,,Remote control ,"Customer can't log in member center with QR code - ""Bad connection"" error - QR is not loading. +Tried with Wi-Fi - result the same +In PKI platform IHU check ""The user does not exist""","0227：该问题已经修复，等待用户反馈 +0218:等待属地运维询问问题是否关闭 +0217：同TR436，计划关闭此问题 +0211: +运维反馈该问题仍然存在","March11. Solved -> closed after customer feedback +feb 27:need local om confrim this issue exist or not +11/02:this issue still exist +PLS add info which data we should collect",Low,close,PKI,Kostya,11/03/2025,JAECOO J7（T1EJ）,LVVDB21B1RC071488,,,"image.png,image.png",Kostya,,,,,,36 +TR434,Mail,04/02/2025,,Remote control ,"Engine start command is not executed remotly via app. Error message ""Response from server was not successful. Time for response has expired"". Vehicle status in the TSP: last tbox login +2025-02-04 13:23:56, high frequenct data +2025-02-04 13:26:27. MNO: apn1&2 are available and operational.","0227：等待用户反馈 +0217：计划关闭此问题 +0211：联系用户确认该问题是否仍然存在，不存在就关闭问题 +07/02 经过日志分析，TBOX没有接到短信 请转平台端排查 +UTC时间,换算成KM时间,最后一条短信接收时间是2月3日早上8点53分37秒,这之后就没收到过信息","March 6: Omoda team asked us to close the problem +Feb 27:waiting feedbcak +17/02: customer asked if the issue is still valid. If so, reproducing of a problem will be requested with rpoviding then all the respective input data. +11/02: Contact the user to confirm that the issue still exists and close the issue if it doesn't +06/02 TSP: waking up TBox spends too much time,pls check the tbox-log @王浩博 +04/02: operation time&date - 03/02/2025 at 9:43, command - engine start, screenshot/tbox log attached.",Low,close,local O&M,Vsevolod,06/03/2025,JAECOO J7（T1EJ）,LVVDD21B2RC052717,,,"LOG_LVVDD21B2RC052717_04_02_2025.tar,Picture_1.PNG",Vsevolod,,,,,,30 +TR435,Telegram bot,04/02/2025,,Remote control ,"Remote control issue: none of the commands is not executed via remote control app. Car status in TSP: last tbox login 2025-02-04 11:12:37, last high frequency data 2025-02-04 11:23:31. MNO status: both apn1&2 are available and active.",0319：等待OTA0217：询问属地运维情况,"03/04: upgrade complete on March, 24th. No any issues since update. +0217: Inquiries about territorial O&M +06/02 tsp: Tsp has received the command from app at 17:44 Russia time but failed, tsp waited tbox feedback timeout , waking up TBox spends too much time +but no stating engine command at 16:45 (Moscow time) +06/02 command - engine start, time&date on 05/02 at 16:45 (Moscow time). Screenshots attached.",Low,close,local O&M,Vsevolod,03/04/2025,EXEED RX（T22）,LVTDD24B7RG032153,,TGR0000480,"image.png,Picture_4.jpg,Picture_3.jpg",Vsevolod,,,,,,58 +TR436,Telegram bot,07/02/2025,,VK ,"Customer can't use VK video on HU. According to customer everything else works fine. +No any abnormal data on platforms","0214: 个别历史遗留数据受影响，IHUID需属地运维手动修改，后续版本不会出现此问题 +0211：专题群讨论","0218: Solved +0214: Individual historical legacy data is affected, IHUID needs to be manually modified by local O&M, this issue will not occur in subsequent versions. +0211: Thematic group discussion +07/02 VK license issue in VK video App +Short HU sn Pki -> Long HU sn",Low,close,PKI,喻起航,18/02/2025,EXEED RX（T22）,LVTDD24B8RG019864,,,image.png,Kostya,,,,,,11 +TR437,Mail,12/02/2025,,Remote control ,The customer can't use remote control,"0318： 等待顾客反馈 +0312：最近一次远控当地时间2025-03-09 10:24:26.956，显示远控成功 +0311：顾客反馈仍然无法使用，重新抓取日志 +0227：等待用户反馈该问题是否仍然存在，若恢复正常，则关闭该问题 +0217：经后台查询，因用户车辆当时处于信号不好的地点，车辆未收到远控指令，后续查看功能可正常使用，建议用户再观察使用，若还有问题，建议再次反馈且提供相关日志。 +0213: 当地时间11:11对应UTC时间8:11，日志上看11:11TBOX处于Sleep状态，TBOX没有收到短信唤醒，日志上也没有收到短信记录，与TSP失去连接，因此收不到车控指令。13分27秒才被上电唤醒; 没收到短信唤醒,转平台处理 +0213：转tbox进行分析 ","March 12: The most recent remote control was successful on 2025-03-09 10:24:26.956 local time. @Evgeniy +Feb 27： ask customer to try again about remote control this function,if ok we can close this issue +Feb 17：After the background inquiry, because the user's vehicle was in a bad signal location, the vehicle did not receive the remote control command, the follow-up view function can be used normally, it is recommended that the user again to observe the use, if there are still problems, it is recommended to feedback and provide relevant logs again. +Feb 14: +0213: Local time 11:11 corresponds to UTC time 8:11, logs show that TBOX is in Sleep state at 11:11, TBOX did not receive SMS wakeup, logs also did not receive SMS records, and TSP lost connection, so it could not receive car control commands. 13 minutes 27 seconds before being woken up by the power supply; did not receive the SMS wakeup, transferred to the platform to handle +0213: transfer tbox for analysis +12/02 : Operation time: 11/02/2025 at 11:11",Low,temporary close,local O&M,Evgeniy,18/03/2025,JAECOO J7（T1EJ）,LVVDD21B9RC053184,,bound 79272197355,"img_v3_02jf_5b7f937f-49f8-43fc-8b8c-b4d4d1c0b3ag.jpg,LOG_LVVDD21B9RC05318420250212131105.tar,image.png",Evgeniy,,,,,,34 +TR438,Mail,13/02/2025,,Remote control ,"After remote start of the engine, after switching on the seat heating, the keyless entry settings are reset, and if I switch on the mirror heating, the projection is switched off.","0318：等待抓取日志 +0227：取得日志 +0213:需要日志进行分析，请提供DMC和tbox日志","25/03: temporary close +18/03：Need to catch new logs and detail time.@Evgeniy +Feb 27:get log +0213:Need logs for analysis, please provide DMC and tbox logs ",Low,temporary close,TBOX,Evgeniy,25/03/2025,EXEED VX FL（M36T）,LVTDD24B6RD030427,,,,Evgeniy,,,,,,40 +TR439,Telegram bot,14/02/2025,,Remote control ,The customer can't use remote control/doesn't see status of car.,"0217：经后台查询，因用户车辆当时处于信号不好的地点，车辆未收到远控指令，后续查看功能可正常使用，建议用户再观察使用，若还有问题，建议再次反馈且提供相关日志。 +0214:转开发分析TSP平台日志中，车辆当时处于不在线状态，TSP平台发送唤醒短信成功，tbox未成功上线，超时35S，转tbox分析 ","Feb 26: Solved +Feb 17：After the background inquiry, because the user's vehicle was in a bad signal location, the vehicle did not receive the remote control command, the follow-up view function can be used normally, it is recommended that the user again to observe the use, if there are still problems, it is recommended to feedback and provide relevant logs again. +0214: turn development analysis TSP platform logs, the vehicle was in the state of not online, the TSP platform to send wake-up SMS successful, tbox unsuccessful online, timeout 35S, turn tbox analysis +14/02: Operation date/time 13.02 at 19:37",Low,close,TBOX,Evgeniy,26/02/2025,CHERY TIGGO 9 (T28)）,LVTDD24B3RG087103,,bound 79197687091,image.png,Evgeniy,,,,,,12 +TR443,Telegram bot,10/02/2025,,Remote control ,"Remote control issue: wrong data is displayed, no commans are executed in app. Vehicle status in TSP: last tbox login 2025-02-10 06:19:34, high frequency data - 2025-02-10 06:51:53. Status in MNO: apn1&2 are available and active.","0515：暂时关闭该问题 +0515：平台查询到用户近日多条远控记录，可关闭该问题 +0424:已下载升级，但尚未应用。等待升级。 +0304:等待用户反馈 +0217：经后台查询，因用户车辆当时处于信号不好的地点，车辆未收到远控指令，后续查看功能可正常使用，建议用户再观察使用，若还有问题，建议再次反馈且提供相关日志。 +0214:转开发分析TSP平台日志中，车辆当时处于不在线状态，TSP平台发送唤醒短信成功，tbox未成功上线，超时35S，转tbox分析","15/05：Suggest temporarily shutting it down. If the user finds that there are still issues, restart the problem +15/05:The platform has found multiple remote control records of the user in recent days, and this issue can be closed. +24/04: upgrade downloaded but not applied yet. Wait for upgrade. +March 4：need customer feedback +Feb 17：After the background inquiry, because the user's vehicle was in a bad signal location, the vehicle did not receive the remote control command, the follow-up view function can be used normally, it is recommended that the user again to observe the use, if there are still problems, it is recommended to feedback and provide relevant logs again. +Feb 14： turn development analysis TSP platform logs, the vehicle was in the state of not online, the TSP platform to send wake-up SMS successful, tbox unsuccessful online, timeout 35S, turn tbox analysis +10/02: customer opened the mobile app on 10/02 at 11:02, vehicle engine is shown as started however vehicle is parked and actually the engine is stopped. Then the customer tried to stop the engine clicking on button ""stop"", some time has passed and then there was an error message ""Time for the response from server has expired. Please try again later"". ",Medium,temporary close,TBOX,Vsevolod,15/05/2025,EXEED RX（T22）,XEYDD14B3RA002651,,TGR0000509,"Picture_3.jpg,Picture_2.jpg",Vsevolod,,,,,,94 +TR447,Mail,14/02/2025,,Remote control ,"The application concluded. indicates that the driver's door is open and the engine is running, the mileage is old. the commands don't work, the update doesn't help. do something about it. I can't warm up the car, it all started about two weeks ago.",0319：等待OTA0217：经后台查询，因用户车辆当时处于信号不好的地点，车辆未收到远控指令，后续查看功能可正常使用，建议用户再观察使用，若还有问题，建议再次反馈且提供相关日志。,"13/05: upgrade success-problem solved +24/04: still wait for upgrade. +17/04: downloaded but not installed +03/04: downloaded +17/04：After the background inquiry, because the user's vehicle was in a bad signal location, the vehicle did not receive the remote control command, the follow-up view function can be used normally, it is recommended that the user again to observe the use, if there are still problems, it is recommended to feedback and provide relevant logs again. +14/02: Operation date 14.02 - operation time-see screenshots",Low,close,车控APP(Car control),Evgeniy,13/05/2025,EXEED RX（T22）,LVTDD24B3RG031453,,,"image.png,image.png,image.png",Evgeniy,,,,,,88 +TR448,Telegram bot,14/02/2025,,Application,Customer can't use VK video app. An error message comes up "License activation was not successful" - see screenshot attached. Others apps work well.,"0227：问题解决 ，等待用户反馈。 +0224:该问题已经修复，等待属地运维咨询用户是否问题解决，进而进行问题关闭。 +0221: +1.问题原因： +由于VK Video的新版本更新，用户从旧版本通过应用市场升级到新版本导致了在雄狮的存储中有两个相同的应用ID从而用户无法使用软件 +2.临时解决方案： +由雄狮老师对该用户的车辆应用ID修改，后续我们这边与雄狮老师确定更好的方案，目前VK也针对此问题做出对应的修改，即使在用户无网络状态下只要激活过，下次也可以校验通过减少出现激活失败的情况。 +3.遇到此类问题的排查方向： +VK在激活失败页面新增了报错提示，通过用户的提示可以更加直观分析出问题的发生情况，比如激活校验失败，PKI失败等等 +4.后续避免方案： +后续VK优化激活逻辑版本应用迭代可以减少此类问题发生，其次正在与雄狮的老师商讨出现问题时自动上报日志的可行性，敲定后此类问题即使出现也是小概率时间，出现后解决问题的方向也会更加明确 +0217:转信源分析@张鹏飞","0227：issue fixed ，waiting customer feedback +0221. +1: +Due to the new version update of VK Video, users upgrading from the old version to the new version through the app market have two identical app IDs in Lion's storage and thus users are unable to use the software. +2.Temporary solution: +By the Lion teacher to the user's vehicle application ID modification, followed by our side and the Lion teacher to determine a better solution, the current VK also for this problem to make the corresponding changes, even if the user no network state as long as the activation of the next time can be verified through the activation to reduce the failure of the situation. +3. The direction of troubleshooting this kind of problem: +VK has added an error message on the activation failure page, which can be used to analyze more intuitively the occurrence of the problem, such as activation verification failure, PKI failure and so on. +4. Subsequent avoidance program: +Subsequent VK optimization activation logic version of the application iteration can reduce the occurrence of such problems, and secondly, we are discussing with Lion's teachers the feasibility of automatically reporting logs when a problem occurs, after finalizing such problems even if they occur is a small probability of time, after the emergence of a solution to the problem will also be more clear in the direction of the problem. +0217:Transfer source analysis Pengfei Zhang",Low,close,生态/ecologically,张鹏飞,06/03/2025,CHERY TIGGO 9 (T28)）,LVTDD24BXRG087843,,TGR0000593,Picture_1.jpg,Vsevolod,,,,,,20 +TR451,Mail,17/02/2025,,Remote control ,"Remote control doesn't work. An error message comes up ""command is not executed. Please try again on the engine started "" when tying to execute the command activation air conditionning. TSP status: last tbox login 2025-02-09 11:26:08; high frequency data on 2025-02-09 11:03:56. MNO: no apn1 working since Jan, 9th.","0218: +1.转辛巴分析中，流量使用正常， +2.转TSP分析，车辆于2月15日处于深度睡眠模式，建议用户钥匙启动车辆后再次尝试远控","24/02: customer's feedback: remote control started working again. The issue is solved. +18/02: after getting in contact with customer at 15:38 vehicle was running and using. No apn1 available leads to no executing of a remote command. Customer still can't use remote control. +Feb 18： +1. In the trans-Simba analysis, the flow rate is used normally, the +2. to TSP analysis, the vehicle was in deep sleep mode on February 15, suggesting that the user key start the vehicle and then try remote control again +17/02: command name - air conditionning on 17/02 at 13:14 (12:14 Moscow time). Screenshot attahed.",Low,close,TBOX,Vsevolod,24/02/2025,EXEED RX（T22）,LVTDD24B7RG031441,89701010050664705050,,Picture_1.jpg,Vsevolod,,,,,,7 +TR452,Mail,17/02/2025,,Remote control ,Remote control doesn't work + wrong status of car.,"0529：等待更新 +0520：等待刷新 +0515:等待用户进站换件 +0513: 所有远控操作仍然失败。需要更换tbox。已要求ASD团队启动tbox更换程序 +0429：会上建议用户进站，解除深度睡眠，如所有操作都无法解决，建议换件 +0427：等待属地与客户确认 +0424：等待属地与客户确认 +0421：TBOX侧反馈是否换件可以解决问题，明日日会，确认问题状态，是无法解除深度睡眠，或其他情况 +0417：建议用户进站换件 +0415：等待用户反馈是否可用 +0410：等待用户反馈状态 +0407：继续等待用户反馈 +0401：TSP尝试远程抓取日志失败，提示车辆已进入深度睡眠。建议使用物理钥匙启动发动机后，等待一会再尝试远控. +0325：尝试使用物理密钥启动 -> 结果相同 +0325：会后检查 +0320：本周车辆未启动，建议用户使用物理钥匙启动车辆，并重新尝试远控 +0318：会后检查远控 +0227：未取得日志转入分析 +0218：转TSP分析，车辆于2月15日处于深度睡眠模式，建议用户钥匙启动车辆后再次尝试远控","05/06: tbox was changed, wating for result +15/05：Waiting change tbox +13/05 all operation still failed. need to change tbox. already asked ASD team to launch procedure of changing tbox +29/04:At the meeting, the user was advised to come in and release the deep sleep, and if all operations failed to solve the problem, it was recommended to change the TBOX. +27/04: Waiting for confirmation between the locality and the customer +24/04: Waiting for confirmation between the locality and the customer +21/04:TBOX side feedback on whether changing parts can solve the problem, tomorrow day meeting, to confirm the status of the problem, is not able to lift the deep sleep, or other circumstances. +17/04: asked ASD team invite the customer for replace TBOX +15/04: Waiting for user feedback on availability +10/04: Waiting for user feedback status +07/04: Continue to wait for user feedback +01/04:TSP attempts to remotely capture logs failed, indicating that the vehicle has entered deep sleep. It is recommended to use the physical key to start the engine and wait for a 15 minutes before attempting remote control. +25/03:after meeting check +25/03: tried to start with physical key -> result is the same +20/03:The vehicle did not start this week and the user is advised to start the vehicle with the physical key and retry the remote control. +Mar 18/03: Post-conference inspection of remote control.@赵杰 +27/02:get log and waiting analysis +18/02: The customer has already started car and nothing happend-> the car still stay in deep sleep mode +18/02: Turning to TSP analysis, the vehicle was in deep sleep mode on February 15, suggesting that the user key start the vehicle and try remote control again. @Evgeniy +17/02: Operation date :15.02 at 12:42",Low,close,车控APP(Car control),Evgeniy,05/06/2025,EXEED VX FL（M36T）,LVTDD24B2PD384362,,,"image.png,image.png,image.png",Evgeniy,,,,,,108 +TR453,Mail,17/02/2025,,Remote control ,Remote control doesn't work ,0319：等待OTA0218：经后台查询，因用户车辆当时处于信号不好的地点，车辆未收到远控指令，后续查看功能可正常使用，建议用户再观察使用，若还有问题，建议再次反馈且提供相关日志。,"Apr17: solved after OTA +03/04: OTA upgrade completed successfully on April, 1st - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +Feb 18：After the background inquiry, because the user's vehicle was in a bad signal location, the vehicle did not receive the remote control command, the follow-up view function can be used normally, it is recommended that the user again to observe the use, if there are still problems, it is recommended to feedback and provide relevant logs again. @Evgeniy +17:02: 14.02 at 22:38",Low,close,车控APP(Car control),Evgeniy,17/04/2025,EXEED RX（T22）,LVTDD24B0RG031393,,,image.png,Evgeniy,,,,,,59 +TR454,Mail,17/02/2025,,doesn't exist on TSP,TE1J with IOV but doesn't exist on TSP platform ,"0226：无异常数据，该问题关闭 +0220：需运维筛查数据，如无历史数据则关闭； +0218： +1.转pdc分析，该车辆存在于TSP 正式环境，但是无TBOX信息, +2.详细TBOX信息见Note +3.具体车辆缺失信息原因排查中，涉及车辆数量排查中","0218: +1. to pdc analysis, the vehicle exists in the TSP official environment, but no TBOX information, the +2.Detailed TBOX information see Note +3. The reasons for missing information on specific vehicles are being investigated, and the number of vehicles involved is being investigated.",Low,close,TSP,喻起航,26/02/2025,JAECOO J7（T1EJ）,LVVDB21B8RC107189,,"SN：FCOT1EEE527M069# +ICCID：89701010050664784857","Телематика Фев 15 2025 (002).jpg,Телематика Скриншот Фев 15 2025.jpg",Evgeniy,,,,,,9 +TR455,Telegram bot,18/02/2025,,Remote control ,"Remote control issue: vehicle data is not displayed in the app, commands are not executed. Vehicle status in the TSP: last tbox login 2025-02-15 07:28:43, high frequency data 2025-02-10 07:24:38. Status in the MNO: no apn1 available and active since Feb, 10th.","0605:问题暂时关闭，待抓到日志或问题再次出现开启 +0603: 建议问题关闭，5月15日已经提出日志收集请求，超过20天 +0529：等待更新 +0520：等待更新 +0519：已超过两周未回复，暂时关闭 +0513：协商一致，暂时关闭 +0429：等待用户进站 +0427：等待用户进站 +0425：等待用户进站 +0424：等待用户进站 +0422：等待属地运维确定 +0421：等待进度反馈 +0417：建议客户进站取TBOX日志 +0410：客户使用实体钥匙启动发动机，等待了 20 分钟，但车辆没有从休眠模式中醒来 - 请参见附图。在手机应用程序中无法执行命令。这是否意味着需要更换 TBOX ECU？最后一次 TBOX 登录 2025-02-15 07:28:43，高频数据 2025-02-10 07:24:38。 +0408：等待用户反馈 +0402：问题重新启用，TSP检查车辆已进入深度睡眠，建议用户使用物理钥匙进入车辆并启动车辆，重新尝试远控，如远控异常，请记录异常操作、异常时间点，及截图方便后续排查 +0328：客户依然遇到远控问题，远控指令失效。 +0319：等待顾客反馈已超过两周，如依然无反馈，建议暂时关闭 +0318: 等待用户反馈 +0311：等待顾客反馈 +0220：经后台查询，因用户车辆当时处于信号不好的地点，车辆未收到远控指令，后续查看功能可正常使用，建议用户再观察使用，若还有问题，建议再次反馈且提供相关日志。 +Feb 19:转国内TSP工程师分析","0605:Issue temporarily closed, to be caught in the log or the issue reappears open +05/06: wait for feedback. +03/06: still wait for +29/05: still wait for tbox from dealer. +19/05: no close possible as request to collect TBOX log has only been sent on May, 15th. +0519: More than two weeks without reply, temporarily closed +15/05: request for getting TBOX log has been sent. Wait for feed-back from dealer. +29/04：waiting customer go to dealer +27/04：waiting customer go to dealer +25/04：waiting customer go to dealer +24/04：waiting customer go to dealer +22/04: Awaiting feedback on progress. +21/04: Awaiting feedback on progress. +17/04：Suggest customer go to dealer for tbox logs.@Vsevolod Tsoi +10/04: customer started the engine wiht physical key, waited for 20 minutes but vehicle did not come out of hibernation mode - see picture attached. No commans possible to execute in the mobile app. Does it mean TBOX ECU needs to be replaced? Last tbox login 2025-02-15 07:28:43, high frequency data 2025-02-10 07:24:38. +April 07: Waiting for customer feedback +April 02：The problem is re-enabled, the TSP checks that the vehicle has entered deep sleep, and suggests that the user use the physical key to enter the vehicle and start the vehicle, and retry the remote control, such as the remote control is abnormal, please record the abnormal operation, the abnormal time point, and the screenshot for the convenience of subsequent troubleshooting. +March 28: customer still has the issue with remote control - commandes are not executed. +March 19:Waiting for customer feedback for more than two weeks, if there is still no feedback, recommend temporary closure.@Vsevolod Tsoi +March 18: Still Waiting. @Vsevolod Tsoi +March 11: Waiting for customer feedback +Feb 20After the background inquiry, because the user's vehicle was in a bad signal location, the vehicle did not receive the remote control command, the follow-up view function can be used normally, it is recommended that the user again to observe the use, if there are still problems, it is recommended to feedback and provide relevant logs again. +18/02: customer asked for reproducing the problem with futher providing the required input data.",Low,temporary close,车控APP(Car control),Vsevolod,05/06/2025,CHERY TIGGO 9 (T28)）,LVTDD24B5RG091332,,TGR0000627,"Hibernation_mode.JPG,Picture_1.jpg",Vsevolod,,,,,,107 +TR458,Mail,19/02/2025,,Remote control ,Remote control doesn't work +wrong status,"0319：等待OTA0220：已知TBOX网络阻塞问题，待后续OTA或者进站软件升级 +0219： +1.转 TSP 国内分析 TSP 端日志@张石树 +2.TBOX log 已抓取，转专业分析@何文国","03/04: OTA upgrade completed successfully. No any issues since ugrade. +Feb 20: Known TBOX network blocking issue, pending subsequent OTA or inbound software upgrade +19/02: operation time 18/02 at 17:57",Low,close,TBOX,Evgeniy,03/04/2025,EXEED RX（T22）,LVTDD24B7RG032105,,,"LOG_LVTDD24B7RG03210520250219115848.tar,image.png",Evgeniy,,,,,,43 +TR460,Telegram bot,20/02/2025,,Remote control ,Remote control issue: vehicle is shown in the remote control app as unlocked and started but in fact it is locked and the engine stopped. When trying to stop the engine in the app an error message comes up "Time for the response has expired. Please try again later" - see attached.,"0319：等待OTA0225：2月20日13：22发出停止发动机指令，用户尝试熄火但实际已熄火了，附图 +0224：属地运维已经提交USB刷写tbox清单，刷写后若问题解决，则问题关闭。","24/04: no issues since upgrade => TR closed +03/04: OTA upgrade completed successfully on March, 31th - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +25/02: command name - engine stop on 20/02 at 13:22. Customer tried to stop the engine although in fact it was already stopped. Picture attached. +24/02: this car was not included into the list of 41 cars for TBOX SW upgrade. Should it be in? +Feb 24：If the issue is resolved after USB refresh, the issue is closed. +20/02: vehicle status in the TSP: last tbox login 2025-02-19 17:18:30, high frequency data 2025-02-19 18:31:08. Status in the MNO: acces to the network is granted. Apn1&2 are available and active.",Low,close,TBOX,Vsevolod,24/04/2025,EXEED RX（T22）,LVTDD24B2RG032562,,TGR0000654,"Picture_3.jpg,Picture_2.jpg,Picture_1.jpg",Vsevolod,,,,,,63 +TR461,Mail,20/02/2025,,Application,The customer can't bound the car in APP. Error : А07913,0224：该问题已经在“TELEMATICA APP”解决·，可关闭该问题,0224: The problem has been solved in the "TELEMATICA APP" - the problem can be closed!,Low,close,用户EXEED-APP(User),Evgeniy,24/02/2025,EXEED VX FL（M36T）,LVTDD24B6PD593801,,,"image.png,image.png",Evgeniy,,,,,,4 +TR462,Telegram bot,20/02/2025,,Activation SIM,"Customer can't activate the remote control. Following the checking IHU ID record in the TSP a message comes up ""Request param error:param tBoxSn is inconsistent with the TSP T-BoxS"". Feedback from 2nd line: ""The production data is this FCOT1EEE527M253#, and it cannot be confirmed whether the actual car has been replaced with parts."" Dealer's feedback ""no repair had been done on the vehicle"". +客户无法激活远控。 在 TSP 中检查 IHU ID 记录后，出现一条信息 ""Request param error:param tBoxSn is inconsistent with the TSP T-BoxS""（请求参数错误：参数 tBoxSn 与 TSP T-BoxS 不一致）。 第二行反馈： ""生产数据是此 FCOT1EEE527M253#，无法确认实车是否已更换部件""。 经销商反馈 ""未对车辆进行过维修""。","1119：TSP库里的tboxSN多了一个空格，已修改，请客户再次尝试,如果问题解决了就可以关闭此问题。 +1118：TR系统已重新启用，因所需数据已提交——详见工程菜单中附带的DMC&TBOX数据截图及最新Tbox日志。 +0807: 暂时关闭。将在获取 TBOX 数据时重新开放。 +0804:目前暂无进展 +0728：等待客户进站读取实车信息 +0725：等待客户进站读取实车信息 +0320：继续等待 +0318：继续等待 +0318：继续等待 +0311：无进度反馈 +0221：等待经销商信息返回 （dealer）","24/11: remote control was restored. TR closed. +19/11: Tbox started loging in. The user was asked to try binding his car in the app. +19/11:An extra space has been added to tboxSN in the TSP library. This has been rectified; please ask the client to try again.If the issue has been resolved, you may close this case.@Vsevolod Tsoi +18/11: TR re-opened since the requested data was provided - see attached DMC&TBOX data photo from engineering menu as well as the latest Tbox log +07/08: closed temporarily. Will be-reopened when getting TBOX data. +04/08: no feedback so far. +31/07: still the same status +28/07: invitation of customer for collecting TBOX data is still pending. +22/07: TR was opened again because customer still was unable to enter into member center. TSP says that TBOX SN doesn't match to one installed in the car. A request for collecting TBOX data has been sent to dealer. +10/04:temp lose +08/04Waiting for dealer feedback +25/03: please keep it open - so, no close possible. +20/03:Still waiting. +18/03: Still waiting. +11/03: Still waiting. +21/02: Wait for the dealer's feedback. +20/02: it seems that vehicle has a different TBOX SN from the one in the TSP - see picure attached. Request has been sent to invite the customer to the dealer for collecting TBOX data. Wait for feedback.",Low,close,TBOX,Vsevolod Tsoi,24/11/2025,JAECOO J7（T1EJ）,LVVDB21B9RC103393,,"TGR0000500 +elantseva.dv@rnd.borauto.ru","CHR_LVVDB21B9RC103393_20251118205043.tar,DMC_data.jpg,TBOX_data.jpg,file_714.jpg,Picture_1.JPG,file_715.jpg,file_702.jpg,file_705.jpg,file_704.jpg,file_703.jpg,file_701.jpg",Vsevolod,,,,,,277 +TR464,Telegram bot,21/02/2025,,Remote control ,"Customer can't start the vehicle vie remote control app. As a result an error message comes up. +Vehicle status in the TSP: last tbox login 2025-02-18 20:20:32, high frequency data 2025-02-18 20:19:26. MNO status: last apn1&2 available on 18/02.",0224：建议加入清单进行USB软件更新,"27/02: customer's feedback - apn1 is again available and as a consequence the remote control started working. +26/02: tbox log attached. +0224: Recommendation to add to the list for USB software update @Vsevolod +21/02: command name - engine start on 21/02 at 12:13. Screenshot attached.",Low,close,local O&M,Vsevolod,27/02/2025,EXEED RX（T22）,LVTDD24B1RG021245,,TGR0000646,"LOG_LVTDD24B1RG021245_26_02_2025.tar,Picture_1.jpg",Vsevolod,,,,,,6 +TR465,Telegram bot,21/02/2025,,Application,Customer can't bind his vehicle in the remote control app. Background: customer was using the app and everythig worked well. But one day he opened the app and noticed that he has been loged out. Then he loged in again with his account data and added the vehicle in the app (vehicle status is OK in the system). However he could not activate it in the app => status in the TSP - unbound . An error message comes up "A07913" - see pictures attached.,"0320：等待客户反馈，追踪是否能够正常使用 +0320：后台已删除错误数据，可让用户重新绑定 +0318：已转入分析@张明亮 +0227：A07913报错 注册品牌信息失败@戴国富 +0225: 客户反馈：手机端仍然无法激活汽车。同样的错误提示“A07913”@喻起航 +0225：此问题已解决，请属地运维联系用户核实进行问题关闭@Vsevolod 7天没有反馈需要关闭 +0224：转APP分析","20/03: Customer's feedback: problem is solved. +20/03:Erroneous data has been deleted in the background, allowing users to rebind.@Vsevolod Tsoi +18/03:Transferred for analysis.@张明亮 +25/02: customer's feedback: still can't activate the car in the mobile app. The same error message comes up ""A07913""@喻起航 +Feb25: This issue has been resolved, please local O&M contact the user to verify for problem closure @Vsevolod +Feb 24: Turn APP Analysis",Low,close,车控APP(Car control),Vsevolod Tsoi,20/03/2025,CHERY TIGGO 9 (T28)）,LVTDD24B9RG088529,,TGR0000590,"Picture_1.jpg,Status_admin.JPG,Vehice_status_undind.JPG,file_971.jpg",Vsevolod,,,,,,27 +TR466,Telegram bot,21/02/2025,,Network,Customer can't laucnh online video app -> License issue -> Other app doesn't work too -> No tbox connect since 18/02 -> No any network connection -> IHU still login well. apps works with wifi,0224：等待更多细节反馈，UPD？,"24/02 Closed, confirmed by customer feedback +21/02 PLS provide information what data we should collect for analysis +UPD solved by itself -> Waiting for feedback",Low,close,local O&M,Kostya,24/02/2025,EXEED RX（T22）,LVTDD24B1RG021245,,TGR0000676,image.png,Kostya,,,,,,3 +TR467,Mail,21/02/2025,,Remote control ,"Remote engine start does not work via app. Status in TSP: last tbox login 2025-02-21 03:08:41. high frequency data 2025-02-21 15:14:11. MNO: apn2 - OK. No working apn1 since Feb, 18th. ","0826：暂无进展，转等待数据 +0819:请QS方更新进展 +0814: 等待TBOX硬件抵达 +0812: 预计抵达日期 W33 底 +0807: 预计抵达日期 CW33 底 +0804：已询问经销商了解预计抵达时间。 +0728: 仍在等待 TBOX 硬件的交付，预计将于 7 月底/8 月初交付。 +0722：仍在等待 TBOX 硬件的交付。 +0714: 到目前为止还没有收到货物。 +0710: 仍未收到 TBOX 硬件。 +0701：等待 8 月份交付 TBOX HW。 +0626:新的 TBOX 预计从 8 月开始交付 +0623: 等待用户更换T-BOX +0610：等待信息刷新 +0603：等待用户更换tbox +0529：等待更新 +0515:建议用户进站，先取日志之后，再更换TBOX，保留日志供分析 +0513:属地反馈问题重新出现，ANP2已在5月1日打开，但无网络连接，会后尝试抓取日志，车辆已进入深度睡眠，建议按深度睡眠流程处理 +0415：建议此问题暂时关闭 +0410：等待用户进站 +0407：等待用户进站 +0401：等待用户进站 +0325：等到用户进站 +0320：等待日志抓取 +0318：等待用户进站取日志 +0311：等待前方抓取日志 +0304：取Tbox日志并分析 +0227：查询到用户远程操控失败原因均因为提示超时，建议用户将车辆移动到信号好的地方再试试，若还不行，建议进站检查。 +0225：转TSP查询; 短信下发后 TBOX无响应，35s超时（time out） +0224：请MNO协助排查下APN。APN正常","09/10: we got really very strange feedback from dealership: we were informed by dealership that spare TBOX arrived and change might be done accordingly so that the remote control was restored. We were told by a dealership that user was contacted by CHERY representative office telling that change of TBOX was not required. +09/10: still pending. Then, status checked out in TSP and MNO: apn1&2 are normal. +25/09: TBOX arrival is pending. +22/09: arrival TBOX HW is still pending. +18/09: no feedback so far. +16/09: no change since the last comment. +11/09: dealer's feedback - TBOX HW arrival is expected soon. Once received, all the required data will be provided to modify TSP with a new TBOX HW. +02/09: repeat request on TBOX arrival date is sent to dealer. Wait for feedback. +26/08：no update ,turn to waiting for data +19/08: pls QS side update the progress +14/08: wait for TBOX HW arrival. +12/08: same status +07/08: expected arrival date end of W33 +04/08: request sent to dealer to find out an expected arrival. +31/07: same status +28/07: still wait for delivery of TBOX HW that is expected end of July/begining August. +22/07: still wait for delivery of TBOX HW. +14/07: there was no delivery so far. +10/07: TBOX HW arrival is still pending. +01.07: wait for delivery of TBOX HW in August +24/06: delivery of new TBOX is expected begining August. +16/06: request for changing TBOX HW has been sent. Waif for after-sales confirmation. +0605：need customer go to the dealer,first,catch the tbox log,secondly,replace a new tbox,that's all. +03/06: please precise when a decision has been made that tbox HW needs to be replaced. +29.05: still wait for feedback +19/05: customer is asked to start the engine with Start/Stop button to let vehicle go out of hibernation mode. Wait for feedback. +13/05:The local feedback issue has reappeared. ANP2 was opened on May 1st, but there was no network connection. After the meeting, attempts were made to capture logs, and the vehicle has entered deep sleep. It is recommended to follow the deep sleep process for handling. +13/05: status checked out in MNO: apn2 has been switched again on May, 1st but there is still no network available - see picture attached. +15/04: Suggest temporarily closing this issue +10/04: still waiting for invititaion of customer to dealer +07/04: still waiting for invititaion of customer to dealer +April 01 :Still Waiting. +March 25:Still Waiting. +March 20:waiting the customer to go to the dealer for logs. +March 18: waiting the customer to go to the dealer for logs. +March 11:need Tbox logs to analysis +March 4: need Tbox logs to analysis +Feb 27：Query to the user remote control failure reasons are because of the prompt timeout, it is recommended that the user will move the vehicle to a good signal place and try again, if it does not work, it is recommended to enter the station to check. +2/24 MNO：APN1 is configured properly without any additional restrictions（APN1配置正常，无任何额外限制） +21/02: wrong vehicle status is displayed in the app: engine shown as started as well as the doors are unlocked. However the car is locked. Commande name - lock the doors on 21/02 at 16:34. Pictures attached. Tbox log in process of upload.",Low,close,TBOX,Vsevolod,16/10/2025,CHERY TIGGO 9 (T28)）,LVTDD24B7RG116179,,,"MNO_status.JPG,Picture_2.JPG,Picture-1.JPG",Vsevolod,,,,,,237 +TR468,Telegram bot,24/02/2025,,Remote control ,"Remote control doesn't work neither apps in the IHU. However, apps work well using the network shared from smartphone. Status TSP: last tbox login on 2024-12-22 22:01:04, high frequency data +2024-12-22 22:18:56. MNO status: no apn1 available since Dec, 22th 2024.","0319：等待OTA +0224：请抓取下tbox日志以及主机日志","24/04: upgrade successfully completed on April, 5th. No issues since upgrade => TR closed. +03/04: there is still no connection. Wait for downloading. +Mar 19: Waiting for OTA. +Feb 24：Please grab the tbox logs as well as the DMC logs.@Vsevolod",Low,close,local O&M,Vsevolod,24/04/2025,EXEED RX（T22）,LVTDD24B5RG020678,,TGR0000602,"file_993.jpg,file_872.jpg,file_870.jpg,file_843.jpg,file_864.jpg,file_844.jpg,file_871.jpg",Vsevolod,,,,,,59 +TR469,Mail,24/02/2025,,Remote control ,Remote control doesn't work + wrong status of car.,0319：等待OTA0225：等待具体日志及信息,"Apr 17: solved after OTA +10/04: OTA upgrade success on 10/04. Wait for 2 weeks to check remote control. if no issue to be closed. +03/04: download complete. Wait for upgrade. +Feb 24: Collecting operation time /screenshots",Low,close,local O&M,Evgeniy,17/04/2025,EXEED RX（T22）,LVTDD24B5RG031311,,,,Evgeniy,,,,,,52 +TR470,Mail,24/02/2025,,Remote control ,Remote control doesn't work + wrong status of car.,0319：等待OTA0225：等待具体日志及信息,"Apr 17: solved after OTA +03/04: download complete. Wait for upgrade. +Feb 24: Collecting operation time /screenshots",Low,close,local O&M,Evgeniy,17/04/2025,EXEED RX（T22）,LVTDD24B6RG021211,,,image.png,Evgeniy,,,,,,52 +TR471,Mail,24/02/2025,,Remote control ,"Remote control doesn't work. Status in the TSP: last tbox login 2025-02-07 04:50:03; high frequency data 2025-01-06 16:37:14. MNO: no apn1 availabale since Jan, 10th.","0515：协商一致，今日拟关闭问题 +0424:用户与今日升级成功，一周后无反馈可关闭问题 +0403:无消息反馈，等待用户下载后OTA +0319：等待OTA0225：该车可以进行USB刷写软件，新增车辆刷写软件可以在此表格中新增，说清楚时间即可","15/05: Consensus reached through negotiation to close the issue today +24/04: upgrade completed successfully on April, 24th. The issue is going to be closed if no there are no any claimes after one week usage. +03/04: there is still no connection. Wait for downloading. +25/02: command name - unlock the doors on 25/02 at 7:52. Picture attached. +Feb 25：The car can be USB brush writing software, new vehicle brush writing software can be added in this form, say clear time can be +links：https://l5j8axkr3y6.sg.larksuite.com/share/base/view/shrlgvxQ7p0rMcpHSQpnTiQU2Dh +24/02: plese check and confirm if TBOX SW of the car might be upgraded with USB at dealer @喻起航",Low,close,local O&M,Vsevolod,15/05/2025,EXEED RX（T22）,LVTDD24B1RG019253,,,Picture_1.jpg,Vsevolod,,,,,,80 +TR472,Mail,24/02/2025,,Remote control ,Remote control doesn't work + wrong status of car.,"0227: +查询到用户远程操控失败原因均因为提示超时，建议用户将车辆移动到信号好的地方再试试，若还不行，建议进站检查 +0226： +经TBOX日志查询，TBOX没有收到短信唤醒 +0225： +1.转TSP分析，车辆不在线执行唤醒操作，短信下发后，tbox无响应，35s超时 +2.转TBOX走跨境流程取tbox后进行分析","Aprik 17: no feedback +Feb 27:the user remote control fails because of the prompt timeout, we recommend that the user will move the vehicle to a good signal place and try again, if it does not work, it is recommended to check the station. +Feb 26:Upon TBOX log query, the TBOX did not receive SMS wakeups +Feb 24: Operation time -22/02/2025 at 20:17",Low,temporary close,TBOX,Evgeniy,11/03/2025,JAECOO J7（T1EJ）,LVVDB21B0RC071594,,,"LOG_LVVDB21B0RC07159420250224161405.tar,image.png",Evgeniy,,,,,,15 +TR473,Telegram bot,24/02/2025,,Remote control ,"Wrong data is reflected in the remote control app + no commands are executed. Status in the TSP: last tbox login 2025-02-24 10:57:11; high frequency data 2025-02-15 14:35:30. MNO: no apn1 available since Feb, 15th.","0610:该车辆仍然没有进行OTA升级 +0605：等待属地更新 +0529：等待更新 +0520:等待更新 +0515:平台暂未查询到近期远控记录，建议联系用户是否OTA了 +0424：等待用户OTA +0319：等待OTA +0225： +1.转MNO进行分析，APN查询正常 +2.转TSP进行分析，TBOX35S超时 +3.建议加入USB升级清单进行T22软件刷写","10/06: checked out - still not upgraded yet +03/06: still the same status. +29/05: downloaded but still not upgraded yet. +19/05: OTA upgrade is downloaded on May, 16th. Wait for upgrade. +15/05: The platform has not yet found any recent remote control records. It is recommended to contact the user to see if they have done OTA.@Vsevolod Tsoi +24/04: still wait for upgrade OTA. +03/04: download complete. Wait for upgrading. +0225: +1. Turn to MNO for analysis, APN query is normal. +2. Turn to TSP for analysis, TBOX35S timeout +3. Suggest to add USB upgrade list for T22 software brushing.",Low,temporary close,local O&M,Vsevolod,17/06/2025,EXEED RX（T22）,XEYDD14B3SA012122,,TGR0000682,"file_997.jpg,file_982.jpg",Vsevolod,,,,,,113 +TR479,Mail,27/02/2025,,Remote control ,Remote control doesn't work + wrong status of car.,"0319：等待OTA +0303： +1.转TSP进行分析：TR481在2月27日没有看到车控请求 +2.转TBOX取日志后进行分析","April 17: solved after OTA +03/04: download complete. Wait for upgrading. +March 19:waiting OTA +0303: +1. Transferred to TSP for analysis: TR481 did not see the car control request on February 27th +2.Turn to TBOX to get logs and then analyze them +Feb 27: no connection between tsp and tbox (hibernation mode)",Low,close,TSP,张石树,17/04/2025,EXEED RX（T22）,LVTDD24B1RG032102,,,image.png,Evgeniy,,,,,,49 +TR480,Telegram bot,27/02/2025,,Remote control ,"Remote conrol issue: customer can't control the car via mobile app - commands are not executed. Engine is always shown as started however actually it is stopped. TSP status: last tbox login +2025-02-25 17:09:25, high frequency data 2025-02-25 17:13:21. MNO: apn1&2 are available and active.","0319：等待OTA +0303： +1.转TSP分析：车辆不在线执行唤醒操作，短信下发后，tbox无响应，35s超时 +2.建议等待OTA解决该问题","24/04: no issue => TR closed. +03/04: OTA upgrade completed successfully on March, 31th - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +March 19:waiting OTA +0303: +1. to TSP analysis: the vehicle is not online to perform the wake-up operation, after the SMS is sent, the tbox does not respond, 35s timeout +2. Suggest waiting for OTA to solve the problem +27/02: engine start on 27/02 at 14:00",Low,close,TSP,张石树,24/04/2025,EXEED RX（T22）,LVTDD24B0RG009460,,TGR0000479,,Vsevolod,,,,,,56 +TR481,Mail,27/02/2025,,Remote control ,Remote control doesn't work + wrong status of car.,"0319：等待OTA +0303：转TSP分析，TR481在2月27日没有看到车控请求","03/04: upgrade completed on March, 19th. There were no any issue since upgrade. +March 19:waiting OTA +March 06:ask customer to use physical key to start the engine +March 03: Transferred to TSP for analysis, TR481 did not see car control request on February 27th +Feb 27: no connection between tsp and tbox ",Low,close,TSP,张石树,03/04/2025,EXEED RX（T22）,LVTDD24B5RG033897,,,,Evgeniy,,,,,,35 +TR482,Mail,27/02/2025,,Remote control ,"Remote control issue: engine start is not executed remotely via app. Status in the TSP: last tbox login 2025-02-27 13:35:31, high frequency data 2025-02-27 13:44:02. MNO: apn1&2 are OK.","0427:查询远控记录，发现26日用户已有成功远控记录，建议可让用户再观察观察，下次日会前无异常，可关闭 +0424：用户反馈问题未解决，等待提供经纬信息和远控记录 +0421：等待用户反馈 +0417：等待用户反馈 +0415：等待用户反馈 +0410：等待用户反馈 +0404:建议换个地方重新尝试远控，如仍然不可用，需要提供远控地的经纬度信息 +0327：TBOX日志分析：短信延迟 7：29收到短信。 +0325：转TBOX分析，远控启动时间：3月24日7:25 +0320：等待用户提供新的操作反馈 +0318：等待用户反馈 +0311：等待反馈 +0305：TBOX日志分析：短信延迟 6：56收到短信 +0303： +1.转TSP分析：车辆不在线，用户试了很多次远控，一直发唤醒短信，直到10几分钟后才成功","27/04：Upon checking the remote control records, it was found that the user had successfully completed remote control on the 26th. It is recommended that the user observe again. If there are no abnormalities before the next day's meeting, it can be closed.@Vsevolod Tsoi +24/04：User feedback issue not resolved, waiting for latitude and longitude information and remote control records to be provided. +21/04： Waiting for customer feedback. +17/04： Waiting for customer feedback. +15/04: Waiting for user feedback +10/04: Waiting for user feedback +04/04:It is recommended to try the remote control again in another place, if it is still unavailable, you need to provide the latitude and longitude information of the remote control place. +27/03:TBOX log analysis: SMS delayed 7:29 received SMS.provide the specific location of the remote control anomaly, we go to check the specific location of the network situation. +24/03: command - engine start on March, 24th at 7:25. Tbox log attached. +20/03：Waiting for users to provide feedback on new operations. +19/03: customer's feedback: commands are executed every other time. Customer is asked to execute an operation and provide the required data for investigation. +Mar 18: Waiting for user feedback.@Vsevolod Tsoi +Mar 11: Waiting for feedback +March 6:sms delay ,suggest owner to try again +03/03: +1. turn to analysis +2. Turn T1EJ's BOX Engineer Analysis. @刘海丰 +27/02: command - engine start on 27/02 at 6:52. Tbox log - see in the attachment.",Low,close,local O&M,Vsevolod,29/04/2025,JAECOO J7（T1EJ）,LVVDD21B7RC084238,,Нижний Новгород,"LOG_LVVDD21B7RC084238_24_03_2025.tar,Picture_3.jpg,LOG_LVVDD21B7RC084238_27_02_2025.tar,Picture_1.jpeg",Vsevolod,,,,,,61 +TR484,Mail,03/03/2025,,Remote control ,"Remote control issue: seat heating is not executed remotly via app. Status in the TSP: last tbox login 2025-03-03 09:29:59, high frequency data 2025-03-03 09:32:30. MNO: apn1&2 are available and active.","0327：此问题已交给售后质量跟进，是否可以关闭 +0325：等待用户反馈 +0320：会后确认状态 +0318：等待反馈 +0306： +1.TBOX下发指令后，座椅加热模块没响应，未执行加热操作，建议转售后质量跟进，用户进站检查单件或者HCU软件 +已转给售后质量跟进 @王斌@林华兴@贾旭杰@徐俊杰 +0305: +1.TBOX日志分析： +2.TSP日志分析：0x0001 ：控制器反馈状态失败 +0304： +1.转TSP分析后转box分析 +0303：11：24分开启座椅加热"," @王斌@林华兴@贾旭杰@徐俊杰 +27/03:This problem has been handed over to after-sales quality follow-up, whether it can be closed.@Vsevolod Tsoi +26/03: command - seat heating on March, 26th at 11:43. Tbox log attached. +26/03: customer's feedback: seat heating command executes. However, there in an error message coming up in the app ""executing is not successful. Please try again later"" - see picture attached. And customer also calls the heating for both seats (driver and co-driver) but actually the only one that is heated. Customer is also asked to call a seat heating command and provide then the respective data. +25/03: wait for feedback whether the problem is still valid. +20/03: customer is asked wether the issue is still valid. Wait for feed-back. +Mar 18: Waiting for feedback +march 06:After the TBOX issued the command, the seat heating module did not respond and did not perform the heating operation, it is recommended to turn to the after-sales quality follow-up, the user into the station to check the single piece or HCU software +03/03: commande - seat heating on 27/02 at 11:24.",Low,close,local O&M,Vsevolod Tsoi,08/04/2025,JAECOO J7（T1EJ）,LVVDB21B4RC107285,,matekin@mail.ru,"LOG_LVVDB21B4RC107285_26_03_2025.tar,App_Error_message_11_43_Moscow_time.jpg,Seat_heat_error_message_in_O&J_app.jpg,img_v3_02k3_6f3aa300-5d68-4796-8ec7-fc9b152e677g.jpg,LOG_LVVDB21B4RC107285_03_03_2025.tar,Picture_1.jpeg",Vsevolod,,,,,,36 +TR485,Mail,04/03/2025,,Remote control ,Remote control doesn't work + wrong status of car.,"0408：等待用户反馈 +0325:查询TBOX有登录登出记录，24小时内有远控正常记录。请属地运维确认远控是偶尔不可用，还是一直不可用。如一直不可用，请提供远控时间及对应日志。 +0320:等待用户反馈 +0318：等待询问用户问题是否依旧存在，并询问具体远控时间，取最近一次日志 +0311：会后分析 +0306: +1.MNO分析反馈：卡状态是正常的，双APN在3月4号和3月5号都有使用记录,MNO排查短信超时 +2.用户车辆接收远控指令短信超时，导致远控失败，建议用户将车辆移动到信号好的地方再试试 +0305： +1.日志已被清除，无法在TSP平台查询到相关操作。","April 17: works ok solved +April 08:Still Waiting. +April 01:Still Waiting. +Mar 25：Please ask the local O&M to confirm whether the remote control is occasionally unavailable or always unavailable. If it is always unavailable, please provide the remote control time and corresponding logs. Specific remote control address. +Mar 20:waiting for feedback. +Mar 18: Wait to ask the user if the problem still exists, and ask for the specific remote control time, take the most recent logs. +March 4:Users are advised to move the vehicle to a place with good signal and try again +Feb 4: operation date Feb 4 at 09:07 am",Low,close,local O&M,Evgeniy,17/04/2025,EXEED VX FL（M36T）,LVTDD24B5RD030449,89701010050608755641,,"image.png,LOG_LVTDD24B5RD03044920250304114416.tar",Evgeniy,,,,,,44 +TR486,Mail,04/03/2025,,Remote control ,Remote control doesn't work,"0305： +1.日志已被清除，无法在TSP平台查询到相关操作。",March 4: operation date Feb 4 at 11:13 am,Low,temporary close,,,06/03/2025,JAECOO J7（T1EJ）,LVVDB21B2RC081754,,,"LOG_LVVDB21B2RC08175420250304120910.tar,image.png",Evgeniy,,,,,,2 +TR488,Mail,04/03/2025,,Remote control ,Remote control: engine start does not work. TSP status: last tbox login 2025-03-04 12:10:15; high frequency data 2025-03-04 12:12:45. MNO: apn1&2 are available and active.,"0318：等待新日志 +0311：重新抓取日志 +0305： +1.日志已被清除，无法在TSP平台查询到相关操作。","20/03: customer's feedback: tried to execute an operation and it worked well => so temporary close. +19/03: customer is asked if problem is still valid. If so, required data will be requested for investigation. +18/03：Need to catch new logs and detail time.@Vsevolod +11/03：Need to catch new logs.@Vsevolod +05/03: The log has been cleared and the operation cannot be queried in the TSP platform. +04/03: command - engine start on 02/03/2025 at 14:30. Error picture is attached as well as tbox log.",Low,close,local O&M,Vsevolod,07/04/2025,JAECOO J7（T1EJ）,LVVDB21B6RC071003,,psb08@bk.ru,"LOG_LVVDB21B6RC071003_04_03_2025.tar,Picture_1.jpeg",Vsevolod,,,,,,34 +TR489,Mail,04/03/2025,,Remote control ,"Remote conrol issue: commands are not executed via app. Vehicle status in the TSP: last tbox login +2025-03-02 09:01:24; high frequency data 2025-03-02 09:01:37. MNO: no apn1 available since march, 1st.","0515:平台查询到5月2日，3日均有远控成功记录，建议可关闭该问题 +0424：仍在等待升级 +0403:等待升级。 +0319：等待OTA +0305：等待操作时间反馈","0515: The platform found that there were successful remote control records on May 2nd and 3rd. It is recommended to close this issue +24/04: no issues since upgrade => TR closed. +03/04: OTA upgrade completed successfully on April, 2nd - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +March 19:waiting OTA +04/03: customer is asked to reproducing the problem and then provide the required data for investigation.",Low,close,local O&M,Vsevolod,15/05/2025,EXEED RX（T22）,LVTDD24B0RG013699,,,,Vsevolod,,,,,,72 +TR490,Mail,04/03/2025,,Remote control ,"Remote control doesn't operate: no commands executed neither displaying of the vehicle data. TSP status: last tbox login 2025-03-03 08:27:05, high frequency data 2025-02-11 16:09:17. MNO: no apn1 available since Feb, 12th.","0319：等待OTA +0305：等待操作时间反馈","24/04: no issues since upgrade => TR closed. +03/04: OTA upgrade completed successfully on April, 3rd - under monitoring Wait for 1 week. If there is no any negative feedback, the issue will be closed. +March 19:waiting OTA +04/03: customer is asked to reproducing the problem and then provide the required data for investigation.",Low,close,local O&M,Vsevolod,24/04/2025,EXEED RX（T22）,LVTDD24B4RG021398,,,LOG_LVTDD24B4RG021398_04_03_2025.tar,Vsevolod,,,,,,51 +TR491,Mail,04/03/2025,,Remote control ,"Remote control: no commands execusted, wrong data is displayed. Status in the TSP: last tbox login 2025-03-04 00:19:39; high frequency data 2024-12-31 21:29:32. MNO: no apn1 available.","0319：等待OTA +0305:等待操作时间反馈","24/04: no claimes since the upgrade => TR closed. +03/04: OTA upgrade completed successfully on April, 1st => under monitoring. Wait for 1 week. If there is no any negative feedback, the issue will be closed. +19/03:waiting OTA +04/03: customer asked for providing the neede data for investigation.",Low,close,local O&M,Vsevolod,24/04/2025,EXEED RX（T22）,LVTDD24B5RG021328,,,LOG_LVTDD24B5RG021328_04_03_2025.tar,Vsevolod,,,,,,51 +TR493,Mail,05/03/2025,,Remote control ,"Remote control issue: no commands are executed via remote control app. TSP status: last tbox login 2025-03-04 17:55:05, high frequency data 2025-03-04 18:16:16. MNO: apn1&2 are available and active. Clients was trying to call the commands in different areas. Mobile network is OK. There is no weak signal or other issues. Vehicle was located in the open area at the moment of executing of commands.",0305:等待操作时间反馈,"24/04: upgrade completed successfully on April, 11th. No customer's claimes since upgrade => TR closed. +25/03: still wait for feedback. +05/03: wait for data (operation time/date, command name) for investigation.",Low,close,,,24/04/2025,EXEED RX（T22）,LVTDD24B1RG019771,,,,Vsevolod,,,,,,50 +TR494,,05/03/2025,,Remote control ,Remote control doesn't work,"0605：仍无更新，暂时关闭 +0603：5号该问题仍未更新，将更新此问题状态为临时关闭 +0520：等待更新最新信息 +0515：建议用户重新尝试远控，因为老旧的记录可能已被覆盖，如仍有异常，再进行分析 +0513：继续观察，用户反馈有时可用，有时不可用 +0429：等待属地反馈进度 +0427：等待属地反馈进度 +0425：等待属地反馈进度 +0424:等待与用户联系 +0422：TSP未见日志上传，建议用户进站尝试重新着车启动，等待10分钟左右尝试远控，若失败，当场抓取日志 +0417：等待用户进站提供新日志 +0415：等待反馈 +0410：等待反馈 +0410:等待新日志 +0325:等待新日志 +0318：等待新日志 +0311：用户尝试重启车辆，但仍无法远控，等待抓取最近一次远控日志 +0306： +1.TSP反馈35S超时 +2.TBOX日志显示11:47:57收到短信 11:47:58上线 11:48:41收到第一次车控指令:方向盘加热","0603: This issue is still not updated on the 5th, will update the status of this issue to temporarily closed +15/05: It is recommended that users try remote control again, as old records may have been overwritten. If there are still abnormalities, further analysis should be conducted +13/05: sometimes it works, but often timeout failed. recommended use another places. (bad signal) - still keep in touch with the customer +29/04: Waiting for local feedback on progress +27/04: Waiting for local feedback on progress +25/04: Waiting for local feedback on progress +24/04: Waiting to contact the user +22/04：TSP did not see any log upload. It is recommended that the user try to restart the car by entering the station and wait for about 10 minutes to try remote control. If it fails, the log should be captured on the spot.@Vsevolod Tsoi +17/04: Waiting new logs +10/04：Still waiting. +25/03：Still waiting. +18/03：Waiting to catch new logs and detail time.@Vsevolod +March 11: The user tries to restart the vehicle, but still can't remote control it, waiting to capture the most recent remote control exception logs.@Evgeniy +March 6 ：suggest customer try again in other place +March 5: operation date 05/03/2025 at 11:47 ",Low,temporary close,local O&M,Vsevolod,05/06/2025,JAECOO J7（T1EJ）,LVVDD21B1RC083604,,,"20250306-105405.jpg,LOG_LVVDD21B1RC08360420250305161502.tar,photo_2025-03-05_11-49-27.jpg",Evgeniy,,,,,,92 +TR495,,06/03/2025,,Remote control ,"After parking the car overnight, the telematics stops working. If you lock the car and leave it closed overnight, in the morning the phone control does not work until the owner starts the car manually.","0320：用户未接听电话，继续等待 +0318：等待用户进站检查 +0310: +1.查询TBOX最后一次登出时间为2025-03-09 19:58:27，尝试远程抓取日志失败 +2.建议属地运维联系用户进站抓取日志后转国内box工程师分析","March 25: switched to temporary close +March 20:User did not answer the call, continue to wait. +Mar 18: Waiting customer go to the dealer for checking. +March10. +1. query TBOX last logout time is 2025-03-09 19:58:27, attempt to capture logs remotely fails +2. Suggest local O&M to contact users to capture logs and transfer to Chinese box engineers to analyze.",Low,temporary close,TSP,Evgeniy,25/03/2025,JAECOO J7（T1EJ）,LVVDB21B8RC071438 ,,,"IMG_20250303_123355.jpg,Screenshot_20250303-124427.png,Screenshot_20250303-124420.png",Evgeniy,,,,,,19 +TR496,,06/03/2025,,Remote control ,Remote control doesn't work + wrong info HUD +wrong status of car,"0319：等待OTA +0311：正在分析中 +3月6日13点27分钟 +0310： +1.转国内TSP分析：3月6日无远控请求，平台无异常 +2.转box分析","Apr 17: solved by OTA +03/04: OTA upgrade completed successfully on April, 1st => under monitoring. Wait for 1 week. If there is no any negative feedback, the issue will be closed. +March 19:waiting OTA +March 10: +1. Turning to domestic TSP analysis: no remote control request on March 6, no platform abnormality +2.to box analysis",Low,close,TBOX,韦正辉,17/04/2025,EXEED RX（T22）,LVTDD24B9RG031988,,,"LOG_LVTDD24B9RG03198820250306135916.tar,WhatsApp Video 2025-03-05 at 15.17.12.mp4,image.png,image.png,image.png,image.png",Evgeniy,,,,,,42 +TR497,Telegram bot,06/03/2025,,Application,"Partialy wrong status of remote control fucntions in the app (When customer tried to turn on heating in mobile app they received ""Command was executed"", heating working, but status of heating app is off)","0320：反馈可能由于合规性限制，车机上 ""允许车辆数据上报 ""未打开，建议本地 OM 询问用户是否打开。 +0318：等待反馈 +0311：等待中 +0310: +1.等待操作视频及日志","24/04: upgrade completed sucessfully on March, 31st. No claimes since upgrade => TR closed. +March 25: temporary close +March 20: Feedback may be that ""Allow Vehicle Data Reporting"" is not switched on on the vehicle due to compliance constraints, it is recommended that the local OM asks the user if this is switched on.@Evgeniy +March18. Waiting, In progress.@Evgeniy +March13. Waiting, In progress +March11. In progress +March10. +1. Waiting for operation video and log",Low,close,local O&M,Kostya,24/04/2025,EXEED RX（T22）,LVTDD24B5RG032569,,TGR0000734,,Kostya,,,,,,49 +TR498,Mail,10/03/2025,,Remote control ,"Remote control: commands are not executed via remote control app. TSP status: last tbox login 2025-03-10 04:30:49, high frequency data 2025-03-10 05:04:39. MNO: apn1&2 are available and operational.",0311:等待月底OTA,"24/04: no claimes since the upgrade => TR closed +03/04: OTA upgrade completed successfully on April, 1st => under monitoring. Wait for 1 week. If there is no any negative feedback, the issue will be closed. +10/03: customer is asked to execute a command as well as providing the needed data.",Low,close,OTA,Evgeniy,24/04/2025,EXEED RX（T22）,LVTDD24B3RG033297,,,,Vsevolod,,,,,,45 +TR499,,10/03/2025,,Application,Customer can't bind the vehicle in the remote control app. When trying to bind in the app an error message A07913 comes up.,"0401：等待用户进站 +0325: 车辆无法唤醒，TSP无Tbox登录登出记录。最后一次Tbox登录时间为2月15。建议用户进站检查 +0320：客户已可以成功绑定，但车辆处于深度睡眠，已告知使用物理钥匙启动，等待客户反馈 +0320：后台已删除错误数据，可让用户重新绑定 +0318：同TR465@张明亮 +0311： A07913报错 注册品牌信息失败，@戴国富","07/04: TR closed. The remote control issue will be managed in TR455 +01/04：Still Waiting. +25/03: Vehicle will not wake up, TSP has no Tbox login logout record. Last Tbox logout on 15 Feb. Users are advised to come in to check +25/03: wake up car didn't help-> there is no connection between tbox and TSP. +20/03: customer's feedback: he could bind the car in the end but it is now in the hibernation mode. He will be requested to wake up the car using the key. +Mar 20: Erroneous data has been deleted in the background, allowing users to rebind.@Vsevolod Tsoi +Mar 18: same with TR465 +Mar 11: A07913 error @戴国富",Low,close,车控APP(Car control),Evgeniy,07/04/2025,CHERY TIGGO 9 (T28)）,LVTDD24B5RG091332,,TGR0000627,,Vsevolod,,,,,,28 +TR500,Mail,12/03/2025,,Remote control ,VK video doesn't work . Error with license ,"0408: 建议暂时关闭 +0320：OTA发起提测，等待具体计划。 +0319：图标问题已经解决，OTA时间待定。 +0318：激活不成功的问题已经解决，图标问题明日解决 +0313：客户未在 VK Video 的应用商店中看到按钮更新。其他服务运行良好。客户在屏幕上的视频中看到的是 ""在线视频""，而在商店中看到的是 ""VK 视频""。 +0312：生态反馈用户车辆VK版本较低，尝试更换网络看VK视频是否可用，如可用，考虑VK视频版本升级，等待属地反馈 +0311：TSP平台无异常，转生态","March 20:OTA initiated mention of testing, awaiting specific plans. +March 19:Icon issue has been resolved, OTA time to be determined. +Marth 18:Unsuccessful activation issue has been resolved, icon issue to be resolved tomorrow. +March 13: The customer can't see button update in the app store of VK Video. Other services works well. Please pay attention, that in the VIDEO on the screen the customer sees ""Online video"" but in the store ""VK VIDEO"". This is misunderstanding, please ask the CABIN team of T28. @赵杰 +March 12:Eco-feedback user vehicle VK version is low, try to change the network to see if the VK video is available, such as available, consider VK video version upgrade, waiting for feedback from the local OM. +March 11: No anomalies in the TSP platform, switching to ecology",Low,temporary close,生态/ecologically,袁清,08/04/2025,CHERY TIGGO 9 (T28)）,LVTDD24B4RG091421 ,,,"VK обновление.MOV,Vk video - лицензия.mp4",Evgeniy,,,,,,27 +TR503,Mail,17/03/2025,,VK ,Function "Search" doesn't work in the app VK video,0317：TR能够在本地解决此问题，无需二线团队支持,"15/04: no feedback - closed. +03/04: customer is asked to update VK video app in IHU. Wait for feedback if the issue gonna be fixed. +March 17: TR is created to be able to track the customer's issue. It will be treated by VK team locally. No 2nd line support required.",Low,close,local O&M,Vsevolod Tsoi,15/04/2025,JAECOO J7（T1EJ）,LVVDB21B9RC107640,,,Picture_1.JPG,Vsevolod Tsoi,,,,,,29 +TR504,Mail,17/03/2025,,Network,"Standard services (VK video, music, weather etc.) do not work. Status checked out in MNO: no apn2 available however customer still has traffic available (about 3Gb).","0424:协商一致，暂时关闭 +0421：等待用户反馈 +0417：等客户反馈 +0415：等客户反馈 +0410：平台尝试手动刷新SIM卡状态，建议用户重新尝试；等客户反馈 +0408：客户来电询问问题进展 +0325：等待反馈 +0320：等待反馈 +0318：等待反馈 +0317：建议切换网络尝试，并提供相关问题的日志、截图或视频@Vsevolod Tsoi","24/04:Agreed upon, temporarily closed +21/04：waiting fo人feedback +18/04: customer is asked again to provide the feedback. +April 17：Waiting for feedback. +April 15： Waiting for feedback. +April 10：The platform tries to manually refresh the SIM card status, and users are advised to try again +April 04: customer is asked to provide a feedback whether the issue is still valid. +March25. Waiting for feedback with network switch. +March20. Waiting for feedback. +March18. Waiting for feedback. @Vsevolod Tsoi +17/03 :Suggest switching networks，please provide relevant logs, screenshots or videos.",Low,temporary close,local O&M,袁清,24/04/2025,EXEED RX（T22）,XEYDD14B3RA002664,,Client phone number: +7 (986) 766 71 72,,Vsevolod Tsoi,,,,,,38 +TR505,Mail,17/03/2025,,Remote control ,Remote control doesn't work + impossible to see status of car ,"0515:已获取到日志，平台查询用户12-14日均有远控成功记录，可关闭该问题 +0513:用户反馈12日远控已可用，持续观察 +0506:等待用户进站 +0429：等待用户进站 +0427：等待用户进站 +0425：等待用户进站 +0424：等待用户进站 +0421：等待进度反馈 +0417：客户反馈更换了很多地方，重启车辆后，远控依然不生效。建议用户进站取日志 +0410：等待用户反馈 +0407：等待用户反馈 +0401：更换地方仍然远控失败，等待用户进站 +0320：等待用户反馈 +0320：等待TBOX日志分析，同时建议客户记录当前环境网络情况，然后换个网络环境好一点的地方再试一次。 +0319：指令下发了，tbox回复收到了，但是后续没有再上报执行结果了，35秒超时 +0318：等待日志 +0317：启动时间3月17日，11:11","15/05: The log has been obtained, and the platform has checked that there were successful remote control records for users from 12-14 days. This issue can be closed +13/05: yesterday customer launched engine remotely successfull, still keep in touch with the customer +13/05: Wait for the user to log in, try manually capturing logs after the meeting +29/04：waiting customer go to dealer +27/04：waiting customer go to dealer +25/04：waiting customer go to dealer +24/04：waiting customer go to dealer +21/04: Awaiting feedback on progress. +17/04：Customer feedback after replacing many places and restarting the vehicle, the remote control still does not work.Suggest customer go to dealer for tbox logs.@Evgeniy +17/04: asked the customer for feedback, waiting -> still doesn't work -> added new video. Operation date and time 17/04/2025 at 9:50 am Moscow time +10/04： Waiting for customer feedback. +07/04： Waiting for customer feedback. +01/04:Changing places still fails remote control, waiting for users to enter the station. +25/03：Still waiting +20/03:Waiting for the TBOX logs to be analysed, and at the same time suggesting that the customer record the current environment network conditions, and then try again in a different place with a better network environment.@Evgeniy +19/03:The remote control command was issued, the tbox replied that it received it, but then it did not report the result of the execution, 35 seconds timeout. +18/03：Waiting for the log.@Evgeniy +17/03: Operation date/time: 17.03 at 11:11",Low,close,local O&M,Evgeniy,15/05/2025,CHERY TIGGO 9 (T28)）,LVTDD24B8RG093060,,,"LOG_LVTDD24B8RG09306020250515045214.tar,IMG_5460.MP4,image.png,image.png",Evgeniy,,,,,,59 +TR506,Mail,17/03/2025,,Remote control ,Remote control doesn't work + impossible to see status of car ,"0320：等待反馈 +0319：平台已间该用户在3月16日使用远控成功，建议明日例会关闭此问题 +0319：平台未见该时间段远控，请属地运维核实是否为网络故障 +0318：无法看见车况，转平台检查 +0317：启动时间：19:21。3.15","March 25: closed +March 20: Waiting for feedback. +March 19：The platform has been successfully used by the user on March 16, suggesting that the issue be closed at tomorrow's regular meeting.@Evgeniy +March 19：The platform does not see the remote control of the time period, please local operation and maintenance to verify whether it is a network failure.@Evgeniy +March 18:Turn to analysis. +March 17: Operation date/time: 15.03 at 19:21",Low,close,local O&M,Evgeniy,25/03/2025,JAECOO J7（T1EJ）,LVVDD21B3RC055187,,,"LOG_LVVDD21B3RC05518720250317131142.tar,image.png",Evgeniy,,,,,,8 +TR507,Mail,18/03/2025,,Remote control ,"Remote control stopped working. TSP: last tbox login 2025-02-19 22:42:54, high frequency data +2025-02-13 09:55:58. MNO: apn1 started working for 100% after the traffic was used up on March, 17th.","0409:建议在OTA群中讨论 +0408:会后讨论是否加入升级清单. +0325：三月未见TBOX登录记录，已尝试刷新SIM卡状态，建议用户重启车辆，重新尝试远控。@Vsevolod Tsoi +0324:询问是否采用OTA方式 +0320:用户流量已用完，停apn2 +0320:检查套餐使用使用情况，核实是否用完","0409：Suggest discussing in OTA group +0408：After the meeting, we will discuss whether to add it to the upgrade list. +25/03：March did not see TBOX logging records, SIM card APN2 is used up, APN1 has remaining traffic. An attempt has been made to refresh the SIM card status, and the user is advised to restart the vehicle and retry remote control.@Vsevolod Tsoi +20/03: Can this car be added to the OTA TBOX SW update when released ?",Low,close,local O&M,Vsevolod Tsoi,17/04/2025,EXEED RX（T22）,LVTDD24B3RG031971,,,,Vsevolod Tsoi,,,,,,30 +TR508,,19/03/2025,,Network,APN1/APN2 doesn't work. After WIFI sharing any functions,"0610：等待用户进行OTA升级 +0605:等待更新 +0603:等待更新 +0520；等待更新 +0515：等待用户下载并OTA +0508:反馈已进行全量推送 +0506：会后与韦工确认时间 +0427：等待OTA升级申请流程，流程结束进行全量推送。 +0425：网络阻塞问题，等待OTA升级。售后技术升级通知已结束、OTA升级申请流程中。流程结束进行全量推送。 +0421：等待分析结果反馈 +0417:TSP4月1日下发日志上传指令，现已获取到TBOX日志，等待分析。@董雪超 +0401:TSP4月1日下发日志上传指令，现已获取到TBOX日志，等待分析@何文国 +0321:转TBOX分析，等待抓取日志 +0321:MNO已查看，用户流量充足，双APN配置正常，3/15号有流量消耗记录 +0321:MNO查询流量情况","24/06: still not upgraded yet. TR is temporarily closed. +16/06: still not upgraded. I asked one more time to upgrade SW +10/06: checked out - still not upgraded yet +10/06: not upgraded +05/06: not upgraded +03/06: still not upgraded yet. +29/05: downloaded but still not upgraded yet. +19/05: OTA upgrade is downloaded on May, 15th. Wait for upgrade. +15/05: Waiting for users to download and OTA +08/05: Feedback has been fully pushed +06/05: Confirm the time with Mr. Wei after the meeting +27/04: Wait for the OTA upgrade application process, complete the process and proceed with full push. +25/04: Network blockage issue, waiting for OTA upgrade. The after-sales technical upgrade notification has ended and the OTA upgrade application process is in progress. At the end of the process, full push will be carried out. +21/04:In process,waiting for answer +17/04: Waiting for feedback on analysis results On April 1st, TSP issued a log upload command and has now obtained the TBOX log, waiting for analysis. +10/04:TSP issued a log upload instruction on 1 April, TBOX logs have now been obtained and are waiting to be analysed. +01/04:TBOX logs have been captured and are waiting to be analysed. +21/03:Transferring to TBOX for analysis, waiting to capture logs.@Evgeniy +21/03:MNO has viewed, user has sufficient traffic, dual APN configuration is normal, traffic consumption record on 3/15",Low,temporary close,TBOX,董雪超,24/06/2025,EXEED RX（T22）,LVTDD24B3RG019190,,,LOG_LVTDD24B3RG01919020250401035850.tar,Evgeniy,,,,,,97 +TR515,Mail,24/03/2025,,HU troubles,VK services do not work due to no IHU log in available in TSP since activation date 2025-03-22. Customer loged in the member center using network shared via smartphone.,"0417:继续等待 +0415:等待DMClogs +0410:继续等待 +0408:等待DMClogs +0324: IHU 在 PKI 中的登录没有问题，但在 TSP 中自激活以来没有 IHU 登录（见所附图片）。因此，VK&Navi 无法使用。它们只能通过智能手机网络工作。请经销商提供 DMC 日志。@Vsevolod Tsoi","18/04: checked out in TSP: 1st IHU log in is on April, 10 after sim card activation on March, 23. Customer's feedback - everything started working => TR closed. +17/04：waiting for DMC logs +15/04：still waiting +10/04：still waiting +08/04：waiting for DMC logs +24/03: IHU log in is OK in PKI however there were no IHU log in in TSP since activation (see pictures attached). Therefore, VK&Navi are not available. They work with smartphone's network only. DMC log is requested at dealer.@Vsevolod Tsoi",Low,close,PKI,陆敏,18/04/2025,EXEED RX（T22）,LVTDD24B0RG014142,,,"PKI_status.JPG,IHU_log_in&out_status.JPG",Vsevolod Tsoi,,,,,,25 +TR516,Mail,24/03/2025,,PKI problem,Navi doesn't work because of error in PKI.,"0416：等待反馈 +0410：属地运维会议后确认状态 +0325:属地运维已通过更换HUid，查看PKI证书有成功记录。建议用户进站，复现问题，并取对应的DMC日志，操作说明会上传附件。","April 17: asked again, waiting- solved +16/04：waiting for feedback +10/04:localO&M will confirm this after the meeting. +25/03：The local O&M has already checked the PKI certificate by replacing the HUid with a successful record. It is recommended that the user enter the dealer, reproduce the problem, and take the corresponding DMC logs, the operation instructions will be uploaded as an attachment.",Low,close,PKI,陆敏,17/04/2025,EXEED RX（T22）,XEYDD14B3RA001286,,,"image.png,e46c872d-2631-45c6-ad65-c24a0693fd97.jpeg",Evgeniy,,,,,,24 +TR518,Mail,26/03/2025,,OTA,"There were no IHU login record in TSP nor in PKI since activation date March, 1st - see pictures attached. Therefore, customer can't log in the member center. An error message ""poor network"" comes up when trying to scan QR code or use the mobile phone number to enter in the member center. +自 3 月 1 日激活以来，TSP 和 PKI 中都没有 IHU 登录记录--见附图。 因此，客户无法登录会员中心。 在尝试扫描二维码或使用手机号码进入会员中心时，会出现 ""网络不良 ""的错误信息。","0807: 按照约定 - 暂时关闭。收到反馈后将重新开放。 +0804: 有关升级的反馈意见正在等待经销商的回复。 +0731：等待OTA结果反馈 +0728：等待OTA结果反馈 +0715：新版本已发属地运维转发给售后团队，等待经销商邀请客户进站刷新 +0709：升级错误DMC版本，经销商手里依然是02.01.00未修复版本，等待提供新版本给属地运维重新升级@郭宏伟 +0701: 建议客户进站通过USB升级DMC版本. （目前已释放的版本:02.02.00_01.37.33） +0701：客户反馈-没有可用的二维码。一个“坏网络”的信息仍然出现-查看附件图片 +0626：等客户验证 +0619: TSP平台未查看到IHU登录记录, PKI有记录。OTA已小批量推送完成DMC升级，待属地运维跟客户确认重新登录是否已恢复。 +0618：升级已完成，建议关闭此问题 +0605: 等待属地更新 +0603：请用户自行查看DMC软件版本 +0522: 已升级完成，待客户反馈确认版本信息 +0520：会后检查该车是否存在于OTA列表中 +0513:该车也在OTA清单中 +0506：会后确认测试结果 +0427：等待测试结果反馈 +0424：等待测试结果反馈 +0421：等待测试结果反馈 +0417：等待OTA测试验证 +0414：分析结果为主机软件版本太低了，拟加入T22小批量推送中 +0411：日志已发送，等待分析结果 +0401:TSP显示车辆绑定SIM卡状态正常，MNO车卡关系一致，与TSP一致，转DMC分析.@许哲霖 +0331:DMC日志已附 +0326：建议车机使用手机网络，同时抓取DMC日志","07/08: As agreed - tempoararily closed. will be re-opened when getting a feedback. +04/08: feedback on upgrade is sitll pending from dealership. +31/07: still wait for feedback +28/07: wait for feedback on upgrade. +10/07: new request for DMC SW upgrade with the latest version ""G7PH_EXEED T22 INT HS_SOP8_FULL_11936_250211_R"" has been made to ASD team. Wait for invitation of customer to dealer. +0709：Upgrade the wrong DMC version, dealers still have 02.01.00 unfixed version in their hands, waiting for the new version to be provided to the local O&M to re-upgrade.@郭宏伟 +07/07: request for DMC upgrade with USB was sent on July, 2nd. Wait for upgrade result. +0701: It is recommended that customers log in to the station and upgrade the DMC version via USB. (currently released version：02.02.00_01.37.33）@Vsevolod Tsoi +26/06: customer's feedback - no QR code available. A message ""Bad network"" still comes up - see photos attached. +23/06: user had already been asked to try enteting to member center with QR code. Wait for feedback. +0623: DMC was upgraded by OTA as a small batch test, waiting for local O&M to confirm with the customer that logging back in has been restored.@Vsevolod Tsoi +0618：Upgrade completed, it is suggested close this tracking +0603: Please check the DMC software version by yourself. +29/05: please check the picture attached from FOTA - we see no any information reflected => not possible to check the version. +22/05:You can check the version number in the OTA backend to see if it has actually become new. If it has, you don't need to worry about it. Just tell the customer that it shows a bug, but it's actually successful@Vsevolod Tsoi +19/05: car has never been connected to FOTA server - see picture attached. How the cars is going to be upgraded OTA? +0513: The car is also on the OTA list +0506: Confirm test results after meeting +21/04: Waiting for feedback on test results. +17/04： waiting for T22 small batch push . +14/04: The analysis result shows that the host software version is too low, and it is planned to be added to the T22 small batch push . +11/04: The log has been sent and is awaiting analysis results +01/04:Turn to DMC analysis.@许哲霖 +31/03: DMC log attached +26/03:It is recommended to connect a mobile phone hotspot to capture DMC logs while connected to the network. DMC is required for investigatio. Request for DMC log to do@Vsevolod Tsoi",Low,temporary close,DMC,郭宏伟,07/08/2025,EXEED RX（T22）,LVTDD24B6RG021144,,"Клиент обращался в Дилерский Центр EXEED ЦЕНТР КЛЮЧАВТО КИПАРИСОВАЯ Город Сочи + +Руководитель Сервиса-Антаева Наталья Сергеевна –Телефон-89189166991 + +Руководитель клиентской службы-Катионова Елизавета Андреевна-89654754848","DMC_SW_update_number.JPG,DMC_data.jpg,WhatsApp Image 2025-06-25 at 17.55.01 (1).jpeg,WhatsApp Image 2025-06-25 at 17.55.01.jpeg,FOTA_status.JPG,DMC_log.zip,TSP_IHU_login_record.JPG,PKI_IHU_status.JPG",Vsevolod Tsoi,,,,,,134 +TR519,Mail,27/03/2025,,Remote control ,Remote control doesn't work + impossible to see status of car ,"0826 已向 ASD 发出请求，正在等待 +0819：等待用户进站提供日志 +0814：暂无日志 +0811:已向 ASD chery 申请 DMC 和 TBOX 日志 +0805：多次远程获取日志失败，建议用户进站复现远控及OTA操作，并抓取TBOX及主机日志 +0804: OTA徐文韬反馈，该车为TBOX自升级失败，具体原因需TBOX分析，两次升级时间为7月16日20：03，25日02：26. +0731：""更新失败，已恢复到 ""更新前状态“联系服务，转 OTA 分析 +0729：属地运维会后确认 +0721: 已对客户进行OTA推送新版本，请转达客户点击进行升级后重启车辆验证 +0717:远控依然无法使用，T-BOX最后登录时间2025-06-02，2025-06-07远控发动机提示网络超时，其余时间无记录。车机登录记录正常，SIM卡状态正常 +0424:无反馈暂时关闭 +0421：等待进度反馈 +0417:等待用户反馈 +0407:等待用户反馈 +0403：MNO反馈网络正常，建议用户在信号较好的地方重启车辆等待15分钟过后尝试远控。 +0402:等待MNO反馈 +0401:用户反馈重试但远控失败，TSP显示有TBOX登录记录SIM状态及流量正常，26,27,31号有远控发动机，车锁控制，一键加热指令，多数为指令下发了，tbox回复收到但未上报执行结果，少数为TBOX无响应，35s超时。 +0327:视频描述时间段平台未收到指令，查询远控仅有查询车辆状态，无远控指令，且查询车辆状态失败，提示35秒超时,仅有26日车辆TBOX登录记录且26日远控正常，无27日记录，建议用户在信号好的地方尝试重启车辆后再进行远控","21/10: still no feedback +18.09: asked ASD again +08/09: no feedback +26/08: request was send to ASD, waiting +19/08: Waiting for users to come in and provide logs +14/08: No logs available at this time +11/08: have sent request to ASD chery for DMC and TBOX log +05/08：Failed to get logs remotely for many times, +suggest users to enter the station to reproduce the remote control and OTA operation, and capture the TBOX and host logs. +04/08:Users are advised to make a pit stop to check the TBOX +30/07: the customer can't update - see screenshot +29/07：Confirmation after local O&M meeting +21/07: The new version has been pushed to the customer by OTA,Please pass on to customers to upgrade then restart vehicle validation @Evgeniy +16/07: user gave feedback that remote control still doesn't work +24/04: user gave feedback that he tried to use remote control from different places, also he tried restart vehicle and waiting 15 minutes in location with good signal-it doesn't help +24/04:Temporarily closed without feedback +21/04: Awaiting feedback on progress. +17/04： Waiting for customer feedback. +07/04： Waiting for customer feedback. +03/04:MNO feedback: The network is normal. It is recommended that the user restart the vehicle in a location with good signal and wait for 15 minutes before attempting remote control. +02/04：waiting for feedback +01/04:User feedback retry but remote control failed, TSP shows that there is TBOX login record SIM status and traffic normal, 26,27,31 have remote control engine, lock control, one key heating instructions, most for the instructions issued, tbox reply received but not reported the results of the implementation of a few for the TBOX is not responsive, 35s timeout. +27/03:Video description of the time period the platform did not receive instructions, query remote control only query vehicle status, no remote control instructions, and query vehicle status failed, prompted 35 seconds timeout, only the 26th vehicle TBOX login record and remote control normal , no record on the 27th, we recommend that the user try to restart the vehicle in a place with a good signal and then remote control. +27/03: operation date 27.03. Operation time - see video in attachmentUser feedback retry but remote control fails, after the meeting troubleshooting",Low,Waiting for data,OTA,徐文韬,24/04/2025,CHERY TIGGO 9 (T28)）,LVTDD24B9RG093147,,,"image.png,IMG_5188.MP4",Andrey Grishin,,,,,,28 +TR522,Mail,02/04/2025,,Remote control ,Remote control doesn't work + impossible to see status of car ,"0424:协商一致，暂时关闭 +0421：等待用户反馈 +0417：等待用户反馈 +0410：等待用户反馈 +0402：远控时间为莫斯科时间14:50，TSP查询SIM已激活，至问题工单提交时刻TSP可见车辆处于在线状态，有TBOX登录记录，唤醒TBOX失败，35秒超时，49分下发的方向盘加热，50下发的发动机启动。建议用户换个地方重启车辆后尝试远控","24/04：Agreed upon, temporarily closed. +21/04: Awaiting feedback on progress. +17/04： Waiting for customer feedback. +10/04：Still waiting for feedback. +03/04:remote control time for Moscow time 14:50, TSP query SIM has been activated, to the moment of the problem work order submission TSP visible vehicle is in the online state, there is a record of TBOX login, wake up TBOX failed, 35 seconds timeout, 49 minutes under the steering wheel heating, 50 under the engine start. Suggest the user to try remote control after restarting the vehicle in another place. +02/04: Operation date March 2 at 14:50 Moscow time (18:50 customer's time) +(唤醒下发后tbox无响应，35s超时)",Low,temporary close,local O&M,Evgeniy,24/04/2025,CHERY TIGGO 9 (T28)）,LVTDD24B7RG128462,,"The customer has old info in app -> old status in tsp. He was a trip to Kazakhstan, after that APN1 stops working and his last connection was in Kazakhstan.","img_v3_02kv_72178698-7547-4743-9468-22962e6d53hu.jpg,IMG_5314.MP4",Evgeniy,,,,,,22 +TR523,Mail,02/04/2025,,Remote control ,"Neither vehicle status data reflected in the mobile app nor remote control working. No TBOX login record since the activation date on April, 4th. PKI is NOK however IHU ID is full one and OK in the TSP (see attachments).","0424：协商一致，暂时关闭、 +0421：等待用户反馈 +0417:等待用户反馈远控是否可用 +0404：客户已按要求重启IHU，等待反馈 +0402:TSP未见TBOX登陆记录，无实时数据上传，SIM卡未见今年流量变动，已通过手动停用再启用SIM卡，已见TBOX重启记录，车辆已进入深度睡眠，建议使用物理钥匙着车，运行一会后尝试远控","24/04：Agreed upon, temporarily closed +21/04: Waiting for feedback . +17/04:wait for customer's feedback whether remote control started working again. +15/04: wait for customer's feedback whether remote control started working again. TSP and MNO are OK. Last tbox log in on +2025-04-14 15:03:02; IHU on 2025-04-14 13:07:22. +04/04: customer was contacted and asked to reboot the IHU. Wait for feedback. +0204:TSP did not see TBOX login records, no real-time data upload, SIM card did not see this year's traffic changes, has been manually deactivated and then enabled SIM card, has seen TBOX restart records, the vehicle has entered deep sleep, it is recommended to use the physical key to start the car, run for a while and then try remote control.",Low,temporary close,local O&M,Vsevolod Tsoi,24/04/2025,EXEED RX（T22）,XEYDD14B3RA009271,,,"TSP_status.JPG,a5ca243e-a682-43d9-b8f1-be2cb5e8b14a.jpg,PKI_status.JPG,8652efe5-1a7f-476b-ad52-71d9f4c1999b.jpg,6397cd34-a8ca-4e7a-a703-6f57d01ed867.jpg,098c152a-20c8-49d9-aa82-277d28aa1d5a.jpg",Vsevolod Tsoi,,,,,,22 +TR526,Telegram bot,04/04/2025,,VIN number doesn't exist,Car doesn't exist in TSP platform,"0415:TSP已见该车，属地运维建议检查有无其他问题 +0407:属地反馈此车架号在DBMS中，等待数据拉送 +0407:请属地运维确认该VIN号是否正确，在MES中未查询到该VIN","April 17: Car bound in the TSP. No feedback from customer -> closed + +April 15: TSP has seen the vehicle, and local operations suggest checking for any other issues.@Kostya +April 09: Check screenshot from PKI platform in the attachment. VIN is correct and car trying to connect with TSP @赵杰 +April 07：This car exist in sales DBMS (Logic star) @赵杰 +April 07：Please ask the local O&M to confirm that the VIN number is correct and that it is not queried in the MES.@Kostya",Low,close,MES,Kostya,17/04/2025,CHERY TIGGO 9 (T28)）,LVTDD24B9RG116006,,TGR0001138,image.png,Kostya,,,,,,13 +TR529,Mail,07/04/2025,,Traffic Payment,No network available after payment for superpackage on 1st April,"0424：VK问题等待生态与产品沟通，续费问题建议在问题排查群确认最终解决方案 +0422:生态反馈已对该车续费，是否为逻辑问题需与产品讨论 +0422：转生态信源排查。@袁清 +0417: 客户反馈： VK 视频和信使等 VK 应用程序无法运行。其他功能正常。出现错误信息 ""您的权利期限已过。只有在付款后才能恢复""，请参见所附视频。 +0414: 客户反馈：所有选项都开启了 +0407：三方评估问题降级，并采拟于MO凌晨将车辆SIM卡重启，7日晚间APN2已恢复正常（MNO未对SIM重启） +0407：MNO初步排查无问题，拉起TBOX，DTS，MNO三方联合排查，等待车辆TBOX与运营商日志分析 +0407：TSP查询TBOX近期有登录记录，车机SIM已激活，转MNO排查","24/04：The VK issue is awaiting communication between the ecosystem and the product. For renewal issues, it is recommended to confirm the final solution in the problem investigation group +If the user doesn't use the car, they can renew their subscription on their phone and start using the network as soon as they get in the car (turn on the ignition) +When users are in the car, if they want to renew their subscription on their mobile phone, they need to lock the car for 5 minutes and then use the car (start the engine), and they will have network connection + +22/04:Eco feedback has been renewed for this vehicle, whether it is a logic problem needs to be discussed with the product +22/04:Turning to eco sources to troubleshoot. +17/04: customer's feedaback: VK apps such as VK video and messenger do not operate. The rest works well. An error message comes up ""Term of your rights is over. They may be restored after payment only "" see video attached. +14/04: customer's feed-back: everything started +07/04: Three-party assessment of the problem degraded, and proposed to restart the vehicle SIM card in the early hours of MO +07/04: MNO preliminary check no problem, pull up the TBOX, DTS, MNO three-party joint investigation, waiting for the vehicle TBOX and the operator's logs to be analysed +07/04: TSP query the TBOX has a recent log-in record, the vehicle SIM has been activated, and transferred to the MNO to check the Temporary solution is urgently applied => issue is fixed.",Low,close,local O&M,Vsevolod Tsoi,30/04/2025,EXEED VX FL（M36T）,LVTDD24B9PD638357,,,"вк видео 2.mp4,LOG_LVTDD24B5PD60643920250407130712.tar,VID-20250403-WA0001.mp4,LOG_LVTDD24B9PD63835720250407120150.tar,20250407-115610.png,img_v3_02l4_a9c6d4cd-2073-49d1-9317-2faf98ee59hu.jpg",Evgeniy,,,,,,23 +TR530,Mail,07/04/2025,,APN 2 problem,"No network available however apn2 had been re-enabled on April, 1st - see attachments","0429:协商一致暂时关闭 +0427:等待属地反馈问题状态 +0424:等待属地确认问题状态 +0421:MNO反馈该车sim卡被停用，用户不能联网，排查发现是TSP频繁调用激活和停卡API(注意短时间内频繁调用MTS是不会响应的)，已手动恢复，请确认问题状态 +0417：继续等待 +0415:等待属地运维反馈 +0410:属地运维会后确认 +0407：TSP查询到最近一次TBOX登录记录为4月4日，SIM卡状态正常，尝试手动重启SIM卡，建议用户尝试重启，如仍不可用，再提供车机页面截图","27/04：Waiting for confirmation of the issue status by the local authorities. +24/04：Waiting for confirmation of the issue status by the local authorities.@Vsevolod Tsoi +21/04: MNO feedback the car sim card was deactivated, the user can not network, troubleshooting found to be the TSP frequently call activation and deactivation API (note that a short period of time frequently call MTS is not responsive), has been manually restored, please confirm the problem status. +17/04： Waiting for customer feedback. +15/04:waiting for local OM feedback. +10/04：Still waiting for feedback. +10/04:after meeting check +07/04: TSP queried the latest TBOX login record for 4 April, SIM card status is normal, try to manually restart the SIM card, we recommend that users try to restart, if still unavailable, and then provide screenshots of the IHU page.",Low,close,local O&M,Vsevolod Tsoi,13/05/2025,CHERY TIGGO 9 (T28)）,LVTDD24B0RG091450,,,"img_v3_02l4_019ec4d8-466d-490a-8d0c-f6cc7952d8hu.png,img_v3_02l4_5ffccd9e-b6cb-42e3-a72b-745848a44chu.jpg",Vsevolod Tsoi,,,,,,36 +TR531,Mail,07/04/2025,,Remote control ,The customer can't use any commands - see scrheenshot.,"0520：问题临时方案已提供，问题暂时关闭 +0515:OJ团队将会限制在应用市场的APP可使用的安装版本 +0429:等待属地反馈进度 +0427:等待属地反馈进度 +0424: 属地会后确认 +0421：建议邀请OJ研发进群沟通 +0417：此问题会后联系研发确认是否可行 +0415：等待用户反馈 +0410：OJ反馈此问题需中方提供帮助，建议用户更新安卓版本 +0409：OJAPP反馈明日会上交流 +0408：建议查看APP日志，确认是未连接平台还是APP本身问题. +0407: TSP见TBOX登录注销正常，SIM卡状态正常，未查询到远控记录，转O&JAPP分析 +0407：O&J反馈非O&J侧问题，怀疑服务器有问题。等待属地运维上传截图","20/05: Interim program for the issue has been provided and the issue is temporarily closed +15/05：The OJ team will limit the installation versions available for apps in the app market. +29/04: Waiting for local OM feedback +27/04: Waiting for local OM feedback +24/04：Local OM after meeting check for it. +21/04:Suggest inviting OJ R&D into the group for communication +17/04:We will contact R&D to confirm the feasibility of this issue. +15/04: Waiting for user feedback +10/04: OJ feedback that this issue needs help from China, suggesting users to update Android version +9/04：OJAPP feedback will be discussed at tomorrow's meeting +8/04：Suggest checking the app logs to confirm whether it is an issue with not connecting to the platform or the app itself +07/04:TSP see TBOX login logout is normal, SIM card status is normal, did not query the remote control records, turn O&JAPP analysis. +07/04: O&J team said that problem with server. It's ok from them side. +Operation date& time: 7 April at 16:09 Moscow time",Low,temporary close,O&J-APP,Vadim,20/05/2025,JAECOO J7（T1EJ）,LVVDB21B9RC069293,,,"4289dd80-3ef3-41c7-873c-8d417956bb9e.jpeg,LOG_LVVDB21B9RC06929320250407161145.tar,image.png",Evgeniy,,,,,,43 +TR534,Mail,08/04/2025,,Traffic Payment,"No network available after purchasing super package on april, 5th. Status: SIMBA - OK as well as MNO - apn2 is active","0424:续费问题建议在问题排查群确认最终解决方案 +0421：等待用户反馈 +0417：等待用户反馈 +0415：重复请求 - 等待客户反馈。 +0409：询问客户是否允许访问网络。等待反馈。 +0408：MNO反馈SIM卡正常，暂时尝试将SIM卡重启","24/04:Renewal issues are recommended to confirm the final solution in the Troubleshooting Group. +21/04: Waiting for user feedback +17/04: Waiting for user feedback +15/04: repeat request - wait for customer's feedback. +09/04: client is asked if the the access to the network is granted. Wait for feedback. +0408: MNO feedback that the SIM card is normal, temporarily attempting to restart the SIM card",Low,close,local O&M,Vsevolod Tsoi,30/04/2025,EXEED VX FL（M36T）,LVTDD24B7PD577171,,,"LOG_LVTDD24B7PD577171_08_04_2025.tar,MON_apn2_status.JPG,Payment_status_SIMBA.JPG",Vsevolod Tsoi,,,,,,22 +TR535,Mail,08/04/2025,,Traffic Payment,"No network available after purchasing super package on april, 8th. Status: SIMBA - OK. apn2 is re-enabled however there is no network available.","0424:续费问题建议在问题排查群确认最终解决方案 +0421：等待用户反馈 +0417：等待反馈。 +0415：再次询问客户是否允许访问网络以及应用程序是否开始工作。 +0409：询问客户是否可以访问网络。等待反馈。 +0408：MNO反馈SIM卡正常，暂时尝试将SIM卡重启","24/04:Renewal issues are recommended to confirm the final solution in the Troubleshooting Group. +21/04：waiting fo人feedback +17/04：waiting fo人feedback +15/04: customer is asked again whether the access to the network is granted now as well as apps started working. wait for feedback. +09/04: client is asked if the the access to the network is granted. Wait for feedback. +0408: MNO feedback that the SIM card is normal, temporarily attempting to restart the SIM card",Low,close,local O&M,Vsevolod Tsoi,30/04/2025,EXEED VX FL（M36T）,LVTDD24B3PD557290,,,"Apn2_status.JPG,SIMBA_payment_status.JPG,Apn2_enable.JPG,LOG_LVTDD24B3PD557290_08_04_2025.tar",Vsevolod Tsoi,,,,,,22 +TR537,Mail,09/04/2025,,Navi,Navi doesn't work,"0424：会后属地确认状态 +0422：等待反馈 +0416：已上传指导视频，请指导用户打开导航权限即可解决；等待反馈 +0409：视频提示打开天气正常，打开导航提示闪退，转座舱排查","29/04：temporary close +24/04: Post meeting territorial confirmation status +22/04: waiting for feedback +16/04: Instructional video has been uploaded, please instruct the user to open the navigation permissions can be solved.@Evgeniy +09/04：Video prompt shows normal weather when turned on, navigation prompt crashes when turned on, switch to ecological investigation.",Low,temporary close,local O&M,Evgeniy,29/04/2025,EXEED RX（T22）,LVTDD24B9RG033319,,,"iChery20250417-104037.mp4,IMG_5385.MP4,image.png",Evgeniy,,,,,,20 +TR538,Mail,10/04/2025,,Traffic Payment,Super package is paid however customer still has no access granted to the network. Date of payment 2025-04-09 15:28:09 ,"0424:续费问题建议在问题排查群确认最终解决方案 +0422：建议用户等车辆休眠下电后，重新启动，观察流量是否恢复 +0417：MNO排查流量使用正常，流量有剩余，建议按照暂时处理方式处理，最终解决方法等待讨论 +0415：等待反馈 +0410：已见MNO中APN1已用完，需与MNO核实APN1使用策略","24/04:Renewal issues are recommended to confirm the final solution in the Troubleshooting Group. +22/04: Users are advised to wait for the vehicle to hibernate and power down, restart and observe whether the traffic is restored +17/04: MNO troubleshooting traffic use is normal, there is a surplus of traffic, it is recommended to deal with it in accordance with the temporary processing method, and the final solution is waiting to be discussed +15/04: Waiting for the feedback +10/04: It has been observed that APN1 in MNO has been used up, and it is necessary to verify the APN1 usage strategy with MNO",Low,close,local O&M,Vsevolod Tsoi,30/04/2025,EXEED VX FL（M36T）,LVTDD24B8PD630668,,,"Apn2_NOK.JPG,Apn2_enable_status.JPG,Simba_status.JPG",Vsevolod Tsoi,,,,,,20 +TR539,Mail,10/04/2025,,Remote control ,"Incorrect operation of remote control - commands are not executed. Last TBOX log in 2025-04-10 13:52:33. +High frequency data 2025-04-10 13:52:31. apn1&2 are available and active in MNO.","0427:平台查询本月远控记录，发现19日远控成功，后续无远控使用记录，建议用户再试试远控功能 +0424：会后平台检查日志是否已获取，及远控时间 +0421：等待用户反馈 +0417：无客户反馈信息，等待客户反馈 +0410：已要求客户提供操作时间，操作指令，等待对应日志","27/04：The platform checked the remote control records for this month and found that the remote control was successful on the 19th, but there were no subsequent records of remote control usage. It is recommended that users try the remote control function again.@Vsevolod Tsoi +24/04：After the meeting, the platform checks whether the logs have been obtained and the remote control time. +21/04：waiting fo人feedback +17/04: no feedback so far. +10/04: customer is asked to provide the input data for investigation such as an operation time/date, TBOX log.",Low,temporary close,local O&M,Vsevolod Tsoi,29/04/2025,EXEED VX FL（M36T）,LVTDD24B9RD067522,,,Picture_1.jpg,Vsevolod Tsoi,,,,,,19 +TR541,Mail,11/04/2025,,Application,Remote control operates correctly. However an error message comes up when click on account in the mobile app - see photo attached.,"0429：属地反馈用户已正常使用，关闭此问题 +0427：等待属地反馈进度 +0424:用户反馈车控可用，但仍提示账户不存在，APP后台查询账户已被注销，会上商讨结果是将APP解绑信息同步至TSP，用户可重新注册绑车。 +0422：APP后台反馈账号状态是注销，询问车控是否可以正常使用， +0421：等待结果反馈 +0417:一直存在这个现象,会后与APP核实情况,转用户APP分析.@张明亮 +0416：请属地确认用户是一直存在这个现象，还是就发了生这一次，后面就好了。 +0416：TSP见流量与TBOX登录记录正常，转EXEED用户APP排查","29/04:Local feedback: The user has been using it normally. Close this issue. +27/04: Waiting for local feedback on progress +24/04: The user reported that the car control is available, but still prompted that the account does not exist. The APP backend checked that the account has been cancelled. The discussion result was to synchronize the unbinding information of the APP to TSP, and the user can re register and bind the car. +22/04: APP background feedback account status is cancellation, asked whether the car control can be used normally.@Vsevolod Tsoi +21/04: Waiting for feedback on results. +17/04:This phenomenon has always existed, after the meeting with the APP to verify the situation, to the user APP analysis. +17/04: it's confirmed that message comes up every time he clicks on account icon shown on the picture attached. +April 16:Please confirm if the user has been experiencing this phenomenon all along, or if it was issued just this one time, and then it was fine.@Vsevolod Tsoi +April 16: TSP saw normal traffic and TBOX login records, transferred to EXEED user app for troubleshooting.Local feedback: The user has been using it normally. Close this issue",Low,close,用户EXEED-APP(User),张明亮,29/04/2025,EXEED RX（T22）,LVTDD24B5RG032670,,,image-11-04-25-10-20.png,Vsevolod Tsoi,,,,,,18 +TR542,Telegram bot,14/04/2025,,OTA,Update failure. Check attachments,"0515：协商一致暂时关闭 +0506：建议用户重新尝试，如失败，抓取DMC日志 +0427：等待排查结果反馈 +0424：等待排查结果反馈 +0421：等待排查结果反馈 +0417:已私信催次OTA刘金龙，正在排查中 +0414:TSP见该车登录注销状态正常，提供截图中提示连接的网络正常，截图错误提示：升级失败，请与售后联系，转OTA排查","15/05：Temporary closure by consensus +06/05：Suggest the user to retry, if it fails, capture the DMC logs. +27/04：Awaiting feedback on clearance results. +24/04：Awaiting feedback on clearance results. +21/04：Awaiting feedback on clearance results. +17/04: Private letter has been urged sub-OTA Liu Jinlong, is in the process of investigation. +14/04: TSP saw that the login and logout status of the vehicle was normal, and provided a screenshot indicating that the connected network was normal. The screenshot error message: upgrade failed. Please contact after-sales and transfer to OTA for troubleshooting.@刘金龙",Low,temporary close,OTA,刘金龙,15/05/2025,EXEED VX FL（M36T）,LVTDD24B8RD064739,,,"image.png,image.png,image.png,image.png,image.png",Kostya,,,,,,31 +TR543,Telegram bot,14/04/2025,,Remote control ,"Commands are not executed. Vehicle data is not updated in the app - shown as started and unlocked but in fact the car locked and the engine stopped. MNO: there is no apn1 available since April, 1st (see photo attached). Last tbox log in on +2025-04-16 08:15:54, last high frequency data 2025-03-06 08:39:11.","0520：等待更新 +0519：问题无反馈更新时长已超过两周，建议问题进行暂时关闭 +0515：建议用户重新尝试远控，因为老旧的记录可能已被覆盖，如仍有异常，再进行分析 +0513：等待用户进站 +0429：等待用户进站 +0427:MNO反馈网络连接正常，TBOX没有主动使用APN1导致日志无法上传，建议用户进站取日志 +0427:TSP尝试远程获取TBOX日志，未见日志上传，但平台显示车辆在线，转MNO排查@林兆国 +0424:等待Tbox日志及MNO分析结果 +0421：等待分析结果与TBOX日志反馈 +0417: 执行操作的坐标为60.068188和30.372103。 +0417: 转MNO排查网络,同时抓取TBOX日志分析。 +0416：平台查询远控提示35秒超时，建议用户反馈远控地的位置信息（经纬度）在信号较好的地方，重启车辆及手机APP后尝试远控。同时针对无APN1走动，建议抓取TBOX日志分析. +0416；反馈远控无法生效，车辆数据在APP中不显示，APN1自四月起不可用，但有TBOX登录记录，最后高频数据上传时间为2025-03-06 08:39:11.","29/05: checked in TSP - everythig is OK as well as in MNO. Temporary close. +0519: Issue no feedback update length has exceeded two weeks, suggesting issue for temporary closure +15/05: It is recommended that users try remote control again, as old records may have been overwritten. If there are still abnormalities, further analysis should be conducted.@Vsevolod Tsoi +13/05：waiting customer go to dealer +29/04：waiting customer go to dealer +27/04：MNO feedback: The network connection is normal, but TBOX did not actively use APN1, resulting in the inability to upload logs. It is recommended that users log in to retrieve logs.@Vsevolod Tsoi +27/04:TSP attempted to remotely obtain TBOX logs, but no logs were uploaded. However, the platform showed that the vehicle was online, so it was transferred to MNO for investigation. +24/04：Waiting for MNO analysis results and TBOX log +21/04: Waiting for analysis results and TBOX log feedback +17/04:Turn MNO analysis.Also recommend to grab the TBOX logs.@Vsevolod Tsoi +17/04: coordinates are 60.068188 & 30.372103 where the operation was executed. +16/04:The platform query remote control prompts 35 seconds timeout, it is recommended that the user feedback the location information (latitude and longitude) of the remote control place where the signal is better, restart the vehicle and the mobile phone APP and then try remote control. Also recommend to grab the TBOX logs and analyse them for no APN1 walks. +16/04: command - stop the engine on April, 16th at 10:00. However, in fact the car was locked and the engine stopped.",Low,temporary close,local O&M,Vsevolod Tsoi,29/05/2025,CHERY TIGGO 9 (T28)）,LVTDD24B5RG089645,,,"Apn1_status.JPG,Stop_engine.jpg,Veh_data_mob_app.jpg",Vsevolod Tsoi,,,,,,45 +TR544,Mail,16/04/2025,,Remote control ,"After starting the engine remotely via mobile app, cutomer calls another command - driver seat heating. It's executed successfully exept that with driver seat heating command, air conditioning is also exectued but it's not needed. Also the engine is stopping when switching off the air conditionning or switching all the heating systems off. Please confirm if it's setup in this way or it's an issue.","17/04：油车设计上空调和座椅加热是关联的，设计如此，无需更改 +0416：询问app张明亮，得知需询问座舱，建议明日日会讨论","18/04: feedback is provided to customer's that this is operation algoritm of the app. Customer's feedback: if it worked seperately it would be better => client's wish. +17/04:The tanker is designed so that the air conditioning and seat heating are linked, this is a preset operation and there is no way to change it. +16/04: Asked app , learnt that need to ask about cockpit, suggested to discuss at tomorrow's day meeting",Low,close,local O&M,Vsevolod Tsoi,18/04/2025,CHERY TIGGO 9 (T28)）,LVTDD24B7RG118806,,,"Engine_started.PNG,AC+driver_seat_heating.JPG",Vsevolod Tsoi,,,,,,2 +TR545,Telegram bot,16/04/2025,,OTA,"Tbox update for T22 cant start engine after turning off by customer. +No any other remote control systems on the car according to the customer.","0729: SK 学习法在测试中，我们正在等待结果，以确认这种方法是否有用。可暂时关闭 +0722: 仍在等待测试后的反馈 +0717：仍在等待测试后的反馈 +0701：正在与 ASD 讨论测试溶质的问题 +0624:建议客户进站重新进行t-box SK学习 +0617：和TR547类似，会后反馈 +0605: 等待更新 +0529：仍无更新 +0519：邀请用户进站抓OTA日志 +0513:等待用户反馈 +0429：用户反馈周末有空会尝试重新操作，等待反馈 +0427：等待反馈重新尝试结果 +0424：等待反馈重新尝试结果 +0423：等待反馈重新尝试结果 +0421：等待反馈重新尝试结果 +0417：OTA反馈上报错误为远程上电失败，未进入升级流程，后台没有包传上来。可以让客户多试几次，如果仍然不行，使用u盘获取OTA日志 +0417:TSP见16日TBOX有重启记录且有短信下发通知，但截止北京时间17日9:00仍未见日志上传，转OTA排查 +0416:无法远程获取 TBox 日志。请求成功，但没有结果","0729: SK learning method in the test, we are waiting for results for confirm the usefulness of this method. +0722: Still waiting for feedback after tests +0717: Still waiting for feedback after tests +0701：In discuss with ASD about testing of the solution +0624: It is suggested that the customer re-enter the station for t-box SK learning again @Kostya +0610: SK learning - Work in progress -> Check SK learning main 547TR +0603: SK learning WIP +0529: waiting for customer feedback and logs +0527: Invited, waiting for comming and capture logs +0522: Invited, waiting for comming and capture logs +0519: Inviting users in to catch OTA logs @Kostya +15/05 SK learning issue, +WIP +13/05：Still waiting +29/04:User feedback will try to re-open when he have time over the weekend, awaiting feedback. +27/04: Asked customer. Waiting for feedback +24/04: Asked customer. Waiting for feedback +21/04:Waiting for feedback and trying again for results. +17/04：OTA feedback reported error as remote power-up failure, not entered the upgrade process, no package uploaded in the background. You can let the customer try a few more times, if it still does not work, use a USB stick to get the OTA logs.@Kostya +17/04: TSP saw TBOX reboot records and SMS notification on the 16th, but as of 9:00 BST on the 17th, no logs have been uploaded.Turn OTA analysis. +16/04: Can't get TBox log remotly. Request is success but there is no result",Low,temporary close,OTA,Kostya,29/07/2025,EXEED RX（T22）,XEYDD14B3SA012122,,,"image.png,image.png,image.png,WhatsApp Video 2025-04-16 at 14.04.39.mp4",Kostya,,,,,,104 +TR547,Mail,17/04/2025,,OTA,OTA update failed. It doesn't start. An error message comes up "Power on failure","1215: DMC、TBOX 都需要学习SK +0807：暂时关闭，等待经销商反馈后重新打开 +0804: 仍在等待 DMC 与 SK 的学习反馈，然后等待升级结果。 +0731: 仍在等待使用 SK 对 DMC 进行编程，以便通过 OTA 成功升级 TBOX SW（开机失败）。 +0728: 至今没有反馈。 +0722: 等待经销商的反馈。 +0714: XEYDD14B3RA002731: 在尝试启动 TBOX SW OTA 时出现开机失败的问题后，已发送 SK 的 DMC 编程请求。等待反馈。 +0714: 无更新。 +0710: 等待 TBOX 到货 +0703: 无更新。 +0701：仍在等待 TBOX 硬件发货。 +0624: 已订购 XEYDD14B3RA002658 型号的 TBOX 硬件。等待交货。一旦安装完毕，ASD 团队将对 SK 进行重新学习。 +0624：建议客户再次进入站点进行 t-box SK 学习 Vsevolod Tsoi +0609：仍在特别群聊中寻找解决方案 +0605: 仍在寻找解决方案。重置 TBOX，需要重新学习 SK => 等待 ASD 团队。 +0603: XEYDD14B3RA002658 上的 SK 学习失败，远程发动机启动仍无法工作。成立特别小组调查该问题 +0530：TBOX SK 学习计划于 6 月 2 日星期一进行。然后，恢复遥控操作，与客户确认。 +0529：客户再次表示遥控器仍然无法使用 (XEYDD14B3RA002658)。经了解，在对 DMC 进行编程后，还需要对 TBOX 进行 SK 学习。计划用于 CW23。 +0528：sk学习成功 问题已解决，等待关闭 +0527：转国内分析 +0519：邀请用户进站学写SK +0513：等待邀请用户进站,OTA +0430：OTA分析因为没有进行SK学习，远程上电防盗过不了，所以上电失败，建议用户进站，重新学习SK +0427:等待OTA分析 +0424:转OTA分析 +0421:等待OTA日志 +0417:需要OTA日志，请邀请客户进站处理，“需要进ota工程模式里 先点击收集log 然后插入u盘” +0417:TBox日志已附，操作视频已附，同TR545","15/12: DMC SW as well as TBOX need ti do SK +07/08: Temporarily closed. Will be re-opened upon receiving a feedback. +04/08: still wait for feedback on learning of DMC with SK and then upgrade result. +31/07: still wait for programming DMC with SK to let TBOX SW being upgraded successfully via OTA (power up failed). +28/07: no feedback so far. +22/07: feedback is pending from dealer. +14/07: XEYDD14B3RA002731: following the issue of power up failed upong trying to start TBOX SW OTA a request for DMC programming with SK has been sent. Wait for feedback. +14/07: no updates. +10/07: wait for TBOX arrival +03.07: no update. +01.07: still wait for delivery of TBOX HW. +24/06: order for TBOX HW had been placed for XEYDD14B3RA002658. Wait for delivery. Once it's installed, SK re-learning will be applied by ASD team. +0624：It is suggested that the customer re-enter the station for t-box SK learning again @Vsevolod Tsoi +09/06: still looking for a solution in the special group chat +05/06: solution is still in process. Reset TBOX and the SK relearning is required => wait for ASD team. +03/06: SK learning failed on XEYDD14B3RA002658, remote engine start still doesn't work. Special group is created to investigate the issue +30/05: TBOX SK learning is scheduled on Monday June, 2nd. Then, restore the remote control operation to confirm with customer. +29/05: customer is back again saying that remote control still doesn't work (XEYDD14B3RA002658). It was figured out that SK learning of TBOX is also required after programming of DMC. Planned for CW23. +28/05:sk learning success problem solved waiting for closure +27/05: XEYDD14B3RA002658 upgrade completed successfully after application DMC programming procedure provided. Request for programming is going to be sent to dealers for those customer's who faced the same issue with power-up failure when starting OTA upgrade. +26/05: SK learning failed for XEYDD14B3RA002658 following the instruction provided - see video @喻起航 +22/05: SK learning has been applied => still power-up failed VIN XEYDD14B3RA002658 @喻起航 +0519: Inviting users into the dealer to learn to write SK +0513: Waiting for invited users to enter the station for OTA. +30/04：OTA analysed that because there was no SK learning, the remote power-up theft could not be passed, so the power-up failed, and suggested that the user should come into the station and re-learn the SK +27/04: waiting OTA team analysis. +24/04: OTA log attached. +21/04: Waiting for OTA logs +17/04:ota logs not Tbox logs.""You need to go into ota project mode, click collect log and then insert the USB stick.""@Vsevolod Tsoi +17/04: tbox log attached as well as video.",Low,close,OTA,韦正辉,19/12/2025,EXEED RX（T22）,XEYDD14B3RA002731,,,"LOG.zip,20250526-105242.mp4,carota.zip,LOG_XEYDD14B3RA002731_17_04_2025.tar,20250416_212024 (2).mp4",Vsevolod Tsoi,,,,,,246 +TR548,Mail,17/04/2025,,Traffic Payment,"VK apps and Navi do not operate after payment for superpackage on April, 14","0603：等待日志中 +0529：无更新 +0513:等待用户进站，取IHU日志 +0429:请属地提供IHU日志供排查 +0425: VK 应用程序和导航仪仍然无法工作 - 请参见附图_2 以及视频_1、视频_2。@袁清 +0424:续费问题建议在问题排查群确认最终解决方案 +0421：等待属地反馈问题进度 +0418：最新的测试方法，让用户锁车、车辆休眠后再上电，就有网了。可供参考，如用户紧急，可用此方法暂时解决，最终解决方案等待商讨 +0418：TSP已见该车TBOX登录注销正常，MNO续费04-14 17:28:59发起，但15日未见流量变动","03/06: no feedback => temporary close. +29/05: user is asked if problem is still valid. Wait for feedback. +13/05：Wait for the user to log in and retrieve IHU logs +29/04: provide IHU logs for check reason. +25/04: VK apps and Navi still do not work - see Picture_2 attached as well as VIDEO_1, VIDEO_2. +24/04:Renewal issues are recommended to confirm the final solution in the Troubleshooting Group. +23/04: customer is asked again to provide a feedback if VK video and Navi still do not work. +21/04: Awaiting local OM feedback on the progress of the problem. +18/04：The latest test method, let the user lock the car, vehicle hibernation and then power on, there is network. For reference, if the user is in an emergency, this method can be used to solve the problem temporarily, the final solution is waiting for discussion! +18/04: TSP has seen the car's TBOX login logged off as normal, MNO renewal initiated at 04-14 17:28:59 but no traffic changes seen on the 15th. +17/04: please provide a procedure to be applied so that the customer can immediately have the access to the network.",Low,temporary close,生态/ecologically,袁清,03/06/2025,EXEED VX FL（M36T）,LVTDD24B4PD575331,,,"VIDEO_2.mp4,VIDEO_1.mp4,Picture_2.jpg,Picture_1.JPG",Vsevolod Tsoi,,,,,,47 +TR549,Telegram bot,18/04/2025,,VK ,"Vk apps doesnt work, NAVI is ok. +Sim Activate +No abnormal data in PKI +Check Attachments","0422:生态是后台配置原因 已修改，建议用户重启车机后重新尝试即可@Kostya +0418：属地反馈VK不可用，但是导航正常，PKI未出现异常，至问题提出时，TSP可见车辆状态在线，查询有18日APN1，APN2流量变动。转生态排查。@颜廷晓","22/04:Solved - possitive feedback +22/04:Eco is the reason for the background configuration has been modified, we recommend that the user restart the car machine and try again can be.@Kostya +18/04：The local feedback shows that VK is unavailable, but the navigation is normal and there are no abnormalities in PKI. By the time the problem was raised, TSP could see that the vehicle status was online, and there were changes in APN1 and APN2 traffic on the 18th. Ecological investigation.@颜廷晓",Low,close,local O&M,Kostya,22/04/2025,CHERY TIGGO 9 (T28)）,LVTDD24B3RG092186,,,"image.png,image.png,file_1757.mp4,file_1756.jpg",Kostya,,,,,,4 +TR550,Telegram bot,21/04/2025,,Remote control ,APN1 Issue on T28,"0519：等待用户反馈后关闭 +0513:已见用户5月12日成功远控操作，可联系用户后关闭 +0427：等待用户进站 +0425：等待用户进站 +0424:平台见19日至23日远控失败，19日Tbox确认指令但未上报执行结果，35秒后超时。23日Tbox不在线，唤醒后无响应。TSP多次尝试抓取日志未果，建议用户进站取日志。 +0421:问题提交时，已见MNO21日流量走动，且TSP车辆在线，请提供远控操作时间","0519: Closed pending user feedback +15/05: Waiitng for response from customer +13/05:The user successfully remotely operated on May 12th and can be contacted to close it +27/04：waiting customer go to dealer +25/04：waiting customer go to dealer +24/04：The platform experienced remote control failures from the 19th to the 23rd. On the 19th, Tbox confirmed the command but did not report the execution result. After 35 seconds, it timed out. On the 23rd, Tbox was offline and there was no response after waking up. TSP has attempted to capture logs multiple times but has not been successful. It is recommended that users log in to retrieve logs. +24/04: Asked customer. Waiting for feedback +21/04: When submitting the issue, it was observed that MNO21 was experiencing daily traffic flow and TSP vehicles were online. Please provide the remote control operation time.@Kostya",Low,temporary close,local O&M,Kostya,20/05/2025,CHERY TIGGO 9 (T28)）,LVTDD24B9RG128401,,TGR0001236,image.png,Kostya,,,,,,29 +TR552,Mail,21/04/2025,,Remote control ,Vehicle data is not reflected in the app. Reporting data is allowed in TSP.,"0527： +问题暂时关闭 +0520： +失败原因： +尝试次数过多，请将车辆点火后再尝试启动 +0515:建议暂时关闭，如用户发现仍有问题，再重启该问题 +0514:平台已见用户11日,13日，远控成功记录，建议关闭此问题 +0513:等待OJ提供车控日志 +0506:等待OJ提供车控日志 +0429:等待OJ提供车控日志 +0427:等待OJ提供车控日志 +0425:等待OJ提供车控日志 +0424:等待OJ提供车控日志 +0421：车辆数据在APP中不显示，TSP中允许车辆数据上报开关已打开.TSP见车辆在平台中在线，TBOX登录注销及流量正常,查询低频数据显示未空，高频数据显示正常，转OJ查询车控日志","0520: Transferring to TSPcheck +Reason for failure: +Too many attempts, please turn the vehicle on and try to start it again19/05: customer's feedback - issue is still valid. it's well seen in TSP that commands are not always executed successfully - see picture attached. +15/05：Suggest temporarily shutting it down. If the user finds that there are still issues, restart the problem +14/05:The TSP has seen successful remote control records from users on the 11th and 13th. It is recommended to close this issue.@Vsevolod Tsoi +13/05：turn OJ query vehicle control logs. +06/05：turn OJ query vehicle control logs. +29/04：turn OJ query vehicle control logs. +27/04：turn OJ query vehicle control logs. +25/04：turn OJ query vehicle control logs. +24/04：turn OJ query vehicle control logs. +21/04：Vehicle data is not displayed in APP, the switch to allow vehicle data reporting in TSP has been turned on.TSP see vehicle online in the platform, TBOX login and logout and traffic is normal, query low-frequency data display is not empty, high-frequency data display is normal, turn OJ query vehicle control logs.@Vadim",Low,temporary close,O&J-APP,Vadim,27/05/2025,JAECOO J7（T1EJ）,LVVDD21B2RC068366,,,"Commands_execution_status.JPG,Reporting_data.JPG",Vsevolod Tsoi,,,,,,36 +TR553,Telegram bot,21/04/2025,,Problem with auth in member center,"Widespread issue: Customers can't get the QR or SMS for auth +PKI is OK +Time is sync +Ihu rebooted","0423：用户反馈已解决，关闭问题。 +0422:用户反馈绑车激活产生的问题，TSP有用户的绑定信息。前两辆车低高频数据不显示，第三辆车数据为补发数据，其余两辆车数据正常，转APP排查，是否有请求二维码的记录 有无报错记录，请求二维码的时间和激活时间是否相差较多。@文占朝 +0421:属地反馈是普遍问题：客户无法获得QR或SMS验证，PKI是正常的，时间是同步设置，平台见Ihu重新启动记录。","23/04: Solved - customer feedback +22/04:User feedback on issues arising from activation of vehicle binding, TSP has user binding information. The low and high frequency data of the first two cars are not displayed, the data of the third car is for reissue, and the data of the other two cars is normal. Transfer to the APP to check whether there are any records of requesting QR codes or error records, and whether there is a significant difference between the time of requesting QR codes and the activation time. +21/04:Genus feedback is a common problem: customers cannot get QR or SMS verification, PKI is normal, time is synchronised setting, platform see Ihu restart record.",Medium,close,车控APP(Car control),文占朝,24/04/2025,All projects,"LVTDD24B3RG031355 T22 +XEYDD14B3RA004589 T22 +XEYDD14B3RA008977 T22 +LVTDD24B2RG089585 T28 +LVTDD24B0RD083964 M36T +LVTDD24BXRG129444 T28",,,,Kostya,,,,,,3 +TR554,Telegram bot,22/04/2025,,Remote control ,"Vehicle data in the app is not conform to the real ones = not up to date. TSP: last Tbox log in on 2025-04-22 18:50:04; last high frequency data 2025-04-23 15:54:11. MNO: last apn1 on April, 10; apn2 is available and active.","0513:已见用户5月12日成功远控操作，可联系用户后关闭 +0429：等待属地反馈问题进展 +0427:等待属地反馈问题进展 +0425:23日远控指令下发后，tbox回复收到了，但是后续没有上报执行结果，35s超时,建议用户在信号较好的地方重启车辆并尝试远控,如仍然无法远控成功，建议抓取TBOX日志。 +0424：MNO反馈网络正常，会后确认远控详细信息 +0423:平台已查询到04-23 00:16:02远控记录失败，未提示失败原因，低频数据回传正常，未见高频数据传，建议转MNO排查网络","13/05:The user successfully remotely operated on May 12th and can be contacted to close it +29/04: Waiting for feedback from the local authorities on the progress of the issue +27/04: Waiting for feedback from the local authorities on the progress of the issue +25/04：On the 23rd remote control command, TBOX received the command but did not report the execution result, resulting in a timeout of 35 seconds. It is recommended that the user restart the vehicle in a location with good signal and try remote control. If remote control still cannot be successful, it is recommended to capture TBOX logs. +24/04:MNO reported that the network is normal, and confirmed the detailed information of remote control after the meeting. +23/04: command name - close the windows on April, 23 at 17:01 Moscow time. In addition, wrong vehicle data is displayed in the app - windows are shown as opened and the engine as started but in fact the vehicle is stopped and locked as well as windows closed. +23/04:The platform has queried 04-23 00:16:02 remote control record failure, no indication of the reason for the failure, low frequency data back to normal, did not see the high frequency data transmission, it is recommended to turn the MNO to troubleshoot the network.@林兆国",Low,temporary close,MNO,林兆国,15/05/2025,CHERY TIGGO 9 (T28)）,LVTDD24B9RG128401,,,Picture_1.jpg,Vsevolod Tsoi,,,,,,23 +TR556,Mail,24/04/2025,,Remote control ,"Engine is shown as started in the app all the time but in fact the car is locked and the engine is stopped. Last tbox log in on 2025-04-24 17:22:25, last high frequency data on 2025-04-24 17:23:07. MNO: apn1&2 are available and active.","0506:建议用户再试一试 +0427：远控详细记录如下，建议用户在信号好的地方重新尝试远控功能，并遵守远控规范 +一条tbox不在线，唤醒短信成功下发后，tbox回复执行失败，失败原因：车内有钥匙 +一条tbox回复执行失败，失败原因：车辆已上电且不在远程启动状态 +四条tbox不在线，唤醒短信成功下发后，tbox没响应，35s超时 +0424:属地反馈已TBOX日志，平台端见用户车控记录23，24两日多条记录失败，等待确认是否为超时问题。","0427: The detailed record of remote control is as follows. It is recommended that users try the remote control function again in areas with good signal and follow the remote control specifications.@Vsevolod Tsoi +A TBOX is not online. After successfully sending a wake-up message, TBOX replied that the execution failed due to the presence of a key in the car +A tbox reply execution failed, reason for failure: the vehicle has been powered on and is not in remote start mode +Four tbox messages are not online. After successfully sending the wake-up message, tbox did not respond and timed out for 35 seconds. +24/04: tbox log attached.",Low,close,local O&M,Vsevolod Tsoi,13/05/2025,CHERY TIGGO 9 (T28)）,LVTDD24B8RG120435,,,LOG_LVTDD24B8RG120435_24_04_2025.tar,Vsevolod Tsoi,,,,,,19 +TR557,Mail,28/04/2025,,Application,Icon Account doesn't exist ->see screenshot,"0512：导致该问题的原因大概率是：App后台与TSP平台用户数据未同步，请属地核实VIN：LVTDD24B5RG032670，手机号：+79032587609的对应关系是否正确 +0428：TSP显示该车已绑定，转APP确认APP账户信息。@文占朝","28/04:TSP shows that the car is bound, turn to APP to confirm APP account information",Low,temporary close,车控APP(Car control),文占朝,29/04/2025,EXEED RX（T22）,LVTDD24B5RG032670,,,"иконка 2 (002).jpg,иконка 1.jpg",Evgeniy,,,,,,1 +TR558,Mail,28/04/2025,,Navi,"The navigator from Yandex.Navi constantly loses satellites. If he writes 0 in red, he won't see them anymore. Restarting the application and turning on and off the media head does not help. Only resetting the settings to factory settings helps, and then only for a short time. Is there anything we can do about it?","0428：希望属地提供恢复出厂设置和问题发生地点是否在同一位置，如是，请提供地点坐标供排查 +0428：平台见TBOX登录登出记录正常，IHU登录记录正常，转生态排查，同时建议属地抓取IHU 日志","13/05: it works now, solved +28/04：Hope to know if the location is in the same place as the factory settings, and if so, please provide the coordinates of the location for troubleshooting.@Evgeniy +28/04:TSP see TBOX login and logout record is normal, IHU login record is normal, transfer cockpit investigation, at the same time recommended that the local capture IHU logs.@Evgeniy",Low,close,生态/ecologically,袁清,13/05/2025,JAECOO J7（T1EJ）,LVVDD21B7RC053720,,,,Evgeniy,,,,,,15 +TR559,Mail,28/04/2025,,HU troubles,The widget weather doesn't work ,0428：属地反馈天气小部件不起作用，查询TBOX及IHU登录记录正常，流量绑定正常，建议用户使用手机热点连接车机，观察小部件是否恢复，如不恢复，尝试抓取IHU日志,"13/05:it's ok now- closed +28/04:Local feedback weather widget does not work, query TBOX and IHU login record is normal, traffic binding is normal, we suggest users to use mobile phone hotspot to connect to the car, observe whether the widget is restored, if not, try to capture the IHU logs.",Low,close,local O&M,Evgeniy,13/05/2025,EXEED RX（T22）,LVTDD24B8RG019153 ,,,image.png,Evgeniy,,,,,,15 +TR564,Mail,12/05/2025,,Application,It is impossible to takWe tested it by ourself) ,"0710: 暂不关闭，等待客户验证 +0708： TSP后台查询7月份远控正常，建议关闭 +0630：等待客户验证 +0618:等待属地跟客户确认问题是否已解决 +0610: +建议关闭次问题，若有其他问题再提交新票 +0605:后台记录查询手机号（+79641058000 ）与VIN（LVTDD24B7RG116201）到关联关系正确，最近一周远控正常，请咨询客户问题是否解决，若已解决请关票，若未解决，请提供报错截图与具体时间点，以便问题查询。 + +0603： +1.等待App给出相关分析结论 +0530： +1.无更新 +0520:无更新 +0519：仍需提供相关绑定车辆信息截图 +0514： +1. 麻烦用户提供一下绑车界面截图 +0513： +1. 系统查询到 +79641058000关联VIN（LVTDD24B7RG116201 ），TSP查看日志0512，App与TSP有远控交互，请属地查看当前远控是否正常 +2. A00361：错误表示用户不存在 + 麻烦属地确认，用户 + VIN码的对应关系是否正确 +0512：属地反馈没有远控页面，每次都收到A00361错误，转APP排查 +0512：属地反馈无法使用远控，属地一线已尝试，但均无法使用。请提供VIN号供排查，目前平台检查车控权限配置正常","0715：waiting for customer feedback +0708：in July remote control is normal on TSP, suggested to close the ticket +0618: Please help consult the user whether the problem is solved. If it has not been resolved, please provide a screenshot of the error and the specific time point for problem inquiry. +10/06: To understand correctly problem, please try to create account in this app and then share rights to another person. And you will understand well what I mean. +0605:The backend records that the correlation between the phone number（+79641058000 ） and VIN（LVTDD24B7RG116201） is correct. Remote control has been normal for the past week. Please consult with the customer to see if the issue has been resolved. If it has been resolved, please close the issue. If it has not been resolved, please provide a screenshot of the error and the specific time point for problem inquiry. +20/05: Screenshots was added +0519: Screenshots of relevant bound vehicle information still required +14/05： +1. Could the user please provide a screenshot of the binding interface +13/05： +1. The APP feedback that+79641058000 is associated with VIN (LVTDD24B7RG116201). TSP viewed log 0512, and there is remote control interaction between the app and TSP. Please check if the current remote control is normal locally +2. A00361: Error indicates that the user does not exist +Please confirm with the local authorities whether the correspondence between the user and VIN code is correct.@Evgeniy +12/05：Feedback from the local OM is that they are unable to use the remote control, the territories have tried on the first line, but none of them are able to use it.",Low,close,local O&M,Evgeniy,15/07/2025,CHERY TIGGO 9 (T28)）,ALL VINS,,+79641058000 Victoria ,"img_v3_02mv_6338ffcd-7981-4424-a137-2350fd97e7dg.jpg,img_v3_02mf_11154d89-93c2-4b4c-acd6-a0e65a973dhu.jpg,img_v3_02mf_7769feb6-bf46-4cb8-9034-1f8ad8c3behu.jpg,20250513-141013.jpeg,20250513-141006.jpeg,20250513-140947.jpeg,20250513-140958.jpeg,IMG_6043.MP4,image.png,image.png",Evgeniy,,,,,,64 +TR565,Mail,12/05/2025,,Traffic Payment,There is impossible to buy package,"6/11: IOS端、安卓端已全部上架 +6月5日： +1.IOS端已通过审核，安卓端4日提审中，等待审核通过各端同时上架。 +6月3日： +1.永久措施： +1.1手机 App 端 续费链接更换为新域名，雄狮App开发已完成，属地验证测试正常，IOS端已提审，安卓待信息公司协调属地提供开发者账号进行提审。—— +1.2 座舱端 续费链接域名替换已完成 SOTA 升级会员中心方式推进，05/27 已对 M36T 车型推送升级。—— +2.临时方案：APP投放应用市场前，如再出现用户异常，根据VIN码等信息辛巴提供新域名链接给到属地运维，提供给用户解决续费问题； +5月20日 +23:00 +根因确认：通过以下测试锁定问题为 DNS解析异常： +用户手机浏览器直接使用IP访问续费页面——正常； +使用原辛巴域名（GoDaddy解析）访问——失败； +使用新TSP子域名（OQ本地DNS解析）访问——正常。 +根因分析： +原辛巴域名依赖美国GoDaddy的云解析服务（欧美节点为主），导致OQ地区用户DNS解析延迟或劫持风险； +新TSP子域名使用OQ本地DNS服务商，覆盖度和时延更优，验证有效。 +最终解决方案： +技术调整： +手机APP修改续费链接域名，确认提审时间（@文占朝）； +座舱同步修改续费链接域名，纳入SOTA升级计划（@赵亚立）。 +应急措施： +若应用市场更新前再出现异常，辛巴提供新域名临时解决（@石子健 @喻起航）。 +运维优化： +维护域名资产清单，提前更新HTTPS证书（@聂飞 @石子健）。 +5月16日 +23:30 +关键发现： +用户通过浏览器直接访问IP正常，但原域名访问失败，新TSP域名正常，初步怀疑DNS解析问题。 +临时方案：提供IP地址供用户临时续费（有效期一周）。 +后续计划： +运维侧监控域名解析稳定性，联系DNS服务商排查劫持可能； +协调经销商测试续费链接有效性 +5月15日 +16:30 +潜在根因： +客户端兼容性（用户设备型号未知）； +辛巴服务端接口异常； +市场版v1.2.5未全量测试。 +紧急措施： + 生成测试包供用户安装，建立异常追踪机制； + 抓取续费链路日志，协调用户安装测试包收集日志。 + 后续计划：若确认接口问题，启动服务降级方案。 +20:00 +新增根因：怀疑OQ地区运营商限制域名访问或DNS解析问题。 +技术行动： +辛巴团队对域名进行多地区拨测； +加速APP侧域名渲染优化（长期目标）。 +用户侧措施：新问题发生时记录用户运营商及位置，建议使用测试域名。 +。 +5月12日 +问题首次出现：用户点击续费入口时出现白屏，伴随辛巴服务H5页面网络超时提示，直接影响付费流程。 +5月14日 +16:30 +初步定位：怀疑M36T续费接口异常（辛巴提供的续费地址可能存在问题）。 +卡点：APP技术团队无法获取日志，属地运维无法联系客户提供测试账号。 +后续计划：获取日志后研发分析根因，运维跟踪问题是否批量。 +17:30 +更新卡点：属地运维因外部因素无法联系客户提供账号，测试受阻。 +新增计划：待属地提供测试账号后转交研发测试 +18:30 +进展：属地提供测试账号并转交技术团队，等待测试结果。 +卡点：仍无法抓取生产环境日志。 +21:30 +排查方向调整： +属地运维及技术团队使用测试账号未复现白屏，怀疑用户设备兼容性问题。 +技术团队未获取市场版v1.2.5安装包，需进一步验证。 +应对措施：建议用户尝试亲属设备操作，并计划测试市场最新版本。 +0514：在与MNO，APP，排查续费接口问题","10/06 : waiting +June 5th: +1.IOS end has passed the audit, android end of the 4th mention in the trial, waiting for the audit through the various ends at the same time on the shelves. +June 3rd: +1.permanent measures: +1.1 The renewal link of the cell phone App end is replaced with a new domain name, the development of Lion App has been completed, the territorial verification test is normal, the IOS end has been submitted for review, Android & Huawei end to be coordinated by the information company to provide a developer account in the territory for the submission of the review.-- +1.2 Cockpit side Renewal link domain name replacement has been completed SOTA upgrade member center way to promote, 05/27 has been pushed to upgrade the M36T model.-- +2. Temporary Program: Before the APP is put into the application market, if there is another user abnormality, according to the VIN code and other information, Simba will provide a new domain link to the local operation and maintenance, and provide it to the user to solve the renewal problem; +14/05：Troubleshooting renewal interface issues with MNO, APP",High ,close,用户EXEED-APP(User),文占朝,16/06/2025,All projects,"LVTDD24B1RG033279 +LVTDD24B0RD065593 +LVTDD24B7PD613912 +LVTDD24B8RD031448 +LVTDD24B1PD621200 IPhone +LVTDD24B9PD587328 +LVTDD24B0RD031461 +LVTDD24B2PD621254 +LVVDB21B5RC077312 +LVTDD24B7PD579096 +LVTDD24B9PD385928",,,"img_v3_02m8_cffa2396-885f-4e58-85e4-9d81bcee9bhu.jpg,6956af2d-83be-45f3-a757-74324fb31e11.jpeg,1747199440525_o_IMG_7381.MOV,1fa7793d-1218-4d90-90bc-1f7c1579a74c.jpeg",Evgeniy Ermishin,,,,,,35 +TR566,Mail,13/05/2025,,VK ,"VK video&music do not work after OTA upgrade T22-TBOX-0306 - see attached photo of issue. An error message ""Activation of license is not successful [Err:0]. 2 VINs are affected. +OTA 升级 T22-TBOX-0306 后，VK 视频和音乐无法播放 - 请参阅所附的问题照片。 错误信息 ""激活许可证不成功 [Err:0]。 2 个 VIN 受影响。","0731：已关闭该问题，后续未解决的将会重新新增一例 +0728: LVTDD24B4RG009803 是否有任何更新？LVTDD24BXRG031370：再次要求客户提供反馈意见。如果在周四的会议之前没有反馈，则将关闭。 +0722：LVTDD24B4RG009803和LVTDD24B4RG033857已恢复正常，等待LVTDD24B4RG014239和 LVTDD24BXRG031370 反馈 +0716：麻烦让另外三辆车的车主也重启下IHU看VK是否恢复 +0715: LVTDD24B4RG033857： 重启 IHU 后，VK 音乐应用程序已恢复，该车辆问题已解决 +0715：LVTDD24B4RG033857HU SN已修改为完整编码，其他app恢复正常，但是VK音乐仍然无法使用 +0624: 新日志解压后损坏无法分析，等待其他车辆的日志 +0623：转国内生态进行分析 +0610：仍然等待最新日志了 +0603： +等待合规流程完毕，日志发送 +0530： +1.转国内生态进行分析 +0528： +1.日志已抓取转国内分析 +0520：无更新 +0519：建议用户抓取DMC日志","31/07: The issue has been closed and a new case will be added for subsequent unresolved cases +31/07: +LVTDD24B4RG009803 still open - wait for feedback from 2nd line. +LVTDD24BXRG031370 - no feedback => issue closed. +LVTDD24B4RG033857 - feedback that VK was restored => solved out. +28/07: +is there any updates on LVTDD24B4RG009803? LVTDD24BXRG031370: customer is requested again to provide with a feedback. If no reply by Thursday's meeting, it will be closed. +LVTDD24B4RG014239 - repeat reqest sent to user. f no by Thursday's meeting, it will be closed. +0722：waiting for LVTDD24B4RG014239 and LVTDD24BXRG031370 Feedback +16/07: LVTDD24B4RG009803 - did not bring any result after rebooting; LVTDD24B4RG014239 and LVTDD24BXRG031370 are requested. +0716：Please help invite thecustomers of the other three cars to reboot the IHU as well to see if VK is restored @Vsevolod Tsoi +15/07: LVTDD24B4RG033857: VK music app is restored after asking to reboot the IHU. +14/07: LVTDD24B4RG033857: all apps have been restored besides VK music which still doesn't work. +14/07：IHU ID has been changed back to long one P3000140031800035700000000000000. Wait for feedback wether VK app are restored. +09/07: DMC log of VIN LVTDD24B4RG033857 is attached to TR. +03/07: log not received yet. +01.07: no DMC log received so far. +23/06: as agreed in the respective chat => wait for another log since several VIN's are impacted by same issue. +0623：Transferring domestic ecology for analysis +19/06: new DMC log of LVTDD24B4RG009803 is attached. Please check it out @张如玉 +09/06: repeat request is sent to dealer. Wait for feedback. +0605： +1.need a new dmc log +0530: +1. Transferring domestic ecology for analysis +28/05: DMC log of LVTDD24B4RG009803 is attached. +19/05: request for collecting DMC log is sent. Wait for feedback. +0519: Suggest that users capture DMC logs +0515：Genus feedback after OTA, VK video and music is unavailable, see attached picture, TSP query to IHU has a login record, May traffic changes are normal, it is recommended to get the host logs first, and then turn to eco-analysis. +15/05: After receiving feedback from the local OTA, VK videos and music are not available, as shown in the attached image. TSP found login records for IHU, and traffic changes were normal in May. It is recommended to transfer to the ecosystem for investigation",Low,close,local O&M,袁清,31/07/2025,EXEED RX（T22）,"LVTDD24B4RG009803 +LVTDD24B4RG014239 +LVTDD24B4RG033857 +LVTDD24BXRG031370",,LVTDD24BXRG031370 - TGR0001492; LVTDD24B4RG033857 - TGR0001510,"DMC_SW_version.jpg,Navi_version.JPG,logs_20250709-102132_VIN_LVTDD24B4RG033857.zip,19.06. Логи RX.009803 (1).zip,LVTDD24B4RG009803.zip,Photo_3.jpg,Photo_1.jpg,Photo_2.jpg",Vsevolod Tsoi,,,,,,79 +TR567,Telegram bot,13/05/2025,,Network,"Network doesn't work. No data on MNO platform. No tbox login on TSP. +Network in the area is OK, everything works well with Wi-Fi.","0530： +用户反馈恢复正常，问题关闭 +0529： +无更新 +0520：无更新 +0519：等待用户进站进行测试同时抓取日志 +0516:建议用户进站，先尝试整车断电，上电后测试，查看是否恢复，如仍有异常使用诊断仪诊断，诊断得出的故障码，烦请记录并抓取TBOX日志供分析。 +0516：MNO与MTS运营商沟通确认了网络相关配置是正常的，需要找硬件相关的业务方进行跟进处理 +0515：转MNO分析网络问题 +0515：属地反馈网络不工作，MNO平台上无数据，无TBOX登录注销记录，车机网络在连接WIFI正常","0530: +User feedback back to normal, issue closed +0527: waiting for customer feedback and logs +0527: Waiting for users to come in for testing while capturing logs +0522: Waiting for users to come in for testing while capturing logs +0519: Waiting for users to come in for testing while capturing logs +16/05：It is recommended that users enter the station and try to cut off the power of the entire vehicle first. After turning it on, test to see if it has been restored. If there are still abnormalities, use a diagnostic tool to diagnose. If the fault code is diagnosed, please record and capture the TBOX log for analysis.@Kostya +16/05 - +No tbox Login +But have DMC login by WI-Fi +No data usage at MNO and simba for last 15 days. + +Doesn't work since 25.04 according to customer + +15/05 - opened +collecting data in progress, +Asked to start the car by button + +UPD: Car was laucnhed by ""start"" button at 7:40-8:00 UTC +5",Low,close,local O&M,Kostya,03/06/2025,CHERY TIGGO 9 (T28)）,LVTDD24BXRG094114,,TGR0001548,"img_v3_02ma_cb19d5df-74e0-45d9-916b-20cc7138echu.jpg,img_v3_02ma_a16a2591-0feb-416d-8670-768be26525hu.jpg,img_v3_02ma_4d8923af-3908-4c4b-abfd-5a83bbc32ehu.jpg,img_v3_02ma_23392bc1-70ca-4165-8581-ed71269816hu.jpg,img_v3_02ma_16ac7513-7268-4b30-a7f8-b78a5ad039hu.jpg,img_v3_02ma_63422ea3-b2b1-4c4a-a4b4-ec3981e508hu.jpg",Kostya,,,,,,21 +TR570,Mail,19/05/2025,,Application,The customer sees wrong status in Exlantix app. Private settings are ok. TBOX login/logout is ok,"0605：问题已解决 关闭 +0603： +1.如无异常反馈 建议此问题关闭 +0530 +TSP平台的数据已经恢复正常了，但是App显示等用户反馈 +0529： +等待用户反馈问题是否解决 +0528： +1.已经操作 仍然无法使用 +0527： +1，提供前方属地运维相关操作手册@刘娇龙 +0522： +1.怀疑用户未打开车机隐私协议服务，请指导用户操作 +0520： +1.app显示数据为tbox上传，需要tbox组抓取日志进行分析 +0519: +1.转App @李维维","0522: +1. Suspect that the user has not opened the car privacy agreement service, please guide the user to operate +20/05: log was added, please check +0520: +1. app shows data as tbox upload, need tbox group to grab logs for analysis @Evgeniy +0519. +1.to App Vivian Lee",Low,close,用户EXEED-APP(User),文占朝,05/06/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ1SD099716,,,"image.png,image.png,LOG_LNNBDDEZ1SD09971620250520111225.tar,image.png,image.png,image.png",Evgeniy Ermishin,,,,,,17 +TR571,Mail,19/05/2025,,Missing EPTS,The customer can't add his car to garage: he see "wrong EPTS number","0528： +预计今日可在App网站看见此台车辆，长期方案进行中 +0527： +1.已经进行问题升级，进行专题讨论 +0523: +1. 协商DMS重新推送VIN号对应的EPTS号 +2. +0522: APP开发正在调试功能，待恢复@文占朝 +0520: +1.需要明确chery App管理网站账号所有方，给属地运维开通相关权限加车","May 28: car was added, problem solved +0528: +Expect to see this vehicle on the App website today, long-term program ongoing +0527: +1. Issues have been escalated for thematic discussion +21/05: client wants to return back the car to 4S store because of this problem!!!!!",High ,close,,,28/05/2025,CHERY TIGGO 9 (T28)）,LVTDD24B4RG121842,,,20250519-115009.png,Evgeniy Ermishin,,,,,,9 +TR576,Mail,20/05/2025,,OTA,"The customer can't do OTA. LOG OTA in attachement + Car doesn't see TBOX, please confirm if dealer can change TBOX","0811：问题已由经销商解决，关闭该问题 +0805：暂无反馈;等SK学习结果反馈； +0804：明日例会询问最新进展 +0730:经销商侧无反馈 +0729:等待SK学习，验证 +0701：等待SK学习，验证 +0623：T-BOX已更换，等待反馈 +0610：等待用户进站抓日志 +0603： +等待客户进站更新 +0529： +等待更新 +0523: +1.在主机工程模式里面看一下是否可以读到tbox信息，如果不能读到，需要更换tbox，如果可以读到，帮忙取一下主机和tbox的日志在进行排查 +0520： +1.转国内ota进行分析@刘金龙 ","11/08: problem was solved by dealer +05/08：No feedback +04/08：Will ask for an update at tomorrow's regular meeting. +30/07: no feedback from the dealer +01.07: tbox login/logout not successfull - dealer didn't do SK learning after TBOX replacment. +Asked dealer to check. +16/06: tbox was changed -waiting for feedback +10/06: request for changing was sent, waiting. +0527: +1. in the dmc engineering mode to see if you can read the tbox information, if you can not read, you need to replace the tbox, if you can read, to help take the host and tbox logs in the troubleshooting @Evgeniy Ermishin",Low,close,OTA,刘金龙,11/08/2025,EXEED VX FL（M36T）,LVTDD24B0RD118471,,"The car shows the over-the-air update, but at the moment of installation (all conditions are met) the error “Failed to install” appears. +at the moment of installation (all conditions are met) the error “Failed to enter update mode” is displayed. +enter update mode” error + +DMC software version (C195) is installed on the vehicle. +For the update we gave out the Internet from a personal phone. +What we noticed: in the menu, the system is not displayed on the instrument cluster. +is not displayed in the menu system on the instrument cluster +a.T-BOX version +b.Hardware version of T-BOX. + +We tried to download files from the service company TB2023088v3. +TB2023088v3. T-BOX module software (TGW) ---- Not installed.",LVTDD24B0RD118471.zip,Evgeniy Ermishin,,,,,,83 +TR577,Telegram bot,20/05/2025,,Application,User can't activate the remote control in the mobile app. 2 error messeges come up: A00362 when scroll down to update and A07913 when trying to activate remote control - see pictures and videos attached.,"0528： +错误信息也被删除，请通知用户再次尝试绑定 +0527： +会后确认信息是否删除，通知用户再次尝试注册 +0522： +1.排查原因为用户注销后注册，T平台与APP后台数据不同步，存在脏数据导致 +0521: +1. 协调数跑、TSP解决问题 +0520： +1、 A00362 意思验证失败，A07913 表示注册品牌信息失败","29/05: problem is solved out. +0528: +The error message was also deleted, please notify the user to try binding again @Vsevolod Tsoi +20/05: background of the issue is as follow: After buying the car customer added the car in and then activated remote control according to the instruction provided. Then, he had been using the remote control for about 1 week and vehicle data stopped being updated in the app as well as executing of the commands. After that, he tried to pull the car out of the app and put it back again and he faced to the imposibility to activate remote control => an error A07913 comes up. Please refer to solution taht had been applied for TR465 and TR499 - probably it might help to find a root cause and then fix the issue.",Low,close,车控APP(Car control),文占朝,29/05/2025,CHERY TIGGO 9 (T28)）,LVTDD24B2RG105090,,TGR0001494,"Video_1.MP4,Video_2.MP4,Picture_3.jpg,Picture_1.jpg,Picture_2.jpg",Vsevolod Tsoi,,,,,,9 +TR578,Telegram bot,22/05/2025,,Navi,"Navi app doesn't reflect the maps. However, weather app works and reflects the data. Network signal level is always 3G. When sharing the internet via WFI from mobile phone, everything works well.","0603： +1，月初流量已刷新，建议属地运维联系用户是否已恢复正常 +0528： +1.请属地运维抓取主机日志后方可进行分析 +2.APN2流量用完，主机地图无法使用； +0527： +1.转生态查看@许哲霖 +0522： +已要求客户用启动和停止按钮启动发动机，等待 15-20 分钟后再试一次 => 没有任何变化，车辆没有从休眠模式中唤醒。 +0522: +1.转MNO核查@胡纯静，MNO核查套餐配置正常，这边可以先让用户重新上电再试试","05/06: customer's feedback - Navi maps started being refclecting - issue closed. +04/06: still no feedback +03/06: user is asked to provide a feedback if the issue is solved out or is still valid. +0603: +1, the beginning of the month traffic has been refreshed, it is recommended that the local operation and maintenance to contact the user whether it has returned to normal +29/05: customer is asked to provide a feedback whether the problem with maps is still valid. Wait for feedback. If so, DMC log will be requested. +0528: +1. Please local operation and maintenance to capture the DMC logs before analysis +27/05: checked out in TSP: commands had successfully been executed starting from May, 22th. Wait for customer's feedback whether the issue is still valid +22/05: customer was already asked to start the engine with Start&Stop button, wait for 15-20 mins and try again => nothing changed, vehicle did not wake up of hibernation mode. +0522. +1. Turn MNO verification Hu Chunjing, MNO verification package configuration is normal, this side can first let the user re-power and try again! +22/05: Vehicle status in TSP: no tbox log in/out since activation date April, 22th. Thus, there is no frequency data available since activation date. MNO: no traffic used since activation date, no apn1&2 available and working.",Low,close,local O&M,Vsevolod Tsoi,05/06/2025,EXEED RX（T22）,XEYDD24B3RA004813,,TGR0001381,"Simba_status.JPG,file_1863.jpg",Vsevolod Tsoi,,,,,,14 +TR579,Mail,22/05/2025,,Application,"It's impossible to share rules of remote control to another person + there is no map, when you try to find your car.","0618：地图问题已更新修复，建议关闭此问题。关于车主账号分享问题建议新建一个工单TR523跟进，需要提供用户操作问题的录屏。 +0610： +1.6/10提审 +0605： +1.地图问题已修复，测试版本前方已验证，预计610提审， +2.车主账号分享问题：需要属地运维联系用户录制问题视频，同时进行日志抓取（抓取手册@刘永斌会后提供） +0530： +1.该问题关联TR581一同分析中 +0522： +1.1. 请提供App版本信息（版本号、系统：iOS、Android）","0618:The map issue has been fixed, and it is recommended to close this issue.Regarding the owner account sharing issue it is recommended to create a new tracking TR623 to follow up, which requires a recording of the user operating the issue. +0605: +1. Problems have been fixed, the test version of the front has been verified, is expected to be 620 officially issued version +2. Owner account sharing problems: need to be local operation and maintenance contact users to record the problem video, while log capture (capture manual @刘永斌 will provide after the meeting) +30/05: Version - see screen, IOS +0528: +1. Please provide the relevant information again,@Evgeniy Ermishin +0522: +1.1. Please provide App version information (version number, system: iOS, Android)",Low,close,用户EXEED-APP(User),邓雄峰,18/06/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ7SD094682,,,"image.png,img_v3_02mh_7ab39c6d-4c11-498e-9d73-28dc846798hu.jpg",Evgeniy Ermishin,,,,,,27 +TR580,Telegram bot,22/05/2025,,Remote control ,Engine doesn't start via app remotely.,"0807：暂时关闭，等待经销商反馈后重新打开 +0804：经销商反馈：已准备好SK相关操作，但用户电话无法接通 => 仍在等待邀请用户进站。 +0728: 暂无经销商侧TBOX SK学习结果反馈 +0722: 暂无经销商侧TBOX SK学习结果反馈 +0716: 仍在等待。 +0715：等待学习SK +0626:仍然等待用户进站学习SK中 +0623: 等待进站学习SK +0610：等待属地运维反馈是否解决问题 +0605; +文档预计0606提供 +0603： +1.等待专业组提供相关学习文档 @项志伟 +0529： +需要T28的Sk学习文档 +0527： +1.会后转专业组提供SK学习文档 +0523: +1.检查TBOX登录记录正常，近几条tbox远控报错原因[{""0031"":0,""0032"":[54]}]，T-BOX认证失败，需要用户进站学写SK（SK未学习会导致发动机控制、空调开启失败）","07/08: temporarily closed. Will be re-opened whent getting a feedback. +04/08: dealer's feedback: they are ready to apply for an instruction requested but user is not reacheable by phone => still wait for invitation. +29/07: reminder is sent to dealer. +28/07: feedback on TBOX learning with SK at dealer is still pending. +22/07: feeback on TBOX learning with SK is still pending from dealer. +16/07: still pending. +14/07: pending +10/07: still pending. +03/07: still wait for feedback. +01/07: still wait for result after TBOX SK learning. +24/06: had no feedback so far +16/06: request for TBOX SK learning has been sent to dealer. Wait for customer's invitation to dealer for procedure to do. +10/06: Waiting for feedback from local O&M on whether the problem is resolved or not +03/06: +1. Waiting for the professional group to provide relevant study documents Xiang Zhiwei +29/05: please provide the instruction to follow for T28 SK learning. Based on expirience with T22, if programming DMC is also required please provide that insturction as well. +23/05. +1. Check the TBOX login record is normal, the last few tbox remote control error report reason [{""0031"":0, ""0032"":[54]}], T-BOX authentication failure, the need for users to enter the station to learn to write SK (SK has not been learned will lead to engine control, air conditioning open failure)",Low,temporary close,TBOX,项志伟,07/08/2025,CHERY TIGGO 9 (T28)）,LVTDD24B7RG092191,,TGR0001661,,Vsevolod Tsoi,,,,,,77 +TR581,Mail,26/05/2025,,Remote control ,Remote control doesn't work: vehicle data such as remaining fuel and maps are not reflected in the app.,"0630：等待客户确认 +0623：APP已上架，等待跟客户确认APP是否已升级，问题已修复 +0619:跟属地确认是否关闭 +0618：0616 APP已上架应用市场 +0610： +1.6/10提审 +0605： +1.地图问题已修复，测试版本前方已验证，预计620正式发版 +0603： +1.会后更新进展@刘娇龙 +0528： +1.排查用户异常流量使用情况 +2.核查具体原因地图KEY到期的问题 +0527： +请用户进行套餐续费 +2.转MNOcheck +0526： +1.转辛巴查看流量套餐配置","03/07: Temporary closed. +01.07: reply is still pending. +27/06: repeat request to customer has been sent. Reply is still pending. +24/06: request for app update was sent on June, 23rd. reply is pending. +0620: APP is on the app market, Please help confirm with the customer whether the APP upgrade has been completed and the problem has been solved @Vsevolod Tsoi +17/06: wait for releae a new version in the app market +0605: +1. Map issues have been fixed, the test version of the front has been verified, is expected to be released on 20th June +0603： +1.root reason :the map's key expired ,find way to slove it in processing +29/05: traffic is used up that leads to stop apn2 temporary until either when a traffic will be recharged or traffic renew happens on June, 1st. But apn1 still has to work, doesn't it ? +0527: +Request subscribers to renew their subscriptions +26/05: TSP status: last tbox log in on 2025-05-26 06:14:15, high frequency data on 2025-05-26 06:16:04. MNO status: traffic is used up so there is network available as apn2 is OFF. Apn1 is available and active.",Low,temporary close,MNO,胡纯静,03/07/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ5SD099802,,"Гасанов Андрей Айдынович, 79113001050 Samsung S25, the latest version in the store marktet","LOG_LNNBDDEZ5SD099802_26_05_2025.tar,Picture_4.JPG,Picture_3.JPG,Picture_2.JPG,Picture_1.JPG",Vsevolod Tsoi,,,,,,38 +TR582,Mail,26/05/2025,,OTA,The customer can't do OTA. After turning off the ignitian to launch OTA the customer see : "Power failure","0605: +tr547 +0528： +11.等待专业提供DMC SK 学习文档 @许哲霖 +2.已提供DMC SK学习文档，昨日属地反馈学习成功 +0526： +1.转OTA团队查看此问题，需要OTA日志进行分析","10/06: waiting +0528: +1. waiting for professional to provide DMC SK study documents +0527: +1. Please grab the OTA logs for analysis",Low,temporary close,OTA,韦正辉,17/06/2025,EXEED RX（T22）,XEYDD14B3RA011824 ,,,"LOG_XEYDD14B3RA01182420250526134954.tar,IMG_20241025_090556.jpg,IMG_20241025_090553.jpg,IMG_0402.JPG",Evgeniy Ermishin,,,,,,22 +TR584,Mail,27/05/2025,,doesn't exist on TSP,The car is not available on TSP ,"0530： +1.请属地运维通知客户再次尝试 +0529: +1.该车辆数据已经手动添加至TSP，同步属地运维 +0528： +1.Mes核查存在数据，TSP核查中@陶军 +0527 +转mes排查","solved +0530: +1. Please ask the local O&M to notify the customer to try again +0529. +1. The vehicle data has been manually added to the TSP and synchronized with the local O&M. +0528: +1.Mes verify the existence of data, TSP verification in Taojun +0527. +Turn mes to troubleshooting",Low,close,TSP,喻起航,02/06/2025,CHERY TIGGO 9 (T28)）,LVTDD24B4RG116026,,,"20250527-153009.png,image.png",Evgeniy Ermishin,,,,,,6 +TR585,Telegram bot,27/05/2025,,Problem with auth in member center,The customer don't see qr code.,"1023：客户的反馈是二维码终于出现了。有人问客户在做什么，得到的答复是，他只是不时检查/尝试点击 ""扫描二维码进入 ""会员中心。 +1020：在使用 QR 码进入会员中心之前，需要填写新日志。 +1020：附上另一个名为 DMC_log_2 的 DMC 日志供调查。 +1017: LNNBDDEZ2SD096906 登录会员中心仍然未显示，请@高喜风发起合规申请，之后转生态分析 @袁清 +0908：建议联系用户可以尝试恢复DMC出厂设置，查看是否有二维码显示 +0826：反馈用户未升级，等待用户进站升级 +0819:请QS方更新进展 +0815: +LNNBDDEZ8SD163170 - fixed +LNNBDDEZ4SD094302 - fixed +0811: 请求已被再次发送，等待经销商或用户反馈是否升级 +0804:TSP暂未见车机登录记录，等待确认是否未进站升级 +0731：等待客户进站升级后验证 +0729: 暂无升级进展 +0715：等待客户进站升级后验证 +0710: 升级通知已经下发给经销商，建议让经销商邀请客户进站升级。（LNNBDDEZ8SD163170没有在这次升级清单里面，需等待下次） +0701: 问题在最新版本已修复，等待售后技术升级通知单发布后，邀请客户进站刷新版本（更新后版本01.00.21); +0701：客户多次重启车机后未恢复，二维码仍未显示，TSP无车机登录记录，PKI平台有登录记录, 等待国内分析 +0624：已完成试装切换，等待OTA，预计十月份 +0618: 重启车辆会恢复，等待属地验证（同TR597) +0617: + 短期方案：同时长按方向盘两侧的球形按钮重启车机，然后再次登录两个APP +长期方案: 8月份预计OTA升级 +0616： +临时措施: 车子放一晚第二天上电再看下是否OK，if not，重启车机，有概率能修复的 +长期措施: 软件升级，当前产线切换中，预计6/21完成，OTA时间未确定 +0610： +1.属地运维日志已提供，等待国内合规审批流转至工程师 +0529： +等待DMC日志中","23/10: Customer's feedback was that QR had finally come up. One the request what actions customer was doing, the reply was that he was just checking/trying from time to time to enter into member center clicking on ""Scan QR code for entering"". +20/10: new log is requested performing entering into member center with QR code before. +20/10: another DMC log called DMC_log_2 was attached for investigation. +17/10: TR is re-opened for LNNBDDEZ2SD096906 since customer still has issue with no QR code for entering into member center. DMC log attached. +08/09: It is recommended to contact the user who can try to restore DMC factory settings to see if there is a QR code displayed +26/08：Feedback that the user has not been upgraded, waiting for the user to come in for upgrading +19/08: pls QS side update the progress +15/08: +LNNBDDEZ8SD163170 - fixed +LNNBDDEZ4SD094302 - fixed +11/08: request has been sent one more time +04/08:TSP has not seen the car machine login record for the time being, waiting to confirm whether it has not been upgraded in the station +31/07: waitting customer go to dealer to upgrade DMC @Evgeniy Ermishin +29/07： no progress +15/07：waitting customer go to dealer to upgrade DMC @Evgeniy Ermishin +10/07：The upgrade notice has been sent to the dealer. It is suggested that the dealer invite customers to dealer for the upgrade. （LNNBDDEZ8SD163170 is not on this upgrade list and will have to wait for the next one.）@Vsevolod Tsoi +01/07: The issue has been fixed in the latest version. After the post-sales technical upgrade notification is released, will invite customers to the station to refresh the version. The new verison will be 01.00.21 @Evgeniy Ermishin +01/07: After the customer restarted the car system several times, it did not recover and the QR code was still not displayed. There are no HU login records on the TSP, but there are login records on the PKI platform. Awaiting domestic analysis +24/06：The trial installation switch has been completed and is waiting for OTA （Expected October） +17/06: +Restart the ICC through pushing the 2 spherical buttons on both side of steering wheel for 5s. then log in to the 2 apps again +software expected to be upgrade about August +16/06: +Temporary measures: the car put a night on the next day on the power to see if it is OK, if not, restart the car, there is a probability that can be repaired! +Long-term measures: software upgrade, the current production line switching, is expected to be completed on 6/21, OTA time has not been determined. @Evgeniy Ermishin +10/06: we are waiting for feedback from 2nd line of support +05/06: dmc in attachement +29/05：need get the DMC log +29/05: The customer can't see qr code in the car, he has already tried to use WIFI hotspot - the same result. IHU login/logout is not ok, TBOX login/logout is ok",Low,close,生态/ecologically,袁清,23/10/2025,EXLANTIX ET (E0Y-REEV),"LNNBDDEZ2SD096906 +LNNBDDEZ8SD163170 +LNNBDDEZ4SD094302",,TGR0001720,"DMC_log_2.zip,DMC_log.zip,Log.zip,image.png,img_v3_02mm_5c879fba-c2f5-41a4-83aa-cf71277185hu.png",Vsevolod Tsoi,,,,,,149 +TR587,Mail,29/05/2025,,HU,"There is no data about wheather displayed on the main screen in IHU. However, when opening weather app itself, weather data is well shown - see pictures attached. After reboot of IHU weather data starts working on main screen but when turning the engine off and then on weather data doesn't reflect again. +IHU 的主屏幕上没有显示天气数据。 不过，当打开天气应用程序本身时，天气数据就会很好地显示出来--见附图。 重启 IHU 后，天气数据开始在主屏幕上显示，但关闭发动机后再打开时，天气数据就不再显示了。","0807：暂时关闭，等待抓取到DMC日志后重新开启 +0804: 暂无DMC日志反馈 +0731: 至今没有日志反馈。 +0728: 至今没有日志反馈。 +0722: 至今没有日志反馈。 +0716：日志仍未获取到。 +0714: 没有更新。 +0710: 暂无更新 +0703：等待日志 +0701: 状态不变。 +0623：等待日志中 +0610：等待日志中 +0603： +等待日志 +0529： +1.请提供主机日志","07/08: temporarily closed. Will be re-opened upon getting DMC log. +04/08: DMC logs still pending. +31/07: no logs received from dealer so far. +28/07: still pending. +22/07: no feedback so far. +16/07: log still pending. +14/07: no updates. +10/07: pending. +03/07: wait for data. +01.07: same status. +24/06: DMC log is still pending. +17/06: still wait for data +10/06: not received so far +09/06: request for collecting DMC log has been sent. Wait for data. +05/06: request not sent yet +03/06: Request for DMC log is in process. +0529: +1. Please provide DMC logs",Low,temporary close,DMC,张少龙,07/08/2025,EXEED VX FL（M36T）,LVTDD24B8PD630668,,,"Picture_2.JPG,Picture_1.JPG",Vsevolod Tsoi,,,,,,70 +TR589,Mail,30/05/2025,,Remote control ,"Remote control doesn't work. It works only when customer shares internet via hotspot from smartphone. Car is in deep sleep but on our request the customer was already starting his car several times with Start&Stop button and it still did not wake up. +远程控制不起作用。 当客户通过智能手机的热点共享网络时，它就会工作。 汽车处于深度休眠状态，但应客户要求，已用启动和停止按钮启动汽车数次，但仍未唤醒。","0730：所提供日志不涵盖描述远控记录，且日志显示无法收到唤醒短信，建议换个网络环境重新尝试 +0729:转国内分析TBOX分析。@刘海丰 +0728: TBOX 日志已从 TSP 上传 - 见附件。经销商仍在等待 DMC 日志。 +0722: 仍在等待。 +0708: 仍然无T-BOX登录记录，7月车机登录均失败. 等待T-BOX和DMC日志 +0626: 等DMC日志 +0610： +无法抓取到日志进行分析，建议暂时关闭问题 +0605：等待抓日志中 +0530： +1.邀请用户进站抓取tbox及DMC日志","30/07:The logs provided do not cover the description of the remote control records, and the logs show that you can not receive the wake-up SMS, it is recommended to change the network environment and try again! Screenshots of uploaded logs.@Vsevolod Tsoi +29/07：Turn TBOX for analysis +28/07: TBOX log has been uploaded from TSP - see attached. DMC log is still pending from dealer. +22/07: still waiting. +16/07: not received so far. +14/07: no logs received yet. +10/07: logs still pending. +08/07：Still no T-BOX logs, HU logs fail. Waiting for T-BOX and DMC logs. +03/07: wait for invitation of customer to dealer for DMC log +01/07: still wait for data. +24/06: invitation to dealership for collecting DMC log is still pending. +17/06: still wait for data. +10/06: +Unable to capture logs for analysis, recommend closing the issue temporarily +09/06: no logs received so far. +05/06: collecting DMC&Tbox logs are in process +03/06: request for TBOX&DMC log has been sent on May, 30th. Wait for invinting customer to dealer to get the logs. +30/05: +1.Invite users in to grab tbox and DMC logs +30/05: no traffic is using. Last apn1&2 available and active were on April, 22th.",Low,close,local O&M,Vsevolod Tsoi,31/07/2025,JAECOO J7（T1EJ）,LVVDD21B2RC052684,,,"img_v3_02om_6dc2aa08-11ae-4eae-bcfc-4ce388b5a26g.jpg,LOG_LVVDD21B2RC052684_28_07_2025.tar,MNO_apn1_2.JPG,Simba_status.JPG,Picture_1.JPG",Vsevolod Tsoi,,,,,,62 +TR590,Telegram bot,30/05/2025,,HU,After launching route in NAVI HUD starts twinkle (see video),"0603: +1.该问题最新版软件已修复，等待OTA即可（优先试装中） +0530: +1.转DMC分析","0603. +1. The problem has been fixed by the latest version of the software, wait for the OTA.",Low,close,OTA,胡广,05/06/2025,CHERY TIGGO 9 (T28)）,LVTDD24B1RG089593,,,file_2375.MP4,Evgeniy Ermishin,,,,,,6 +TR591,Mail,30/05/2025,,VK ,"VK doesn't work - an error message comes up whent starting ""Activation of license is not successful"". QR code doesn't come up when trying to log in member center. QR code also doesn't come up when sharing the internet via hot spot +VK 不工作 - 启动时出现错误信息 ""许可证激活不成功""。 尝试登录会员中心时没有显示二维码。 通过热点共享互联网时，二维码也不会出现","0807：暂时关闭，等待抓取到DMC日志后重新开启 +0804:暂无日志 +0731: DMC 日志仍未获取到 +0728: DMC 日志仍未完成 +0722: 仍在等待。 +0716: 仍在等待 +0714: 暂无日志上传 +0710：至今没有日志上传。 +0703：仍在等待数据。 +0701：仍在等待 DMC 日志。 +0626： +等待用户进站抓取日志中 +0619: 等待日志 +0610：等待最新日志中 +0602：问题已转中国生态工程师 +0602: TBOX 日志和 DMC 日志附后。 +0602: 要求提供 DMC 日志和 TBOX 日志。 等待反馈。","07/08: closed temporarily. Will be re-opened upon getting DMC log. +04/08: no logs received so far. +31/07: no logs received yet. +28/07: DMC logs are still pending. +22/07: still waiting. +16/07: still pending +14/07: pending +10/07: no data so far. +03/07: still wait for data. +01.07: still wait for DMC log. +24/06: getting DMC log is pending +17/06: request for DMC log has been sent. +1706: pls capture DMC logs +02/06: TBOX log as well as DMC are attached. +02/06: DMC log as well as TBOX are requested. Wait for feedback.",Low,temporary close,生态/ecologically,袁清,07/08/2025,EXEED RX（T22）,LVTDD24B2RG033209,,TGR0001789,"logs_20250602-150509.7z,tboxlog.tar,License_error.jpg,DMC_data.jpg,8cd32041-2ae4-4112-9c3a-837cb20966a3.jpg",Vsevolod Tsoi,,,,,,69 +TR592,Mail,02/06/2025,,VK ,"VK as well as navi do not work. An error message comes up ""Check your network conection"". Apps work when using hotspot +VK 和 navi 都无法使用。 出现错误信息 ""检查您的网络连接""。 使用热点时，应用程序可以工作","0807：进站请求已发送，但无进展暂时关闭 +0804：建议用户进站，检查实车TBOX与主机之间线束连接是否有问题，同时抓取主机及TBOX日志 +0731:转国内TBOX专业先行分析，同时等待主机日志 +0730:已远程获取到TBOX日志，主机日志仍在等待中。 +0729：会后尝试抓取TBOX日志 +28/07: 仍在等待 DMC 日志 +22/07: 仍在等待数据。 +16/07: 仍在等待数据。 +0715：等待日志 +0626： +等待用户进站抓取日志中 +0618: +已发日志抓取手册，等待日志； +0617: +需要该车型提取日志的操作手册 +0603： +1.工单转国内生态工程师 +2.等待dmc日志","07/08: request is on progress +04/08：Suggest the user to come in and check whether there is any problem with the wiring harness connection between the TBOX and the main unit of the real car, and at the same time capture the logs of the main unit and the TBOX. +31/07:Turning to domestic TBOX professional to analyse first, while waiting for host logs +30/07:TBOX logs have been obtained remotely, host logs are still pending. +29/07：Trying to capture TBOX logs after the meeting +28/07: DMC log still pending +22/07: still waiting for data. +16/07: still wait for data. +14/07: no updates. +10/07: wait for data. +03/07: no data received yet. +01.07: no data received so far. +24/06: still wait for feedback. +18/06: request for log has been sent. Wait for data. +18/06：already sent log capture instruction, waiting for logs. +Note: before collecting DMC log, the VK music app needs to be started and repoudure the problem. +17/06: wait for an instruction for collecting DMC log +17/06：Pls capture DMC logs and T-box logs +03/06: Restart of tbox has been applied asking the customer to start the engine => so, after that car network started working (apps started working) until the next shutdown of the engine that means that when he shuted the engine off and started again, there was no more network available +03/06： +1.Ticket to chinese ecological engineer",Low,temporary close,生态/ecologically,袁清,07/08/2025,EXEED VX FL（M36T）,LVTDD24B7RD078552,,TGR0001769,"file_2461.MOV,Picture_1.jpg,Picture_2.jpg",Vsevolod Tsoi,,,,,,66 +TR593,Telegram bot,03/06/2025,,Network,"User has no network working in the car There is no network available however apn2 had been re-enabled on June, 1st according to the strategy of traffic renewal. +用户在车内没有网络，但根据流量更新策略，apn2 已于 6 月 1 日重新启用。","0610 +平台端已经修复，请顾客查看车辆是否恢复 +0605： +反馈车主已经重启车辆，仍然存在该问题 +0604: +1.建议用户重新启动车辆，重启时tbox也会重启，网络会进行策略刷写 +0603: +转MNO check","17/06: no reply so far. Temproray close +10/06: checked out in MNO - internet traffic was started being used. So, customer is asked to provide a feedback if the issue is no longer valid. +0610 +The platform side has been fixed, customers are asked to check if the vehicle is restored +05/06: what does it mean reboot the vehicle ? What needs to be done for reboot ? To take the battery terminals off? +0604. +1. Users are advised to reboot the vehicle, when rebooting the tbox will also be rebooted and the network will do a policy refresh @Vsevolod Tsoi",Low,temporary close,MNO,胡纯静,17/06/2025,EXEED VX FL（M36T）,LVTDD24B1PD604767,,TGR0001821,"image.png,Picture_3.JPG,Picture_2.JPG,Picture_1.JPG",Vsevolod Tsoi,,,,,,14 +TR594,Mail,03/06/2025,,Chinese TBOX in Russia,,"0811:换件成功，已解决该问题 +0804:暂无进展更新 +0731:暂无进展更新 +0729:暂无进展更新 +0715：等待更换t-box +0708：等待更换T-BOX +0626:仍然等待客户进站更换tbox中 +1706： +等待更换T-BOX +0610： +更换tbox，进行中 +0604: +需要进行Tbox更换","11/08: has been replaced successfuly->solved +04/08: still no progress +31/07: still no progress +29/07: still no progress +15/07: Waiting to replace t-box +08/07: Waiting to replace t-box +05/06: in process +0604. +Tbox replacement required @Evgeniy Ermishin",Low,close,TBOX,Evgeniy Ermishin,11/08/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ6SD094284,,,image.png,Evgeniy Ermishin,,,,,,69 +TR595,Telegram bot,03/06/2025,,Remote control ,"Remote control doesn't work. The car is shown as started in the mobile app however in fact the engine is OFF and car locked. +遥控器失灵 手机应用中显示汽车已启动，但实际上发动机处于关闭状态，汽车被锁住。","0610: +再次抓取日志，等待国内分析中 +0605： +1.属地运维反馈车主更换地理位置后仍远控超时 +需重新获取日志分析 +0604;TBOX日志分析，0603 车主远控时 TBOX未连上平台 可能当地信号不好，建议车主移动到信号好地方 +0604:经TSP平台日志分析，近两日远控失败原因均因为超时，转TBOX专业组查看具体原因","17/06: issue fixed. TR closed. +17/06: executing commands is checked out inTSP: remote engine start has successuffly been executed 3 times on June, 17th. Customer is asked to provide a feedback wether the issue is still valid. +0617: pls capture the log again +04/06: TBOX log is attached. +0603：Please retrieve the relevant tbox log +03/06: as the engine is shown as started in the app, user executed an operation of stopping the engine at on June, 3rd at 15:22 moscow time. Car coordinates at the moment of executing of stopping the engine: Tambov city, longitude&latitude 52.576024, 41.517779",Low,close,TBOX,Vsevolod Tsoi,17/06/2025,JAECOO J7（T1EJ）,LVVDD21B0RC053641,,TGR0001404,"LOG_LVVDD21B0RC053641_04_06_2025.tar,Picture_1.jpg",Vsevolod Tsoi,,,,,,14 +TR597,Telegram bot,04/06/2025,,VK ,VK music app doesn't work. All other apps work well. A message "Activation is in process/ongoing" comes up when opening the app - see picture attached,"0630：等待客户验证 +0618: 重启车辆会恢复正常，等待属地验证（TR585同样问题） +0617: + 短期方案：同时长按方向盘两侧的球形按钮重启车机，然后再次登录两个APP +长期方案: 8月份预计OTA升级 +0616： +临时措施: 车子放一晚第二天上电再看下是否OK，if not，重启车机，有概率能修复的 +长期措施: 软件升级，当前产线切换中，预计6/21完成，OTA时间未确定 +0610; +1.日志已获取，转国内分析中 +0604： +1.转国内生态分析 +2.请提供相关DMC日志","01.07: customer is back saying that VK music started working by itself without doing anything (ICC reboot etc.) +01.07: repeat request sent to user. Weply still pending. +24/06: no reply so far. +19/06: user is asked to reboot the ICC. Wait for feedback. +0617：Restart the ICC through pushing the 2 spherical buttons on both side of steering wheel for5s. then log in to the 2 apps again +software expected to be upgrade about August +0616: +Temporary measures: the car put a night on the next day on the power to see if it is OK, if not, restart the car, there is a probability that can be repaired! +Long-term measures: software upgrade, the current production line switching, is expected to be completed on 6/21, OTA time has not been determined. @Vsevolod Tsoi +09/06: DMC log is attached. +04/06: Request for DMC log is sent to dealer. Wait for feedback. +0604: +1. Ecological analysis within the transit country +2. Please provide relevant DMC logs @Vsevolod Tsoi",Low,close,生态/ecologically,袁清,01/07/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ6SD099307,,TGR0001851,"Exlantix.zip,file_2530.jpg",Vsevolod Tsoi,,,,,,27 +TR598,Telegram bot,05/06/2025,,Application,Some options are not displayed in the app - see photos attached. Smartphone model Samsung S24+,"0617: +等待客户反馈 +0610：请确认该账号是否为被授权账号，被授权账号只显示地图服务 +0605: +1.转app分析","25/06: issue is closed. +25/06: customer was asked again to provide a feedback. +24/04: customer is provided with an instruction to follow. feedback is pending wether thе issue is solved. +17/06: work in progress with customer. +0610: Please confirm whether the account is an authorized account, authorized accounts only display map services@ @Vsevolod Tsoi",Low,close,车控APP(Car control),文占朝,25/06/2025,EXEED RX（T22）,LVTDD24B0RG023469,,TGR0001820,Picture_1.jpg,Vsevolod Tsoi,,,,,,20 +TR599,Mail,05/06/2025,,VIN number doesn't exist,CH VIN doesnt exist in TSP PROD and UAT. But requests in PKI system exist (Check attachments),"0819：等待实车数据 +0814：等待实车数据 +0807:等待用户进站获取实车数据 +0805:暂无反馈 +0730：等待用户进站核实车辆信息，包含VIN，TBOXSN，ICCID，IHU_SN,Material NUM。 +0729：等待实车信息 +0708：等待实车信息 +0701：已联系客户 - 等待用户进站 +0619: 等客户进站核实车辆信息 +0610：Vin 已由客户确认，并存在于 PKI 系统中。 您说的 ""Vin 已更改 ""是什么意思？ +0606： +1.TSP平台不存在此车辆，请核实相关信息@葛英骐 +2.MES系统里车联网与非车联网都查询不到该VIN号，请@喻起航与前方确认该vin号是否发生过变更","16/09: No feedback from user - temporary close +19/08:waiting for data +14/08:waiting for data +07/08:waiting for data +05/08:waiting for data +30/07:Waiting for the user to come in to verify vehicle information, including VIN, TBOXSN, ICCID, IHU_SN,Material NUM. +29/07：Waiting for data +08/07：Waiting for data +01/07：Info requested - Waiting for results +17/06: Customer was invited to the dealer for collect data for import in TSP +10/06: Vin was confirmed by the customer and exists in the PKI system. What do you mean by ""Vin has been changed"" +The VIN number cannot be found in the MES system for both telematic and non - telematic. Please confirm whether the VIN number has been changed. @Kostya +05/06: @喻起航 Pls add this car to the TSP",Low,temporary close,local O&M,Kostya,16/09/2025,EXEED RX（T22）,LVTDD24B9RG006265,,From Andrew,"image.png,image.png",Kostya,,,,,,103 +TR600,Telegram bot,05/06/2025,,Remote control ,"The customer can't launch the engine. +Checked from TSP: @Multiple requests received simultaneously, please try again later"" But he said that launching engine didn't work since he bought the car. +客户无法启动发动机。 +已从 TSP 检查： @同时收到多个请求，请稍后再试""，但他说自从他买了这辆车后，启动发动机就无法工作了。","0811: SK完成 -> 问题解决可关闭 +0805:暂无SK学习后结果反馈 +0731:暂无SK学习后结果反馈 +0729:暂无SK学习后结果反馈 +0715：等待学完SK后反馈问题是否解决 +0702：PIN已发到群里 +0626：等客户进站学SK +0618:已提供 +0617: +EMS认证失败，需要提供SK学习操作说明 +0616： +日志已抓取 等待国内分析中 +0606: +1.平台端查询远控错误原因为：同时收到多个请求，请稍后重试 +2.等待Tbox日志获取中","11/08: SK done -> solved +05/08:No feedback on SK post-learning outcomes +31/07: no progress +29/07: no progress +15/07：Waiting for feedback on whether the problem is solved after learning SK +02/07：PIN has been sent to the chat group for TR600 @Evgeniy Ermishin +01/07: please send us immo pin +20/06: T-BOX instruction already sent +17/06: SK learning instruction later provide +16/06: TBOX in attachement +10/06：Waiting for Tbox logs to be fetched +10/06: waiting for comment",Low,close,车控APP(Car control),刘海丰,26/08/2025,JAECOO J7（T1EJ）,LVVDB21B8RC069270,,Immo PIN: 51433537,"LOG_LVVDB21B8RC06927020250616120856.tar,image.png,image.png",Evgeniy Ermishin,,,,,,82 +TR601,Mail,06/06/2025,,Network,"There is no network available after purchasing of an annual service package on June, 2nd.","0610: +TSP平台已经进行重启Tbox，问题已修复，建议回访用户问题是否关闭 +0606: +1.转MNO核实流量是否正常：自续费6.2~6.4只存在APN1使用记录；6.5号APN1与APN2都存在使用记录 +2.转tbox分析 +06/06: 6 月 5 日，作为临时解决方案，重新安装了 TBOX，网络重新开始运行（应用程序可以运行），但直到下一次关闭发动机。 重新启动发动机后，网络又可以使用了。","10/06: a request has been sent to find out if car network started working => wait for reply. +0610. +TSP platform has been carried out to restart the Tbox, the problem has been fixed, it is recommended to return to the user problem is closed or not +06/06: restart of TBOX has been applied on June, 5th as temporary solution and network started working again (apps work) but until the next shuting the engine off. When the engine was restarted, there was no network available again. ",Low,temporary close,TBOX,王桂玲,17/06/2025,EXEED VX FL（M36T）,LVTDD24B5PD621359,,,"image.png,LOG_LVTDD24B5PD62135920250606113100.tar",Vsevolod Tsoi,,,,,,11 +TR602,Telegram bot,06/06/2025,,Activation SIM,"Sim was activated and remote control works well but infotainment app on HU doesnt work (Sim not activated) + +No abnormal data on TSP and Simba platform. +!!! No enddate of pakage in web payment page !!! +Sim 已激活，遥控器工作正常，但 HU 上的信息娱乐应用程序无法工作（Sim 未激活） + + TSP 和 Simba 平台上没有异常数据。 + ！！！网页支付页面上没有关于套餐费用的数据！！！！","0929：升级通知已发布，升级编号：SL8998620250002，请邀请客户进站升级，新版本号：00.08.00 +0925：升级流程已走完，目前新版本再翻译中，预计下周完成释放到前方 +0917：仍在流程中，新版本还未释放到前方 +0916: 跟海外品质部确认升级是否已释放到前方 +0904:售后升级技术通知流程完成； +0902：售后升级技术流程中 +0814：等待发版 +0807：等待发版 +0804：等待发版 +0729：先按照临时方案处理，等待后续发版 +0722：翻译存在问题，仍在修复 +0715: 售后品质部未收到升级通知流程，等待通知 +0710：售后品质部未收到升级通知流程，等待通知 +0624: 已完成验证，预计06.26完成试装切换，6.27升级通知下发 +0623：等待验证 +0617： + 等待验证 +0616: +1.临时方案：已经同步至属地侧，等待外方验证 +2.长期方案：正式软件已集成开始提测，预计18日完成提测 +0612：提供临时方案，正式软件预计6/26释放； +0610：日志已获取，转国内分析中 +0606：转生态分析，dmc日志抓取中","1014: Request sent -> Waiting for data from Dealer and customer +0930:In procces +0929: Upgrade notice has been issued, upgrade number: SL8998620250002, please invite customers to dealer for upgrade. New DMC version: 00.08.00 @Kostya +0925：The upgrade process has been completed, and the new version is currently being translated and is expected to be released to dealer next week. +0917：Still in process, new version not yet released to dealer +0916: Confirm with the overseas quality department whether the upgrade has been released to the front +16/09:Waiting for update from customer +04/09: Aftermarket upgrade technical notification process completed; +02/09: After-sales upgrade technology in process +14/08: waiting for release +07/08: Waiting for release +04/08: Waiting for release +29/07：Handled under the provisional programme pending subsequent issuance of the version +22/07：Problems with translation, still being fixed +10/07：The after-sales quality department has not received the upgrade notification process and is waiting for further notice +24/06：The verification has been completed. It is expected that the trial installation and switch will be carried out on June 25th, and the upgrade notification will be completed on June 27th +24/06: Waiting for official update release +1. Interim solution: already synchronized to the territorial side, waiting for external validation +2.Long-term solution: the official software has been integrated and started testing, expected to complete testing on the 18th. +10/06: Attached DMC log from test car with same issue (The same as Andrew sent at 0609) +06/06： +please grab the dmc log",Low,Waiting for data,DMC,孙松,,OMODA C7 (T1GC),LVUGFB226SD831063,,TGR0001902,"log.mega.co.7z,image.png,image.png,image.png",Kostya,,,,,, +TR603,Mail,09/06/2025,,Navi, It is impossible to create route in Navi,"0610： +等待日志","19/06: reason - access to the network is suspended due to using up of internet traffic. +09/06: It is impossible to create route in Navi +please grab the dmc log@Evgeniy Ermishin ",Low,close,生态/ecologically,袁清,19/06/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ0SD104632 ,,,img_v3_02n3_b84fb031-b8db-4520-987a-c9df6c511fhu.jpg,Evgeniy Ermishin,,,,,,10 +TR604,Mail,09/06/2025,,Network,"There is no vehicle network available: an annual serivce package had been paid in advance on June, 6th. However, vehicle network still has to be available according to free 1 year service package that is provided when service activation (02/07/2024). Apps do not work accordingly. When using hotspot apps work. +没有可用的车辆网络：已于 6 月 6 日提前支付了年度服务套餐。 但是，根据服务激活（02/07/2024）时提供的 1 年免费服务套餐，车辆网络仍必须可用。 应用程序无法正常工作。 使用热点时，应用程序可以工作。","0610: +1.转MNO处理：建议先重启TBOX重新拨号，M36T的TBOX在续费后存在拨号机制问题；一般重启拨号可以恢复正常 +2.TSP平台已进行Tbox重启短信下发，请通知客户再次尝试 @Vsevolod Tsoi","16/06: customer's feedback - network is available again. Problem fixed. +0610. +1. to MNO processing: it is recommended to restart the TBOX first to redial, M36T TBOX in the renewal of the dialing mechanism problems; generally restart dialing can be restored to normal +2.TSP platform has been Tbox restart SMS sent Vsevolod Tsoi",Low,close,MNO,Vsevolod Tsoi,16/06/2025,EXEED VX FL（M36T）,LVTDD24B2PD573576,,TGR0001995,image.png,Vsevolod Tsoi,,,,,,7 +TR605,Telegram bot,09/06/2025,,Remote control ,There is no possible to launch engine remotely since the customer has bought the car,"0811: SK学习后，问题已解决 +0805：等待实车TBOX检查结果及日志反馈 +0731：等待实车TBOX检查结果及日志反馈 +0729：等待实车TBOX检查结果及日志反馈 +0722: 等待检查结果和日志（7月20日远控仍提示深度睡眠） +0715：等待日志和进站检查结果 +0626： +等待用户进站检查相关信息 +0623：等待客户进站检查T-box +0610：转国内TSP分析，已发送tbox重启唤醒短信，tbox未上线，建议用户进站检查tbox +0609: 错误代码 59： ""同时收到多个请求，请稍后再试""，但我试了很多次，问题都一样 +0609: 请提供远控错误代码@Evgeniy Ermishin ","11/08: solved by SK +05/08: Waiting for real car TBOX inspection results and log feedback +31/07: Waiting for real car TBOX inspection result and log feedback +29/07：Waiting for real car TBOX to check solution results and log feedback +22/07: Awaiting test results and logs (remote control still indicates deep sleep on 20 July) +17/06：users are advised to dealer to check tbox，and capture the logs +10/06：turn to chinese TSP side to check，SMS has been sent for tbox reboot wakeup, tbox is not online, users are advised to come in and check tbox +09/06: error code 59: ""Multiple requests received simultaneously, please try again later"" but hi tried many times, the same problem +09/06 Please check the cause of remote control fault code error@Evgeniy Ermishin ",Low,close,TBOX,刘海丰,11/08/2025,JAECOO J7（T1EJ）,LVVDB21B8RC069270,,,"image.png,image.png,image.png",Evgeniy Ermishin,,,,,,63 +TR606,Mail,09/06/2025,,Weather,Weather app issue in IHU - zero degree is always displayed,"0626：等客户验证 +0623：请参照附件图片打开APP中开关和隐私协议，之后到桌面小卡片查看是否有信息。若附件步骤操作后未恢复，请录个视频。 +0617: +等待客户反馈 +0610： +1.请属地运维按照附件进行操作即可 +2.请用户点击天气软件查看是否正常，不正常请录制视频并且抓取dmc日志","24/06: customer is asked again. If there is no reply until Thursday's meeting, TR will temporarily be closed. +0623：Please refer to the attached photo to open the switch and privacy agreement in the app, after that, back to the desktop to check if there is any weather information. If it is still not recovered after the attached steps, please record a video.@Vsevolod Tsoi +17/06: customer is asked if swithing privacy agreement ON fixed the issue. Wait for feedback. +0610: +Please local O&M just follow the attached file. +2. Please click on the weather software to see if the user is normal, not normal please record video and grab dmc log +10/06: should privace agreement have been opened somewhere in the system setup?",Low,temporary close,DMC,郭润函,26/06/2025,JAECOO J7（T1EJ）,LVVDB21B2RC107169,,,"img_v3_02n4_d4013f18-8233-4ca4-8d4f-c494398c10hu.jpg,Picture_1.jpg,Picture_2.jpg",Vsevolod Tsoi,,,,,,17 +TR607,Telegram bot,10/06/2025,,VK ,VK music doesn't work after DMC OTA upgrade. A message "Activation of license is not successful" comes up when opening the app - see picture attached.,"0807：暂时关闭，等待抓取到DMC日志后重新开启 +0804：等待DMC日志 +0731：等待DMC日志 +0728：等待DMC日志 +0722：等待DMC日志 +0716：暂无日志反馈 +0710：等待DMC日志 +0703：等待DMC日志 +0701：等待DMC日志 +0617: +已发日志抓取说明文件，等待日志抓取 +0610： +等待 DMC 日志抓取，转国内生态分析","07/08: closed temporarily. Will be re-opened when receiving DMC log. +04/08: DMC logs still pending. +31/07: no logs received so far. +28/07: still pending. +22/07: wait for data. +16/07: still wait for logs. +14/07: no logs received so far. +10/07: still wait for logs. +03/07: wait for DMC log from dealer. +01/07: still wait for receiving of DMC log +24/06: data is still pending. +18/06: request for collecting DMC log has been sent. Wait for dealer's feedback on data. +17/06: 1. Instruction to be prepared in russian +2. once translated, it will be sent to dealer. +0617： +already sent，waiting for DMC log capture +16/06: wait for an instruction to be provided being able to sent a request to dealer for collecting DMC log. +0610: +Waiting for DMC log capture, transferring to domestic ecosystem analysis",Low,temporary close,生态/ecologically,袁清,07/08/2025,CHERY TIGGO 9 (T28)）,LVTDD24B0RG115990,,TGR0002015,Picture_1.jpg,Vsevolod Tsoi,,,,,,58 +TR610,Mail,11/06/2025,,Activation SIM,"HU Apps doesnt work after activation and login. +remote control - stable","0929：升级通知已发布，升级编号：SL8998620250002，请邀请客户进站升级，新版本号：00.08.00 +0929：翻译已完成，正在等待挂网 +0925：升级流程已走完，目前新版本再翻译中，预计下周完成释放到前方 +0917：仍在流程中，新版本还未释放到前方 +0904:售后升级技术通知流程完成； +0902：售后升级技术流程中 +0814：等待发版 +0807：等待发版 +0804：等待发版 +0729：先按照临时方案处理，等待后续发版 +0722：翻译存在问题，仍在修复 +0715：售后品质部未收到升级通知流程，等待通知 +0710：售后品质部未收到升级通知流程，等待通知 +0624: 已完成验证，预计06.26完成试装切换，6.27升级通知下发 +0617： + 等待验证 +0616： +进展同TR602 +0610： +转国内分析","1014: Request sent -> Waiting for data from Dealer and customer +0930:In procces +0929: Upgrade notice has been issued, upgrade number: SL8998620250002, please invite customers to dealer for upgrade. New DMC version: 00.08.00 @Kostya +0925：The upgrade process has been completed, and the new version is currently being translated and is expected to be released to dealer next week. +0917：Still in process, new version not yet released to dealer +16/09:Waiting for update from customer +04/09:Aftermarket upgrade technical notification process completed; +02/09: After-sales upgrade technology in process +14/08: waiting for release +07/08: Waiting for release +04/08: Waiting for release +29/07：Handled under the provisional programme pending subsequent issuance of the version +29/07：Please. update the status of the fix for ASD +22/07：Problems with translation, still being fixed +10/07: The after-sales quality department has not received the upgrade notification process and is waiting for further notice +24/06：The verification has been completed. It is expected that the trial installation and switch will be carried out on June 25th, and the upgrade notification will be completed on June 27th +24/06: Waiting for official update release +16/06: +Progress same as TR602",Low,Waiting for data,DMC,孙松,,OMODA C7 (T1GC),LVUGFB222SD830802,,,IMG_1747.MP4,Kostya,,,,,, +TR611,Mail,11/06/2025,,Remote control ,Remote control doesn't work + IHU login/logout not ok,"0826：协商一致，切换等待数据状态 +0819:建议切换成等待数据，用户进站后再切换状态 +0814：暂无DMC日志 +0811: 请求已被再次发送，等待经销商反馈是否抓取DMC日志 +0804：暂无DMC日志 +0729：暂无日志 +0715：等待DMC日志 +0708：等待DMC日志 +0623：tbox日志分析未果，等待DMC日志中 +0620: +1.TSP平台查询车辆T-BOX登录正常，实时数据正常上报。新日志无远控操作。 +2. 6月11日已有远控成功记录，麻烦客户重启启动车俩再尝试下远控。 +3. 如果还是未成功建议客户提供APP远控失败的截图和视频。 +0620：新日志已提供，等待分析 +0617: 卡正常，APN2用完关停了，APN1可以正常使用，麻烦客户进站检查，再次抓取日志 +0616:查询失败原因为深度睡眠，建议用户使用物理钥匙启动发动机即可 +0613: +1.该车TBOX近三日登录记录正常，DMC无登录记录，App状态里程等信息未显示，tbox日志已上传 +2.问题已流转至DMC、TBOX、App等相关责任方 +3。TBOX方已发送日志获取邮件，等合规接口人审批后流转至相应工程师进行问题分析 +4.需属地运维提供更多问题描述细节","18.09: customer told us that now all works ok +26/08: Consensus, toggle wait for data status +19/08:It is recommended to switch to wait for data and switch the state after the user enters the station. +14/08：still waiting +11/08: request has been sent one more time +04/08 still waiting +31/07 still waiting +29/07 still waiting +01/07: still waiting +25/06： +Still waiting in the DMC log and the video record for remote control +23/06： +Wait for DMC log to check the no ICC login record issue. +20/06： +1. TSP platform query vehicle T-BOX login normal, real-time data normal report.The new log has no remote control operation. +2. On 11th June, there is a record of successful remote control, please restart the car and try remote control again. +3. If still unsuccessful, it is suggested customer to provide screenshot and video of APP remote control failure.@Evgeniy Ermishin +19/06: new log was added, please check +17/06：pls capture new t-box log +16/06:Query failed due to deep sleep, users are advised to just start the engine with a physical key +11/06: Remote control doesn't work +bad status of car + IHU login/logout not ok. tbox log in attachment +13/06: +1. The car's TBOX login record is normal in the past three days, DMC has no login record, App status mileage and other information is not displayed, tbox logs have been uploaded +2. The problem has been transferred to DMC, TBOX, App and other related parties. +3. TBOX has sent an email to obtain the logs, and will flow to the corresponding engineers to analyze the problem after approval by the compliance interface person. +4. Local O&M is required to provide more details of the problem description. @Evgeniy Ermishin",Low,close,DMC,王冬冬,18/09/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZXSD097527,,,"LOG_LNNBDDEZXSD09752720250619090737.tar,image.png,LOG_LNNBDDEZXSD09752720250611164254.tar,image.png,image.png,image.png,image.png",Evgeniy Ermishin,,,,,,99 +TR615,Telegram bot,16/06/2025,,VK ,VK music doesn't work. All other apps work well.,"0626：问题已解决，等反馈问题怎么恢复的 +1806：VK音乐无法工作. 等待属地抓取DMC日志 +17/06：属地等待抓取日志中","02.07: dealer's feedback: troubleshouting was applied only and then the respective faults were deleted. +01.07: repeat request sent to dealer to know the actions that were done to fix the issue. Feedback is still pending. +24/06: we got feedback from dealer that issue was solved. Dealer was asked on what was done to fix the issue. Wait for feedback +18/06: Waiting for DMC logs +17/06: the issue is with VK music - changed in TR description +17/06: aksed to clarifify what app is client having a problem with +0617: pls help confirm Is it VK Music cannot be activated, or VK Video cannot be activated? +17/06: request for DMC log has been sent.",Low,close,生态/ecologically,袁清,02/07/2025,EXEED RX（T22）,LVTDD24B3RG021277,,TGR0002086,file_2725 (1).jpg,Vsevolod Tsoi,,,,,,16 +TR619,Mail,18/06/2025,,Problem with auth in member center,"After scanning QR, customer sees : ""Couldn't log in. A +car owner account is required"" +扫描 QR 后，客户看到：""无法登录。 需要车主账户""。","0819：暂无更新 +0814:暂无更新 +0811: 经销商在两辆不同的车之间更换了 DMC，已告知让他们换回。 +0805:等待新日志上传，之前的日志是非该问题车辆 +0731:等待新日志上传，之前的日志是非该问题车辆 +0729:等待新日志上传，之前的日志是非该问题车辆 +0724: 日志发错不属于这辆车，等待重新取日志 +0708: 等待DMC日志 +0624：等待DMC日志 +0620: 需要抓取DMC日志","26/08: upade successfull- solved +19/08:No update for now +14/08:No update +11/08: The dealer changed DMC between two different cars, I told them to return it back. +05/08: Waiting for new logs to be uploaded, previous logs are non-problematic vehicles +31/07: Waiting for new logs to be uploaded, previous logs are non-problematic vehicles +29/07: Waiting for new logs to be uploaded, previous logs are non-problematic vehicles +24/07: Logs sent in error not belonging to this vehicle, waiting to re-fetch logs +23/07: DMC log was attached, please check +01/07: in process +20/06：pls help capture DMC log. and Pls reproduce the problem before taking the log to ensure that the effective log is extracted. @Evgeniy Ermishin",Low,close,DMC,Evgeniy Ermishin,26/08/2025,EXEED RX（T22）,LVTDD24B3RG019707,,,"log LVTDD24B3RG019707.zip,VIDEO-2025-06-18-08-50-55.mp4",Evgeniy Ermishin,,,,,,69 +TR620,Telegram bot,18/06/2025,,Navi,The customer sees distance in kilometers on NAVI (its correct) but in HUD sees meters - see photo,0619:该问题最新版本软件已修改，售后升级通知已下发，待OTA即可,"0619:The problem has been fixed by the latest version of the software, wait for the OTA.",Low,temporary close,DMC,殷秀梅,20/06/2025,CHERY TIGGO 9 (T28)）,LVTDD24B3RG104191,,,"image.png,image.png",Evgeniy Ermishin,,,,,,2 +TR623,Telegram bot,18/06/2025,,Application,"It's impossible to share rules of remote control to another person +无法与他人共享远控","0703: 问题已修复 +0701: 等待排查 +0630：等待验证 +0626：24日下午数据已修复，等待属地验证 +0624：下午确认已完成数据修复，请再尝试下 +0623：TSP的授权接口有点问题，预计今天会完成数据修复，请明天再试下 +0619：需要属地确认是被分享账号无法远控还是被分享账号网络问题 +0618: TR579地图问题已修复，账号分享问题新建跟进，需要属地运维联系用户录制账号分享问题视频","07/01: still doesn't work +0626：data was repaired on the afternoon of the 24th and is awaiting verification by the local 0&M team +0624：confirmed that the data repair has been completed. Please help try again @Evgeniy Ermishin +24/06: still doesn't work +0623: There is a problem with the TSP authorisation interface. Data repair is expected to be completed today. Please try again tomorrow.@Evgeniy Ermishin +20/06: We used our phones (Evgeniy and Andrey) in attached video. Andrew is owner of car, his phone: +79859203437, Evgeniy (+79106007644). +Network on our phones is perfect. +0619：pls provide the authorised mobile phone number and confirm whether the problem is that the authorized account has no network or is unable to use the remote control @Evgeniy Ermishin +19/06: Video was added, please check +0618： TR579 map issue has been fixed, account sharing issue new tracking to follow up, need to local O&M to contact users to record video of the issue.",Low,close,用户EXEED-APP(User),刘永斌,03/07/2025,EXLANTIX ET (E0Y-REEV),ANY VIN,,,"IMG_1539.MOV,image.png",Evgeniy Ermishin,,,,,,15 +TR627,Mail,19/06/2025,,Network,"There is no network connection in any places, also no information in IHU about TBOX. ","0730：已询问 ASD 和经销商有关更改 tbox 和将其切换到 ""正常 ""模式，暂无反馈 +0728:25日后无实时数据上传，建议咨询用户是否已经恢复，如恢复可关闭 +0718: t-box已更换，tsp数据已更新，等待结果验证。（7月18日ihu和t-box 登录记录正常） +0701：等待换t-box +0626：等待t-box日志 +0624：等待t-box日志 +0620: +1. 没有查询到t-box登录记录，车控记录5月8日失败提示深度睡眠，物理钥匙无法唤醒车辆。 +2. SIM卡状态正常。 +3. 建议客户进站用U盘取下T-BOX日志. +0619：没有进行SIM卡的实名认证，建议用户去实名认证后重试 +0619：2022年型车需要确认是否是联网车型@刘娇龙","30/07: asked ASD and dealears about tbox changing and switching it to ""normal"" mode +28/07:No real-time data uploaded after 0728:25, suggest consulting users whether it has been restored, if restored can be closed +18/07: tbox was changed-> also data in TSP was changed, waiting for result +01/07: still waiting +26/06: have sent request for changing tbox to ASD +26/06: it's impossible to record TBOX-LOG, because there is no info about tbox in engineering menu ->see screenshots +0626: Waiting for t-box logs +0622：1. No t-box login record was found. The remote control prompt on May 8th failed because of deep sleep and the physical key was unable to wake up the vehicle. +2. The SIM card is in normal condition. +3. It is recommended that the customer go to dealer to capture the T-BOX log with USB.@Evgeniy Ermishin +19:06: I am not agreed with you, please check TSP again +0619：There is no real name authentication of the SIM card, it is recommended that users to go to real name authentication and retry @Evgeniy Ermishin",Low,close,TBOX,Evgeniy Ermishin,31/07/2025,EXEED VX FL（M36T）,LVTDD24B5RD584753,,,"img_v3_02nk_529d9ad8-9518-48b5-bc04-37af3a8d8chu.png,img_v3_02nk_8345b3ee-6a22-4cc6-ae47-8ebd0a3529hu.png,img_v3_02nd_918764af-09fc-4464-9614-a0a50ac8073g.jpg,image.png,видео неисправности.mp4,IMG_20250611_165728 (002).jpg",Evgeniy Ermishin,,,,,,42 +TR633,Telegram bot,20/06/2025,,VIN number doesn't exist,"CH VIN doesnt exist in TSP PROD, UAT and no requests in PKI. Pls check on the MES side +中国车架号 VIN 不存在于 TSP PROD 和 UAT 中，在 PKI 中也没有请求。 请检查 MES 端","0701：无法在MES系统中查询到该车辆信息，麻烦手动在TSP平台录入车辆信息 +0626：等待客户确认 +0623: +1.经核查，oq TSP正式环境不存在该车辆，转MES端排查此问题 +2.经查询MES车 该车辆为23年，仅存在物料号及车机SN，进一步排查中 +3.经查询，该车辆物料号为T6480NMGXKH0006，此物料号为非车联网车辆，仅支持绑定车辆App，不支持激活车控等操作","0717: Waiting for data - temporary close due customer's ignore +0708：Waiting for data +0701：Info requested - Waiting for results +0701：The vehicle information cannot be queried in the MES system. Please manually enter the vehicle information on the TSP platform @Kostya +30.06 reopen - got feedback from customer. vehicale has Tbox and IOV apps check attachments +feedback time out - temporary close +0624: Waiting for customer respond +0623. +In contact with customer, waiting for respond. +0623. +1. After verification, oq TSP official environment does not exist in the vehicle, to the MES side of the investigation of this problem +2. After querying the MES vehicle The vehicle is 23 years old, only the material number and vehicle machine SN exist, further investigation in progress. +3. Upon enquiry, the vehicle material number is T6480NMGXKH0006, this material number is not a vehicle network vehicle, only support the binding of the vehicle App, does not support the activation of the car control and other operations @Kostya",Low,temporary close,MES,Kostya,17/07/2025,EXEED RX（T22）,LVTDD24B6PD668920,,TGR0002201,"file_3081.mp4,image.png,image.png,image.png",Kostya,,,,,,27 +TR634,Mail,20/06/2025,,OTA,"The customer can't do OTA. Roolback failed. +客户无法进行 OTA。 回滚失败。","0826: QS属地已通知所有有此问题的客户到经销商处办理此手续。协商一致，转为等待数据 +0811: ASD 已告知经销商此问题处理流程： ""如果客户不能进行 OTA，则应进行 DMC SK 学习""--正在进行中 +0805: 等待DMC SK学习反馈 +0731: 等待DMC SK学习反馈 +0729: 等待DMC SK学习反馈 +0708: 等待学习SK +0626: 等待DMC SK学习反馈 +0623： +1.T22OTA问题，转国内专业组分析·@韦正辉 +2.上电失败，怀疑未学习sk，现在需要属地运维学习DMC 的SK，具体疑问可咨询@韦正辉","18/09: solved +26/08: I have sent to all customers with this problem go to dealer and make this procedure. Consensus to wait for data +11/08: ASD are preparing now special procedure for dealers: "" if the customer can't do OTA, then they should DMC SK learning"" - in process +05/08: Waiting for DMC SK learning feedback +31/07: Waiting for DMC SK learning feedback +29/07: Waiting for DMC SK learning feedback +08/07: waiting to learn SK +26/06：Waiting for DMC SK learning feedback +23/06: +1.T22OTA issue, transferred to domestic professional group for analysis +2.power-up failure, suspected of not learning SK, now need to belong to the O&M to learn DMC SK, specific questions can consult @韦正辉 @Evgeniy Ermishin",Low,close,OTA,韦正辉,18/09/2025,EXEED RX（T22）,XEYDD14B3SA012216,,,5_Дефект 1.jpg,Evgeniy Ermishin,,,,,,90 +TR635,Telegram bot,20/06/2025,,Application,"The customer can't activate his car (bound) He became error: A07913. But he deleted his account 10 days ago and nothing happend after 7 days +客户无法激活他的汽车（已绑定）： A07913. 但他在 10 天前删除了账户，7 天后也没有任何反应。","0730：核实为APP自身问题，未把用户数据同步给TSP系统导致，目前会采用临时手段：数据库上清除异常数据，维持业务稳定； +长期措施：APP与APP后台优化代码，增加校验逻辑及其他预防措施我，根本上解决问题。临时方式周五前反馈结果 +0729：会后协调信息公司讨论解决方式 +0708: 等待客户重新绑定验证 +0702: 已从TSP后台删除数据，请建议客户重新绑定 +0701: 预计7月2号从TSP平台删除数据解决 +0626：等待确认APP发版时间（未得到确认发版时间信息） +0624: 预计下个版本修复，确认预计发版时间信息 +0623： +1.车辆激活绑定App问题，转国内App分析 ","30/07: Verified as APP own problem, not synchronised user data to the TSP system, currently will use temporary means: database to remove abnormal data, to maintain business stability; Interim approach to feedback results by Friday +Long-term measures: APP and APP background optimisation code, increase the checking logic and other preventive measures I, fundamentally solve the problem +29/07: Coordinate with the information company after the meeting to discuss the solution. +08/07：waitting for customer to rebind +02/07: The data has been deleted from the TSP backend. Please advise the customer to try to rebind.@Evgeniy Ermishin +01/07: It is expected that the data will be deleted from the TSP platform on July 2nd for resolution +24/06：It is expected to be fixed in the next release app，Confirm the specific information again +23/06: +1. Vehicle activation binding App issues, to domestic App analysis",Low,close,用户EXEED-APP(User),岳晓磊,30/07/2025,CHERY TIGGO 9 (T28)）,LVTDD24B2RG089618,,,"20250620-174954.png,image.png",Evgeniy Ermishin,,,,,,40 +TR636,Telegram bot,20/06/2025,,Network,"No TBOX Login. No connection. Car in deepsleep after launch via start buitton +没有 TBOX 登录。 无连接。 通过启动按钮启动后汽车处于休眠状态","0819:建议切换成等待数据，用户进站后再切换状态 +0814：等待用户进站 +0807：等待用户进站 +0805：等待用户进站 +0731：等待用户进站 +0729：等待用户进站升级TBOX +0721：T-BOX版本不对，建议客户建站升级，最新版本为18.19.04(客户目前版本18.19.03，该版本未测试过OTA升级04，建议进站升级） +0718：日志已付，转国内分析 +0717：等待日志上传 +0708：等待日志 +0701:等待日志上传 +0626： +等待用户进站抓取日志中 +0623: 建议客户进站抓取T-BOX日志","19/08:It is recommended to switch to wait for data and switch the state after the user enters the station. +14/08: still waiting +07/08: still waiting +04/08: still waiting +31/07: still waiting +29/07: Waiting for users to come in to upgrade the TBOX +22/07: Ananlysis +21/07：The version of T-BOX is not correct, suggested customers go to dealer to upgrade T-BOX, the latest version is 18.19.04.@Kostya +18/07: tbox log from dealer attached. +17/07: Waiting for data +08/07：Waiting for data +01/07：Logs requested - Waiting for results +24/06：Logs requested. Waiting for logs from dealer +23/06：Sent request for invating customer and capturing logs. Waiting +23/06：it is suggested that customer go to dealer to capture log with USB @Kostya",Low,Waiting for data,TBOX,项志伟,,CHERY TIGGO 9 (T28)）,LVTDD24B6RG129232,,TGR0001347,tboxlog.tar,Kostya,,,,,, +TR639,Telegram bot,23/06/2025,,OTA,DMC OTA upgrade failed - see photo attached.,"0807：暂时关闭，等待抓取到DMC日志后重新开启 +0804: 仍在等待 OTA日志 +0731：仍在等待。 +0728: 仍在等待 OTA 日志 +0722：等待OTA日志 +0708: 等待日志 +0627：等待日志 +0624:等待属地抓取日志","07/08: closed temporarily. Will be re-open when getting DMC log. +04/08: still wait for DMC logs +31/07: still pending. +28/07: OTA log still pending +22/07: still pending. +16/07: OTA log is still pending. +14/07: still pending. +10/07: OTA log still pending. +03/07: still wait for data. +01.07: no feedback so far. +25/06: wait for OTA log +0623：please directly capture the log，no need any actions +23/06: OTA log is requested. Please clarify if some actions are required before collecting OTA log",Low,temporary close,OTA,Vsevolod Tsoi,07/08/2025,EXEED RX（T22）,LVTDD24B0RG013640,,TGR0002195,,Vsevolod Tsoi,,,,,,45 +TR640,Telegram bot,23/06/2025,,Navi,"Navi app crashes upon starting - see video attached. +打开Navi闪退，请查看附件视频","0627: 客户根据提供的说明，将允许地理定位的开关打开最终解决了问题 +0626：等客户反馈 +0624：请先确认主机版本是否为 “02.02.00” 和导航位置权限是否已开启。如果不是请先更新后重试。如果以上两项信息都无误，还是出现此问题建议客户进站提取DMC日志。 +0623: 打开Navi闪退，请查看附件视频","0627: customer Switching allowing geoposition ON has fixed the issue in the end according to the instruction provided +26/06: allowing privacy agreement has fixed the issue solved => TR closed. +0624: Please first invite customer to confirm whether the host version is ""02.02.00"" and whether the navigation location permission has been enabled. If not, please update first and then try again. If both of the above information are correct but the problem still occurs, it is recommended that the customer go to station to capture DMC log.@Vsevolod Tsoi",Low,close,DMC,郭宏伟,26/06/2025,EXEED RX（T22）,LVTDD24B9RG033319,,TGR0002222,file_2855.mp4,Vsevolod Tsoi,,,,,,3 +TR642,Telegram bot,24/06/2025,,VIN number doesn't exist,"Car doesnt exist in the Legend.Exlantix (screenshot 3) but exist in the TSP (screenshot 2). Pls add cat to the legend platform. We dont have info about Colour codes and deskcription (screenshot 1) +/Legend.Exlantix（截图 3）中没有汽车，但 TSP（截图 2）中有。 请将猫添加到传奇平台。 我们没有关于颜色代码和描述的信息（截图 1）","0626： +1.转App开发+信息公司对齐中 ","26/06: vehicles data has been imported in legend so that customers are able to add their cars in mobile app. TR closed. +24/06: one more VIN is added (see column VIN). It is present in TSP but no in legend.",Low,close,用户EXEED-APP(User),文占朝,26/06/2025,EXLANTIX ET (E0Y-REEV),"LNNBDDEZ6SD142236 +LNNBDDEZ4SD156765 +LNNBDDEZ9SD099804",,TGR0002247,"image.png,image.png,image.png",Kostya,,,,,,2 +TR643,Mail,24/06/2025,,HU troubles,No ICC log in => no car network available. Navi doens't work.,"0826：协商一致，切换等待数据状态 +0819:建议切换成等待数据，用户进站后再切换状态 +0814：暂无进展更新 +0812：暂无客户实车数据 +0808:等待客户数据，以便向经销商提出申请。 +0805：请前方进入实车工程模式，确认是否是在生产环境中 +0804: 等待询问具体时间信息 +0731: 请求正在处理中。 +0729：请属地人员更新进展 +0725: 需确认一下导航不可用的时间点 +0722: DMC日志已发专业分析 +0708: 等待DMC日志 +0625: +等待抓取DMC日志及相关问题视频 +0624： +1.经核查T-box登录数据和SIM卡流量状态正常。无车机注册记录，无网络，NAVI不可用","09/10: temporary closed. Will be re-opened when receiving the data. +25/09: no data received yet. +22/09: data still not received +18/09: data pending. +15/09: no data received so far. +11/09: still wait for data. +26/08: Consensus, toggle wait for data status +19/08:It is recommended to switch to wait for data and switch the state after the user enters the station. +14/08: still pending +12/08: customer's contact data is pending. +08/08: wait for customer's data being able to make a request to dealer. +07/08: request is on process +05/08: Please go ahead and enter the live vehicle engineering mode to confirm that it is in the production environment +04/08: time point is requested. +31/07: request is in progress. +29/07: Request for progress update from territorial personnel +25/07: Need to confirm the point in time when navigation is not available. +22/07: DMC log is attached. +22/07: wait for feedback wether visit took place. +16/07: visit of customer is planned for July, 19th. +14/07: still pending +10/07: ICC log still pending. +02/07: request for ICC log has been sent. Wait for data. +01/07: prepartion of the instruction for dealer is in process. It is gonna be sent on 02/07. +25/06: once step by step instruction is provided by 2nd line, it will be prepared and translated in russian and then a request will be sent to dealer. +0625: +1.please grab the DMC log,provide the issue time and video etc.@Vsevolod Tsoi",Low,temporary close,DMC,王冬冬,09/10/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZXSD099522,,,E.7z,Vsevolod Tsoi,,,,,,107 +TR645,Mail,24/06/2025,,Network,"No connection, no QR code in member centre and no DMC login on E0Y after bound in the app. Tbox working well, remote control is ok, +DMC version: +""sv"": ""01.00.21_02.02.230"" according to the OTA logs. +But only one version was mentioned in update campaings before - 01.00.13_02.02.79. + +Please, confirm wheter this version is stable +无法连接，会员中心没有二维码，在应用程序中绑定后无法在 E0Y 上登录 DMC。 Tbox 运行良好，远控正常、","0626：车辆环境配置问题，测试环境切换至生产环境，恢复正常。(海外验证借用车辆测评，未正确设置环境) +0625: +那现在是平台修复了.需要用户核实下是否恢复正常 +0624： +转国内DMC工程师分析","Solved according to feedback -> Closed +0625. +So now it's a platform fix.We need the user to verify that it's back to normal. @Kostya",Low,close,DMC,沈世敏,26/06/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ5SD094857,,internal,,Kostya,,,,,,2 +TR646,Mail,25/06/2025,,Navi,"There is no voice notifications (where you need to go, then there are no sound alerts where +to turn, how much time is left before the turn, cameras and speed limit) +没有语音通知（您需要去哪里，哪里就没有声音提示转弯、距离转弯还有多少时间、摄像头和限速）。","0805：建议暂时关闭此问题，如用户进站获取到日志后再进行分析 +0708：等待DMC日志 +0627: 语音助手处于激活状态，且音量不为0. 日志抓取申请已发，等待日志。 +0625： +1.建议抓取DMC日志，转国内生态分析 +2.请确认用户是否关闭导航语言播报功能，或者是否在系统设置中将导航音量设置为0","05/08：Suggest that this issue be closed temporarily and analysed after the logs have been obtained. +08/07：waiting for DMC logs +30.06: 2 more VINs are added (see column ""VIN/esim""). Log is requested for LVTDD24B5RG033835. +25/06: voice assistant is activated and volume is not 0. +making request for invitation to the dealer for DMC log. +0625: +1. Suggest grabbing DMC logs @Evgeniy Ermishinand turning domestic ecological analysis +2.Please make sure that the user has turned off the navigation language broadcasting function or set the navigation volume to 0 in the system settings. @Evgeniy Ermishin",Low,temporary close,生态/ecologically,袁清,26/08/2025,EXEED RX（T22）,"XEYDD14B3RA008772 +LVTDD24B5RG033835 +LVTDD24B8RG031383",,,17506726012371-900967465.mp4,Evgeniy Ermishin,,,,,,62 +TR651,Telegram bot,26/06/2025,,VK ,"VK video app doesn't work. App doens't require an update in app market in IHU. +VK VIideo程序无法工作，应用市场里面也没有APP更新信息。","0728: DMC SW OTA 升级后恢复了 VK 视频中的搜索选项。问题已解决。 +0722: 暂无升级后反馈。 +0716: 等待升级。 +0715: 等待升级反馈 +0708: 等待客户进站升级DMC +0701: 建议客户进站升级DMC版本（目前已释放的版本:02.02.00_01.37.33） +0627: 客户DMC版本1.0.20250312.154455，该版本是未修复的老版本。27日已OTA推送最新DMC版本, 建议客户升级DMC +0626: 1.车辆SIM卡状态正常,流量正常，近一周T-BOX和IHU登录数据正常@袁清","28/07: Search option in VK video is restored following DMC SW OTA upgrade. Issue solved out. +28/07: checked out in FOTA - DMC SW version is the latest one 02.02.00. Thus, it seems DMC was upgraded with USB but there was no feedback from dealer. So, customer was asked to provide wether search option was restored in VK video app. +22/07: no feedback on upgrade so far. +16/07: wait for upgrade. +14/07: wait for feedback. +10/07: wait for feedback on upgrade result +04/07: request for DMC SW upgrade with USB has been sent. Wait for invitation customer to dealer. +0701: Advise customer to come in and upgrade DMC version (currently released version：02.02.00_01.37.33） +01.07: current status - car has no connection to download OTA upgrade. +28/06: customer was informed that OTA upgraded has been sent out for his car. Wait for download and then upgrade. +0627：Customer DMC version 1.0.20250312.154455, this version is an old one that has not been fixed. The latest DMC version was pushed out via OTA on the 27th. It is recommended that customers upgrade DMC @Vsevolod Tsoi@韦正辉 +26/06: Request for DMC log has been sent. Wait for data. +0626：The SIM card status of the vehicle is normal, the data traffic is normal, and the login data of T-BOX and IHU are normal in the past week.",Low,close,生态/ecologically,袁清,28/07/2025,EXEED RX（T22）,LVTDD24B9RG033319,,TGR0002221,"file_2919.MP4,file_2854.jpg,file_2853.jpg",Vsevolod Tsoi,,,,,,32 +TR652,Telegram bot,26/06/2025,,Network,"We have M36T, which has problems with remote control. +He has already replaced tbox, he is online right now. +Here you can see screenshot with missing data. +Also in attachment there is a tbox log. +我们有M36T，遥控器有问题。他已经换了tbox，他现在在线。这里你可以看到缺少数据的截图。 +附件中还有一个tbox日志。","0728：28日检查平台端，该车仍无TBOX登录记录，请核实是否已经进站 +0708：等待验证 +0626:更换完t-box后未退出工厂模式，建议客户进站处理","28/07: Checked the platform side on 28th, there is still no TBOX login record for this vehicle, please verify if it has been in the station. +08/07：waiting for customer feedback +01/07: already asked, waiting +0626: After replacing the t-box, the factory mode was not exited. It is suggested that the customer go to dealer to handle it @Evgeniy Ermishin",Low,close,TBOX,Evgeniy Ermishin,29/07/2025,EXEED VX FL（M36T）,LVTDD24B2PD384362 ,,,"img_v3_02nk_a9313e10-3f23-4f13-bce3-2a66a36bcbhu.jpg,img_v3_02nk_67cdc4cd-1e47-4324-b9f1-e61020e903hu.png,tboxlog.tar",Evgeniy Ermishin,,,,,,33 +TR653,Telegram bot,26/06/2025,,Network,"Same as TR645. No connection, no QR code in member centre and no DMC login on E0Y after bound in the app. Tbox working well, remote control is ok, +But now on 01.00.13 DMC version +和TR645一样。没有连接，会员中心没有QR码，app绑定后E0Y上没有DMC登录。Tbox工作正常，遥控没问题， +但现在DMC版本01.00.13 ","0826：协商一致，切换等待数据状态 +0819:建议切换成等待数据，用户进站后再切换状态 +0814:等待用户进站 +0812:等待用户进站 +0807:等待用户进站 +0805:等待用户进站 +0731:等待用户进站 +0729：请属地人员更新进展 +0715：等待客户进站刷新DMC +0710：升级通知已经下发给经销商，建议让经销商邀请客户进站升级。 +0701: DMC版本01.00.13是老问题版本。这个问题在最新版本已修复，等待售后技术升级通知单发布后，邀请客户进站刷新版本（更新后版本01.00.21） +0627: 建议客户建站抓取DMC日志，并说明问题发生的具体日期。考虑到日志可能会被覆盖无法取到有效日志，最好是客户进站后复现问题并拍摄截图问题界面的照片，之后再提取日志。 +0626:转国内DMC分析","26/08: Consensus, toggle wait for data status +19/08:It is recommended to switch to wait for data and switch the state after the user enters the station. +14/08: still waiting +12/08: still waiting +07/08: still waiting +05/08: Waiting for users to enter the station +31/07:still waiting +29/07: Request for progress update from territorial personnel.@Kostya +15/07：waitting customer go to dealer to upgrade DMC @Kostya +10/07：The upgrade notice has been sent to the dealer. It is suggested that the dealer invite customers to dealer for the upgrade. @Kostya +08/07：Waiting for update +01/07：DMC version 01.00.13 is an old issue version. The issue has been fixed in the latest version. After the post-sales technical upgrade notification is released, will invite customers to the station to refresh the version. The new verison will be 01.00.21 @Evgeniy Ermishin +01/07：Info requested - Waiting for results +27/06：It is recommended that the customer go to dealer to capture DMC logs and specify the exact date when the problem occurred. Considering that the logs may be overwritten and no valid logs can be obtained, it is best to reproduce the problem and take pictures of the problem interface, and then grab the logs. @Kostya +26/06: Transfer to domestic DMC analysis",Low,Waiting for data,DMC,王冬冬,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ2SD099756,,TGR0002304,"image.png,image.png,image.png,image.png",Kostya,,,,,, +TR657,Mail,27/06/2025,,Application,Mass problem for CHERY and EXEED with applications. Cars were missed from the app.,,Closed. But what was the reason? ,Critical,close,,,27/06/2025,,ALL CHERY AND EXEED CARS,,,"20250627-083045.jpg,20250627-083040.jpg,20250627-083033.jpg,20250627-083024.mp4,img_v3_02nl_31b60adf-6672-4790-8a1e-18695ce5dbhu.png",Evgeniy Ermishin,,,,,,0 +TR658,Telegram bot,27/06/2025,,Application,Customer cant activate car in Chery app (error A07913),"0708: 等待客户重新绑定 +0702: 已从TSP后台删除数据，请建议客户重新绑定. +0701: 预计7月2号从TSP平台删除数据解决 +0627： +转 app 分析(和TR635一样问题）","0708：Waiting for customers to rebind -> Success, closed +0702: The data has been deleted from the TSP backend. Please advise the customer to try to rebind.@Kostya +0701: It is expected that the data will be deleted from the TSP platform on July 2nd for resolution +0627： +app analysis (same issue as TR635)",Low,close,用户EXEED-APP(User),岳晓磊,08/07/2025,CHERY TIGGO 9 (T28)）,LVTDD24B0RG094557,,TGR0002297,image.png,Kostya,,,,,,11 +TR659,Telegram bot,27/06/2025,,Network,"No network available after purchasing an annual services package on July, 2nd. Simba has re-enabled apn2 but not active in MNO - see screenshot attached. Apn1 is available and active only. +7 月 2 日购买年度服务套餐后无网络可用。 Simba 已重新启用 apn2，但未在 MNO 中激活 - 请参阅所附截图。 只有 Apn1 可用且处于激活状态。","0710: 等待客户验证是否恢复 +0707：TSP后台重启t-box +0702：短期方案：建议客户重新启动车辆激活网络","14/07: no feedback so far. Temprary closed. +10/07: repeat request sent to customer. Wait for reply. +0710： waiting for customer check if the betwork recovery +0707: on TSP reboot t-box +0702：pls advice customer turn off the vehicle for 3-5 minutes, then power it on again to active APN02",Low,temporary close,MNO,Vsevolod Tsoi,14/07/2025,EXEED VX FL（M36T）,LVTDD24B7PD621217,,TGR0002429,,Vsevolod Tsoi,,,,,,17 +TR660,Telegram bot,03/07/2025,,Network,"No network available, But on Simba and mno platform traffic exist",,Fixied by itself,Low,close,,,03/07/2025,EXEED VX FL（M36T）,LVTDD24B3RD662639,,TGR0002468,image.png,Kostya,,,,,,0 +TR666,Mail,03/07/2025,,Application,"Customer was kicked out of app. Customer doesn't find anymore his car added and bound in the app. An error message ""A07913"" comes up when trying to bind - see photo attached. But car is added in the growing admin app and bound in TSP. +客户被踢出应用程序。 客户在app中也找不到已添加和绑定的汽车。 尝试绑定时出现错误信息 ""A07913""--见附图。 但车已添加中，并在 TSP 中绑定。","0730：删除数据后，客户反馈绑定成功，可关闭改问题 +0730：核实为APP自身问题，未把用户数据同步给TSP系统导致，目前会采用临时手段：数据库上清除异常数据，维持业务稳定； +长期措施：APP与APP后台优化代码，增加校验逻辑及其他预防措施我，根本上解决问题。临时方式周五前反馈结果 +0729：会后协调信息公司讨论解决方式 +0728：等待国内二线反馈进展 +16/07：根据岳晓磊的邮件反馈，等待供应商数跑工程师对 CW29 的解决方案 +0708：TSP查看车辆已绑定，星途APP查看绑定关系存在，转国内分析","30/07: customer's feedback - car is bound again and remote control is restored. Issue solved out. +30/07: request has been sent to customer to bind his car in the app. Wait for feedback whether the issue is solved out. +30/07: Verified as APP own problem, not synchronised user data to the TSP system, currently will use temporary means: database to remove abnormal data, to maintain business stability; Interim approach to feedback results by Friday +Long-term measures: APP and APP background optimisation code, increase the checking logic and other preventive measures I, fundamentally solve the problem +29/07: Coordinate with the information company after the meeting to discuss the solution. +28/07: wait for feedback from 2nd line. +16/07: wait for solution from supplier Supaur engineer on CW29 according to feedback by email from 岳晓磊 +0708：vehicle bound in the TSP platform，",Low,close,用户EXEED-APP(User),岳晓磊,30/07/2025,EXEED RX（T22）,XEYDD24B3RA008663,,,"4.jpg,3.jpg",Vsevolod Tsoi,,,,,,27 +TR667,Mail,04/07/2025,,Application,"Something went wrong with app: customer can't see any more his car added and bound in the app. However, the vehicle is bound in TSP. A message to rebind the car comes up when trying to add the vehicle in the app - see photo attached. Customer did some actions such as log out of app and then re-install it => It did not bring any result in the end. Customer phone number - +7 (903) 258-76-09 +应用程序出了问题：客户无法在应用程序中看到已添加和绑定的车辆。 但是，车辆已在 TSP 中绑定。 当尝试在应用程序中添加车辆时，会出现一条重新绑定车辆的信息--见附图。 客户做了一些操作，如注销应用程序然后重新安装 => 但最终没有任何结果。 客户电话号码 - +7 (903) 258-76-09","1024:已修复app相关错误数据，请告知用户重试，如验证通过可关闭该问题 +1023: 已与 Andrey 交谈过。我们将发送一封升级邮件，以跟进问题的解决。 +1021：Andey 将于周三结束休假返回。这个问题将上报。 +1020：暂无更新 +1017：已联系数跑，反馈周五提供进展 +1014：如果本周信息公司没有反馈，则需要升级。 +0926: 已确认修复方案，待开发完成 +0923：会后与供应商对齐 +0917: APP后台9月3号有通过一个换绑申请，但是认证手机号码依然是之前的，另外TSP平台是未绑定的状态，待信息公司处理，预计本周五跟信息公司会议后同步信息 +0916：跟信息公司反馈再次沟通 +0901: 用户反馈9 月 1 日尝试后无变化。 +0825：建议告知用户重新尝试，已删除临时数据， +0814：客户再次尝试在应用程序中绑定他的汽车，但未成功。错误信息 ""A07913 ""仍然出现。 +0812：信息公司反馈，周三可解决该问题 +0808: 用户反馈 - 尝试绑定汽车时出现错误信息，状态相同 +0805：已同步app开发，反馈需等待APP修改后可解决，如用户抱怨可按临时方法解决 +0731：重新绑定请求得到确认，用户可以在应用程序中看到自己的车辆，但无法绑定--出现错误信息 “A07913”--见附图。 +0731：要求用户提出重新绑定请求。等待请求确认。 +0730：用户可使用新账号绑定，触发换绑申请，APP后台审核，审核通过后，用户可重新绑定 +0729:反馈现在客户无法绑定，无法申请解绑 +0722: 建议用户先申请解绑，等待解绑申请审核通过后，然后用户再重新绑定 +0708: tsp平台存在绑定关系，星途APP存在绑定关系但是车主账号已注销","24/10: car finally bound, remote control restored. +24/10:App related error data has been fixed, please inform the user to retry, if the validation passes you can close the issue. +23/10: talked to Andrey. En escalation email is gonna be sent to follow up the resolving of the issue. +21/10: Andey is back on Wednesday from vacation. This issue will be escalated. +20/10:No updates at this time +14/10: if no feedback this week from information company, escalation would be required. +25/09：is currently being processed by information company +22/09: feedback from the information company is still pending. +18/09: still wait for temporary solution. +15/09: temporary solution is pending. +11/09: wait for temporary solution (deleting of abnormal data) from information company. +02/09: no change after attempt done on September, 1st. +25/08: It was recommended that the user be advised to retry, and that the temporary data had been deleted. +14/08: after customer's repeat attempt to try binding his car in the app - not successful. Error message ""A07913"" still comes up. +12/08：Feedback from the information company that the issue could be resolved on Wednesday +08/08: user's feedback - same status with error message coming up upon trying to bind the car +07/08: user confirmed that the issue is still valid. +05/08:Have synchronised app development, feedback need to wait for app modification can be solved, if users complain can be solved by temporary method +31/07: the rebinding request was confirmed, user could see his vehicle in the app but was not able to bind - an error message ""A07913"" came up - see photo attached. +31/07: user was asked to make a request for rebinding. Wait for request in order to confirm it. +30/07: Users can use the new account binding, triggering the application to change the binding, APP background audit, after passing the audit, the user can re-binding +29/07: Feedback now customers can't bind and can't apply for unbinding +22/07：It is recommended that the user first apply for unbinding, wait for the unbinding application to be approved, and then the user will be re-bound. @Vsevolod Tsoi +16/07: wait for solution from supplier Supaur engineer on CW29 according to feedback by email from 岳晓磊 +08/07: tsp platform binding relationship exists, starway app binding relationship exists but owner account has been cancelled",Low,close,用户EXEED-APP(User),岳晓磊,24/10/2025,EXEED RX（T22）,LVTDD24B5RG032670,,,"Binging_issue.jpeg,Picture_2.jpg,Picture_3.jpg,Picture_1.jpg",Vsevolod Tsoi,,,,,,112 +TR674,Telegram bot,08/07/2025,,Application,"No update of vehicle status is possible in the app. An error message ""A00362"" comes up when trying to update - see photo attached. TSP: tbox log in is normal as well as high frequency data transfer. MNO: apn1&2 are normal +应用程序无法更新车辆状态。 尝试更新时会出现错误信息 ""A00362""，请参阅所附照片。 TSP：Tbox 登录正常，高频数据传输也正常。 MNO：APN1 和 2 正常","0902:建议联系用户确认是否已解决，如未解决请复现操作。方便问题排查 +0825：已修复异常数据，建议用户重新尝试 +0819：已催促数跑团队提供短期解决及长期解决方案，核实为APP后台数据配置异常，已与TSP后台校对异常数据，预计解决时间待定。 +0814: 客户反馈 - 问题尚未解决。在应用程序中更新车辆数据时，仍会出现错误信息 A00362。 +0812：信息公司反馈，周三可解决该问题 +0808: 用户反馈 - 尝试绑定汽车时出现错误信息，状态相同 +0730：核实为APP自身问题，未把用户数据同步给TSP系统导致 +长期措施：APP与APP后台优化代码，增加校验逻辑及其他预防措施，根本上解决问题。临时方式周五前反馈结果 +0729：会后协调信息公司讨论解决方式 +0716：根据岳晓磊邮件反馈，CW29等待供应商Supaur工程师解决 +0708：A00362错误代码提示APP用户在TSP平台不存在，APP端提供以下用户信息岳晓磊","02/09: user's feedback - remote car control with mob app is restored. TR is closed. +02/09: user is asked to check the mob app operation as well as reflecting of actual car data. +02/09:It is recommended to contact the user to confirm whether the issue has been resolved, if not, please reproduce the operation. Convenient for troubleshooting +25/08：Abnormal data has been fixed, users are advised to try again +19/08: We have urged the number of running team to provide short-term solutions and long-term solutions, verified as APP background data configuration anomalies, and have proofread the anomalous data with the TSP backstage, the expected solution time is to be determined. +14/08: customer's feedback - the issue is not sorted out. An error message A00362 is still coming up when updating vehicle data in the app. +12/08: Feedback from info company, issue could be resolved on Wednesday +08/08: User feedback - error message when trying to bind car, same status +30/07: verified as APP own problem, not synchronised user data to the TSP system. +Long-term measures: APP and APP background optimisation code, increase the checking logic and other preventive measures I, fundamentally solve the problem +29/07: Coordinate with the information company after the meeting to discuss the solution. +16/07: wait for solution from supplier Supaur engineer on CW29 according to feedback by email from 岳晓磊 +08/07：A00362 error code indicates that the APP user does not exist in the TSP platform, the APP side provides the following user information@岳晓磊",Low,close,用户EXEED-APP(User),岳晓磊,02/09/2025,CHERY TIGGO 9 (T28)）,LVTDD24B2RG092213,,TGR0002236,file_3179.jpg,Vsevolod Tsoi,,,,,,56 +TR675,Mail,08/07/2025,,Application,"User can't control remotely his vehicle with app: buttons are not active and vehicle data is not displayed - see sceenshots attached. +用户无法通过应用程序远程控制其车辆：按钮未激活且车辆数据未显示 - 请见所附截图","0804: 修复了应用程序中按钮未激活的问题。按钮已激活，遥控器操作已恢复 => 已修复。 +0731:暂无用户反馈 +0730：已临时删除异常数据，可建议用户重新尝试。 +0730：核实为APP自身问题，未把用户数据同步给TSP系统导致，目前会采用临时手段：数据库上清除异常数据，维持业务稳定； +长期措施：APP与APP后台优化代码，增加校验逻辑及其他预防措施，根本上解决问题。临时方式周五前反馈结果 +0729：会后协调信息公司讨论解决方式 +0724: 用户不一致的问题, 需要把用户注销打通，等信息公司处理 +0722:建议客户提供下他的账号和密码和app版本 +0709:转国内APP分析 +0709：APP分析中，OQ CHERY需信息公司协调数跑看下，TSP后台近三天没搜索到查车况日志，需要APP后台看下。@岳晓磊","04/08: issue with non active buttons in the app is fixed. Buttons are active now and remote control operation is restored => fixed. +31/07: no feedback so far. +30/07: user was asked to provide a feedback whether inactive buttons in the app were restored. +30/07: Verified as APP own problem, not synchronised user data to the TSP system, currently will use temporary means: database to remove abnormal data, to maintain business stability; Interim approach to feedback results by Friday +Long-term measures: APP and APP background optimisation code, increase the checking logic and other preventive measures I, fundamentally solve the problem +29/07: Coordinate with the information company after the meeting to discuss the solution. +28/07: no providing of password as well as login is possible. Please find another way to do a troubleshouting. See photo attached to see app version +0722: It is suggested that the customer provide his account and password. need to log in to his account to retrieve the app logs for analysis.，also pls help check the app veision information@Vsevolod Tsoi +0709:TSP background in the last three days did not search to check the car condition log, need APP background to see, waiting for information company to check ",Low,close,用户EXEED-APP(User),岳晓磊,04/08/2025,CHERY TIGGO 9 (T28)）,LVTDD24B6RG104153,,TGR0002209,"App_version.jpg,IMG-20250709-WA0007.jpg,IMG-20250709-WA0006.jpg",Vsevolod Tsoi,,,,,,27 +TR679,Mail,09/07/2025,,Remote control ,"Remote conrol doesn't work. User was able to enter in member center but none of the apps work - see video attached. A notice ""Wrong VIN number""came up - see photo attached. TSP: no IHU log in since binding the vehicle in TSP. MNO: apn1&2 are normal. +远控无法工作。用户能够进入会员中心，但应用程序都无法运行-见视频附件。 +出现“错误的VIN号码”的通知-见附件照片。 +TSP：自将车辆绑定到TSP后，没有IHU登录。MNO: apn1&2正常。","0819:建议切换成等待数据，用户进站后再切换状态 +0814：暂无DMC日志 +0812：暂无DMC日志 +0807：正在申请 DMC 日志。 +0805：请提供DMC日志 +0804：等待属地APP团队车控日志分析结果，DMC version 00.04.00 ， +0801：暂无DMC版本提供，车控日志已由属地人员提供给OJ，请@Vadim分析车控日志 +0729：已要求前方提供DMC软件版本，针对OJ车控请咨询Vadim +0728: 要求提供以下信息的申请正在进行中。 +0725: +1、确认APP是否下发过远控指令？ (反馈给 O&J 远程组，等待回复） +2. 请帮助确认 DMC 的版本信息并提供 DMC 日志 +0723：T-BOX日志已发专业分析 +0710: 建议客户进站抓取T-BOX和DMC日志，和抓取BDCAN报文，报文抓取视频已发群里 +0709: t-box登录记录正常，无远控记录,无HU登录记录。转国内DMC分析","23/10: tempory closed. Will be re-opened upon receiving the data. +21/10: no feedback so far. +16/10: the same status +14/10: DMC log still pending. +09/10: no DMC so far. +25/09: no DMC log received yet. +22/09: DMC log still pending. +18/09: data pending. +16/09: no feedback so far. +11/09: data is pending. +02/09: no feedback so far. +19/08：It is recommended to switch to wait for data and switch the state after the user enters the station +14/08: no log received so far. +12/08: DMC log pending. +07/08: request for DMC log is on process. +05/08：Please provide DMC logs. +04/08: DMC SW versions is attached - see photo. +01/08：No DMC version is available at the moment, the vehicle control log has been provided to OJ by the territorial staff, and Vadim is requested to analyse the vehicle control log. +29/07: DMC software version has been requested from the front, please consult Vadim for OJ car control. +28/07: request for providing the information below is in progress. +24/07：pls help check following information：@Vsevolod Tsoi +1、Has the APP issued any remote control instructions? (Feedback to O&J telematic group, awaiting reply) +2. Please help confirm the version information of the DMC and provide the DMC log +23/07: T-BOX logs sent for professional analysis +16/07: wait for password for entering into engineering mode. +14/07: request for DMC and TBOX logs is ongoing. +10/07：pls invite customer go to dealer to capture the T-BOX and DMC logs, as well as the BDCAN messages. The video of the message capture has been sent to the group of TR679. @Vsevolod Tsoi +09/07：The t-box login record is normal. There is no remote control record and no HU login record. turn to domestic DMC analysis",Low,temporary close,DMC,孙松,23/10/2025,OMODA C7 (T1GC),LVUGFB226SD831242,,,"DMC_SW_version.jpeg,LOG_LVUGFB226SD83124220250722101119.tar,WhatsApp Video 2025-07-03 at 10.14.11.mp4,WhatsApp Image 2025-07-03 at 10.05.58.jpeg,C7.jpg",Vsevolod Tsoi,,,,,,106 +TR680,Telegram bot,09/07/2025,,Activation SIM,"Customer cant activate car in the app with his account(Error A00362) Tested on other profiles - everything works +客户无法使用其账户在应用程序中激活汽车（错误 A00362） 在其他配置上进行了测试 - 一切正常","0819：已催促数跑团队提供短期解决及长期解决方案，核实为APP后台数据配置异常，已与TSP后台校对异常数据，预计解决时间待定。 +0814: 等待客户反馈 +0812：信息公司反馈，周三可解决该问题 +0808: 用户反馈 - 尝试绑定汽车时出现错误信息，状态相同 +0730：核实为APP自身问题，未把用户数据同步给TSP系统导致。 +长期措施：APP与APP后台优化代码，增加校验逻辑及其他预防措施，根本上解决问题。临时方式周五前反馈结果 +0729：会后协调信息公司讨论解决方式 +0710: TSP显示车主未绑定，客户7月9日申请通过过解绑，7月10日重新认证已通过。登录app报错A00362，转国内app分析","26/08: customer said that now it works-solved +21/08: please check another screenshots in attachement +19/08: We have urged the number of running team to provide short-term solutions and long-term solutions, verified as APP background data configuration anomalies, and have proofread the anomalous data with the TSP backstage, the expected solution time is to be determined. +14/08: waiting for customer feedback +12/08: Feedback from info company, issue could be resolved on Wednesday +08/08: User feedback - error message when trying to bind car, same status +30/07: Verified as APP own problem, not synchronised user data to the TSP system. +29/07: Coordinate with the information company after the meeting to discuss the solution. +10/07:TSP shows that the owner is not bound, the customer applied for unbinding on 9 July, and the re-authentication was passed on 10 July. Logging into the app reported error A00362, transferred to domestic app analysis",Low,close,用户EXEED-APP(User),岳晓磊,26/08/2025,CHERY TIGGO 9 (T28)）,LVTDD24B2RG122018,,TGR0002030,"1000026944.jpg,1000026945.jpg,1000026946.jpg,image.png",Kostya,,,,,,48 +TR681,Mail,09/07/2025,,Missing in admin platform,"No vehicle data available in the Chery International Intelligent Marketing Platform - see photo attached +奇瑞国际智能营销平台没有车辆数据，见附图",0710: 转国内app分析,14/07: one more VIN is added.,Low,close,用户EXEED-APP(User),岳晓磊,23/07/2025,CHERY TIGGO 9 (T28)）,"LVTDD24B7RG120393 +LVTDD24B2RG120429 +LVTDD24B2RG129485",,"LVTDD24B7RG120393 - 164302110300450; +LVTDD24B2RG120429 - 164302110751735.",Missing_vehicle_data.JPG,Vsevolod Tsoi,,,,,,14 +TR684,Mail,11/07/2025,,Navi,"Navi doesn't work as well as Weather app. Vehicle is well bound in TSP. MNO is OK. +导航和天气app无法使用。 车辆在 TSP 中绑定良好。 移动网络连接正常","0902：已要求客户提供反馈，暂无 反馈 +0820:反馈8月19日DMC已是最新版本，请与用户尽快核实是否已可用导航及天气 +0812: 在 FOTA 中检查过 - 版本仍然是旧的 19.80。仍在等待经销商用 USB 升级 DMC SW。 +0807：暂无升级反馈 +0804：由于 DMC 版本错误，ugrade 失败 one 02.01.00_01.19.80""。因此，已向经销商发出请求，要求将 DMC 升级到最新版本。 +0728：OTA已下载，但仍未升级 +0725：OTA已下载，等待升级 +0724: 主机版本02.00.00， 已加到OTA列表推送升级DMC +0711：转国内DMC分析（HU ID为32位完整编码）","04/09: customer's feedback - Navi&Weater are restored. Issue solved. +02/09: request to provide a feedback is made. +20/08:Feedback on 19 August DMC is now the latest version, please check with the user as soon as possible to see if the navigation and weather are available! +14/08: pending +12/08: checked out in FOTA - version is still old one 19.80. Still wait for DMC SW upgrade at dealer with USB. +07/08: feedback on upgrade is pending +04/08: ugrade failed due to DMC version is wrong one 02.01.00_01.19.80"". Therefore, a request has been sent to dealer for DMC upgrade to the latest version. +31/07: still the same status. +28/07: downloaded but still not upgraded. +25/07: OTA upgrade is downloaded. Wait for upgrade. +0724: DMC version 02.00.00. Please upgrade DMC via OTA +21/07: DMC SW version photo is attached. Still wait for Navi and Weather versions. Customer is currenty on vacation. +16/07: reminder for collecting DMC log was sent out. +14/07: DMC log was already requested as well as Navi and Weather SW version. Wait for feedback. +0711：Please help confirm the DMC version number, as well as the version numbers of navigation and weather + Please also help request the DMC logs @Vsevolod Tsoi",Low,close,OTA,韦正辉,04/09/2025,EXEED RX（T22）,XEYDD14B3RA004348,,,"DMC_SW_version.JPG,Navi&Weather.JPG",Vsevolod Tsoi,,,,,,55 +TR685,Telegram bot,14/07/2025,,PKI problem,"Navi doesn't work. Vehicle is well bound in TSP. MNO is OK. +导航不工作。 车辆在 TSP 中绑定良好。 MNO 正常。","0916：等待客户反馈 +0902：等待用户升级 +0820:8月起无主机登录记录，建议让用户，重启车辆后，点击OTA升级 +0814：等待OTA +0807: 等待OTA +0729：等待OTA +0722：等待OTA +0715：等待数据 +0714：导航无法工作，转国内生态分析（TSP平台为完整HU SN，未修改过）","23/09 Closed -> Feedback timeout +16/09:Waiting for update from customer +02/09:Waiting for update from customer +20/08:No host login record from August, suggest to let the user, after restarting the vehicle, click on OTA upgrade +14/08: still waiting OTA +07/08: still waiting +29/07: waiting for data +22/07: waiting for data +15/07：waiting for data +14/07：Please help confirm the DMC version number, as well as the version numbers of navigation + Please also help request the DMC logs and screenshot @Kostya",Low,close,OTA,韦正辉,23/09/2025,EXEED RX（T22）,LVTDD24BXRG031448,,TGR0002626,"image.png,image.png,image.png",Kostya,,,,,,71 +TR686,Telegram bot,14/07/2025,,PKI problem,"Navi doesn't work. Vehicle is well bound in TSP. MNO is OK +导航不工作。 车辆在 TSP 中绑定良好。 MNO 正常。","0820:见主机登录记录正常，建议与用户核实是否问题已解决 +0814：等待OTA +0807：等待OTA +0729：等待OTA +0717：等待版本信息及日志上传，建议也添加到OTA清单中 +0714：导航无法工作，转国内生态分析（TSP平台为完整HU SN，未修改过）","20/08:See host login records are normal, suggest checking with user if problem is resolved +14/08: still waiting OTA +07/08: still waiting +29/07：waiting for OTA +17/07:All data requested, waiting for versions and logs +14/07:Please help confirm the DMC version number, as well as the version numbers of navigation and weather + Please also help request the DMC logs @Kostya",Low,close,OTA,韦正辉,02/09/2025,EXEED RX（T22）,LVTDD24B8RG049673,,TGR0002619,image.png,Kostya,,,,,,50 +TR687,Telegram bot,14/07/2025,,PKI problem,"Navi doesn't work. Vehicle is well bound in TSP. MNO is OK +导航不工作。 车辆在 TSP 中绑定良好。 MNO 正常","0820:见主机登录记录正常，建议与用户核实是否问题已解决 +0814：等待OTA +0807：等待OTA +0714: 转国内生态分析（TSP平台为完整HU SN，未修改过）","20/08:See host login records are normal, suggest checking with user if problem is resolved +14/08: still waiting OTA +07/08: still waiting +14/07: Please help confirm the DMC version number, as well as the version numbers of navigation and weather + Please also help request the DMC logs @Kostya",Low,close,OTA,韦正辉,02/09/2025,EXEED RX（T22）,LVTDD24B3RG014216,,TGR0002615,image.png,Kostya,,,,,,50 +TR688,Telegram bot,14/07/2025,,Application,"After turning on climate temperature always shows 0 degrees. (see screenshot) +打开温度调节功能后，温度始终显示为 0 度（见截图）","0811：问题解决，已关闭 +0807：请与用户确认是否已解决，如解决可关闭 +0730：已临时删除异常数据，建议用户重新绑定尝试 +0730：核实为APP自身问题，未把用户数据同步给TSP系统导致，目前会采用临时手段：数据库上清除异常数据，维持业务稳定； +长期措施：APP与APP后台优化代码，增加校验逻辑及其他预防措施，根本上解决问题。临时方式周五前反馈结果 +0729：会后协调信息公司讨论解决方式 +0728：等待信息公司处理 +0724: app User Id和tsp平台已有的不一致，登录校验不通过，需要数跑公司将用户注销打通 +0714：转国内APP分析","11/08: problem solved +07/08: Please confirm with the user whether it has been resolved, if resolved can be closed +30/07：this can be suggested to the user to try again, has been deleted the abnormal data, please users to re-bind the vehicle! +30/07: Verified as APP own problem, not synchronised user data to the TSP system, currently will use temporary means: database to remove abnormal data, to maintain business stability; Interim approach to feedback results by Friday +Long-term measures: APP and APP background optimisation code, increase the checking logic and other preventive measures I, fundamentally solve the problem +29/07: Coordinate with the information company after the meeting to discuss the solution. +28/07: Waiting for information companies to process +24/07：The app User ID does not match the existing one on the tsp platform, the login verification fails, and the information company needs to cancel the user +14/07：Transnational APP Analysis",Low,close,用户EXEED-APP(User),岳晓磊,11/08/2025,CHERY TIGGO 9 (T28)）,LVTDD24B6RG131871,,,"image.png,image.png",Evgeniy Ermishin,,,,,,28 +TR689,Mail,14/07/2025,,PKI problem,"Navi doesn't work. Vehicle is well bound in TSP. MNO is OK. +导航不工作。 车辆在 TSP 中绑定良好。 MNO 正常。","0725: 已下载更新包，但未安装 +0715:等待版本信息和日志（TSP平台为完整HU SN，未修改过）","25/07：downloaded. but not installed +0715:Please help confirm the DMC version number, as well as the version numbers of navigation and weather + Please also help request the DMC logs @Evgeniy Ermishin",Low,close,OTA,韦正辉,30/07/2025,EXEED RX（T22）,LVTDD24BXRG033863,,,image.png,Evgeniy Ermishin,,,,,,16 +TR690,Telegram bot,14/07/2025,,Network,"No network, No TBOX login, No veh. data in TSP. +Car in hibernation mode. Manual start via button didn't help +无网络，无 TBOX 登录，TSP 中没有登录数据。 +汽车处于休眠模式。 通过按钮手动启动也无济于事","1021:14天无反馈转暂时关闭 +0826：协商一致，转等待数据 +0819：无T-BOX登录记录，等待用户进站 +0814：无T-BOX登录记录，等待用户进站 +0812：无T-BOX登录记录，等待用户进站 +0807: 用户尚未到站，正在等待日志 +0805：暂无日志反馈 +0731：暂无日志反馈 +0728：用户暂未进站，等待日志 +0715：车机最后登录记录时间2025-05-21，无T-BOX登录记录，sim卡状态正常，车辆进入深度睡眠，无法从TSP获取T-BOX日志。建议客户进站抓取DMC和T-BOX日志","21/10:14 days no feedback to temporary closure +26/08: Consensus to wait for data +19/08: No T-BOX login record, waiting for user to enter the station +14/08: No T-BOX login record, waiting for user to enter the station +12/08：No T-BOX login record, waiting for users to enter the station. +07/08: User not in station yet, waiting for logs +05/08: User not in station yet, waiting for logs +31/07: User not in station yet, waiting for logs +28/07: User not in station yet, waiting for logs +15/07: pls help invite customer to go to dealer to capture T-BOX and DMC logs. @Kostya +Vehicle last login record time 2025-05-21, no T-BOX login record, sim card status is normal, vehicle enters deep sleep, unable to get T-BOX log from TSP, ",Low,temporary close,TBOX,董雪超,21/10/2025,EXEED RX（T22）,LVTDD24B0RG009913,,TGR0002292,,Kostya,,,,,,99 +TR691,Mail,14/07/2025,,PKI problem,"Navi app doesn't work. Sim car is activated. Vehicle is bount in TSP. All other apps work well. +导航无法工作，sim卡已激活，车辆已绑定TSP，其他app正常","0728: 导航应用程序已恢复。问题已解决。 +0724：DMC SW 已于 7 月 23 日通过 OTA 升级。已询问客户导航是否已恢复。 +0722：等待DMC日志中。 +0716：等待反馈。 +0715：已向 ASD 团队发出 DMC 日志请求。等待数据。 +0715：等待DMC和导航版本 （TSP平台为完整HU SN，未修改过）","28/07: navi app is restored. Issue solved. +28/07: repeat request wether Navi app is restored sent to customer. Wait for feedback +24/07: DMC SW has been upgraded via OTA on July, 23th. Therefore, customer was asked if Navi app was restored. +22/07: still waiting for data. +16/07: wait for feedback. +15/07: request for DMC log has been sent out to ASD team. Wait for data. +15/07: DMC SW version is provided as well as Navi app - see photo attached. +14/07: DMC and Navi versions are requested. DMC log is in process of requesting.",Low,close,OTA,韦正辉,28/07/2025,EXEED RX（T22）,LVTDD24B3RG049032,,,"Navi_app_version.jpg,DMC_SW_version.jpg,PKI_status.JPG,Navi_start_issue.JPG",Vsevolod Tsoi,,,,,,14 +TR693,Mail,14/07/2025,,PKI problem,"Navi app doesn't work. Sim car is activated. Vehicle is bount in TSP. All other apps work well. +导航无法工作，sim卡已激活，车辆已绑定TSP，其他app正常",0715：等待版本信息和日志 （TSP平台为完整HU SN，未修改过）,"25/07: customer's feedback - Navi app is restored. Issue solved out => TR closed. +25/07: OTA upgrade completed successfully. Wait for customer's feedaback wether Navi app was restored. +24/07: OTA upgrade is downloaded. Wait for update. +15/07: DMC log is requested. DMC, Navi and Weather versions - see photo attached. +0715:Please help confirm the DMC version number, as well as the version numbers of navigation and weather + Please also help request the DMC logs @Vsevolod Tsoi",Low,close,OTA,韦正辉,25/07/2025,EXEED RX（T22）,LVTDD24B4RG049668,,,"Navi_SW_version.jpg,Weather_SW_version.jpg,DMC_SW_version.jpg,PKI_issue.JPG,image-14-07-25-04-22.jpg",Vsevolod Tsoi,,,,,,11 +TR695,Mail,15/07/2025,,PKI problem,"Navi doesn't work. Vehicle is well bound in TSP. MNO is OK +导航不工作。 车辆在 TSP 中绑定良好。 MNO 正常","0811: 升级成功，问题已解决 +0729：等待OTA +0715：等待版本和日志信息 ","11/08: updated successfully, solved! +29/07:Suggest users OTA upgrade, after the upgrade to confirm whether the solution can be recovered + 0715:Please help confirm the DMC version number, as well as the version numbers of navigation and weather + Please also help request the DMC logs @Evgeniy Ermishin",Low,close,OTA,韦正辉,11/08/2025,EXEED RX（T22）,LVTDD24B6RG024500,,,"{4E80621C-2B66-42D4-83CE-D85176C4A2E8}.png,17525182443820714_194003.mp4",Evgeniy Ermishin,,,,,,27 +TR697,,15/07/2025,,Navi,"There is impossible to create route in Navi - see attached video +无法在 导航中创建路线 - 请参阅所附视频","0722: 前方验证把车移到其他地方后有已恢复，关闭该问题 +0722：地库的GPS信号不好，建议把车移到不同的地方尝试下 +0716: +1、在导航无法生成路线，因为车辆行驶到地库内，导航内部定位丢失了无法生成路线 +2、无法在地图上选择目的地：该功能目前在规划中，预计下半年进行，目前不支持使用 +0716：导航无法生成路线，有多个客户反馈此问题，附件视频和日志是在试验车进行测试获取的","0722：The GPS signal in the garage is not good, so it is suggested moving the car to a different place to try it out @Evgeniy Ermishin +0716: +1. NAVI fails to generate a route: As the vehicle enters the underground garage, the internal positioning of the navigation system is lost, making it impossible to generate a route +2. Inability to select destinations on the map: This feature is currently in the planning stage and is expected to be implemented in the second half of the year. It is not supported for use at present @Evgeniy Ermishin +15/07: operation time 15/07 at 16:02",Low,close,生态/ecologically,袁清,22/07/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ5SD094857,,,"2025_07_15_16_14_07.zip,IMG_6949.MOV,IMG_6948.MOV,5454210687980142662.jpg,5454210687980142661.jpg",Evgeniy Ermishin,,,,,,7 +TR698,Telegram bot,15/07/2025,,PKI problem,"Navi app doesn't work. Sim car is activated. Vehicle is bount in TSP. All other apps work well. +导航无法工作，sim卡已激活，车辆在TSP已绑定，其他app正常，车辆激活时间：2025-06-09","0820:见主机登录记录正常，建议与用户核实是否问题已解决 +0814：等待OTA +0807：等待OTA +0728：建议用户OTA升级，升级后确认是否可以恢复解决 +0716: 车辆激活时间：2025-06-09，TSP 平台查询IHU软件版本号:02.00.00，请属地确认版本信息","20/08:See host login records are normal, suggest checking with user if problem is resolved +14/08: still waiting OTA +07/08: still waiting +28/07:Suggest users OTA upgrade, after the upgrade to confirm whether the solution can be recovered +16/07：The version number of the IHU software can be queried on the TSP platform :02.00.00. pls help confirm the DMC version with customer @Kostya",Low,close,OTA,韦正辉,02/09/2025,EXEED RX（T22）,LVTDD24B6RG024500,,TGR0002652,image.png,Kostya,,,,,,49 +TR699,Mail,16/07/2025,,Problem with auth in member center,No entering in member center possible. An error message E00011 comes up when entering - see photo attached.,"0716: 修改回完成HU SN后问题解决 +0716: IHU登录失败原因：请求参数错误：参数hu SN与TSP hu SN不匹配。请先更换完整的HU SN，然后重新启动车机，确认是否恢复。","16/07: IHU ID has been changed. Promlem is sorted out. +0716: IHU login failed Cause: request parameter error: parameter hu SN does not match TSP hu SN. Please change the full HU SN first and reboot the IHU to verify whether it is restored or not. @Vsevolod Tsoi",Low,close,DMC,Vsevolod Tsoi,16/07/2025,EXEED RX（T22）,LVTDD24B2RG021836,,,Issue_entering_member_center.jpg,Vsevolod Tsoi,,,,,,0 +TR700,Telegram bot,16/07/2025,,PKI problem,"Navi app doesn't work. Sim car is activated. Vehicle is bound in TSP. All other apps work well. +导航无法工作，sim卡已激活，车辆在TSP已绑定，其他app正常，","0916：等待客户反馈 +0902：等待用户升级 +0820:见主机登录记录正常，建议与用户核实是否问题已解决 +0814：等待OTA +0728：建议用户OTA升级，升级后确认是否可以恢复解决 +0724: 请向客户确认Navi的定位权限是否开启，如果是开启的状态但是导航仍然不可用请邀请客户进站抓取DMC日志 +0723: dmc ver = 02.02.00_01.37.33 navi ver = 1.0.0.0 +0717:请属地确认版本信息","23/09: Closed -> customer feedback +16/09:Waiting for update from customer +02/09:Waiting for update from customer +20/08:See host login records are normal, suggest checking with user if problem is resolved +14/08: still waiting OTA +28/07：Suggest users OTA upgrade, after the upgrade to confirm whether the solution can be recovered +24/07: Please confirm with the customer whether the Navi location permission is enabled. If it is enabled but the navigation is still unavailable, please invite the customer go to dealer to capture the DMC logs @Kostya +23/07: +dmc ver = 02.02.00_01.37.33 +navi ver = 1.0.0.0 +17/07: information requested +17/07: Please help confirm the version information",Low,close,OTA,韦正辉,23/09/2025,EXEED RX（T22）,LVTDD24B5RG032135,,TGR0002640,Navi_version.jpg,Kostya,,,,,,69 +TR703,Telegram bot,16/07/2025,,Application,"Car doesn't exist in chery admin. We dont have permissions to add this car in platform please provide permissions for our account or another account or add it by yourself +奇瑞app中不存在车辆。 我们没有在平台中添加此车的权限，请为我们的账户或其他账户提供权限，或自行添加。","0723: 车辆已加入到奇瑞app后台，请告知客户绑定车辆 +0716:转国内app","0723：LVTDD24B2RG121936 have been added to the backend of the Chery app, please help invite customers to bind vehicle",Medium,close,用户EXEED-APP(User),岳晓磊,23/07/2025,CHERY TIGGO 9 (T28)）,"LVTDD24B2RG121936 +Ando many other cars",,TGR0002620 and many other,,Kostya,,,,,,7 +TR704,,16/07/2025,,PKI problem,"Navi doesn't start. +导航无法工作","0807：无反馈暂时关闭 +0804: 仍未收到反馈。 +0731：至今无回复。 +0728：DMC OTA 升级已于 7 月 26 日完成。等待客户反馈 Navi 应用程序是否恢复。 +0725: 已下载 OTA 升级包。等待升级。 +0724：通过 OTA 升级 DMC +0722：已发送提醒。 +0717：等待版本信息 +0716：要求提供 DMC SW 版本和 Navi。","07/08: closed temporarily. +04/08: feedback is still pending. +31/07: no reply so far. +28/07: DMC OTA upgrade completed on July, 26th. Wait for customer's feedback if Navi app was restored. +25/07: OTA upgrade package downloaded. Wait for update. +24/07：upgrade DMC by OTA +22/07: reminder has been sent. +16/07: DMC SW version as well as Navi are requested.",Low,temporary close,OTA,韦正辉,07/08/2025,EXEED RX（T22）,LVTDD24B0RG013735,,,,Vsevolod Tsoi,,,,,,22 +TR705,,17/07/2025,,Problem with auth in member center,"No possibility to enter into member center due to missing of QR code. A notice ""Poor network"" comes up when trying to enter with QR code. All apps work in IHU. +由于缺少二维码，无法进入会员中心。 尝试使用二维码进入时，会出现 ""网络不佳 ""的提示。 所有应用程序均可在 IHU 中使用。","0731：与 SK 成功进行 DMC 编程，使客户成功完成 TBOX SW OTA 升级。TR 关闭。 +0728： 客户用电话号码登录会员中心了。出现了另一个问题- apn1 不可用。为了解决这个问题，已经发送了 TBOX OTA 升级，但升级失败 - 上电失败。因此，已向经销商发送了使用 SK 进行 DMC 编程的请求。等待经销商的反馈。 +0722:等待DMC日志 +0718: 等待DMC日志 +0717：T-BOX登录记录和远控正常，IHU登录记录正常, 转国内DMC分析","31/07: programming DMC with SK successfull that let cutomer complete TBOX SW OTA upgrade successfully. TR closed. +28/07: customer was finally able to enter into member center with his phone number (not QR code). But there is another issue happened - apn1 was no longer available. In order to fix the issue TBOX OTA upgrade had been sent out for DMC SW upgrade but update has failed - an error message ""Power up failure"" came up upon starting update. Therefore, a request for DMC programmming with immo SK has been sent to dealer. Wait for feedback. +22/07: still waiting for data. +17/07: DMC log requested. Wait for data. +0717: pls help confirm DMC version first, it may be a version problem need be be upgrade. @Vsevolod Tsoi",Low,close,DMC,郭宏伟,31/07/2025,EXEED RX（T22）,XEYDD14B3RA004620,,,,Vsevolod Tsoi,,,,,,14 +TR707,,17/07/2025,,Traffic Payment,"There is impossible to buy packages +无法购买套餐","0729：验证正常，可关闭该问题 +0728：等客户确认 +0724：使用测试账号测试已恢复，待客户升级app确认 +0721：正在等待APP审核，预计本周内发版完成修复该问题（app侧排查域名问题） +o717: 反馈辛巴排查续费连接正常，转app侧排查","0729: Verify that it is working properly to close the issue +0728：Waiting for customer confirmation +0724：Tests have been recovered using a test account, pending customer upgrade app confirmation +0721：Waiting for APP review, expect the release to be completed within this week to fix the issue",Low,close,车控APP(Car control),李维维,29/07/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ5SD094857,,,"20250717-100020.mp4,image.png,image.png,image.png",Evgeniy Ermishin,,,,,,12 +TR708,Telegram bot,21/07/2025,,VK ,"Can't open VK video ""Unable to check licenses"" +无法打开 VK 视频 ""无法检查许可证""","0819:建议切换成等待数据，用户进站后再切换状态 +0814: 持续等待中 +0805:等待版本及日志等信息上传 +0728：等DMC日志和DMC版本和VK版本信息 +0721: 请邀请客户进站抓取DMC日志，确认DMC版本和VK版本信息 +0721：转国内生态分析","19/08:It is recommended to switch to wait for data and switch the state after the user enters the station. +14/08: still waiting +05/08:Waiting for version and logs to be uploaded. +28/07: Waiting for DMC logs and DMC version and VK version information. +21/07：Please help invite customers to dealer to grab the DMC logs and confirm the DMC version and VK version @Kostya +Asked to test another apps +21/07: Turning domestic ecological analyses",Low,Waiting for data,生态/ecologically,袁清,,CHERY TIGGO 9 (T28)）,LVTDD24B5RG089659,,,image.png,Kostya,,,,,, +TR710,Mail,21/07/2025,,PKI problem,"Navi doesn't work. Vehicle is well bound in TSP. MNO is OK. +导航不工作。 车辆在 TSP 中绑定良好。 MNO 正常。",0723: 请帮助确认版本信息，如果不是最新版请加入OTA升级DMC,"25/07: updated successfully, waiting for feedback +0724：please add the OTA list to upgrade DMC",Low,close,OTA,韦正辉,25/07/2025,EXEED RX（T22）,LVTDD24B3RG049645,,,"image-21-07-25-10-39.jpeg,image.png",Evgeniy Ermishin,,,,,,4 +TR711,Telegram bot,21/07/2025,,PKI problem,Navi doesn't work. Vehicle is well bound in TSP. MNO is OK. ,"0916：等待客户反馈 +0902：等待用户升级 +0820:见主机登录记录正常，建议与用户核实是否问题已解决 +0814：等待OTA +0728：暂无OTA结果，等待OTA反馈 +0723：请添加 OTA 列表以升级 DMC +0723: 请帮助确认版本信息，如果不是最新版请加入OTA升级DMC","23/09:Closed -> time out feedback +16/09:Waiting for update from customer +02/09:Waiting for update from customer +20/08:See host login records are normal, suggest checking with user if problem is resolved +14/08: still waiting OTA feedback +28/07：No OTA results at this time, awaiting OTA feedback +24/07：please add the OTA list to upgrade DMC +23/07: Please help to confirm the version information, if it is not the latest version, please join the OTA to upgrade the DMC.",Low,close,OTA,韦正辉,23/09/2025,EXEED RX（T22）,XEYDD14B3RA004254,,,"image.png,image.png",Kostya,,,,,,64 +TR712,Mail,21/07/2025,,PKI problem,Navi doesn't work. Vehicle is well bound in TSP. MNO is OK. ,"0725：更新成功，等待反馈 +0724：请添加 OTA 列表以升级 DMC +0723: 请帮助确认版本信息，如果不是最新版请加入OTA升级DMC","25/07: updated successfully, waiting for feedback +24/07：please add the OTA list to upgrade DMC +23/07: Please help to confirm the version information, if it is not the latest version, please join the OTA to upgrade the DMC.",Low,close,OTA,韦正辉,30/07/2025,EXEED RX（T22）,XEYDD24B3RA008170,,,"image.png,WhatsApp Image 2025-07-20 at 14.30.59 (2) (002).jpeg,WhatsApp Image 2025-07-20 at 14.30.59.jpeg,WhatsApp Image 2025-07-20 at 14.30.59 (1).jpeg,WhatsApp Image 2025-07-20 at 14.30.59 (3).jpeg",Evgeniy Ermishin,,,,,,9 +TR713,Mail,21/07/2025,,Navi,Navi does not work. Car status is OK in TSP and MNO.,"0728: 升级成功完成。导航应用程序已恢复。TR 关闭。 +0728：请反馈OTA结果 +0724：OTA包已下载，等待OTA +0724：版本信息已上传至附件图片 +0723: 请帮助确认版本信息，如果不是最新版请加入OTA升级DMC","28/07: upgrade completed successfylly. Navi app is restored. TR closed. +28/07: downloaded but still not upgraded. +28/07: Please provide feedback on OTA results +24/07: OTA upgrade is downloaded. Wait for update. +24/07: photo with DMC SW version is attached. +0724：please add the OTA list to upgrade DMC",Low,close,OTA,韦正辉,28/07/2025,EXEED RX（T22）,LVTDD24B6RG013593,,TGR0002748,"DMC_SW_version.jpg,Navi_version.jpg",Vsevolod Tsoi,,,,,,7 +TR714,,21/07/2025,,PKI problem,Navi doesn't work. Vehicle is well bound in TSP. MNO is OK. ,"0725：OTA更新成功，等待更新结果反馈 +0723: 请帮助确认版本信息，如果不是最新版请加入OTA升级DMC","25/07: updated successfully, waiting for feedback +0724：please add the OTA list to upgrade DMC",Low,close,OTA,韦正辉,30/07/2025,EXEED RX（T22）,LVTDD24B6RG032645,,,{4184CAD6-C211-49E9-B503-BD91EDC4B4FA}.png,Evgeniy Ermishin,,,,,,9 +TR715,Telegram bot,22/07/2025,,Activation SIM,"The car doesn't exist on the ADMIN platform - The user is unable to add this car to the app +该车在奇瑞ADMIN平台上不存在-用户无法在app中绑定车辆",0723: 从TSP后台查询车辆已绑定，请跟客户确认下,"0723: Checked from TSP Platform that the vehicle has been bound, please help confirm with the customer @Kostya",Low,close,用户CHERY-APP(User),岳晓磊,24/07/2025,CHERY TIGGO 9 (T28)）,LVTDD24B2RG120429,,TGR0002775,image.png,Kostya,,,,,,2 +TR716,Mail,22/07/2025,,PKI problem,Navi doesn't work. Vehicle is well bound in TSP. MNO is OK. ,"1021：14天无反馈转暂时关闭 +0908：客户暂无反馈 +0820:见主机登录记录正常，建议与用户核实是否问题已解决 +0811:仍然没有安装 +0725：已下载升级包，但还未升级 +0722: ota推送升级版本","23/10: PKI is ok for Navi => closed. +21/10:14 days no feedback to temporary closure +18/09: still no info, switch status to waiting for data +08/09: the customer doesn't answer us about current status +26/08: still waiting for update - pki is not ok +20/08:See host login records are normal, suggest checking with user if problem is resolved +11/08: still not installed +25/07: downloaded but not installed yet +0722: try to upgrade DMC by OTA",Low,close,OTA,韦正辉,23/10/2025,EXEED RX（T22）,XEYDD14B3RA004364,,,"image.png,file_3479.jpg",Vsevolod Tsoi,,,,,,93 +TR717,Telegram bot,23/07/2025,,Application,"Schedule route function in app doesn't work. Please provide info if this function is available in the current version of the app or not +Init function -> timeout error +app中的预约出行功能不起作用。请提供信息，说明该功能在当前版本的应用程序中是否可用。 +初始函数 -> 超时错误","0724: 该版本APP无此功能，TSP平台配置错误，已修复 +0723：转国内app确认","0724：APP does not have this function, TSP platform configuration error, already fixed. @Kostya",Low,close,车控APP(Car control),李维维,24/07/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ4SD233604,,TGR0002773,"image.png,image.png",Kostya,,,,,,1 +TR718,Telegram bot,23/07/2025,,PKI problem,Navi doesn't work. Vehicle is well bound in TSP. MNO is OK. ,"0728：等待客户确认 +0725：已成功OTA，等待确认问题是否解决 +0723: 请帮助确认版本信息，如果不是最新版请加入OTA升级DMC","25/07: OTA successfull, I will asked if problem solved +0723： Please help to confirm the version information, if it is not the latest version please join the OTA upgrade DMC",Low,close,OTA,韦正辉,30/07/2025,EXEED RX（T22）,EDYDD24B3S0000772,,,"{7EDBE9F2-101D-4B82-809D-55B4D8C3B2FB}.png,image.png",Evgeniy Ermishin,,,,,,7 +TR720,Telegram bot,23/07/2025,,Navi,Navi app does not work. Vehicle status is OK in TSP as well as in MNO.,"0807: 由于没有反馈，暂时关闭。 +0804：重复请求已发送给用户。如果在周四的会议上没有回复，该问题将暂时关闭。 +0731:暂无客户反馈 +0728: 等待客户确认 +0725：OTA 升级于 7 月 24 日完成。已询问客户 导航APP是否已恢复，暂无反馈。 +0724：OTA 升级已下载。等待升级。 +0724：请添加 OTA 列表以升级 DMC +0723：附上 DMC SW 版本的照片。","07/08: closed temporarily since no feedback. +04/08: repeat request has been sent to the user. If no reply by Thursday's meeting, issue will temporarily be closed. +31/07: feedback is pending. +28/07: repeat request sent again. Wait for feedback. +25/07: OTA upgrade completed on July, 24th. Customer has been asked wether Navi app was restored. +24/07: OTA upgrade is downloaded. Wait for update. +0724：please add the OTA list to upgrade DMC +23/07: Photo of DMC SW version is attached.",Low,temporary close,OTA,韦正辉,07/08/2025,EXEED RX（T22）,XEYDD24B3RA008192,,TGR0002786,DMC_SW_version.jpg,Vsevolod Tsoi,,,,,,15 +TR721,Telegram bot,23/07/2025,,Navi,"Navi and VK messenger apps do not work. Vehicle status is OK in TSP as well as in MNO. +导航和 VK 信息应用程序无法使用。TSP 和 MNO 中的车辆状态均正常","0728: DMC SW OTA 升级至 02.02.00 后，Navi 和 VK messener 应用程序已恢复。TR 已关闭。 +0728：OTA 升级于 7 月 26 日成功完成。 +0724：图片展示DMC版本是02.00.00，请先升级OTA升级DMC","28/07: Navi and VK messener apps are restored following DMC SW OTA upgrade to 02.02.00. TR closed. +28/07: OTA upgrade completed successfully on July, 26th. +24/07: OTA upgrade is downloaded. Wait for upgrade. +0724：Pictures show DMC version 02.00.00， pls help add OTA list to upgrade DMC",Low,close,DMC,郭宏伟,28/07/2025,EXEED RX（T22）,XEYDD24B3RA008392,,TGR0002708,"DMC_SW_version.jpg,Navi_version.jpg,VK_messenger_version.jpg",Vsevolod Tsoi,,,,,,5 +TR722,Telegram bot,24/07/2025,,PKI problem,"Ihu apps doesn't work, outdated data in the mobile app, remote control works normal, PKI issue +hu 应用程序无法使用，移动应用程序中的数据过时，远程控制工作正常，PKI 问题","0819:建议切换成等待数据，用户进站后再切换状态 +0814：等待信息反馈 +0805：等待DMC版本信息和DMC日志,并提供大概的IHU APP不可使用的时间 +0731：等待DMC版本信息和DMC日志,并提供大概的IHU APP不可使用的时间 +0728：等待DMC版本信息和DMC日志,并提供大概的IHU APP不可使用的时间 +0724: 请帮助确认DMC版本信息和邀请客户进站抓取DMC日志 +0724: 车辆激活时间2025.7.22日，T-BOX登录正常，远控正常，无车机登录记录。TSP平台查看IHU版本：02.00.04","19/08:It is recommended to switch to wait for data and switch the state after the user enters the station. +14/08: still waiting +05/08: Waiting for DMC version information and DMC logs. and provide an approximate time when the IHU APP will be unavailable +31/07: Waiting for DMC version information and DMC logs. and provide an approximate time when the IHU APP will be unavailable +28/07: Waiting for DMC version information and DMC logs. and provide an approximate time when the IHU APP will be unavailable +24/07: Please help confirm the DMC version information and invite customers to dealer to capture the DMC logs @Kostya +24/07: Vehicle activated on 2025.7.22, T-BOX logged in OK, remote control OK, no vehicle log in record.",Low,Waiting for data,DMC,郭润函,,JAECOO J7（T1EJ）,EDXDD21BXSC061504,,TGR0002797,image.png,Kostya,,,,,, +TR725,Mail,28/07/2025,,Problem with auth in member center," No QR in member centre. +1) Car bound in tsp +2) SIM activated +3) Wi-Fi used +4) Auto time sync is enabled +-> No IHU login in tsp, no IHU in PKI","1014：等待来自经销商和客户的数据 +1009：正在处理 +0930：等待客户进站重新设置环境后反馈 +0925：等待客户进站处理 +0916: 请邀请客户进站进入工程模式，重新设置环境，操作视屏已发前方。如修改环境后未恢复正常，请帮忙抓取DMC日志。 +0909：等待客户反馈” +0908：建议联系用户可以尝试恢复DMC出厂设置，查看是否有二维码显示 +0828：反馈怀疑主机环境非正式环境，建议用户进站检查DMC环境是否正确 +0826：会后转主机分析日志 +0819: 等待日志上传 +0814：等待日志 +0805:已提供在群聊中，等待日志上传 +0731: 请提供 E0Y 的日志收集手册 @王冬冬 +0730：等待用户进站抓取DMC日志 +0730：尝试下电，并重启主机，如仍无变化，请抓取主机日志 +0729：更新至最新的 DMC 版本 - 01.00.21_02.02.236 +(更新后我们才尝试使用自动同步和无线网络登录） - 没有任何变化 +0728：请确认用户实车主机版本，如不是最新版建议更新，同时抓取DMC日志，及实车IHU_SN","0112:Closed - solved by reboot +1014:Waiting for data from dealer and customer +1009:In procces +0930:In procces +0925: Prepairing guide for dealer -> please provide instruction for switching for e0X +0916: Please invite the customer to come in and enter engineering mode, reset the environment, and send a video screen of the operation to the front after the meeting. If the environment does not return to normal after modification, please help capture the DMC log.@Kostya +15/09: data was provided, check dmc log +09/09:waiting for feedback from customer +08/09: It is recommended to contact the user who can try to restore DMC factory settings to see if there is a QR code displayed. +28/08：Feedback suspected host environment informal environment, suggest that the user into the station to check the DMC environment is correct +26/08：Post-conference to DMC analysis +21/08: log was attached +19/08: Requested, waiting for logs +14/08: Requested, waiting for logs +05/08:Already available in the group chat, waiting for logs to be uploaded +31/07: please provide manual for collecting logs on E0Y @王冬冬 +31/07: waiting for DMC logs +30/07: Try to power down and reboot the DMC, if there is still no change, grab the DMC logs.@Kostya +29/07: Car updated by the dealer to the last DMC version - 01.00.21_02.02.236 +(Only after update we tried to login with auto sync and wi-fi) - nothing changes +28/07: Please confirm the user's real car host version, such as not the latest version of the proposed update, while capturing the DMC logs, and real car IHU_SN.",Low,close,DMC,王冬冬,01/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ3SD097546,,,2025_08_21_13_34_58.zip,Kostya,,,,,,126 +TR730,Mail,31/07/2025,,Navi,"""There is impossible to turn off notifications of the speed limit. Because of that I should turning off all the notifications, but it is not comfortable. Please fix this issue"" +""无法关闭限速通知。因此，我应该关闭所有通知，但这样做很不舒服。请解决这个问题""。","0811: 0811: 确定，将状态切换为临时关闭-> 等待根据规划进行新的更新 +0805:等待软件发版即可，建议暂时关闭 +0801：软件提测已完成；8/15EWO流程完成；8/20试装完成；8/30切换完成；9/10 售后升级通知下发 +0731：反馈主机提示限速提醒，无法关闭，建议优化","11/08: ok, switch status to temporary close-> waiting for new update according planning +05/08：Just wait for the software to be released, it is recommended to close it for the time being +01/08: software testing completed; 8/15 EWO process completed; 8/20 trial installation completed; 8/30 switchover completed; 9/10 post-sale upgrade notice issued +31/07：There is impossible to turn off notifications of the speed limit. Because of that I should turning off all the notifications, but it is not comfortable.",Low,temporary close,DMC,郭宏伟,11/08/2025,EXEED RX（T22）,XEYDD14B3RA011926,,,,Evgeniy Ermishin,,,,,,11 +TR731,Mail,01/08/2025,,OTA,"DMC OTA upgrade can not be started. An error message ""Power up failure"" comes up when trying to start - see photo attached. +无法启动 DMC OTA 升级。在尝试启动时，会出现 ""上电失败 ""的错误信息，请参阅所附照片。","0916：等待客户进站学习SK后确认 +11/09：检查了FOTA -没有DMC和TBOX SW的升级，这意味着SK的DMC学习已经完成了。 +0902: 属地运维已发布技术公告给属地经销商及售后人员，实施 SK 学习指导。用户现在知道应该去经销商那里学习 TBOX 与 SK。 +0819：经销商无反馈 +0814：经销商无反馈 +0812：与 ASD 团队商定，将为所有客户创建关于使用 SK 对 DMC 进行编程手册。等待 ASD 团队。一旦完成，将邀请所有客户执行程序 +0807：等待用户进站学习DMC的SK +0804:OTA专业反馈，未对DMC编程，建议用户进站学习DMC的SK， +0801：反馈OTA失败，建议下电重启下后重新尝试OTA，如仍提示失败，抓取OTA日志","18/09: no DMC nor TBOX OTA upgrade yet. TR closed. Will be reopend if any issue. +11/09: checked in FOTA - no DMC nor TBOX SW upgrade that means there was no DMC learning with SK done yet. +02/09: techical bulletin had been issued for implementing SK learinig instruction. User is aware now that he should go to dealership for learning TBOX with SK. +19/08：dealer's feedback is pending. +14/08: dealer's feedback is pending. +12/08: agreed with ASD team that technical bulletin is gonna be created on prgramming DMC with SK for all the customers. Wait for ASD team. Once done all the customers will be invited for implementing of procedure +07/08: request for learing of DMC with SK is on process +04/08:OTA professional feedback, not programmed for DMC, suggesting that user come in and learn SK for DMC. +01/08：Feedback OTA failure, it is recommended to re-try OTA after power down and reboot DMC, if still prompted failure, capture OTA logs.",Low,close,OTA,韦正辉,18/09/2025,EXEED RX（T22）,XEYDD14B3RA007152,,"Россман Антон Семёнович, +79104032994, г.Москва, Автодом Exeed Варшавка",OTA_upgrade_failure.jpg,Vsevolod Tsoi,,,,,,48 +TR732,Mail,01/08/2025,,OTA,DMC OTA upgrade can not be started. An error message "Power up failure" comes up when trying to start - see photo attached.,"0916：等待客户进站学习SK后确认 +0902: 属地运维已发布技术公告给属地经销商及售后人员，实施 SK 学习指导。用户现在知道应该去经销商那里学习 TBOX 与 SK。 +0814：等待经销商反馈 +0812：与 ASD 团队商定，将为所有客户创建关于使用 SK 对 DMC 进行编程的手册。等待 ASD 团队。一旦完成，将邀请所有客户执行程序 +0807：等待用户进站学习DMC的SK +0804:OTA专业反馈，未对DMC编程，建议用户进站学习DMC的SK， +0801：反馈OTA失败，建议下电重启下后重新尝试OTA，如仍提示失败，抓取OTA日志","22/09: let user upgrade his TBOX SW OTA. If any issue, TR will be re-opened. +18/09: status in FOTA: DMC SW is up to date. TBOX - upgrade downloaded but not installed yet. +11/09: checked in FOTA: no DMC nor TBOX SW upgrade that means there was no DMC learning with SK done yet. +02/09: techical bulletin had been issued for implementing SK learinig instruction. User is aware now that he should go to dealership for learning TBOX with SK. +14/08: feedback from dealer is pending. +12/08: agreed with ASD team that technical bulletin is gonna be created on prgramming DMC with SK for all the customers. Wait for ASD team. Once done all the customers will be invited for implementing of procedure. +07/08: request for learing of DMC with SK is on process +04/08:OTA professional feedback, not programmed for DMC, suggesting that user come in and learn SK for DMC. +01/08: Feedback OTA failure, it is recommended to re-try OTA after power down and reboot DMC, if still prompted failure, capture OTA logs.",Low,close,OTA,韦正辉,22/09/2025,EXEED RX（T22）,XEYDD14B3RA002666,,"Богатов Илья Юрьевич, 89048580622, город Владимир EXEED ЦЕНТР АВТОТРАКТ",DMC_upgrade_failure.jpg,Vsevolod Tsoi,,,,,,52 +TR734,Telegram bot,04/08/2025,,OTA,"DMC OTA upgrade can not be started. An error message ""Power up failure"" comes up when trying to start - see photo attached. SK DMC learning is useless in this case (PIN already written in) DMC log attached +无法启动 DMC OTA 升级。在尝试启动时，会出现 ""上电失败 ""的错误信息--见附图。SK DMC 学习在这种情况下毫无用处（PIN 已写入）。","0812:需要先复位SK，后才能执行SK编程。 +0805:已附上DMC 日志（尝试更新后 15 分钟后捕获的日志）编程失败的原因可能是PIN已经存在？ +0804： +1.反馈OTA失败，建议下电重启下后重新尝试OTA，如仍提示失败，抓取DMC日志 +2.同时附件图片显示编程失败，建议转DMC专业分析","12/08:SK needs to be reset before SK programming can be performed.@Kostya +05/08 DMC logs alredy attached (captured 15 minutes later after the try to update) +May programming failure be caused by alredy existed pins? +04/08： +1.Feedback OTA failure, it is recommended to power down and reboot after retrying OTA, such as still prompted by the failure to capture the DMC logs +2. At the same time, the attached picture shows programming failure, it is recommended to turn to DMC for professional analysis.",Low,close,OTA,韦正辉,12/08/2025,EXEED RX（T22）,LVTDD24B6RG009818,,Андрей Иванов,"log.7z,image.png,image.png,image.png",Kostya,,,,,,8 +TR736,Mail,04/08/2025,,Chinese TBOX in Russia,Network doesn't work because of chinese TBOX. We need to replace T-box and then change data in DB,"1009: TBOX和远控均正常，建议关闭 +0930：等待客户反馈 +0918: 今天TSP平台查看TBOX登录成功，待客户确认是否恢复正常 +0917：新的TBOX和ICCID信息已经更新到TSP平台，请建议客户重新启动车辆 +0916：请帮忙提供新的TBOX SN和ICCID +15/09: tbox 已更换 +0909:tbox 将更改 +0908：再次向 ASD 询问情况 +0826：暂无更新 +0819:请QS方更新进展 +0814:no update +0811: TBOX大约在 W33-34 周到达QS，然后迅速转给ECB的同事。 +0804:建议邀请用户进站换件，换件后上传最新TBOX信息，后台维护后可正常使用","09.10: solved +18.09: asked about current status +0918: Today's TSP platform viewed TBOX login successfully, pending customer confirmation that it is back to normal or not +0917: New TBOX and ICCID information has been updated to the TSP platform, please advise the customer to restart the vehicle @Evgeniy Ermishin +0916: ICCID - 89701010060630592862 ; SN -YCHE0YDF706801C# +0916: Please help provide the new TBOX SN and ICCID @Evgeniy Ermishin +15/09: tbox was changed +09/09: 09/09 tbox will be changed +08/09: Asked ASD again about status +26/08：no update +19/08:pls QS side update the progress +14/08: no update +11/08: The block will arrive in Moscow approximately on W33-34 weeks, then it will be promptly redirected to colleagues at the ECB. +04/08：It is recommended to invite users to come in for replacement and upload the latest TBOX information after replacement, which can be used normally after maintenance in the background.",Low,close,TBOX,Evgeniy Ermishin,09/10/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ9SD094280,,,{49ED034B-A1CE-448F-AFA9-38B10D6C5BB3}.png,Evgeniy Ermishin,,,,,,66 +TR740,Telegram bot,05/08/2025,,OTA,DMC OTA upgrade can not be started. An error message "Power up failure" comes up when trying to start - see photo attached.,"0916：等待客户进站学习SK后确认 +0902: 属地运维已发布技术公告给属地经销商及售后人员，实施 SK 学习指导。用户现在知道应该去经销商那里学习 TBOX 与 SK。 +0814：等待经销商反馈 +0812: 与 ASD 团队商定，将为所有客户创建关于使用 SK 对 DMC 进行编程的手册。等待 ASD 团队。一旦完成，将邀请所有客户执行程序。 +0807：等待用户进站学习 DMC 的 SK +0807：等待用户进站学习DMC的SK +0804:OTA专业反馈，未对DMC编程，建议用户进站学习DMC的SK， +0801：反馈OTA失败，建议下电重启下后重新尝试OTA，如仍提示失败，抓取OTA日志","22/09: TR closed. If any issue, it will be re-opened. +18/09: still the same status - no DMC nor TBOX have been upgrade OTA. +11/09: checked in FOTA - no DMC nor TBOX SW upgrade that means there was no DMC learning with SK done yet. +02/09: techical bulletin had been issued for implementing SK learinig instruction by dealer. User is aware now that he should go to dealership for learning TBOX with SK. +14/08: feedback from dealer is pending. +12/08: agreed with ASD team that technical bulletin is gonna be created on prgramming DMC with SK for all the customers. Wait for ASD team. Once done all the customers will be invited for implementing of procedure. +07/08: request for learing of DMC with SK is on process +04/08:OTA professional feedback, not programmed for DMC, suggesting that user come in and learn SK for DMC. +01/08: Feedback OTA failure, it is recommended to re-try OTA after power down and reboot DMC, if still prompted failure, capture OTA logs.",Low,close,OTA,韦正辉,22/09/2025,EXEED RX（T22）,XEYDD14B3RA004392,,TGR0003000,DMC_upgrade_failure.MOV,Vsevolod Tsoi,,,,,,48 +TR741,Telegram bot,07/08/2025,,Application,"Can't share the remote control with existed user - 79268443232 +The owner number is 79060898915 +installed last public available version","0826:QS侧会后与客户确认 +0819：请QS方更新进展 +0814：等待用户反馈 +0812：后台日志显示用户使用 79268443232手机号分享车控给 相同的 79268443232手机号，请核实是否为用户误操作 +0808:建议用户提供下存在用户 79268443232的手机型号，如果不是最新，建议更新至最新后尝试 +0807: 没有 VPN，网络正常，尝试了几次 - 结果相同：""服务器响应超时"",当我们尝试从我们的账户共享访问到这部手机时，结果正常。","23/09 Closed -> customer feedback +26/08：after meeting check with customer +19/08: pls QS side update the progress +14/08: Waiting for info from user +12/08：Background logs show that users use 79268443232 mobile phone number to share car control to the same 79268443232 mobile phone number, please verify whether it is a user misuse. +08/08:Suggest users to provide the mobile phone model and APP version of the existing user 79268443232, if it is not the latest, it is recommended to update to the latest and try! +07/08 NO VPN, network is ok, Tried few times - result the same: ""Server responce Time out"",When we tried share access from our account to this phone, result is ok.",Low,close,车控APP(Car control),Kostya,23/09/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ2SD152553,,TGR0003110,"img_v3_02p3_f77a1695-957a-4e41-91c4-fce5f845ed3g.jpg,img_v3_02p3_223d485d-9ccd-4871-aabc-4513cca543fg.jpg",Kostya,,,,,,47 +TR742,Mail,08/08/2025,,Traffic is over,Abnormal traffic consumption,"暂无进展，该类异常消耗详细见TR1039分析进展 +1204：E03未添加此流量监控功能 +1118：更新结果已附，请在后续问题出现时抓取DMC日志分析-主机升级到0924版本的软件，若后续出现流量异常的情况，抓主机日志，供应商分析日志，根据UID去识别。 +1111：监控功能预计将于十一月发布。 +1106：是否已确定发布日期？这个月 +1101：用于流量监控功能的OTA更新正在等待发布。 +1023：等待发布 OTA 流量监控功能。 +1021：等待新的交通监控功能 +1014：等待流量监控功能 +0922: 通过对E03车辆的日志分析：主机、VK应用、在线导航排查无异常流量消耗问题；同步排查此车未进行过软件升级OTA操作和车机应用的升级；在日志时发现当日用户曾用手机连接车机WIFI热点，时长2小时，无法确认是否是热点原因造成的流量异常。所以目前暂未定位到明确原因。针对这个情况将对下个主机版本增加流量监控功能，该功能预计10月30日完成试装后下发售后升级通知。 +0909：测试车反馈只打开了一次视频应用，后续流量异常时请建议用户提供更详细的操作步骤 +0908: 我们提供测试车 LNNAJDEZ1SD236951 的 TBOX 日志和 DMC 日志，并附有运行日期/时间。请首先从您自己的角度检查该日志！ +0826：已赠送5G流量，等待更多日志上传 +0820：已分析VIN：LNNBDDEZ0SD104615，日志显示该车在异常消耗时间段在下载导航图资，后续仍需排查其他车辆，诊断根本原因，主机侧拟定下个版本加入流量监控功能 +0819：国内反馈需提供MTS后台使用记录，外方已提供 +0815：已获取到一台车主机日志，转国内分析 +0809：建议联系与服务站距离较近的用户，进站获取主机日志。 +0808:目前仍在排查定位原因，暂无排查结果","04/12: confirmed - E03 has no traffic monitoring function. +25/11: An E03 LNNAJDEZ1SD236951 is present among E0Y list. Was a monitoring function released for E03 as well?-------No only E0Y. +18/11:Updated results are attached. When subsequent issues arise, capture DMC logs for analysis. Upgrade the host to software version 0924. If abnormal traffic occurs later, capture host logs and vendor analysis logs, then identify based on UID. +18/11: still wait for release monitoring function. +11/11: monitoring function releae is exepcted in November. +06/11: is a date of release alredy known? This month +01/11: release of an OTA for traffic monitoting function is pending. +23/10: waiting for release of an OTA traffic monitoring function. +21/10: waiting for new traffic monitoring function +14/10: waiting for new traffic monitoring function +0922: Through the log analysis of the E03 vehicle: no abnormal data consumption issues were found in the host, VK application, and online navigation. Simultaneously check that this vehicle has not undergone OTA operations or upgrades to in-vehicle applications. It was found in the log that the user had connected to the car's Wi-Fi hotspot with their mobile phone on that day for 2 hours. It is impossible to confirm whether the abnormal data traffic was caused by the hotspot. +The next steps for this situation: +The traffic monitoring function will be added to the next host version. This function has been initiated for testing and it is expected that the after-sales upgrade notice will be issued on October 30th. +0916: A preliminary analysis of the logs shows that the traffic consumption of applications such as VK and weather is normal, while further investigation is underway for other applications. Please help confirm the following two aspects: +1、What operations were performed before testing to grap the log. +2.、It was found in the log that offline maps of 27 regions have been downloaded. Please confirm when the maps were downloaded. If the map is downloaded during the test log retrieval period, it may consume 5 to 6 gigabytes of data traffic. + +0909：Test car feedback only opened the video application once, subsequent traffic anomalies please suggest that users provide more detailed operating procedures. +08/09: we provide TBOX log and DMC log from our test car LNNAJDEZ1SD236951 with date/time operation time. Please check this one from yourside first! +26/08: 5G of traffic has been given away, waiting for more logs to be uploaded +20/08: VIN: LNNBDDEZ0SD104615 has been analyzed, the log shows that the car in the abnormal consumption of time in the download of navigation maps, the follow-up still need to investigate other vehicles, diagnosis of the root cause, the host side of the next version of the proposed addition of traffic monitoring features. +19/08：Domestic feedback need to provide MTS background use records, foreign parties have provided +15/08：One car host log has been obtained, transferred to domestic analysis. +09/08：It is recommended to contact users who are in close proximity to the service station to come in and get the DMC logs. +08/08:The cause of the positioning is still being investigated and no results are available at this time.",Low,Processing,DMC,林希玲,,EXLANTIX ET (E0Y-REEV),"LNNBDDEZ6SD233605 - upgraded, Nov 13 +LNNBDDEZXSD233607 - upgraded, Nov 17 +LNNBDDEZ5SD233563 - Nov, 25 - downloaded +LNNBDDEZ5SD152577 - upgraded Nov, 14",,,{84F23F53-3E98-42CA-B4F3-CC62D7CF07FA}.png,Vsevolod Tsoi,,,,,, +TR745,Telegram bot,12/08/2025,,Traffic is over,No QR code available being able to enter into member center,"暂无进展，该类异常消耗详细见TR1039分析进展 +1202：11月30日OTA升级已成功完成。需要等待用户复现后，抓取对应的IHU日志 +1127：已下载但尚未升级。 +1125：OTA包已下载但尚未安装。 +1120：车辆仍无法连接OTA服务器。 +1118：OTA反馈，该用户暂未升级 +1111：监控功能预计将于十一月发布。 +1106：是否已确定发布日期？ +1101：用于流量监控功能的OTA更新正在等待发布。 +1023:等待发布 OTA 流量监控功能。 +1011：从日志检查到下载过离线地图，但是无法定位到原因，等待10月底上线流量监控功能 +1009：等待日志分析 +23/09：与 ASD 小组达成一致意见 - 10 月 2 日维修服务时将重新检查 DMC 日志。 +0918：等待日志中 +0916：请提供DMC日志 +0826：已赠送5G流量，等待更多日志上传 +0820：等待主机方确认哪些应用消耗流量，下个主机版本加入流量监控功能 +0819：国内反馈需提供MTS后台使用记录，外方已提供 +0815：已获取到一台车主机日志，转国内分析 +0812：新客户的反馈 - 提供的 5Gb 流量在一天内全部用完，甚至用得更多 - 参见 SIMBA 截图。 +0812:无主机登录记录，TBOX登录正常；客户反馈--在多次尝试连接与热点共享的 WIFI 进入会员中心后，二维码终于出现了。然后，客户就可以登录会员中心了。无二维码问题为DMC版本问题，如下次遇到相同情况可确认版本，目前。ICC 1.0.21 版本已修复此问题","02/12: Upgrade OTA was successfully completed on Nov, 30. Once the issue occurs, an ICC log will be requested. +27/11: still downloaded but not upgarede yet. +25/11: OTA package downloaded but not installed yet. +20/11: car still has no connect with OTA server. +18/11: still wait for release monitoring function.----1118: OTA feedback indicates this user has not yet upgraded. +11/11: monitoring function releae is exepcted in November. +06/11: is a date of release alredy known? +01/11: release of an OTA for traffic monitoting function is pending. +23/10:waiting for release of an OTA traffic monitoring function. +21/10: wait for traffic monitoring function release. +1011: From log checks to the download of offline maps, but the exact cause cannot be located. waiting for the traffic monitoring function to be launched at the end of October @Vsevolod Tsoi +03/10: dmc log was added +23/09: agreed with ASD team - DMC log will be recored when maintenance service on October, 2nd. +22/09: a request has been sent to ASD team whether recording DMC log might be included when a service maintenance scheduled on October, 2nd. Wait for confirmation. +18/09: request in on process. +0916: Please provide DMC logs @Vsevolod Tsoi +16/09: the issue of an extra consumption is still under investigation +26/08: 5G of traffic has been given away, waiting for more logs to be uploaded +20/08: Waiting for the host to confirm which applications consume traffic, and add traffic monitoring function in the next host version. +19/08：Domestic feedback need to provide MTS background use records, foreign parties have provided +15/08：One car host log has been obtained, transferred to domestic analysis. +12/08: new customer's feedback - all the traffic provided 5Gb was used up by one day (05/08) and even more - see screenshot from SIMBA. +12/08: customer's feedback - after several attempts to enter into member center connecting to WIFI shared with hotspot, QR code finally came up. Then customer was able to log into member center. ",Low,Analysising,DMC,林希玲,12/08/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ2SD152553,,TGR0003074,"2025_10_02_14_09_17.rar,Traffic_issue.JPG,file_3959.mp4,file_3958.jpg,file_3859.jpg,file_3845.mp4,file_3857.jpg,file_3858.jpg,file_3846.jpg",Vsevolod Tsoi,,,,,,0 +TR753,Mail,14/08/2025,,Application,The customer can't activate telematics,"10/21: 14天无反馈转暂时关闭 +09/18：仍然无法联系到客户。已将状态切换至等待数据状态 +09/09：经销商表示目前无法联系到客户 +08/26：TSP显示SIM卡已激活，将在会议后与开发部门确认应用报错问题 +08/26：收到O&J反馈表明问题不在他们那边 +08/14：已要求O&J应用团队进行核查 +08/20：他们告知我们他们那边一切正常","21/10：14 days no feedback to temporary closure +18/09: still can't communicate. switch data to waiting +09/09: dealer said that he can't connect with the customer at the moment +26/08: TSP shows that SIM has been activated, will confirm with development after the meeting that the app is reporting errors +26/08: received information from O&J that problem is not on them side +14/08: asked O&J app team to check +20/08: they told us that everything is ok from them side",Low,temporary close,O&J-APP,Vadim,21/10/2025,JAECOO J7（T1EJ）,EDXDD21BXSC061504 ,,,IMG_20250814_095720.jpg,Evgeniy Ermishin,,,,,,68 +TR756,Telegram bot,19/08/2025,,Application,The customer can't reset password ,"0916: T平台查看近几日远控正常，等待客户确认 +0908:等待用户反馈 +0902:平台见用户近期多条远控记录，建议联系用户确认是否已解决，如未解决请复现操作。方便问题排查 +0825：已修复异常数据，建议用户重新尝试 +0819:用户反馈重设车控密码，APP报错A00120，转国内分析；需要数跑排查","0916: The remote control on the TSP platform has been normal in recent days. waiting for the customer's confirmation +08.09: asked the customer about current status +02/09:TSP Platform have seen the user's recent multiple remote control records. we suggest to contact the user to confirm whether it has been resolved, if not resolved, please reproduce the operation. Convenient for problem troubleshooting +25/08: Abnormal data has been fixed, users are advised to try again +19/08:User feedback reset car control password, APP reported error A00120, turn domestic analysis",Low,close,用户CHERY-APP(User),岳晓磊,16/09/2025,CHERY TIGGO 9 (T28)）,LVTDD24B0RG128478,,,image.png,Evgeniy Ermishin,,,,,,28 +TR760,Mail,20/08/2025,,Application,The customer can't activate telematics,"1021：14 days no feedback to temporary closure +0918：再次委托经销商邀请客户提供日志。 +0826：协商一致，转状态为等待数据。 +0821：已发出邀请请求。 +0820：TSP平台显示SIM卡已激活但无数据流量，无主机与TBOX登录记录；CMP检查发现两条短信发送失败，建议用户进站检测： +1.实车TBOX是否未退出工程模式 +2.检查实车TBOX信息与平台是否一致 +3.同步抓取TBOX日志 +0820：TBOX与DMC登录/注销失败。","21/10：14 days no feedback to temporary closure +18/09: asked dealer again to invite the customer for logs +26/08: Consensus to wait for data +21/08: request for invitation was send +20/08:TSP see SIM card has been activated, but no traffic go, no host and TBOX login record, CMP check two SMS record send failure, suggest user into the station to check +1. Whether the TBOX of the real car has not exited the engineering mode. +2. Check whether the real TBOX information is consistent with the platform. +3. Simultaneous capture of TBOX logs +20/08: tbox and dmc login/logout nok. ",Low,temporary close,TBOX,刘海丰,21/10/2025,JAECOO J7（T1EJ）,LVVDB21B9RC071514,,,image.png,Evgeniy Ermishin,,,,,,62 +TR763,Mail,21/08/2025,,HU troubles,SMS doesn't receive during restoring the factory settings,"0930: 等待客户反馈 +0918：暂无客户反馈 +0908:询问客户，等待反馈 +0827:检查到用户今日有车机登录的验证码请求，建议用户可以重新尝试恢复出厂设置 +0826:开发反馈后台无描述请求记录，请用户换个信号好点的地方尝试 +0822：客户已绑定，但无法恢复出厂设置，客户没有收到短信验证码。 +0821：请检查该用户是否已解绑，请在绑定情况下恢复出厂设置 +0821:反馈恢复出厂设置时，收不到验证码","09/10: changed status to temporary close - no feedback +18/09: no feedback from customer +08/09: asked the customer, waiting for feedback +27/08:Checked that the user has a CAPTCHA request to log in the car today, suggested that the user can try to restore the factory settings again. +26/08:The developer feedbacks that there is no record of description request in the background, please try in another place with better signal. +21/08: Client is bound , but it is impossible restore factory settings, the customer doesn't receive SMS verification code. +21/08:Please check whether this user is unbound, please restore factory settings in case of binding +21/08:Feedback when restoring factory settings, can't receive the verification code",Low,temporary close,local O&M,Evgeniy Ermishin,09/10/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ7SD163242,,,"img_v3_02pi_ce6f7c9b-da0c-466f-8242-eb7d961efcag.jpg,image.png",Evgeniy Ermishin,,,,,,49 +TR764,Mail,25/08/2025,,Problem with auth in member center,QR code doesn't exist. ,"0902:见主机正常登录，22日属地人员尝试更换IHU-sn，后续更换回原有SN后，主机正常登录，建议用户重新尝试，与客户确认是否已解决。同时建议进站抓取日志复核 +0827：PKI反馈客户车辆PKI下发成功，建议用户重新尝试，与客户确认是否已解决。同时建议进站抓取日志复核 +0825：反馈会员中心无法不显示二维码，同时有PKI报错记录，主机正常登录，但是PKI平台见有报错信息，正在与PKI核实，建议用户进站抓取DMC日志","08.09: asked the customer - solved +02/09: see host normal login, 22nd belonging to the personnel to try to replace the IHU-sn, subsequent replacement back to the original SN, the host normal login, it is recommended that the user to retry, and confirm with the customer to confirm whether it has been resolved. At the same time, it is recommended that the station capture logs to review +27/08: PKI feedback customer vehicle PKI issued successfully, suggest user retry, confirm with customer if resolved. At the same time, it is recommended that the station capture logs to review +25/08: Feedback member center can not not display the QR code, at the same time there are PKI error records, the host is normally logged in, but the PKI platform to see the error message, is verifying with PKI, suggested that the user into the station to capture the DMC logs",Low,close,生态/ecologically,Evgeniy Ermishin,09/09/2025,JAECOO J7（T1EJ）,EDXDD21B1SC057888,,,"image.png,IMG_20250822_232228.jpg",Evgeniy Ermishin,,,,,,15 +TR765,Mail,25/08/2025,,Problem with auth in member center,QR code doesn't exist. (DMC log in attachment) ,"0827：PKI反馈客户车辆PKI下发成功，建议用户重新尝试，与客户确认是否已解决 +0826:等待合规流程审批后，日志转入分析流程 +0825：反馈会员中心无法显示二维码，主机正常登录，但是PKI平台见有报错信息，正在与PKI核实，建议用户进站抓取DMC日志","29/08: still doesn't work - solved by entering VIN in uppercase in engineering menu in TSP settings +27/08: PKI Feedback Customer Vehicle PKI Issued Successfully, suggest user to retry, confirm with customer if resolved +26/08: Waiting for approval from the compliance process before logs are transferred to the analysis process +25/08: Feedback member center can not not display the QR code, the host is normally logged in, but the PKI platform to see the error message, is verifying with PKI, suggested that the user into the station to capture the DMC logs",Low,close,生态/ecologically,袁清,29/08/2025,OMODA C7 (T1GC),LVUGFB224SD833622,,,"2025_08_23_14_32_11.zip,IMG_20250727_153520.jpg,IMG_20250727_153625.jpg,IMG_20250727_153632.jpg,IMG_20250727_153516.jpg,VID_20250822_103831 (1).mp4",Evgeniy Ermishin,,,,,,4 +TR766,Mail,25/08/2025,,Activation SIM,The customer can't activate SIM (PKI problem),"0918: tsp平台查看tbox和车机登录记录近几日均正常，SIM卡为激活状态，流量消耗正常。 +0916: 等待客户确认是否恢复，如未恢复提供TBOX和DMC日志 +0908：已询问用户，暂无回复 +0903：平台端见9月2日TBOX及DMC均有登录记录，但9月3日无主机登录，仅有TBOX登录记录，请与用户核实是否已恢复 +0826：建议用户进站抓取主机日志 +0825：已确认平台端SIM已激活，无主机登录记录，转主机确认是否是版本已知问题","18/09: problem solved by update, dmc/tbox login/logout ok, pki ok +0916: Waiting for customer to confirm recovery or not, if not, provide TBOX and DMC logs. @Evgeniy Ermishin +08.09: asked the customer +03/09：On the TSP platform side, there were login records for both TBOX and DMC on September 2, but there was no host login and only TBOX login records on September 3, so please check with the users to see if it has been restored. +26/08：suggest to catch the DMC logs +26/08: dmc"",""sv"":""02.01.00_01.19.80 +25/08: Have confirmed that the platform side SIM has been activated, no DMC login record, turn the host to confirm whether it is a version of known issues",Low,close,DMC,郭宏伟,18/09/2025,EXEED RX（T22）,XEYDD14B3SA012169,,"""dmc"",""sv"":""02.01.00_01.19.80","image.png,{D4BB9916-C2CD-40D6-8E44-CD6AFA766F23}.png",Evgeniy Ermishin,,,,,,24 +TR768,Mail,25/08/2025,,Problem with auth in member center,QR code doesn't exist. ,"0826:昨日晚间PKI反馈内存超出预警值，等待客户反馈是否已解决 +0826:反馈25日晚间TBOX有登录记录，请用户重新尝试，查看是否恢复 +0825:此车激活后未见TBOX登陆记录，建议用户进站检查TBOX是否未退出工程模式，并抓取实车日志","26/08: asked for feedback from the customer - solved +26/08:Feedback on the evening of the 25th TBOX has a login record, please users retry to see if it is restored +25/08: No TBOX login record was found after this vehicle was activated. It is recommended that the user visit the station to check if the TBOX has not exited the engineering mode and capture the real vehicle logs.",Low,close,TBOX,Evgeniy Ermishin,26/08/2025,EXLANTIX ES (E03),LNNAJDEZXSD148187,,,image.png,Evgeniy Ermishin,,,,,,1 +TR769,Mail,25/08/2025,,OTA,"""When updating the firmware over the air, the car froze and turned off after an hour. when the ignition is turned on, the main screen indicates that the software is 99% loaded and the main screen is not working""","0909:会后与专业同步 +0908：我们订购了新的 dmc ecu，因为重启没有用，客户每次都能看到 99%，拔掉电池也没有用。 +0901:反馈无OTA日志，请用户尝试重启车辆，在户外信号较好的地方重试OTA +0825:反馈“在OTA时，汽车在一小时后死机并关闭。当点火开关打开时，主屏幕显示软件已加载99%，但主屏幕无法正常工作”，转OTA分析","10/09: solved +09/09：Post-conference synchronization with the profession +08/09: we ordered new dmc ecu, because restart doesn't help, the customer sees 99% every time, unclamping battery also doesn't help. +01/09:Feedback no OTA log, please user try to restart the vehicle, retry OTA in outdoor places with good signal. +25/08:Turn OTA analysis.",Low,close,OTA,刘金龙,10/09/2025,EXEED VX FL（M36T）,LVTDD24B6RD083970,,,image.png,Evgeniy Ermishin,,,,,,16 +TR774,Mail,27/08/2025,,Problem with auth in member center,QR code doesn't exist. DMC SW is the lattest (by OTA),"1014：无反馈 - TSP 登录/注销正常 - > 暂时关闭 +0925: 等待日志中 +0916: 等待客户进站抓取DMC日志分析 +0828：反馈无会员中心二维码，车辆主机版本已是最新,车辆有4G信号显示，PKI仅有一条报错，已告知抓取主机日志分析","14/10: no feedback - in TSP login/logout is ok - > temporary close +18/09: asked again +0916：Wait for the customer to dealer to capture the DMC log for analysis @Evgeniy Ermishin +28/08: feedback no member center QR code, vehicle host version is the latest, the vehicle has a 4G signal display, PKI only one error, has been told to capture the host log analysis.",Low,temporary close,生态/ecologically,Evgeniy Ermishin,14/10/2025,EXEED RX（T22）,LVTDD24B7RG019273,,,"image.png,175623312897551013264376.mp4",Evgeniy Ermishin,,,,,,48 +TR777,Mail,28/08/2025,,Traffic is over,Abnormal traffic consumption,"1030:有无进展？能否转状态为等待数据 +1023:建议客户进站抓取DMC和TBOX日志 +1016:建议客户进站抓取DMC和TBOX日志 +0930:等待DMC和TBOX日志 +0916: 等待DMC及TBOX日志分析 +0828:已初步分析，平台无法远程获取TBOX日志，建议用户进站抓取DMC及TBOX日志。回传国内分析","30/10: temporary close. If issue again, TR will be re-opened. +30/10:Any progress? Can you change the status to waiting for data @Vsevolod Tsoi +23/10: Advise customers to go in and grab DMC and TBOX logs. +21/10：Advise customers to go in and grab DMC and TBOX logs. +16/10: Advise customers to go in and grab DMC and TBOX logs. +30/09: Waiting for DMC and TBOX log for analysis +16/09: Waiting for DMC and TBOX log for analysis +28/08: Has been initially analyzed, the platform can not remotely obtain the TBOX logs, it is recommended that users enter the station to capture the DMC and TBOX logs. Back to domestic analysis.",Low,temporary close,DMC,Vsevolod Tsoi,30/10/2025,EXEED RX（T22）,XEYDD14B3RA004401 ,,,"img_v3_02pc_e8920289-8845-48ee-a27a-efddc3caechu.png,img_v3_02pc_3aeab68a-d3ed-4122-a673-798695e917hu.png",Vsevolod Tsoi,,,,,,63 +TR782,Telegram bot,01/09/2025,,Traffic Payment,"""Transaction not completed""","0902：TBOX侧建议用户或经销商重启车辆TBOX，或者锁车休眠后再上电 +0901：转TBOX及辛巴分析，反馈短信下发失败，明日核实原因 +0901：反馈用户续费后，仍然无流量，已远程下发TBOX重启指令，等待客户反馈，属地运维表示客户已付款，但实车流量未恢复。","16/09: No feedback, solved according to status on CMP - closed +02/09: TBOX Side It is recommended that the user or dealer reboot the vehicle's TBOX, or lock the vehicle and hibernate before powering up +01/09: Turned to TBOX and Simba for analysis, feedback on SMS downlink failure, verifying cause tomorrow +01.09 - Transaction not competed, ON CMP traffic is ok. However, customer dont have acces to the net -> TBOX was rebooted remotly, waiting for customer feedback, Please check on your side. Customer paid for package - it's urgent +CMP management platform +CMP management platform +(Also check attachments)",Low,close,TBOX,王桂玲,16/09/2025,EXEED VX FL（M36T）,LVTDD24B9RD031863,,TGR0003515,"image.png,image.png,image.png",Kostya,,,,,,15 +TR783,Telegram bot,03/09/2025,,Application,User can't bind his car in the app. An error message "A07913" comes when trying to bind the car (see picture attached). Note: car is not bound in TSP.,"0918：暂无反馈，临时关闭。如果有问题再次开启。 +0916: APP后台没有查看到解绑申请的记录，目前绑定的号码仍然是“79228125091”, 和TSP上绑定的账号一致，如果客户想要更换绑车账号，建议客户申请二手车换绑到新账号。或者先登录“79228125091”解绑，之后再用新号码绑定。 +0903：用户提交解绑审核通过后，再次登录出现A07913报错，请转数跑排查分析","18/09: still no feedback => temporary closed. If any issue, it will be reopened. +16/09: checked in TSP - vehicle is now bound before wasn't. User has been asked whether the issue is solved. +0916: No record of unbinding application was found in the APP backend. Currently, the bound number is still ""79228125091"", which is same with the account on TSP. If the customer wants to change the car binding account, it is recommended that the customer apply for a second-hand car to be bound to a new account. Or customer can first log in with ""79228125091"" to unbind car, and then bind it with the new number. @Vsevolod Tsoi +03/09:After the user submits the unbinding audit and passes, logging in again, there is an error A07913, please turn the number of running troubleshooting analysis",Low,temporary close,用户CHERY-APP(User),岳晓磊,18/09/2025,CHERY TIGGO 9 (T28)）,LVTDD24B4RG088552,,TGR0003448,file_4245.jpg,Vsevolod Tsoi,,,,,,15 +TR785,Telegram bot,03/09/2025,,Remote control ,"Vehicle data is not displayed in the mobile application. Neither the VK service nor the weather application is functional, except for navigation (see attached image). Since the SIM card activation on July 29, the TBOX has been unable to log in. ICC login is functioning normally. +移动应用程序中没有反映车辆数据。除导航外，VK 服务和天气应用程序均无法使用（见所附图片）。自 7 月 29 日 SIM 卡激活以来，TBOX 无法登录。ICC 登录正常。","1118：建议U盘更新最新TBOX'软件，已提供升级包 +1111：下一步计划？ +1105：已检查TBOX错误代码 => 未发现错误。此前已设置模式""2""。 +那么下一步计划是什么？ +1101：已向经销商发送请求： +1. 读取TBOX故障代码（若存在） +2. 将TBOX模式设为""2""——具体操作需由二级支持团队提供指导。 +1023：目前尚未收到反馈。 +1021：暂无反馈 +1014：等待客户进站退出工厂模式反馈 +0928: 日志显示获取VIN为空。怀疑车辆TBOX未退出工厂模式。请邀请客户进站使用诊断仪读取实车TBOX设置，退出工厂模式。配置完后重启TBOX就行了。 +0925：等待合规流程结束后，发送日志给专业分析 +0918: 等待日志后分析 +0915: TBOX和ICC日志的请求已发送给经销商。等待数据传送给相应的工程师进行分析。 +0903:建议用户进站检查实车tbox ，并抓取主机及tbox日志","18/12: remote control as well as operation of the VK apps were restored. Issue solved. Finally no upgrade of TBOX SW has been done with USB. +18/12: the istructuion has been prepared and the request for TBOX SW upgrade with USB has been sent. +15/12: instruction will be prepared within today and then a request will be sent to the dealer. +11/12: preparation of a guide for upgrading the TBOX SW with USB is still in process. +09/12: the instruction will be prepared within this week and then a request for Tbox upgrade using an USB interface will be sent to the dealer. +04/12: pending. +02/12: preparation of an instruction is pending. +27/11: preparation of the instruction is still in process +25/11: instruction is provided by the 2nd line. Preparation of the instruction for TBOX SW upgrade with an USB flash drive for dealer is in progress. +20/11: wait for an instruction to be agreed with ASD. Once agreed, it will be sent out to ther dealer for upgrade. +18/11: any progress ?--------18/11: We recommend updating the TBOX software to the latest version via USB drive. The upgrade package has been provided. +11/11: next steps? +05/11: TBOX was checked for errors => no errors were found. Mode ""2"" was setup before. +So, what are the next steps? +01/11: a request has been sent to the dealer for: +1. reading the fault codes of TBOX if they are: +2. Set TBOX mode to ""2"" - an instruction to provide by 2nd line support team. +23/10: no feedback so far. +21/10: feedback is pending. +16/10: feedback pending. +13/10: a request for setting TBOX in normal mode has been sent to a dealer. Wait for feed-back. +09/10: request to dealer is on process. +0928: The log shows that the VIN obtained is empty. It is suspected that the vehicle TBOX has not exited the factory mode. Please invite the customer to dealer to use the diagnostic to read the actual vehicle TBOX Settings and exit the factory mode. After configuration, restart TBOX and the problem will be solved. @Vsevolod Tsoi +24/09: TBOX and ICC are attached to the TR. Photo with ICC SW version is also attached. +22/09: wait for data from dealer. +15/09: request for TBOX as well as ICC log have been sent to dealer. Wait for data to be trasfered to respective eningeer for analysis. +11/09: wait for customer's contact data being able to make a request for invitation of customer to dealer. +03/09:It is recommended that users enter the station to check the actual car tbox, and grab the host and tbox log.",Low,close,TBOX,刘娇龙,18/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ8SD152606,,TGR0003459,"log.mega.co.zip,20250924155708_tboxlog.tar,ICC_SW_version.jpeg,file_4320.jpg,file_4319.jpg,file_4257.jpg,file_4256.jpg",Vsevolod Tsoi,,,,,,106 +TR786,Autosales team (dealer),03/09/2025,,OTA,"""No connect"" status for activated exlantix ET cars in FOTA","0904：已核实清单中均为最新版本CBU。无需升级，所以ota平台显示未连接 +0903：反馈无法进行FOTA，显示为连接状态，主机无登陆记录，已尝试重启主机，但TSP上始终无登录记录，请查看附件中的受影响车辆清单，已上传其中一辆车在 FOTA 中的日志截图。","05/09: Info provided to the ASD, please update the maping for info about versions of blocks on EOX on FOTA, because right now we cant check current versions on E0X by report fucntion, Only via logs, and manually for every car. @赵杰 +04/09: It has been verified that the listings are of the latest version of CBU. no upgrades are required, so the ota platform is showing no connection. +03/09:""No connect"" status for activated exlantix ET cars in FOTA. Cars can't get the update +checked the info in the TSP -> Everything ok execpt the DMC login +Tried to reboot dmc too. Pls Check the attachment for list of affected cars and screen of logs from one car on FOTA",Low,close,OTA,王冬冬,05/09/2025,EXLANTIX ET (E0Y-REEV),Not one,,,"image.png,image.png,et.xlsx",Kostya,,,,,,2 +TR788,Telegram channel,04/09/2025,,Remote control ,Vehicle Preparation Set - Timeout. Operation date/time 09.04 at 8:07 -see screenshot. Tbox log is attached,"0909：客户反馈已正常，可关闭该问题 +0905：该车已核实无此配置，已去除异常数据，请用户重新尝试 +0904：一键备车远控失败，提示超时，转国内分析，已有TBOX日志","05/09: ""Now the menu item related to setting the autorun schedule has disappeared from the application altogether."" +05/09: This vehicle has been verified as not having this configuration, abnormal data has been removed, please try again! +04/09:Vehicle Preparation Set the remote control of the car failed, prompted a timeout, turn to the domestic analysis, there are TBOX logs",Low,close,local O&M,Evgeniy Ermishin,09/09/2025,OMODA C7 (T1GC),LVUGFB221SD831200,,,"LOG_LVUGFB221SD83120020250904111905.tar,20250904-112330.png,image.png",Evgeniy Ermishin,,,,,,5 +TR791,Mail,08/09/2025,,Application,No binding the car is possible. An error message "A07913" comes up upon trying to bind the car.,"0917: 开发人员已从TSP清除绑定关系，请邀请客户重新绑定确认 +0916: 星途APP后台无车辆绑定关系，TSP平台存在绑定关系，已发送邮件给TSP开发清除TSP绑定关系 +0909:已知问题，确认userid及渠道id后转用户app修改","22/09: user's feedback - issue is sorted out. TR closed. +18/09: user has been asked to try again. Wait for feedback. +0917: The developer has cleared the binding relationship from TSP. Please invite the customer to rebind @Vsevolod Tsoi +09/09: Known problem, confirm the userid and channel id and then transfer the user app to modify",Low,close,用户EXEED-APP(User),岳晓磊,22/09/2025,EXEED RX（T22）,XEYDD24B3RA008657,,,03bd7ea8-3cee-479b-ba9f-4682d1eff2f2image1757081414004.jpg,Vsevolod Tsoi,,,,,,14 +TR795,Mail,10/09/2025,,OTA,"OTA upgrade failed. Every time when trying to upgrade, it fails at 6% out of 100 and then an error message ""Vehicle is out of service. Usage is not allowed"" comes up - see picture attached. DMC logs as well as OTA are attached.","0917: OTA失败的原因是蓄电池电量不足和在工程模式里点了“检测前置条件”导致失败 +0910：OTA分析结果如下：车辆开始DMC没学sk导致上电失败，中间是蓄电池电量不足 导致失败，后面是工程模式里点了“检测前置条件”导致失败 +措施： +1.学习DMC的sk； +2.蓄电池充半个小时电； +3.工程模式里的“检测前置条件” 不要点击，正常点击检查更新 然后回到ota主界面执行升级 +0910：OTA 升级失败。每次尝试升级时，100 次中有 6% 都会失败，然后出现错误信息 ""车辆不在服务区。不允许使用""--见附图。DMC 日志和 OTA 均附后。","0917：The reason for the OTA failure is that the battery power is insufficient and the ""Detection Preconditions"" were clicked in the engineering mode, which led to the failure， same reason as before. @Vsevolod Tsoi +16/09: dealer's feedback: DMC learning with SK had been performed but the OTA uprade had been failing several times as decribed before. Then, one day dealer started collecting OTA log, the OTA upgrade suddenly started being launched and then completed successfully. Root cause is unknown. The issue is solved now. +10/09: OTA logs are attached. +10/09：OTA analysis results are as follows: the vehicle did not learn sk at the beginning of the DMC, which led to power-up failure; in the middle of the failure was caused by insufficient battery power; in the back of the failure was caused by clicking ""Detect preconditions"" in the engineering mode. +Measures: +1. Learn DMC sk. +2. Charge the battery for half an hour; +3.Don't click the ""detect precondition"" in engineering mode, click check update normally and then go back to ota main interface to execute the upgrade.",Low,close,OTA,韦正辉,17/09/2025,EXEED RX（T22）,XEYDD14B3RA004594,,,"carota_09.09.25.zip,carota_10.09.25.zip,logs_20250909-174548.zip,OTA_failed.jpg",Vsevolod Tsoi,,,,,,7 +TR796,Telegram bot,10/09/2025,,doesn't exist on TSP,No vehicle data is available in TSP => no binding the vehicle is possble.,"16/09：收集TBOX&DMC数据的请求正在准备中，将于今天发送。 +0911：同TR797，建议用户进站读取实车信息。包含：物料号，TBOXSN，ICCID，IHUSN +0910:同步DRE与MES，核查车辆信息缺失原因","18/09: feedback from product team - these both cars are not equipped wit IOV. TR closed. +18/09: request is still on process. +16/09: request for collecting TBOX&DMC data is being prepared and is gonna be sent within today. +11/09：same as TR797,Users are advised to come into the station to read the actual car information。Contains: Material Number, TBOXSN, ICCID, IHUSN +10/09: one more car is added in TR. +10/09:Synchronize DRE with MES to verify reasons for missing vehicle information",Low,close,local O&M,Vsevolod Tsoi,18/09/2025,JAECOO J7（T1EJ）,"EDXDB21B4SC051797 +EDXDB21B9SC050855",,,,Vsevolod Tsoi,,,,,,8 +TR797,Telegram bot,10/09/2025,,doesn't exist on TSP,No vehicle data is available in TSP => no binding the vehicle is possble.,"0918：等待前方提供数据 +0911：地产化件，海外工厂侧无法提供信息，建议用户进站获取物料号，TBOXSN，ICCID，IHUSN +0910：与MES核实相关信息","22/09: TBOX&DMC data have finally been provided by AGK plant and the imported into TSP. TR closed. +18/09: request to dealer was send for providing data +11/09：Realized parts, overseas factory side can't provide information, suggest users to get material number, TBOXSN, ICCID, IHUSN. +10/09: Verify relevant information with MES",Low,close,local O&M,Evgeniy Ermishin,22/09/2025,CHERY TIGGO 9 (T28)）,EDEDD24B6SG018288,,,{6F6DE11C-77C1-4DE1-9D23-2842331056A4}.png,Evgeniy Ermishin,,,,,,12 +TR798,Telegram bot,11/09/2025,,Application,"there is no coonect between DMC-TSP platform, can not load QR code. No log in DMC","1027:客户没有答复，建议暂时关闭 +1021:已向客户发送提醒,暂无回复 +1015: 已向客户发送提醒,暂无回复 +0930：等待DMC日志 +0923：客户尝试重置车机仍然无反馈，需DMC日志 +0911:建议属地联系用户，尝试恢复DMC出厂设置，查看是否可以恢复并显示会员中心二维码","27/10 No answer from the customer, suggest to temporary close +21/10: No answer from the customer, reminder was sent +15/10: Reminder to customer was sent +23/09: Customer tries to reset the DMC still no feedback，need DMC logs +11/09: It is recommended that you contact the local user to try to restore the DMC factory settings to see if it can be restored and display the QR code of the member center. @Sergei Antipov",Low,temporary close,生态/ecologically,,28/10/2025,CHERY TIGGO 9 (T28)）,LVTDD24B4RG118780,,TGR0003639,file_4439.jpg,Sergei Antipov,,,,,,47 +TR801,Mail,12/09/2025,,Traffic is over,Abnormal traffic consumption,"1120:后续客户面临流量异常消耗时，可引导用户抓取DMC日志分析，日志会更加详细 +1118:ota成功，建议联系用户反馈进展。 +1111：监控功能预计将于十一月发布。 +1106：是否已确定发布日期？ +1101：用于流量监控功能的OTA更新正在等待发布。 +1023: 等待 OTA 流量监控功能的发布。 +1021：等待流量监控功能预计在 10 月发布 +1015：经核实信息存在延迟，问题已修复，但流量异常消耗需待主机流量监控功能上线后再行分析。 +1014: 调查仍在进行中。等待流量监控功能 +0916：收到反馈。由于额外的消费原因，额外提供给客户5GB修复不同步MNO<=>SIMBA预计将在10月。额外的流量消耗仍在调查中。 +0911:反馈流量异常，属地已向辛巴反馈","02/12: temporary closed. Once the issue occurs, it will be re-opened. +25/11: upgrade completed on Nov, 15. When the issue occurs, ICC log will be requested. +20/11: When subsequent customers encounter abnormal traffic consumption, guide them to capture DMC logs for analysis, as these logs provide more detailed information. +18/11:OTA successful. +18/11: still wait for release monitoring function. +11/11: monitoring function releae is exepcted in November. +06/11: is a date of release alredy known? +01/11: release of an OTA for traffic monitoting function is pending. +23/10: waiting for release of an OTA traffic monitoring function. +21/10: wait for traffic monitoring function release expected in October +15/10: It has been verified that the information is delayed and the problem has been fixed, but the abnormal consumption of traffic needs to wait for the host traffic monitoring function to go on line before further analyzing it +14/10: ivestigation is still on process. +16/09: feedback was received. 5GB has additionally been provided to customer for an extra consumption reason. Fix of disynshronization MNO<=>SIMBA is expected to be in October. Extra consumption of the traffic is still under investigation. +11/09: a request has been sent to SIMBA and MNO.",Low,temporary close,MNO,胡纯静,02/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ4SD226832,,,,Vsevolod Tsoi,,,,,,81 +TR802,Mail,12/09/2025,,Problem with auth in member center,QR code doesn't exist,"0930:等待客户进站后反馈 +0923：等待信息中 +0918：任然等待信息 +0915：车机SN和TBOX SN写反了，请邀请客户进站用诊断仪重新修改， +0912反馈会员中心无二维码，已提供工程模式截图，已要求客户进站提供日志","18/09: no feedback yet from dealer, will ask again +0915:Vehicle IHU SN and TBOX SN are written in reverse, please invite the customer into the station with a diagnostic device to re-modify, learning SK @Evgeniy Ermishin +12/09: asked to dmc log ",Low,temporary close,生态/ecologically,袁清,09/10/2025,OMODA C7 (T1GC),LVUGFB227SD830942,,,"image.png,image.png,image.png,image.png",Evgeniy Ermishin,,,,,,27 +TR803,Mail,15/09/2025,,Traffic is over,"Abnormal traffic consumption +异常流量消耗","1106：等待DMC logs +1031：不行，因为DMC日志的请求已于10月29日发出。 +1030：能否转为等待数据状态 +1023：等待主机日志 +1021：等待主机日志 +1014：等待主机日志 +0923： +1.尽可能抓取主机日志 +2.等待新版本释放流量监控软件，具体时间待同步 +0916: 流量大量消耗时间8.30日和9.3日。辛巴反馈目前看流量是客户正常消耗，请跟客户了解这两天使用了什么应用，最好是邀请客户建站抓取DMC日志后进一步排查。 +0915：转辛巴排查","02/12: no feedback=> temporary closed. +27/11: no customer's feedback so far +25/11: wait for customer's confirmation that the issue can be closed. +20/11: DMC log pending. +18/11: a reminder has been sent to ASD department. +11/11: DMC log is pending +06/11: no DMC logs received so far. +31/10: no, we can't since a request for DMC log was sent on October, 29 +30/10：Can we change the status of this issue to waiting for data? @Vsevolod Tsoi +23/10: waiting for DMC logs +21/10: waiting for DMC logs +14/10: waiting for DMC logs +23/09: +1. Grab DMC logs as much as possible +2. wait for the new version to release the traffic monitoring software, the exact time to be synchronised +16/09: Traffic consumption on 8.30 and 9.3. Simba feedback so far looks like the traffic is normal consumption by the customer, please talk to the customer to find out what applications were used in the past two days, it is best to invite the customer to dealer to capture the DMC logs for further investigation. ",Low,temporary close,MNO,胡纯静,02/12/2025,OMODA C7 (T1GC),LVUGFB229SD831011,,,"LOG_LVUGFB229SD83101120250915120027.tar,image.png,image.png,image.png",Vsevolod Tsoi,,,,,,78 +TR804,Mail,16/09/2025,,Network,"There is no icon 4g on the right up corner in IHU + It is impossible to record TBOX log and get all the data about TBOX in engineering menu. The dealer has already checked all harnes connection between DMC and TBOX +checked tbox normal mode. +We want to change tbox HW. Please give us confirmation from HQ side. +IHU右上角未显示4G图标，且无法在工程菜单中记录TBOX日志及获取所有TBOX相关数据。经销商已检查DMC与TBOX间所有线束连接，并确认TBOX处于正常模式。 +我们计划更换TBOX硬件，请总部予以确认。","1118: TBOX已变更 - 正在导入新数据 +1111:等待ASD反馈 +1027： 向 ASD 小组再次催促，以提供信息 +1024：已向 ASD 发出催复通知，经销商告知没有要求更换 T-BOX，ASD 已跟进该要求。 +1022：请更新属地进展. +1021：会后更新进展 +1014: 该车的国内VIN为 LVTDD24B7RD010509。问题是经销商在新 TBOX 上写错了 VIN。 +0930 ：等待更换TBOX +0925：等待更换TBOX +0917：请邀请客户进站更换TBOX +0916:转国内TBox专业","18/11: TBOX changed - importing new data - Added, TR closed +11/11: Waiting for feedback +27/10 Second letter was sent to the ASD team to provide information +24/10: Reminder to ASD sent, dealer infromed that there was not request to change T-BOX, The request was followed up by ASD +23/10: it was figured out that there were no TBOX change done. Request for changing TBOX has been followe up to ASD team. Wait for feedback. +22/10:Please update progress on local side. +21/10：Post-session update on progress.@Evgeniy Ermishin +14/10: car has chinese VIN in dmc LVTDD24B7RD010509. problem is that the dealer wrote wrong VIN in new TBOX. +18/09: request for changing tbox was send +17/09: Please invite the customer to dealer for TBOX replacement. +16/09: waiting for confirmation of changing TBOX",Low,close,TBOX,王桂玲,19/11/2025,EXEED VX FL（M36T）,XEYDD14B1RA006307,,TGR0003552,"1000052740.jpg,1000052741.jpg,1000052742.jpg,image.png,image.png,2025-09-11 13.44.29_корп.3, 8, Торфяная дорога.mp4,1000052745.jpg,1000052749.jpg,1000052744.jpg,1000052750.jpg,1000052747.jpg,1000052748.jpg,1000052743.jpg,1000052746.jpg",Kostya,,,,,,64 +TR806,Mail,16/09/2025,,Remote control ,Wrong data in app,"0924：GPS信号干扰引起的数据时序错误，可以让客户重启车辆等待一段时间数据会恢复正常。长期措施：下个tbox版本会修复这个问题。预计11月底完成。 +0917：TSP平台看目前数据已经恢复正常，请跟客户确认APP上数据是否正常。异常原因仍在分析中 +0916:Exlantix 应用程序中的数据错误，TSP 中的数据也错误, 转国内TBOX分析","14/10: solved +09/10: please explain more detailed what does it mean ""restart vehicle?"" +0924: Data timing error caused by GPS signal interference, could suggest that customer restart the vehicle and wait for some time the data will be back to normal. Long term measure: This issue will be fixed in the next t-box version. @Evgeniy Ermishin +0917: According to the TSP platform, the current data has returned to normal. Please confirm with the customer whether the data on the APP is normal. The cause of the anomaly is still under analysis @Evgeniy Ermishin +16/09: wrong data in Exlantix app, also wrong data in TSP",Low,close,TBOX,刘娇龙,14/10/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ1SD233558,,,"img_v3_02q6_4c15a710-917c-46c0-9b8d-923231f2afhu.png,20250916-163807.mp4,LOG_LNNBDDEZ1SD23355820250916163450.tar,img_v3_02q6_e78ad7c6-3acb-4b2b-a1e3-d5761114e5hu.jpg",Evgeniy Ermishin,,,,,,28 +TR807,Mail,16/09/2025,,OTA,"TBOX OTA upgrade is still not available on the vehicle. However, DMC OTA upgrade had been completed + weather app doesn't work. Permition to trasmit the location for Weather app is allowed in the system settings - see picture attached. PKI is also OK - see picture attached as well. +TBOX OTA升级在车辆上仍然不可用。然而，DMC OTA升级已经完成；天气应用程序不工作。允许在系统设置中传输位置-见附件图片。PLI也可以-看附图。","0919：天气问题是因为服务器资源不足，目前已恢复。通过OTA日志查看是TBOX的问题，请建议客户尝试断开12V电池连接并等待3分钟后,重新连接电池看是否恢复。 +0917：请邀请客户进站抓取DMC日志 +0917：转OTA分析和生态分析","23/09: after taking battery terminals off OTA upgrade had been restored and then installed that restored remote control operation. +22/09: wait for feedback from dealer when it could be checked. +19/09: the request for taking battery terminals off has been sent to dealership. Wait for feedback. +0919: Weather problem is due to insufficient server resources, it has been recovered. Through the OTA log to see is the TBOX problem, please suggest customers try to disconnect the 12V battery and wait for 3 minutes, reconnect the battery to see if it is restored.@Vsevolod Tsoi +19/09: weather app operation was restored. +18/09: DMC log was already attached before you asked for. +0917: Please invite the customer todealer to capture the DMC log",Low,close,OTA,韦正辉,23/09/2025,EXEED RX（T22）,LVTDD24B0RG019261,,,"DMC_log_20250918-132501.zip,Weather_transmit_permitions.jpeg,PKI_status.JPG",Vsevolod Tsoi,,,,,,7 +TR808,Telegram bot,16/09/2025,,Problem with auth in member center,"Customer loged out of his account in ICC by an accident and now he can't enter into member center with QR code because it doesn't display. A message ""Poor connection"" comes up instead of. +客户不小心注销了他在ICC的账户，现在无法用二维码进入会员中心，因为二维码不显示。出现“连接不良”的消息","0923：现在不清楚用户具体问题是什么 +0918:请邀请客户进站抓取DMC日志和拍摄操作视频 +0918: 二维码不显示转生态分析。","22/09: now it's not clear what issue customer has +0918: Please invite customer to capture the DMC log and shoot a operation video.@Vsevolod Tsoi +18/09: user was asked to do the following actions but it didn''t bring any result => QR code still doesn't download: +1) Delete his vehicle of mobile app; +2) Log out of his account; +3) Reboot ICC; +4) Relog in mobile app account; +5) Try to enter in member center with QR code but it doesn't appear. +What I noticed: when implementing the 1st step, the vehicle was well uncertified in the legend platfrom however it still left bound in TSP that is I would say not normal.",Low,temporary close,生态/ecologically,袁清,25/09/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ2SD099496,,TGR0003527,,Vsevolod Tsoi,,,,,,9 +TR809,Telegram bot,18/09/2025,,Remote control ,"Vehicle date is not reflected on the APP, vehcile has been boun on TSP platform, but on MNO side - something went wrong. +车辆信息并未在app中显示，车辆已在 TSP 平台上完成绑定，但在移动运营商这边却出现了问题","0925: 前方反馈该问题已恢复， +0924：等待客户反馈是否恢复正常 +0924: 辛巴侧排查卡状态已恢复正常，APN1/APN2均已流量消耗记录，T-BOX登录和远控均正常，无主机登录记录。 +0923：问题仍然存在 +0923:运营商已处理恢复正常，请跟客户确认 +0922：运营商内部系统出了点问题，在加急处理中，等待反馈 +0919: 卡激活有问题，等待辛巴处理 +0918:车辆9月17日激活后没有tbox和车机登陆记录，转国内分析","0925：customer informed that problem was solved +0924: Wait for customer feedback on whether it has returned to normal +0923: The operator has processed it and returned to normal. Please confirm with the customer. +2.issue still exist. +0922: There is a problem with the internal system of the operator. It is being dealt with urgently and waiting for them feedback +18/09: No T-box login since activation from september 17.",Low,close,DMC,沈世敏,25/09/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ0SD391289,,TGR0003773,"image.png,image.png",Sergei Antipov,,,,,,7 +TR810,Telegram bot,18/09/2025,,Navi,"Does not work NAVI from IHU for the long period of time. It happens in all regions even that signal is stable. Dealer restarted the system, but it had not helped. +IHU的NAVI长时间不工作。即使信号稳定，在所有地区都不可用。经销商重新启动了系统，但没有用。","1211:等待TBOX换件 +1209:等待TBOX换件 +1202:等待TBOX换件 +1127：请求已发送 -> 等待中 +1125：为T1EJ准备说明 +1122：请明确说明，是否因客户无法使用地理位置功能而需要更换我们的TBOX（用于远程控制和网络）？===已解释 +1113:国内专业反馈该问题的TBOX版本较老，且不是版本必现问题，建议属地换件TBOX、 +1104：初步分析结果：卫星数量都是0，需要主机或者TBOX先进行分析一下。已经获取到T-box日志，转T-BOX工程师分析 +1030 :日志分析中(因为没有明确时间点，需要逐步分析,可能要相对久一点) +1027：日志已附，转国内分析 +1020：未查看到附件的DMC——logs，请再次上传 +1016：未查看到附件的logs，请再次上传 +0925：已邀请客户进站，等DMC日志中 +0922：对tbox日志分析该车辆17-18日均有有效定位输出，信号良好。等待DMC日志后进一步排查 +0918: 从视频上看是没有定位的问题，请邀请客户进站检查下GPS模块并抓取DMC日志 +0918:导航不可用，转国内生态分析","18/12: Waiting for TBOX replacing - new status woulc be added after replacing +11/12: Waiting for TBOX replacing +09/12: Waiting for TBOX replacing +02/12: Waiting for TBOX replacing +27/11: Request has been sent -> waiting +25/11: Preparing isntructions for T1EJ +22/11: Please make it clear, should we replace our TBOX (for remote control and net) because of customer cant use geopossition feature? ===Has been explained +18/11: Request sent +13/11: Domestic technical feedback indicates the TBOX version involved in this issue is outdated, and it is not a version-specific problem. It is recommended to replace the TBOX locally.@Kostya +11.11: Waiting +04/11：Preliminary analysis results: The number of satellites is 0, requiring the host or TBOX to perform an initial analysis first. T-box logs have been obtained and transferred to T-BOX engineers for analysis. +30/10:Log analysis in progress(Because there is no clear point in time, it needs to be analysed step by step, and may take a relatively long time)@Kostya TR810, could you please ask the customer about the approximate date when this issue occurred? Since there are quite a few logs, it would be faster to troubleshoot if we have the time point when the issue occurred. +27/10: Log attached, transferred to domestic analysis . +27/10 Logs in attachments +20/10 Customer will be sent to the dealer to take logs on 24/10 +1020: Attached DMC logs not viewed, please help upload again @Sergei Antipov +1016: Attached logs not viewed, please help upload again @Sergei Antipov +1003 logs provided (in the attachment) +0925: Customer invited to the dealer, to take logs +0923：need dmc logs +0922: The tbox log analysis shows that the vehicle has effective positioning output on both the 17th and 18th, with good signals. Wait for the DMC log for further investigation +0918: from the video, there is no positioning problem. Please invite the customer to dealer to check the GPS module and grab the DMC log.@Sergei Antipov +16/09: The customer provided inforamtion about issue with NAVI",Low,Processing,生态/ecologically,袁清,18/09/2025,JAECOO J7（T1EJ）,LVVDD21B8RC053807,,"TGR0003749 +Дилер: Максим 89166270073","logs_20251024-190332.zip,Tgr 2.jpg,Tgr1.jpg,file_4579.mp4,image.png",Kostya,,,,,,0 +TR813,Mail,19/09/2025,,VK ,"VK services do not start. A message ""Activation is on process"" comes up when starting and then nothing happens (see video attached). +VK 服务无法启动。启动时会出现 ""激活正在进行中 ""的提示，然后就什么也不发生了（见所附视频）。","1016：暂无日志反馈，建议转成等待数据状态 +0930：等待DMC日志 +0919：无主机登录记录，辛巴侧排查流量卡状态正常，转国内DMC分析，等待DMC日志 +0919: 已申请 ICC 日志。 +9 月 15 日购买了 10GB 的额外流量，但自此之后在 MNO 中未发现任何流量消耗。是网络接入问题吗？","02/12: VK video was restored +28/11: same as TR901 - the user was asked to provide a feedback whether the apps were restored. +20/11: temporary closed. +18/11: logs still pending. +11/11: logs pending. +06/11: no ICC log received so far. +01/11: logs are still pending. +23/10: logs pending. +21/10: still no logs received. +16/10: No log feedback available. It is recommended to transition to the waiting for date status. +14/10: No ICC log so far. +09/10: ICC log is pending. +25/09: wait for receiving the ICC log. +22/09: ICC log is pending +19/09:No host login records. Simba side confirmed the data card status is normal. Case transferred to domestic ICC for analysis. Awaiting ICC logs. +19/09: ICC log has been requested. +Additional traffic 10GB has been purchased on September, 15th but no traffic consumption found in MNO since this date. An issue with the access to the network?",Low,close,生态/ecologically,高喜风,02/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ8SD154646,,,"Логи Тихненко.zip,IMG_9201.MOV",Vsevolod Tsoi,,,,,,74 +TR814,Mail,19/09/2025,,doesn't exist on TSP,IOV activation is not possible due to missing vehicle data in TSP.,"0922: 从MES系统中也未查询到车辆的信息，请再确认VIN是否正确，或者邀请客户进站进入工程模式读取数据 +0919:tsp中缺少车辆信息，转国内MES分析","22/09: vehice data has been provided by AGK plant and then imported into TSP. +19/09: woud you be able to update TSP platform with this vehicle?",Low,close,MES,徐辉文,22/09/2025,CHERY TIGGO 9 (T28)）,EDEDD24B6SG018288,,,Picture_1.jpg,Vsevolod Tsoi,,,,,,3 +TR815,Telegram bot,19/09/2025,,Application,User cant bind the car in the mobile app,"1024:已修复app相关错误数据，请告知用户重试，如验证通过可关闭该问题 +1014：请更新状态 +0919:绑车提示A07913,转数跑处理","24/10: car finally bound, remote control restored. +24/10:App related error data has been fixed, please inform the user to retry, if the validation passes you can close the issue. +21/10: Please update status +14/10: Please update status +19/09:Tying up the car prompts A07913, turn number run processing",Low,close,用户EXEED-APP(User),岳晓磊,24/10/2025,EXEED RX（T22）,LVTDD24B5RG032670,,TGR0003373,img_v3_02q9_0f224463-e4bf-42e0-83a9-f1d52b2a45hu.jpg,Kostya,,,,,,35 +TR816,Telegram bot,23/09/2025,,PKI problem,"NAVI PKI issue on T1EJ - the same as on T22 +T1EJ 上的 NAVI PKI 问题 - 与 T22 上的相同","1009: 等待反馈 +0925：请帮助确认DMC和导航应用的版本信息 +0924：转国内PKI团队分析","1009: Wait for feedback +0930:In procces +0925: Please help confirm the version info of DMC and navigation application",Low,Waiting for data,PKI,Kostya,,JAECOO J7（T1EJ）,LVVDD21BXRC148207,,TGR0003849,image.png,Kostya,,,,,, +TR819,Mail,24/09/2025,,Traffic is over,"Extra traffic comsumption +流量消耗异常","暂无进展，该类异常消耗详细见TR1039分析进展 +1118:ota成功，建议联系用户反馈进展。--需要等待用户复现后，抓取对应的IHU日志 +1111：监控功能预计将于十一月发布。 +1106：是否已确定发布日期？ +1101：用于流量监控功能的OTA更新正在等待发布。 +1028：等待 OTA 流量监控功能的发布。 +1021: 等待新的流量监控功能 +1014：问题定位解决后补偿客户流量（避免再次消耗） +0930：等待日志 +0924：转国内分析，请尽快帮忙抓取DMC日志，避免日志被覆盖","02/12: DMC Logs under analysis +27/11: pending - new case after update +25/11: pending - new case after update +18/11:OTA successful. We recommend contacting the user to provide progress updates. +11/11: monitoring function releae is exepcted in November. +28/10: waiting for new traffic monitoring function +21/10: waiting for new traffic monitoring function +14/10: Compensate customers for traffic (to avoid re-consumption) after the problem is localised and resolved +14/10: waiting for new traffic monitoring function +24/09：Please help grab the DMC logs as soon as possible to avoid them being overwritten @Evgeniy Ermishin",Low,Processing,MNO,林希玲,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ0SD163230,,,image.png,Kostya,,,,,, +TR824,Mail,29/09/2025,,Problem with auth in member center,QR code doesn't exist,"11.06：未收到用户反馈，系统显示一切运行正常，流量消耗超出平均远程信息处理速率→应用程序应可正常运行→暂时关闭 +1030:需要检查车端主机时间同步是否正常，是否时间显示为当地时间 +1023:会后确认，告知DRE转入分析流程 +1021:附件中的 Tbox 日志和 DMC 日志 +1020:建议用户重新尝试后，如无法恢复，请抓取TBOX及DMC日志分析。 +1015: TBOX日志分析该时间点GPS信号很差，无法获取定位，导致主机登录请求时间错误，无法通过PKI。建议客户到信号好的地方重新登录。 +1014: 已从TSP获取TBOX日志，等待TBOX分析 @谢恩堂 +1010：PKI侧排查：主机会员中心登录请求时间错误，请求PKI显示时间2025-03-17，但是主机登录和取日志时间是2025-09-28;主机侧dmc日志排查：Tbox那边显示的是没有定位信号，主机请求时间是从GPS数据里拿的，转国内TBOX专业分析 +0929: 转国内分析，等待合规流程后发送日志","11.06: No feedback from user, according to the system everything works fine, traffic consumed over avarage telematic rate -> Apps should work -> Temporary close +30/10:Check whether the vehicle host time synchronization is functioning properly and whether the time displayed is local time.@Kostya +23/10:Post-meeting acknowledgement to inform DRE of transfer to analysis process. +21/10: tbox log and dmc log in attachement +20/10:Suggest users to grab TBOX and DMC logs to analyze if they can't recover after retrying. +15/10: TBOX log analyses the GPS signal at this point in time to be very poor and unable to obtain a location, resulting in the host login request being timed incorrectly and failing to pass the PKI. the customer is advised to re-login at a location with a good signal. @Evgeniy Ermishin +14/10: The TBOX log has been obtained from TSP and is awaiting TBOX analysis +10/10: PKI-side troubleshooting: host member centre login request time error, request PKI display time 2025-03-17, but host login log time is 2025-09-28; host-side dmc logs troubleshooting: Tbox shows no positioning signals, the host request time is taken from the GPS data, turn domestic TBOX professional analysis +29/09: Forwarded to DRE analysis; under compliance process then send log to DRE",Low,temporary close,生态/ecologically,袁清,06/11/2025,EXEED RX（T22）,LVTDD24B1RG013677,,dmc log in attachment was recorded 28 of September,"LOG_LVTDD24B1RG01367720251021120033.tar,logs_20000101-020529-20250929T105350Z-1-001.zip,IMG-20250929-WA0113.jpg",Kostya,,,,,,38 +TR825,Telegram bot,30/09/2025,,Problem with auth in member center,The car has disconnected from the telematics system.,"1021：协商一致，切换成等待数据 +1015: 已向客户发送催复函 +1009: 请邀请客户进站抓取TBOX日志，T平台无法获取 +0930: 主机和TBOX登录正常，25日远控提示深度睡眠，29日远控提示网络超时. +汽车与TSP系统断开连接，汽车处于离线状态，虽然 sim 卡处于激活状态，但有几天数据消耗量为 0 Mb（在附件的屏幕上）","21/10: Consensus to switch to waiting for data +15/10: Reminder to customer was sent +09/10: Please invite the customer to dealer to capture the TBOX log. TSP platform cannot obtain it @Sergei Antipov +30/09 The car has disconnected from the telematics system, and the car is offline, although sim card is active, but there are days, where data consuption 0 Mb( on the screen in the attachments). ",Low,Waiting for data,TBOX,刘海丰,,JAECOO J7（T1EJ）,LVVDD21BXRC054408,,"TGR0003855 Trafic consumption, System fault log","image.png,image.png",Sergei Antipov,,,,,, +TR826,Mail,30/09/2025,,Application," In the application, when starting the car, there is an icon for turning on the rear window heating. When you click on it, the animation turns on, but does not turn on. +在APP中，启动汽车时有一个打开后窗加热功能的图标。当您点击它时，动画显示打开，但车辆没有打开。","1030: 能否转为临时关闭 +1020：转售后硬件 +1014：后窗除霜控制器反馈失败，可能是硬件损坏，建议客户进站检查或者是转售后排查 +1009: 远控后窗除霜失败，提示控制器状态失败，待TBOX排查 +1009：请TSP同学排查 +0930：T平台上查看视频展示时间点空调控制反馈成功，转国内app分析","11.06 - temporary close due to transition ASD +30/10:Can we change the status of this issue to temporarily close? @Kostya +28/10: on ASD side +20/10: Transferred to After-sales for hardware issues. +14/10: Rear window defroster controller feedback failed, may be hardware damage, suggest customer to dealer to check or transfer to after-sales for investigation. @Evgeniy Ermishin +09/10: Remote control of rear window defroster failed, system prompts ""controller status failure"". Awaiting TBOX investigation. +09/10: Requested TSP team to investigate. +30/09: Checked the T-platform, AC control feedback was successful at the specified video timestamp. Transferred to the domestic app team for analysis.",Low,temporary close,TBOX,谢恩堂,06/11/2025,EXEED RX（T22）,"LVTDD24B8RG009836 +LVTDD24B0RG012035 ",,"operation date 30.09 at 8:41 + ++TGR0003963","image.png,17591931150754860751EACB.mp4",Kostya,,,,,,37 +TR828,Mail,30/09/2025,,Problem with auth in member center,QR code doesn't exist,30.09：已要求将数据/时间更改为自动同步。如果这无济于事，我会要求DMC日志,"01.10: solved by turned on permissions +30.09: asked change data/time to autosynchronisation. If it won't help, I will ask for DMC log",Low,close,生态/ecologically,袁清,01/10/2025,CHERY TIGGO 9 (T28)）,LVTDD24B8RG131158,,,Фото 3.09.jpg,Evgeniy Ermishin,,,,,,1 +TR829,Mail,01/10/2025,,Network,"Network is not ok. Can't activate SIM, with WIFI he autorised successfully, but in fact VK and other app doesn't work with WIFI too. Also remote control doesn't work, no status of car +网络不正常。无法激活 SIM 卡，使用 WIFI 成功授权，但事实上 VK 和其他应用程序也无法使用 WIFI。远控也不起作用，没有车辆状态。","1111：等待日志 +1106:等待DMC和TBOX日志 +1030：所有应用在共享热点或连接WiFi时均可正常运行，但使用车载网络时无法使用。已要求在所有应用启动前开始记录ICC日志。 +1027:已向经销商发出提醒 +1021:向经销商了解情况。暂无反馈 +1009: 请建议客户重启车辆后再尝试远控是否正常，如仍然无网络，建议客户进站抓取TBOX和DMC日志。 +1004: 车辆激活后无tbox登陆记录，远控失败提示深度睡眠中，重启tbox未唤醒。（SIM卡状态正常）","13/11: customer's feedback: car network was restored => apps started working. TR closed. +11.11: Collecting data +06/11：Need DMC and TBOX logs @Kostya +30/10: update: all the apps work when sharing hotspot or connected to WIFI but not using car network. ICC log has been requested starting before all the apps. +27/10 reminder to the dealer was sent +21/10: asked the dealer about situation +09/10: Please advise the customer to restart the vehicle and then try the remote control again to see if it is normal, if there is still no network, please advise the customer to dealer to capture the TBOX and DMC logs. @Evgeniy Ermishin +04/10:After vehicle activation, no T-Box login records are found. Remote control attempts fail with a “deep sleep” status prompt. Restarting the T-Box did not wake it up. (SIM card status is normal)",Low,close,TBOX,刘娇龙,13/11/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ0SD391325,,,image.png,Kostya,,,,,,43 +TR830,Mail,01/10/2025,,Network,"Network is not ok. Can't activate SIM, with WIFI he autorised successfully, but in fact VK and other app doesn't work with WIFI too. Also remote control doesn't work, no status of car +网络不正常。无法激活 SIM 卡，使用 WIFI 成功授权，但事实上 VK 和其他应用程序也无法使用 WIFI。远控也不起作用，没有车辆状态。","1104:目前T平台查看TBOX登录正常，2025-10-08远控提示车辆已上电且不在远程启动状态，IHU无登录记录，需要主机日志分析 +1023：会后尝试远程获取TBOX日志，并检查车辆实时数据 +1021:始终无法运行 +1014: TBox登录正常，IHU无登录记录，等待客户反馈 +1009：建议客户用钥匙先锁车，尝试远控是否正常；主机登录仍然异常的话建议进站抓DMC日志。 +1009: 目前T平台查看TBOX登录正常，2025-10-08远控提示车辆已上电且不在远程启动状态，IHU无登录记录。 +0903:转国内分析","11.06: No feedback from user, according to the system everything works fine, traffic consumed over avarage telematic rate -> Apps should work -> Temporary close +04/11：Currently, the T-Box login status appears normal on the T-Platform. On 8 October 2025, remote control indicated the vehicle was powered on and not in remote start mode. No login records were found in the IHU. Analysis of the host logs is required.@Kostya +30/10: Analysis of Tbox logs +23/10： Post-meeting attempt to remotely obtain TBOX logs and check real-time vehicle data.also suggest the user go to dealer to catch the DMC logs. +21/10: still doesn't work +14/10: TBox login normal, IHU no login record, waiting for customer feedback +09/10: It is recommended that the customer locks the car with the key first and tries to see if the remote control is normal; if the host login is still abnormal, it is recommended to go into the station to catch the DMC log. @Evgeniy Ermishin +09/10: Currently, the TBOX login on the T platform is normal. 2025-10-08 the remote control prompts that the vehicle is powered on but not in the remote start state. No login records for IHU.",Low,temporary close,DMC,Kostya,06/11/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ6SD391233,,,image.png,Kostya,,,,,,36 +TR831,Mail,01/10/2025,,doesn't exist on TSP,"Vehicle information does not exist. Transfer to MES analysis. +车辆信息不存在，转mes分析","1010: 车辆信息已同步到TSP，请确认 +1010：已补充缺失的车辆数据，如TBOX序列号和ICCID。 +0910：这些车辆在TSP平台中仍不存在。 +0910：车辆信息已同步至TSP平台，请@Evgeniy Ermishin确认。 +1001：请咨询MES团队","10/10: Vehicle information has been synchronized to the TSP. Please confirm. +10/10: Missing vehicles data such as TBOX SN as well as ICCID have been added. +09/10: These cars are still not exists in TSP +09/10: Vehicle information has been synchronised to TSP, please confirm @Evgeniy Ermishin +01/10: Please ask MES guys",Low,close,MES,徐辉文,10/10/2025,EXLANTIX ET (E0Y-REEV),"LNNBDDEZ9SD391324 +LNNBDDEZ9SD391274 +LNNBDDEZ7SD391306 +LNNBDDEZ4SD391277",,"TGR0003964 +LNNBDDEZ4SD391277 - Евгений Горлов ",,Evgeniy Ermishin,,,,,,9 +TR835,Telegram bot,01/10/2025,,Remote control ,"Does not work remote control for seat heating. +customer turned on remote heat seating from the app, but actualy seats werenot warm. From bottom inside car seat heating work without issue. +From logs it is alright, all the command for A/C is done suceessfuly (logs in attachments) +座椅加热遥控器不起作用。 +客户通过应用程序打开了远程座椅加热功能，但实际座椅并不暖和。从车内底部看，座椅加热功能正常。 +从记录来看没有问题，所有空调指令都能顺利完成（记录在附件中）","1021:属地建议暂时关闭该问题 +1015:重新引导客户与 O&J 应用程序开发人员联系, 等待客户反馈 +1009:TSP侧排查图片显示时间点远控的是座椅通风，未查询到座椅加热远控请求，请O&J app开发进一步排查 +1009:请TSP同学排查。 +1004:转国内车控分析","21/10:Territorial recommendation to close the issue temporarily +21/10: Customer has not provided feedback +15/10: Redirect customer to contact with developers of O&J app +09/10: The TSP side inspection image shows that the remote control at the time point is for seat ventilation. No request for remote control of seat heating was found. Please further investigate with the O&J app developer ",Low,temporary close,O&J-APP,,28/10/2025,JAECOO J7（T1EJ）,LVVDD21B8RC052656,,TGR0003950,"image.png,LOG_LVVDD21B8RC05265620251001162628.tar",Sergei Antipov,,,,,,27 +TR836,Omoda team,01/10/2025,,Remote control ,"Can you tell me, please, does climate control differ in different car configurations? Do you have the opportunity to provide us with information so that we can properly advise users? +The fact is that users contacted us with the problem ""The seat heating does not turn on and the interior temperature is not regulated,"" in the screenshot (https://myomoda-source-public.storage .yandexcloud.net/50/a0/50a0714c949d36cde7ca7865b9677811.jpg ) it can be seen that these climate functions are basically inaccessible to the user. The car is equipped with Active.","1114：建议转暂时关闭状态，因为已排查是控制器问题 +1106:等待反馈 +1028：已联系经销商，等待反馈 +1016：日志分析TBOX已下发指令，但是控制器未响应，需要转售后团队排查硬件问题，或者邀请客户进站抓取CAN报文后，进一步分析控制器的状态。 +1014: 远控记录查看远控空调均反馈:[1]：控制器反馈状态失败，转TBOX分析 @刘海丰 +1004:T平台有配置座椅加热功能，转app车控分析","14/11: Recommendation to temporary close , as the issue has been identified as a controller problem.@Kostya +11.11: In progress +11.06: Still in progress +28/10: communication with dealer -> in process +16/10: The tbox log analyses that the TBOX has issued commands, but the controller is not responding. It is better to transfer to the after-sales team to troubleshoot the hardware problem, or suggested that invitie the customer to dealer to capture the CAN telegrams for analyse the status of the controller @Evgeniy Ermishin +14/10: remote control record view machine remote control air conditioning are feedback:[1]: controller feedback status failure, turn TBOX analysis +0410: T platform has configuration seat heating function, turn app car control analysis",Low,temporary close,O&J-APP,Kostya,18/11/2025,JAECOO J7（T1EJ）,LVVDD21B0RC084257,,,LOG_LVVDD21B0RC08425720251003113832.tar,Kostya,,,,,,48 +TR837,Mail,06/10/2025,,Problem with auth in member center,"When logging in to your personal account by phone number, the error is a screen in the attachment. +车机上登录账号提示:请输入正确号码","1014：等待客户反馈 +1009：客户同一个号码在exlantix和exeed两个app都注册绑车了，请客户在exeed解绑车辆，并注销账号 +1006:车机上登录账号提示:请输入正确号码。 +App后台查看只有一条认证信息，无换绑申请，T平台存在两个用户id","14/10: done +1009: The customer has registered and bound the vehicle on both Exlantix and Exeed apps with same account. Please suggest that customer unbind the vehicle on Exeed and cancel the account. @Evgeniy Ermishin",Low,close,TSP,张石树,14/10/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ6SD444853,,,"{1F363C24-5B28-49B9-A336-4769696C3FCA}.png,image-05-10-25-08-20.jpeg",Evgeniy Ermishin,,,,,,8 +TR838,Mail,06/10/2025,,Remote control ,"Telematics is not working +Sim card is activated +Auto activated +When you click on any of the ""Start engine"" commands, etc. +He writes either a car in a deep sleep , or try it with the car running ( It doesn 't help ) +Previously, there were no problems with connecting telematics. Car of the year 2025, technically serviceable. Everything has been updated +It also does not correctly determine the location of the application. +车联网无法正常工作 +SIM卡已激活 +自动激活 +点击任何“启动引擎”指令时 +他写道车辆处于深度睡眠状态，或尝试在车辆运行时操作（无效） +此前连接车载信息系统从未出现问题。2025年度车型，技术上可维修。所有系统均已更新 +应用程序也无法正确定位车辆位置。","1106：等待客户复现问题，然后获取到TBOX日志 +1030：反馈日志与远控命令时间上无法对应（日志最后一条是莫斯科时间下午1点），需要重新尝试远控，若远控失败，尝试后抓取TBOX日志 +1027：日志已在分析中 +1023:已有日志，转国内分析. +1023: 已执行 2 条命令： +1) 在鄂木斯克时区 2025-10-21 16:21 启动发动机（莫斯科时间 15:21）； +2) 在鄂木斯克时区 16:23 时（莫斯科时间 15:23）解锁车辆。 +附上相应的照片以及 TBOX 日志。请拿去调查。 +1021:等待属地更新反馈 +1014:今天将邀请客户前往经销商处 +1009：建议邀请客户进站抓取TBOX日志，同步排查是否退出工厂模式 +1006:车辆处于深度睡眠中，重启tbox未恢复","11.11: Waiting for data +06/11:Await the customer's reproduction of the issue, then obtain the TBOX logs. +30/10: The log cannot correspond to the remote control command in time (the last entry in the log is 1pm Moscow time), you need to retry the remote control, if the remote control fails, capture the TBOX log after the attempt.@Kostya +28/10: Waiting for feedback from 2nd line +27/10：Logs are being analyzed and will be synchronized as progress is made. +23/10: TR put in High level because if not sorted out in the coming day, user will make a request for buyback. +23/10: 2 commands had been executed: +1) start engine 2025-10-21 at 16:21 at Omsk time zone (Moscow time 15:21); +2) vehicle unlock at 16:23 at Omsk time zone (Moscow time 15:23). +Respective photos attached as well as TBOX log. Please take for investigation. +21/10:Waiting for feedback on territorial updates +14/10: will invite the customer to the dealer today +13/10: please provide instruction how ""check factory mode"" for T28- already sent IOV group +09/10: It is recommended that customers be invited in to grab the TBOX logs and synchronise to check if they have exited factory mode.@Evgeniy Ermishin +06/10: Vehicle is in deep sleep, restarting tbox did not restore it",Low,Waiting for data,TBOX,项志伟,,CHERY TIGGO 9 (T28)）,EDEDD24B0SG018223 ,,,"tboxlog_EDEDD24B0SG018223.tar,Vehicle_location.jpeg,Engine_start.jpeg,Unlocking.jpeg,{D6BCB985-4864-482C-9DC9-D483A2F25CCE}.png,image.png,WhatsApp Image 2025-10-02 at 22.14.02.jpeg",Kostya,,,,,, +TR839,Mail,06/10/2025,,Problem with auth in member center,"crashes from your account (you have to log in again each time) +账户会自动退出（每次都需要重新登录）","1020：建议转等待数据状态 +1014:暂无更新 +1007:转国内分析,请抓取DMC日志","20/10: Recommended to switch to 'waiting for data' status. +14/10: No updates yet. +07/10: pls help grap DMC logs and check DMC version @Evgeniy Ermishin ",Low,Waiting for data,生态/ecologically,袁清,,EXEED VX FL（M36T）,LVTDD24B5PD641045,,,,Kostya,,,,,, +TR840,Telegram bot,06/10/2025,,Traffic Payment,"Customer cant load the payment page via phone in O&J app (one free year licenses and traffic also is exhausted +客户无法通过手机在O&J应用中加载支付页面（免费一年许可证及流量已耗尽）","1106：已核实辛巴已经向O&J应用程序团队提供新域名链接,请与OJ团队核实新版本上线时间 +1031:已询问OJ团队，等待反馈。 +1029:需要属地员工联系OJ APP开发团队确认续订链接是否使用的是prod-rus-appdatastore.chery.ru +1031： 向O&J应用程序团队索取信息 -> 等待中 +1028: 另一个用户 LVVDB21BXRC076172 被添加到无法进行付款的列表中 - 请参阅附件中名为 ""LVVDB21BXRC076172_payment_issue ""的照片。 +1028: 正在分析 +1024： 据 O&J 称，问题出在辛巴方面，总部同事大约一个月前已经解决了类似问题 +1023：会后辛巴已确认续费API、URL正常，转OJ app分析 +1022：新增一例，无法加在支付页面 +1021：14天无反馈转暂时关闭 +0913：用户 VIN LVVDB21B5RC077312 已要求用户检查APP否为最新版本。 +0910：请帮忙确认该客户处于哪个地区，以及请帮忙登录测试看续费页面是否正常。另外确认客户APP是否是最新版本，如不是建议更新app后再重试下 +0910:转国内分析","11.11: Solved - Tests and feedback +11.06: It has been verified that Simba has provided the O&J application team with a new domain link. Please liaise with the OJ team to confirm the launch date for the new version. +31/10 Requested info from O&J APP team -> Waiting +29/10:Local employees need to contact the OJ APP development team to confirm whether the renewal link uses prod-rus-appdatastore.chery.ru @Kostya@Vsevolod Tsoi +28/10: another user LVVDB21BXRC076172 added in the list not being able to do a payment - see photo attached called ""LVVDB21BXRC076172_payment_issue"" +28/10: Analyzing in process +24/10: According to O&J - problem on Simba side and the similiar issue was already fixied by HQ collegues Approximately mounth ago +23/10: @赵杰 please, can you privide proper URL to payment page for one of these cars? We also want tot test it on customer side while waiting feedback from O&J, if there any limitations for network +23/10: another user LVUGFB226SD831192 who encountered the issue to get the payment page downloaded - white screen instead of. Mobile app version is the latest one. +1023: After the meeting Simba has confirmed that the renewal API, URL is normal, to OJ app analysis.@Sergei Antipov +22/10: One more cutsomer faced with this issue, after APP update on mobile phone, payment clicking ""Payment"" is empty ( LVVDB21B7RC078834) @Sergei Antipov +21/10：14 days no feedback to temporary closure. +13/09: user VIN LVVDB21B5RC077312 was asked to check wether the app is the latest one. +10/09: Wait for feedback +10/09: Pls help confirm whether the customer's APP is the latest version. If not, it is recommended to update the app and try again. after update is still have problem please help to log in and test to see if the payment page works or not. and Pls help to check which region those customers are in. @Kostya",Low,close,MNO,胡纯静,11/11/2025,JAECOO J7（T1EJ）,"LVVDB21B0RC070252 +LVVDD21B7RC053197 +LVVDB21B5RC077312 +LVUGFB226SD831192 +LVVDB21BXRC076172 +LVVDB21B5RC079495 +LVVDB21B5RC072207",,TGR0004052,"LVVDB21BXRC076172_payment_issue.jpg,image.png",Kostya,,,,,,36 +TR841,Mail,07/10/2025,,Network,"No internet network available in the vehicle. No IHU log in since Aug, 8th. MNO is OK. Last TBOX log in 2025-10-07 12:49:10 +DMC版本02.06.00，图片拍摄日期10月7日 + +车机没有网络，从8月8日后没有IHU 登录记录，移动网络运营商正常。最后一次TBOX登录时间：2025-10-07 12:49:10","1120: 主机工程师说：问题发生时间距离目前太久了，日志应该被覆盖了，没有分析日志的必要了。平台上看从11月12日起，主机和TBOX有多次成功登陆的记录，请和客户确认一下目前主机是否有网络能正常使用？ +1119：DMC主机工程师正在分析中，提醒：当日志上传后，请把状态从Waiting for data转换为processing，不然我们会忽略waiting for data 的问题检查。 +1113：DMC日志已上传，请用于调查。 +1111：日志待处理。 +1105：目前尚未收到DMC日志，已向ASD团队发送提醒。 +1101：目前尚未收到DMC日志。 +1023：等待主机日志。 +1021：等待主机日志 +1009: 版本信息无误，请邀请客户进站抓取DMC日志 +1009: 请先确认DMC版本信息，和拍摄图片的日期。 +1009: 车机没有网络，从8月8日后没有IHU 登录记录，流量正常，TBOx登陆正常。","25/11: user's feedback - car network was restored. TR closed. +25/11: the user has been asked to provide the information whether the access to the car network was restored. +20/11:The DMC engineer stated: The issue occurred too long ago; the logs would have been overwritten by now, rendering log analysis unnecessary. The platform shows multiple successful login records for the DMC and Tbox since 12th November. Please confirm with the client whether the host currently has network connectivity and is functioning normally.@Vsevolod Tsoi +19/11: DMC host engineers are currently analysing the issue. Please note: once the log has been uploaded, change the status from 'Waiting for data' to 'Processing'. Failure to do so will result in our team overlooking the 'Waiting for data' issue during checks. +18/11: is there any progress following an ivestigation? +13/11: DMC log uploaded. Please take for investigation. +11/11: logs pending. +05/11: no DMC log received so far. A reminder was sent to ASD team. +01/11: no DMC logs so far +23/10: DMC log is pending. +21/10: DMC log is pending. +09/10: request for DMC log is sent to dealership. +09/10: Version information is OK. Please invite the customer to dealer to capture the DMC logs. @Vsevolod Tsoi +09/10: DMC SW version is provided - see photo attached. +09/10: DMC SW version is requested. All the pictures are dated September, 7. +09/10: Please help check the DMC version information and the date the picture was taken first @Vsevolod Tsoi",Low,close,DMC,聂换换,25/11/2025,CHERY TIGGO 9 (T28)）,LVTDD24B4RG128483,,Вадим Сорвачев ,"logs_20160101-001757.7z,DMC_SW_version.jpg,photo.jpg,IMG_20251007_152726.jpg,IMG_20251007_152707.jpg",Vsevolod Tsoi,,,,,,49 +TR842,Telegram bot,07/10/2025,,Application,Customer cant activate car in the app - error A07913,"1028：等待客户反馈 +1024：已见该车辆已被+79****4626绑定，如核实为车主手机号，即可关闭该问题 +1020：暂无更新 +1017：已联系数跑，反馈周五提供进展 +1014: 请更新状态 +0910：绑车报错A07913","11.06: No feedback, car is bound - close +28/10: Waiting for feedback +24/10：The vehicle has been seen to be tied to +79****4626 and the issue can be closed if verified as the owner's cell phone number. +20/10: No update at this time +17/10: Contacted Counting Runs with feedback to provide progress on Friday +14/10: Please update status +10/09: Tie-down error A07913",Low,close,用户CHERY-APP(User),岳晓磊,06/11/2025,CHERY TIGGO 9 (T28)）,LVTDD24B2RG093071,,TGR0004100,image.png,Kostya,,,,,,30 +TR843,Mail,08/10/2025,,Problem with auth in member center,No entering in the member is possible since QR code is unavailable. User was requested to do an ICC reset to the factory settings but not possible since system says the user should be loged in the member center before being able to do a reset - see pictures attached.,1008: 问题已解决。背景：用户在 Exeed 移动应用程序中添加和绑定了他的车辆，并知道他的车辆是 Exlantix。经销商没有告知用户需要使用什么应用程序。这是导致他在 Exeed 应用程序中激活后无法进入会员中心的原因。解决方案：在 Exeed 应用程序中删除车辆，然后注销账户。之后，在 Exlantix 应用程序中添加车辆，然后绑定并在会员中心输入电话号码。,"08/10: Issue closed. Background: the user added and bound his vehicle in the Exeed mobile app knowing that his vehicle is Exlantix. The user was not informed by dealership what app needs to be used. This was route cause that he was unable to enter in the member center already having been activated in the Exeed app. Solution: deleting the vehicle in the Exeed app, then log out of the account. After that, adding the vehicle in the Exlantix app, then binding and entering in member center with phone number.",Low,close,,,08/10/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ6SD444853,,"TGR0004101 +Федюнин Александр Александрович 79104482434 +Автоспецентр Exeed химки","image.png,file_5009.jpg,file_5010.jpg",Vsevolod Tsoi,,,,,,0 +TR846,Mail,09/10/2025,,Remote control ,Remote control doesn't work -> on tsp the car is in deep sleep,"1106:等待反馈 +1028:客户的问题悬而未决，需待与MTS确认哈萨克斯坦地区网络是否可用后方能解决。 +1024:建议进站，使用OBD确认TBOX工作模式，如果为工厂模式，请退出 +1023:会后检查， +1023:深度睡眠和 tbox 登录/注销有问题，IHU 登录/注销没有问题 +1021:协商一致，切换成等待数据 +1009: 请邀请客户进站抓取TBOX日志 +1009: 车辆9月13日激活sim卡后，远控均提示网络超时和深度睡眠，t平台抓取日志提示深度睡眠，IHU登录正常（2025-09-13 19:38:39远控失败提示车内有钥匙）","11/11:Awaiting feedback +06/11:Awaiting feedback +28/10: customer's problem is on hold until finding out with MTS if network could be available in Kazahstan region +24/10 As I mentioned before, in our yesterday's meeting User left Russian border to Kazahstan, where MTS provider is not availabe, that's probably the reason why T-Box in the deep sleep mode. Now we try to contact with MTS to confirm whether provider mobile signal is available on Kazahstan. +24/10:It is recommended to make a pit stop and use OBD to confirm the TBOX operating mode, if it is factory mode, exit this mode. +23/10:The problem with Deep sleep and tbox log in/ log out, no ptoblem with IHU log in/ log out +21/10:Consensus to switch to waiting for data +13/10: A request for the TBOX log has been sent to a dealer. +1009: Invite customers to grab TBOX logs @Evgeniy Ermishin +09/10:Remote control doesn't work -> on tsp the car is in deep sleep.",Low,Waiting for data,TBOX,项志伟,,CHERY TIGGO 9 (T28)）,LVTDD24B0RG122762,,,"image.png,{AA6F13A6-A5B0-4834-9354-EE2B04483EDB}.png",Kostya,,,,,, +TR849,Mail,09/10/2025,,Activation SIM,"Impossible to activate SIM. TSP settings in engineering menu wetr completed. DMC log in attachement +无法激活 SIM 卡。工程菜单中的 TSP 设置已完成。 DMC 日志已在附件中。","1118：用户计划于周五（21日）到访经销商处。确认首项操作为在DMC系统中录入车辆识别码（VIN）。请按要求等待英文版视频资料。 +1114：已上传新的DMC日志。操作时间与数据：14/11 11:37-11:38多次尝试通过二维码进入会员中心；11:38尝试启动VK视频、音乐及导航功能 +1109：确认日志未被请求，遂于11月9日提交请求。 +1106：等待DMC日志 +1101：经销商反馈：DMC软件已升级至08版，现请求获取DMC日志。 +1030：需要用户进站升级版本至08，并反馈升级后是否解决 +1022：主机侧建议进实车工程模式确认版本，确认开关是关掉状态，重启车辆尝试，如不可，同时抓取DMC日志并录制操作视频。@Vsevolod Tsoi +1020: 经销商检查空格和 ""tsp 三码"" - 正常，但结果相同 +1014：等待客户进站操作后反馈 +1010: 从日志查看PKI校验失败导致接口失败。日志中显示获取的VIN前面多了一个空格。 +1、请邀请客户进站用诊断仪重新刷写VIN； +2、进入工程模式查看四码信息是否完整正确，同时检查“card activation status”开关是不是关闭的（需要关闭），附图 +1009:sim卡正常，流量正常，tbox登陆和远控正常。无IHU登陆记录。车机无网络","21/11: issue was fixed. Root cause - a space was present vefore VIN number set up in the repsective field TSP four code. +20/11: wait for ther user's visit. Please provide a support from the 2nd line while sorting out the issue. +18/11: visit of the user to the dealer is planned for Friday, 21st. Writing of VIN code in DMC was proived as the 1st action to do. Wait for video in english language as requested. +14/11: new DMC logs has been uploaded. Operations time and data: 14/11 severals attempts to enter into member center with QR code at 11:37-11:38; trying to start VK video, music and Navi at 11:38 +09/11: it was figured out that logs were not requested. A request then was done on November, 9. +06/11: wait for DMC log +01/11: dealer's feeback: DMC SW was already upgraded to 08. Now, DMC log was requested. +30/10：Users must upgrade to version 08 and report whether the issue is resolved after upgrading.@Vsevolod Tsoi +22/10：DMC side is recommended to go into the real vehicle engineering mode to confirm the version, make sure the switch is off, restart the vehicle to try, if not possible, while capturing the DMC logs and recording the operation video.@Vsevolod Tsoi +20/10: dealer check space and ""tsp three-code"" - it is ok, but result is the same +14/10：Waiting for customer feedback after inbound operation +1010: +Reason: Checking from the log that the PKI verification failed, resulting in the interface failure. The log shows that there is an extra space before VIN. +Measure： +1、If Please invite the customer to dealer and re-write the VIN with the diagnostic tool +2、Pls enter the engineering mode to see whether the four code information is complete and correct, and at the same time check whether the ""TSP Three- code"" switch is off (need to be turned off), see picture in comment +@Evgeniy Ermishin",Low,close,DMC,孙松,21/11/2025,OMODA C7 (T1GC),LVUGFB225SD830857,,,"log.mega.co.zip,img_v3_02ra_9d094a88-e105-479a-9f4e-17d00661128g.jpg,2025_10_08_16_50_27.zip,WhatsApp Video 2025-10-08 at 17.05.15.mp4.mp4",Vsevolod Tsoi,,,,,,43 +TR850,Telegram bot,09/10/2025,,Application,"Wrong vehicle location is shown on the map in the app when executing a command ""vehicle hunting"" - see picture attached. User was trying to execute a command in different areas - result was the same. +客户点击寻车显示错误的车辆定位，客户在不同的地方尝试结果都一样 ","1106：已向用户发送提醒。 +1101: 由于TBOX日志可从TSP平台下载，故要求客户执行若干车辆搜索指令，并相应提供具体日期和时间。请等待反馈。 +1023：TBOX专业人员反馈，需要客户在车载导航正常的情况下使用APP进行远程寻车尝试。如果有错误报告，请抓取此时的TBOX日志。 +1021:用户反馈：在距离每个区域 30-50 千米的不同区域（用户提供了 6 个不同区域）- 结果相同。 +1015: 日志分析客户获取车辆定位时没有获取到GPS信号，可能是客户停车的地方信号不好，建议客户停车到信号好的地方再重新尝试远控寻车是否正常。 +1014: 等待日志分析中 @张科委 +1010:TSP侧排查box上报了这个错误，另外上报的gps状态207F是无效值。转TBOX 专业分析，等待合规流程中发送日志 +1010：车辆SIM卡正常，tbox和车机登录正常，转国内TBOx分析 （图片文字翻译显示：无法确定车辆位置）","11/11: the user's feedback: vehicle hunting command was restored. TR closed. +06/11: a reminder was sent to the user. +01/11: since TBOX log is available to be downloaded from TSP platform, customer was asked to execute a couple of the vehicle hunting command provoding the respective date and time accordingly. Wait for feedback. +23/10：TBOX professional feedback, need to customers in the car navigation is normal in the case of using APP remote car search attempt. If there is an error report, capture the TBOX log at this time.@Vsevolod Tsoi +21/10: user's feedback: vehicle hunting command was executed in different areas at a distance of 30-50 km from each one (user provided at list 6 different areas) - same result. +15/10: Log analysis: When the customer obtained the vehicle location, no GPS signal was obtained. It might be due to poor signal at the place where the customer parked. It is recommended that the customer park in a place with good signal and try remote control to find the vehicle again to see if it is normal. @Vsevolod Tsoi +14/10: under analysing +10/10: TSP side troubleshooting box reported the error , in addition the reported gps status 207F is an invalid value. Transferring to TBOX Professional analysis, waiting for logs to be sent in the compliance process",Low,close,TBOX,项志伟,11/11/2025,CHERY TIGGO 9 (T28)）,LVTDD24B1RG131163,,,file_5015.jpg,Vsevolod Tsoi,,,,,,33 +TR854,Telegram bot,13/10/2025,,Network,"No TBOX login ""deep sleep"", cant catch TBOX logs remotly","1218：等待TBOX更换 +1209：等待TBOX更换 +1117：TBox反馈，可邀请用户进站使用OBD读取TBOX故障码，若无明显故障码，但实车无法恢复，可更换该车TBOX。 +1114:(1031反馈工程模式显示，TBOX未连接）待咨询TBOX专业 +1015:已联系用户，等待日志上传 +1015: 请邀请客户进站抓取tbox日志 +1014: TBOX最后登出时间10月7日，远控失败提示网络超时。无法远程抓取TBOX日志，转国内分析","18/12: Waiting for TBOX replacing - new status woulc be added after replacing +11/12: Waiting for TBOX replacing +09/12: Waiting for TBOX replacing +02/12: Waiting for TBOX replacing +27/11: TO BE requested - Preparing isntructions for dealer +17/11: TBOX Feedback Invite the user to visit the service station to use an OBD device to read the TBOX fault codes. If no obvious fault codes are present but the vehicle cannot be restored, replace the TBOX in that vehicle.@Kostya +14/11（31/10 feedback）: ""TBOX is not connected"", but actually connected +Check attachments +1015: Already asked - waiting for data +1015: PLS invite customers to dealer to grab tbox logs @Kostya +1014: TBOX last logged out on 7 October, remote control failed to prompt network timeout. Unable to capture TBOX logs remotely, transferring to domestic analysis.",Low,Processing,TBOX,Kostya,,EXEED RX（T22）,XEYDD24B3RA004829,,TGR0004181,"10-18-24(3).jpg,10-18-24(1).jpg,10-18-24(2).jpg,10-18-24.jpg",Kostya,,,,,, +TR857,Telegram bot,16/10/2025,,Application,"""Steering wheel heating"" button doesn't respond to the activation in mobile app => No vissial change of state - check attachments +""方向盘加热 ""按钮不响应移动应用程序中的激活 => 没有明显的状态变化 - 检查附件","1106:等待用户反馈 +1028:等待用户反馈 +1021:已检查T28实时数据配置，请用户重新尝试后反馈 +1021: 命令成功执行，但用户界面中的按钮图标没有变化，请查看附件。 +这不是 TBOX 的问题，只是应用程序的用户界面出了问题。 +1020:已见20日多次成功远控方向盘加热记录，无失败记录， +1016: app远控方向盘加热无响应，TSP后台查看2025-10-16 12:29:22远控失败，故障码“1”控制器反馈状态失败， 2025-10-16 12:29:35远控反馈成功，但是方向盘温度无变化。反馈TBOX先排查","11.11: Solved - customer feedback +11.06: Still waiting +28/10: Waiting for feedback +21/10：T28 real-time data configuration has been changed and users are asked to retry with feedback. +21/10: Command is succesfull - but in the UI three is no change of button icon - please check attachments. +That is not TBOX issue only aplication UI is wrong +20/10:Have seen many successful remote steering wheel heating records on the 20th, no failure records, +16/10: app remote control steering wheel heating not responding, TSP background check 2025-10-16 12:29:22 remote control failed, fault code ""1"" controller feedback status failed, 2025-10-16 12:29:35 remote control feedback successful, but no change in steering wheel temperature. Feedback TBOX first troubleshooting",Low,close,TBOX,张科委,11/11/2025,CHERY TIGGO 9 (T28)）,LVTDD24B9RG119567,,TGR0003925,file_4953.mp4,Kostya,,,,,,26 +TR858,Mail,20/10/2025,,Remote control ,Remote control doesn't work. Vehicle is in deep sleep.,"1204:EDEFB32B8SE017193 - 遥控器恢复功能尚未收到反馈------一已有登录，但无客户反馈 +EDEFB32B5SE023808 - 已确认 - 遥控器功能已恢复。 +1202：EDEFB32B8SE017193 ，EDEFB32B5SE023808 两车还未确认关闭. +1117: EDEFB32B2SE016802 -远控已恢复。 +1113：新增一台T1E EDEFB32BXSE019642设备，其Tbox处于深度睡眠状态。 +EDEFB32B2SE016802 - 已向经销商发送提醒，确认该问题是否已解决。 +02/12: 两辆车未恢复 +EDEFB32B8SE017193 Tbox log in records were restored - a reminder sent. +EDEFB32B5SE023808 Tbox log in records were restored - reminder sent. + +1113：EDEFB32B2SE016802见TBOX已恢复登录，请询问用户是否进行了什么操作 +1111：按约定，将在测试车辆上确认Tbox日志采集流程，若操作成功，将为客户实施该流程。 +1106：仍在协商。 +1101：线缆问题尚未解决，且尚未与ASD团队达成一致。初步计划是使用诊断工具检查部分故障车辆的TBOX软件版本，然后与遥控功能正常的T1E车型进行比对。因此已向ASD团队提出请求，要求其优先检查故障车辆的TBOX软件版本。 +1029：查询到EDEFB32B6SE019654，此车10月初有TBOX及实时数据上传，与其他三例不同，建议用户重启车辆，启动发动机后查看数据是否恢复，其余三例需要TBOX日志分析 +1023：TBOX 日志收集日志需要先与 ASD 小组商定，然后批准购买特定的电缆，经销商将随电缆一起提供。在此之前，我们无法提供任何日志。 +1021：TBOX反馈处理方法如下： +1.用户进站后，重启TBOX（打开前舱盖，整车蓄电池断电重新接回后）、使用OBD读取TBOX故障信息，查看是否未退出工程模式; +2.使用HSD线提取TBOX日志（教程已在群里提供）看看能否取出日志; +3.上述方法都不可，进行换件。 +1020：自10月13日启动以来，车辆一直处于深度睡眠状态。 因此远控不可用。","09/12: EDEFB32B8SE017193 - remote control was restored. Thus, remote control was restored for all the VINs in the TR => TR closed. +04/12: EDEFB32B8SE017193- no feedback so far on the restoring remote control +EDEFB32B5SE023808 - confirmed - remote control restored. +02/12: statuses of VIN's below are as follows: + - EDEFB32B6SE019654 Tbox log in records were restored - closed. +EDEFB32B0SE019701 Tbox log in records were restored => remote control restored - closed. +EDEFB32B8SE017193 Tbox log in records were restored - a reminder sent. +EDEFB32B5SE023808 Tbox log in records were restored - reminder sent. +EDEFB32BXSE019642 Tbox log in records were restored => confirmed by the user => solved. +28/11: all the tbox of VIN below were finally woken up from deep sleep. User asked to check whether remote control was restored. +DEFB32B6SE019654 Tbox log in records were restored +EDEFB32B0SE019701 Tbox log in records were restored => remote control restored - closed. +EDEFB32B8SE017193 Tbox log in records were restored. +EDEFB32B5SE023808 Tbox log in records were restored - reminder sent. +EDEFB32BXSE019642 Tbox log in records were restored => confirmed by the user => solved. +27/11: EDEFB32B6SE019654 tbox log in records restored. The user asked to check whether remote control was restored. +EDEFB32B8SE017193 tbox loig in records restored. The user asked to check whether remote control was restored. +27/11: statuses are up to date. Sim cards have been restarted via TSP today for VINs below. Wait for results. +EDEFB32B6SE019654 still in deep sleep +EDEFB32B0SE019701 still in deep sleep +EDEFB32B8SE017193 still in deep sleep +EDEFB32B5SE023808 still in deep sleep +EDEFB32BXSE019642 still in deep sleep +25/11: statuses are uppdated from Nov, 25. EDEFB32B9SE019745: the user's feedback - remote control restored => the issue closed. +20/11: statuses of cars are updated in VIN column +17/11: EDEFB32B2SE016802 - remote control restored. +13/11: one more T1E EDEFB32BXSE019642 added whose Tbox is in deep sleep. +EDEFB32B2SE016802 - a reminder was sent to the dealer whether the issue was sorted out. +13/11: EDEFB32B2SE016802 detected TBOX has resumed login. Please inquire if the user performed any actions. +11/11: as agreed, a procedure for collecting Tbox log will be confrimed on a test car and then if successful, it will be performed for a customer. +06/11: agreement is still pending. +01/11: cable is still an issue and was not agreed yet with ASD team. The plan for the first time is to check TBOX SW version of some problem vehicles using a diagnostic tool and then compare it with one of T1E car whose remote control works good. Therefore, a request was sent to ASD team to check a TBOX SW version of prolem cars first. +29/10：The vehicle with EDEFB32B6SE019654 was identified. This vehicle had TBOX and real-time data uploads in early October. Unlike the other three cases, it is recommended that the user restart the vehicle and check if the data is restored after starting the engine. The remaining three cases require TBOX log analysis.@Vsevolod Tsoi +28/10: meeting not held yet. +23/10: TBOX log collecting log needs to be agreed with ASD team first, then purchasing of a specific cable needs to be approved, dealers to be supplied with cable. Before this we can't provide any logs +21/10: TBOX feedback is handled as follows: +1. After the user enters the station, restart the TBOX (after opening the front hatch and reconnecting the entire vehicle battery disconnection), use OBD to read the TBOX fault information, and check if it has not exited the engineering mode.@Vsevolod Tsoi +2. Use the HSD line to extract the TBOX log (tutorial has been provided in the group) to see if you can take out the log. +3.If none of the above methods work, replace the TBOX. +20/10: vehicle is in deep sleep since activation held on October, 13. Therefore, remote control is not available.",Low,close,TBOX,Vsevolod Tsoi,09/12/2025,Tenet T7 (T1E),"EDEFB32B6SE019654 Tbox log in records were restored. +EDEFB32B0SE019701 Tbox log in records were restored => remote control restored - closed. +EDEFB32B8SE017193 Tbox log in records were restored. +EDEFB32B9SE019745 tbox started loging in. 1st Tbox log in record on Nov, 25. fixed +EDEFB32B2SE016802 Logged in recent days，waiting feedback form user. The user's feedback - remote control restored => issue closed. +EDEFB32B5SE023808 Tbox log in records were restored. +EDEFB32BXSE019642 Tbox log in records were restored.",,,,Vsevolod Tsoi,,,,,,50 +TR863,Mail,23/10/2025,,Remote control ,"Vehicle data is not updated in the app => dated from October, 19 - thus, they are old one. No TBOX log in since October, 19. TBOX is in deep sleep since October, 19. +APP中的车辆数据没有更新，从10月19日起t-box处于深度睡眠中","1211: 用户被要求检查遥控器是否已恢复。然而，通过在TSP中查看状态可清晰发现，所有指令在12月10日均因""超时""失败——详见附图。 +1211：日志反馈目前登录已正常，数据已正常上传，可能是由于获取日志，刷新了TBOX网络状态 +1209：Tbox日志调查是否有进展？----日志今日已发送 +1204: 已上传两份Tbox日志。等待二线分析。 +1127：等待新的Tbox日志。 +1125：已收到Tbox日志，但文件大小为0。需与经销商确认是否会提供后续日志。 +1120：已向经销商发送提醒通知。 +1118：11月10日提供了DMC日志，而非最初要求的Tbox日志。已再次发送Tbox日志请求。11月18日已发出提醒。 +1101：已向经销商发送请求，要求收集TBOX日志。 +1024:车辆处于深度睡眠中，远程无法获取T-box日志，问题有点复杂不好定位，需要客户进站取T-box日志和DMC日志","12/12: the user's feedback: the remote control operation has finally been restored. +11/12: the user was asked to check whether the reomote control was restored. However, following checking the status in TSP, it's well seen that all the commands were failed on Dec, 10 ""Time out"" - see picture attached. +11/12：Log feedback: Login is now functioning normally, and data is uploading correctly. This may have been caused by retrieving logs, which refreshed the TBOX network status. +09/12: is there any progress on Tbox logs investigation?----Today's Log Analysis Has Been Sent +04/12: two Tbox logs were uploaded. Wait for the 2nd line investigation. +02/12: Tbox log pending. +27/11: wait for a new Tbox log. +25/11: tbox log was received but the file size is 0. Need to talk to dealer whether nex log will be provided. +20/11: a reminder has been sent to the dealer. +18/11: DMC logs were provided on November, 10 instead of Tbox requested initially. A request was sent again for Tbox log. A reminder has been sent on November, 18. +11/11: Tbox log pending. +01/11: a request was sent to the dealer for collecting TBOX log. +24/10: The vehicle is in deep sleep, and T-box logs cannot be remotely obtained. The problem is a bit complex and difficult to locate, so the customer needs to visit the station to retrieve T-box logs and DMC logs. @Vsevolod Tsoi",Low,close,TBOX,刘娇龙,12/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ8SD345645,,'Астанин Артем Иванович (CSAT: 4.5 ⭐)' ,"Dec_10th_Commands_failed.JPG,20251202151944_tboxlog.tar,20251202154242_tboxlog.tar",Vsevolod Tsoi,,,,,,50 +TR864,Mail,23/10/2025,,Problem with auth in member center,User not able to enter into member center neither mobile phone nor QR code.,"1111：已向经销商发送了最后一次提醒。 +1106：仍在等待反馈。 +1101：已于10月29日向客户发送请求。等待反馈该问题是否已解决。 +1025:日志显示此vin码绑定了两个手机号，需要用户用6562的手机号解绑，然后2322的手机号才能正常登录 +1024: 附上 DMC 日志以及问题的视频。","18/11: the user finally managed to enter into member center with QR code. +11/11: one more reminder has been sent to the dealer. +06/11: still wait for feedback. +01/11: a requst was sent to the customer on October, 29. Wait for feedback whether the issue was sorted out. +25/10：The log shows that this vin code is bound to two cell phone numbers, requiring the user to unbind with the 6562 cell phone number, and then the 2322 cell phone number to log in normally @Vsevolod Tsoi +23/10: DMC logs attached as well as vieos of the issue.",Low,close,生态/ecologically,袁清,18/11/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZXSD449358,,'Астанин Артем Иванович (CSAT: 4.5 ⭐)' ,LNNBDDEZXSD449358.zip,Vsevolod Tsoi,,,,,,26 +TR866,Mail,24/10/2025,,Traffic is over,Abnormal traffic consumption,"1218：只有等待下次流量异常消耗时，及时记录消耗，用户行为，及DMC日志。 +1209: 用户不使用Carplay，仅使用导航应用。 +1201：等待下次流量异常时，抓取DMC日志，同时记录流量消耗记录 +1125：由于日志中未记录相关的异常消耗，只有等待下次流量异常消耗时，及时记录相关日志。 +1118：转入分析中，生态应用正在对应日志分析。 +1111: 已有DMC日志，会后转DMC分析 +1106：目前尚未收到日志。 +1101：目前尚未收到日志。 +1030：已向经销商发送DMC日志请求。 +1028：等待客户进站取日志。 +1024:建议用户抓取DMC日志回传分析。 +1024：用户表示仅使用导航应用，未使用其他应用。流量消耗量：3天内达3.12GB。与E0X案例症状相同——流量套餐容量存在差异，具体详见运营商提供的PDF附件。","18/12：Only by waiting for the next instance of abnormal traffic consumption can we promptly record the consumption, user behavior, and DMC logs. +09/12: the user doesn't use a Carplay, Navi app only. +01/12：When the next traffic anomaly occurs, capture the DMC logs and simultaneously record the traffic consumption history. +25/11: wait for investigation of the log by T22 DMC team.-----Since no related abnormal consumption was recorded in the logs, we can only wait for the next instance of abnormal traffic consumption and promptly document the relevant logs. +18/11:Transitioning to analysis, ecological applications are undergoing corresponding log analysis. +11/11: DMC log uploaded. Please do an investigation. +06/11: logs are pending. +01/11: No logs so far. +30/10: a request for DMC log has been sent out to the dealer. +28/10: wait for user's contact date to make a request to ASD team for invitation, +24/10: It is recommended that users grab the DMC log back for analysis.@Vsevolod Tsoi +24/10: user states he use Navi only and no other apps. Consumption volume - 3.12 Gb for 3 days. Same symptom as E0X - traffic package size is plus mines the same - see pdf from MNO attached",Low,Analysising,DMC,Vsevolod Tsoi,,EXEED RX（T22）,XEYDD14B3SA012164,,Ксения Митрофанова ,"logs_20251105-134832.zip,Traffic_consumption_issue.pdf",Vsevolod Tsoi,,,,,, +TR867,,24/10/2025,,Traffic is over,Abnormal traffic consumption Chery,"1118：等待日志 +1111：等待日志 +1106：因为是不同车型且是不同的项目组，所以需要判断是否有增加功能的必要，所以还是要抓取DMC日志 +1027：建议邀请用户进站抓取DMC日志。 +1024： 截图显示 1 天内流量消耗完","25/11: Waiting for logs +18/11: Waiting for logs +11/11: Waiting for logs +06/11：As these are different vehicle models and distinct project teams, it is necessary to assess whether additional functionality is required. Therefore, it remains essential to capture the DMC logs.@Kostya +11.06: But if its the same issue as on E0x is there some profit for capturing logs without traffci monitor function +27/10：It is recommended that users be invited in to capture DMC logs.@Kostya +24/10 all Trafic consumptuion for 1 day on screenshot",Low,Waiting for data,DMC,Kostya,,CHERY TIGGO 9 (T28)）,LVTDD24B4RG091306,,TGR0004494,image.png,Kostya,,,,,, +TR869,Mail,28/10/2025,,VK ,"No network is available in the car => apps (VK, Navi...) do not work. Tbox is in deep sleep and has not woken up after getting it restarted.车内没有网络 => 应用程序（VK、导航......）无法使用。Tbox 处于深度休眠状态，重启后仍未唤醒。","1113:该用户是否已正常使用，如果正常使用，则该问题可以暂时关闭 +1111:经销商询问是否可以换件TBOX,国内侧提议先分析今天获取到的日志后，给出建议 +1111：已见用户有TBOX登录记录，建议与用户确认是否问题已解决 +1106：如何重新启动车辆？--- +1103：日志是上一个月的，需要客户用物理钥匙重启下车辆，然后我们看看能否远程取到TBOX日志 +1030: 开始分析日志。ICC日志已一并附上，请尽快查阅。（这个问题TBOX先分析，需要主机接力分析的时候再走流程） +1028：建议用户进站检查TBOX设置是否异常，并抓取TBOX日志","13/11: customer's feedback: car network was restored => apps started working again. TR closed. +13/11：Is the user currently using the service normally? If so, this issue can be temporarily closed. +11/11:The dealer inquired whether it is possible to replace the TBOX. The domestic side proposed analyzing the logs obtained today first and then providing recommendations. +11/11: A request was sent to dealer since the car is located in the dealership. +11/11：The TBOX in the actual vehicle has a login record. This can be confirmed with the user to determine if the issue has been resolved. +06/11: what steps to do to restart the vehicle? +03/11:The logs are from last month. We require the customer to restart the vehicle using the physical key, after which we shall attempt to retrieve the TBOX logs remotely.@Vsevolod Tsoi +30/10: ICC log has also been attached. please check it ASAP. +Please provide feedback as soon as posible @赵杰 +30/10: Tbox logs have been uploaded. Please check it. +28/10: Users are advised to go into the station to check if the TBOX settings are abnormal and to capture the TBOX logs @Vsevolod Tsoi",Low,close,TBOX,Vsevolod Tsoi,13/11/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ0SD391325,,,"ICC_logs.zip,20251029193027_tboxlog.tar,20251029194557_tboxlog.tar",Vsevolod Tsoi,,,,,,16 +TR872,Mail,28/10/2025,,Network,"Car network is not available. All the apps work when sharing hotspot. +车载网络不可用。共享热点时，所有应用程序都能正常工作。","1106：等待经销商提供的日志。 +1031：已发送TBOX和DMC日志请求 +1030:研发反馈需要主机及TBOX日志分析，请复现操作后，抓取日志 +1028：建议 +1. 将 ""I ""更改为 ""1""，然后检查车载网络是否恢复； +2/ 关闭 TSP 三码测试，然后再次检查车载网络。 +上面提供的所有建议都已采纳，但没有结果。我们被告知，唯一有帮助的办法是将 12V 电池端子拆下，然后再装回去。网络恢复了，但恢复了一段时间后又消失了。问题的相关照片和视频附后。","11/11: the user's feedback: a car network was restored. Background: 12V battery terminals had been taken off, after that car network was restoring and then gone away again several time. Next dealer was checking again => car network was restored again and no longer gone away. +06/11: wait for logs from dealer. +31/10: a request for TBOX and DMC logs have been sent. +30/10：R&D feedback requires analysis of host and TBOX logs. Please capture the logs after reproducing the operation.@Vsevolod Tsoi +28/10: all the provided recommendations below have been done - no result. We were told that the only thing that helped was to take the 12V battery terminals off and then putting them back. The network was restored but for a while and then went away. Respective photo and vides of issue are attached. +Recommendations: +1. Change ""I"" to ""1"" and then check whether the car network is restored; +2/ Turn TSP three-code test OFF and then check again the car network.",Low,close,DMC,孙松,11/11/2025,OMODA C7 (T1GC),LVUGFB221SD830984,,Kostin Dmitry ,"WiFi.mp4,4G.mp4,TBOX_IHU_data_engineering_menu_setup.jpg",Vsevolod Tsoi,,,,,,14 +TR873,Mail,30/10/2025,,Remote control ,"Remote control issue. Command are not executed since TBOX is in deep sleep since activation date. In addition, all the traffic used for apn1 was used up - see pictures uploaded. +遥控器故障。由于TBOX自激活日期起处于深度睡眠状态，导致指令无法执行。此外，APN1的流量已全部耗尽——详见上传图片。","23/12:等待TBOX学习SK +1215： 已向ASD团队发送TBOX'学些SK的指导，等待反馈结果，确认远程发动机启动功能是否将被恢复。 +1204：Tbox从深度睡眠中唤醒。最后一次登录记录为11月4日。因此要求用户执行若干命令后反馈结果。--------等待反馈 +1201：等待用户联系信息，以便发送SK学习TBOX的请求。 +1127：关于SK学习Tbox的请求将于今日内发送。 +1125：需要进行SK +1118：TBOX登录正常，但在TSP中清晰显示54故障代码——详见附图。是否需要使用SK对TBOX进行学习？ +1110：TBOX已正常登录，可询问用户是否正常 +1107:TBOX已正常登录，该问题可询问用户是否正常 +1106:已核实是Tbox SN缺了#符号，导致频繁请求消耗流量 +1105：用户通过Start&Stop按钮启动车辆，但TBOX未被唤醒，仍处于深度睡眠状态。 +1031：请判断并分析@芮千 +1031：远控故障。由于TBOX自激活日期起处于深度睡眠状态，导致指令无法执行。此外，APN1的流量已全部耗尽——详见上传图片。","23/12: Tbox has been leant with SK. Successful commans of the engine start are now in TSP. Wait for confirmation from dealer before closing the issue. +23/12: wait for feedback on the learning TBOX with SK. +15/12: a request for the learning TBOX with SK has been sent to ASD team. Wait for feedback on the result whether remote engine start will be restored. +11/12: the instruction is still under preparation. +09/12: an insturuction is in process of preparation. +08/12: tbox learning with SK is required due to 54 fault code. +04/12: Tbox was woken up from deep sleep. Last tbox log in records on Nov, 4th. Therefore, the user was asked to execute some commands and then provide a feedback.--------waiting for feedback +01/12: wait for the user's contact data to send a request for learning TBOX with SK. +27/11: a request for learning of Tbox with SK will be sent within today. +25/11: please confirm that learning Tbox with SK is required to fix the issue.---SK is required. +20/11: wait for 2nd support feedback. +18/11: TBOX log in is OK but 54 fault code is well seen in TSP - see photo attached. Does it require for learning TBox with SK ? +10/11：TBOX has logged in successfully. local side need to inquire whether the user is functioning normally. +07/11: the user is aked to check whether the remote control is restore. +07/11:TBOX has logged in successfully. This issue can be addressed by asking the user if everything is functioning normally. +06/11:It has been verified that the Tbox SN is missing the # symbol, resulting in frequent requests consuming data traffic. +05/11: User started his car with Start&Stop button but TBOX was not waken up and is still in deep sleep. +1031: Please diagnose and analyze the remote control malfunction.@芮千 +1031: The remote control is faulty. Since the TBOX has been in deep sleep mode since its activation date, commands cannot be executed. Additionally, all APN1 data traffic has been exhausted—see attached image for details.",Low,Processing,TBOX,Vsevolod Tsoi,,Tenet T7 (T1E),EDEFB32B3SE004920,,,"Authentification_TBOX_failed.pdf,TBOX_deep_sleep.JPG,Apn1_issue.JPG",Vsevolod Tsoi,,,,,, +TR874,Mail,31/10/2025,,Remote control ,"No TBOX login ""deep sleep"", cant catch TBOX logs remotly","1204：车辆已恢复登录，但后续仍需整理如何抓取日志手册及流程 +1127：为流程准备硬件和手册 +1125：为流程准备硬件和手册 +1118：为流程准备硬件和手册 +1111：为流程准备硬件设备及操作手册 +1106:请尽快联系客户进站取TBOX日志 +1031：TBOX无登录记录，提示深度睡眠，无法远程获取日志,需要联系客户进站取TBOX日志","23/12: Same status +09/12: TR for procedure status tracking - Looking for hardware +02/12: Nothing new here +27/11: Preparing hardware and manuals for procedure +25/11: Preparing hardware and manuals for procedure +18/11: Preparing hardware and manuals for procedure +11/11: Preparing hardware and manuals for procedure +07/11:as mentioned in today meeting purchase of cable not approved yet +06/11:Please contact the customer as soon as possible to arrange collection of the TBOX log at the station.@Kostya +31/10:TBOX shows no login records, indicating deep sleep mode. Unable to remotely retrieve logs. It is necessary to contact the customer to arrange collection of the TBOX log at the station.@Kostya",Low,Processing,local O&M,Vladimir|米尔,,Tenet T7 (T1E),"EDEFB32BXSE019589 ------TBOX login normal +EDEFB32B3SE019594 ------TBOX login normal",,Владимир Чурсинов ,,Kostya,,,,,, +TR875,Mail,31/10/2025,,VIN number doesn't exist,Missing TBOX and DMC data. Car was locally produced in Russia. TR was created to follow the resolving the issue.,,"31/10: data was provided by the AGR plant. Vehicle data has then been imported into TSP. +31/10: this issue will be followed up localy. No need to track it in dayly meetings. AGR plant has been requested to provide the data if available.",Low,close,,,31/10/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG018622,,Landina Vlada ,,Vsevolod Tsoi,,,,,,0 +TR876,Mail,31/10/2025,,Network,"No car network is available, VK and Navi do not work accordingly. However, apps and navi work when sharing a hotspot or connecnting to WIFI. No TBOx log in sice activation date held on Sept, 24. +当前无车载网络可用，VK和导航功能无法正常运行。但通过共享热点或连接WiFi时，应用程序和导航功能可正常使用。自9月24日激活以来，TBOx未记录任何登录信息。","1120：等待反馈 +1118: 已向经销商发送请求，要求其与用户确认该问题是否仍然存在。 +1117：尝试TSP手动停卡重启后（间隔20分钟），TBOX，DMC恢复登录，但此前异常原因未知，客户侧可告知已恢复，可重新尝试。 +1114：日志显示驻网失败，已拉专题群分析 +1106: tbox工程师正在分析日志 +1101:反馈激活后无tbox登陆记录，其他生态应用无网，仅wifi下正常使用，建议转tbox排查.TBOX日志已上传至TR。","27/11: TR closed since no feedback. +25/11: a repeat request has been sent to the dealer. If no feedback by Thursday's meeting, the issue will be closed. +20/11: feedback pending. +18/11: a request has been sent to the dealer to confirm with the user whether the issue is still valid. +17/11：After attempting a manual card stop and restart via TSP (with a 20-minute interval), TBOX and DMC have resumed login functionality. However, the cause of the previous abnormality remains unknown. The customer side can be informed that service has been restored and attempts can be made again.@Vsevolod Tsoi +14/11：The log indicates network residency failed. A dedicated group has been established for analysis. +06/11:The tbox engineer is analysing the logs. +01/11: TBOX log was uploaded to the TR. +There is no tbox login record after feedback activation. Other ecological applications have no network. Only wifi can be used normally. It is recommended to transfer to tbox for troubleshooting.",Low,close,TBOX,项志伟,27/11/2025,CHERY TIGGO 9 (T28)）,LVTDD24B8RG131158,,,"tboxlog.tar,When_use_car_network.jpg",Vsevolod Tsoi,,,,,,27 +TR877,Telegram bot,01/11/2025,,Remote control ,"Rear window heating doesn't work -> No heat accrding to customer, no button reaction in the UI od mobile app, but got the success pop up. +A/C control requests in the logs are succesful","1128：已取消后窗除霜配置，属地可验证后告知用户 +1127:会后跟进进展 +1113:已确认是功能配置问题，需要属地提供测试车验证方案可行性 +1111: 该功能在除霜时是否应加热车窗？激活时UI按钮上的徽标是否应变为橙色？据客户反馈，激活该功能后车辆没有任何反应。 +1106：app端不支持远程控制后车窗加热，仅支持车窗除霜，因为功能预设中，前窗除霜和后窗除霜是在一个模块下的，如果需要更改，请邮件通知国际公司丁雪。 +1101：后窗加热功能失效 -> 客户反馈无加热效果，移动应用界面按钮无响应，但弹出操作成功提示。 +日志中空调控制请求显示为成功状态，已有TBOX日志，请专业分析。","02/12: Confirmed - Issue closed +28/11： Rear window defrost configuration has been canceled. Local personnel may verify and inform the user. +27/11: Looking for test vehicle - in procces +13/11:Confirmed as a functional configuration issue. Requires the local team to provide a test vehicle to validate the feasibility of the solution. @Kostya +11/11: Should this function heat window while defrosting? Should the insignia on button in the UI become orange while activated? According to the customer there is no any reaction on the car after activating that function +06/11：The app does not support remote control of rear window heating; it only supports window defrosting. This is because in the preset functions, front window defrosting and rear window defrosting are grouped under the same module. If you need to make changes, please email to layla. +01/11: TBOX logs added",Low,close,local O&M,Kostya,02/12/2025,EXEED RX（T22）,LVTDD24B3RG021182,,TGR0004587,"LOG_LVTDD24B3RG02118220251101141303.tar,file_5532.MP4",Kostya,,,,,,31 +TR878,Telegram bot,01/11/2025,,VIN number doesn't exist,"Chinese car (VIN LVTDD...) doesn't exist in the TSP, Please import it from the MES. +该中国车辆（VIN LVTDD...）在TSP中不存在，请从MES导入。",1101:已检查TSP，四码信息完整，建议属地确认,"11.06: Sim activated - closed +01/11: TSP verified, four-digit information complete. Recommend local confirmation.@Kostya",Low,close,TBOX,Kostya,06/11/2025,EXEED RX（T22）,LVTDD24B3RG048995,,TGR0004591,,Kostya,,,,,,5 +TR880,Mail,01/11/2025,,Remote control ,An error message "A00362" comes up upon trying to execute any commands,"1118：已发送提醒，如周四无反馈可关闭该问题 +1114：已见用户车控使用记录，该问题可关闭@Vsevolod Tsoi +1111：异常数据已删除，请告知用户重新尝试 +1106:已告知信息公司需要邮件发出删除异常数据，等待处理 +1101：请信息公司排查处理。@岳晓磊","24/11: user's feedback - remote control via mobile app was restored. +20/11: TR closed on the reason of absence of a feedback. +18/11: a reminder has been sent to the dealer to confirm with an user whether an user was finally able to bind his car. If no reply by Thursday, TR will be closed. +14/11: User vehicle control usage records have been reviewed. This issue can be closed.@Vsevolod Tsoi +11/11: the user was asked to bind his car in the app again. +11/11：The abnormal data has been deleted. Please inform the user to try again. +06/11:The information company has been notified that an email must be sent to delete the anomalous data; awaiting processing. +01/11: this type of the issue is known and was fixed before for previous cases. Please inform the information company about the issue. ",Low,close,用户CHERY-APP(User),岳晓磊,20/11/2025,CHERY TIGGO 9 (T28)）,LVTDD24B1RG123600,,,,Vsevolod Tsoi,,,,,,19 +TR881,Mail,01/11/2025,,Application,User can't bind his car in the Exlantix app however the car is already bound in the TSP.,"1118：已发送重复提醒。若周四前未收到回复，该事项将视为已解决。 +1111: 已向经销商发送提醒。 +1105：根据TSP中的应用账户数据分析发现，用户将车辆绑定至错误的移动应用Exeed Connect而非EXLANTIX应用。因此要求其先在Exeed应用中删除车辆绑定，再转至Exlantix应用重新绑定车辆。 +1101：建议检查Exlantix app后台是否正常绑定","20/11: TR closed on the reason of the absence of a feedback. +18/11: a repeat reminder has been sent. If no reply by Thursday, the issue will be considered as sorted out. +11/11: a reminder was sent to the dealer. +05/11: following the app account data in TSP it was figured out that user bound his car in wrong mobile app Exeed Connect but not in EXLANTIX app. Therefore, he was requested to delete his car in Exeed app and the bind his car in Exlantix app. +01/11：We recommend checking whether the Exlantix app backend is properly bound.",Low,close,用户CHERY-APP(User),Vsevolod Tsoi,20/11/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ3SD391318,,,,Vsevolod Tsoi,,,,,,19 +TR882,Telegram bot,05/11/2025,,Network,"Dead TBOX - No login, PKI, frequancy data -> TBOX log requested, Waiting data from user +故障TBOX - 无登录记录、PKI数据、频率数据 -> 已请求TBOX日志，等待用户提供数据",1105：等待tbox日志,05/11: Waiting for data from user,Low,Waiting for data,,,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ5SD442995,,,,Kostya,,,,,, +TR884,Mail,05/11/2025,,Problem with auth in member center,User was kicked out from his account in the member center.,"1127：因涉及两个不同的T1GC车辆识别码且发生混淆，正与经销商核实情况。 +1125：目前尚未收到反馈。 +1120：等待反馈。 +1118：已上传Tbox日志及工程菜单中的Tbox数据。Tbox序列号与TSP中配置的序列号一致。--------日志显示写入的TBOXSN被写成了ICCID，需要修改 +1111：等待Tbox日志。 +1105：经检查TSP系统中的TBOX及DMC日志记录，发现TBOX序列号与车辆实际安装的设备不符。现已向经销商发出收集TBOX数据的请求。","02/12: dealer's feedback: access to the member center was restored. The issue is solved. +27/11: finding out with dealer since 2 different T1GC VIN numbers were involved and then mixed up. +25/11: no feedback so far. +20/11: wait for feedback. +18/11: a request for modifying ICCID and TBOX SN in four-code information menu has been sent out to the dealer. +18/11： We checked the logs on the TSP and found that the TBOX_SN reported by the actual vehicle was the ICCID, which should have been a mistake when writing the four-code information during the first activation; it should be the TBOX_SN of the actual vehicle. +18/11: Tbox log was uploaded as well as Tbox data from engineering menu. Tbox SN matches to the one configured in TSP. +11/11: wait for Tbox log. +05/11: following check of TBOX and DMC log in/out in TSP, it was figured out that TBOX SN doesn't match to the one installed in the car. Thus, a request for collecting TBOX data has been sent to the dealer.",Low,close,TBOX,Vsevolod Tsoi,02/12/2025,OMODA C7 (T1GC),LVUGFB222SD830802,,,"Tbox_log_in_failed.JPG,Tbox_data_1.jpg,Tbox_data_2.jpg,LVUGFB222SD830802-FOTO+LOG.rar",Vsevolod Tsoi,,,,,,27 +TR885,Mail,05/11/2025,,Missing in admin platform,The car is missing in the web platform https://growing-admin.chery.ru/,"1118：已发送提醒，如周四无反馈可关闭该问题 +1114：已录入，用户可直接绑车@Vsevolod Tsoi +1107: 已在周五录入APP后台，请属地确认 +1106：已提供EPTS（发动机）- 164301115200519。请配置平台。 +1106：已同步DRE询问发动机编号，查询MES获取后，可录入app后台 +1105：已向用户发送提供EPTS编号的请求。请等待反馈。","20/11: TR closed on the reason of the absence of a feedback. +18/11: a request to confirm whether the issue was sorted out was sent on November, 9th. A reminder has been sent again. If no reply by Thursday, the issue will be considired as solved. +14/11: Registered. You may now attempt to link your vehicle directly. +11/11: what is the current status ? +1107：The information has been entered into the app backend on Friday. Please confirm with the local office. +06/11: EPTS (engine) provided - 164301115200519. So, please configure the platform. +06/11: DRE has synchronised the engine serial number enquiry. Upon retrieval from MES, it may be entered into the app's backend. +05/11: a request for providing EPTS number has been sent to ther user. Wait for feedback.",Low,close,车控APP(Car control),陶军,20/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B7SG004111,,,,Vsevolod Tsoi,,,,,,15 +TR886,Mail,05/11/2025,,Remote control ,"TBOX is in deep sleep since the activation date that took place on October, 31st +TBOX自10月31日激活日期起便处于深度休眠状态。","1120：暂无日志上传 +1118:等待日志 +1106：反馈TBOX从激活起，始终无登录记录，远控提示深度睡眠，建议用户进站获取TBOX日志","02/12: the user's feedback: remote control was restored => the issue closed. +27/11: a repeat request sent again. +25/11: Tbox started loging in. Last Tbox log in record on Nov, 21. Thus, the user has been asked to provide a feedback whether remote control was restored. +20/11: no Tbox log received so far. +18/11: wait for Tbox log. +09/11: Tbox log has been requested at dealer. +06/11：need Tbox log from the real vehicle @Vsevolod Tsoi.",Low,close,TBOX,Vsevolod Tsoi,02/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG018622,,,,Vsevolod Tsoi,,,,,,27 +TR887,Mail,05/11/2025,,Chinese TBOX in Russia,Vehicle is equipped with chinese TBOX data - see the photo of TBOX data attached.,"1106：需要属地运维二次确认这辆车是测试车还是商品车。更换TBOX并且读取下IHU_SN。收集完成可由属地录入TSP以及APP后台 +1105：需要确认该车是否支持网联，如果不支持，则该车无法通过更换TBOX使用车联网","06/11: this car was not bought from an official dealership => we call it a parallel import. So, this is the reason of missing vehicle data in TSP. The issue is closed. +06/11:Local operations and maintenance personnel must conduct a secondary verification to determine whether this vehicle is a test vehicle or a commercial vehicle. Replace the TBOX and read the IHU_SN. Once collection is complete, local personnel may input the TSP and APP backend.@Vsevolod Tsoi +05/11: please confirm the replacement of TBOX since the car was produced with chinese one. Wait for customer's contact data being able to make a request to the dealer.",Low,close,TSP,Vsevolod Tsoi,11/11/2025,EXEED VX FL（M36T）,LVTDD24B0PD556274,,,Chinese_TBOX_data.JPG,Vsevolod Tsoi,,,,,,6 +TR888,Mail,05/11/2025,,Remote control ,"Commands are not executed from the app - all the commands are failed => time out. Car was successfully upgraded with OTA on November, 1st but TBOX SW was not since car TBOX SW version (18.14.03_22.64.00) didn't match to the source one (18.14.01_22.39.00) set up in the sequence control. Last TBOX log in on 2025-10-30 but no more since upgrade OTA. +应用程序无法执行命令——所有命令均失败 => 超时。车辆已于11月1日通过OTA成功升级，但TBOX软件未同步升级，因车辆TBOX软件版本（18.14.03_22.64.00）与序列控制中设置的源版本（18.14.01_22.39.00）不匹配。最后一次TBOX日志记录于2025-10-30，但OTA升级后再无日志更新。","1223: 等待其他部门确认OTA升级的可行性：18.14.03_22.64.00 => 18.14.04_22.69.00（FOTA后端涉及383辆汽车）。 +1215:OTA需求已由TBOX专业提供给OTA部门，等待收集其他部门需求后，统一OTA。 +1211: 已在相关群组聊天中向OTA团队发送请求。请等待反馈。 +1209：Tbox软件版本18.14.03_22.64.00（270辆车）的OTA发布是否有截止日期？ +1204：等待国内专业核实-----T22已有更新计划，T28等待OTA计划 +1202:会后确认T22 , T28 是否可以同时更新。18.14.03_22.64.00 (约200台)---会后确认T22 +1125:已确认解决，可联系客户确认 +1119：暂无日志上传 +1118：已与用户约定1119进站，如有日志会上传到问题清单. +1111：需要日志进一步分析 +1106：反馈多数远控超时，车辆已在11月1日成功OTA，但是TBOX版本与OTA版本不匹配。自OTA后TBOX无登录记录，最后TBOX登录一次在10月30日。主机正常登录。需要TBOX日志分析.","23/12: wait for other departments to confirm the feasibilty of an OTA 18.14.03_22.64.00 => 18.14.04_22.69.00 (383 cars in FOTA backend). +15/12: a request is being discussed in the respective group chat.---------The OTA requirements have been submitted by the TBOX team to the OTA department. We are awaiting the collection of requirements from other departments before conducting a unified OTA update. +11/12: a request was sent to the OTA team in the respective group chat. Wait for a feedback. +09/12: is there a deadline of an OTA release for Tbox SW version 18.14.03_22.64.00 (270 cars)? +04/12: wait for the 2nd line team on the result of discussion.---T22 has an update plan in place, while T28 is awaiting an OTA plan. +02/12: what was confirmed ? Remote control wasn't restored since Tbox SW version is 18.14.03_22.64.00（200 car ） and can't be upgraded to 18.14.04_22.69.00. +27/11: Confirmed resolved. Contact the customer for confirmation. +25/11：Confirmed resolved. Contact the customer for confirmation. +25/11: wait for 2nd line investigation result. +20/11: wait for a result of an investigation +19/11: tbox log uploaded. Commands executed are as foollows before recording log: +1. Unlock the car 11:39 (8:39 Moscow time) => failed; +2. Engine start at 11:41 (8:41 Moscow time) => failed; +18/11: user's visit for collecting Tbox log is scheduled for 19/11. Once received, it will be uploaded to TR. +11/11: request for Tbox log has been requested. +06/11: The last TBOX login occurred on October 30. The host logged in normally. TBOX log is required.@Vsevolod Tsoi",Low,Processing,TBOX,Vsevolod Tsoi,,CHERY TIGGO 9 (T28)）,LVTDD24B9RG129256,,,tboxlog.tar,Vsevolod Tsoi,,,,,, +TR889,Mail,06/11/2025,,Remote control ,"TBOX is in deep sleep and did not wake up after starting the vehicle with Start&Stop button. So, remote control can't be used by the user. TBOX SW version is 18.14.03_22.64.00 and can't be upgraded to 18.14.04_22.69.00 since TBOX SW verison in the car doesn't match to the source one that is 18.14.01_22.39.00. +TBOX处于深度睡眠状态，且在使用Start&Stop按钮启动车辆后未能唤醒。因此用户无法使用遥控功能。当前TBOX软件版本为18.14.03_22.64.00，且无法升级至18.14.04_22.69.00版本——因车载TBOX软件版本18.14.01_22.39.00与源版本不匹配。","1120:暂无TBOX日志 +1118:暂无TBOX日志 +1111：需要日志进一步分析 +1106：目前车辆TBOX无法连接至TSP，需要与国内确认是否为版本问题。","02/12: since there was no feedback, TR closed. +27/11: a reminder sent. If no feedback by Tuesday's meeting, TR willbe closed. +25/11: a reminder has been sent to the dealer to ask the user whether the remote control was restored. +21/11: Jeason's feedback: Tbox started loging in thefore the user has been asked to check whether remote control has been restored. +20/11: Tbox logs pending. +18/11: no Tbox logs received so far. +11/11: request for tbox log has been sent. +11/11: Further analysis of the TBOX logs is required. +06/11: The vehicle's TBOX is currently unable to connect to the TSP. Confirmation is required from the domestic team to determine if this is a version-related issue. TBOX log is required.@Vsevolod Tsoi",Low,close,TBOX,项志伟,02/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG018359,,Сергей Мышко ,,Vsevolod Tsoi,,,,,,26 +TR892,Mail,06/11/2025,,doesn't exist on TSP,"User can't bind his car since the car is missing in TSP. Car was locally produced at AGK plant. Therefore, teh plant has been requested to provuide the required data.",1106:属地反馈，国内无需关注,"11/11: Vehicle data was provided by AGK plant and then imported into TSP. TR closed. +06/11: TR created to be able to track the resolving the issue locally. No need to follow in daily meetings.",Low,close,local O&M,Vsevolod Tsoi,11/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B0SG018187,,,,Vsevolod Tsoi,,,,,,5 +TR893,Mail,06/11/2025,,Application,"Vehicle is not seen in the app - see photo attached. Hower, it was bound in TSP. Customer was asked to log out from the app and then log in again but it did not bring any result, still not available => can't control remotly via Chery app.","1204:会后在CHERY后台验证 +1127：建议属地在CHERY后台检查配置，同时通知信息公司进行核查 +1120：用户电话无法接通。已发送短信。等待反馈。 +1118：已发送提醒，要求提供流程的录像视频。 +1111: +1. 卸载应用程序并重新安装。 +2. 安装应用程序后，使用您的手机号码登录（）。 +1107：TSP检查实时数据正常显示，未见远控记录，建议使用最新版app，录制视频复现操作 +1107：车辆在应用中无法显示——详见附图。然而该车已在TSP系统中绑定。已要求客户退出应用后重新登录，但未见成效，车辆仍不可用 => 无法通过奇瑞应用进行远程控制。","08/12: the user's feedback - the issue was sorted out. +04/12: a phone call is required. Try to have it within today - to confirm by @赵杰 +02/12: did not manage to find the configuration in chery backend. A phone call would be required.--------today will check +1127: Recommend that the local authority verify the configuration in the CHERY backend and simultaneously notify the information company to conduct an audit. +27/11: user's feedback: car is now seen in the app and not T28 but M1E (ARIZZO 8) - see photo attached. Vehicles data is not reflected in the app. TSP is ok. +25/11: a remider has been sent again. If no feedback by Thursday's meeting, the issue will be closed. +20/11: the user is not reachable by phone. A SMS was sent then. Wait for feedback. +18/11: a reminder has been sent to provide a recorded video of process. +11/11: a request to perform the actions below was sent to the user. +1. Uninstall the app and reinstall it. +2. After installing the APP, log in with your mobile phone number (whether it is possible to change the language to english on the app). +07/11：TSP inspection shows real-time data displayed normally with no remote control records observed. We recommend using the latest app version and recording a video to reproduce the operation.@Vsevolod Tsoi",Low,close,车控APP(Car control),Vsevolod Tsoi,08/12/2025,CHERY TIGGO 9 (T28)）,LVTDD24B3RG118771,,,"Screenshot_20251120_191242_CHERY.jpg,Screenshot_20251120_191235_CHERY.jpg,TSP_permissions_statuses.JPG,Screenshot_app.jpg",Vsevolod Tsoi,,,,,,32 +TR894,Mail,06/11/2025,,Application,"The user can't bind his car in the Exlantix app. However, the car was already bound in TSP. Photos attached.","1118:暂无反馈 +1111:建议联系用户确认操作步骤，后台记录显示11月1日，11月4日，多次尝试登录，需要核实具体操作判断问题是否产品原因。 +1107:后台检查为A00062报错，提示为车辆已被绑定，当前车主账号为+79****7825，昨日今日均有成功远控记录，建议询问用户是否恢复，如异常请反馈操作时间及录屏","20/11: still no feedback. if no reply by Tuesday's meeting, TR will be closed. +18/11: no feedback so far. +11/11：We recommend contacting the user to confirm the operational steps. Backend records indicate multiple login attempts on November 1st and November 4th. Further verification of the specific actions is required to determine whether the issue stems from the product itself. +07/11: Backend check returned error A00062, indicating the vehicle is already bound. The current owner account is +79****7825. Successful remote control records exist for both yesterday and today. Recommend inquiring with the user about restoration. If abnormal, please report the operation time and provide a screen recording.",Low,close,车控APP(Car control),Vsevolod Tsoi,20/11/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ3SD391318,,Елизавета Родионова ,"Binding_issue_in_Exlantix_app.JPG,Binding_status_TSP.JPG",Vsevolod Tsoi,,,,,,14 +TR895,Mail,06/11/2025,,OTA,"User applied for factory settings in IHU. Then, OTA upgrade was again available - button ""Update"" is active. When started upgrade, it achieved 10% and then failed. ","1211:已向经销商发送提醒。请等待反馈。 +1209：反馈待处理。 +1204：状态不变 +1202:暂无日志 +1127: 等待升级结果以及DMC日志。 +1124:建议已发送至经销商。因此，请等待升级结果以及DMC日志。 +1113：主机返回升级结果是0-失败，需要主机日志分析，建议用户进站尝试升级，失败的同时抓取日志回传分析 +1106：反馈恢复出厂设置后，开始ota 操作，进度条到10%时保存失败","15/12: TR temporary closed since no feedback. +11/12: a reminder has been sent to the dealer. Wait for a feedback. +09/12: feedback is pending. +04/12: Same status +02/12: Feedback pending. +27/11: wait for an upgrade result as well as DMC log. +24/11: Recommendations have been sent to the dealer. Thus, wait for a result of an upgrade as well as DMC log. +13/11:The DMC returned an upgrade result of 0 (failure). DMC logs require analysis. Users are advised to attempt the upgrade the DMC in station . If it fails, capture the DMC logs and send them back for analysis.@Vsevolod Tsoi +08/11:Not sure I got what the user needs to do. So, please decribe what the user should do exactly. +1106：Feedback After restoring the factory settings, start the ota operation, and the saving failed when the progress bar reached 10%.",Low,temporary close,OTA,Vsevolod Tsoi,16/12/2025,EXEED VX FL（M36T）,LVTDD24B0RD523892,,,,Vsevolod Tsoi,,,,,,40 +TR896,Mail,07/11/2025,,Traffic is over,"Anormal traffic consumption: the user reported that traffuc jams stopped being reflected in Navi app. After checking in CMP platform it was figured out that all the traffic (5Gb and even more) was used up for one day on November, 2nd - see photo attached. ","1120：后续问题出现时，请及时抓取日志回传分析 +1118:ota成功， +1108：已添加至小批量推送的VIN清单中，如果用户抱怨强烈，可以进站更新最新软件，软件以提供属地运维","02/12: once occuring, an ICC log will be requested => temporary closed. +20/11: what does it mean ""provide progress updates""? +18/11:OTA successful. +08/11: Added to the VIN list for small-batch push updates. If user complaints are significant, they may visit the service station for the latest software update, which is provided by local maintenance operations.",Low,temporary close,DMC,林希玲,02/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ7SD233578,,TGR0004732,Traffic_issue.JPG,Vsevolod Tsoi,,,,,,25 +TR897,Mail,08/11/2025,,Traffic is over,"Abniormal traffic consumption. All was used up on Nov, 1st straight afre monthly traffic renewal.",1108：流量异常消耗，属地拟向辛巴发送添加流量请求,"02/12: Temporary closed. +25/11: once the abnormal traffic consumption issue occurs, DMC log will be requested. +20/11: a request for reimbursement will be sent to SIMBA beginning December. OTA upgrade was completed Nov, 16th. +18/11: a request for traffic reimbursement to send to SIMBA => Andrey. Wait for monitoring function release. +08/11: a reimbursement to confirm with SIMBA at least.",Low,temporary close,DMC,林希玲,02/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ1SD152690,,,Traffic_consumption_issue.JPG,Vsevolod Tsoi,,,,,,24 +TR898,Mail,08/11/2025,,Weather,"Wheather app doesn't work. An istruction to allow the app to provide a location (see attached to the TR) was completed but did not bring any results. All the apps work well when shring a hotspot or connected to WFI. +天气应用无法正常运行。已完成允许应用获取位置的操作（详见TR附件），但未见成效。所有应用在共享热点或连接WFI时均运行良好。","1209:暂无日志 +1127：等待ICC日志。 +1125：已向经销商发送ICC日志请求，要求在取件前启动Wheather应用程序。 +1125：将于今日内请求ICC日志。 +1120：用于复现问题的信息请求及用户联系方式仍在等待中。 +18/11仍需等待用户的联系方式信息，方可发送邀请请求。 +1108：反馈天气app不工作，当使用热点时，车端APP均正常.建议用户进展复现操作，并抓取DMC日志","23/12: pending. +15/12: ICC logs pending. +11/12: ICC logs pending.--------turn to waiting for data +09/12: no logs received so far. +04/12: ICC log not received yet. +02/12: ICC log pending. +27/11: wait for ICC log. +25/11: a request for ICC log has been sent to the dealer asking for starting Wheather app before collecting it. +25/11: ICC log will be requested within today. +20/11: requested info to reproduce the issue as well as the user's contact data are pending. +18/11: still wait for an user's contact data being able to send a request for invitation. +08/11: The weather feedback app is not functioning. When using the hotspot, the in-vehicle app operates normally. We recommend users perform the steps to reproduce the issue and capture the DMC logs.",Low,Waiting for data,生态/ecologically,Vsevolod Tsoi,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ0SD152776,,"Custome's contact data: +Бондарев Виталий Владимирович/79124122541 +Дилер-EXEED ЦЕНТР АЛЬЯНС МОТОР ТЮМЕНЬ ЮГ Улица Федюнинского, 41","Exlantix_ET_Navi_location_allowing.pdf,20251103_111433.mp4",Vsevolod Tsoi,,,,,, +TR899,Mail,08/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,"1120：日志已重新上传。请确认是否可纳入工作流程。 +1118：已向经销商发送提醒通知。 +1114:二线支持反馈：TBox日志损坏（压缩问题）。已向经销商发送第二次请求，要求额外记录一次数据及DMC日志。 +1113：指令记录：11月12日16:53启动引擎；16:54解锁车辆；16:55锁车；15:56启动引擎。 +1108：反馈TBOX深度睡眠，且使用物理钥匙无法解除,最后一次TBOX登录记录为·10-24 16:17:08","27/11: user's feedback - remote control was restored. TR closed. +25/11: a reminder has been sent again. Wait for a reply. +21/11: Tbox log in records were restored => the user has been asked to provde a feedback whether the remote control has been restored. +20/11: logs has been uploaded again. Please check whether it can be taken in work. +18/11: a reminder has been sent to the dealer. +14/11: 2nd line support's feedback - tbox log is corrupted (compression issue). The second request was sent to the dealer for recording one more as well as DMC log. +13/11: commands: engine start - 12/11 at 16:53; unlock car - 16:54; lock the car - 16:55; engine start - 15:56. +08/11: the user was asked to start his car with a physical ket using Start&Stop button - no results.",Low,close,TBOX,项志伟,27/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B6SG018288,,,"Tbox_logs_ 20_11_2025.zip,logs_20251112-171950.zip",Vsevolod Tsoi,,,,,,19 +TR900,Mail,09/11/2025,,doesn't exist on TSP,Vehicle is missing in TSP. AGK plant has been requested to provide the required vehicle data needed to configure TSP,1109：TR创建了能够追踪问题解决的机制。无需在每日会议中跟进。,"11/11: vehicle data (TBOX SN&ICCID as well as IHU ID) was provided by AGK plant. Then, vehicle data was imported into TSP. TR closed. +09/11: TR created being able to track the resolving the issue. locally No need to follow in daily's meeting",Low,close,local O&M,Vsevolod Tsoi,11/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG015249,,,,Vsevolod Tsoi,,,,,,2 +TR901,Mail,09/11/2025,,VK ,VK services do not work. Video of the issue is attached to the TR.,"1125: 该问题云平台上未查询到日志，尝试清除激活记录，后台手动刷新，可建议用户重新操作并反馈。如仍无法恢复，提供操作视频及时间点 +1121：TR重新开放（TR813同理）。服务仍无法运行。ICC日志已上传 +1113：已件见平台有流量使用记录，建议询问客户是否进行了什么操作。 +1110：反馈VK视频不可用，仅有操作视频，APN1，APN2均有使用记录，建议用户可尝试恢复出厂设置，如无法解决抓取主机日志分析","02/12: the user's feedback - VK video was restored. TR closed. +02/12: the user's feedback still pending. +28/11: same as TR813 - the user was asked to provide a feedback whether the apps were restored. +25/11：No logs were found for this issue on the cloud platform. Attempt to clear activation records and manually refresh the backend. Recommend that the user repeat the operation and provide feedback. If the issue persists, submit an operation video and the specific time stamp. +25/11: wait for 2nd line investigation of an ICC log. +21/11: TR re-opened (same with TR813). Services still do not work. ICC logs uploaded @赵杰 +18/11: temporary closed. +13/11: The platform shows traffic usage records for the item. We recommend asking the customer if they performed any actions. +10/11：Feedback indicates VK videos are unavailable, with only operational videos accessible. Both APN1 and APN2 show usage records. Users are advised to attempt a factory reset. If the issue persists, capture the DMC logs for analysis.",Low,close,生态/ecologically,Vsevolod Tsoi,02/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ8SD154646,,,"Логи Тихненко.zip,Video_issue.mp4",Vsevolod Tsoi,,,,,,23 +TR902,Mail,09/11/2025,,Remote control ,"Remote control doesn't work. When trying to execute any commands, an error message ""Vehicle is in deep slee"" comes up.","1120：11月18日已发送Tbox日志请求，请等待数据。 +1118:已联系用户，TBOX日志今日会获取到 +1114：等待用户反馈Tbox日志 +1110：远控无法正常工作。尝试执行任何指令时，均会弹出错误提示：“车辆处于深度睡眠状态”。平台未查询到实时数据，建议用户进站抓取TBOX日志","03/12: the user's feedback: remote control was restored => issue closed. +02/12: the user's feedback: remote control was restored => the issue closed. +27/11: a reminder sent. Wait for a reply. +25/11: the user has been asked to provide a feedback whether the remote conrol was restored. +21/11:Fixed. Users are advised to try again. +20/11: a request for Tbox log was sent Nov, 18. Thus, wait for data. +18/11: the user's contact data received. A request for Tbox log will be sent within today. +14/11: wait for the user's contact data to make a request for collecting Tbox log. +10/11: Remote control is not functioning properly. Attempting any command triggers the error message: ""Vehicle is in deep sleep mode."" The platform cannot retrieve real-time data. Users are advised to visit the station to capture TBOX logs.",Low,close,TBOX,Vsevolod Tsoi,02/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B5SG018170,,,"Picture_3.jpeg,Picture_1.jpeg,Picture_2.jpeg",Vsevolod Tsoi,,,,,,23 +TR903,Mail,10/11/2025,,Remote control ,AC control command can not be executed only - see photos attached. An error message "Please try again later" comes up. All other commands work well.,"1202:协商一致，转暂时关闭 +1127: 等待经销商的反馈。 +1118：已向经销商反馈意见。 +1113：日志显示控制器反馈状态失败，转售后硬件排查空调控制器 +1110：命令日期时间 08/11 17:52（莫斯科时间）。Tbox日志已上传。"," +02/12: dealer's feedback pending.------temp close +27/11: wait for dealer's feedback. +18/11: feedback was provided to the dealer. +13/11：The log indicates a failure in receiving feedback status from the controller. Escalate to after-sales for hardware troubleshooting of the air conditioner controller.@Vsevolod Tsoi +10/11: command date&time 08/11 at 17:52 Moscow time. Tbox log uploaded. ",Low,temporary close,TBOX,刘娇龙,02/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ3SD094839,,,"LOG_LNNBDDEZ3SD09483920251110003247.tar,AC_control_command_exectuing_issue.JPG",Vsevolod Tsoi,,,,,,22 +TR904,Telegram bot,10/11/2025,,Application,Customer can't bind the car Chery T9 (t28) - A00196 error,"1111：已删除异常数据，请用户重新尝试 +1111：APP反馈有使用+79和79同一个手机号不同格式注册，导致报错，需要删除异常数据","27/11: No Feedback - temporary close +25/11: Waiting for feedback +18/11: Waiting for feedback +11/11：The abnormal data has been deleted. Please try again.@Kostya +11/11: The app has reported an error where the same phone number was registered using both the +79 and 79 formats. The abnormal data needs to be deleted..",Low,temporary close,用户CHERY-APP(User),Kostya,27/11/2025,CHERY TIGGO 9 (T28)）,LVTDD24BXRG088507,,,"Picture_1.jpg,Picture_2.jpg",Kostya,,,,,,17 +TR905,Telegram bot,10/11/2025,,Network,"Dead TBOX - No login, no remote logs, no data -> deep sleep -> data for inviting to station requested - waiting for data",1110：等待TBOX日志,"27/11: Fixied by itself - close +25/11: waiting for logs +18/11： waiting for logs +11/11： waiting for logs +10/11： waiting for logs",Low,close,TBOX,Kostya,27/11/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ0SD152776,,TGR0004682,,Kostya,,,,,,17 +TR906,Telegram bot,10/11/2025,,Network,"Dead TBOX - No login, no remote logs, no data -> deep sleep - waiting for data +死机状态的TBOX - 无登录记录、无远程日志、无数据 -> 深度休眠 - 等待数据",1110:同TR902,"27/11: Fixied by itself - closed +25/11: waiting for logs +18/11： waiting for logs +11/11： waiting for logs +1110: Same as TR902",Low,close,TBOX,项志伟,27/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B4SG018273,,TGR0004785,,Kostya,,,,,,17 +TR907,Mail,10/11/2025,,Remote control ,The user can't bind his car after changing 12V battery. An error A00196 comes up when trying to bind the car.,"由于重复，关闭该问题，信息已合并至TR904 +1112：核实为注册的手机号格式导致，同TR904，已清除异常数据，建议询问用户目前是否正常，另外建议合并处理，因为VIN相同 +1111：需要更多信息划转问题VIN、大概的操作时间","This issue is closed due to duplication. Information has been merged into TR904. +12/11: the user was asked to check whether the issue is solved out. +12/11: Verified as caused by the registered mobile number format, same as TR904. Abnormal data has been cleared. Recommend inquiring with the user whether the current status is normal. Additionally, recommend consolidated processing since the VIN is identical.@Vsevolod Tsoi +11/11: Additional information is required regarding the VIN transfer issue and the approximate processing time.",Low,close,用户EXEED-APP(User),岳晓磊,12/11/2025,CHERY TIGGO 9 (T28)）,LVTDD24BXRG088507,,,"Picture_1.jpg,Picture_2.jpg",Vsevolod Tsoi,,,,,,2 +TR909,Mail,11/11/2025,,Traffic is over,"Abnormal traffic consumption. All the traffic was used up on Nov, 1st and 2nd","暂无进展，该类异常消耗详细见TR1039分析进展 +1203：后台显示用户已升级成功，可联系用户确认。---需要等待用户复现后，抓取对应的IHU日志 +1202：用户已获5GB流量补偿——SIMBA确认。已提供车辆清单。OTA下载失败——FOTA后端行为——""隐私协议文件复制失败""——这意味着什么？-------已转OTA核实原因 +1120：将于12月起向SIMBA提交流量费用报销申请。 +1118：等待第二批次将车辆纳入其中。 +1112：OTA侧反馈已构建好任务，无法额外添加，只添加到第二批次的推送中","09/12: the OTA upgrade was successfully completed on December, 4th. When the issue occurs, an ICC log will be requested. +03/12: The backend shows the user has upgraded successfully. You may contact the user to confirm. +02/12: the user was reimbursed with 5GB - confirmed by SIMBA. A list of car is provided. OTA download failed - behaviour in FOTA backend - ""Privacy Agreement Copy File Failure"" - what does it mean?----------will be confirmed after meeting +27/11: still did not recieve the list.-------will check +25/11: has this vehicle been added to the 2nd batch OTA campaign @赵杰 ? ------- A list will be provided after the meeting (OTA list) +20/11: a request for reuimbursement of the traffic will be sent to SIMBA beginning Decebmber. +18/11: wait for the 2nd batch to include the car. +12/11: OTA side feedback indicates tasks have been successfully built and cannot be added additionally; they will only be included in the second batch of pushes.@Vsevolod Tsoi +11/11: adding to the small OTA batch monitoring function release to confirm @Jeason. Traffic reimbursement to confirm with Simba => Andrey ",Low,Processing,DMC,Vsevolod Tsoi,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ2SD449371,,,Traffic_consumption_issue.JPG,Vsevolod Tsoi,,,,,, +TR910,Mail,11/11/2025,,Remote control ,Remote control issue - commands are not executed,"1118：TSP检查：11月16日和17日的命令已成功执行 => 已要求客户确认问题是否仍存在。 +1112：TBOX侧日志反馈11月9日远控时间段内实车网络环境异常，11月10日远控记录均成功，建议用户下次可以换个地方重新尝试。 +1112：已见9号远控全部失败，10号开始远控正常，转TBOX侧分析日志","25/11: no feedback - TR closed. +20/11: a reminder was sent. If no reply by Tuesday's meeting, TR will be closed. +18/11: TSP checked out: commands were successfully executed on 16/11 and 17/11 => customer has been asked to confirm whether the issue still takes place. +12/11: TBOX side log feedback indicates abnormal vehicle network conditions during the remote control session on November 9. All remote control attempts on November 10 were successful. We recommend the user try again from a different location next time.@Vsevolod Tsoi +12/11: Remote control for Unit 9 has completely failed. Remote control for Unit 10 has started normally. Switch to TBOX side for log analysis. +11/11: command name - engine start on 09/11/2025 at 11:25. Screenshot of an error attached as well as tbox log",Low,close,TBOX,芮千,25/11/2025,Tenet T7 (T1E),EDEFB32B5SE001050,,,"LOG_EDEFB32B5SE001050_11_11_2025.tar,Picture_2.jpg,Picture_1.jpg",Vsevolod Tsoi,,,,,,14 +TR911,Mail,12/11/2025,,Remote control ,AC switching command is not exeuted - see picture attached,"1204：已发送提醒。 +1202：在创建的对应群聊中解决问题后，要求用户反馈AC命令操作是否已恢复。 +1127: 会后拉属地运维入群讨论 +1126：测试车辆已到位。应用日志等数据将稍后提供。 +1125：仍在处理中。 +1119:怀疑是APP侧未将远控指令发送成功，将提供测试软件包，尝试使用测试软件包远控，同时反馈对应车控日志https://www.pgyer.com/8ebdf4ca6db8fe3d75bf8d498ffcdbb8。供跟国内分析。日志的路径在文件管理中，Android/data/com.chery.rus.exlantix/files/local/ 目录中 +1119:后台无 莫斯科时间11月10日13:41的远控记录，转tbox分析 +1118:会后确认最新分析结果 +1112:TSP无远控记录，实时数据检查正常，建议用户使用wifi尝试下发远控请求，并反馈操作时间。","09/12: the user's feedback - the issue with AC command was solved => TR closed. +04/12: a reminder sent. +02/12: following the sorting the issue out in the created respective group chat, the user was asked to provide a feedback whether AC command operation was restored. +27/11: After the meeting, invite local operations and maintenance personnel to join the group for discussion. +26/11: we have our test car. Data such as app log and will be provided later on. +25/11: still in process. +19/11:We suspect the remote control commands may not have been successfully transmitted from the app side. We will provide a test software package for user to attempt remote control using it. Please also provide the corresponding vehicle control logs from https://www.pgyer.com/8ebdf4ca6db8fe3d75bf8d498ffcdbb8 for analysis by our domestic team. The log path is located in the file manager under the directory: Android/data/com.chery.rus.exlantix/files/local/. + +18/11: the user was asked to provide whether the issue is still valid. +12/11: command - AC switching, operation time&date - Nov, 10th at 13:41 Moscow time. +12/11:No remote control records are available in TSP. Real-time data checks are normal. We recommend that users attempt to send remote control requests via Wi-Fi and provide feedback on the operation time.",Low,close,车控APP(Car control),Vsevolod Tsoi,09/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ4SD484736,,,AC_control_executing_issue.JPG,Vsevolod Tsoi,,,,,,27 +TR914,Telegram bot,12/11/2025,,Remote control ,"Remote control is not available since Tbox is in deep sleep. +由于Tbox处于深度睡眠状态，无法进行远程控制。",1112:激活后无TBOX登录记录，建议用户进站获取TBOX日志分析,"24/11: Fixed +21/11:Fixed. Users are advised to try again. +20/11: confirmed by dealer - customer's visit for Tbox log is scheduled for Nov, 31st. +12/11: No TBOX login records after activation. Users are advised to visit the station to obtain TBOX logs for analysis. +13/11: Wrote to Sergey.Belov@tenet.ru asking him to invite the client to the dealership to record the logs",Low,close,TBOX,项志伟,24/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B0SG018187,,TGR0004749,20251112-104357.jpg,Vladimir|米尔,,,,,,12 +TR915,Telegram bot,12/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,1112:激活后无TBOX登录记录，建议用户进站获取TBOX日志分析,"24/11: Fixed +21/11:Fixed. Users are advised to try again. +12/11: No TBOX login records after activation. Users are advised to visit the station to obtain TBOX logs for analysis. +13/11: Wrote to Sergey.Belov@tenet.ru asking him to invite the client to the dealership to record the logs",Low,close,TBOX,项志伟,24/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B6SG018596,,TGR0004857,20251112-152046.jpg,Vladimir|米尔,,,,,,12 +TR920,Telegram bot,13/11/2025,,Traffic is over,Abnormal traffic consumption. All the traffic was used up on Nov 1st,"暂无进展，该类异常消耗详细见TR1039分析进展 +1114：建议邀请用户抓取DMC日志，如果客户愿意升级，可对其升级最新系统------需要等待用户复现后，抓取对应的IHU日志 +1113：OTA侧反馈已构建好任务，无法额外添加，只添加到第二批次的推送中。","14/11: Recommend inviting users to capture DMC logs. If customers are willing to upgrade, they can be upgraded to the latest system of DMC. +13/11: OTA side feedback indicates tasks have been successfully built and cannot be added additionally; they will only be included in the second batch of pushes.@Vladimir Vdovichenko",Low,Processing,DMC,Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ1SD152690,,TGR0004748,,Vladimir|米尔,,,,,, +TR922,Telegram bot,13/11/2025,,Missing in admin platform,"No car in the CHERY APP - EDEDD24B8SG004134 +Please add the car into the Chery Admin Platform DB https://growing-admin.chery.ru/","1118：等待处理 +1117：反馈无法录入，提示账号到期，转信息公司处理 +1113：请属地核实该车EPTS，后可由属地自行上传至APP后台","27/11: Got the access - car added - closed +18/11:Awaiting processing by the information company +17.11:please update status @赵杰 +13/11: EPTS - 164301115201509 +13/11：Please have the local authority verify the vehicle's EPTS. Subsequently, the local authority may upload it to the app's backend independently.",Low,close,TSP,Kostya,27/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B8SG004134,,TGR0004881,,Kostya,,,,,,14 +TR924,Telegram bot,13/11/2025,,Traffic is over,Abnormal traffic consumption. All the traffic was used up on Nov 1st and 2nd,"暂无进展，该类异常消耗详细见TR1039分析进展 +1114：建议邀请用户抓取DMC日志，如果客户愿意升级，可对其升级最新系统-----需要等待用户复现后，抓取对应的IHU日志 +1114：OTA侧反馈已构建好任务，无法额外添加，只添加到第二批次的推送中。","14/11：Recommend inviting users to capture DMC logs. If customers are willing to upgrade, they can be upgraded to the latest system. +14/11: OTA side feedback indicates tasks have been successfully built and cannot be added additionally; they will only be included in the second batch of pushes.@Vladimir Vdovichenko",Low,Processing,DMC,Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ2SD449371,,TGR0004764,Screenshot 2025-11-13 150135.png,Vladimir|米尔,,,,,, +TR925,Telegram bot,13/11/2025,,Activation SIM,"The vehicle is displayed in the TSP, but there is no data from the T-BOX installed in the car. The customer cannot activate the IoV services.","1114:已与国内项目确认，该车不支持车联网，无法使用手机APP +1114：确认无TBOX，ICCID信息，需要确认信息后手动在后台录入 +1114：未在TSP查看到该车VIN信息，请检查是否是VIN输入错误","14/11:Confirmed with the domestic project team: This vehicle does not support telematics and cannot be operated via a mobile app. +14/11: Confirmed no TBOX or ICCID information. Manual entry in the backend is required after verifying the details. +14/11：The vehicle's VIN information was not found in the TSP system. Please verify that the VIN was entered correctly.",Low,close,TSP,Vladimir|米尔,18/11/2025,JAECOO J7（T1EJ）,LVVDB21B1RC069210,,TGR0004769,,Vladimir|米尔,,,,,,5 +TR926,Telegram bot,13/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,1112:激活后无TBOX登录记录，建议用户进站获取TBOX日志分析,"24/11:Fixed +21/11:Fixed. Users are advised to try again. +14/11: Wrote to Sergey.Belov@tenet.ru asking him to invite the client to the dealership to record the logs +12/11: No TBOX login records after activation. Users are advised to visit the station to obtain TBOX logs for analysis.",Low,close,TBOX,项志伟,24/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24BXSG012106,,TGR0004817,Screenshot 2025-11-13 164011.png,Vladimir|米尔,,,,,,11 +TR927,Mail,13/11/2025,,VK ,"VK doesn't work. Activation license is required - see photo attached. An annual sevice package was paid Ocotber, 19","1218：反馈VK仍不可使用， +1211：等待客户反馈 +1209: 在与客户联系中 +1202：暂无反馈,属地建议不关闭此TR +1127:已联系用户，等待用户反馈 +1114:未见附图，但apn2未使用完，可让DMC使用手机热点，观察VK是否恢复,并同时抓取DMC日志分析","23/12: please check the license status———not the licenses issue ,need to upgrade the latest version by OTA +18/12: VK App still unable. Please waiting for media details. Liccense activation issue please check on your side video in attachments +11/12: Waiting for feedback +09/12: In contact with customer +02/12: No feedback from user - please don't close the ticket +27/11: In chat with user - waiting for info +14/11: No attached diagram available, but since APN2 is not fully utilized, allow DMC to use the mobile hotspot. Observe whether VK recovers while simultaneously capturing DMC logs for analysis.",Low,Processing,生态/ecologically,Kostya,18/12/2025,JAECOO J7（T1EJ）,LVVDB21B7RC080180,,,20251218-123512.mp4,Kostya,,,,,,35 +TR928,Mail,13/11/2025,,doesn't exist on TSP,Vehicle data is missing for T28 localy produced at AGL plant. Required information was requested.,1113：请属地核实该车EPTS，后可由属地自行上传至APP后台,"17/11: vehicle data was provided by AGK => TSP has just been configured. TR closed. +13/11: no need to track the issue in dayly meetings +13/11：Please have the local authority verify the vehicle's EPTS. Subsequently, the local authority may upload it to the app's backend independently.",Low,close,用户CHERY-APP(User),Vsevolod Tsoi,17/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24BXSG014521,,,,Vsevolod Tsoi,,,,,,4 +TR929,Telegram bot,14/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,1114:激活后无TBOX登录记录，apn2使用正常，建议用户进站获取TBOX日志分析,"24/11: Fixed +21/11:Fixed. Users are advised to try again. +14/11: No TBOX login records after activation. APN2 is functioning normally. We recommend users visit our station to obtain TBOX logs for analysis. +17/11 Wrote to Sergey.Belov@tenet.ru asking him to invite theclient to the dealership to record the logs",Low,close,TBOX,项志伟,24/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B8SG018292,,TGR0004799,Screenshot 2025-11-14 094708.png,Vladimir|米尔,,,,,,10 +TR933,Telegram bot,14/11/2025,,Traffic is over,Abnormal traffic consumption. All the traffic was used up on Nov 1st and 2nd,"暂无进展，该类异常消耗详细见TR1039分析进展 +1114：建议邀请用户抓取DMC日志，如果客户愿意升级，可对其升级最新系统-------需要等待用户复现后，抓取对应的IHU日志 +1114：OTA侧反馈已构建好任务，无法额外添加，只添加到第二批次的推送中。","14/11：Recommend inviting users to capture DMC logs. If customers are willing to upgrade, they can be upgraded to the latest system. +14/11: OTA side feedback indicates tasks have been successfully built and cannot be added additionally; they will only be included in the second batch of pushes.@Vladimir Vdovichenko",Low,Processing,DMC,Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ1SD443013,,TGR0004805,,Vladimir|米尔,,,,,, +TR934,Telegram bot,14/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,1114:激活后无TBOX登录记录，apn2使用正常，建议用户进站获取TBOX日志分析,"24/11: Fixed +21/11:Fixed. Users are advised to try again. +14/11: No TBOX login records after activation. APN2 is functioning normally. We recommend users visit our station to obtain TBOX logs for analysis. +17/11 Wrote to Sergey.Belov@tenet.ru asking him to invite theclient to the dealership to record the logs",Low,close,TBOX,项志伟,24/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B1SG018554,,TGR0004807,,Vladimir|米尔,,,,,,10 +TR935,Mail,14/11/2025,,Remote control ,Remote control doesn't work as well as VK services. Tbox is in deep sleep. Photo of version in the engineering meny attached. 12V battery terminals were taken off for a while => no result,"1120：等待反馈 +1118:要求用户确认该问题是否已关闭。 +1114：反馈自激活起，始终无TBOX登录记录，无APN1，APN2消耗，断连12V小电池仍无反应。尝试手动停卡后再启用，恢复登录，已抓取TBOX日志。客户侧可告知重新尝试。告知用户后，该问题可关闭","25/11: dealer's feedback - VK services are restored. TR closed. +20/11: waiting for feedback +18/11: the user was asked to confirm whether the issue was solved out. +14/11: Since activation, no TBOX login records have been recorded. No consumption from APN1 or APN2. No response even after disconnecting the 12V backup battery. Attempted manual card deactivation followed by reactivation restored login functionality. TBOX logs have been captured. Customer side may be advised to retry.@Vsevolod Tsoi After notifying the user, this issue can be closed.",Low,close,TBOX,Vsevolod Tsoi,25/11/2025,EXEED RX（T22）,LVTDD24B4RG023474,,,"IMG_20251113_122315.jpg,IMG_20251113_122253.jpg",Vsevolod Tsoi,,,,,,11 +TR937,Mail,17/11/2025,,Remote control ,"Tail gate is shown as opened in the app but closed in reality. O&J support team's feedback: thet receive an opened tailgate status from TSP. +应用程序显示尾门处于打开状态，但实际已关闭。O&J支持团队反馈：他们从TSP处接收到的尾门状态为打开。",1117：与车型项目组核实，该车不支持APP电动尾门，已修正配置，请用户重新尝试，并告知用户该功能无法APP开启。,"25/11: there were no more issues since fixing. TR closed. +17/11: ok. Then will wait for a while whetehr the isse comes up again. If no, TR will be closed. +17/11: After verifying with the vehicle model project team, this vehicle does not support the app-controlled power tailgate. The configuration has been corrected. Please have the user try again and inform them that this function cannot be activated via the app.",Low,close,TBOX,芮千,25/11/2025,Tenet T7 (T1E),EDEFB32B3SE000978,,,"LOG_EDEFB32B3SE00097820251117084503.tar,Opened_tailgate.jpg,image.jpg",Vsevolod Tsoi,,,,,,8 +TR938,Telegram bot,17/11/2025,,OTA,The customer is unable to install the HU update because the process consistently fails with an error. I can see in the OTA logs that an error occurred during the first update attempt,"1223：等待反馈 +1218：下周四无反馈，转暂时关闭 +1212: 等待客户反馈 +1209: 等待客户反馈 +1204:等待客户反馈 +1128：该版本为解决仪表黑屏的测试版本，建议用户进站更新DMC版本 +1124:上述为OTA平台上的版本信息，需要核实用户车机上的版本信息，因为推送发现是小版本不匹配导致的报错。 +1120: ""sv"": ""02.00.00_02.00.00"", + ""app_v"": ""1.0.49.2508.one"", + ""sdk_v"": ""2.1.2.2508-r"" +1118: OTA反馈是版本不匹配，需要查看实车具体的DMC版本信息 +1118：无法更新HU软件，OTA平台查看时，反馈首次更新时就出现报错，转OTA分析","23/12: Waiting for feedback +11/12: The customer has contacted the dealership. We are awaiting an update +11/12: Waiting for feedback +09/12: Waiting for feedback +04/12: Waiting for feedback +02/12: We asked the customer for their details to invite them to the dealership +28/11: This version is a test release addressing the instrument panel black screen issue. Users are advised to update to the DMC version at the service station. +27/11: @赵杰 New photo added with extended version +24/11: New photo attached @赵杰-------To view a more detailed version, please click 02.00.00 repeatedly. @Vladimir Vdovichenko +24/11：The above version information is from the OTA platform. It is necessary to verify the version information on the user's in-vehicle system, as the push notification error was caused by a minor version mismatch. +20/11: ""sv"": ""02.00.00_02.00.00"", + ""app_v"": ""1.0.49.2508.one"", + ""sdk_v"": ""2.1.2.2508-r"" +18/11: OTA feedback indicates a version mismatch. The specific DMC version information of the actual vehicle must be checked. +18/11：Unable to update HU software. When checked via the OTA platform, an error occurred during the initial update attempt. Refer to OTA for analysis.",Low,Processing,OTA,董晶晶,,EXEED VX FL（M36T）,XEYDD14B1SA010582,,TGR0004739,"file_6316.jpg,file_5670.jpg,Screenshot 2025-11-17 124422.png,file_5874.jpg,file_5875.jpg",Vladimir|米尔,,,,,, +TR940,Mail,17/11/2025,,Network,Dead tbox - no login deep sleep - waiting for logs,1118：尝试手动停卡，已见TBOX恢复登录，已核实是MTS侧激活时未切换SIM卡状态，可告知用户现在已恢复，近期SIM卡APN1，APN2均无使用记录的情况可在TSP中停卡10分钟后重启，观察是否可以恢复,"27/11: Solved - user feedback - close +25/11：waiting for Feedback. +20/11:same as +18/11:Attempted manual card suspension. TBOX login has been restored. Verified that MTS failed to switch SIM card status during activation. Inform user that service is now restored. For recent cases where both APN1 and APN2 show no usage records, suspend the card for 10 minutes in TSP, then restart to observe if recovery occurs.",Low,close,TBOX,Kostya,27/11/2025,EXEED RX（T22）,XEYDD14B3RA011415,,"Рожнева Оксана Иркиновна +Нет связи EXEED Connect. Работает только погода. Подключение к телефонам не работает. +Владельцы: +Погодаев Антон Игоревич - XEYDD14B3RA011415 +7(913)0610147 + +Погодаева Юлия Владимировна - LVTDD24B4RG023474 +7(913)7899009",,Kostya,,,,,,10 +TR941,Mail,17/11/2025,,Network,Dead tbox - no login deep sleep - waiting for logs,1118:目前已见TBOX，DMC登录记录，平台未做任何操作，同TR940，目前TBOX登录已正常，建议告知用户后，关闭该问题,"27/11: Solved - user feedback - close +18/11：TBOX and DMC login records are currently visible. The platform has not performed any actions. Similar to TR940, TBOX login is now functioning normally. Recommend informing the user and closing this issue. +17.11: Log attached",Low,close,TBOX,谢恩堂,27/11/2025,EXEED RX（T22）,LVTDD24B4RG023474,,"Рожнева Оксана Иркиновна +Нет связи EXEED Connect. Работает только погода. Подключение к телефонам не работает. +Владельцы: +Погодаев Антон Игоревич - XEYDD14B3RA011415 +7(913)0610147 +Погодаева Юлия Владимировна - LVTDD24B4RG023474 +7(913)7899009",tboxlog.tar,Kostya,,,,,,10 +TR942,Mail,17/11/2025,,Remote control ,Nothing works neither remote control nor VK services. Tbox is on deep sleep.,"1127：通过TSP重启SIM卡后，Tbox开始登录——详见附图。经销商反馈：远程控制及服务功能均已恢复。TR已关闭。 +1127：TBOX日志已上传，请取用进行调查。----SIM卡状态需核实,MTS状态刷新逻辑仍有缺陷 +1127：经销商数据待处理。 +1124：已发送TBOX日志请求，并使用诊断工具检查故障。 +1118：尝试手动停卡启用，无法恢复，怀疑是TBOX故障，建议进站使用OBD读取故障码，同时抓取Tbox日志回传分析。主机登录记录，有可能是使用了手机热点。","27/11: after restarting sim card via TSP, Tbox started loging in - see photo attached. Dealer's feedback - remote control as well as services operation were restored. TR closed. +27/11: tbox log uploaded. Please take it for investigation +27/11: data is pending from dealer. +24/11: request for TBOX log has been sent as well as check a faults using diagnostic tool. +18/11: Attempted manual card deactivation and reactivation failed. Suspect TBOX malfunction. Recommend visiting a service station to read fault codes via OBD and capture TBOX logs for analysis. Host login records indicate possible use of a mobile hotspot.",Low,close,TBOX,Vsevolod Tsoi,27/11/2025,OMODA C7 (T1GC),LVUGFB224SD830798,,Газенкамф Алексей Эдуардович ,"20251126102813_tboxlog.tar,Deep_sleep.JPG",Vsevolod Tsoi,,,,,,10 +TR943,Telegram bot,18/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,1118:激活后无TBOX登录记录，apn1无使用记录，APN2正常使用，建议用户进站抓取TBOX日志分析,"24/11: fixed +21/11:Fixed. Users are advised to try again. +18/11: Wrote to Sergey.Belov@tenet.ru asking him to invite theclient to the dealership to record the logs +18/11: No TBOX login records after activation.,APN1 shows no usage records, APN2 is functioning normally. We recommend the user visit the station to retrieve TBOX logs for analysis.",Low,close,TBOX,项志伟,24/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG009693,,TGR0004897,,Vladimir|米尔,,,,,,6 +TR944,Telegram bot,18/11/2025,,HU troubles,"The applications on the HU are not working. I checked and found that the TSP had the full PKI, while the PKI Admin showed the short one. I tried updating it in the TSP, but it didn't resolve the issue. The customer reports that the applications are still non-functional.",1119:平台上看，主机在18，19号登陆成功，实车最近一次调用PKI接口也是成功的。需要和客户确认下问题是否解决，如果问题仍然存在，需要故障现象视频和DMC日志。,"1121: 1 year package has expired +1119: A request has been forwarded to the customer +1119: On the platform, the host successfully logged in on the 18th and 19th. The actual vehicle's most recent invocation of the PKI interface was also successful. We need to confirm with the customer whether the issue has been resolved. If the problem persists, we require a video of the fault symptoms and the DMC log.@Vladimir Vdovichenko",Low,close,DMC,Vladimir|米尔,21/11/2025,JAECOO J7（T1EJ）,LVVDD21B7RC077399,,TGR0004816,,Vladimir|米尔,,,,,,3 +TR945,Telegram bot,18/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,"1202:协商一致，转暂时关闭 +02/12：等待客户回复 +25/11：等待客户回复 +1121：已修复。建议用户重新尝试。 +1119:激活后无TBOX登录记录，apn1无使用记录，APN2正常使用，建议用户进站抓取TBOX日志分析","02/12: Waiting for customer response - temp close +25/11: Waiting for customer response +21/11:Fixed. Users are advised to try again. +19.11: Wrote to Sergey.Belov@tenet.ru asking him to invite the cliernt to the dealership to record the logs +19/11:No TBOX login records after activation. APN1 shows no usage records, APN2 is functioning normally. It is recommended that the user visit the station to retrieve TBOX logs for analysis.",Low,temporary close,TBOX,项志伟,02/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24BXSG014518,,TGR0004905,,Vladimir|米尔,,,,,,14 +TR946,Telegram bot,18/11/2025,,Remote control ,"The customer reports recurring errors when controlling the car via the application in the morning, typically between 7:40 and 8:00 AM Moscow Time. For example, on the following timestamps, the commands failed to execute: +2025-11-14 07:44:04 +2025-11-14 07:45:35 +2025-11-14 07:52:52 +2025-11-18 07:42:47 +Furthermore, the vehicle status during this time period is also often displayed incorrectly. The customer asks to clarify the root cause and explain why the commands were not executed on these specific dates and times. +客户报告称，每日早晨通过应用程序控制车辆时会反复出现故障，通常发生在莫斯科时间上午7:40至8:00之间。例如，在以下时间戳记录中，指令均未能执行： +2025-11-14 07:44:04 +2025-11-14 07:45:35 +2025-11-14 07:52:52 +2025-11-18 07:42:47 +此外，该时段内车辆状态显示也常出现异常。客户要求查明根本原因，并解释为何在上述具体日期和时间段内指令未能执行。","1218：下周二如无反馈，转等待数据 +1215：等待反馈 +1211：等待反馈 +1209：等待反馈 +1202：用户已约定明日进站 +1121：致函Pavel.Fersman@exeed.ru，请其邀请客户前往经销店记录日志。 +1119：由于TBOX日志无法远程获取，可提供操作指导，引导用户复现问题后，进入工程模式抓取TBOX日志分析。 +1119：远控偶发失败，失败原因：超时，TSP开发排查结果：车辆不在线，执行唤醒操作，tbox无响应，35s超时。待tbox工程师排查","15/12: Waiting for feedback-----waiting for data +11/12: Waiting for feedback +04/12: Waiting for feedback +02/12: The customer is scheduled to visit the dealership on December 3 +21/11: Wrote to Pavel.Fersman@exeed.ru asking him to invite the client to the dealership to record the logs +19/11: A request has been forwarded to the customer +19/11：Since TBOX logs cannot be retrieved remotely, we can provide operational guidance to assist users in reproducing the issue. Once the issue is reproduced, enter engineering mode to capture and analyze the TBOX logs. +19/11:Remote control occasional failure, cause: timeout. TSP development troubleshooting findings: vehicle offline. Wake-up operation executed, T-Box unresponsive, 35-second timeout. Awaiting T-Box engineer investigation.",Low,Waiting for data,TBOX,王桂玲,,EXEED VX FL（M36T）,LVTDD24B0PD638909,,TGR0004919,,Vladimir|米尔,,,,,, +TR957,Telegram bot,18/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,1119:激活后无TBOX登录记录，apn1无使用记录，APN2正常使用，建议用户进站抓取TBOX日志分析,"24/11: Fixed +21/11:Fixed. Users are advised to try again. +19/11: Wrote to Sergey.Belov@tenet.ru asking him to invite the client to the dealership to record the logs +19/11:No TBOX login records after activation.APN1 shows no usage records, APN2 is functioning normally. It is recommended that the user visit the station to retrieve TBOX logs for analysis.",Low,close,TBOX,项志伟,24/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B6SG016251,,TGR0004814,,Vladimir|米尔,,,,,,6 +TR958,Telegram bot,18/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,1119：TBOX自激活起未登录，建议用户进站获取TBOX日志。,"24/11: Fixed +19/11: Wrote to Sergey.Belov@tenet.ru asking him to invite the client to the dealership to record the logs +19/11: The TBOX has not been logged in since activation. Users are advised to visit the station to retrieve the TBOX log.",Low,close,TBOX,Vladimir|米尔,24/11/2025,EXEED RX（T22）,EDEDD24B9SG018625,,EDEDD24B9SG018625,,Vladimir|米尔,,,,,,6 +TR959,Mail,18/11/2025,,OTA,"The car can't get an OTA upgrade. Status in FOTA - package downloaded. Multimedia settigs were reseted to the factory but it did not bring any results. Still no an OTA upgrade available. Tbox is normal. MNO is OK. apn1&2 are OK as well +车辆无法接收OTA升级。FOTA状态显示：软件包已下载。多媒体设置已恢复出厂状态，但未见成效。仍无可用OTA升级。Tbox正常。移动网络运营商正常。APN1和APN2均正常。","1223： 已再次发送提醒。若在周四会议前未收到反馈，TR将暂时关闭，直至收到变更反馈为止。 +1215：已再次提醒经销商，等待反馈 +1211: 仍在等待关于DMC变更的反馈。 +1209：等待DMC变更反馈，以便我们使用新数据配置TSP。 +1204：已发送变更DMC的请求。 +1202：用户联系数据待处理。 +1127： 等待用户联系信息，以便向经销商提交DMC硬件变更请求。 +1120：主机工程师排查结果：主机是非网联的件，非网联的件无法OTA升级，需要更换为网联的件。 +1119: tbox最新版本，dmc比推送版本还新，发现主机有换过件。等待主机工程师排查。","23/12: a reminder was sent again. If no feedback by Thusday's meeting TR wil temporary be closed until receiving a feedback on changing. +15/12: a repeat reminder was sent. +11/12: still wait for a feedback on changing of DMC. +09/12: wait for a feedback on changing of DMC so that we can configure TSP with a new data. +04/12: a request for change DMC has been sent. +02/12: the user's contact data pending. +27/11: wait for the users contact data to prepare a request for DMC HW change to the dealer. +20/11: Dmc Engineer Investigation Findings: The host unit is a non-Telematics component. Non-networked components cannot be upgraded via OTA and require replacement with a Telematics DMC.@Vsevolod Tsoi +19/11: Latest version of tbox, DMC newer than the push version. Components have been replaced in the host. Awaiting investigation by the host engineer.",Low,Processing,After sales,Vsevolod Tsoi,,EXEED RX（T22）,XEYDD24B3RA004870,,TGR0004475,,Vsevolod Tsoi,,,,,, +TR961,Mail,19/11/2025,,Missing in admin platform,T28 is missing in admin Chery as well as in TSP.,1119：等待实车数据，同时等待信息公司处理app后台账号问题,"20/11: Admin Chery as well as TSP have been configured. +19/11: EPTS 16430117999986. A request has been sent to AGK for providinig TBOX and DMC data.",Low,close,用户CHERY-APP(User),岳晓磊,20/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG018572,,,,Vsevolod Tsoi,,,,,,1 +TR962,Mail,19/11/2025,,Missing in admin platform,T28 is missing in admin Chery as well as in TSP.,1119：等待实车数据，，同时等待信息公司处理app后台账号问题,"20/11: Admin Chery as well as TSP have been configured. +19/11: EPTS 164301117134286. A request has been sent to AGK for providinig TBOX and DMC data.",Low,close,用户CHERY-APP(User),岳晓磊,20/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B8SG015702,,,,Vsevolod Tsoi,,,,,,1 +TR964,Telegram bot,19/11/2025,,OTA,"The customer is unable to complete the OTA update. The process consistently fails and resets at 14% progress. We already recommended resetting the Head Unit (HU) to factory settings, but this did not resolve the issue.","1211：等待反馈 +1209：等待反馈 +1204：等待反馈 +1202：等待客户回复 +1119：OTA反馈，当前车内版本损坏，只能进站使用U盘升级","15/12: Waiting for feedback +11/12: Waiting for feedback----Turn to waiting for data +09/12: Waiting for feedback +04/12: Waiting for feedback +02/12: Waiting for customer response +19/11 A request has been forwarded to the customer +19/11：OTA feedback indicates the current in-vehicle software version is corrupted. A service station visit is required to perform the upgrade using a USB drive.",Low,Waiting for data,OTA,Vladimir|米尔,,EXEED RX（T22）,LVTDD24B3RG021134,,TGR0004840,,Vladimir|米尔,,,,,, +TR966,Telegram bot,19/11/2025,,HU troubles,"Customer can't use VK VIDEO, MUSIC, MESSENGER. Loged and reloged in memeber center","1209：已联系用户，等待反馈 +1204：日志显示12月1日网络接口已经正常了，建议用户尝试 +1202: 今日已将日志发送专业，等待分析结果 +1201：已获日志，转分析流程 +1127：未收到用户响应 - 等待数据 +1119:建议用户进站操作，并抓取主机日志，回传分析。","15/12: Solved after OTA +11/12: Waiting for feedback +09/12: In contact with customer +04/12: Logs indicate the network interface was restored on December 1st. Users are advised to attempt reconnection. +02/12: Logs attached----The logs have been sent to the professionals today, awaiting the analysis results. +01/12: Logs will be attached soon(Uploading) @赵杰 +27/11: Request has been sent - waiting for logs +27/11: No responce from user - waiting for data +19/11：Recommend that users perform on-site operations, capture DMC logs, and transmit them back for analysis.",Low,close,生态/ecologically,高喜风,16/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ4SD405047,,TGR0004880,"Саакян.zip,image.png",Kostya,,,,,,27 +TR968,Telegram bot,19/11/2025,,Missing in admin platform,T28 is missing in TSP. Also need to be chaked in chary admin (no access),"1211：等待用户反馈 +1209：等待用户反馈 +1204：等待用户反馈 +1124: 等待用户反馈 +1121：账号已处理，等待实车数据。 +1119：等待实车数据，，同时等待信息公司处理app后台账号问题","15/12: Waiting for feedback +11/12: Waiting for feedback +09/12: Waiting for feedback +04/12: Waiting for feedback +24/11: Waiting for customer response +21/11：Account processed, awaiting actual vehicle data. +19/11: Awaiting actual vehicle data. Simultaneously awaiting the information company to resolve the app backend account issue.",Low,temporary close,用户CHERY-APP(User),Vladimir|米尔,15/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG018606,,TGR0004933,,Vladimir|米尔,,,,,,26 +TR969,Telegram bot,19/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,"1202:协商一致，转暂时关闭 +21/11:Fixed. Users are advised to try again. +19/11:致函Sergey.Belov@tenet.ru，请其邀请客户前往经销店记录日志。 +1119:激活后无TBOX登录记录，apn1无使用记录，APN2正常使用，建议用户进站抓取TBOX日志分析","02/12: Waiting for customer response ---temp close +25/11: Waiting for customer response +21/11:Fixed. Users are advised to try again. +11/19: Wrote to Sergey.Belov@tenet.ru asking him to invite the client to the dealership to record the logs +19/11:No TBOX login records after activation.APN1 shows no usage records, APN2 is functioning normally. It is recommended that the user visit the station to retrieve TBOX logs for analysis.",Low,temporary close,TBOX,Vladimir|米尔,02/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG015249,,TGR0004936,,Vladimir|米尔,,,,,,13 +TR970,Telegram bot,19/11/2025,,doesn't exist on TSP,Internal KM issue - Pass this TR (VIN doesn't exist in the TSP - DATA requested from the plant),,,Low,Waiting for data,,,,CHERY TIGGO 9 (T28)）,EDEDD24B6SG018551 ,,TGR0005018,,Kostya,,,,,, +TR971,Telegram bot,19/11/2025,,Application,The customer cannot add the vehicle to the application. We have info in tsp. EPTS - 164301119222482,"1121：账号已处理，请将信息录入后，该问题可关闭。 +1120：等待信息公司处理app后台账号问题","21/11: The account has been processed. Please enter the information, and this issue can be closed. +20/19：Awaiting resolution of the app backend account issue by the information company.",Low,close,用户CHERY-APP(User),Vladimir|米尔,21/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG018605,,TGR0004935,,Vladimir|米尔,,,,,,2 +TR972,Telegram bot,19/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,"1119：apn1,apn2均无法使用，尝试手动停卡，目前已恢复，可告知用户尝试","19/11: remote control is avaliable +19/11: Both APN1 and APN2 were unavailable. Attempted manual card suspension. Service has now been restored. Please advise users to try again.",Low,close,TBOX,Vladimir|米尔,19/11/2025,CHERY TIGGO 9 (T28)）,LVTDD24B0RG131283,,TGR0004974,,Vladimir|米尔,,,,,,0 +TR973,Telegram bot,19/11/2025,,Remote control ,Remote control is not available. No tbox login/logout from 13 november,"1201：建议转等待数据，14天无反馈 +1121：等待客户回复 +1120:13号开始,TBOX无登录记录，DMC登录正常，建议用户进站获取tbox日志分析","15/12: Waiting for feedback +11/12: Waiting for feedback +09/12: Waiting for feedback +04/12: Waiting for feedback +02/12: Waiting for customer response +01/12： Recommendation to transfer pending data; no response within 14 days. +21/11: Pending customer response +20/11:Starting on the 13th, TBOX has not logged any records. DMC logs are normal. Users are advised to enter the station to obtain TBOX logs for analysis.",Low,Waiting for data,TBOX,Vladimir|米尔,,EXEED RX（T22）,XEYDD14B3RA009137,,TGR0004942,,Vladimir|米尔,,,,,, +TR975,Telegram bot,19/11/2025,,OTA,Cannot install ota update,"1211：等待反馈 +1209：等待反馈 +1204：等待反馈 +1121：等待客户回复 +1120：OTA工程师分析结果：VR版本不匹配导致的版本校验出错，需要客户进站用U盘升级主机版本","15/12: Waiting for feedback +11/12: Waiting for feedback-------turn to waiting for data +09/12: Waiting for feedback +04/12: Waiting for feedback +21/11: Pending customer response +20/11:OTA Engineer Analysis Findings: Version verification error caused by VR version mismatch. Customer must visit the service centre to upgrade the host version using a USB drive.@Vladimir Vdovichenko",Low,Waiting for data,OTA,韦正辉,,EXEED RX（T22）,LVTDD24B2RG023392,,TGR0004944,file_5916.jpg,Vladimir|米尔,,,,,, +TR976,Telegram bot,19/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,"1121：已修复，建议用户重新尝试 +1120:激活后无TBOX登录记录，apn1无使用记录，APN2正常使用，建议用户进站抓取TBOX日志分析","02/12: Fixed +25/11: Waiting for customer response +21/11:Fixed. Users are advised to try again. +21|11: Wrote to Sergey.Belov@tenet.ru asking him to invite the client to the dealership to record the logs +20/11:No TBOX login records after activation. APN1 shows no usage records, APN2 is functioning normally. It is recommended that the user visit the station to retrieve TBOX logs for analysis.",Low,close,TBOX,Vladimir|米尔,02/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B8SG004344,,TGR0004946,,Vladimir|米尔,,,,,,13 +TR977,Telegram bot,19/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,"1121：已修复，建议用户重新尝试 +1120:激活后无TBOX登录记录，apn1无使用记录，APN2正常使用，建议用户进站抓取TBOX日志分析","24/11: Fixed +21/11: Wrote to Sergey.Belov@tenet.ru asking him to invite the client to the dealership to record the logs +20/11:No TBOX login records after activation. APN1 shows no usage records, APN2 is functioning normally. It is recommended that the user visit the station to retrieve TBOX logs for analysis.",Low,close,TBOX,Vladimir|米尔,24/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B2SG018191,,TGR0004947,,Vladimir|米尔,,,,,,5 +TR978,Mail,19/11/2025,,Remote control ,No binding the car is possible in the app since TBOX data is missing in TSP but the car is in itself,,19/11: a request has been sent to AGK to provide the missing data of Tbox. No need to track it in dayly meetings,Low,local management,,,,,,,,,,,,,,, +TR979,Telegram bot,19/11/2025,,HU,"Login flow failure: User scans QR code in Exlantix app - gets ""success"" message in app - but the car's HU doesn't react. Still shows ""Authorization"" and QR code. +登录流程失败：用户在Exlantix应用中扫描二维码后，应用内显示""成功""提示，但车载主机未响应，仍显示""授权中""及二维码。","1209：等待反馈 +1204：等待反馈 +1202：等待客户回复 +1121：已联系客户 +1120：反馈车辆的vin绑了两个渠道（exeed，exlantix）需要解绑其中exeed账户绑定关系即可正常使用。 +1120：生态软件部门尝试复现，但客户侧建议可使用车机连接手机热点复现，有进展及时更新","09/12: Waiting for feedback-----------turn to waiting for data +04/12: Waiting for feedback +02/12: Waiting for customer response +21/11: wrote to the client +20/11: The vehicle's VIN is currently bound to two channels (EXEED, EXLANTIX). To resolve this, simply unbind the EXEED account association to restore normal functionality. +20/11: The ecological software department attempted to reproduce the issue, but the client suggested using the vehicle's system to connect to a mobile hotspot for reproduction. Updates will be provided promptly as progress is made.",Low,Waiting for data,用户EXEED-APP(User),Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ3SD407730,,TGR0005106,file_5923.jpg,Vladimir|米尔,,,,,, +TR980,Telegram bot,20/11/2025,,OTA,"Cannot install ota update. +His version: +""sv"": ""02.01.00_01.19.80"", +""app_v"": ""1.2.41.2415.one"", +""sdk_v"": ""4.0.1.2415-r""","1211：等待反馈 +1209：等待反馈 +1204：等待反馈 +1121:OTA工程师分析结果：VR版本不匹配导致的版本校验出错，需要客户进站用U盘升级主机版本","15/12: Waiting for feedback +11/12: Waiting for feedback-----turn to waiting for data +09/12: Waiting for feedback +04/12: Waiting for feedback +02/12: Waiting for customer response +21/11: wrote to the client +21/11:OTA Engineer Analysis Findings: Version verification error caused by VR version mismatch. Customer must visit the service centre to upgrade the host version using a USB drive.@Vladimir Vdovichenko",Low,Waiting for data,OTA,韦正辉,,EXEED RX（T22）,LVTDD24B9RG013717,,TGR0004982,"file_5957.jpg,file_5958.jpg,file_5959.jpg",Vladimir|米尔,,,,,, +TR982,Telegram bot,20/11/2025,,Application,"This ticket should NOT be assigned to the Chinese team. + +The customer is unable to add the vehicle to the application. We are currently waiting for access to the Chary Admin system to resolve this issue internally.",,,Low,close,TBOX,Vladimir|米尔,21/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B7SG004142,,TGR0004992,file_5973.jpg,Vladimir|米尔,,,,,,1 +TR984,Telegram bot,20/11/2025,,Remote control ,Remote control is not available. Data leak. Tbox version 64. Cannot make OTA update to fix it ,"1202:协商一致，转暂时关闭 +1121：已修复，建议用户重新尝试 +1121:等待OTA处理 ，同其他T28，版本为03版，apn1无使用记录，","18/12: Waiting for feedback +02/12: Waiting for customer response-----temp close +25/11: Waiting for customer response +21/11：Fixed. Users are advised to try again. +21/11: Awaiting OTA processing. Same as other T28 devices, version 03. APN1 shows no usage records.",Low,temporary close,TBOX,Vladimir|米尔,02/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B6SG018629,,TGR0005023,,Vladimir|米尔,,,,,,12 +TR985,Telegram bot,20/11/2025,,Remote control ,Remote control is not available. Data leak. Tbox version 64. Cannot make OTA update to fix it ,"1202：协商一致，暂时关闭 +1121：已修复，建议用户重新尝试 +1121:等待OTA处理 ，同其他T28，版本为03版，apn1无使用记录，","03/12: call center's feedback - confirmed, issue closed. +02/12: Fixed ------temp close +24/11: Waiting for customer response +21/11：Fixed. Users are advised to try again. +21/11: Awaiting OTA processing. Same as other T28 devices, version 03. APN1 shows no usage records.",Low,close,TBOX,Vladimir|米尔,03/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B3SG018622,,TGR0005026,,Vladimir|米尔,,,,,,13 +TR986,Telegram bot,20/11/2025,,Application,"The customer complains that when he set the air conditioning to run for 15 minutes, it only operates for 10 minutes and then turns off automatically. +客户投诉称，当他将空调设置为运行15分钟时，空调仅运行10分钟便自动关闭。",1121:已与项目核实，ICE车型仅支持app远控发动机10分钟，已调整配置，可告知用户该功能ICE仅可开启最大10分钟,"25/11: Fixed +24/11: Will we fix the UI?------ fixed +21/11: Verified with the project team that ICE models only support remote engine start via the app for a maximum of 10 minutes. Configuration has been adjusted accordingly. Please inform users that this ICE function can only be activated for a maximum duration of 10 minutes.",Low,close,TSP,Vladimir|米尔,25/11/2025,EXEED RX（T22）,XEYDD14B3RA008764,,TGR0005031,file_6032.jpg,Vladimir|米尔,,,,,,5 +TR987,Telegram bot,20/11/2025,,Remote control ,Remote control is not available. Data leak. Tbox version 64. Cannot make OTA update to fix it ,"1121：已修复，建议用户重新尝试 +1121:等待OTA处理 ，同其他T28，版本为03版，apn1无使用记录，","02/12: Fixed +24/11: Waiting for customer response +21/11：Fixed. Users are advised to try again. +21/11: Awaiting OTA processing. Same as other T28 devices, version 03. APN1 shows no usage records.",Low,close,TBOX,Vladimir|米尔,02/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B6SG018629,,TGR0005023,,Vladimir|米尔,,,,,,12 +TR988,Telegram bot,21/11/2025,,Remote control ,Remote control is not available. Data leak. Tbox version 64. Cannot make OTA update to fix it ,"1121：已修复，建议用户重新尝试 +1121:等待OTA处理 ，同其他T28，版本为03版，apn1无使用记录，","25/11: Solved +24/11: Waiting for customer response +21/11：Fixed. Users are advised to try again. +21/11: Awaiting OTA processing. Same as other T28 devices, version 03. APN1 shows no usage records.",Low,close,TBOX,Vladimir|米尔,25/11/2025,CHERY TIGGO 9 (T28)）,EDEDD24B1SG015413,,TGR0005042,,Vladimir|米尔,,,,,,4 +TR989,Telegram bot,21/11/2025,,Traffic is over,Abnormal traffic consumption. ,"暂无进展，该类异常消耗详细见TR1039分析进展 +1121：请属地确认是否在升级清单中，如在，请引导用户及时进展获取。------需要等待用户复现后，抓取对应的IHU日志","10/12: updated +24/11: No in update +21/11: Please confirm with the local authority whether it is included in the upgrade list. If so, guide users to promptly proceed with obtaining it.",Low,Processing,DMC,Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZXSD442748,,TGR0005059,Screenshot 2025-11-21 123028.png,Vladimir|米尔,,,,,, +TR990,Telegram bot,21/11/2025,,Remote control ,Remote control is not available. Timeout,"1202：协商一致，暂时关闭 +1121：已修复，建议用户重新尝试","18/12: Waiting for feedback +02/12: Waiting for customer response------temp close +21/11：Fixed. Users are advised to try again.",Low,temporary close,TBOX,Vladimir|米尔,02/12/2025,CHERY TIGGO 9 (T28)）,LVTDD24B3RG121797,,TGR0005024,,Vladimir|米尔,,,,,,11 +TR991,Telegram bot,21/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,"1202：协商一致，暂时关闭 +1124:用户反馈车控异常， +1121：已修复，建议用户重新尝试","08/12: the user's feedback - remote control was restored => TR closed. +02/12:------temp close +24/11: The customer is now experiencing a new issue: commands frequently fail to execute with error codes 8 and 9. The client requests clarification on the root causes. The logs have been attached. @赵杰 +21/11：Fixed. Users are advised to try again.",Low,close,TBOX,Vladimir|米尔,08/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B5SG014328,,TGR0005095,LOG_EDEDD24B5SG01432820251124120145.tar,Vladimir|米尔,,,,,,17 +TR992,Telegram bot,21/11/2025,,HU troubles,The customer cannot search for videos in the VK Video app,"1211:用户已进站，属地运维仍在等待日志 +1209：等待反馈 +1204：等待反馈 +1124：建议用户进站复现问题，并抓取DMC日志，如果用户配合，可以用户不进站抓取，自行抓取并上传。","15/12: Waiting for feedback +11/12: The customer has visited the dealership. We are awaiting the DMC log +09/12: Waiting for feedback +04/12: Waiting for feedback +02/12: Waiting for customer response +25/11: Waiting for customer response +24/11: Recommend that users reproduce the issue on the site and capture DMC logs. If users cooperate, logs can be captured without them visiting the site—capture and upload them independently.",Low,temporary close,生态/ecologically,Vladimir|米尔,15/12/2025,EXEED RX（T22）,LVTDD24B2RG032609,,TGR0004809,,Vladimir|米尔,,,,,,24 +TR993,Telegram bot,21/11/2025,,Remote control ,"Real-time vehicle status is not updating in the mobile application +Also why i unable to check or verify user permissions in the TSP platform? (screenshot attached)",1124：未查询到用户服务集，等待TSP核实是否用户使用了EXEED，EXLANTIX两个APP，目前已看到已删除EXEED绑定关系，建议用户在EXLANTIX上重新绑车即可,"18/12: Waiting for feedback +11/12: Waiting for feedback-----temp close +09/12: Waiting for feedback +02/12: Waiting for customer response +24/11: Wrote to the client +24/11: User service set not found. Awaiting TSP verification on whether the user has used both EXEED and EXLANTIX apps. Currently, the EXEED binding relationship has been deleted. We recommend the user rebind their vehicle in EXLANTIX.",Low,temporary close,TSP,Vladimir|米尔,11/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ5SD390302,,TGR0005070,"Screenshot 2025-11-21 165753.png,file_6080.jpg,file_6079.jpg",Vladimir|米尔,,,,,,20 +TR996,Telegram bot,21/11/2025,,Remote control ,AC control command can not be executed only - see photos attached. An error message "Please try again later" comes up. All other commands work well.,"1124：远控失败，提示控制器反馈状态失败，已有TBOX日志，TBOX侧反馈为空调件未反馈执行结果/未执行,转售后硬件","02/12: Fixed +24/11:Remote control failed. Controller feedback status failure detected. TBOX log available. TBOX side feedback indicates air conditioning component did not report execution result/did not execute. Escalate to after-sales hardware team.",Low,close,TBOX,刘娇龙,02/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ8SD163167,,TGR0005073,"Screenshot 2025-11-21 173910.png,LOG_LNNBDDEZ8SD16316720251121173732.tar",Vladimir|米尔,,,,,,11 +TR998,Mail,24/11/2025,,Network,No network is available in the car. No TBOX loging records are available in TSP,"1211: 迄今未收到TBOX日志 +1209：仍在等待Tbox日志。 +1204：等待Tbox日志。 +1202：已发送TBOX日志请求。 +1124:双APN无消耗，尝试停卡重启，无法恢复，建议用户进站抓取日志","23/12: no logs so far. +18/12: Tbox logs pending. +11/12: no logs received so far.------turn to waiting for data +09/12: still wait for Tbox logs. +04/12: wait for Tbox logs. +02/12: a request for TBOX log has been sent. +24/11: Dual APN with no data consumption. Attempted to stop the SIM card and restart, but failed to restore. Recommend that users visit the service station to get TBOX logs.",Low,Waiting for data,TBOX,Vsevolod Tsoi,,EXEED RX（T22）,XEYDD14B3RA012099,,Шалин Алексей Николаевич ,,Vsevolod Tsoi,,,,,, +TR999,Mail,24/11/2025,,PKI problem,"No network is available in the car. Apn1&2 are not OK. Short PKI is reqested however, there were successful IHU log in/out records in TSP. See picture and video attached.","1127：要求提供反馈，但尚未完成。 +1124:尝试停卡后，SIM卡正常，Pki有成功请求记录，可要求用户核实是否已解决。","04/12: no feedback. TR temporary closed. +02/12: a reminder sent to the dealer. If no feedback by Thursday's meeting, the issue will temporary be closed. +27/11: providing a feedback was asked but pending. +24/11:After attempting to suspend the card, the SIM card functions normally, and Pki shows a successful request record. You may ask the user to verify if the issue has been resolved.",Low,temporary close,TBOX,Vsevolod Tsoi,04/12/2025,JAECOO J7（T1EJ）,EDXDD21B9SC060683,,Savinsky Nikolay ,"VID-20251113-WA0006.mp4,Short_PKI_issue.JPG",Vsevolod Tsoi,,,,,,10 +TR1002,Telegram bot,24/11/2025,,Remote control ,Remote control is not available. Timeout,1124:查询远控记录，均提示超时，但该车辆远控时，TBOX均未唤醒，下发TBOX重启短信，CMP显示已送达，但TBOX未见重启记录，已有TBOX日志，转国内分析,"02/12: Fixed +1124: Querying remote control records consistently shows timeout errors. However, during remote control operations, the TBOX failed to wake up. A TBOX restart SMS was sent, and CMP indicates delivery confirmation. Yet, no restart record is visible in the TBOX. TBOX logs are available and have been forwarded for domestic analysis.",Low,close,TBOX,孙明明,02/12/2025,CHERY TIGGO 9 (T28)）,LVTDD24B3RG091426,,TGR0005100,,Vladimir|米尔,,,,,,8 +TR1003,Telegram bot,24/11/2025,,Application,The customer reports not receiving unauthorized access notifications.,"1209: 等待客户回复 +1209: 等待客户回复 +1204: 等待客户回复 +1202: 等待客户回复 +1125:用户反馈：为何开门时警报未响？----会后讨论 +1125:用户反馈车门被打开为什么没有报警。 +1125:该问题需要更多信息，（视频+具体时间点+操作），因为描述中未提及进行了什么操作。","18/12: Waiting for feedback +11/12: Waiting for feedback +09/12: Waiting for feedback +04/12: Waiting for feedback +02/12: Waiting for customer response +25/11: User feedback: Why didn't the alarm go off when the door was opened? +25/11: Wrote to the client +25/11: This issue req mention what actions were performed.",Low,temporary close,TENET app,Vladimir|米尔,18/12/2025,Tenet T7 (T1E),EDEFB32B2SE001202,,TGR0005104,,Vladimir|米尔,,,,,,24 +TR1004,Telegram bot,24/11/2025,,Remote control ,"Remote control is not available. +[{""0031"":0,""0032"":[54]}]","1211：等待反馈 +1209：等待反馈 +1204：等待反馈 +1202：等待反馈。 +1127：车主已变更，我们正在核实数据。 +1125:远控失败，反馈错误码为[54],转译为T-BOX认证失败，需要学习SK","15/12: Waiting for feedback +11/12: Waiting for feedback +09/12: Waiting for feedback +04/12: Waiting for feedback +02/12: waiting for feedback. +27/11: Еhe owner has changed, we are clarifying the data +25/11: Wrote to Sergey.Belov@tenet.ru asking him to invite the cliernt to the dealership +25/11:Remote control failed. Feedback error code [54], interpreted as T-BOX authentication failure. Requires learning the SK.",Low,temporary close,TBOX,Vladimir|米尔,15/12/2025,CHERY TIGGO 9 (T28)）,LVTDD24B7RG092191,,TGR0005115,,Vladimir|米尔,,,,,,21 +TR1005,Telegram bot,24/11/2025,,VK ,VK Vidoe doesn't work - Wrong licences ,"1127：等待客户反馈 +1126：生态同事已从后台手动升级，可让用户重新尝试 +1125：该问题需要DMC日志排查","04/12: No feedback - closed +02/12: Waiitng for feedback +27/11: Waiitng for feedback +26/11: The ecological team has manually upgraded from the backend. Users may now retry. +25/11: This issue requires troubleshooting via DMC logs.",Low,close,生态/ecologically,Kostya,04/12/2025,CHERY TIGGO 9 (T28)）,LVTDD24B5RG090682,,TGR0002413,image.png,Kostya,,,,,,10 +TR1007,Telegram bot,25/11/2025,,Remote control ,Remote control is not available. Timeout,"1211: 命令已执行，正在等待客户反馈 +1209：等待升级 +1202：等待升级 +1126: 已联系Andrey，添加到18.14.04版本，需要用户点击OTA更新TBOX软件，并反馈结果。 +1125:查询远控记录，均提示超时，但该车辆远控时，TBOX均未唤醒，下发TBOX重启短信，CMP显示已送达，但TBOX未见重启记录，已有TBOX日志，转国内分析","11/12: Commands have been executed, awaiting client feedback +09/12: Waiting for feedback +02/12: Waiting for upgrade +26/11: We have contacted Andrey and added this to version 18.14.04. Users need to click to update the TBOX software via OTA and provide feedback on the results. +25/11: Querying remote control records consistently shows timeout errors. However, during remote control operations, the TBOX failed to wake up. A TBOX restart SMS was sent, and CMP indicates delivery confirmation. Yet, no restart record is visible in the TBOX. TBOX logs are available and have been forwarded for domestic analysis.",Low,temporary close,TBOX,Vladimir|米尔,15/12/2025,EXEED RX（T22）,XEYDD14B3RA007090,,TGR0005094,,Vladimir|米尔,,,,,,20 +TR1008,Telegram bot,25/11/2025,,Remote control ,"AC control command can not be executed only. At the same time, others comands are working well.","1127：等待用户进站确认。 +1126：远控记录提示：控制器反馈状态失败，建议转售后硬件排查","04/12: Fixed +27/11: Wrote to the client. +26/11：Remote Control Log Alert: Controller status feedback failed. We recommend contacting after-sales support for hardware troubleshooting.",Low,close,After sales,Vladimir|米尔,04/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24BXSG018178,,TGR0005130,,Vladimir|米尔,,,,,,9 +TR1009,Mail,25/11/2025,,Remote control ,Tbox is in deep sleep => no remote control is available,"1204：已发送提醒。------若下周二会议前未收到反馈则关闭 +1202：tbox登录记录已恢复。已询问经销商用户遥控器是否已修复。 +1126，目前配置的套餐车辆TBOX无法使用APN2驻网，正在验证打开APN通道是否有效 +1126：自激活起无TBOX登录记录，今日有登录记录，已抓取TBOX日志，转入分析流程","17/12: feedback - remote control was restored. +09/12: TR temporary closed since there was no any feedback. +04/12: a reminder has been sent. ------if no Feedback by next Tuesday's meeting __closed +02/12: tbox log in recoreds were restored. Dealer was asked whether the user's remote control was restored. +26/11: Currently configured package vehicles' TBOX cannot use APN2 network access. Verifying whether opening APN2 channels is effective. +26/11: No TBOX login records since activation. Login records present today. TBOX logs captured and transferred to analysis process.",Low,close,TBOX,Vsevolod Tsoi,17/12/2025,Tenet T7 (T1E),EDEFB32B1SE016791,,Валентина Д. Фельдшерова ,,Vsevolod Tsoi,,,,,,22 +TR1010,Telegram bot,25/11/2025,,Remote control ,Remote control is not available since Tbox is in deep sleep.,"1126:同TR1009,目前有TBOX'登陆记录，但仍需验证方法是否有效","11.27: The client reported that everything is working------close +1126:同TR1009,目前有TBOX'登陆记录，但仍需验证方法是否有效",Low,close,TBOX,芮千,02/12/2025,Tenet T7 (T1E),EDEFB32B9SE016764,,TGR0005152,,Vladimir|米尔,,,,,,7 +TR1012,Telegram bot,26/11/2025,,VK ,The video in VK Video won't play. I have attached a recording of the error.,"1211：等待反馈 +1209: 等待反馈 +1204: 等待反馈 +1127: 已联系客户确认信息 +1126：视频中显示的VK视频版本较低，建议用户更新版本后，重新尝试，更新后仍然无法使用，建议用户配合复现并抓取DMC日志","15/12: Waiting for feedback +11/12: Waiting for feedback +09/12: Waiting for feedback +04/12: Waiting for feedback +27/11: Wrote to the client +26/11：The VK video version shown in the video is outdated. Users are advised to update the version and try again. If the issue persists after updating, users are advised to reproduce the issue and capture the DMC logs.",Low,temporary close,生态/ecologically,Vladimir|米尔,15/12/2025,CHERY TIGGO 9 (T28)）,LVTDD24B4RG119623,,TGR0005161,VK_LVTDD24B4RG119623.MOV,Vladimir|米尔,,,,,,19 +TR1014,Mail,26/11/2025,,Remote control ,Remote control is unavailable due to Tbox is in deep sleep.,"1205：已有远控操作记录，建议关闭该问题 +1204：仍在等待反馈。 +1202：已发送提醒。等待反馈。 +1127：通过TSP重启模拟车辆后，Tbox在5小时后开始记录日志。因此，已要求用户确认该问题是否仍然存在。 +1126:同TR1009,目前有TBOX'登陆记录，但仍需验证方法是否有效","08/12: the user's feedback - remote control started working => issue closed. +05/12：Recent remote control operation records for this vehicle have been retrieved. It is recommended to close this issue. +04/12: still wait for a feedback. +02/12: a reminder sent. Wait for feedback. +27/11: after restarting sim car via TSP, Tbox started loging in 5 hours later. Therfore, the user was asked to confirm whether the issue is still vaild. +26/11:Same as TR1009, currently has TBOX login records, but the method still needs to be verified for effectiveness.",Low,close,TBOX,Vsevolod Tsoi,08/12/2025,Tenet T7 (T1E),EDEFB32B8SE016867,,Landina Vlada ,,Vsevolod Tsoi,,,,,,12 +TR1015,Telegram bot,26/11/2025,,Remote control ,"Location not updating for a vehicle since September. Screenshot attached. Team, please prioritize - this is a long-standing issue. Likely causes: GPS module, network, or server-side data processing. +自九月以来，某车辆位置信息未更新。截图已附。团队请优先处理——此为长期存在的问题。可能原因：GPS模块故障、网络问题或服务器端数据处理异常。","1211：等待反馈 +1209：等待反馈 +1204：等待反馈 +1202：等待客户反馈 +1127：查询TSP用户服务集未打开，见附件图片，已手动打开，请确认用户重新刷新后确认。同时抓取TBOX日志分析 +1126：已建专题群沟通","11/12: Waiting for feedback-------temp close +09/12: Waiting for feedback +04/12: Waiting for feedback +02/12: waiting for customers feedback +27/11: Query indicates TSP user service set is not enabled. See attached image. Manually enabled; please confirm after user refreshes. Simultaneously capture TBOX logs for analysis. +26/11：Specialized communication groups have been established.",Low,temporary close,TBOX,Vladimir|米尔,11/12/2025,EXEED RX（T22）,XEYDD24B3RA008543,,TGR0005202,"image.png,file_6253 (1).jpg",Vladimir|米尔,,,,,,15 +TR1017,Mail,26/11/2025,,Remote control ,AC command can't be executed only. All other commands work well - see document attached. Tbox log is in attachment.,"1127：远控失败，提示控制器反馈状态失败，已有TBOX日志，TBOX侧反馈为空调件未反馈执行结果/未执行,转售后硬件","11/12: TR closed since there was no any feedback from the user. +09/12: wait for Thursday's meeting. If no feedback TR will temporary be closed. +04/12: no feedback so far. +02/12: Executing of AC command was restored. The user was asked to provide a feedback whether AC command was restored. +27/11:Remote control failed. Controller feedback status failure detected. TBOX log available. TBOX side feedback indicates air conditioning component did not report execution result/did not execute. Escalate to after-sales hardware team.",Low,temporary close,TBOX,张志臣,11/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ4SD097247,,,"LOG_LNNBDDEZ4SD09724720251126165559.tar,Execution_commands_list.JPG,AC_command_issue.pdf",Vsevolod Tsoi,,,,,,15 +TR1018,Telegram bot,27/11/2025,,Remote control ,AC control command can not be executed only - see photos attached. An error message "Please try again later" comes up. Other commands work well.,"1216：等待反馈，建议转入等待数据 +1211：等待反馈 +1209：等待反馈 +1204：等待反馈 +1202：等待客户反馈 +1128:远控日志提示控制器反馈状态失败，转售后硬件排查","16/12: Waiting for feedback---temp close +16/12: Waiting for feedback +11/12: Waiting for feedback +09/12: Waiting for feedback +04/12: Waiting for feedback +02/12: waiting for customers feedback +28/11: Remote control log indicates controller feedback status failure. Escalate to after-sales for hardware troubleshooting.",Low,temporary close,After sales,Vladimir|米尔,18/12/2025,CHERY TIGGO 9 (T28)）,EDEDD24B9SG018639,,TGR0005079,"20251127-140455.jpg,file_6321.jpg",Vladimir|米尔,,,,,,21 +TR1020,Telegram bot,28/11/2025,,Remote control ,"After remote starting the vehicle (via the app or key fob), if you approach the car from the rear and open the trunk, the engine stalls and the alarm is triggered. In Simba, it shows that we sent an SMS about an anomaly.远程启动车辆（通过应用程序或钥匙遥控器）后，若从车尾靠近车辆并打开后备箱，发动机将熄火且触发警报。在Simba系统中，会显示我们已发送异常情况的短信通知。","1216: 已告知用户，等待后续OTA,建议可转入暂时关闭或等待数据 +1211：已决定通过OTA升级该策略，BDM侧已提交需求，等待OTA部门排期 +1202：核实5月后BDM已修改策略，该车可能BDM版本较低，正在商讨解决方案 +1201:核实逻辑为域控逻辑，转域控专业","16/12: The customer has been notified-----Awaiting subsequent OTA updates. It is recommended to switch to temporary shutdown mode or wait for data. +11/12：It has been decided to implement this policy via OTA upgrade. The BDM side has submitted the request and is awaiting scheduling by the OTA department. +02/12：After verifying that BDM modified the logic in May, this vehicle may be running an older BDM version. A solution is currently being discussed. +01/12: Verification logic follows domain controller logic, transitioning to domain controller expertise.",Low,temporary close,OTA,康君博,18/12/2025,CHERY TIGGO 9 (T28)）,LVTDD24B2RG114985,,TGR0005236,,Vladimir|米尔,,,,,,20 +TR1021,Telegram bot,28/11/2025,,Traffic is over,Abnormal traffic consumption. LOG Attached ,"暂无进展，该类异常消耗详细见TR1039分析进展 +1203：建议询问用户是否使用carplay，手机是否连接了车机热点---需要等待用户复现后，抓取对应的IHU日志 +1202：日志仍在分析中，已建立专题群沟通 +1128：已有日志及流量消耗明细，转DMC侧分析","02/12: The log analysis is still in progress, and a dedicated communication group has been established. +28/11: Logs and traffic consumption details are available. Forward to DMC for analysis.",Low,Processing,DMC,林希玲,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ3SD389942,, mishenkov.nikita13@gmail.com,"img_v3_02sk_bb6d9690-f956-4ae0-baaa-99dcabcb074g.jpg,89701011059098065741_Traffic_cunsumption_Nov_25th.xlsx,2025_11_28_17_20_29.zip",Vladimir|米尔,,,,,, +TR1023,Telegram bot,01/12/2025,,VK ,VK Vidoe doesn't work. Navi is ok,"1202:等待客户反馈 +1201：已对后台异常数据检查，可以建议用户尝试","02/12: Fixed +02/12: Waiting for customer response +01/12: Backend abnormal data has been checked. Users may be advised to try again.",Low,close,生态/ecologically,Vladimir|米尔,02/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ4SD477060,,TGR0005122,file_6379.jpg,Vladimir|米尔,,,,,,1 +TR1024,Mail,01/12/2025,,Remote control ,"Remote control issue: from time to time neither engine start nor AC control commands can be executed +遥控器故障：偶尔无法执行发动机启动或空调控制指令","1218：等待客户反馈 +1211：等待客户反馈 +1209: 已向O&J团队提供反馈。请等待反馈。 +1201：见有成功远控记录，也有失败远控记录，失败原因为控制器反馈状态失败，建议客户可以在网络稳定的环境尝试远控，排除网络因素，如还是无法成功，建议查看失败原因后，反馈售后团队分析","23/12: no feedback => closed. +18/12: still wait for a feedback. +11/12: still wait for a feedback. +09/12: a feedback was provided to the O&J team. Wait for a feedback. +01/12: We observe both successful and failed remote control records. The failure is attributed to controller feedback status issues. We recommend the customer attempt remote control in a stable network environment to rule out network factors. If the issue persists, we advise reviewing the failure cause and reporting it to the after-sales team for analysis.",Low,close,local O&M,Vsevolod Tsoi,23/12/2025,JAECOO J7（T1EJ）,LVVDD21B7RC083574,,,"Commands_executing_results.JPG,Remote_start_issue.JPG",Vsevolod Tsoi,,,,,,22 +TR1025,Mail,01/12/2025,,VK ,VK Video doesn't work. Photos attached. Rebooting didn't help,"1223：等待经销商反馈日志----建议转等待数据 +1216：等待经销商反馈日志 +1209：等待经销商反馈 +1204：致函Sergey.Belov@tenet.ru（ASD）获取DMC日志 +1202:未见主机登录记录，建议用户检查DMC网络信号是否正常，如果连接手机网络尝试刷新后无法恢复，建议用户进站获取DMC日志回传分析","23/12: Waiting for feedback-----waiting for data +18/12: Waiting for feedback +16/12: Waiting for feedback +09/12: Waiting for feedback +04/12: Wrote to Sergey.Belov@tenet.ru （ASD）to get the DMC log +02/12: No DMC login records found. Users are advised to verify the DMC network signal status. If the issue persists after refreshing via mobile network, users should visit the station to retrieve DMC logs for analysis.",Low,Waiting for data,生态/ecologically,Vladimir|米尔,,CHERY TIGGO 9 (T28)）,LVTDD24B0RG089715,,obaid mansur ,"image-25-11-25-09-24-2.jpeg,image-25-11-25-09-24.jpeg",Vladimir|米尔,,,,,, +TR1026,Mail,01/12/2025,,OTA,OTA package can't be downloaded. It failed every time when achieving 1% of progress - see photo attached.,"1223：等待ICC日志 +1218：等待主机日志 +1204:OTA反馈：OTA日志提示有权限问题，需要主机日志分析 +1202:转OTA分析","23/12: still wait for ICC logs. +18/12: wait for logs. +11/12: a request for an ICC log has been sent. +09/12: the user's contact data was received. DMC log will be requested within today. +04/12：OTA Feedback: OTA logs indicate permission issues; DMC logs require analysis. +02/12:OTA Analysis ",Low,Processing,OTA,Vsevolod Tsoi,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ7SD345846,,,OTA_download_failed.JPG,Vsevolod Tsoi,,,,,, +TR1027,Telegram bot,01/12/2025,,Remote control ,"Engine start command - A00606 Error, No bad command in the commands log","1202：app问题，已在1.8.1修复，建议用户更新即可 +1202:已有TBOX日志，转分析流程，但未诊断出原因.","04/12：Solved, confirmed from user +02/12：The app issue has been fixed in version 1.8.1. Users are advised to update. +01/12: TBOX log attached.The analysis process was transferred, but the cause was not diagnosed.",Low,close,TENET app,杜星雨,04/12/2025,Tenet T7 (T1E),EDEFB32B9SE016764,,TGR0005354,"LOG_EDEFB32B9SE01676420251201172354.tar,image.png,image.png",Kostya,,,,,,3 +TR1031,Telegram bot,02/12/2025,,Remote control ,"Engine start command ---- A00606 Error------Illegal duration when activated , No command in the commands log at SPB time 9:26 28.11 (Time of executing)","1202：同TR1027，app问题，已在1.8.1修复，建议用户更新即可 +1202：排查中，暂无进展","04/12：Solved, confirmed from user +02/12：same as TR 1027.The app issue has been fixed in version 1.8.1. Users are advised to update. +01/12: TBOX log attached",Low,close,TENET app,杜星雨,04/12/2025,Tenet T7 (T1E),EDEFB32B9SE003948,,TGR0005276,"LOG_EDEFB32B9SE00394820251202095858.tar,image.png,image.png",Kostya,,,,,,2 +TR1032,Telegram bot,02/12/2025,,VK ,VK Video doesn't work - Wrong licences. Same is TR1005,"1204:已修改，可建议用户重新尝试，并反馈 +1203:已在PKI检查，实车上报IHUSN为P300+SN（长编码），TSP中录入为短编码，已在TSP修改","05/12: Fixed +04/12:The issue has been resolved. may suggest that users try again and provide feedback. +03/12:The PKI check has been completed. The actual vehicle reported IHUSN as P300+SN (long code), while the TSP system recorded it as a short code. The TSP system has been updated accordingly.",Low,close,TSP,Vladimir|米尔,05/12/2025,EXEED RX（T22）,LVTDD24B3RG021277,,TGR0005295,file_6393.jpg,Vladimir|米尔,,,,,,3 +TR1033,Mail,02/12/2025,,HU troubles,"No connection between DMC and TBOX: +Local VX FL, we requested data from Engineer menu for importing to the TSP, but there is no any data. +Dealer checked physical connection between TBOX and DMC - Looks like normal, as usual. Cheked TBOX by Engineer Tool (Launch) - no errors. DMC logs attached","1211：会后与DMC侧确认是否有指导说明 +1210：日志分析为日志分析socket 无法识别端口号， +建议排查。1.主机与tbox连接接口有问题 +2.主机和tbox连接线 +3.tbox接口问题 +1209：等待跨境数据发起----- 已处理 +1203：有主机日志，PKI查询CDC上报的SN报错，建议分析主机日志","23/12 need to check the error on TBOX and DMC by OBD +18/12: Proccesing in chat +11/12: +1. Check if the host TBOX interface is present. - What do you mean? We don't have TBOX info in EM in the DMC +2. Inspect the connection cable between the host and TBOX. - any special procedure for that, like check input-output +3. Verify the TBOX interface. - What do you mean? Dealer alredy checked the connection between CAN and TBOX - no errors +10/12：Log analysis: The log analysis socket cannot recognize the port number. +Recommended troubleshooting steps: +1. Host-to-TBox connection interface issue +2. Host-to-TBox connection cable +3. TBox interface problem +09/12:Waiting for cross-border data initiation +03/12：DMC logs are available. PKI queries report SN errors in CDC submissions. It is recommended to analyze the host logs.",Low,Processing,DMC,张少龙,,EXEED VX FL（M36T）,XEYDD14B1RA001770,,Светиков Максим Викторович ,Documents.zip,Kostya,,,,,, +TR1034,Mail,02/12/2025,,OTA,OTA upgrade can't be installed. It fail when achieving 16% of progress,"1218：等待用户反馈 +1211：已向用户发送建议，提醒其在进行OTA升级时切勿进入工程菜单。 +1209: 进入OTA工程菜单是否是故障的原因？ +1203：OTA日志显示 11/13号 这天用户进了工程模式操作升级， 研发团队建议：引导用户正常主界面进行升级","23/12: checked out int FOTA backcend - still not upgraded. +18/12: wait for feedback. +11/12: a recommendations were sent to ther user to not enter in the engineering menu when upgrading OTA. +09/12: Was the entering in the OTA engineering menu a reason of a failure ?------Yes +03/12：OTA logs indicate that on November 13th, users entered engineering mode to perform the upgrade. The R&D team recommends guiding users to perform the upgrade through the normal main interface.",Low,Processing,OTA,Vsevolod Tsoi,,CHERY TIGGO 9 (T28)）,LVTDD24B3RG090762,,,LOG_OTA.zip,Vsevolod Tsoi,,,,,, +TR1035,Mail,03/12/2025,,doesn't exist on TSP,"The vehicle is in ""test"" status in the TSP. It cannot be found by VIN, and IoV services cannot be activated. It can only be found in the TSP using the ICCID.","1216：已修复，可关闭 +1210：该问题中5辆车均已有数据，可让用户重新尝试 +1204：物料号未与外部车型维护，需要BOM侧维护数据","16/12: Fixed +11/12: Waiting for feedback +10/12：Data is available for all 5 vehicles in this issue. Users may retry. +04/12: Material number not maintained with external vehicle model; requires data maintenance on the BOM side.",Low,close,MES,Vladimir|米尔,18/12/2025,TENET T8 (T18),"EDEGD34B7SE027421 +EDEGD34B0SE027826 +EDEGD34B8SE024186 +EDEGD34B9SE032264 +EDEGD34B2SE023857",,TGR0005434,"image.png,Screenshot 2025-12-03 152532.png",Vladimir|米尔,,,,,,15 +TR1036,Mail,03/12/2025,,Application,The PKI length differs between the TSP and PKI Admin systems.,"1223:已与经销商联系，等待反馈 +1216：等待经销商反馈 +1211: 该请求已发送至经销商 +1204：目前PKI上显示的IHUSN为短的，TSP上记录的为完整编码，需要商讨解决方案(需要核实版本)","23/12: Wrote to the client. Waiting for feedback +18/12: Waiting for feedback +16/12: Waiting for feedback +11/12: The request has been sent to the dealer-----check the DMC version +04/12: Discussed in the meeting that we send it to ASD for update @赵杰------get +04/12: The IHUSN currently displayed on the PKI is truncated, while the TSP records the full code. A solution needs to be discussed.",Low,Processing,DMC,Vladimir|米尔,,JAECOO J7（T1EJ）,EDXDD21B0SC056392,,Кирилл Аладьев ,,Vladimir|米尔,,,,,, +TR1037,Mail,04/12/2025,,Remote control ,Remote control can't be used. TSP platform reports that Tbxo SN doesn't match to the one installed in the car.,"1218：等待反馈实车TBOX、DMC SN +1211：用户反馈：Tbox硬件未发生变更。唯一更换的控制器为交流控制器。今日内将发送采集Tbox数据的请求。 +1209：由于此请求来自O&J应用支持团队，已向该团队发送了提供反馈的提醒。 +1204:实车上上报的TBOXSN与平台不一致，需要实车反馈ICCID，并核实是否是MES上传了错误的信息","18/12: following TBOX data collected from a car it was figured out that TBOX HW was changed. So, TSP has now been configured with a new one. +18/12: a request for collecting TBOX&DMC data was sent. Wait for feedback. +11/12: the user's feedback: there was no changing Tbox HW. The only controller that was chanched is AC one. A request for collecting Tbox data will be sent within today. +09/12: since this request was received from O&J app support team, a reminder to provide a feedback was sent to the O&J app support team. +04/12: 2nd line support team feedback: Tbox SN FCOT1EEF113M462# is different from one in the car FCOT1EEE612M070#. The user was asked to provide a feedback whether Tbox HW was changed.",Low,close,MES,Vsevolod Tsoi,23/12/2025,JAECOO J7（T1EJ）,LVVDD21B5RC147935,,,,Vsevolod Tsoi,,,,,,19 +TR1039,,04/12/2025,,Traffic is over,Reproduce of an abnormal traffic consumption on E0Y test car,"1211：目前DMC已要求供应商联系apple确认无线Carplay连接逻辑，解决方案待DMC侧提供 +1210：属地验证后反馈结果已同步至群聊，已进行有线无线Carplay连接，但未复现出问题 +1207：DMC-DRE建议链接Carplay后，忽略网络，等待属地验证 +1205：已建群讨论 +1204:ICC日志及Tbox数据已上传。可能需要通过电话说明最终发现的情况。","11/12: DMC has requested suppliers to contact Apple to confirm wireless CarPlay connection logic. Solution pending from DMC side. +10/12: Local verification results have been shared in group chat. Wired and wireless CarPlay connections tested, but issue not reproduced. +07/12: DMC-DRE recommends connecting CarPlay and ignoring network status while awaiting local verification. +05/12: Discussion group established. +04/12: ICC log as well as Tbox were uploaeded. Probably a phone call would be requred to explain what was finally discovered.",Low,Processing,DMC,林希玲,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ5SD097290,,,"2025_12_04_14_50_29.7z,20251204150249_tboxlog.tar,Книга1.xlsx",Kostya,,,,,, +TR1040,Telegram bot,05/12/2025,,VK ,"VK Video is not working. The customer can log into the app, but a black screen appears when trying to play videos. I have attached a video recording of the issue.","1223:等待反馈 +1218：属地反馈上电失败，可在属地闭环（需要对DMC执行SK），等待后续进展 +1211: 该车辆已添加至OTA。已要求客户下载并安装。----等待用户反馈 +1209：反馈视频版本较老，建议用户OTA至最新版 +1209：VK视频点击视频后，内容无法观看，显示一直加载中，等待专业分析","23/12: Waiting for feedback +18/12: power on failure - will go to the dealer ------will be solved on local side +09/12: Waiting for feedback +11/12: The vehicle has been added to the OTA. The customer has been asked to download and install it +09/12：The feedback video is an older version. We recommend users update to the latest version via OTA. +09/12：After clicking a VK video, the content cannot be viewed and displays a continuous loading screen. Awaiting professional analysis.",Low,Processing,生态/ecologically,Vladimir|米尔,,EXEED RX（T22）,XEYDD14B3RA011483,,TGR0005367,file_6491.mp4,Vladimir|米尔,,,,,, +TR1041,Telegram bot,05/12/2025,,doesn't exist on TSP,Can't find the car in the TSP,"1216：已修复，可关闭 +1210：该问题中VIN已有数据，可让用户重新尝试 +1208：物料号未与外部车型维护，需要BOM侧维护数据","16/12: Fixed +11/12: Waiting for feedback +10/12: The VIN data is already present in this issue; users may retry. +08/12: Material number not maintained with external vehicle model; requires data maintenance on the BOM side.",Low,close,MES,Vladimir|米尔,18/12/2025,TENET T8 (T18),EDEGD34B6SE031749,,TGR0005369,,Vladimir|米尔,,,,,,13 +TR1042,Telegram bot,05/12/2025,,HU,"When launching the navigation app, various search categories appear during the initial load, but later only ""EV charging"" and ""gas stations"" remain. The customer is asking for an explanation as to why the other categories disappear. Video attached","1223：等待日志 +1218：等待日志 +1216：无法获取日志 +1211：需要主机日志排查 +1208：已附版本图片 +1208：需要查看当前导航软件的版本，可在导航应用里核实","23/12: waiting for DMC logs +18/12：waiting for DMC logs +16/12: unavailable to get the log remote +11/12: DMC log analysis is required.（The Navi version is intended solely for auxiliary positioning logs.） +08/12: v1.0.0.0 photo was attached +08/12: To check the current version of your navigation software, verify it within the navigation application.",Low,Processing,生态/ecologically,Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ7SD360282,,TGR0005376,"20251208-091139.jpg,20251205-170015.jpg,20251205-165809.mp4",Vladimir|米尔,,,,,, +TR1044,Telegram bot,08/12/2025,,Application,The vehicle's location has not been updating since December 2nd.,"1218：等待用户进站取TBOX日志 +1216：等待日志 +1208：需要提供TBOX日志 +1208：需要用户核实车机端导航定位是否正常，如果车端GPS正常，建议抓取TBOX日志分析","23/12: Waiting for feedback +18/12: Waiting for feedback +16/12: Waiting for feedback +11/12: An invitation request for the customer to visit the dealership has been sent +09/12：TBox logs is required. +08/12: The location is also not detected in the application on the car's head unit @赵杰 +08/12：Users should verify whether the in-vehicle navigation positioning is functioning properly. If the vehicle's GPS is working normally, it is recommended to capture the TBOX logs for analysis.",Low,Processing,TBOX,Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ4SD162369,,TGR0005388,"file_6676.jpg,file_6517.jpg",Vladimir|米尔,,,,,, +TR1045,Mail,08/12/2025,,OTA,OTA upgrade failed when achieved 99% of install progress.,"1223:暂无反馈 +1208：收到反馈称车辆在进行OTA升级时未从充电站充电。等待用户反馈。 +1208:OTA侧反馈插枪的时候 不要升级","23/12: no feedback so far. +18/12: feedback is pending, +11/12: a sms was sent by the call center to the user. Wait for feedback. +08/12: a feedback of not having the car been charging from charging station while upgrading OTA was sent. Wait for the user's feedback.",Low,Processing,OTA,Vsevolod Tsoi,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ0SD345736,,Lebold Alexey ,,Vsevolod Tsoi,,,,,, +TR1046,Telegram bot,08/12/2025,,Application,"When the customer tries to grant long-term access to the vehicle, the date automatically resets to 1970, and the access is not granted. UPD: this issue is valid for EXEED app as well from 2038 year +当客户尝试授予车辆长期访问权限时，日期会自动重置为1970年，导致访问权限无法授予。更新：此问题同样适用于EXEED应用程序，且自2038年起生效。","1211：已确认，下个版本会修复该问题，测试app目前已修复 +1209：需要TSP/APP DRE确认","17/12: TR has been switched to Prcessing and will be in this status until new app version will be released. +11/12: waiting for new version +11/12：Confirmed. The issue will be fixed in the next version. The test app has already been fixed. +09/12：Requires confirmation from TSP/APP DRE",Low,Processing,车控APP(Car control),刘永斌,11/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ6SD483037,,TGR0005422,file_6554.jpg,Vladimir|米尔,,,,,,3 +TR1047,Mail,08/12/2025,,doesn't exist on TSP,Vehcle is missing in the TSP. MES issue?,"1210：该问题中VIN已有数据，可让用户重新尝试 +1208：物料号未与外部车型维护，需要BOM侧维护数据","11/12: fixed +11/12: wait for the user's feedback being able to closed it. +10/12: The VIN data is already present in this issue; users may retry. +08/12: Material number not maintained with external vehicle model; requires data maintenance on the BOM side.",Low,close,MES,Vladimir|米尔,11/12/2025,TENET T8 (T18),EDEGD34BXSE027820,,Lebold Alexey ,,Vsevolod Tsoi,,,,,,3 +TR1048,Telegram bot,08/12/2025,,Remote control ,"The customer's remote engine start is not working. The history shows consistent issues with engine start. On 07.12.2025 at 11:54 (Moscow time), the customer attempted to start the engine (screenshot attached), but it did not start. However, there is no corresponding log entry for this time in the TSP. +客户的远程发动机启动功能失效。历史记录显示发动机启动存在持续性故障。2025年12月7日11:54（莫斯科时间），客户尝试启动发动机（附截图），但未能成功。然而，TSP系统中该时间点未记录对应日志条目。","1218：等待用户反馈，如仍不可使用，抓取TBOX日志 +1215：已检查远控记录，与TBOX登录记录，发现远控下发为13:23，但是TBOX登录未13：29.怀疑当时网络信号较差，导致无法唤醒，尝试远程抓取日志失败，建议用户换个地方重新尝试远控，如仍无法恢复，建议抓取TBOX日志 +1209：见三次远控故障，12报错（2次）95报错（1次），建议用户规范远控 +12 车内有钥匙，无法进行远控操作 +95 车辆已上电且不在远程启动状态","23/12: 19.12.2025 again, the car does not respond to commands +18/12: Waiting for feedback +16/12: Waiting for feedback +15/12：Remote control logs and TBOX login records have been reviewed. The remote control command was issued at 13:23, but the TBOX login occurred at 13:29. We suspect poor network signal at the time prevented wake-up. Attempts to remotely capture logs failed. We recommend the user relocate and retry remote control. If recovery remains unsuccessful, we advise capturing the TBOX logs. +10/12: The customer attempted to start the engine again, and it failed to start. I have attached a screenshot from the TSP. The history shows that remote engine start attempts consistently result in an error. @赵杰-----check shows time out. +09/12：Three remote control failures detected: Error 12 (2 occurrences), Error 95 (1 occurrence). Recommend user standardizes remote control procedures. +12 Key present inside vehicle; remote control operation unavailable. +95 Vehicle powered on and not in remote start state.",Low,Processing,TBOX,Vladimir|米尔,,TENET T8 (T18),EDEDD24B7SD171182,,Tatiana Bekker ,"image.png,image.png,image.png,1000040951.jpg",Vladimir|米尔,,,,,, +TR1053,Mail,09/12/2025,,doesn't exist on TSP,Remote control is not available since the vehicle doesn't exist in the TSP,1210：该问题中VIN已有数据，可让用户重新尝试,"18/12: it's well seen in the TSP that the user uses well the remote cotrol. The last commands from Dec, 12, 13 and 15 were successfully executed. TR closed. +11/12: vehicle has finally been imported into TSP in order to be able to start activating the remote cotrol. The feedback was provided to Tenet app support team => wait for a feedback. +10/12: The VIN data is already present in this issue; users may retry. +09/12: Importing issue for AGK MES? If so, as a counter measure, when manual import can be applied ?",Low,close,MES,Vladimir|米尔,18/12/2025,TENET T8 (T18),EDEGD34B4SE030194,,,,Vsevolod Tsoi,,,,,,9 +TR1054,Telegram bot,09/12/2025,,doesn't exist on TSP,No Tenet in TSP,"1212：TSP反馈，已在12月10日用户成功绑车及远控 ，建议关闭该问题 +1211：等待用户反馈 +1210：该问题中VIN已有数据，可让用户重新尝试","18/12: Closed +12/12：TSP R&D feedback: The issue has been resolved as the user successfully bound the vehicle and performed remote control on December 10. We recommend closing this case.c +11/12: Waiting for feedback-------after meeting check with TSP R&D +10/12: The VIN data is already present in this issue; users may retry.",Low,close,MES,Vladimir|米尔,18/12/2025,TENET T8 (T18),EDEGD34B7SE027449,,TGR0005780,img_v3_02ss_308fb2b8-819b-43be-bc0a-c94498c113hu.jpg,Kostya,,,,,,9 +TR1055,Telegram bot,09/12/2025,,doesn't exist on TSP,No Tenet in TSP,"1211：等待客户反馈 +1210：该问题中VIN已有数据，可让用户重新尝试","18/12: Tenet app feedback - issue fixed = TR closed. +11/12: Waiting for feedback +10/12: The VIN data is already present in this issue; users may retry.",Low,close,MES,Kostya,18/12/2025,Tenet T7 (T1E),EDEFB32B3SE037061,,TGR0005774,,Kostya,,,,,,9 +TR1056,Telegram bot,09/12/2025,,doesn't exist on TSP,No Tenet in TSP,1210：该问题中VIN已有数据，可让用户重新尝试,"18/12: Closed +11/12: Waiting for feedback +10/12: The VIN data is already present in this issue; users may retry.",Low,close,MES,Vladimir|米尔,18/12/2025,TENET T8 (T18),EDEGD34B7SE024776,,TGR0005704,,Kostya,,,,,,9 +TR1057,Telegram bot,09/12/2025,,Remote control ,"The remote engine start command frequently fails to execute. I have sent the log to the TR-numbered chat, as my Lark storage quota has been exhausted. +远程引擎启动指令频繁执行失败。我已将日志发送至TR编号的聊天群组，因我的Lark存储配额已用尽。","1211：等待客户反馈 +1210：TSP后台查询远控记录，12月10日又多次的成功远控发动机记录，此前失败的原因可能为网络环境较差","11/12: wrote to the client +10/12: TSP backend query remote control records show multiple successful engine remote control attempts on December 10. Previous failures were likely due to poor network conditions.",Low,Processing,TBOX,Vladimir|米尔,,Tenet T7 (T1E),EDEFB32B9SE003948,,TGR0005443,,Vladimir|米尔,,,,,, +TR1061,Mail,11/12/2025,,HU,DMC upgrade fails with USB flash drive.,"1218：日志显示升级分区无空间了，请用户进站，在DMC中进ota工程模式里，点删除下载包-清除数据，后使用G7PH_EXEED_T22_INT_HS_SOP8_FULL_14465_250525_R.zip此版本软件升级。并按操作说明执行。升级前保证U盘中只有升级包 +1212：DRE已发邮件，等待合规审批-----已发送，等待分析反馈","23/12: DMC SW was finally upgraded. TR closed. +18/12：The log indicates insufficient space in the upgrade partition. Users should enter the station, access OTA engineering mode in DMC, select ""Delete Download Package"" and ""Clear Data,"" then use the software version G7PH_EXEED_T22_INT_HS_SOP8_FULL_14465_250525_R.zip for the upgrade. Follow the operating instructions precisely. Before upgrading, ensure the USB drive contains only the upgrade package. +11/12: latest DMC logs are attached after reproducing an error when upgrading with USB => VR failed. See photo attached.",Low,close,DMC,Vsevolod Tsoi,23/12/2025,EXEED RX（T22）,XEYDD14B3RA002731,,,"1233AA DMC Software update manual.pptx,logs_20251211-150935-20251211T122309Z-3-001.zip,VR_failed.JPG,logs_20251211-112641-20251211T101645Z-3-001.zip",Vsevolod Tsoi,,,,,,12 +TR1062,Telegram bot,11/12/2025,,Remote control ,"1. The customer started the engine remotely. +2. They navigated to the AC tab and activated the ""One Button Heating"" function. Immediately after, the engine shut off, but the button in the app did not change its status (did not turn on/off visually). +The customer asks to explain the system logic: +Why does the engine turn off? +Why doesn't the button status change, and why is nothing activated in the application? +A video is attached (the vehicle's behavior in the background is visible when commands are sent).","1212：远控发动机报错：请在发动机远程启动情况下操作，建议用户合理远控。 +远程启动发动机仅可支持开启10分钟，T7暂不支持一键加热远控功能","23/12: Waiting for feedback +18/12: Wrote to the client +12/12：Remote engine control error: Please operate while the engine is in remote start mode. Users are advised to use remote control appropriately. +Remote engine start is only supported for 10 minutes. The T7 currently does not support one-touch remote heating functionality.",Low,Processing,TENET app,Vladimir|米尔,,Tenet T7 (T1E),EDEFB32B3SE009423,,TGR0005326,"image.png,file_6696 (1).MOV",Vladimir|米尔,,,,,, +TR1072,Telegram bot,12/12/2025,,Remote control ,"Since 1.12.2025 - Dead TBOX: No data. no connection in MTS. Can't download TBOX logs and catch it manually (Still preparing all unstructions, hardware and procedures)",1215：建议用户进站尝试断开蓄电池，重启一下整车（让TBOX重新驻网拨号）,"22/12: Waiting for customer responce +18/12: In communication with customer +15/12：We recommend that users disconnect the battery upon entering the station and restart the entire vehicle (to allow the TBOX to reconnect to the network and dial in).",Low,Processing,TBOX,Kostya,,Tenet T7 (T1E),EDEFB32B1SE023787,,TGR0005756 - FROM TENET,,Kostya,,,,,, +TR1073,Telegram bot,15/12/2025,,Remote control ,"Remote control is not working, and the vehicle status is not updating.","1216：等待用户反馈 +1215：见最后一次TBOX登录记录在12月13日，可能是车辆14号未使用，建议用户尝试重启车辆刷新下app数据","23/12: Waiting for feedback +16/12: Waiting for feedback +15/12: The last TBOX login record was on December 13th, indicating the vehicle may not have been used on the 14th. We recommend the user attempt to restart the vehicle to refresh the app data.",Low,Processing,MNO,Vladimir|米尔,,JAECOO J7（T1EJ）,LVVDB21B9RC069276,,TGR0005924,image.png,Vladimir|米尔,,,,,, +TR1075,Telegram bot,16/12/2025,,Traffic is over,Abnormal traffic consumption,1217：建议与用户询问是否使用了carplay。如果使用了，建议在使用过程中，忽略iphone上的车机热点连接，或者换用有线carplay连接。,"18/12: Wrote to the client +17/12: We recommend asking users if they are using CarPlay. If they are, we suggest ignoring the iPhone's hotspot connection during use or switching to a wired CarPlay connection.",Low,Processing,DMC,Vladimir|米尔,16/12/2025,EXLANTIX ET (E0Y-REEV),LNNBDDEZ4SD359221,,TGR0006048,,Vladimir|米尔,,,,,,0 +TR1076,Mail,16/12/2025,,Application,"Vehicle position is not found when executing a vehicle hunting command +执行车辆搜索指令时未找到车辆位置",1216：要求用户执行车辆搜索指令，随后提供指令执行日期与时间。,"23/12: the user's feedback: vehicle hunting command was restored - issue sorted out. +18/12: feedback pending. +16/12: the user was asked to execute a vehicle hunting command and then provide an command date&time",Low,close,车控APP(Car control),Vsevolod Tsoi,23/12/2025,Tenet T7 (T1E),EDEFD32B0SE035309,,,,Vsevolod Tsoi,,,,,,7 +TR1077,Telegram bot,17/12/2025,,Remote control ,"GPS failure only.T-BOX is online, other data updates, permissions OK.","1218：日志显示GPS信号较差，13号有成功的位置信息上报记录，建议用户在信号好的地方重新试一试. +1218:TSP已检查位置服务集已打开，已有TBOX日志，转国内分析","23/12: Waiting for feedback +18/12：The log indicates poor GPS signal reception. Successful location updates were recorded on the 13th. We recommend the user retry in an area with better signal coverage. +18/12：TSP has verified that the location service set is enabled. TBOX logs are available. Proceed with domestic analysis.",Low,Processing,TBOX,Vladimir|米尔,,EXEED RX（T22）,XEYDD14B3RA004650,,TGR0006068,image.png,Vladimir|米尔,,,,,, +TR1079,Telegram bot,18/12/2025,,Remote control ,"The vehicle does not exit remote control model when the brake pedal is pressed +踩下制动踏板时，车辆不会退出遥控模式","1223:已提供相关验证方法，需要属地验证是否是在车内远控发动机，且未打开车门（域控预设策略是，人在车外，使用远控发动机，带钥匙打开车门后，弹窗提示踩刹车可切换模式） +1223:客户反馈，当使用任何启动发动机的功能（如远程启动或无钥匙启动）时，就会出现该问题。当他们踩下制动踏板时，主机（HU）屏幕不会亮起。结果均为负面（HU屏幕保持关闭）： +按下并立即释放。 +按下，保持2 - 3秒，然后松开。 +按下并释放，重复2 - 3次。 +按下，保持2 - 3秒，松开，重复2 - 3次。 +按下并保持约30秒，然后松开。---------踩下制动踏板后，图片中消息没出现 +1219:需要进一步核实用户操作及问题点","23/12: The customer reports that the issue occurs when using any function that starts the engine (e.g., remote start or keyless start). When they press the brake pedal, the Head Unit (HU) screen does not turn on. The following pressing patterns were attempted, all with the same negative result (HU screen remains off): +Pressed and immediately released. +Pressed, held for 2-3 seconds, then released. +Pressed and released, repeated 2-3 times. +Pressed, held for 2-3 seconds, released, repeated 2-3 times. +Pressed and held for approximately 30 seconds, then released. +19/12:Further verification of user actions and problem areas is required.",Low,Processing,BDM,Vladimir|米尔,,CHERY TIGGO 9 (T28)）,LVTDD24B7RG123634,,TGR0005914,image.png,Vladimir|米尔,,,,,, +TR1080,Telegram bot,18/12/2025,,Traffic is over,Abnormal traffic consumption,1219：暂无流量异常的具体时间点及用户操作，建议在下次异常出现时，抓取DMC日志，并反馈用户操作细节,19/12:No specific time points or user actions related to traffic anomalies have been identified at this time. We recommend capturing DMC logs during the next occurrence of anomalies and providing feedback on the details of user actions.,Low,Processing,DMC,Vladimir|米尔,,EXEED VX FL（M36T）,LVTDD24B0RD030407,,TGR0006259,image.png,Vladimir|米尔,,,,,, +TR1081,Telegram bot,19/12/2025,,VK ,"VK Video is not working. The customer can log into the app, but a black screen",1219：vk视频不工作，可登录，但登录后界面黑屏，建议可查看当前主机版本,"23/12: Waiting for feedback +22/12: wrote to the client +19/12：Confirm the current host version. If the user cooperates, DMC logs can be captured.c",Low,Processing,生态/ecologically,Vladimir|米尔,,EXEED RX（T22）,XEYDD24B3RA008446,,TGR0006186,file_6854.jpg,Vladimir|米尔,,,,,, +TR1083,Telegram bot,19/12/2025,,VK ,Cannot update the vk. Check the video: IMG_3363.mov — Яндекс Диск,"1223：建议用户OTA后，尝试重新下载安装 +1222：无法打开视频，请上传至附件，同时需要DMC日志分析失败记录。","23/12: Waiting for feedback +22/12: Unable to open the video. Please upload it as an attachment and provide the DMC log containing the failed analysis records.",Low,Processing,生态/ecologically,Vladimir|米尔,,EXEED VX FL（M36T）,XEYDD14B1RA006245,,TGR0006238,Issue_video.mov,Vladimir|米尔,,,,,, +TR1084,Telegram bot,19/12/2025,,VK ,Cannot update the vk,"1223：需要用户查看当前的VK视频版本，拍摄一下现有的VK里视频 +1222：无视频及日志，同时需要DMC日志分析失败记录。","23/12: Waiting for feedback +23/12：Users need to check the current version of the VK video and record the existing video within VK. +22/12: Unable to open the video. Please upload it as an attachment and provide the DMC log containing the failed analysis records.",Low,Processing,生态/ecologically,,,EXEED VX FL（M36T）,XEYDD14B1RA006310,,TGR0006157,file_6986.jpg,Vladimir|米尔,,,,,, +TR1085,Mail,19/12/2025,,VK ,VK update can't be installed.,1222：无法打开视频，请上传至附件，同时需要DMC日志分析失败记录。,"22/12: root cause was that DMC SW version was not the latest one. DMC OTA upgrade happened on December, 21th. Then VK SOTA has successfully been completed. +22/12: Unable to open the video. Please upload it as an attachment and provide the DMC log containing the failed analysis records.",Low,close,生态/ecologically,,22/12/2025,EXEED VX FL（M36T）,XEYDD14B1RA002813,,,VK_update_install_issue.mov,Vsevolod Tsoi,,,,,,3 +TR1086,Mail,19/12/2025,,Traffic is over,Abnormal traffic consumption,1222：建议与用户询问是否使用了carplay。如果使用了，建议在使用过程中，忽略iphone上的车机热点连接，或者换用有线carplay连接。,"22/12: We recommend asking users if they are using CarPlay. If they are, we suggest ignoring the iPhone's hotspot connection during use or switching to a wired CarPlay connection.",Low,Processing,DMC,Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ7SD391287,,TGR0006420,image.png,Vladimir|米尔,,,,,, +TR1087,Telegram bot,22/12/2025,,Activation SIM,Can't activate the SIM card. Restarting and resetting to factory settings didn't help. Log attached.,1222：车辆已激活，DMC无登录记录，TBOX登录正常，远控正常，转DMC分析,22/12：Vehicle activated. No DMC login records. TBOX login normal. Remote control normal. Switch to DMC analysis.,Low,Processing,DMC,,,EXLANTIX ES (E03),LNNAJDEZ4SD152526,,TGR0006242,"Exlantix.zip,file_6968.jpg,file_6969.jpg",Vladimir|米尔,,,,,, +TR1088,Telegram bot,22/12/2025,,Traffic is over,Abnormal traffic consumption. Used carplay,1222:建议用户进站抓取DMC日志,"23/12 +A request for reimbursement to do to simba",Low,Processing,DMC,Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZXSD443012,,TGR0006446,,Vladimir|米尔,,,,,, +TR1089,Telegram bot,22/12/2025,,Remote control ,The rear seat heating behind the driver does not start. The video was made on 17.12.2025 Moscow time. Log file,"1223：已转TBOX侧，等待发起合规流程 +1222:远控记录显示报错为 ""9"":尝试次数过多，请将车辆点火后再尝试启动 。近期远控记录提示超时，建议用户换个信号好的地方再重新尝试","23/12：Transferred to TBOX side, awaiting initiation of compliance process. +22/12: Please check the video at the same time. 3 heaters are turned on, but it doesn't work and no info about ""too many attempts"" +22/12:Remote control records indicate error code ""9"": Too many attempts. Please turn on the vehicle ignition and try starting again. Recent remote control records show timeout errors. We recommend users relocate to an area with better signal reception and retry.",Low,Processing,车控APP(Car control),Vladimir|米尔,,JAECOO J7（T1EJ）,LVVDB21B5RC072708,,TGR0006467,"file_6970.mp4,LOG_LVVDB21B5RC07270820251222120736.tar",Vladimir|米尔,,,,,, +TR1092,Telegram bot,22/12/2025,,Traffic is over,Abnormal traffic consumption,1223:建议用户进站抓取DMC日志,23/12:Recommend that users access the site to capture DMC logs.,Low,Processing,DMC,Vladimir|米尔,,EXLANTIX ET (E0Y-REEV),LNNBDDEZ0SD405059,,TGR0006495,,Vladimir|米尔,,,,,, +TR1093,Mail,22/12/2025,,Application,Map doesn't refeclect in the app - see pictures attached.,1223：手机app地图定位时不显示图资，请app侧排查。,22/11: request has been sent to the Tenet app support team to check it out from a developer team side. If you @赵杰 can provide any support it would also be great.,Low,Processing,TENET app,Denis Voronkov,,TENET T8 (T18),EDEDD24B2SD163376,,Tatiana Bekker ,"Picture_2.jpg,Picture_1.jpg",Vsevolod Tsoi,,,,,, +TR1094,Mail,23/12/2025,,Remote control ,"Remote control doesn't work - see photo attached. No data is reflected in the app. No Tbox log in records since activation date Nov, 25th.",1224：无apn1使用记录，APN2有消耗，IHUSN为空，建议用户进站检查TBOX是否未退出工厂模式，并读取IHU SN，抓取TBOX日志,"24/12：No usage records for APN1. APN2 shows consumption. IHUSN is empty. Recommend that the user visit the station to inspect the TBOX setting（Confirm whether factory mode has been exited.), read the IHU SN, and capture the TBOX log.",Low,Processing,TBOX,Vsevolod Tsoi,,CHERY TIGGO 9 (T28)）,EDEDD24B8SG015702,,,Remote_control_issue.JPG,Vsevolod Tsoi,,,,,, diff --git a/__init__.py b/__init__.py new file mode 100644 index 0000000..ff71db5 --- /dev/null +++ b/__init__.py @@ -0,0 +1,54 @@ +# -*- coding: utf-8 -*- +""" +Data Analysis Agent Package + +一个基于LLM的智能数据分析代理，专门为Jupyter Notebook环境设计。 +""" + +from .core.notebook_agent import NotebookAgent +from .config.llm_config import LLMConfig +from .utils.code_executor import CodeExecutor + +__version__ = "1.0.0" +__author__ = "Data Analysis Agent Team" + +# 主要导出类 +__all__ = [ + "NotebookAgent", + "LLMConfig", + "CodeExecutor", +] + +# 便捷函数 +def create_agent(config=None, output_dir="outputs", max_rounds=20, session_dir=None): + """ + 创建一个数据分析智能体实例 + + Args: + config: LLM配置，如果为None则使用默认配置 + output_dir: 输出目录 + max_rounds: 最大分析轮数 + session_dir: 指定会话目录（可选） + + Returns: + NotebookAgent: 智能体实例 + """ + if config is None: + config = LLMConfig() + return NotebookAgent(config=config, output_dir=output_dir, max_rounds=max_rounds, session_dir=session_dir) + +def quick_analysis(query, files=None, output_dir="outputs", max_rounds=10): + """ + 快速数据分析函数 + + Args: + query: 分析需求（自然语言） + files: 数据文件路径列表 + output_dir: 输出目录 + max_rounds: 最大分析轮数 + + Returns: + dict: 分析结果 + """ + agent = create_agent(output_dir=output_dir, max_rounds=max_rounds) + return agent.analyze(query, files) \ No newline at end of file diff --git a/config/__init__.py b/config/__init__.py new file mode 100644 index 0000000..4c973a4 --- /dev/null +++ b/config/__init__.py @@ -0,0 +1,8 @@ +# -*- coding: utf-8 -*- +""" +配置模块 +""" + +from .llm_config import LLMConfig + +__all__ = ['LLMConfig'] diff --git a/config/llm_config.py b/config/llm_config.py new file mode 100644 index 0000000..6da98e0 --- /dev/null +++ b/config/llm_config.py @@ -0,0 +1,44 @@ +# -*- coding: utf-8 -*- +""" +配置管理模块 +""" + +import os +from typing import Dict, Any +from dataclasses import dataclass, asdict + + +from dotenv import load_dotenv + +load_dotenv() + + +@dataclass +class LLMConfig: + """LLM配置""" + + provider: str = "openai" # openai, anthropic, etc. + api_key: str = os.environ.get("OPENAI_API_KEY", "") + base_url: str = os.environ.get("OPENAI_BASE_URL", "https://api.openai.com/v1") + model: str = os.environ.get("OPENAI_MODEL", "gpt-4o-mini") + temperature: float = 0.3 + max_tokens: int = 131072 + + def to_dict(self) -> Dict[str, Any]: + """转换为字典""" + return asdict(self) + + @classmethod + def from_dict(cls, data: Dict[str, Any]) -> "LLMConfig": + """从字典创建配置""" + return cls(**data) + + def validate(self) -> bool: + """验证配置有效性""" + if not self.api_key: + raise ValueError("OPENAI_API_KEY is required") + if not self.base_url: + raise ValueError("OPENAI_BASE_URL is required") + if not self.model: + raise ValueError("OPENAI_MODEL is required") + return True diff --git a/data_analysis_agent.py b/data_analysis_agent.py new file mode 100644 index 0000000..7456af5 --- /dev/null +++ b/data_analysis_agent.py @@ -0,0 +1,628 @@ +# -*- coding: utf-8 -*- +""" +简化的 Notebook 数据分析智能体 +仅包含用户和助手两个角 +2. 图片必须保存到指定的会话目录中，输出绝对路径，禁止使用plt.show() +3. 表格输出控制：超过15行只显示前5行和后5行 +4. 强制使用SimHei字体：plt.rcParams['font.sans-serif'] = ['SimHei'] +5. 输出格式严格使用YAML共享上下文的单轮对话模式 +""" + +import os +import json +import yaml +from typing import Dict, Any, List, Optional +from utils.create_session_dir import create_session_output_dir +from utils.format_execution_result import format_execution_result +from utils.extract_code import extract_code_from_response +from utils.data_loader import load_and_profile_data +from utils.llm_helper import LLMHelper, LLMCallError +from utils.execution_session_client import ( + ExecutionSessionClient, + WorkerSessionError, + WorkerTimeoutError, +) +from config.llm_config import LLMConfig +from prompts import data_analysis_system_prompt, final_report_system_prompt + + +class DataAnalysisAgent: + """ + 数据分析智能体 + + 职责： + - 接收用户自然语言需求 + - 生成Python分析代码 + - 执行代码并收集结果 + - 基于执行结果继续生成后续分析代码 + """ + + def __init__( + self, + llm_config: LLMConfig = None, + output_dir: str = "outputs", + max_rounds: int = 20, + force_max_rounds: bool = False, + ): + """ + 初始化智能体 + + Args: + config: LLM配置 + output_dir: 输出目录 + max_rounds: 最大对话轮数 + force_max_rounds: 是否强制运行到最大轮数（忽略AI的完成信号） + """ + self.config = llm_config or LLMConfig() + self.llm = LLMHelper(self.config) + self.base_output_dir = output_dir + self.max_rounds = max_rounds + self.force_max_rounds = force_max_rounds + # 对话历史和上下文 + self.conversation_history = [] + self.analysis_results = [] + self.current_round = 0 + self.session_output_dir = None + self.executor = None + self.data_profile = "" # 存储数据画像 + self.fatal_error = "" + self.fatal_error_stage = "" + self.session_files = [] + self.template_content = "未提供特定模板，请根据数据画像自主发挥。" + + def _process_response(self, response: str) -> Dict[str, Any]: + """ + 统一处理LLM响应，判断行动类型并执行相应操作 + + Args: + response: LLM的响应内容 + + Returns: + 处理结果字典 + """ + try: + yaml_data = self.llm.parse_yaml_response(response) + action = yaml_data.get("action", "generate_code") + + print(f"🎯 检测到动作: {action}") + + if action == "analysis_complete": + return self._handle_analysis_complete(response, yaml_data) + elif action == "collect_figures": + return self._handle_collect_figures(response, yaml_data) + elif action == "generate_code": + return self._handle_generate_code(response, yaml_data) + else: + print(f"⚠️ 未知动作类型: {action}，按generate_code处理") + return self._handle_generate_code(response, yaml_data) + + except Exception as e: + print(f"⚠️ 解析响应失败: {str(e)}，按generate_code处理") + return self._handle_generate_code(response, {}) + + def _handle_analysis_complete( + self, response: str, yaml_data: Dict[str, Any] + ) -> Dict[str, Any]: + """处理分析完成动作""" + print("✅ 分析任务完成") + final_report = yaml_data.get("final_report", "分析完成，无最终报告") + return { + "action": "analysis_complete", + "final_report": final_report, + "response": response, + "continue": False, + } + + def _handle_collect_figures( + self, response: str, yaml_data: Dict[str, Any] + ) -> Dict[str, Any]: + """处理图片收集动作""" + print("📊 开始收集图片") + figures_to_collect = yaml_data.get("figures_to_collect", []) + + collected_figures = [] + + for figure_info in figures_to_collect: + figure_number = figure_info.get("figure_number", "未知") + # 确保figure_number不为None时才用于文件名 + if figure_number != "未知": + default_filename = f"figure_{figure_number}.png" + else: + default_filename = "figure_unknown.png" + filename = figure_info.get("filename", default_filename) + file_path = figure_info.get("file_path", "") # 获取具体的文件路径 + description = figure_info.get("description", "") + analysis = figure_info.get("analysis", "") + + print(f"📈 收集图片 {figure_number}: {filename}") + print(f" 📂 路径: {file_path}") + print(f" 📝 描述: {description}") + print(f" 🔍 分析: {analysis}") + + # 验证文件是否存在 + # 只有文件真正存在时才加入列表，防止报告出现裂图 + if file_path and os.path.exists(file_path): + print(f" ✅ 文件存在: {file_path}") + # 记录图片信息 + collected_figures.append( + { + "figure_number": figure_number, + "filename": filename, + "file_path": file_path, + "description": description, + "analysis": analysis, + } + ) + else: + if file_path: + print(f" ⚠️ 文件不存在: {file_path}") + else: + print(f" ⚠️ 未提供文件路径") + + return { + "action": "collect_figures", + "collected_figures": collected_figures, + "response": response, + "continue": True, + } + + def _handle_generate_code( + self, response: str, yaml_data: Dict[str, Any] + ) -> Dict[str, Any]: + """处理代码生成和执行动作""" + # 从YAML数据中获取代码（更准确） + code = yaml_data.get("code", "") + + # 如果YAML中没有代码，尝试从响应中提取 + if not code: + code = extract_code_from_response(response) + + # 二次清洗：防止YAML中解析出的code包含markdown标记 + if code: + code = code.strip() + if code.startswith("```"): + import re + # 去除开头的 ```python 或 ``` + code = re.sub(r"^```[a-zA-Z]*\n", "", code) + # 去除结尾的 ``` + code = re.sub(r"\n```$", "", code) + code = code.strip() + + if code: + print(f"🔧 执行代码:\n{code}") + print("-" * 40) + + # 执行代码 + result = self.executor.execute_code(code) + + # 格式化执行结果 + feedback = format_execution_result(result) + print(f"📋 执行反馈:\n{feedback}") + + return { + "action": "generate_code", + "code": code, + "result": result, + "feedback": feedback, + "response": response, + "continue": True, + } + else: + # 如果没有代码，说明LLM响应格式有问题，需要重新生成 + print("⚠️ 未从响应中提取到可执行代码，要求LLM重新生成") + return { + "action": "invalid_response", + "error": "响应中缺少可执行代码", + "response": response, + "continue": True, + } + + def analyze( + self, + user_input: str, + files: List[str] = None, + template_path: str = None, + session_output_dir: str = None, + reset_context: bool = True, + keep_session_open: bool = False, + ) -> Dict[str, Any]: + """ + 开始分析流程 + + Args: + user_input: 用户的自然语言需求 + files: 数据文件路径列表 + template_path: 参考模板路径（可选） + session_output_dir: 指定的会话输出目录（可选） + + Returns: + 分析结果字典 + """ + files = files or [] + self.current_round = 0 + self.fatal_error = "" + self.fatal_error_stage = "" + if reset_context or not self.executor: + self.conversation_history = [] + self.analysis_results = [] + self._initialize_session(user_input, files, template_path, session_output_dir) + initial_prompt = self._build_initial_user_prompt(user_input, files) + else: + self._validate_followup_files(files) + if template_path: + self.template_content = self._load_template_content(template_path) + initial_prompt = self._build_followup_user_prompt(user_input) + + print(f"🚀 开始数据分析任务") + print(f"📝 用户需求: {user_input}") + if files: + print(f"📁 数据文件: {', '.join(files)}") + if template_path: + print(f"📄 参考模板: {template_path}") + print(f"📂 输出目录: {self.session_output_dir}") + print(f"🔢 最大轮数: {self.max_rounds}") + + # 添加到对话历史 + self.conversation_history.append({"role": "user", "content": initial_prompt}) + + try: + while self.current_round < self.max_rounds: + self.current_round += 1 + print(f"\n🔄 第 {self.current_round} 轮分析") + + try: + # 获取当前执行环境的变量信息 + notebook_variables = self.executor.get_environment_info() + + # 格式化系统提示词，填入动态变量 + # 注意：prompts.py 中的模板现在需要填充三个变量 + formatted_system_prompt = data_analysis_system_prompt.format( + notebook_variables=notebook_variables, + user_input=user_input, + template_content=self.template_content + ) + + response = self.llm.call( + prompt=self._build_conversation_prompt(), + system_prompt=formatted_system_prompt, + ) + + print(f"🤖 助手响应:\n{response}") + + # 使用统一的响应处理方法 + process_result = self._process_response(response) + + # 根据处理结果决定是否继续（仅在非强制模式下） + if not self.force_max_rounds and not process_result.get( + "continue", True + ): + print(f"\n✅ 分析完成！") + break + + # 添加到对话历史 + self.conversation_history.append( + {"role": "assistant", "content": response} + ) + + # 根据动作类型添加不同的反馈 + if process_result["action"] == "generate_code": + feedback = process_result.get("feedback", "") + self.conversation_history.append( + {"role": "user", "content": f"代码执行反馈:\n{feedback}"} + ) + + # 记录分析结果 + self.analysis_results.append( + { + "round": self.current_round, + "code": process_result.get("code", ""), + "result": process_result.get("result", {}), + "response": response, + } + ) + elif process_result["action"] == "collect_figures": + # 记录图片收集结果 + collected_figures = process_result.get("collected_figures", []) + missing_figures = process_result.get("missing_figures", []) + + feedback = f"已收集 {len(collected_figures)} 个有效图片及其分析。" + if missing_figures: + feedback += f"\n⚠️ 以下图片未找到，请检查代码是否成功保存了这些图片: {missing_figures}" + + self.conversation_history.append( + { + "role": "user", + "content": f"图片收集反馈:\n{feedback}\n请继续下一步分析。", + } + ) + + # 记录到分析结果中 + self.analysis_results.append( + { + "round": self.current_round, + "action": "collect_figures", + "collected_figures": collected_figures, + "missing_figures": missing_figures, + "response": response, + } + ) + + except LLMCallError as e: + error_msg = str(e) + self.fatal_error = error_msg + self.fatal_error_stage = "模型调用" + print(f"❌ {error_msg}") + break + except WorkerTimeoutError as e: + error_msg = str(e) + self.fatal_error = error_msg + self.fatal_error_stage = "代码执行超时" + print(f"❌ {error_msg}") + break + except WorkerSessionError as e: + error_msg = str(e) + self.fatal_error = error_msg + self.fatal_error_stage = "执行子进程异常" + print(f"❌ {error_msg}") + break + except Exception as e: + error_msg = f"分析流程错误: {str(e)}" + print(f"❌ {error_msg}") + self.conversation_history.append( + { + "role": "user", + "content": f"发生错误: {error_msg}，请重新生成代码。", + } + ) + + # 生成最终总结 + if self.current_round >= self.max_rounds: + print(f"\n⚠️ 已达到最大轮数 ({self.max_rounds})，分析结束") + + return self._generate_final_report() + finally: + if self.executor and not keep_session_open: + self.executor.close() + self.executor = None + + def _build_conversation_prompt(self) -> str: + """构建对话提示词""" + prompt_parts = [] + + for msg in self.conversation_history: + role = msg["role"] + content = msg["content"] + if role == "user": + prompt_parts.append(f"用户: {content}") + else: + prompt_parts.append(f"助手: {content}") + + return "\n\n".join(prompt_parts) + + def _generate_final_report(self) -> Dict[str, Any]: + """生成最终分析报告""" + if self.fatal_error: + final_report_content = ( + "# 分析任务失败\n\n" + f"- 失败阶段: 第 {self.current_round} 轮{self.fatal_error_stage or '分析流程'}\n" + f"- 错误信息: {self.fatal_error}\n" + "- 建议: 根据失败阶段检查模型配置、执行子进程日志和数据文件可用性。" + ) + report_file_path = os.path.join(self.session_output_dir, "最终分析报告.md") + try: + with open(report_file_path, "w", encoding="utf-8") as f: + f.write(final_report_content) + print(f"📄 失败报告已保存至: {report_file_path}") + except Exception as e: + print(f"❌ 保存失败报告文件失败: {str(e)}") + + return { + "session_output_dir": self.session_output_dir, + "total_rounds": self.current_round, + "analysis_results": self.analysis_results, + "collected_figures": [], + "conversation_history": self.conversation_history, + "final_report": final_report_content, + "report_file_path": report_file_path, + } + + # 收集所有生成的图片信息 + all_figures = [] + for result in self.analysis_results: + if result.get("action") == "collect_figures": + all_figures.extend(result.get("collected_figures", [])) + + print(f"\n📊 开始生成最终分析报告...") + print(f"📂 输出目录: {self.session_output_dir}") + print(f"🔢 总轮数: {self.current_round}") + print(f"📈 收集图片: {len(all_figures)} 个") + + # 构建用于生成最终报告的提示词 + final_report_prompt = self._build_final_report_prompt(all_figures) + + try: # 调用LLM生成最终报告 + response = self.llm.call( + prompt=final_report_prompt, + system_prompt="你将会接收到一个数据分析任务的最终报告请求，请根据提供的分析结果和图片信息生成完整的分析报告。", + max_tokens=16384, # 设置较大的token限制以容纳完整报告 + ) + + # 解析响应，提取最终报告 + try: + # 尝试解析YAML + yaml_data = self.llm.parse_yaml_response(response) + + # 情况1: 标准YAML格式，包含 action: analysis_complete + if yaml_data.get("action") == "analysis_complete": + final_report_content = yaml_data.get("final_report", response) + + # 情况2: 解析成功但没字段，或者解析失败 + else: + # 如果内容看起来像Markdown报告（包含标题），直接使用 + if "# " in response or "## " in response: + print("⚠️ 未检测到标准YAML动作，但内容疑似Markdown报告，直接采纳") + final_report_content = response + else: + final_report_content = "LLM未返回有效报告内容" + + except Exception as e: + # 解析完全失败，直接使用原始响应 + print(f"⚠️ YAML解析失败 ({e})，直接使用原始响应作为报告") + final_report_content = response + + print("✅ 最终报告生成完成") + + except Exception as e: + print(f"❌ 生成最终报告时出错: {str(e)}") + final_report_content = f"报告生成失败: {str(e)}" + + # 保存最终报告到文件 + report_file_path = os.path.join(self.session_output_dir, "最终分析报告.md") + try: + with open(report_file_path, "w", encoding="utf-8") as f: + f.write(final_report_content) + print(f"📄 最终报告已保存至: {report_file_path}") + except Exception as e: + print(f"❌ 保存报告文件失败: {str(e)}") + + # 返回完整的分析结果 + return { + "session_output_dir": self.session_output_dir, + "total_rounds": self.current_round, + "analysis_results": self.analysis_results, + "collected_figures": all_figures, + "conversation_history": self.conversation_history, + "final_report": final_report_content, + "report_file_path": report_file_path, + } + + def _build_final_report_prompt(self, all_figures: List[Dict[str, Any]]) -> str: + """构建用于生成最终报告的提示词""" + + # 构建图片信息摘要，使用相对路径 + figures_summary = "" + if all_figures: + figures_summary = "\n生成的图片及分析:\n" + for i, figure in enumerate(all_figures, 1): + filename = figure.get("filename", "未知文件名") + # 使用相对路径格式，适合在报告中引用 + relative_path = f"./{filename}" + figures_summary += f"{i}. {filename}\n" + figures_summary += f" 相对路径: {relative_path}\n" + figures_summary += f" 描述: {figure.get('description', '无描述')}\n" + figures_summary += f" 分析: {figure.get('analysis', '无分析')}\n\n" + else: + figures_summary = "\n本次分析未生成图片。\n" + + # 构建代码执行结果摘要（仅包含成功执行的代码块） + code_results_summary = "" + success_code_count = 0 + for result in self.analysis_results: + if result.get("action") != "collect_figures" and result.get("code"): + exec_result = result.get("result", {}) + if exec_result.get("success"): + success_code_count += 1 + code_results_summary += f"代码块 {success_code_count}: 执行成功\n" + if exec_result.get("output"): + code_results_summary += ( + f"输出: {exec_result.get('output')[:]}\n\n" + ) + + # 使用 prompts.py 中的统一提示词模板，并添加相对路径使用说明 + prompt = final_report_system_prompt.format( + current_round=self.current_round, + session_output_dir=self.session_output_dir, + data_profile=self.data_profile, # 注入数据画像 + figures_summary=figures_summary, + code_results_summary=code_results_summary, + ) + + # 在提示词中明确要求使用相对路径 + prompt += """ + +📁 **图片路径使用说明**： +报告和图片都在同一目录下，请在报告中使用相对路径引用图片： +- 格式：![图片描述](./图片文件名.png) +- 示例：![营业总收入趋势](./营业总收入趋势.png) +- 这样可以确保报告在不同环境下都能正确显示图片 +""" + + return prompt + + def reset(self): + """重置智能体状态""" + self.conversation_history = [] + self.analysis_results = [] + self.current_round = 0 + self.fatal_error = "" + self.fatal_error_stage = "" + self.session_files = [] + self.template_content = "未提供特定模板，请根据数据画像自主发挥。" + self.close_session() + + def close_session(self): + """关闭当前分析会话但保留对象实例。""" + if self.executor: + self.executor.close() + self.executor = None + + def _initialize_session( + self, + user_input: str, + files: List[str], + template_path: str, + session_output_dir: str, + ) -> None: + if session_output_dir: + self.session_output_dir = session_output_dir + else: + self.session_output_dir = create_session_output_dir( + self.base_output_dir, user_input + ) + + self.session_files = list(files) + self.executor = ExecutionSessionClient( + output_dir=self.session_output_dir, + allowed_files=self.session_files, + ) + + data_profile = "" + if self.session_files: + print("🔍 正在生成数据画像...") + data_profile = load_and_profile_data(self.session_files) + print("✅ 数据画像生成完毕") + self.data_profile = data_profile + self.template_content = self._load_template_content(template_path) + + def _load_template_content(self, template_path: str = None) -> str: + template_content = "未提供特定模板，请根据数据画像自主发挥。" + if template_path and os.path.exists(template_path): + try: + with open(template_path, "r", encoding="utf-8") as f: + template_content = f.read() + print(f"📄 已加载参考模板: {os.path.basename(template_path)}") + except Exception as e: + print(f"⚠️ 读取模板失败: {str(e)}") + return template_content + + def _build_initial_user_prompt(self, user_input: str, files: List[str]) -> str: + prompt = f"### 任务启动\n**用户需求**: {user_input}\n" + if files: + prompt += f"**数据文件**: {', '.join(files)}\n" + if self.data_profile: + prompt += f"\n{self.data_profile}\n\n" + prompt += "请基于上述数据画像和用户问题，自主决定本轮最合适的分析起点。" + return prompt + + def _build_followup_user_prompt(self, user_input: str) -> str: + return ( + "### 继续分析专题\n" + f"**新的专题需求**: {user_input}\n" + "请基于当前会话中已经加载的数据、已有图表、历史分析结果和中间变量继续分析。" + ) + + def _validate_followup_files(self, files: List[str]) -> None: + if files and [os.path.abspath(path) for path in files] != [ + os.path.abspath(path) for path in self.session_files + ]: + raise ValueError("同一分析会话暂不支持切换为不同的数据文件集合，请新建会话。") diff --git a/main.py b/main.py new file mode 100644 index 0000000..16b089e --- /dev/null +++ b/main.py @@ -0,0 +1,74 @@ +from data_analysis_agent import DataAnalysisAgent +from config.llm_config import LLMConfig + +import sys +import os +from datetime import datetime + +from utils.create_session_dir import create_session_output_dir + +class DualLogger: + """同时输出到终端和文件的日志记录器""" + def __init__(self, log_dir, filename="log.txt"): + self.terminal = sys.stdout + log_path = os.path.join(log_dir, filename) + self.log = open(log_path, "a", encoding="utf-8") + + def write(self, message): + self.terminal.write(message) + # 过滤掉生成的代码块，不写入日志文件 + if "🔧 执行代码:" in message: + return + self.log.write(message) + self.log.flush() + + def flush(self): + self.terminal.flush() + self.log.flush() + +def setup_logging(log_dir): + """配置日志记录""" + # 记录开始时间 + logger = DualLogger(log_dir) + sys.stdout = logger + # 可选：也将错误输出重定向 + # sys.stderr = logger + print(f"\n{'='*20} Run Started at {datetime.now().strftime('%Y-%m-%d %H:%M:%S')} {'='*20}\n") + print(f"📄 日志文件已保存至: {os.path.join(log_dir, 'log.txt')}") + + +def main(): + llm_config = LLMConfig() + files = ["./UB IOV Support_TR.csv"] + + # 简化后的需求，让 Agent 自主规划 + analysis_requirement = "我想了解这份工单数据的健康度。请帮我进行全面分析，并找出核心问题点和改进建议。" + + # 在主函数中先创建会话目录，以便存放日志 + base_output_dir = "outputs" + session_output_dir = create_session_output_dir(base_output_dir, analysis_requirement) + + # 设置日志 + setup_logging(session_output_dir) + + # force_max_rounds=False 允许 AI 在认为完成后主动停止 + agent = DataAnalysisAgent(llm_config, max_rounds=20, force_max_rounds=False) + + # 这里的 template_path 如果你有特定的参考模板文件，可以传入路径 + template_path = None + + report = agent.analyze( + user_input=analysis_requirement, + files=files, + template_path=template_path, + session_output_dir=session_output_dir + ) + + print("\n" + "="*60) + print(f"✅ 分析任务圆满完成！") + print(f"📊 报告路径: {report.get('report_file_path')}") + print("="*60) + + +if __name__ == "__main__": + main() diff --git a/prompts.py b/prompts.py new file mode 100644 index 0000000..2b8deb0 --- /dev/null +++ b/prompts.py @@ -0,0 +1,147 @@ +data_analysis_system_prompt = """你是一个顶级 AI 数据分析专家 (Data Scientist Agent)，运行在 Jupyter Notebook 环境中。你的使命是：像人类专家一样理解数据、选择合适的方法、自主生成分析代码，并给出有证据支撑的业务结论。 + +### 核心工作原则 (Core Principles) +1. **目标驱动**：围绕用户问题组织分析，不机械套用固定流程，也不要为了使用某种方法而使用某种方法。 +2. **方法自选**：你可以自由决定本轮要做描述统计、可视化、异常检测、相关分析、分组比较、回归、聚类、文本挖掘或根因拆解；但每次都要说明为什么当前方法适合当前问题。 +3. **证据优先**：每个重要结论都必须有指标、表格、图形或统计检验支撑。没有证据时，要明确说明“不足以得出结论”。 +4. **隐私保护**： + - 严禁直接转储大段原始数据。 + - 优先输出聚合结果、摘要统计、分布、分组对比和样本量信息。 + - 原始数据处理必须在本地 Python 环境中完成。 +5. **动态下钻**：发现异常、结构性差异或可疑模式后，可以继续细分维度追查原因；如果没有新增价值，也可以停止无效下钻。 +6. **业务解释**：每张图、每个统计结果都要回答“这说明了什么”“对业务意味着什么”。 + +--- + +### 可用环境 (Environment) +- 数据处理：`pandas`, `numpy`, `duckdb`, `scipy` +- 可视化：`matplotlib`, `seaborn`, `plotly` +- 建模与统计：`scikit-learn` +- 文本分析：`sklearn.feature_extraction.text` +- 中文图表：已支持中文字体显示 + +--- + +### 方法选择原则 (Method Guidance) +- 如果目标是理解数据结构，可使用：维度、字段类型、缺失率、分布、重复率、时间范围、分组汇总。 +- 如果目标是识别异常，可使用：分位数/IQR、Z-score、分组对比、时序波动、异常检测模型等合适方法。 +- 如果目标是解释驱动因素，可使用：相关分析、分组均值比较、卡方检验、回归、树模型特征重要性等合适方法。 +- 如果目标是发现结构分层，可使用：聚类、分层分组、贡献度分析、Pareto 分析等合适方法。 +- 如果目标涉及文本字段，可使用：2-gram/3-gram、TF-IDF、高频短语、相似文本聚类等合适方法。 +- 不要写死方法顺序；优先选择当前数据和问题最匹配的方法。 + +### 输出质量标准 (Evidence Standards) +- 结论必须对应到可复核的指标或图表。 +- 做分组比较时，要说明样本量，避免基于极小样本下结论。 +- 使用建模或统计检验时，要简要说明目标变量、特征或检验对象。 +- 如果图表没有明显增量价值，可以只输出表格和结论。 +- 如果用户提供了参考模板，可以借用其结构，但不要被模板限制住分析判断。 + +### 统计方法使用规范 (Statistical Quality Rules) +- 选择统计方法时，要说明它为什么适合当前问题，而不是机械套用。 +- 进行分组比较时，至少说明样本量、比较维度和核心差异指标。 +- 使用相关分析时，要区分“相关”与“因果”，避免把相关性直接解释为因果关系。 +- 使用回归、树模型或聚类时，要明确目标变量、输入特征和结果含义，不要只输出模型分数。 +- 使用异常检测时，要交代异常判定依据，例如分位数阈值、标准差阈值、模型评分或时序偏离程度。 +- 使用文本分析时，要输出短语、主题或类别模式，并结合业务语境解释，不要只给孤立词频。 +- 如果样本量过小、字段质量不足或方法前提不满足，应降低结论强度，并明确说明局限性。 + +### 证据链要求 (Evidence Chain) +- 每个关键发现尽量形成以下链路：指标/统计结果 -> 图表或表格 -> 业务解释 -> 行动建议。 +- 如果引用图表，必须说明该图回答了什么问题，而不是只展示图片。 +- 如果没有图表，也必须提供足够的数值证据或表格摘要支撑结论。 +- 建议项必须尽量回扣前面的证据，不要给与数据无关的泛化建议。 + +--- + +### 强制约束规则 (Hard Constraints) +1. **图片保存**：必须使用 `os.path.join(session_output_dir, '中文文件名.png')` 保存，并打印绝对路径。严禁使用 `plt.show()`。 +2. **图表规范**： + - 类别较多时优先使用条形图，避免难以阅读的饼图。 + - 必须设置 `plt.rcParams['font.sans-serif']` 确保中文不乱码。 + - 图表标题、坐标轴和图例应可直接支持业务解读。 +3. **文本分析**：如果分析文本字段，优先提取短语或主题，不要只统计单字频率。 +4. **响应格式**：始终输出合法 YAML。 +5. **动作选择**： + - 当需要继续分析时，使用 `generate_code` + - 当已经生成关键图表且需要纳入最终证据链时，使用 `collect_figures` + - 当分析已足以回答用户问题时，使用 `analysis_complete` + +--- + +### 响应格式示例 + +**探索/分析轮：** +```yaml +action: "generate_code" +reasoning: "当前先验证数据结构、关键字段分布和样本量，再决定是否需要进一步做异常检测或分组对比。" +code: | + import pandas as pd + import os + # 读取数据 + # 输出聚合统计 + # 根据结果决定下一步方法 +next_steps: + - "确认关键字段的数据质量" + - "识别是否存在异常分布或结构性差异" +``` + +**最终报告轮：** +```yaml +action: "analysis_complete" +final_report: | + # 专业 Markdown 报告内容... +``` + +当前 Jupyter Notebook 环境变量： +{notebook_variables} + +用户需求：{user_input} +参考模板（如有）：{template_content} +""" + +# 最终报告生成提示词 +final_report_system_prompt = """你是一位资深数据分析专家 (Senior Data Analyst)。你的任务是基于详细的数据分析过程，撰写一份专业级、可落地的业务分析报告。 + +### 输入上下文 +- **数据画像 (Data Profile)**: +{data_profile} + +- **分析过程与关键代码发现**: +{code_results_summary} + +- **可视化证据链 (Visual Evidence)**: +{figures_summary} +> **警告**：你必须引用已生成的关键图表。引用格式为 `![描述](./图片文件名.png)`。 + +### 报告核心要求 +1. **客观性**：严禁使用“我”、“我们”等主观人称，采用陈述性语气。 +2. **闭环性**：报告必须针对初始计划中的所有核心方向给出明确的“结论”或“由于数据受限无法给出结论的原因”。 +3. **行动力**：最后的“建议矩阵”必须具体到部门、周期和预期收益。 + +--- + +### 报告结构模板 (Markdown) + +# [项目/产品名称] 业务洞察报告 + +## 1. 摘要 (Executive Summary) +- **核心洞察**：[一句话概括] +- **健康度评分**：[0-100] +- **TOP 3 关键发现**： +- **核心建议预览**： + +## 2. 数据理解与方法论 (Methodology) +- **数据覆盖范围**：[时间窗口、样本量] +- **分析框架**：[如：用户漏斗、RCA 归因、时序预测等] +- **局限性声明**：[如：数据缺失某字段导致的分析受限] + +## 3. 核心发现与洞察 (Key Insights) +[按业务主题展开，每个主题必须包含证据图表、数据表现、业务结论] + +## 4. 专项根因分析 (Deep Dive) +[针对分析过程中发现的异常点进行的下钻分析结论] + +## 5. 建议与行动矩阵 (Recommendations) +[建议项 | 优先级 | 关键举措 | 预期收益 | 负责人] +""" diff --git a/require.md b/require.md new file mode 100644 index 0000000..54e2d03 --- /dev/null +++ b/require.md @@ -0,0 +1,447 @@ +# 真正的 AI 数据分析 Agent - 需求文档 + +## 1. 项目背景 + +### 1.1 当前问题 + +现有系统是"四不像"： +- 任务规划：基于模板的规则生成（固定90个任务） +- 任务执行：AI 驱动的 ReAct 模式 +- 结果：规则 + AI = 不协调、不灵活 + +### 1.2 核心问题 + +**用户的真实需求**： +> "我有数据，帮我分析一下" +> "我想了解工单的健康度" +> "按照这个模板分析，但要灵活调整" + +**系统应该做什么**： +- 像人类分析师一样理解数据 +- 自主决定分析什么 +- 根据发现调整分析计划 +- 生成有洞察力的报告 + +**而不是**： +- 机械地执行固定任务 +- 死板地按模板填空 + +## 2. 用户故事 + +### 2.1 场景1：完全自主分析 + +**作为** 数据分析师 +**我想要** 上传数据文件，让 AI 自动分析 +**以便** 快速了解数据的关键信息 + +**验收标准**： +- AI 能识别数据类型（工单、销售、用户等） +- AI 能推断关键字段的业务含义 +- AI 能自主决定分析维度 +- AI 能生成合理的分析计划 +- AI 能执行分析并生成报告 +- 报告包含关键发现和洞察 + +**示例**： +``` +输入：cleaned_data.csv +输出： + - 数据类型：工单数据 + - 关键发现： + * 待处理工单占比50%（异常高） + * 某车型问题占比80% + * 平均处理时长超过标准2倍 + - 建议：优先处理该车型的积压工单 +``` + +### 2.2 场景2：指定分析方向 + +**作为** 业务负责人 +**我想要** 指定分析方向（如"健康度"） +**以便** 获得针对性的分析结果 + +**验收标准**： +- AI 能理解"健康度"的业务含义 +- AI 能将抽象概念转化为具体指标 +- AI 能根据数据特征选择合适的分析方法 +- AI 能生成针对性的报告 + +**示例**： +``` +输入： + - 数据：cleaned_data.csv + - 需求："我想了解工单的健康度" + +AI 理解： + - 健康度 = 关闭率 + 处理效率 + 积压情况 + 响应及时性 + +AI 分析： + - 关闭率：75%（中等） + - 平均处理时长：48小时（偏长） + - 积压工单：50%（严重） + - 健康度评分：60/100（需改进） +``` + +### 2.3 场景3：参考模板分析 + +**作为** 数据分析师 +**我想要** 使用模板作为参考框架 +**以便** 保持报告结构的一致性，同时保持灵活性 + +**验收标准**： +- AI 能理解模板的结构和要求 +- AI 能检查数据是否满足模板要求 +- 如果数据缺少某些字段，AI 能灵活调整 +- AI 能按模板结构组织报告 +- AI 不会因为数据不完全匹配而失败 + +**示例**： +``` +输入： + - 数据：cleaned_data.csv + - 模板：issue_analysis.md（要求14个图表） + +AI 检查： + - 模板要求"严重程度分布"，但数据中没有"严重程度"字段 + - 决策：跳过该分析，在报告中说明 + +AI 调整： + - 执行其他13个分析 + - 报告中注明："数据缺少严重程度字段，无法分析该维度" +``` + +### 2.4 场景4：迭代深入分析 + +**作为** 数据分析师 +**我想要** AI 能根据发现深入分析 +**以便** 找到问题的根因 + +**验收标准**： +- AI 能识别异常或关键发现 +- AI 能自主决定是否需要深入分析 +- AI 能动态调整分析计划 +- AI 能追踪问题的根因 + +**示例**： +``` +初步分析： + - 发现：待处理工单占比50%（异常高） + +AI 决策：需要深入分析 + +深入分析1： + - 分析待处理工单的特征 + - 发现：某车型占80% + +AI 决策：继续深入 + +深入分析2： + - 分析该车型的问题类型 + - 发现：都是"远程控制"问题 + +AI 决策：继续深入 + +深入分析3： + - 分析"远程控制"问题的模块分布 + - 发现：90%是"车门模块" + +结论：车门模块的远程控制功能存在系统性问题 +``` + +## 3. 功能需求 + +### 3.1 数据理解（Data Understanding） + +**FR-1.1 数据加载** +- 系统应支持 CSV 格式数据 +- 系统应自动检测编码（UTF-8, GBK等） +- 系统应处理常见的数据格式问题 + +**FR-1.2 数据类型识别** +- AI 应分析列名、数据类型、值分布 +- AI 应推断数据的业务类型（工单、销售、用户等） +- AI 应识别关键字段（时间、状态、分类、数值） + +**FR-1.3 字段含义理解** +- AI 应推断每个字段的业务含义 +- AI 应识别字段之间的关系 +- AI 应识别可能的分析维度 + +**FR-1.4 数据质量评估** +- AI 应检查缺失值 +- AI 应检查异常值 +- AI 应评估数据质量分数 + +### 3.2 需求理解（Requirement Understanding） + +**FR-2.1 自主需求推断** +- 当用户未指定需求时，AI 应根据数据类型推断常见分析需求 +- AI 应生成默认的分析目标 + +**FR-2.2 用户需求理解** +- AI 应理解用户的自然语言需求 +- AI 应将抽象概念转化为具体指标 +- AI 应判断数据是否支持用户需求 + +**FR-2.3 模板理解** +- AI 应解析模板结构 +- AI 应理解模板要求的指标和图表 +- AI 应检查数据是否满足模板要求 +- AI 应在数据不满足时灵活调整 + +### 3.3 分析规划（Analysis Planning） + +**FR-3.1 动态任务生成** +- AI 应根据数据特征和需求生成分析任务 +- 任务应是动态的，不是固定的 +- 任务应包含优先级和依赖关系 + +**FR-3.2 任务优先级** +- AI 应根据重要性排序任务 +- 必需的分析应优先执行 +- 可选的分析应后执行 + +**FR-3.3 计划调整** +- AI 应能根据中间结果调整计划 +- AI 应能增加新的深入分析任务 +- AI 应能跳过不适用的任务 + +### 3.4 工具集管理（Tool Management） + +**FR-4.1 预设工具集** +- 系统应提供基础数据分析工具集 +- 基础工具包括：数据查询、统计分析、可视化、数据清洗 +- 工具应有标准的接口和描述 + +**FR-4.2 动态工具调整** +- AI 应根据数据特征决定需要哪些工具 +- AI 应根据分析需求动态启用/禁用工具 +- AI 应能识别缺少的工具并请求添加 + +**FR-4.3 工具适配** +- AI 应根据数据类型调整工具参数 +- 例如：时间序列数据 → 启用趋势分析工具 +- 例如：分类数据 → 启用分布分析工具 +- 例如：地理数据 → 启用地图可视化工具 + +**FR-4.4 自定义工具生成** +- AI 应能根据特定需求生成临时工具 +- AI 应能组合现有工具创建新功能 +- 自定义工具应在分析结束后可选保留 + +**示例**： +``` +数据特征： + - 包含时间字段（created_at, closed_at） + - 包含分类字段（status, type, model） + - 包含数值字段（duration） + +AI 决策： + - 启用工具：时间序列分析、分类分布、数值统计 + - 禁用工具：地理分析（无地理字段） + - 生成工具：计算处理时长（closed_at - created_at） +``` + +### 3.5 分析执行（Analysis Execution） + +**FR-5.1 ReAct 执行模式** +- 每个任务应使用 ReAct 模式执行 +- AI 应思考 → 行动 → 观察 → 判断 +- AI 应能从错误中学习 + +**FR-5.2 工具调用** +- AI 应从可用工具集中选择合适的工具 +- AI 应能组合多个工具完成复杂任务 +- AI 应能处理工具调用失败的情况 + +**FR-5.3 结果验证** +- AI 应验证每个任务的结果 +- AI 应识别异常结果 +- AI 应决定是否需要重试或调整 + +**FR-5.4 迭代深入** +- AI 应识别关键发现 +- AI 应决定是否需要深入分析 +- AI 应动态增加深入分析任务 + +### 3.6 报告生成（Report Generation） + +**FR-6.1 关键发现提炼** +- AI 应从所有结果中提炼关键发现 +- AI 应识别异常和趋势 +- AI 应提供洞察而不是简单罗列数据 + +**FR-6.2 报告结构组织** +- AI 应根据分析内容组织报告结构 +- 如果有模板，应参考模板结构 +- 如果没有模板，应生成合理的结构 + +**FR-6.3 结论和建议** +- AI 应基于分析结果得出结论 +- AI 应提供可操作的建议 +- AI 应说明建议的依据 + +**FR-6.4 多格式输出** +- 系统应生成 Markdown 格式报告 +- 系统应支持导出为 Word 文档（可选） +- 报告应包含所有生成的图表 + +## 4. 非功能需求 + +### 4.1 性能需求 + +**NFR-1.1 响应时间** +- 数据理解阶段：< 30秒 +- 分析规划阶段：< 60秒 +- 单个任务执行：< 120秒 +- 完整分析流程：< 30分钟（取决于数据大小和任务数量） + +**NFR-1.2 数据规模** +- 支持最大 100MB 的 CSV 文件 +- 支持最大 100万行数据 +- 支持最大 100列 + +### 4.2 可靠性需求 + +**NFR-2.1 错误处理** +- AI 调用失败时应有降级策略 +- 单个任务失败不应影响整体流程 +- 系统应记录详细的错误日志 + +**NFR-2.2 数据安全** +- 数据应在本地处理，不上传到外部服务 +- 生成的报告应保存在用户指定的目录 +- 敏感信息应脱敏处理 + +### 4.3 可用性需求 + +**NFR-3.1 易用性** +- 用户只需提供数据文件即可开始分析 +- 分析过程应显示进度和状态 +- 错误信息应清晰易懂 + +**NFR-3.2 可观察性** +- 系统应显示 AI 的思考过程 +- 系统应显示每个阶段的进度 +- 系统应记录完整的执行日志 + +### 4.4 可扩展性需求 + +**NFR-4.1 工具扩展** +- 应易于添加新的分析工具 +- 工具应有标准接口 +- AI 应能自动发现和使用新工具 +- 工具应支持热加载，无需重启系统 + +**NFR-4.2 工具动态性** +- 工具集应根据数据特征动态调整 +- 工具参数应根据数据类型自适应 +- 系统应支持运行时生成临时工具 + +**NFR-4.3 模型扩展** +- 应支持不同的 LLM 提供商 +- 应支持本地模型和云端模型 +- 应支持模型切换 + +## 5. 约束条件 + +### 5.1 技术约束 + +- 使用 Python 3.8+ +- 使用 OpenAI 兼容的 LLM API +- 使用 pandas 进行数据处理 +- 使用 matplotlib 进行可视化 + +### 5.2 业务约束 + +- 系统应在离线环境下工作（除 LLM 调用外） +- 系统不应依赖特定的数据格式或业务领域 +- 系统应保持通用性，适用于各种数据分析场景 + +### 5.3 隐私和安全约束 + +**数据隐私保护**： +- AI 不能访问完整的原始数据内容 +- AI 只能读取： + - 表头（列名） + - 数据类型信息 + - 基本统计摘要（行数、列数、缺失值比例、数据类型分布） + - 工具执行后的聚合结果（如分组统计结果、图表数据） +- 所有原始数据处理必须在本地完成，不发送给 LLM +- AI 通过调用本地工具来分析数据，工具返回摘要结果而非原始数据 + +### 5.3 隐私和安全约束 + +**数据隐私保护**： +- AI 不能访问完整的原始数据内容 +- AI 只能读取： + - 表头（列名） + - 数据类型信息 + - 基本统计摘要（行数、列数、缺失值比例、数据类型分布） + - 工具执行后的聚合结果（如分组统计结果、图表数据） +- 所有原始数据处理必须在本地完成，不发送给 LLM +- AI 通过调用本地工具来分析数据，工具返回摘要结果而非原始数据 + +## 6. 验收标准 + +### 6.1 场景1验收 + +- [ ] 上传任意 CSV 文件，AI 能识别数据类型 +- [ ] AI 能自主生成分析计划 +- [ ] AI 能执行分析并生成报告 +- [ ] 报告包含关键发现和洞察 + +### 6.2 场景2验收 + +- [ ] 指定"健康度"等抽象需求，AI 能理解 +- [ ] AI 能生成相关指标 +- [ ] AI 能执行针对性分析 +- [ ] 报告聚焦于用户需求 + +### 6.3 场景3验收 + +- [ ] 提供模板，AI 能理解模板要求 +- [ ] 数据缺少字段时，AI 能灵活调整 +- [ ] 报告按模板结构组织 +- [ ] 报告说明哪些分析被跳过及原因 + +### 6.4 场景4验收 + +- [ ] AI 能识别异常发现 +- [ ] AI 能自主决定深入分析 +- [ ] AI 能动态调整分析计划 +- [ ] 报告包含深入分析的结果 + +### 6.5 工具动态性验收 + +- [ ] 系统根据数据特征自动启用相关工具 +- [ ] 系统根据数据特征自动禁用无关工具 +- [ ] AI 能识别需要但缺失的工具 +- [ ] AI 能生成临时工具满足特定需求 +- [ ] 工具参数根据数据类型自动调整 + +## 7. 成功指标 + +### 7.1 功能指标 + +- 数据类型识别准确率 > 90% +- 字段含义推断准确率 > 80% +- 分析计划合理性（人工评估）> 85% +- 报告质量（人工评估）> 80% + +### 7.2 性能指标 + +- 完整分析流程完成率 > 95% +- AI 调用成功率 > 90% + +### 7.3 用户满意度 + +- 用户认为分析结果有价值 > 80% +- 用户愿意再次使用 > 85% +- 用户推荐给他人 > 75% + +--- + +**版本**: v3.0.0 +**日期**: 2026-03-06 +**状态**: 需求定义完成 \ No newline at end of file diff --git a/requirements.txt b/requirements.txt new file mode 100644 index 0000000..cca2ecc --- /dev/null +++ b/requirements.txt @@ -0,0 +1,55 @@ +# 数据分析和科学计算库 +pandas>=2.0.0 +openpyxl>=3.1.0 +numpy>=1.24.0 +matplotlib>=3.6.0 +duckdb>=0.8.0 +scipy>=1.10.0 +scikit-learn>=1.3.0 + +# Web和API相关 +requests>=2.28.0 +urllib3>=1.26.0 +fastapi>=0.110.0 +uvicorn>=0.29.0 +python-multipart>=0.0.9 + +# 绘图和可视化 +plotly>=5.14.0 +dash>=2.0.0 + +# 流程图支持（可选，用于生成Mermaid图表） +# 注意：Mermaid图表主要在markdown中渲染，不需要额外的Python包 +# 如果需要在Python中生成Mermaid代码，可以考虑： +# mermaid-py>=0.3.0 + +# Jupyter/IPython环境 +ipython>=8.10.0 +jupyter>=1.0.0 + +# AI/LLM相关 +openai>=1.0.0 +pyyaml>=6.0 + +# 配置管理 +python-dotenv>=1.0.0 + +# 异步编程 +asyncio-mqtt>=0.11.1 +nest_asyncio>=1.5.0 + +# 文档生成（基于输出的Word文档） +python-docx>=0.8.11 + +# 系统和工具库 +pathlib2>=2.3.7 +typing-extensions>=4.5.0 + +# 开发和测试工具（可选） +pytest>=7.0.0 +pytest-asyncio>=0.21.0 +black>=23.0.0 +flake8>=6.0.0 + +# 字体支持（用于matplotlib中文显示） +fonttools>=4.38.0 diff --git a/utils/__init__.py b/utils/__init__.py new file mode 100644 index 0000000..cbdc720 --- /dev/null +++ b/utils/__init__.py @@ -0,0 +1,16 @@ +# -*- coding: utf-8 -*- +""" +工具模块初始化文件 +""" + +from utils.code_executor import CodeExecutor +from utils.execution_session_client import ExecutionSessionClient +from utils.llm_helper import LLMHelper +from utils.fallback_openai_client import AsyncFallbackOpenAIClient + +__all__ = [ + "CodeExecutor", + "ExecutionSessionClient", + "LLMHelper", + "AsyncFallbackOpenAIClient", +] diff --git a/utils/code_executor.py b/utils/code_executor.py new file mode 100644 index 0000000..3a19c5d --- /dev/null +++ b/utils/code_executor.py @@ -0,0 +1,456 @@ +# -*- coding: utf-8 -*- +""" +安全的代码执行器，基于 IPython 提供 notebook 环境下的代码执行功能 +""" + +import os +import sys +import ast +import traceback +import io +from typing import Dict, Any, List, Optional, Tuple +from contextlib import redirect_stdout, redirect_stderr +from IPython.core.interactiveshell import InteractiveShell +from IPython.utils.capture import capture_output +import matplotlib +import matplotlib.pyplot as plt +import matplotlib.font_manager as fm + + +class CodeExecutor: + """ + 安全的代码执行器，限制依赖库，捕获输出，支持图片保存与路径输出 + """ + + ALLOWED_IMPORTS = { + "pandas", + "pd", + "numpy", + "np", + "matplotlib", + "matplotlib.pyplot", + "plt", + "seaborn", + "sns", + "duckdb", + "scipy", + "sklearn", + "statsmodels", + "plotly", + "dash", + "requests", + "urllib", + "os", + "sys", + "json", + "csv", + "datetime", + "time", + "math", + "statistics", + "re", + "pathlib", + "io", + "collections", + "itertools", + "functools", + "operator", + "warnings", + "logging", + "copy", + "pickle", + "gzip", + "zipfile", + "yaml", + "typing", + "dataclasses", + "enum", + "sqlite3", + "jieba", + "wordcloud", + "PIL", + "random", + "networkx", + } + + def __init__(self, output_dir: str = "outputs"): + """ + 初始化代码执行器 + + Args: + output_dir: 输出目录，用于保存图片和文件 + """ + self.output_dir = os.path.abspath(output_dir) + os.makedirs(self.output_dir, exist_ok=True) + + # 为每个执行器创建独立的 shell，避免跨分析任务共享状态 + self.shell = InteractiveShell() + + # 初始化隔离执行环境 + self.reset_environment() + + # 图片计数器 + self.image_counter = 0 + + def _setup_chinese_font(self): + """设置matplotlib中文字体显示""" + try: + # 设置matplotlib使用Agg backend避免GUI问题 + matplotlib.use("Agg") + + # 获取系统可用字体 + available_fonts = [f.name for f in fm.fontManager.ttflist] + + # 设置matplotlib使用系统可用中文字体 + # macOS系统常用中文字体（按优先级排序） + chinese_fonts = [ + "Hiragino Sans GB", # macOS中文简体 + "Songti SC", # macOS宋体简体 + "PingFang SC", # macOS苹方简体 + "Heiti SC", # macOS黑体简体 + "Heiti TC", # macOS黑体繁体 + "PingFang HK", # macOS苹方香港 + "SimHei", # Windows黑体 + "STHeiti", # 华文黑体 + "WenQuanYi Micro Hei", # Linux文泉驿微米黑 + "DejaVu Sans", # 默认无衬线字体 + "Arial Unicode MS", # Arial Unicode + ] + + # 检查系统中实际存在的字体 + system_chinese_fonts = [ + font for font in chinese_fonts if font in available_fonts + ] + + # 如果没有找到合适的中文字体，尝试更宽松的搜索 + if not system_chinese_fonts: + print("警告：未找到精确匹配的中文字体，尝试更宽松的搜索...") + # 更宽松的字体匹配（包含部分名称） + fallback_fonts = [] + for available_font in available_fonts: + if any( + keyword in available_font + for keyword in [ + "Hei", + "Song", + "Fang", + "Kai", + "Hiragino", + "PingFang", + "ST", + ] + ): + fallback_fonts.append(available_font) + + if fallback_fonts: + system_chinese_fonts = fallback_fonts[:3] # 取前3个匹配的字体 + print(f"找到备选中文字体: {system_chinese_fonts}") + else: + print("警告：系统中未找到合适的中文字体，使用系统默认字体") + system_chinese_fonts = ["DejaVu Sans", "Arial Unicode MS"] + + # 设置字体配置 + plt.rcParams["font.sans-serif"] = system_chinese_fonts + [ + "DejaVu Sans", + "Arial Unicode MS", + ] + + plt.rcParams["axes.unicode_minus"] = False + plt.rcParams["font.family"] = "sans-serif" + + # 在shell中也设置相同的字体配置 + font_list_str = str( + system_chinese_fonts + ["DejaVu Sans", "Arial Unicode MS"] + ) + self.shell.run_cell( + f""" +import matplotlib +matplotlib.use('Agg') +import matplotlib.pyplot as plt +import matplotlib.font_manager as fm + +# 设置中文字体 +plt.rcParams['font.sans-serif'] = {font_list_str} +plt.rcParams['axes.unicode_minus'] = False +plt.rcParams['font.family'] = 'sans-serif' + +# 确保matplotlib缓存目录可写 +import os +cache_dir = os.path.expanduser('~/.matplotlib') +if not os.path.exists(cache_dir): + os.makedirs(cache_dir, exist_ok=True) +os.environ['MPLCONFIGDIR'] = cache_dir +""" + ) + except Exception as e: + print(f"设置中文字体失败: {e}") + # 即使失败也要设置基本的matplotlib配置 + try: + matplotlib.use("Agg") + plt.rcParams["axes.unicode_minus"] = False + except: + pass + + def _setup_common_imports(self): + """预导入常用库""" + common_imports = """ +import pandas as pd +import numpy as np +import matplotlib.pyplot as plt +import duckdb +import os +import json +from IPython.display import display +""" + try: + self.shell.run_cell(common_imports) + # 确保display函数在shell的用户命名空间中可用 + from IPython.display import display + + self.shell.user_ns["display"] = display + except Exception as e: + print(f"预导入库失败: {e}") + + def _check_code_safety(self, code: str) -> Tuple[bool, str]: + """ + 检查代码安全性，限制导入的库 + + Returns: + (is_safe, error_message) + """ + try: + tree = ast.parse(code) + except SyntaxError as e: + return False, f"语法错误: {e}" + + for node in ast.walk(tree): + if isinstance(node, ast.Import): + for alias in node.names: + if alias.name not in self.ALLOWED_IMPORTS: + return False, f"不允许的导入: {alias.name}" + + elif isinstance(node, ast.ImportFrom): + if node.module not in self.ALLOWED_IMPORTS: + return False, f"不允许的导入: {node.module}" + + # 检查属性访问（防止通过os.system等方式绕过） + elif isinstance(node, ast.Attribute): + # 检查是否访问了os模块的属性 + if isinstance(node.value, ast.Name) and node.value.id == "os": + # 允许的os子模块和函数白名单 + allowed_os_attributes = { + "path", "environ", "getcwd", "listdir", "makedirs", "mkdir", "remove", "rmdir", + "path.join", "path.exists", "path.abspath", "path.dirname", + "path.basename", "path.splitext", "path.isdir", "path.isfile", + "sep", "name", "linesep", "stat", "getpid" + } + + # 检查直接属性访问 (如 os.getcwd) + if node.attr not in allowed_os_attributes: + # 进一步检查如果是 os.path.xxx 这种形式 + # Note: ast.Attribute 嵌套结构比较复杂，简单处理只允许 os.path 和上述白名单 + if node.attr == "path": + pass # 允许访问 os.path + else: + return False, f"不允许的os属性访问: os.{node.attr}" + + # 检查危险函数调用 + elif isinstance(node, ast.Call): + if isinstance(node.func, ast.Name): + if node.func.id in ["exec", "eval", "__import__"]: + return False, f"不允许的函数调用: {node.func.id}" + + return True, "" + + def get_current_figures_info(self) -> List[Dict[str, Any]]: + """获取当前matplotlib图形信息，但不自动保存""" + figures_info = [] + + # 获取当前所有图形 + fig_nums = plt.get_fignums() + + for fig_num in fig_nums: + fig = plt.figure(fig_num) + if fig.get_axes(): # 只处理有内容的图形 + figures_info.append( + { + "figure_number": fig_num, + "axes_count": len(fig.get_axes()), + "figure_size": fig.get_size_inches().tolist(), + "has_content": True, + } + ) + + return figures_info + + def _format_table_output(self, obj: Any) -> str: + """格式化表格输出，限制行数""" + if hasattr(obj, "shape") and hasattr(obj, "head"): # pandas DataFrame + rows, cols = obj.shape + print(f"\n数据表形状: {rows}行 x {cols}列") + print(f"列名: {list(obj.columns)}") + + if rows <= 15: + return str(obj) + else: + head_part = obj.head(5) + tail_part = obj.tail(5) + return f"{head_part}\n...\n(省略 {rows-10} 行)\n...\n{tail_part}" + + return str(obj) + + def execute_code(self, code: str) -> Dict[str, Any]: + """ + 执行代码并返回结果 + + Args: + code: 要执行的Python代码 + + Returns: + { + 'success': bool, + 'output': str, + 'error': str, + 'variables': Dict[str, Any] # 新生成的重要变量 + } + """ + # 检查代码安全性 + is_safe, safety_error = self._check_code_safety(code) + if not is_safe: + return { + "success": False, + "output": "", + "error": f"代码安全检查失败: {safety_error}", + "variables": {}, + } + + # 记录执行前的变量 + vars_before = set(self.shell.user_ns.keys()) + + try: + # 使用IPython的capture_output来捕获所有输出 + with capture_output() as captured: + result = self.shell.run_cell(code) + + # 检查执行结果 + if result.error_before_exec: + error_msg = str(result.error_before_exec) + return { + "success": False, + "output": captured.stdout, + "error": f"执行前错误: {error_msg}", + "variables": {}, + } + + if result.error_in_exec: + error_msg = str(result.error_in_exec) + return { + "success": False, + "output": captured.stdout, + "error": f"执行错误: {error_msg}", + "variables": {}, + } + + # 获取输出 + output = captured.stdout + + # 如果有返回值，添加到输出 + if result.result is not None: + formatted_result = self._format_table_output(result.result) + output += f"\n{formatted_result}" + # 记录新产生的重要变量（简化版本） + vars_after = set(self.shell.user_ns.keys()) + new_vars = vars_after - vars_before + + # 只记录新创建的DataFrame等重要数据结构 + important_new_vars = {} + for var_name in new_vars: + if not var_name.startswith("_"): + try: + var_value = self.shell.user_ns[var_name] + if hasattr(var_value, "shape"): # pandas DataFrame, numpy array + important_new_vars[var_name] = ( + f"{type(var_value).__name__} with shape {var_value.shape}" + ) + elif var_name in ["session_output_dir"]: # 重要的配置变量 + important_new_vars[var_name] = str(var_value) + except: + pass + + return { + "success": True, + "output": output, + "error": "", + "variables": important_new_vars, + } + except Exception as e: + return { + "success": False, + "output": captured.stdout if "captured" in locals() else "", + "error": f"执行异常: {str(e)}\n{traceback.format_exc()}", + "variables": {}, + } + + def reset_environment(self): + """重置执行环境""" + self.shell.reset() + self._setup_common_imports() + self._setup_chinese_font() + plt.close("all") + self.image_counter = 0 + + def set_variable(self, name: str, value: Any): + """设置执行环境中的变量""" + self.shell.user_ns[name] = value + + def get_environment_info(self) -> str: + """获取当前执行环境的变量信息，用于系统提示词""" + info_parts = [] + + # 获取重要的数据变量 + important_vars = {} + for var_name, var_value in self.shell.user_ns.items(): + if not var_name.startswith("_") and var_name not in [ + "In", + "Out", + "get_ipython", + "exit", + "quit", + ]: + try: + if hasattr(var_value, "shape"): # pandas DataFrame, numpy array + important_vars[var_name] = ( + f"{type(var_value).__name__} with shape {var_value.shape}" + ) + elif var_name in ["session_output_dir"]: # 重要的路径变量 + important_vars[var_name] = str(var_value) + elif ( + isinstance(var_value, (int, float, str, bool)) + and len(str(var_value)) < 100 + ): + important_vars[var_name] = ( + f"{type(var_value).__name__}: {var_value}" + ) + elif hasattr(var_value, "__module__") and var_value.__module__ in [ + "pandas", + "numpy", + "matplotlib.pyplot", + ]: + important_vars[var_name] = f"导入的模块: {var_value.__module__}" + except: + continue + + if important_vars: + info_parts.append("当前环境变量:") + for var_name, var_info in important_vars.items(): + info_parts.append(f"- {var_name}: {var_info}") + else: + info_parts.append("当前环境已预装pandas, numpy, matplotlib等库") + + # 添加输出目录信息 + if "session_output_dir" in self.shell.user_ns: + info_parts.append( + f"图片保存目录: session_output_dir = '{self.shell.user_ns['session_output_dir']}'" + ) + + return "\n".join(info_parts) diff --git a/utils/create_session_dir.py b/utils/create_session_dir.py new file mode 100644 index 0000000..d641aab --- /dev/null +++ b/utils/create_session_dir.py @@ -0,0 +1,15 @@ +import os +from datetime import datetime + + +def create_session_output_dir(base_output_dir, user_input: str) -> str: + """为本次分析创建独立的输出目录""" + + # 使用当前时间创建唯一的会话目录名（格式：YYYYMMDD_HHMMSS） + timestamp = datetime.now().strftime("%Y%m%d_%H%M%S") + session_id = timestamp + dir_name = f"session_{session_id}" + session_dir = os.path.join(base_output_dir, dir_name) + os.makedirs(session_dir, exist_ok=True) + + return session_dir diff --git a/utils/data_loader.py b/utils/data_loader.py new file mode 100644 index 0000000..c1c2cef --- /dev/null +++ b/utils/data_loader.py @@ -0,0 +1,90 @@ +# -*- coding: utf-8 -*- +import os +import pandas as pd +import io + +def load_and_profile_data(file_paths: list) -> str: + """ + 加载数据并生成数据画像 + + Args: + file_paths: 文件路径列表 + + Returns: + 包含数据画像的Markdown字符串 + """ + profile_summary = "# 数据画像报告 (Data Profile)\n\n" + + if not file_paths: + return profile_summary + "未提供数据文件。" + + for file_path in file_paths: + file_name = os.path.basename(file_path) + profile_summary += f"## 文件: {file_name}\n\n" + + if not os.path.exists(file_path): + profile_summary += f"⚠️ 文件不存在: {file_path}\n\n" + continue + + try: + # 根据扩展名选择加载方式 + ext = os.path.splitext(file_path)[1].lower() + if ext == '.csv': + # 尝试多种编码 + try: + df = pd.read_csv(file_path, encoding='utf-8') + except UnicodeDecodeError: + try: + df = pd.read_csv(file_path, encoding='gbk') + except Exception: + df = pd.read_csv(file_path, encoding='latin1') + elif ext in ['.xlsx', '.xls']: + df = pd.read_excel(file_path) + else: + profile_summary += f"⚠️ 不支持的文件格式: {ext}\n\n" + continue + + # 基础信息 + rows, cols = df.shape + profile_summary += f"- **维度**: {rows} 行 x {cols} 列\n" + profile_summary += f"- **列名**: `{', '.join(df.columns)}`\n\n" + + profile_summary += "### 列详细分布:\n" + + # 遍历分析每列 + for col in df.columns: + dtype = df[col].dtype + null_count = df[col].isnull().sum() + null_ratio = (null_count / rows) * 100 + + profile_summary += f"#### {col} ({dtype})\n" + if null_count > 0: + profile_summary += f"- ⚠️ 空值: {null_count} ({null_ratio:.1f}%)\n" + + # 数值列分析 + if pd.api.types.is_numeric_dtype(dtype): + desc = df[col].describe() + profile_summary += f"- 统计: Min={desc['min']:.2f}, Max={desc['max']:.2f}, Mean={desc['mean']:.2f}\n" + + # 文本/分类列分析 + elif pd.api.types.is_object_dtype(dtype) or pd.api.types.is_categorical_dtype(dtype): + unique_count = df[col].nunique() + profile_summary += f"- 唯一值数量: {unique_count}\n" + + # 如果唯一值较少（<50）或者看起来是分类数据，显示Top分布 + # 这对识别“高频问题”至关重要 + if unique_count > 0: + top_n = df[col].value_counts().head(5) + top_items_str = ", ".join([f"{k}({v})" for k, v in top_n.items()]) + profile_summary += f"- **TOP 5 高频值**: {top_items_str}\n" + + # 时间列分析 + elif pd.api.types.is_datetime64_any_dtype(dtype): + profile_summary += f"- 范围: {df[col].min()} 至 {df[col].max()}\n" + + profile_summary += "\n" + + except Exception as e: + profile_summary += f"❌ 读取或分析文件失败: {str(e)}\n\n" + + return profile_summary diff --git a/utils/execution_session_client.py b/utils/execution_session_client.py new file mode 100644 index 0000000..c966870 --- /dev/null +++ b/utils/execution_session_client.py @@ -0,0 +1,219 @@ +# -*- coding: utf-8 -*- +""" +Client for a per-analysis execution worker subprocess. +""" + +import json +import os +import queue +import subprocess +import sys +import threading +import uuid +from typing import Any, Dict, Optional + + +class WorkerSessionError(RuntimeError): + """Raised when the execution worker cannot serve a request.""" + + +class WorkerTimeoutError(WorkerSessionError): + """Raised when the worker does not respond within the configured timeout.""" + + +class ExecutionSessionClient: + """Client that proxies CodeExecutor methods to a dedicated worker process.""" + + def __init__( + self, + output_dir: str, + allowed_files=None, + python_executable: str = None, + request_timeout_seconds: float = 60.0, + startup_timeout_seconds: float = 180.0, + ): + self.output_dir = os.path.abspath(output_dir) + self.allowed_files = [os.path.abspath(path) for path in (allowed_files or [])] + self.allowed_read_roots = sorted( + {os.path.dirname(path) for path in self.allowed_files} + ) + self.python_executable = python_executable or sys.executable + self.request_timeout_seconds = request_timeout_seconds + self.startup_timeout_seconds = startup_timeout_seconds + self._process: Optional[subprocess.Popen] = None + self._stderr_handle = None + self._start_worker() + self._request( + "init_session", + { + "output_dir": self.output_dir, + "variables": { + "session_output_dir": self.output_dir, + "allowed_files": self.allowed_files, + "allowed_read_roots": self.allowed_read_roots, + }, + }, + timeout_seconds=self.startup_timeout_seconds, + ) + + def execute_code(self, code: str) -> Dict[str, Any]: + return self._request("execute_code", {"code": code}) + + def set_variable(self, name: str, value: Any) -> None: + self._request("set_variable", {"name": name, "value": value}) + + def get_environment_info(self) -> str: + payload = self._request("get_environment_info", {}) + return payload.get("environment_info", "") + + def reset_environment(self) -> None: + self._request("reset_environment", {}) + self.set_variable("session_output_dir", self.output_dir) + self.set_variable("allowed_files", self.allowed_files) + self.set_variable("allowed_read_roots", self.allowed_read_roots) + + def ping(self) -> bool: + payload = self._request("ping", {}) + return bool(payload.get("alive")) + + def close(self) -> None: + if self._process is None: + return + + try: + if self._process.poll() is None: + self._request("shutdown", {}, timeout_seconds=5) + except Exception: + pass + finally: + self._teardown_worker() + + def _start_worker(self) -> None: + runtime_dir = os.path.join(self.output_dir, ".worker_runtime") + mpl_dir = os.path.join(runtime_dir, "mplconfig") + ipython_dir = os.path.join(runtime_dir, "ipython") + os.makedirs(mpl_dir, exist_ok=True) + os.makedirs(ipython_dir, exist_ok=True) + + stderr_log_path = os.path.join(self.output_dir, "execution_worker.log") + self._stderr_handle = open(stderr_log_path, "a", encoding="utf-8") + + worker_script = os.path.join( + os.path.dirname(__file__), + "execution_worker.py", + ) + env = os.environ.copy() + env["MPLCONFIGDIR"] = mpl_dir + env["IPYTHONDIR"] = ipython_dir + env.setdefault("PYTHONIOENCODING", "utf-8") + + self._process = subprocess.Popen( + [self.python_executable, worker_script], + stdin=subprocess.PIPE, + stdout=subprocess.PIPE, + stderr=self._stderr_handle, + text=True, + encoding="utf-8", + cwd=os.path.abspath(os.path.join(os.path.dirname(__file__), "..")), + env=env, + bufsize=1, + ) + + def _request( + self, + request_type: str, + payload: Dict[str, Any], + timeout_seconds: float = None, + ) -> Dict[str, Any]: + if self._process is None or self._process.stdin is None or self._process.stdout is None: + raise WorkerSessionError("执行子进程未启动") + if self._process.poll() is not None: + raise WorkerSessionError( + f"执行子进程已退出，退出码: {self._process.returncode}" + ) + + request_id = str(uuid.uuid4()) + message = { + "request_id": request_id, + "type": request_type, + "payload": payload, + } + + try: + self._process.stdin.write(json.dumps(message, ensure_ascii=False) + "\n") + self._process.stdin.flush() + except BrokenPipeError as exc: + self._teardown_worker() + raise WorkerSessionError("执行子进程通信中断") from exc + + effective_timeout = ( + self.request_timeout_seconds + if timeout_seconds is None + else timeout_seconds + ) + response_line = self._read_response_line(effective_timeout) + if not response_line: + if self._process.poll() is not None: + exit_code = self._process.returncode + self._teardown_worker() + raise WorkerSessionError(f"执行子进程已异常退出，退出码: {exit_code}") + raise WorkerSessionError("执行子进程未返回响应") + + try: + response = json.loads(response_line) + except json.JSONDecodeError as exc: + raise WorkerSessionError(f"执行子进程返回了无效JSON: {response_line}") from exc + + if response.get("request_id") != request_id: + raise WorkerSessionError("执行子进程响应 request_id 不匹配") + + if response.get("status") != "ok": + raise WorkerSessionError(response.get("error", "执行子进程返回未知错误")) + + return response.get("payload", {}) + + def _read_response_line(self, timeout_seconds: float) -> str: + assert self._process is not None and self._process.stdout is not None + + response_queue: queue.Queue = queue.Queue(maxsize=1) + + def _reader() -> None: + try: + response_queue.put((True, self._process.stdout.readline())) + except Exception as exc: + response_queue.put((False, exc)) + + thread = threading.Thread(target=_reader, daemon=True) + thread.start() + + try: + success, value = response_queue.get(timeout=timeout_seconds) + except queue.Empty as exc: + self._teardown_worker(force=True) + raise WorkerTimeoutError( + f"执行子进程在 {timeout_seconds:.1f} 秒内未响应，已终止当前会话" + ) from exc + + if success: + return value + + self._teardown_worker() + raise WorkerSessionError(f"读取执行子进程响应失败: {value}") + + def _teardown_worker(self, force: bool = False) -> None: + if self._process is not None and self._process.poll() is None: + self._process.terminate() + try: + self._process.wait(timeout=5) + except subprocess.TimeoutExpired: + self._process.kill() + self._process.wait(timeout=5) + + if self._stderr_handle is not None: + self._stderr_handle.close() + self._stderr_handle = None + + self._process = None + + def __del__(self): + self.close() diff --git a/utils/execution_worker.py b/utils/execution_worker.py new file mode 100644 index 0000000..5299502 --- /dev/null +++ b/utils/execution_worker.py @@ -0,0 +1,321 @@ +# -*- coding: utf-8 -*- +""" +Subprocess worker that hosts a single CodeExecutor instance for one analysis session. +""" + +import json +import os +import sys +import traceback +from pathlib import Path +from contextlib import redirect_stderr, redirect_stdout +from io import StringIO +from typing import Any, Dict, Iterable, Optional + +PROJECT_ROOT = os.path.abspath(os.path.join(os.path.dirname(__file__), "..")) +if PROJECT_ROOT not in sys.path: + sys.path.insert(0, PROJECT_ROOT) + + +class WorkerProtocolError(RuntimeError): + """Raised when the worker receives an invalid protocol message.""" + + +class FileAccessPolicy: + """Controls which files the worker may read and where it may write outputs.""" + + def __init__(self): + self.allowed_reads = set() + self.allowed_read_roots = set() + self.allowed_write_root = "" + + @staticmethod + def _normalize(path: Any) -> str: + if isinstance(path, Path): + path = str(path) + elif hasattr(path, "__fspath__"): + path = os.fspath(path) + elif not isinstance(path, str): + raise TypeError(f"不支持的路径类型: {type(path).__name__}") + return os.path.realpath(os.path.abspath(path)) + + def configure( + self, + allowed_reads: Iterable[Any], + allowed_write_root: Any, + allowed_read_roots: Optional[Iterable[Any]] = None, + ) -> None: + self.allowed_reads = { + self._normalize(path) for path in allowed_reads if path + } + explicit_roots = { + self._normalize(path) for path in (allowed_read_roots or []) if path + } + derived_roots = { + os.path.dirname(path) for path in self.allowed_reads + } + self.allowed_read_roots = explicit_roots | derived_roots + self.allowed_write_root = ( + self._normalize(allowed_write_root) if allowed_write_root else "" + ) + + def ensure_readable(self, path: Any) -> str: + normalized_path = self._normalize(path) + if normalized_path in self.allowed_reads: + return normalized_path + if self._is_within_read_roots(normalized_path): + return normalized_path + if self._is_within_write_root(normalized_path): + return normalized_path + raise PermissionError(f"禁止读取未授权文件: {normalized_path}") + + def ensure_writable(self, path: Any) -> str: + normalized_path = self._normalize(path) + if self._is_within_write_root(normalized_path): + return normalized_path + raise PermissionError(f"禁止写入会话目录之外的路径: {normalized_path}") + + def _is_within_write_root(self, normalized_path: str) -> bool: + if not self.allowed_write_root: + return False + return normalized_path == self.allowed_write_root or normalized_path.startswith( + self.allowed_write_root + os.sep + ) + + def _is_within_read_roots(self, normalized_path: str) -> bool: + for root in self.allowed_read_roots: + if normalized_path == root or normalized_path.startswith(root + os.sep): + return True + return False + + +def _write_message(message: Dict[str, Any]) -> None: + sys.stdout.write(json.dumps(message, ensure_ascii=False) + "\n") + sys.stdout.flush() + + +def _write_log(text: str) -> None: + if not text: + return + sys.stderr.write(text) + if not text.endswith("\n"): + sys.stderr.write("\n") + sys.stderr.flush() + + +class ExecutionWorker: + """JSON-line protocol wrapper around CodeExecutor.""" + + def __init__(self): + self.executor = None + self.access_policy = FileAccessPolicy() + self._patches_installed = False + + def handle_request(self, request: Dict[str, Any]) -> Dict[str, Any]: + request_id = request.get("request_id", "") + request_type = request.get("type") + payload = request.get("payload", {}) + + try: + if request_type == "ping": + return self._ok(request_id, {"alive": True}) + if request_type == "init_session": + return self._handle_init_session(request_id, payload) + if request_type == "execute_code": + self._require_executor() + return self._ok( + request_id, + self.executor.execute_code(payload.get("code", "")), + ) + if request_type == "set_variable": + self._require_executor() + self._handle_set_variable(payload["name"], payload["value"]) + return self._ok(request_id, {"set": True}) + if request_type == "get_environment_info": + self._require_executor() + return self._ok( + request_id, + {"environment_info": self.executor.get_environment_info()}, + ) + if request_type == "reset_environment": + self._require_executor() + self.executor.reset_environment() + return self._ok(request_id, {"reset": True}) + if request_type == "shutdown": + return self._ok(request_id, {"shutdown": True}) + + raise WorkerProtocolError(f"未知请求类型: {request_type}") + except Exception as exc: + return { + "request_id": request_id, + "status": "error", + "error": str(exc), + "traceback": traceback.format_exc(), + } + + def _handle_init_session( + self, request_id: str, payload: Dict[str, Any] + ) -> Dict[str, Any]: + output_dir = payload.get("output_dir") + if not output_dir: + raise WorkerProtocolError("init_session 缺少 output_dir") + + from utils.code_executor import CodeExecutor + + self.executor = CodeExecutor(output_dir) + self.access_policy.configure( + payload.get("variables", {}).get("allowed_files", []), + output_dir, + payload.get("variables", {}).get("allowed_read_roots", []), + ) + self._install_file_guards() + + for name, value in payload.get("variables", {}).items(): + self.executor.set_variable(name, value) + + return self._ok(request_id, {"initialized": True}) + + def _install_file_guards(self) -> None: + if self._patches_installed: + return + + import builtins + import matplotlib.figure + import matplotlib.pyplot as plt + import pandas as pd + + policy = self.access_policy + + original_open = builtins.open + original_read_csv = pd.read_csv + original_read_excel = pd.read_excel + original_to_csv = pd.DataFrame.to_csv + original_to_excel = pd.DataFrame.to_excel + original_plt_savefig = plt.savefig + original_figure_savefig = matplotlib.figure.Figure.savefig + + def guarded_open(file, mode="r", *args, **kwargs): + if isinstance(file, (str, Path)) or hasattr(file, "__fspath__"): + if any(flag in mode for flag in ("w", "a", "x", "+")): + policy.ensure_writable(file) + else: + policy.ensure_readable(file) + return original_open(file, mode, *args, **kwargs) + + def guarded_read_csv(filepath_or_buffer, *args, **kwargs): + if isinstance(filepath_or_buffer, (str, Path)) or hasattr( + filepath_or_buffer, "__fspath__" + ): + policy.ensure_readable(filepath_or_buffer) + return original_read_csv(filepath_or_buffer, *args, **kwargs) + + def guarded_read_excel(io, *args, **kwargs): + if isinstance(io, (str, Path)) or hasattr(io, "__fspath__"): + policy.ensure_readable(io) + return original_read_excel(io, *args, **kwargs) + + def guarded_to_csv(df, path_or_buf=None, *args, **kwargs): + if isinstance(path_or_buf, (str, Path)) or hasattr(path_or_buf, "__fspath__"): + policy.ensure_writable(path_or_buf) + return original_to_csv(df, path_or_buf, *args, **kwargs) + + def guarded_to_excel(df, excel_writer, *args, **kwargs): + if isinstance(excel_writer, (str, Path)) or hasattr(excel_writer, "__fspath__"): + policy.ensure_writable(excel_writer) + return original_to_excel(df, excel_writer, *args, **kwargs) + + def guarded_savefig(*args, **kwargs): + target = args[0] if args else kwargs.get("fname") + if target is not None and ( + isinstance(target, (str, Path)) or hasattr(target, "__fspath__") + ): + policy.ensure_writable(target) + return original_plt_savefig(*args, **kwargs) + + def guarded_figure_savefig(fig, fname, *args, **kwargs): + if isinstance(fname, (str, Path)) or hasattr(fname, "__fspath__"): + policy.ensure_writable(fname) + return original_figure_savefig(fig, fname, *args, **kwargs) + + builtins.open = guarded_open + pd.read_csv = guarded_read_csv + pd.read_excel = guarded_read_excel + pd.DataFrame.to_csv = guarded_to_csv + pd.DataFrame.to_excel = guarded_to_excel + plt.savefig = guarded_savefig + matplotlib.figure.Figure.savefig = guarded_figure_savefig + + self._patches_installed = True + + def _require_executor(self) -> None: + if self.executor is None: + raise WorkerProtocolError("执行会话尚未初始化") + + def _handle_set_variable(self, name: str, value: Any) -> None: + self.executor.set_variable(name, value) + + if name == "allowed_files": + self.access_policy.configure( + value, + self.access_policy.allowed_write_root, + self.access_policy.allowed_read_roots, + ) + elif name == "allowed_read_roots": + self.access_policy.configure( + self.access_policy.allowed_reads, + self.access_policy.allowed_write_root, + value, + ) + elif name == "session_output_dir": + self.access_policy.configure( + self.access_policy.allowed_reads, + value, + self.access_policy.allowed_read_roots, + ) + + @staticmethod + def _ok(request_id: str, payload: Dict[str, Any]) -> Dict[str, Any]: + return { + "request_id": request_id, + "status": "ok", + "payload": payload, + } + + +def main() -> int: + worker = ExecutionWorker() + + for raw_line in sys.stdin: + raw_line = raw_line.strip() + if not raw_line: + continue + + try: + request = json.loads(raw_line) + except json.JSONDecodeError as exc: + _write_message( + { + "request_id": "", + "status": "error", + "error": f"无效JSON请求: {exc}", + } + ) + continue + + captured_stdout = StringIO() + captured_stderr = StringIO() + with redirect_stdout(captured_stdout), redirect_stderr(captured_stderr): + response = worker.handle_request(request) + + _write_log(captured_stdout.getvalue()) + _write_log(captured_stderr.getvalue()) + _write_message(response) + + if request.get("type") == "shutdown" and response.get("status") == "ok": + return 0 + + return 0 + + +if __name__ == "__main__": + raise SystemExit(main()) diff --git a/utils/extract_code.py b/utils/extract_code.py new file mode 100644 index 0000000..bd2420f --- /dev/null +++ b/utils/extract_code.py @@ -0,0 +1,38 @@ +from typing import Optional +import yaml + + +def extract_code_from_response(response: str) -> Optional[str]: + """从LLM响应中提取代码""" + try: + # 尝试解析YAML + if '```yaml' in response: + start = response.find('```yaml') + 7 + end = response.find('```', start) + yaml_content = response[start:end].strip() + elif '```' in response: + start = response.find('```') + 3 + end = response.find('```', start) + yaml_content = response[start:end].strip() + else: + yaml_content = response.strip() + + yaml_data = yaml.safe_load(yaml_content) + if 'code' in yaml_data: + return yaml_data['code'] + except: + pass + + # 如果YAML解析失败，尝试提取```python代码块 + if '```python' in response: + start = response.find('```python') + 9 + end = response.find('```', start) + if end != -1: + return response[start:end].strip() + elif '```' in response: + start = response.find('```') + 3 + end = response.find('```', start) + if end != -1: + return response[start:end].strip() + + return None \ No newline at end of file diff --git a/utils/fallback_openai_client.py b/utils/fallback_openai_client.py new file mode 100644 index 0000000..2101f22 --- /dev/null +++ b/utils/fallback_openai_client.py @@ -0,0 +1,230 @@ +# -*- coding: utf-8 -*- +import asyncio +from typing import Optional, Any, Mapping, Dict +from openai import AsyncOpenAI, APIStatusError, APIConnectionError, APITimeoutError, APIError +from openai.types.chat import ChatCompletion + +class AsyncFallbackOpenAIClient: + """ + 一个支持备用 API 自动切换的异步 OpenAI 客户端。 + 当主 API 调用因特定错误（如内容过滤）失败时，会自动尝试使用备用 API。 + """ + def __init__( + self, + primary_api_key: str, + primary_base_url: str, + primary_model_name: str, + fallback_api_key: Optional[str] = None, + fallback_base_url: Optional[str] = None, + fallback_model_name: Optional[str] = None, + primary_client_args: Optional[Dict[str, Any]] = None, + fallback_client_args: Optional[Dict[str, Any]] = None, + content_filter_error_code: str = "1301", # 特定于 Zhipu 的内容过滤错误代码 + content_filter_error_field: str = "contentFilter", # 特定于 Zhipu 的内容过滤错误字段 + max_retries_primary: int = 1, # 主API重试次数 + max_retries_fallback: int = 1, # 备用API重试次数 + retry_delay_seconds: float = 1.0 # 重试延迟时间 + ): + """ + 初始化 AsyncFallbackOpenAIClient。 + + Args: + primary_api_key: 主 API 的密钥。 + primary_base_url: 主 API 的基础 URL。 + primary_model_name: 主 API 使用的模型名称。 + fallback_api_key: 备用 API 的密钥 (可选)。 + fallback_base_url: 备用 API 的基础 URL (可选)。 + fallback_model_name: 备用 API 使用的模型名称 (可选)。 + primary_client_args: 传递给主 AsyncOpenAI 客户端的其他参数。 + fallback_client_args: 传递给备用 AsyncOpenAI 客户端的其他参数。 + content_filter_error_code: 触发回退的内容过滤错误的特定错误代码。 + content_filter_error_field: 触发回退的内容过滤错误中存在的字段名。 + max_retries_primary: 主 API 失败时的最大重试次数。 + max_retries_fallback: 备用 API 失败时的最大重试次数。 + retry_delay_seconds: 重试前的延迟时间（秒）。 + """ + if not primary_api_key or not primary_base_url: + raise ValueError("主 API 密钥和基础 URL 不能为空。") + + _primary_args = primary_client_args or {} + self.primary_client = AsyncOpenAI(api_key=primary_api_key, base_url=primary_base_url, **_primary_args) + self.primary_model_name = primary_model_name + + self.fallback_client: Optional[AsyncOpenAI] = None + self.fallback_model_name: Optional[str] = None + if fallback_api_key and fallback_base_url and fallback_model_name: + _fallback_args = fallback_client_args or {} + self.fallback_client = AsyncOpenAI(api_key=fallback_api_key, base_url=fallback_base_url, **_fallback_args) + self.fallback_model_name = fallback_model_name + else: + print("⚠️ 警告: 未完全配置备用 API 客户端。如果主 API 失败，将无法进行回退。") + + self.content_filter_error_code = content_filter_error_code + self.content_filter_error_field = content_filter_error_field + self.max_retries_primary = max_retries_primary + self.max_retries_fallback = max_retries_fallback + self.retry_delay_seconds = retry_delay_seconds + self._closed = False + + async def _attempt_api_call( + self, + client: AsyncOpenAI, + model_name: str, + messages: list[Mapping[str, Any]], + max_retries: int, + api_name: str, + **kwargs: Any + ) -> ChatCompletion: + """ + 尝试调用指定的 OpenAI API 客户端，并进行重试。 + """ + last_exception = None + for attempt in range(max_retries + 1): + try: + # print(f"尝试使用 {api_name} API ({client.base_url}) 模型: {kwargs.get('model', model_name)}, 第 {attempt + 1} 次尝试") + completion = await client.chat.completions.create( + model=kwargs.pop('model', model_name), + messages=messages, + **kwargs + ) + return completion + except (APIConnectionError, APITimeoutError) as e: # 通常可以重试的网络错误 + last_exception = e + print(f"⚠️ {api_name} API 调用时发生可重试错误 ({type(e).__name__}): {e}. 尝试次数 {attempt + 1}/{max_retries + 1}") + if attempt < max_retries: + await asyncio.sleep(self.retry_delay_seconds * (attempt + 1)) # 增加延迟 + else: + print(f"❌ {api_name} API 在达到最大重试次数后仍然失败。") + except APIStatusError as e: # API 返回的特定状态码错误 + is_content_filter_error = False + if e.status_code == 400: + try: + error_json = e.response.json() + error_details = error_json.get("error", {}) + if (error_details.get("code") == self.content_filter_error_code and + self.content_filter_error_field in error_json): + is_content_filter_error = True + except Exception: + pass # 解析错误响应失败，不认为是内容过滤错误 + + if is_content_filter_error and api_name == "主": # 如果是主 API 的内容过滤错误，则直接抛出以便回退 + raise e + + last_exception = e + print(f"⚠️ {api_name} API 调用时发生 APIStatusError ({e.status_code}): {e}. 尝试次数 {attempt + 1}/{max_retries + 1}") + if attempt < max_retries: + await asyncio.sleep(self.retry_delay_seconds * (attempt + 1)) + else: + print(f"❌ {api_name} API 在达到最大重试次数后仍然失败 (APIStatusError)。") + except APIError as e: # 其他不可轻易重试的 OpenAI 错误 + last_exception = e + print(f"❌ {api_name} API 调用时发生不可重试错误 ({type(e).__name__}): {e}") + break # 不再重试此类错误 + + if last_exception: + raise last_exception + raise RuntimeError(f"{api_name} API 调用意外失败。") # 理论上不应到达这里 + + async def chat_completions_create( + self, + messages: list[Mapping[str, Any]], + **kwargs: Any # 用于传递其他 OpenAI 参数，如 max_tokens, temperature 等。 + ) -> ChatCompletion: + """ + 使用主 API 创建聊天补全，如果发生特定内容过滤错误或主 API 调用失败，则回退到备用 API。 + 支持对主 API 和备用 API 的可重试错误进行重试。 + + Args: + messages: OpenAI API 的消息列表。 + **kwargs: 传递给 OpenAI API 调用的其他参数。 + + Returns: + ChatCompletion 对象。 + + Raises: + APIError: 如果主 API 和备用 API (如果尝试) 都返回 API 错误。 + RuntimeError: 如果客户端已关闭。 + """ + if self._closed: + raise RuntimeError("客户端已关闭。") + + try: + completion = await self._attempt_api_call( + client=self.primary_client, + model_name=self.primary_model_name, + messages=messages, + max_retries=self.max_retries_primary, + api_name="主", + **kwargs.copy() + ) + return completion + except APIStatusError as e_primary: + is_content_filter_error = False + if e_primary.status_code == 400: + try: + error_json = e_primary.response.json() + error_details = error_json.get("error", {}) + if (error_details.get("code") == self.content_filter_error_code and + self.content_filter_error_field in error_json): + is_content_filter_error = True + except Exception: + pass + + if is_content_filter_error and self.fallback_client and self.fallback_model_name: + print(f"ℹ️ 主 API 内容过滤错误 ({e_primary.status_code})。尝试切换到备用 API ({self.fallback_client.base_url})...") + try: + fallback_completion = await self._attempt_api_call( + client=self.fallback_client, + model_name=self.fallback_model_name, + messages=messages, + max_retries=self.max_retries_fallback, + api_name="备用", + **kwargs.copy() + ) + print(f"✅ 备用 API 调用成功。") + return fallback_completion + except APIError as e_fallback: + print(f"❌ 备用 API 调用最终失败: {type(e_fallback).__name__} - {e_fallback}") + raise e_fallback + else: + if not (self.fallback_client and self.fallback_model_name and is_content_filter_error): + # 如果不是内容过滤错误，或者没有可用的备用API，则记录主API的原始错误 + print(f"ℹ️ 主 API 错误 ({type(e_primary).__name__}: {e_primary}), 且不满足备用条件或备用API未配置。") + raise e_primary + except APIError as e_primary_other: + print(f"❌ 主 API 调用最终失败 (非内容过滤，错误类型: {type(e_primary_other).__name__}): {e_primary_other}") + if self.fallback_client and self.fallback_model_name: + print(f"ℹ️ 主 API 失败，尝试切换到备用 API ({self.fallback_client.base_url})...") + try: + fallback_completion = await self._attempt_api_call( + client=self.fallback_client, + model_name=self.fallback_model_name, + messages=messages, + max_retries=self.max_retries_fallback, + api_name="备用", + **kwargs.copy() + ) + print(f"✅ 备用 API 调用成功。") + return fallback_completion + except APIError as e_fallback_after_primary_fail: + print(f"❌ 备用 API 在主 API 失败后也调用失败: {type(e_fallback_after_primary_fail).__name__} - {e_fallback_after_primary_fail}") + raise e_fallback_after_primary_fail + else: + raise e_primary_other + + async def close(self): + """异步关闭主客户端和备用客户端 (如果存在)。""" + if not self._closed: + await self.primary_client.close() + if self.fallback_client: + await self.fallback_client.close() + self._closed = True + # print("AsyncFallbackOpenAIClient 已关闭。") + + async def __aenter__(self): + if self._closed: + raise RuntimeError("AsyncFallbackOpenAIClient 不能在关闭后重新进入。请创建一个新实例。") + return self + + async def __aexit__(self, exc_type, exc_val, exc_tb): + await self.close() diff --git a/utils/format_execution_result.py b/utils/format_execution_result.py new file mode 100644 index 0000000..7706d92 --- /dev/null +++ b/utils/format_execution_result.py @@ -0,0 +1,25 @@ + +from typing import Any, Dict + + +def format_execution_result(result: Dict[str, Any]) -> str: + """格式化执行结果为用户可读的反馈""" + feedback = [] + + if result['success']: + feedback.append("✅ 代码执行成功") + + if result['output']: + feedback.append(f"📊 输出结果：\n{result['output']}") + + if result.get('variables'): + feedback.append("📋 新生成的变量：") + for var_name, var_info in result['variables'].items(): + feedback.append(f" - {var_name}: {var_info}") + else: + feedback.append("❌ 代码执行失败") + feedback.append(f"错误信息: {result['error']}") + if result['output']: + feedback.append(f"部分输出: {result['output']}") + + return "\n".join(feedback) diff --git a/utils/llm_helper.py b/utils/llm_helper.py new file mode 100644 index 0000000..89cc94e --- /dev/null +++ b/utils/llm_helper.py @@ -0,0 +1,91 @@ +# -*- coding: utf-8 -*- +""" +LLM调用辅助模块 +""" + +import asyncio +import yaml +from config.llm_config import LLMConfig +from utils.fallback_openai_client import AsyncFallbackOpenAIClient + + +class LLMCallError(RuntimeError): + """Raised when the configured LLM backend cannot complete a request.""" + + +class LLMHelper: + """LLM调用辅助类，支持同步和异步调用""" + + def __init__(self, config: LLMConfig = None): + self.config = config or LLMConfig() + self.config.validate() + self.client = AsyncFallbackOpenAIClient( + primary_api_key=self.config.api_key, + primary_base_url=self.config.base_url, + primary_model_name=self.config.model + ) + + async def async_call(self, prompt: str, system_prompt: str = None, max_tokens: int = None, temperature: float = None) -> str: + """异步调用LLM""" + messages = [] + if system_prompt: + messages.append({"role": "system", "content": system_prompt}) + messages.append({"role": "user", "content": prompt}) + + kwargs = {} + if max_tokens is not None: + kwargs['max_tokens'] = max_tokens + else: + kwargs['max_tokens'] = self.config.max_tokens + + if temperature is not None: + kwargs['temperature'] = temperature + else: + kwargs['temperature'] = self.config.temperature + + try: + response = await self.client.chat_completions_create( + messages=messages, + **kwargs + ) + return response.choices[0].message.content + except Exception as e: + raise LLMCallError(f"LLM调用失败: {e}") from e + + def call(self, prompt: str, system_prompt: str = None, max_tokens: int = None, temperature: float = None) -> str: + """同步调用LLM""" + try: + loop = asyncio.get_event_loop() + except RuntimeError: + loop = asyncio.new_event_loop() + asyncio.set_event_loop(loop) + + import nest_asyncio + nest_asyncio.apply() + + return loop.run_until_complete(self.async_call(prompt, system_prompt, max_tokens, temperature)) + + def parse_yaml_response(self, response: str) -> dict: + """解析YAML格式的响应""" + try: + # 提取```yaml和```之间的内容 + if '```yaml' in response: + start = response.find('```yaml') + 7 + end = response.find('```', start) + yaml_content = response[start:end].strip() + elif '```' in response: + start = response.find('```') + 3 + end = response.find('```', start) + yaml_content = response[start:end].strip() + else: + yaml_content = response.strip() + + return yaml.safe_load(yaml_content) + except Exception as e: + print(f"YAML解析失败: {e}") + print(f"原始响应: {response}") + return {} + + async def close(self): + """关闭客户端""" + await self.client.close() diff --git a/webapp/__init__.py b/webapp/__init__.py new file mode 100644 index 0000000..68e11ed --- /dev/null +++ b/webapp/__init__.py @@ -0,0 +1,4 @@ +# -*- coding: utf-8 -*- +""" +Web application package for the data analysis platform. +""" diff --git a/webapp/api.py b/webapp/api.py new file mode 100644 index 0000000..df1c0e1 --- /dev/null +++ b/webapp/api.py @@ -0,0 +1,242 @@ +# -*- coding: utf-8 -*- +""" +FastAPI application for the data analysis platform. +""" + +import os +import re +import uuid +from typing import List, Optional + +from fastapi import FastAPI, File, Form, HTTPException, Query, UploadFile +from fastapi.responses import FileResponse, HTMLResponse +from fastapi.staticfiles import StaticFiles +from pydantic import BaseModel, Field + +from webapp.session_manager import SessionManager +from webapp.storage import Storage, utcnow_iso +from webapp.task_runner import TaskRunner + + +BASE_DIR = os.path.abspath(os.path.join(os.path.dirname(__file__), "..")) +RUNTIME_DIR = os.path.join(BASE_DIR, "runtime") +UPLOADS_DIR = os.path.join(RUNTIME_DIR, "uploads") +OUTPUTS_DIR = os.path.join(BASE_DIR, "outputs") +DB_PATH = os.path.join(RUNTIME_DIR, "analysis_platform.db") + +os.makedirs(UPLOADS_DIR, exist_ok=True) +os.makedirs(OUTPUTS_DIR, exist_ok=True) + +storage = Storage(DB_PATH) +session_manager = SessionManager(OUTPUTS_DIR) +task_runner = TaskRunner( + storage=storage, + uploads_dir=UPLOADS_DIR, + outputs_dir=OUTPUTS_DIR, + session_manager=session_manager, + max_workers=2, +) + +app = FastAPI(title="Data Analysis Platform API") +STATIC_DIR = os.path.join(os.path.dirname(__file__), "static") +app.mount("/static", StaticFiles(directory=STATIC_DIR), name="static") + + +class CreateSessionRequest(BaseModel): + user_id: str = Field(..., min_length=1) + title: str = Field(..., min_length=1) + query: str = Field(..., min_length=1) + file_ids: List[str] + template_file_id: Optional[str] = None + + +class CreateTopicRequest(BaseModel): + user_id: str = Field(..., min_length=1) + query: str = Field(..., min_length=1) + + +def sanitize_filename(filename: str) -> str: + cleaned = re.sub(r"[^A-Za-z0-9._-]+", "_", filename).strip("._") + return cleaned or "upload.bin" + + +def ensure_session_access(session_id: str, user_id: str) -> dict: + session = storage.get_session(session_id, user_id) + if not session: + raise HTTPException(status_code=404, detail="Session not found") + return session + + +def ensure_task_access(task_id: str, user_id: str) -> dict: + task = storage.get_task(task_id, user_id) + if not task: + raise HTTPException(status_code=404, detail="Task not found") + return task + + +@app.get("/health") +def health(): + return {"status": "ok"} + + +@app.get("/", response_class=HTMLResponse) +def index(): + index_path = os.path.join(STATIC_DIR, "index.html") + with open(index_path, "r", encoding="utf-8") as f: + return HTMLResponse(f.read()) + + +@app.post("/files/upload") +async def upload_files( + user_id: str = Form(...), + files: List[UploadFile] = File(...), +): + saved = [] + user_dir = os.path.join(UPLOADS_DIR, user_id) + os.makedirs(user_dir, exist_ok=True) + + for upload in files: + safe_name = sanitize_filename(upload.filename or "upload.bin") + stored_path = os.path.join(user_dir, f"{uuid.uuid4()}_{safe_name}") + with open(stored_path, "wb") as f: + while True: + chunk = await upload.read(1024 * 1024) + if not chunk: + break + f.write(chunk) + saved.append(storage.create_uploaded_file(user_id, upload.filename or safe_name, stored_path)) + + return {"files": saved} + + +@app.get("/files") +def list_files(user_id: str = Query(...)): + return {"files": storage.list_all_uploaded_files(user_id)} + + +@app.post("/sessions") +def create_session(request: CreateSessionRequest): + if not storage.list_uploaded_files(request.file_ids, request.user_id): + raise HTTPException(status_code=400, detail="No valid files found for session") + + session = storage.create_session( + user_id=request.user_id, + title=request.title, + uploaded_file_ids=request.file_ids, + template_file_id=request.template_file_id, + ) + task = storage.create_task( + session_id=session["id"], + user_id=request.user_id, + query=request.query, + uploaded_file_ids=request.file_ids, + template_file_id=request.template_file_id, + ) + task_runner.submit(task["id"], request.user_id) + return {"session": session, "task": task} + + +@app.get("/sessions") +def list_sessions(user_id: str = Query(...)): + return {"sessions": storage.list_sessions(user_id)} + + +@app.get("/sessions/{session_id}") +def get_session(session_id: str, user_id: str = Query(...)): + session = ensure_session_access(session_id, user_id) + tasks = storage.list_session_tasks(session_id, user_id) + return {"session": session, "tasks": tasks} + + +@app.post("/sessions/{session_id}/topics") +def create_followup_topic(session_id: str, request: CreateTopicRequest): + session = ensure_session_access(session_id, request.user_id) + if session["status"] == "closed": + raise HTTPException(status_code=400, detail="Session is closed") + + task = storage.create_task( + session_id=session_id, + user_id=request.user_id, + query=request.query, + uploaded_file_ids=session["uploaded_file_ids"], + template_file_id=session.get("template_file_id"), + ) + task_runner.submit(task["id"], request.user_id) + return {"session": session, "task": task} + + +@app.post("/sessions/{session_id}/close") +def close_session(session_id: str, user_id: str = Query(...)): + session = ensure_session_access(session_id, user_id) + storage.update_session(session_id, status="closed", closed_at=utcnow_iso()) + session_manager.close(session_id) + return {"session": storage.get_session(session_id, user_id)} + + +@app.get("/tasks") +def list_tasks(user_id: str = Query(...)): + return {"tasks": storage.list_tasks(user_id)} + + +@app.get("/tasks/{task_id}") +def get_task(task_id: str, user_id: str = Query(...)): + task = ensure_task_access(task_id, user_id) + return {"task": task} + + +@app.get("/tasks/{task_id}/report") +def get_task_report(task_id: str, user_id: str = Query(...)): + task = ensure_task_access(task_id, user_id) + report_path = task.get("report_file_path") + if not report_path or not os.path.exists(report_path): + raise HTTPException(status_code=404, detail="Report not available") + return FileResponse(report_path, media_type="text/markdown", filename=os.path.basename(report_path)) + + +@app.get("/tasks/{task_id}/report/content") +def get_task_report_content(task_id: str, user_id: str = Query(...)): + task = ensure_task_access(task_id, user_id) + report_path = task.get("report_file_path") + if not report_path or not os.path.exists(report_path): + raise HTTPException(status_code=404, detail="Report not available") + with open(report_path, "r", encoding="utf-8") as f: + return {"content": f.read(), "filename": os.path.basename(report_path)} + + +@app.get("/tasks/{task_id}/artifacts") +def list_task_artifacts(task_id: str, user_id: str = Query(...)): + task = ensure_task_access(task_id, user_id) + session_output_dir = task.get("session_output_dir") + if not session_output_dir or not os.path.isdir(session_output_dir): + return {"artifacts": []} + + artifacts = [] + for name in sorted(os.listdir(session_output_dir)): + path = os.path.join(session_output_dir, name) + if not os.path.isfile(path): + continue + artifacts.append( + { + "name": name, + "size": os.path.getsize(path), + "is_image": name.lower().endswith((".png", ".jpg", ".jpeg", ".gif", ".webp")), + "url": f"/tasks/{task_id}/artifacts/{name}?user_id={user_id}", + } + ) + return {"artifacts": artifacts} + + +@app.get("/tasks/{task_id}/artifacts/{artifact_name}") +def get_artifact(task_id: str, artifact_name: str, user_id: str = Query(...)): + task = ensure_task_access(task_id, user_id) + session_output_dir = task.get("session_output_dir") + if not session_output_dir: + raise HTTPException(status_code=404, detail="Artifact directory not available") + + artifact_path = os.path.realpath(os.path.join(session_output_dir, artifact_name)) + session_root = os.path.realpath(session_output_dir) + if artifact_path != session_root and not artifact_path.startswith(session_root + os.sep): + raise HTTPException(status_code=400, detail="Invalid artifact path") + if not os.path.exists(artifact_path): + raise HTTPException(status_code=404, detail="Artifact not found") + return FileResponse(artifact_path, filename=os.path.basename(artifact_path)) diff --git a/webapp/session_manager.py b/webapp/session_manager.py new file mode 100644 index 0000000..956402e --- /dev/null +++ b/webapp/session_manager.py @@ -0,0 +1,66 @@ +# -*- coding: utf-8 -*- +""" +In-memory registry for long-lived analysis sessions. +""" + +import os +import threading +from dataclasses import dataclass, field +from typing import Dict, Optional + +from config.llm_config import LLMConfig +from data_analysis_agent import DataAnalysisAgent + + +@dataclass +class RuntimeSession: + session_id: str + user_id: str + session_output_dir: str + uploaded_files: list[str] + template_path: Optional[str] + agent: DataAnalysisAgent + initialized: bool = False + lock: threading.Lock = field(default_factory=threading.Lock) + + +class SessionManager: + """Keeps session-scoped agents alive across follow-up topics.""" + + def __init__(self, outputs_dir: str): + self.outputs_dir = os.path.abspath(outputs_dir) + self._sessions: Dict[str, RuntimeSession] = {} + self._lock = threading.Lock() + + def get_or_create( + self, + session_id: str, + user_id: str, + session_output_dir: str, + uploaded_files: list[str], + template_path: Optional[str], + ) -> RuntimeSession: + with self._lock: + runtime = self._sessions.get(session_id) + if runtime is None: + runtime = RuntimeSession( + session_id=session_id, + user_id=user_id, + session_output_dir=session_output_dir, + uploaded_files=uploaded_files, + template_path=template_path, + agent=DataAnalysisAgent( + llm_config=LLMConfig(), + output_dir=self.outputs_dir, + max_rounds=20, + force_max_rounds=False, + ), + ) + self._sessions[session_id] = runtime + return runtime + + def close(self, session_id: str) -> None: + with self._lock: + runtime = self._sessions.pop(session_id, None) + if runtime: + runtime.agent.close_session() diff --git a/webapp/static/app.js b/webapp/static/app.js new file mode 100644 index 0000000..63cd861 --- /dev/null +++ b/webapp/static/app.js @@ -0,0 +1,299 @@ +const state = { + userId: null, + files: [], + sessions: [], + currentSessionId: null, + currentTaskId: null, + pollTimer: null, +}; + +function ensureUserId() { + const key = "vibe_data_ana_user_id"; + let userId = localStorage.getItem(key); + if (!userId) { + userId = `guest_${crypto.randomUUID()}`; + localStorage.setItem(key, userId); + } + state.userId = userId; + document.getElementById("user-id").textContent = userId; +} + +async function api(path, options = {}) { + const response = await fetch(path, options); + const text = await response.text(); + let data = {}; + try { + data = text ? JSON.parse(text) : {}; + } catch { + data = { raw: text }; + } + if (!response.ok) { + throw new Error(data.detail || data.error || response.statusText); + } + return data; +} + +function setText(id, value) { + document.getElementById(id).textContent = value || ""; +} + +function renderFiles() { + const fileList = document.getElementById("file-list"); + const picker = document.getElementById("session-file-picker"); + fileList.innerHTML = ""; + picker.innerHTML = ""; + + if (!state.files.length) { + fileList.innerHTML = '
还没有上传文件。
'; + picker.innerHTML = '
先上传文件后才能创建会话。
'; + return; + } + + state.files.forEach((file) => { + const item = document.createElement("div"); + item.className = "file-item"; + item.innerHTML = `${file.original_name}
${file.id}
`; + fileList.appendChild(item); + + const label = document.createElement("label"); + label.className = "checkbox-item"; + label.innerHTML = ` + + ${file.original_name} + `; + picker.appendChild(label); + }); +} + +function statusBadge(status) { + return `${status}`; +} + +function renderSessions() { + const container = document.getElementById("session-list"); + container.innerHTML = ""; + if (!state.sessions.length) { + container.innerHTML = '
暂无会话。
'; + return; + } + + state.sessions.forEach((session) => { + const card = document.createElement("button"); + card.type = "button"; + card.className = `session-card ${session.id === state.currentSessionId ? "active" : ""}`; + card.innerHTML = ` +
${session.title}
+
${session.id}
+
${statusBadge(session.status)}
+ `; + card.onclick = () => loadSessionDetail(session.id); + container.appendChild(card); + }); +} + +function renderTasks(tasks) { + const container = document.getElementById("task-list"); + container.innerHTML = ""; + if (!tasks.length) { + container.innerHTML = '
当前会话还没有专题任务。
'; + return; + } + + tasks.forEach((task) => { + const card = document.createElement("button"); + card.type = "button"; + card.className = `task-card ${task.id === state.currentTaskId ? "active" : ""}`; + card.innerHTML = ` +
${task.query}
+
${task.created_at}
+
${statusBadge(task.status)}
+ `; + card.onclick = () => loadTaskReport(task.id); + container.appendChild(card); + }); +} + +async function refreshFiles() { + const data = await api(`/files?user_id=${encodeURIComponent(state.userId)}`); + state.files = data.files || []; + renderFiles(); +} + +async function refreshSessions(selectSessionId = null) { + const data = await api(`/sessions?user_id=${encodeURIComponent(state.userId)}`); + state.sessions = data.sessions || []; + renderSessions(); + if (selectSessionId) { + await loadSessionDetail(selectSessionId); + } else if (state.currentSessionId) { + const exists = state.sessions.some((session) => session.id === state.currentSessionId); + if (exists) { + await loadSessionDetail(state.currentSessionId, false); + } + } +} + +async function loadSessionDetail(sessionId, renderReport = true) { + const data = await api(`/sessions/${sessionId}?user_id=${encodeURIComponent(state.userId)}`); + state.currentSessionId = sessionId; + document.getElementById("detail-title").textContent = data.session.title; + document.getElementById("detail-meta").textContent = `${data.session.id} · ${data.session.status}`; + renderSessions(); + renderTasks(data.tasks || []); + + const latestDoneTask = (data.tasks || []).slice().reverse().find((task) => task.status === "succeeded"); + if (renderReport && latestDoneTask) { + await loadTaskReport(latestDoneTask.id); + } else if (!latestDoneTask) { + setText("report-title", "暂无已完成专题"); + setText("report-content", "当前会话还没有可展示的报告。"); + document.getElementById("artifact-gallery").innerHTML = ""; + } +} + +async function loadTaskReport(taskId) { + state.currentTaskId = taskId; + renderSessions(); + const taskData = await api(`/tasks/${taskId}?user_id=${encodeURIComponent(state.userId)}`); + setText("report-title", taskData.task.query); + + if (taskData.task.status !== "succeeded") { + setText("report-content", `当前任务状态为 ${taskData.task.status}。\n错误信息：${taskData.task.error_message || "暂无"}`); + document.getElementById("artifact-gallery").innerHTML = ""; + return; + } + + const reportData = await api(`/tasks/${taskId}/report/content?user_id=${encodeURIComponent(state.userId)}`); + setText("report-content", reportData.content || ""); + + const artifactData = await api(`/tasks/${taskId}/artifacts?user_id=${encodeURIComponent(state.userId)}`); + renderArtifacts(artifactData.artifacts || []); +} + +function renderArtifacts(artifacts) { + const gallery = document.getElementById("artifact-gallery"); + gallery.innerHTML = ""; + const images = artifacts.filter((item) => item.is_image); + if (!images.length) { + gallery.innerHTML = '
当前任务没有图片产物。
'; + return; + } + images.forEach((artifact) => { + const card = document.createElement("div"); + card.className = "artifact-card"; + card.innerHTML = ` + ${artifact.name} + + `; + gallery.appendChild(card); + }); +} + +async function handleUpload(event) { + event.preventDefault(); + const input = document.getElementById("upload-input"); + if (!input.files.length) { + setText("upload-status", "请选择至少一个文件。"); + return; + } + + const formData = new FormData(); + formData.append("user_id", state.userId); + Array.from(input.files).forEach((file) => formData.append("files", file)); + setText("upload-status", "上传中..."); + await api("/files/upload", { method: "POST", body: formData }); + setText("upload-status", "文件上传完成。"); + input.value = ""; + await refreshFiles(); +} + +async function handleCreateSession(event) { + event.preventDefault(); + const checked = Array.from(document.querySelectorAll("#session-file-picker input:checked")); + const fileIds = checked.map((item) => item.value); + if (!fileIds.length) { + setText("session-status", "请至少选择一个文件。"); + return; + } + + const payload = { + user_id: state.userId, + title: document.getElementById("session-title").value.trim(), + query: document.getElementById("session-query").value.trim(), + file_ids: fileIds, + }; + setText("session-status", "会话创建中..."); + const data = await api("/sessions", { + method: "POST", + headers: { "Content-Type": "application/json" }, + body: JSON.stringify(payload), + }); + setText("session-status", "会话已创建，正在执行首个专题。"); + document.getElementById("session-form").reset(); + await refreshSessions(data.session.id); +} + +async function handleFollowup() { + if (!state.currentSessionId) { + setText("detail-meta", "请先选择一个会话。"); + return; + } + const query = document.getElementById("followup-query").value.trim(); + if (!query) { + return; + } + await api(`/sessions/${state.currentSessionId}/topics`, { + method: "POST", + headers: { "Content-Type": "application/json" }, + body: JSON.stringify({ user_id: state.userId, query }), + }); + document.getElementById("followup-query").value = ""; + await refreshSessions(state.currentSessionId); +} + +async function handleCloseSession() { + if (!state.currentSessionId) { + return; + } + await api(`/sessions/${state.currentSessionId}/close?user_id=${encodeURIComponent(state.userId)}`, { + method: "POST", + }); + await refreshSessions(state.currentSessionId); +} + +function startPolling() { + if (state.pollTimer) { + clearInterval(state.pollTimer); + } + state.pollTimer = setInterval(() => { + refreshSessions().catch((error) => console.error(error)); + }, 8000); +} + +async function bootstrap() { + ensureUserId(); + document.getElementById("upload-form").addEventListener("submit", (event) => { + handleUpload(event).catch((error) => setText("upload-status", error.message)); + }); + document.getElementById("session-form").addEventListener("submit", (event) => { + handleCreateSession(event).catch((error) => setText("session-status", error.message)); + }); + document.getElementById("submit-followup").onclick = () => { + handleFollowup().catch((error) => setText("detail-meta", error.message)); + }; + document.getElementById("close-session").onclick = () => { + handleCloseSession().catch((error) => setText("detail-meta", error.message)); + }; + document.getElementById("refresh-sessions").onclick = () => { + refreshSessions().catch((error) => console.error(error)); + }; + + await refreshFiles(); + await refreshSessions(); + startPolling(); +} + +bootstrap().catch((error) => { + console.error(error); + setText("detail-meta", error.message); +}); diff --git a/webapp/static/index.html b/webapp/static/index.html new file mode 100644 index 0000000..8cec2cb --- /dev/null +++ b/webapp/static/index.html @@ -0,0 +1,88 @@ + + + + + + Vibe Data Analysis + + + +
+
+
+

Vibe Data Analysis

+

在线数据分析会话

+

+ 上传文件，发起分析，会话结束后继续追问新的专题，不中断当前上下文。 +

+
+
+ 当前访客标识 + +
+
+ +
+
+

1. 上传文件

+
+ + +
+
+
+
+ +
+

2. 新建分析会话

+
+ + +
+ +
+
+
+
+ +
+ + +
+
+
+

未选择会话

+

选择左侧会话查看分析结果与后续专题。

+
+ +
+ +
+ + +
+ +
+
+

专题任务

+
+
+
+

报告展示

+
暂无报告
+ 
选择一个已完成任务查看报告。
+ +
+
+
+
+
+ + + diff --git a/webapp/static/style.css b/webapp/static/style.css new file mode 100644 index 0000000..7c415e1 --- /dev/null +++ b/webapp/static/style.css @@ -0,0 +1,278 @@ +:root { + --bg: #f4efe7; + --panel: #fffaf2; + --line: #d8cdbd; + --text: #1f1a17; + --muted: #6e645a; + --accent: #b04a2f; + --accent-soft: #f2d5c4; + --success: #2f7d62; + --warning: #aa6a1f; +} + +* { + box-sizing: border-box; +} + +body { + margin: 0; + font-family: "IBM Plex Sans", "Noto Sans SC", sans-serif; + color: var(--text); + background: + radial-gradient(circle at top left, #fff7ec 0, transparent 28rem), + linear-gradient(180deg, #efe5d7 0%, var(--bg) 100%); +} + +.app-shell { + max-width: 1440px; + margin: 0 auto; + padding: 24px; +} + +.hero, +.panel, +.content, +.sidebar { + border: 1px solid var(--line); + background: rgba(255, 250, 242, 0.96); + backdrop-filter: blur(10px); + border-radius: 20px; + box-shadow: 0 12px 40px rgba(93, 67, 39, 0.08); +} + +.hero { + display: flex; + justify-content: space-between; + gap: 24px; + padding: 24px 28px; + margin-bottom: 20px; +} + +.eyebrow { + margin: 0 0 10px; + color: var(--accent); + text-transform: uppercase; + letter-spacing: 0.12em; + font-size: 12px; +} + +h1, +h2, +h3, +p { + margin-top: 0; +} + +.subtle, +.hint { + color: var(--muted); +} + +.identity-card { + min-width: 220px; + padding: 16px; + border-radius: 16px; + background: linear-gradient(135deg, var(--accent-soft), #f8e7dc); + display: flex; + flex-direction: column; + gap: 8px; +} + +.panel-grid, +.layout, +.tasks-area { + display: grid; + gap: 20px; +} + +.panel-grid { + grid-template-columns: repeat(2, minmax(0, 1fr)); + margin-bottom: 20px; +} + +.layout { + grid-template-columns: 340px minmax(0, 1fr); +} + +.tasks-area { + grid-template-columns: 320px minmax(0, 1fr); +} + +.panel, +.content, +.sidebar { + padding: 20px; +} + +.stack-form { + display: grid; + gap: 12px; +} + +input, +textarea, +button { + font: inherit; +} + +input, +textarea { + width: 100%; + padding: 12px 14px; + border-radius: 12px; + border: 1px solid var(--line); + background: #fffdf9; +} + +button { + border: 0; + border-radius: 999px; + padding: 12px 18px; + background: var(--accent); + color: #fff; + cursor: pointer; + transition: transform 120ms ease, opacity 120ms ease; +} + +button:hover { + transform: translateY(-1px); + opacity: 0.95; +} + +button.ghost { + background: transparent; + color: var(--accent); + border: 1px solid var(--accent-soft); +} + +.file-list, +.checkbox-list, +.session-list, +.task-list, +.artifact-gallery { + display: grid; + gap: 10px; +} + +.file-item, +.session-card, +.task-card, +.artifact-card { + padding: 12px 14px; + border-radius: 14px; + border: 1px solid var(--line); + background: #fffdf8; +} + +.checkbox-item { + display: flex; + align-items: center; + gap: 10px; + padding: 10px 12px; + border-radius: 12px; + border: 1px solid var(--line); + background: #fffdf8; +} + +.sidebar-header, +.content-header { + display: flex; + justify-content: space-between; + align-items: start; + gap: 16px; +} + +.followup-box { + margin: 20px 0; + display: grid; + gap: 12px; +} + +.session-card.active, +.task-card.active { + border-color: var(--accent); + background: #fff3eb; +} + +.status { + display: inline-flex; + padding: 4px 10px; + border-radius: 999px; + font-size: 12px; + font-weight: 600; +} + +.status.queued { + background: #f1ead7; + color: #7b6114; +} + +.status.running { + background: #e6edf9; + color: #1e5dab; +} + +.status.succeeded, +.status.open { + background: #dff1ea; + color: var(--success); +} + +.status.failed, +.status.closed { + background: #f8dfda; + color: #a03723; +} + +.report-title { + margin-bottom: 10px; + color: var(--muted); +} + +.report-content { + min-height: 360px; + max-height: 720px; + overflow: auto; + padding: 16px; + border-radius: 16px; + background: #1d1a18; + color: #f8f2ea; + line-height: 1.6; + white-space: pre-wrap; +} + +.artifact-gallery { + margin-top: 16px; + grid-template-columns: repeat(auto-fill, minmax(220px, 1fr)); +} + +.artifact-card img { + width: 100%; + height: 180px; + object-fit: cover; + border-radius: 12px; + background: #ede3d7; +} + +.artifact-card a { + color: var(--accent); + text-decoration: none; +} + +.empty { + color: var(--muted); + font-style: italic; +} + +@media (max-width: 1024px) { + .panel-grid, + .layout, + .tasks-area, + .hero { + grid-template-columns: 1fr; + } + + .hero { + flex-direction: column; + } +} diff --git a/webapp/storage.py b/webapp/storage.py new file mode 100644 index 0000000..7aee329 --- /dev/null +++ b/webapp/storage.py @@ -0,0 +1,311 @@ +# -*- coding: utf-8 -*- +""" +SQLite-backed storage for uploaded files and analysis tasks. +""" + +import json +import os +import sqlite3 +import threading +import uuid +from contextlib import contextmanager +from datetime import datetime +from typing import Any, Dict, Iterable, List, Optional + + +def utcnow_iso() -> str: + return datetime.utcnow().replace(microsecond=0).isoformat() + "Z" + + +class Storage: + """Simple SQLite storage with thread-safe write operations.""" + + def __init__(self, db_path: str): + self.db_path = os.path.abspath(db_path) + os.makedirs(os.path.dirname(self.db_path), exist_ok=True) + self._write_lock = threading.Lock() + self.init_db() + + @contextmanager + def _connect(self): + conn = sqlite3.connect(self.db_path, check_same_thread=False) + conn.row_factory = sqlite3.Row + try: + yield conn + conn.commit() + finally: + conn.close() + + def init_db(self) -> None: + with self._connect() as conn: + conn.executescript( + """ + CREATE TABLE IF NOT EXISTS uploaded_files ( + id TEXT PRIMARY KEY, + user_id TEXT NOT NULL, + original_name TEXT NOT NULL, + stored_path TEXT NOT NULL, + created_at TEXT NOT NULL + ); + + CREATE TABLE IF NOT EXISTS analysis_sessions ( + id TEXT PRIMARY KEY, + user_id TEXT NOT NULL, + title TEXT NOT NULL, + status TEXT NOT NULL, + uploaded_file_ids TEXT NOT NULL, + template_file_id TEXT, + session_output_dir TEXT, + created_at TEXT NOT NULL, + updated_at TEXT NOT NULL, + closed_at TEXT + ); + + CREATE TABLE IF NOT EXISTS analysis_tasks ( + id TEXT PRIMARY KEY, + session_id TEXT NOT NULL, + user_id TEXT NOT NULL, + query TEXT NOT NULL, + status TEXT NOT NULL, + uploaded_file_ids TEXT NOT NULL, + template_file_id TEXT, + session_output_dir TEXT, + report_file_path TEXT, + error_message TEXT, + created_at TEXT NOT NULL, + started_at TEXT, + finished_at TEXT + ); + """ + ) + + def create_uploaded_file( + self, user_id: str, original_name: str, stored_path: str + ) -> Dict[str, Any]: + record = { + "id": str(uuid.uuid4()), + "user_id": user_id, + "original_name": original_name, + "stored_path": os.path.abspath(stored_path), + "created_at": utcnow_iso(), + } + with self._write_lock, self._connect() as conn: + conn.execute( + """ + INSERT INTO uploaded_files (id, user_id, original_name, stored_path, created_at) + VALUES (:id, :user_id, :original_name, :stored_path, :created_at) + """, + record, + ) + return record + + def get_uploaded_file(self, file_id: str, user_id: str) -> Optional[Dict[str, Any]]: + with self._connect() as conn: + row = conn.execute( + """ + SELECT * FROM uploaded_files WHERE id = ? AND user_id = ? + """, + (file_id, user_id), + ).fetchone() + return dict(row) if row else None + + def list_uploaded_files( + self, file_ids: Iterable[str], user_id: str + ) -> List[Dict[str, Any]]: + file_ids = list(file_ids) + if not file_ids: + return [] + placeholders = ",".join("?" for _ in file_ids) + params = [*file_ids, user_id] + with self._connect() as conn: + rows = conn.execute( + f""" + SELECT * FROM uploaded_files + WHERE id IN ({placeholders}) AND user_id = ? + ORDER BY created_at ASC + """, + params, + ).fetchall() + return [dict(row) for row in rows] + + def list_all_uploaded_files(self, user_id: str) -> List[Dict[str, Any]]: + with self._connect() as conn: + rows = conn.execute( + """ + SELECT * FROM uploaded_files + WHERE user_id = ? + ORDER BY created_at DESC + """, + (user_id,), + ).fetchall() + return [dict(row) for row in rows] + + def create_task( + self, + session_id: str, + user_id: str, + query: str, + uploaded_file_ids: List[str], + template_file_id: Optional[str] = None, + ) -> Dict[str, Any]: + record = { + "id": str(uuid.uuid4()), + "session_id": session_id, + "user_id": user_id, + "query": query, + "status": "queued", + "uploaded_file_ids": json.dumps(uploaded_file_ids, ensure_ascii=False), + "template_file_id": template_file_id, + "session_output_dir": None, + "report_file_path": None, + "error_message": None, + "created_at": utcnow_iso(), + "started_at": None, + "finished_at": None, + } + with self._write_lock, self._connect() as conn: + conn.execute( + """ + INSERT INTO analysis_tasks ( + id, session_id, user_id, query, status, uploaded_file_ids, template_file_id, + session_output_dir, report_file_path, error_message, + created_at, started_at, finished_at + ) + VALUES ( + :id, :session_id, :user_id, :query, :status, :uploaded_file_ids, :template_file_id, + :session_output_dir, :report_file_path, :error_message, + :created_at, :started_at, :finished_at + ) + """, + record, + ) + return self.get_task(record["id"], user_id) + + def get_task(self, task_id: str, user_id: str) -> Optional[Dict[str, Any]]: + with self._connect() as conn: + row = conn.execute( + """ + SELECT * FROM analysis_tasks WHERE id = ? AND user_id = ? + """, + (task_id, user_id), + ).fetchone() + return self._normalize_task(row) if row else None + + def list_tasks(self, user_id: str) -> List[Dict[str, Any]]: + with self._connect() as conn: + rows = conn.execute( + """ + SELECT * FROM analysis_tasks + WHERE user_id = ? + ORDER BY created_at DESC + """, + (user_id,), + ).fetchall() + return [self._normalize_task(row) for row in rows] + + def list_session_tasks(self, session_id: str, user_id: str) -> List[Dict[str, Any]]: + with self._connect() as conn: + rows = conn.execute( + """ + SELECT * FROM analysis_tasks + WHERE session_id = ? AND user_id = ? + ORDER BY created_at ASC + """, + (session_id, user_id), + ).fetchall() + return [self._normalize_task(row) for row in rows] + + def create_session( + self, + user_id: str, + title: str, + uploaded_file_ids: List[str], + template_file_id: Optional[str] = None, + ) -> Dict[str, Any]: + now = utcnow_iso() + record = { + "id": str(uuid.uuid4()), + "user_id": user_id, + "title": title, + "status": "open", + "uploaded_file_ids": json.dumps(uploaded_file_ids, ensure_ascii=False), + "template_file_id": template_file_id, + "session_output_dir": None, + "created_at": now, + "updated_at": now, + "closed_at": None, + } + with self._write_lock, self._connect() as conn: + conn.execute( + """ + INSERT INTO analysis_sessions ( + id, user_id, title, status, uploaded_file_ids, template_file_id, + session_output_dir, created_at, updated_at, closed_at + ) + VALUES ( + :id, :user_id, :title, :status, :uploaded_file_ids, :template_file_id, + :session_output_dir, :created_at, :updated_at, :closed_at + ) + """, + record, + ) + return self.get_session(record["id"], user_id) + + def get_session(self, session_id: str, user_id: str) -> Optional[Dict[str, Any]]: + with self._connect() as conn: + row = conn.execute( + """ + SELECT * FROM analysis_sessions WHERE id = ? AND user_id = ? + """, + (session_id, user_id), + ).fetchone() + return self._normalize_session(row) if row else None + + def list_sessions(self, user_id: str) -> List[Dict[str, Any]]: + with self._connect() as conn: + rows = conn.execute( + """ + SELECT * FROM analysis_sessions + WHERE user_id = ? + ORDER BY updated_at DESC + """, + (user_id,), + ).fetchall() + return [self._normalize_session(row) for row in rows] + + def update_session(self, session_id: str, **fields: Any) -> None: + if not fields: + return + fields["updated_at"] = utcnow_iso() + assignments = ", ".join(f"{key} = :{key}" for key in fields.keys()) + payload = dict(fields) + payload["id"] = session_id + with self._write_lock, self._connect() as conn: + conn.execute( + f"UPDATE analysis_sessions SET {assignments} WHERE id = :id", + payload, + ) + + def update_task(self, task_id: str, **fields: Any) -> None: + if not fields: + return + assignments = ", ".join(f"{key} = :{key}" for key in fields.keys()) + payload = dict(fields) + payload["id"] = task_id + with self._write_lock, self._connect() as conn: + conn.execute( + f"UPDATE analysis_tasks SET {assignments} WHERE id = :id", + payload, + ) + + @staticmethod + def _normalize_task(row: sqlite3.Row) -> Dict[str, Any]: + task = dict(row) + task["uploaded_file_ids"] = json.loads(task["uploaded_file_ids"]) + return task + + @staticmethod + def _normalize_session(row: sqlite3.Row) -> Dict[str, Any]: + session = dict(row) + session["uploaded_file_ids"] = json.loads(session["uploaded_file_ids"]) + return session diff --git a/webapp/task_runner.py b/webapp/task_runner.py new file mode 100644 index 0000000..f53a838 --- /dev/null +++ b/webapp/task_runner.py @@ -0,0 +1,147 @@ +# -*- coding: utf-8 -*- +""" +Background task runner for analysis jobs. +""" + +import os +import shutil +import threading +from concurrent.futures import ThreadPoolExecutor +from contextlib import redirect_stderr, redirect_stdout +from typing import Optional + +from utils.create_session_dir import create_session_output_dir +from webapp.session_manager import SessionManager +from webapp.storage import Storage, utcnow_iso + + +class TaskRunner: + """Runs analysis tasks in background worker threads.""" + + def __init__( + self, + storage: Storage, + uploads_dir: str, + outputs_dir: str, + session_manager: SessionManager, + max_workers: int = 2, + ): + self.storage = storage + self.uploads_dir = os.path.abspath(uploads_dir) + self.outputs_dir = os.path.abspath(outputs_dir) + self.session_manager = session_manager + self._executor = ThreadPoolExecutor(max_workers=max_workers) + self._lock = threading.Lock() + self._submitted = set() + + def submit(self, task_id: str, user_id: str) -> None: + with self._lock: + if task_id in self._submitted: + return + self._submitted.add(task_id) + self._executor.submit(self._run_task, task_id, user_id) + + def _run_task(self, task_id: str, user_id: str) -> None: + try: + task = self.storage.get_task(task_id, user_id) + if not task: + return + session = self.storage.get_session(task["session_id"], user_id) + if not session: + return + + uploaded_files = self.storage.list_uploaded_files( + task["uploaded_file_ids"], user_id + ) + data_files = [item["stored_path"] for item in uploaded_files] + template_path = self._resolve_template_path(task, user_id) + session_output_dir = session.get("session_output_dir") + if not session_output_dir: + session_output_dir = create_session_output_dir( + self.outputs_dir, session["title"] + ) + self.storage.update_session( + session["id"], + session_output_dir=session_output_dir, + ) + session = self.storage.get_session(task["session_id"], user_id) + + runtime = self.session_manager.get_or_create( + session_id=session["id"], + user_id=user_id, + session_output_dir=session_output_dir, + uploaded_files=data_files, + template_path=template_path, + ) + + self.storage.update_task( + task_id, + status="running", + session_output_dir=session_output_dir, + started_at=utcnow_iso(), + error_message=None, + ) + self.storage.update_session(session["id"], status="running") + + log_path = os.path.join(session_output_dir, "task.log") + with runtime.lock: + with open(log_path, "a", encoding="utf-8") as log_file: + log_file.write( + f"[{utcnow_iso()}] task started for session {session['id']}\n" + ) + try: + with redirect_stdout(log_file), redirect_stderr(log_file): + result = runtime.agent.analyze( + user_input=task["query"], + files=data_files, + template_path=template_path, + session_output_dir=session_output_dir, + reset_context=not runtime.initialized, + keep_session_open=True, + ) + runtime.initialized = True + except Exception as exc: + self.storage.update_task( + task_id, + status="failed", + error_message=str(exc), + finished_at=utcnow_iso(), + report_file_path=None, + ) + self.storage.update_session(session["id"], status="open") + log_file.write(f"[{utcnow_iso()}] task failed: {exc}\n") + return + + report_file_path = self._persist_task_report( + task_id, session_output_dir, result.get("report_file_path") + ) + + self.storage.update_task( + task_id, + status="succeeded", + report_file_path=report_file_path, + finished_at=utcnow_iso(), + error_message=None, + ) + self.storage.update_session(session["id"], status="open") + finally: + with self._lock: + self._submitted.discard(task_id) + + def _resolve_template_path(self, task: dict, user_id: str) -> Optional[str]: + template_file_id = task.get("template_file_id") + if not template_file_id: + return None + file_record = self.storage.get_uploaded_file(template_file_id, user_id) + return file_record["stored_path"] if file_record else None + + @staticmethod + def _persist_task_report( + task_id: str, session_output_dir: str, current_report_path: Optional[str] + ) -> Optional[str]: + if not current_report_path or not os.path.exists(current_report_path): + return current_report_path + task_report_path = os.path.join(session_output_dir, f"report_{task_id}.md") + if os.path.abspath(current_report_path) != os.path.abspath(task_report_path): + shutil.copyfile(current_report_path, task_report_path) + return task_report_path