Horus X12S Touchscreen. Wrong function selected.

[KevinFairgrieve]

Is there an existing issue for this problem?

• [X] I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

When selecting a menu from the eight main images. The wrong one is selected. The screen is then locked from touch. Going in to a menu using the rotary encoder I.E. MDL and then selecting the telemetry icon. RF set up is displayed, again touch is disabled.

Please see the video it makes it much clearer.

Expected Behavior

When the relevant item is selected it should go to that screen.

Steps To Reproduce

See Video https://www.youtube.com/watch?v=1cRtON4a6s8

Version

Other (Please specify below)

Transmitter

FrSky X12

Anything else?

Horus X12S with touchscreen mod. FW: edge tx-x12s VERS: 2.8.0-nightly (c4fc11b7) Date: 2022-06-18 Time: 03:17:33 CFG: EPROM_VER

[raphaelcoeffic]

That pretty much sounds like you mounted the touch sensor upside down.

[raphaelcoeffic]

Or the touch sensor outputs the coordinates inverted.

[KevinFairgrieve]

Using the firmware from "https://github.com/wimalopaan/Electronics/tree/main/edgetx/firmware/x12s" I have had no issues, as per this video.

https://www.youtube.com/watch?v=hiQ0qBhCax8

[wimalopaan]

Just tested witch actual main and it works as expected

[KevinFairgrieve]

Just tested witch actual main and it works as expected

main?

Can you add an EN version so that I can try that?

Many thanks.

[rotorman]

main means main branch of EdgeTX. For building on your own, please see: https://github.com/EdgeTX/edgetx/wiki/Building-radio-firmware-in-a-webbrowser-with-Gitpod

[wimalopaan]

Just use my german version to test, if you can select the functions

[KevinFairgrieve]

Will try tomorrow.

Thanks again.

[pfeerick]

main?

Can you add an EN version so that I can try that?

i.e. For a pre-build main you can choose the latest build from here, or use a nightly build or grab

[KevinFairgrieve]

Just use my german version to test, if you can select the functions

Will try tomorrow.

Thanks again.

Tried the DE version, still the same.

[wimalopaan]

Then something of your hw is screwd up

[KevinFairgrieve]

And I have now tried the latest "main" 3ce1aef

Still the same.

Pretty sure my screen is in the correct way, but a stripdown will show that.

[pfeerick]

Check the touch screen diagnostics first ... Radio Settings -> Hardware -> Analogs (at the very bottom). If you press and hold in the middle of the screen, and then move up to the top left corner, coordinates should be near 0,0, and near 480,272 at the bottom right corner

[KevinFairgrieve]

Check the touch screen diagnostics first ... Radio Settings -> Hardware -> Analogs (at the very bottom). If you press and hold in the middle of the screen, and then move up to the top left corner, coordinates should be near 0,0, and near 480,272 at the bottom right corner

So that appears to be my issue. If I move to top left the cross goes to bottom right. How to fix?

Have I wired something wrong?

[raphaelcoeffic]

So that appears to be my issue. If I move to top left the cross goes to bottom right. How to fix?

Have I wired something wrong?

possibly, you should check how the sensor is oriented. Other possibility would be that it’s configuration stored inside is wrong.

[rcman45]

si le capteur est mal monté ou si sa configuration interne est incorrecte alors pourquoi fonctionne-t’il avec la version de wimalopaan

English translation: if the sensor is incorrectly mounted or if its internal configuration is incorrect then why does it work with the version of wimalopaan

[pfeerick]

Given you mention that etx_x12s_de_2.8.0_wm_touch_4.bin and etx_x12s_de_2.8.0_wm_touch_5.bin didn't work for you, but etx_x12s_en_2.8.0_wm_touch_3.bin did, it could be due to changes as the PR for this evolved - hence why internal configuration of the TP itself could be wrong / at fault. I think the early version of wimalopaan's PR may have set the rotation bit every time, rather than just when it was different to what was expected, or had some other rotation flag enabled... which may not have have been detected while it was being tested since it probably wasn't done with an as new screen (until now).

[KevinFairgrieve]

I just saw that an uninverted version was available. https://github.com/wimalopaan/Electronics/tree/main/edgetx/firmware/x12s

This has now solved my issue. I hope this will be rolled out to the full release. Currently only available as a DE version.

[pfeerick]

Rather than just hope, why not ask @wimalopaan what was configured differently in that firmware build? ;)

[raphaelcoeffic]

I believe the difference is really in the config stored on the touch controller, depending on which versions have been installed in between. My plan was to to see if I could download the existing config to compare and upload a new version if required.

[KevinFairgrieve]

Rather than just hope, why not ask @wimalopaan what was configured differently in that firmware build? ;)

I have now done so. Thank you.

[pfeerick]

@KevinFairgrieve Are you in a position where you can see if https://github.com/EdgeTX/edgetx/pull/2351 / tomorrows nightly build will fix this for you? Basically, if that the TP input is still inverted with the build of firmware from that PR, there is now a mechanism by which you can reset the touch panel controller to find out if it is the problem. You should be able to plug the radio into your computer, choose the USB Serial (VCP) option, and then use a serial console tool like Putty to connect to the virtual serial port that is created (at 400,000 baud). When you press enter after opening the console up, you should get a prompt. You enter the reset_gt911 command, and press enter. It should tell you what the GT911 configuration value was, and what it is now. Hopefully, the touchpanel is also now the right way around.

If that seems too daunting, that's ok. And if you do want to give it a go, I'll try and walk you through it more if needed.

[KevinFairgrieve]

@KevinFairgrieve Are you in a position where you can see if #2351 / tomorrows nightly build will fix this for you? Basically, if that the TP input is still inverted with the build of firmware from that PR, there is now a mechanism by which you can reset the touch panel controller to find out if it is the problem. You should be able to plug the radio into your computer, choose the USB Serial (VCP) option, and then use a serial console tool like Putty to connect to the virtual serial port that is created (at 400,000 baud). When you press enter after opening the console up, you should get a prompt. You enter the reset_gt911 command, and press enter. It should tell you what the GT911 configuration value was, and what it is now. Hopefully, the touchpanel is also now the right way around.

If that seems too daunting, that's ok. And if you do want to give it a go, I'll try and walk you through it more if needed.

Happy to give it a go.

I will download "putty" and the next nightly.

[KevinFairgrieve]

Downloaded the Nightly 83c21ad.

Loaded and all works as expected.

I now see the 2.8.0 RC1 is also out.

[KevinFairgrieve]

And 2.8.0 RC-1 works just fine.

You guys rock.

[Luznatural]

I have exactly the same problem with my X12S touch screen. Everything is inverted. I have installed PuTTY but I am unable to make the virtual serial connection with the radio, as apparently Windows does not detect it. So I cannot reset the screen. Is there another way to reset the screen? Perhaps making some lua process to reset the screen without having to get a connection with a computer? I would appreciate some help here Thanks in advance

[rotorman]

You could try hTerm https://www.der-hammer.info/pages/terminal.html instead (this is a serial program that I mostly use). Have a look in your Device Manager if you might need ST VCP drivers for your computer. If, get them from: https://www.st.com/en/development-tools/stsw-stm32102.html

[Luznatural]

I have been able to load the drivers and connect with COM4 to the radio WITH 400.000 bauds, but I am unable to write anything in the console of PuTTY. When I type, nothing happens. Any ideas?

[raphaelcoeffic]

@Luznatural most probably CLI is not set for the USB serial port. Go to the radio hardware settings, at the end of the page.

[Luznatural]

I have in the hardware tab of SYS in the X12S the USB-VCP to CLI, Aux1 OFF and port power off, and no luck. Can you be so kind to Ispecify for me the connection data in PuTTY? I have the following: Serial line COM4 Speed (baud): 400000 Data bits:8 Stop bits: 1 Parity: None Row control: XON/XOFF

More ideas? Thanks in advance

[rotorman]

Row control? You mean flow? Anyhow, please try with hTerm instead, as with this all the settings are cleary visible on one page and if still no luck you could post the screenshot and one can easily see what the issue would be, if communication settings are wrong.

[pfeerick]

I use Kitty, which is just a fork of Putty, and those settings look correct.

When you start the session, hit enter once, you should get the > prompt

I can't remember the default terminal settings on kitty/putty, you may want to check that also - specifically the Implicity CR/LF settings

[Luznatural]

First, thanks to all for offering your savior counseils. I have tried PuTTY, KiTTY and hTerm without success in my 3 different computers. It looks like my radio has something wrong with the VCP connection or something extrange (like myself) makes me unable to reset the touch screen. I have also tried several different connection cables, just checking if it was a wiring problem. No luck up to now. I would like to know if you think there could be any alternate way to reset the screen using any command or making something that could modify it inside ETX, perhaps a LUA script, or producing a specific version of ETX for X12S that includes this reset in the core of the firmare. Please, help this poor and desperate soul Thanks in advance

[KevinFairgrieve]

Just as an off chance, have you tried using one of the earlier versions from wimalopaan?

I found that using the test versions was OK then when 2.8.0 came out, mine just started working ok.

See my post above.

https://github.com/EdgeTX/edgetx/issues/2063#issuecomment-1159625809

It may be worth a shot.

[rotorman]

@Luznatural can you show a screenshot of your hTerm? Especially, did you set CR-LF for Send on Enter in the transmit side:

[Luznatural]

@Luznatural can you show a screenshot of your hTerm? Especially, did you set CR-LF for Send on Enter in the transmit side:

Here you have a screenshot: No luck connecting with the radio

[Luznatural]

Just as an off chance, have you tried using one of the earlier versions from wimalopaan?

I found that using the test versions was OK then when 2.8.0 came out, mine just started working ok.

See my post above.

#2063 (comment)

It may be worth a shot.

I have not been able to find any file from @wimalopaan, except one named etx_x12s_de_2.8.0_wm_7_tuninv.bin that I tried also without luck. Everything continues the same. The screen continues inverted.

I have used Windows 11 and Windows 8 to run PuTTY, KiTTY and H-term. Could that be part of the problem?

Thanks to all for your help.

[rotorman]

@Luznatural Your baudrate looks wrong. Disconnect, change it to 400000, reconnect. Then put your cursor to the right of Type "ASC" field and press Enter there. Any improvement?

[Luznatural]

Yes!!! Finaly I was able to connect and pressed reset_gt911 and the radio responded something like reset_gt911, your current configuration is "0" and then the screen started to work correctly. Thanks to all for your patience with this very dumb guy. As an aliby, I didn´t even remember how long ago I used a COM terminal. Thanks again for your kind help

[KevinFairgrieve]

Excellent. Now your TX12S will be the transmitter it should have been from the start.

If only it ran ETHOS as well!

[mervin1961]

Hi, I just bought the gt911 touch panel for my Jumper T16 and I had the same problem. Reading this post I tried to reset gt911. It return with old version 109 and new version is 0 it turn the right side but from the center 2 to 2.5 cm the screen is inactive. Is there something else I can do to correct this? Thanks.

[rotorman]

You can diagnose touch screen under hardware analogs diagnose page. Is the 0,0 point somewhere in the middle or is an area on one side cut? Would be easier to understand if you could make a small video tapping the screen at various points, while the analog diagnose page is open and post a link to that video here to see if it is a software or hardware issue.

[mervin1961]

Firstly thanks for the reply. Check with diagnostics the left top in giving the maximum 81:0 that is if my finger is extreme top and extreme left and the right bottom is 479:271. Centre nothing happens. I have Hterm to reset the touch panel and the is the only software that works for me. I have already made a video and I will upload it here. Sorry for the video quality. I had to compress it from a 88mb to upload it here.

https://github.com/EdgeTX/edgetx/assets/92143050/6e18c896-d1e2-414e-ab64-e1be8ae5594c

[mervin1961]

As you can see the main menu screen the 4 center selections icons are dead. As you already know before I did a reset the gt911 was diagonally opposite on the selection.

[rotorman]

Can you please navigate first to analogs diagnose page and THEN tap the screen while doing a new video. You should see on the bottom of the screen the detected coordinates of your finger. I am interested to see which coordinates get detected and which not.

[mervin1961]

Uploading now. Please let me know if you need more videos. Thank you.

https://github.com/EdgeTX/edgetx/assets/92143050/3070d49a-73da-499f-895c-4461d4999eae

[rotorman]

Can you try once more resetting the GT911 via CLI. If that does not solve the issue, it seems to me that your touch panel layer is unfortunately defective.

P.S. In the last video you have a theme where some text is shown in black. Can you change to default theme and also list what is the output of the bottommost row.

[mervin1961]

Everything works before resetting only diagonally opposite or 180 degrees around. Actually I have tried resetting many times but I will try again in fact hoping everything will be ok. Give me a few mins I will do another video.

[mervin1961]

reset again and results are old version 109 and new version 0. I hope this is the video you want.

https://github.com/EdgeTX/edgetx/assets/92143050/2a33ccfb-529b-4565-aa3d-4d478b4458a8

[mervin1961]

Just asking, does it have anything to do with the firmware version?