@blyshchak

Just saw your message, a buddy of mine has a T-Beam, not sure what frequencies his operates at, so I will get my hands on it and take a look.

Little update.

I am able to receive the initialization message from the SIM7600 board, so at least I know that the hardware serial read works :

RDY +CPIN: READY SMS DONE PB DONE

If anyone has this issue, you can just do a read in the main loop....

String response = ""; while (SIMCOM.available()) { char c = SIMCOM.read(); response += c; } Serial.print(response);

and then power cycle the SIM7600 with The T-Display-S3 connected

Still a mystery as to what is going on

@teastain2

Thanks for the heads up Terry, I just had my T-Display-S3 Touch delivered on Friday, I will be jumping on it very soon, I need to resolve an issue with the none touch unit....I posted that topic tonight.

Thank you again.

@bumptop

It seems like we are working in the same space, albeit different objectives... I just posted this T-Display-S3 UART communication issue so I"m happy to hear that you got further than me.

Would you mind either looking at my posted code to see where I made a mistake or perhaps post the code you are using to even get an OK from the SIMCOM unit.

I'm also curious what Lilygo product you are using ?

Thank you in advance.

@teastain2 Thank you. It was the pins that were wrong, I looked at the schemes on the lilygo github and put the rigth ones.

Is realy confusing that if you download a program for a board it gives you the pins wrong :////

Hi, did you manage to fix this? I'm facing similar problems with board definitions, although the board I'm using is probably a different version, it's a Lora32 but on the back it says T3 V1.6.1.
I'm probably doing something wrong, but it either gives an error about header file missing in libraries (Xinyuan-LilyGO), wrong pin definitions (Sandeepmistry), etc.
Since this is a very common board I'm hoping you or someone else can point me to the correct library.
Thanks!

The LilyGO site for your product is here:
https://www.lilygo.cc/en-ca/products/t-watch-s3.

And they say to use micropython from here:
https://micropython.org/download/esp32/

I found the schematic here:
https://github.com/Xinyuan-LilyGO/TTGO_TWatch_Library/tree/t-watch-s3/schematic

There are never any MicroPython programming tips or example by LilyGO .
All the examples are C++, intended for the Arduino IDE !

Python may be fun and easy on established platforms like Adafruit boards, but...
There may be no drivers (called "libraries" in C language) for your LCD screen and LORA and you will have to program them yourself using low-level code.
C language is the most common language on Earth(!) Arduino boards were developed to use C (C++)15 years ago and there is a multitude of examples and libraries available, easily updated.

Simple Arduino IDE program:

//words preceded by "//"" are comments and are not executed bool ticktock; //declare ticktock as a boolean flag void setup() { //runs once on start up Serial.begin (115200); //open the serial port for USB cable } void loop() { //runs in circles! ticktock = !ticktock; //every pass through reverse the flag if (ticktock) { //test current value of the ticktock flag Serial.println("tick"); } else { //prints one or the other to the USB port Serial.println("tock"); } delay (1000); //wait for a second and run again! }

This program will compile and run on literally thousands of microcontrollers!

@teastain2 the v2.3.1 version does have a CP2104, but the label on this board is clearly a v2.3.2.
When I plug the cable straight into the board, Windows doesn't show anything - no COM port or anything else. Device manager doesn't blink at all. The board just powers on.
I'll try to get in contact with LilyGo later today...

I was planning on uploading a sketch fron the Arduino IDE but PlatformIO is also installed and ready to go.
And I'd be surprised if my supplier is mistaken.. I had email contact with them about the board and they specifically indicated this difference between the two versions, as I asked them because there's no information online.

@txinto You have a very uncommon module and I think this "community" site, which is mostly supported by users (usually me) will not get any answers!
Please try:
https://github.com/Xinyuan-LilyGO/T-RSC3/issues
and raise an issue.
Their response time is terrible, so you may have to email them @
sales@lilygo.cc

BTW OTA is like uploading sketches via USB, but much more complicated and risky. So you may have a case where the units are deployed far from you but they have WiFi connection...I would try uploading simpler test sketches to be sure that they are functional.
What IDE are you using to program?
It is very hard to Brick a ESP32 but sometimes the sketch you loaded causes CPU crashes like Kernal Panic. The trick is to find it's reset pins and try combinations of resetting until it can upload a simple serial monitor test with a time delay like this one I wrote:

bool ticktock = true; void setup() { Serial.begin (115200); } void loop() { ticktock = !ticktock; if (ticktock) { Serial.println("tick"); } else { Serial.println("tock"); } delay (1000); }

Regards, Terry

@teastain2 OOB Out-Of-the-Box.
When you reset this unit, you get two on screen buttons: "Self Test", and "Into UI".
The Self Test does a wifi scan, lists all the APs it sees and then outputs: connecting to xinyuandianzi sprays lots of dots on the screen as it goes. On the battery device, this waits forever. On the USB-C powered device I get
Connection timed out, start smartconfig wait for smartconfig ... Please use EspTouch Apps to connect to distribution network.

Picking the Into UI button, I get a LilyGo logo animation, some sound then it displays 6 choices: Light, Controller, Wireless, Music, Mic FFT, and Configuration.
Light demos the LEDs, Controller shows some gauges which you can use with I/O inputs.
Music evidently can play music files... not sure how you get anything in there.
Mic FFT is some sort of Microphone test. This unit has a built in speaker and microphone.
The Configuration consists entirely of a button labeled Deep Sleep, which when pressed puts the Embed unit to sleep... which after you have a charged battery installed is useful.

It may be dependent on sensing a battery. I'm not repeatedly getting the animation on the battery powered device.
More experimentation is needed.

@teastain2 Oh, that's great! Thanks for support!

It looks like it was SENSOP_VN. After a few attempts the module stopped dropping off USB, and I was able to flash at least the "demo".

It would help if this were documented somewhere, though...

@aravecchia Try changing the initialisation string from tft.init(135, 240); to tft.init(); or tft.begin(); and add TFT_eSPI tft = TFT_eSPI(135,240); between your include and define declerations.