98 KiB
98 KiB
| 1 | 工单号 | 来源 | 创建日期 | 问题类型 | 问题描述 | 处理过程 | 跟踪记录 | 严重程度 | 工单状态 | 模块 | 责任人 | 关闭日期 | 车型 | VIN | SIM | Notes | Attachment | 创建人 | 关闭时长(天) | 创建日期_解析 | 关闭日期_解析 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | 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.0 | 2025-01-02 | 2025-04-24 | |||
| 3 | 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.0 | 2025-01-02 | 2025-02-11 | ||
| 4 | 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.0 | 2025-01-02 | 2025-02-18 | ||
| 5 | 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.0 | 2025-01-02 | 2025-02-11 | |||
| 6 | 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.0 | 2025-01-02 | 2025-05-13 | ||
| 7 | 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.0 | 2025-01-02 | 2025-04-24 | ||
| 8 | 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.0 | 2025-01-03 | 2025-01-21 | ||||
| 9 | 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.0 | 2025-01-03 | 2025-02-27 | ||||
| 10 | 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.0 | 2025-01-03 | 2025-02-26 | ||
| 11 | 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.0 | 2025-01-06 | 2025-01-08 | |||
| 12 | 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.0 | 2025-01-06 | 2025-01-10 | ||||
| 13 | 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.0 | 2025-01-06 | 2025-01-10 | |||
| 14 | 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.0 | 2025-01-06 | 2025-01-10 | |||||
| 15 | TR365 | 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.0 | 2025-01-06 | 2025-01-14 | ||||
| 16 | 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.0 | 2025-01-06 | 2025-01-14 | ||
| 17 | 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.0 | 2025-01-08 | 2025-01-16 | ||
| 18 | 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.0 | 2025-01-10 | 2025-03-18 | |
| 19 | TR371 | 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.0 | 2025-01-10 | 2025-02-26 | |||
| 20 | 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.0 | 2025-01-10 | 2025-02-13 | ||
| 21 | TR374 | 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.0 | 2025-01-13 | 2025-05-13 | |||
| 22 | TR375 | 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.0 | 2025-01-13 | 2025-02-13 | |||||
| 23 | TR376 | 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.0 | 2025-01-13 | 2025-02-13 | |||
| 24 | 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.0 | 2025-01-13 | 2025-01-21 | ||
| 25 | TR378 | 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.0 | 2025-01-13 | 2025-04-24 | ||
| 26 | 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.0 | 2025-01-13 | 2025-02-13 | |||
| 27 | TR380 | 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.0 | 2025-01-13 | 2025-02-26 | |||
| 28 | TR381 | 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.0 | 2025-01-13 | 2025-02-17 | |||
| 29 | TR387 | 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.0 | 2025-01-14 | 2025-05-13 | ||
| 30 | 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.0 | 2025-01-14 | 2025-05-13 | |
| 31 | 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.0 | 2025-01-15 | 2025-02-13 | |
| 32 | TR395 | 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.0 | 2025-01-16 | 2025-05-13 | ||
| 33 | TR396 | 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.0 | 2025-01-16 | 2025-03-20 | ||
| 34 | TR402 | 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.0 | 2025-01-17 | 2025-02-27 | ||
| 35 | 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.0 | 2025-01-17 | 2025-01-20 | |
| 36 | TR405 | 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.0 | 2025-01-20 | 2025-01-23 | ||||
| 37 | TR406 | 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.0 | 2025-01-20 | 2025-04-17 | ||
| 38 | TR407 | 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.0 | 2025-01-20 | 2025-03-13 | |||
| 39 | 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.0 | 2025-01-21 | 2025-01-23 | ||
| 40 | TR409 | 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.0 | 2025-01-21 | 2025-02-14 | ||||
| 41 | TR410 | 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.0 | 2025-01-21 | 2025-02-17 | |||
| 42 | TR411 | 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.0 | 2025-01-21 | 2025-04-24 | |||
| 43 | TR412 | 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.0 | 2025-01-21 | 2025-05-13 | ||
| 44 | TR413 | 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.0 | 2025-01-21 | 2025-02-26 | |||
| 45 | TR414 | 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.0 | 2025-01-22 | 2025-04-24 | |||
| 46 | TR415 | 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.0 | 2025-01-22 | 2025-04-24 | ||
| 47 | TR416 | 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.0 | 2025-01-23 | 2025-04-17 | |||
| 48 | TR417 | 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.0 | 2025-01-23 | 2025-04-01 | |||
| 49 | 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.0 | 2025-01-23 | 2025-04-22 | ||
| 50 | TR423 | 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.0 | 2025-01-23 | 2025-02-26 | ||
| 51 | TR424 | 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.0 | 2025-01-24 | 2025-03-06 | |||
| 52 | TR425 | 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.0 | 2025-01-24 | 2025-02-25 | |||
| 53 | TR426 | 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.0 | 2025-01-27 | 2025-02-26 | ||
| 54 | 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.0 | 2025-01-27 | 2025-02-27 | ||
| 55 | TR429 | 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.0 | 2025-01-28 | 2025-02-27 | ||
| 56 | TR430 | 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.0 | 2025-01-28 | 2025-04-24 | |||
| 57 | TR431 | 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.0 | 2025-01-29 | 2025-04-08 | |||
| 58 | TR432 | 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.0 | 2025-01-30 | 2025-04-24 | |||
| 59 | 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.0 | 2025-02-03 | 2025-03-11 | ||
| 60 | TR434 | 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.0 | 2025-02-04 | 2025-03-06 | |||
| 61 | 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.0 | 2025-02-04 | 2025-04-03 | |
| 62 | 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.0 | 2025-02-07 | 2025-02-18 | ||
| 63 | TR437 | 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.0 | 2025-02-12 | 2025-03-18 | ||
| 64 | TR438 | 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.0 | 2025-02-13 | 2025-03-25 | ||||
| 65 | 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.0 | 2025-02-14 | 2025-02-26 | |
| 66 | 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.0 | 2025-02-10 | 2025-05-15 | |
| 67 | TR447 | 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.0 | 2025-02-14 | 2025-05-13 | |||
| 68 | 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.0 | 2025-02-14 | 2025-03-06 | |
| 69 | TR451 | 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.0 | 2025-02-17 | 2025-02-24 | ||
| 70 | TR452 | 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.0 | 2025-02-17 | 2025-06-05 | |||
| 71 | TR453 | 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.0 | 2025-02-17 | 2025-04-17 | |||
| 72 | TR454 | 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.0 | 2025-02-17 | 2025-02-26 | ||
| 73 | 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.0 | 2025-02-18 | 2025-06-05 | |
| 74 | TR458 | 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.0 | 2025-02-19 | 2025-04-03 | |||
| 75 | 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.0 | 2025-02-20 | 2025-04-24 | |
| 76 | TR461 | 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.0 | 2025-02-20 | 2025-02-24 | |||
| 77 | 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.0 | 2025-02-20 | 2025-11-24 | |
| 78 | 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.0 | 2025-02-21 | 2025-02-27 | |
| 79 | 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.0 | 2025-02-21 | 2025-03-20 | |
| 80 | 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.0 | 2025-02-21 | 2025-02-24 | |
| 81 | TR467 | 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.0 | 2025-02-21 | 2025-10-16 | |||
| 82 | 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.0 | 2025-02-24 | 2025-04-24 | |
| 83 | TR469 | 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.0 | 2025-02-24 | 2025-04-17 | ||||
| 84 | TR470 | 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.0 | 2025-02-24 | 2025-04-17 | |||
| 85 | TR471 | 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.0 | 2025-02-24 | 2025-05-15 |