Hello,
In my case it does not work. I’m still thinking when the wifi module is plug-in for the first time it sends some commands to initialise the module.
I will keep trying 
Thanks very much.
@m0st1ted thanks for the info. I tried your suggestion but it didn’t succeed for me. Tried it with and without adding P
I’ve managed to get my hands on a Wifi module through a colleague from the Czech Republic. I learned it’s possible to connect multiple Rx to one Tx. Using a breadboard and 2 USB TTL converters I was able to hook up the Wifi module to the main circuitboard and simultaneously sniffing all messages on my laptop, using 2 Coolterm sessions:
After downloading the TMT Chow! app on my phone and using it to configure the Wifi module, messages started appearing:
2026-02-26 21:17:42 READ DEVINFO;src=P003E22C
2026-02-26 21:18:05 READ DEVINFO;src=P003E22C
So it seems there is no separate ‘handshake like’ message sent by the Wifi module, it just sends the READ DEVINFO command twice within 2 seconds. This was the response send by the main circuit board
2026-02-26 21:17:41 ACK READ DEVINFO:P190U,PS20088A,V3.0
2026-02-26 21:18:06 ACK READ DEVINFO:P190U,PS20088A,V3.0
I’m assuming it does this so it knows the firmware version and presumably knows which commands to use. When using the TMT Chow! app to open the gate, the following messages are sent by the Wifi module:
2026-02-26 21:19:20 FULL OPEN;src=P003E22C
2026-02-26 21:19:20 RS;src=P003E22C
2026-02-26 21:19:21 RS;src=P003E22C
2026-02-26 21:19:23 RS;src=P003E22C
2026-02-26 21:19:25 RS;src=P003E22C
2026-02-26 21:19:27 RS;src=P003E22C
2026-02-26 21:19:29 RS;src=P003E22C
2026-02-26 21:19:32 RS;src=P003E22C
2026-02-26 21:19:34 RS;src=P003E22C
2026-02-26 21:19:36 RS;src=P003E22C
2026-02-26 21:19:38 RS;src=P003E22C
2026-02-26 21:19:43 RS;src=P003E22C
In this case, RS seems to be my READ STATUS variant which @RPJ mentioned in his post, I’m guessing because of different versions. So the TMT Chow! App sends the open command and then polls the status every 2 seconds untill it’s fully opened. The response on the RS command look like this:
2026-02-26 21:19:19 ACK FULL OPEN
2026-02-26 21:19:20 $V1PKF0,22,Opening;src=P003E22C
2026-02-26 21:19:20 ACK RS:60,64,CC,80,40,2F,80,40,00
2026-02-26 21:19:21 ACK RS:60,64,CC,83,29,05,82,38,05
2026-02-26 21:19:23 ACK RS:60,64,CC,97,3E,0F,8F,24,0E
2026-02-26 21:19:25 ACK RS:60,64,CC,AC,3E,05,9C,15,0B
2026-02-26 21:19:28 ACK RS:60,64,CC,C4,3E,05,AA,20,09
2026-02-26 21:19:30 ACK RS:60,64,CC,D2,3E,0A,B7,13,0A
2026-02-26 21:19:32 ACK RS:60,64,CC,DC,1A,06,C3,3E,0B
2026-02-26 21:19:34 ACK RS:60,64,CC,E4,7E,00,CD,3E,09
2026-02-26 21:19:36 ACK RS:60,64,CC,E4,7B,00,D4,33,07
2026-02-26 21:19:36 ACK RS:60,64,CC,E4,7E,00,D5,3E,07
2026-02-26 21:19:38 ACK RS:60,64,CC,E4,7E,00,DB,3E,09
2026-02-26 21:19:41 $V1PKF0,17,Opened;src=0001
First few values don’t change, after that are fields which most likely describe the gate position, torque/power stats etc.
After finally having success and being able to sniff the messages, I wanted to see ifI could open the gate by sending the FULL OPEN command from my laptop, using Coolterm. Should be easy, right?
So I sent FULL OPEN;src=P003E22C\r\n using Coolterm, and I got a NAK FULL OPEN;SRC=P003E22C response. I saw the command work coming from the app, so I must be doing something wrong.
My error was as follows: when programming, I’m used to adding \r\n in a string value to add a Carriage Return + Line feed. (CR+LF), like this:
But in Coolterm, the Send String is a multiline textfield, instead of trying to add the literal \r\n characters, I needed to hit the Enter key. The cursor moves to the next line and the proper CR+LF are added:
Sending the command like this finally allowed me to open the gate! And immediately afterwards I tested @m0st1ted’s suggestion again, doing the FULL OPEN command with P + src code from my remote. This also successfully opened the gate, so it seems I kept making the same error over and over, not sending the messages in the proper format.
@ibernat how do you send your messages? Do you also use Coolterm for testing purposes? If you haven’t, I suggest you try it once, just to make sure you’re not making the same mistake as me.
Also, I’m going to use the Wifi module one more time to make sure I’ve triggered and logged all the commands from the TMT Chow! app. After that I have no use for the Wifi module any more, if you would like to have a go at it, you can DM me and I can send it to you.
Hi, it does not work for me. When I send commands to the motor always I receive NAK, but as I see on your output you reveice NAK FULL OPEN… (not only NAK)
can you try to resset the wifi module? (press P button 5 seconds and press R button once, the blue led will flash).
After this, can you sniff the TX pin on wifi module without connecting to the motor, I mean, sniff tx and power up the wifi module.
Thanks!