I just finished my breadboard adapter for the OG T4-S3 and before I burn something up I thought I should ask where I can find info on what Voltage is accepted on the VBUS pin?

TIA.

So, I took this risk for order it anyway, because my development environment is the Microsoft Visual Studio and C# programming, and the result is the following screen snippet:

The above board is running my app such as an IoT Device connected to the Microsoft Azure IoT Central for handling and managing a device telemetry data. It's built using the NanoFramework .NET C# code.

In other words, the T-QT C6 has been flashed with the NanoFramework firmware, connected to the Visual Studio 2022 and using programming technique like at the other projects included its debugging.

Thanks for T-QT C6 team for creating this cool product and I am looking forward for its next version and extensions, for instance, some adapter (stack) to use sensors from the M5Stack product line.

it seems I cannot edit , so here's an update

it's my provider, using another SIM I can send all the SMS's I want.

when test MAX30105 sensor, if use: TDS3+max30105+OLED without use TDS3's TFT, it works well.

this time when initialize TDS3's TFT by TFT_eSPI.h, the TFT init OK, but OLED and MAX30105 not work(no need both OLED and TFT works, just for testing);

if disable OLED and use TDS3's TFT to show the content, TDS3 stuck at the first page;

please let me know if need the testing code.

Thanks
Adam

I found the problem, the USB-C cable does not work, I have 4 USB-C cables, there is only one that works correctly.
The problem is solved.

THANKS.

https://github.com/Xinyuan-LilyGO/T-HMI/issues/7

I fixed the issue.
In file: "Setup207_LilyGo_T_HMI.h"
Located in: \libraries\TFT_eSPI\User_Setups

Either remove or remark line 11 "#define CGRAM_OFFSET"

After making that change all rotations orientations work.

Thanks, I realize that I can change the definitions of Wire to the other pin, but then would the Touch display not function appropriately?

I would prefer to define GPIO2 and GPIO3 as Wire1 and not Wire, and have the touch display use that interface. I would then define Wire as the new pins (as per your example above).

Is there a software option to do this? I am using some libraries that are hardcoded to Wire, and don't want to manually change them myself.

If not possible, the Mutex method around the lv_task_handler() seems to work well - the board has been running for about 2 weeks with no issues, and no bad data.

I have a custom PCB designed around the LilyGo-T-Call-SIM800 board and wanted to know if this is pin to pin compatible (replaceable) with T-Call V1.4
Can I switch the T-Call SIM800 board with T-Call v1.4 without any changes to hardware/firmware?

Thanks

Will go with 24VDC for the board, and then use another power supply for the relay dry contacts.

Best, Marko