I am in need of assistance with my 13.3' HA2208-Scout head unit. Model: PX6
The touch screen just stopped working for no reason a little after a year. I tried just resetting the cache with no change. I then completed a factory reset with no change. After reviewing the logs I found that I am getting a:
I just responded to the email, and yes the order was refunded via Amazon because I had damaged harnesses and could not get the Amazon Dasiata team to respond. Because of this Amazon the company, refunded me my purcahse price. However what does the cost that was or was not refunded have to do with getting technical support for a product that your company manafactured. I am simply looking for someone to assist me in why the touchscreen stopped working, and what can be done to resolve this.
@finachem We are wondering if you can reset the touch screen under the following instruction. https://youtu.be/yaRKoQb1jlc If still no luck, please shot a video to show us the situation that you mentioned, we will forward to our engineer for further diagnosing. Your cooperation will be appreciated.
Thank you for your assistance. I did try this with no luck. Here is a video of me walking through this process. https://youtu.be/u4zFDnNhWGU Addationally I entered recovery mode and captured this video with a walkthrough of all screens of the logs as it does not seem that I can export the logs to usb. https://youtu.be/SchD0yY1EYA Thank you for your assistance.
2. As I had completed a factory reset when trying to correct the touchscreen issue I realized that my Tourque application uninstalled so I re-installed it from the APK installer. I then found that the unit was not seeing the OBD 2 adapter. I went to Bluetooth in an atempt to re-pair the OBD 2 adapter and on the newest version of the software it apears that the unit no longer displays devices that are visable in range. I only get a menu that asks to search on the phone for the head unit. I have also disabled carplay as a diffrent post sugested, with no change. Can you advise how I can pair my OBD 2 adapter again?
3. What would need to be done to upgrade to Android 11 on this unit?
I was able to downgrade back to 3.3.10, connect my bluetooth OBD2 via the android menu, and then upgrade back to 3.4.4. I did try the touchscreen, and relearning the touch on both versions still with no change in the touchscreen. Any updates on the technical side?
@finachem Our technicians reckon if the harness connected with the screen is loose and they advise you can try to reconnect the screen harness and the power cables as well. Please let us know if it can help. If still fail, it maybe the hardware issue, we will further diagnose.
@Support Dasaita I had already removed the unit from the vehicle and removed the screen to re-seat the connections 2 diffrent times with no change. Visual inspection of the connectors shows no damage or odd discoloration on either side.
@finachem Sorry to tell you that it should be the front panel that fail to work. In this case, we are wondering if you can purchase one and replace it by your own. Please let us know your choice and we will offer further instruction accordingly.
@finachem Would you mind sending your paypal account to us via email so that we can send you payment invoice? And we would like to tell you that the front panel cost $100, please kindly let us know if you can accept.
Hello @Support Dasaita, can you provide me with the most current firmware version? I have updated Scout to 3.8.40, with MCU: MTCH_HA_V3.80_1from 7/22/2021.
Hello @Support Dasaita, I upgraded the firmware telenav_s4c_rk3399_10.0_ota(20230807), and noticed that the MCU did not update. I then entered recovery mode to view the logs, and found I could not export the ones from the recovery window. I did a logcat, but that just seems to be operational data, and not the data of the harware like is contained in the recovery logs.
1. How can the recovery logs be exported to view on PC?
Hello @Support Dasaita, I am still dealing with the touchscreen digitizer not working. I have been getting some info from the logs, but it is a picture at a time, I want to be able to review in something like VS Code to make it easier and see everything. I disasymbled the display down to the board and cleaned all connections to the board and the ribbon cables hoping that would resolve the issue, but it did not.
