Help with Serial Reads from touch controller.

[Shach01]

Hi Adward, we are struggling to get usable serial information from the touch controller. it is always the same stream no matter if we attemp to trigger any form of touch event:

AA 55 1 7 0 62 3B 46 57 53 57 45 53 2D 54 35 54 4F 55 43 48 2D 54 35 2D 43

any help or guidance would be much appreciated, have a great day man!

Kind regards,

Josh

[edwardtfn]

Hey @Shach01,
In fact I haven't explored the protocol that much, so I've just used the custom component by @SmartHome-yourself (https://github.com/SmartHome-yourself/sonoff-tx-ultimate-for-esphome) with minor changes.
You can enable verbose logging and you will see a bit more from the UART data.

From what I got from the protocol, a message always starts with AA 55 01, then the next byte informs the touch type:

        const static uint8_t TOUCH_STATE_RELEASE = 1;
        const static uint8_t TOUCH_STATE_PRESS = 2;
        const static uint8_t TOUCH_STATE_SWIPE = 3;
        const static uint8_t TOUCH_STATE_MULTI_TOUCH = 11;
        const static uint8_t TOUCH_STATE_SWIPE_RIGHT = 12;
        const static uint8_t TOUCH_STATE_SWIPE_LEFT = 13;

I don't know why, but the code sets as invalid when the message starts with AA 55 01 02.

The position of the touch (a number between 0 a 10) is defined by the 6th or 7th byte:

        int TxUltimateEasy::get_touch_position_x(int uart_received_bytes[]) {
            int state = uart_received_bytes[4];
            switch (state) {
                case TOUCH_STATE_RELEASE:
                case TOUCH_STATE_MULTI_TOUCH:
                case TOUCH_STATE_SWIPE_LEFT:
                case TOUCH_STATE_SWIPE_RIGHT:
                    return uart_received_bytes[5];
                    break;

                default:
                    return uart_received_bytes[6];
                    break;
            }
        }

I can try to look more at this later. Please share here if you find something more. 😉

[edwardtfn]

Hey @Shach01, did you got what you were looking for?

[Shach01]

Hey Edward! We did cone right! After reviewing the drivers for tasmota and esp easy we realized (not documented) that they are pulling GPIO5 HIGH to activate the touch driver, weird as the touch driver still spams a default serial stream and once you pull this pin high the driver behaves and starts to send correct touch serial data. Thank you so much for your assistance. I hope that helps. Kind regards, Josh

…

Sent from my Galaxy

-------- Original message -------- From: Edward Firmo ***@***.***> Date: 2024/07/12 11:31 (GMT+02:00) To: edwardtfn/TX-Ultimate-Easy ***@***.***> Cc: Shach01 ***@***.***>, Mention ***@***.***> Subject: Re: [edwardtfn/TX-Ultimate-Easy] Help with Serial Reads from touch controller. (Issue #24) Hey @Shach01<https://github.com/Shach01>, did you got what you were looking for? — Reply to this email directly, view it on GitHub<#24 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMPAUWZWWZWWHMGFCX4SC3TZL6O53AVCNFSM6AAAAABJP2WYESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRVGE4TANBZGU>. You are receiving this because you were mentioned.Message ID: ***@***.***>