New Xsight Touch is not working anymore

tajvdz · Post by **tajvdz** » Sat Oct 19, 2024 11:27 am

Well the new remote worked just fine for 10 days but now I have problems.

I used it yesterday and no problem. When I went to bed I put it in the loading unit. When I took it out half an hour ago the touch screen was black and didn't turn on with pressing a button. I took out the battery and put it back in. I got the white starting screen with the Xsight touch logo. I first tought it was working again but the only thing i got was this logo. I started Rmir and connected the remote to my pc with the usb cable. That worked. I was able to download from the remote and able to write to it. I uploaded the original configuaration first. On the touch screen there was the message of USB connection. After the upload was finished i took the usb cable from the remote. I still got the message of usb connection. When I took out the battery and put it back in I got the white logo screen again. When I connected it to my pc I got a message that there was a problem with the device an that windows doesn't recognize it. I tried the other usb ports and also another pc but I got the same message. What happened and can this be fixed? I'm seriously worried. I was glad to have a good working remote again and replacing it for yet a new one will cost me a lot of money again..

A small update. I left the battery out for a few minutes and when I put it back in it looked like it was working again but only for a few seconds. I got the home screen and I was able to go to the devices. But that was all. Touch screen didn't respond anymore. When I took out the battery again and put it back in I only get the Home screen after the logo screen but that is all. By the way also still no usb connection possible. I think the last thing worries me the most...

mdavej · Post by **mdavej** » Sat Oct 19, 2024 11:53 am

Maybe some debris in the USB port or a loose or bridged solder joint. Only way to check the latter is disassembly unfortunately.

Have you tried a different cable?

tajvdz · Post by **tajvdz** » Sat Oct 19, 2024 1:17 pm

mdavej wrote:Maybe some debris in the USB port or a loose or bridged solder joint. Only way to check the latter is disassembly unfortunately.

Have you tried a different cable?

No I didn't try another usb cable. Read my message there are more problems with the remote. I think the usb problem is part of the rest. It started the same time. The remote doesn't work now either. I get the home screen but touch screen isn't working.

What I did try is connect my old remote with the same cable. That is working. So cable is ok. So the problem is completely in my new remote.

tajvdz · Post by **tajvdz** » Sat Oct 19, 2024 2:09 pm

well strange because the remote is working again. I left the battery out a few hours. when I put it back in the touch screen was working again. I only had a config in it that was not mine. So I couldn't test it further. What i did was add my tv on the remote. It worked but right after that the touch screen froze again and didn't respond. I took the batter out again and after a few minutes it worked again. I connected it to my pc and there was a connection. I uploaded my config and that worked. Only thing was that after I disconnected the usb cable the usb connection message was still on the remote and the remote didn't start working. After i took the battery out and put it in it worked. Also pc connection and also after I take off the usb cable. very strange. Now after 10 minutes still working.

What id happen is there a way to take action so that this doesn't happen anymore?

tajvdz · Post by **tajvdz** » Sun Oct 20, 2024 5:33 am

The problems are still there. The remote worked just fine for about an hour. But then I saw that the touchscreen was black and stayed black. Removing the battery for a while has different results. Most of the time I only get the logo and sometimes I get the home screen. Most of the times the home screen is not working and sometimes it works for a few minutes. So it looks like that right after the remote got powered up by the battery the remote freezes. Either during the startup (logo), immediately after the startup or a few minutes later. What causes this problem and can it be solved?

I use the new battery and loading unit but the old power supply because the new one firts in an american socket. As far as I can see myself they are compatible. But since the remote was in the loading unit the first time the screen stayed black I started to wonder about this.

Post by **The Robman** » Sun Oct 20, 2024 6:54 am

If your old remote still works, have you tried swapping the batteries? It's starting to sound like a battery issue rather than a remote issue.

Post by **mathdon** » Sun Oct 20, 2024 8:01 am

It sounds to me that the issue is with the battery and/or the loading unit, by which I assume you mean the charging cradle. Can you try the old everything, battery with loading unit and power supply? I don't know where you are, so don't know the mains voltage there, but the new power supply with a US plug may be for 110v only. Your combination of the new loading unit and old power supply seems to be asking for trouble.

tajvdz · Post by **tajvdz** » Sun Oct 20, 2024 10:14 am

My old remote is still working. I swapped batteries but that doesn't make any difference. They are also both the same type.

What I did is using the new charging cradle with the old power supply. I had to do this because the new power supply is with a US`plug. I also used the new battery. I think the charging cradle hasn't got any electronical parts in it or not? If so and the batteris are both the same why should the power supply cause any problems? I live in The Netherlands and we have 220 volt over here. On the power supply it says that it is suitable for 100-240v.
I think this should be safe then? If it wasn't I think the charging combination caused some damage to the remote al ready.

Post by **The Robman** » Sun Oct 20, 2024 10:51 am

What Graham was suggesting was to remove as many variables as possible. In other words, use the old battery with the old charging cradle and the old power supply, then put the old battery in the new remote. Then, if that doesn't make a difference, we've eliminated the battery, the cradle and the power supply as being the problem.

If that is the case, the best I can suggest now is, if you can make a successful connection to the remote using JP1, force RMIR to re-load the last firmware upgrade. Graham can tell you how to do that.

tajvdz · Post by **tajvdz** » Sun Oct 20, 2024 12:44 pm

The Robman wrote:What Graham was suggesting was to remove as many variables as possible. In other words, use the old battery with the old charging cradle and the old power supply, then put the old battery in the new remote. Then, if that doesn't make a difference, we've eliminated the battery, the cradle and the power supply as being the problem.

If that is the case, the best I can suggest now is, if you can make a successful connection to the remote using JP1, force RMIR to re-load the last firmware upgrade. Graham can tell you how to do that.

The battery is working and the problem appears when I put the battery in the remote. Nothing changes if I put it in the cradle and the cradle is not part of a working remote. The problem is there now. Maybe it was caused by the cradle or power supply what I think is very unlikely because it charges and that is all it does. All values of the parts are the same. I wish I never mentioned this because it is not getting to the solution. I think the problem is in the remote itself. So a firmware update would be better. But you said using JP1. Is that a special cable or can it be done with the usb cable?

Post by **The Robman** » Sun Oct 20, 2024 1:17 pm

tajvdz wrote:
The Robman wrote:What Graham was suggesting was to remove as many variables as possible. In other words, use the old battery with the old charging cradle and the old power supply, then put the old battery in the new remote. Then, if that doesn't make a difference, we've eliminated the battery, the cradle and the power supply as being the problem.

If that is the case, the best I can suggest now is, if you can make a successful connection to the remote using JP1, force RMIR to re-load the last firmware upgrade. Graham can tell you how to do that.
The battery is working and the problem appears when I put the battery in the remote. Nothing changes if I put it in the cradle and the cradle is not part of a working remote. The problem is there now. Maybe it was caused by the cradle or power supply what I think is very unlikely because it charges and that is all it does. All values of the parts are the same. I wish I never mentioned this because it is not getting to the solution. I think the problem is in the remote itself. So a firmware update would be better. But you said using JP1. Is that a special cable or can it be done with the usb cable?

I think you are missing the point that I was agreeing with you, hence why I suggested re-applying the firmware update. "Using JP1" means connecting the remote to your computer using the USB cable and using the RMIR program.

tajvdz · Post by **tajvdz** » Sun Oct 20, 2024 3:39 pm

The Robman wrote:I think you are missing the point that I was agreeing with you, hence why I suggested re-applying the firmware update. "Using JP1" means connecting the remote to your computer using the USB cable and using the RMIR program.

"

ok sorry I missunderstood. I thought you wanted me to double check. I don't know how to upload a picture but I compared the power supplies and they are both the same. Only the plug is different.

I think it either is a software or a hardware problem with my remote. Maybe because it wasn't used for years? It looks like it freezes and stops working. If it is working it is only for a minute or so. So i hope I can get a working connection with USB.

I thought there was a special JP1 cable but USB I have.

So I hope to find out how I can do a firmware update. Isn't it possible to see the error in a logfile now if I connect it to RMIR?

Post by **The Robman** » Sun Oct 20, 2024 6:34 pm

Graham,
Is there a way for him to force a firmware upgrade using RMIR, even if RMIR thinks he has the most recent version? The best I can think of, regarding his remote issues, is that the firmware has become corrupted.

tajvdz · Post by **tajvdz** » Tue Oct 22, 2024 12:53 pm

I really don't know if this is a hardware of software issue. Sunday night it worked for a while and then I went to bed. Yesterday morning it didn't go further than the logo. I tried at least 25 times. This afternoon I put the battery back in and it workd for at least 2 hours. I had to go to the shops then and when I came back about 1.5 hour later the touch screen was black. I removed the battery but only the logo again. I tried about 5 times and only the logo.

I can try what a firmware update does if I know how to do that.
I also bought a hardly used One For All Xsight touch for 25 Euros to be sure.

Post by **mathdon** » Wed Oct 23, 2024 4:25 am

The Robman wrote:Graham,
Is there a way for him to force a firmware upgrade using RMIR, even if RMIR thinks he has the most recent version? The best I can think of, regarding his remote issues, is that the firmware has become corrupted.

Yes. Download the remote into RMIR (or open an XSight setup in it). The Advanced menu should then have an item XSight operations. Click this to open the submenu and then select the checkbox item Force XSight Firmware Upgrade. Now do a download. It will run the upgrade process regardless of whether the existing firmware is the latest one or not.