@luki743 said in CAN Transceiver Support:
T-Embed
Yes. ESP32 supports CAN and these are featured S3 boards.
Retired Industrial Robotics Interface Designer
@luki743 said in CAN Transceiver Support:
T-Embed
Yes. ESP32 supports CAN and these are featured S3 boards.
@danardi It is indeed annoying and it gave me trouble, but I figured out that you can edit the pinconfig.h that appears in the Arduino IDE off to the right with your own SSID and Password and avoid the ESPTouch nonsense. (this 'ESP touch" has nothing to do with the optional touch screen, BTW)
If you are new to LilyGO T-Display S3 I made a support GitHub repository here:
https://github.com/teastainGit/LilyGO-T-display-S3-setup-and-examples
-Terry
@mistera I tried but could not determine which chip. There are 2 five-pin, one 3.3v reg and the other the battery charge controller.
Try poking around their GitHub here:
https://github.com/Xinyuan-LilyGO/T-Display-S3
https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/schematic
https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/main/image/T-DISPLAY-S3.jpg
@patofoto No worries, I'm a retired engineer with spare time, looking for a challenge.
Well, you did get a value from the Dallas while it was under ESPHome.
I could not see anything in the YAML that configures the I2C port signal SDA to be a bi-directional serial comm link like onewire!
There must be another config file when you select LilyGO T-Display S3 .
I'm still poking around on it, intriguing.
-Terry
@patofoto well this is good news. If ESPHome can use a onewire sensor on pin 43 then we need to look at how it assigns the pin.
As you may know, the DS18B20 is a onewire device not i2c. Onewire is somewhat outdated now replaced largely by i2c. The JST is intended for I2c which is a bus topology that will support many sensors and I/O devices at one time due to their internal addressing. SPI is popular for displays and SD cards.
The Volos example uses solely i2c sensors! This is a good example of multiple i2c sensors on an i2c bus.
If you were to use the JST for onewire sensors there would be no way to connect i2c sensors.
Arduino IDE is the way to go. It gives low level control and is the most flexible to customization.
Yes, the libraries take care of the on-chip address.
I made my own GitHub repository for the LilyGO T-Display S3:
https://github.com/teastainGit/LilyGO-T-display-S3-setup-and-examples
Take a look for more info!
-Terry
From @teastain2 an example of DS18B20 Dallas Temperature sensor connected to pin 17 on my LilyGO T-Display S3 and tested good!
#include <OneWire.h>
#include <DallasTemperature.h>
const int oneWireBus = 17; //WORKS with pin17 but neither 43 or 44.
OneWire oneWire(oneWireBus);
DallasTemperature sensors(&oneWire);
void setup() {
Serial.begin(115200);
sensors.begin();
}
void loop() {
sensors.requestTemperatures();
float temperatureC = sensors.getTempCByIndex(0);
Serial.print(temperatureC);
Serial.println("ºC");
Serial.println(" ");
delay(2000);
}
The HotHead Temp Sensor sketch is an example of reading a SHTx series temp/humidity sensor using i2c, but not onewire!
Having said that, I just discovered that I too cannot read the onewire sensor on pin 43 either!
It appears that 43 and 44 are set by the I/O mux in the ESP32 to be I2C, they recommend that you use another GPIO pin!
I am investigating right now, will get back to you later!
(Check this post, I may just edit my answer!)
-Terry
@rotortalk Hi, the technical resource is here:
https://github.com/Xinyuan-LilyGO/T-RGB
It matters what senders you are using, could you be more specific?
There is only one Grove port and beware that the pins are not standard qwiic or M5Stack wire position correct.
So with only 2 GPIO avail, and you would have to make your own cable to correct the pin order, you may have to go the i2c route with an i2c I/o expander. Not very neat!
-Terry
@oh23 Here is an “Instructable” set up guide:
https://www.instructables.com/Simple-Arduino-and-HC-SR04-Example/
You could use GPIOpins 1 and 2 for the trig and echo.
The other, fancier sensor would need need a dedicated library with a suggested example.
Such as here:
https://www.dfrobot.com/product-1935.html
Use pins 17, 18 as per the LilyGO T-Display S3 pinout, strictly observing tx and rx pin assignments.
Hope this helps!
-Terry
P.S. I also have a general, but comprehensive setup guide for the LilyGO T-Display S3 here:
https://github.com/teastainGit/LilyGO-T-display-S3-setup-and-examples
@oh23 Well, if you don't need any of it except the water sensor...can you tell me which sensor and sensor board product and I'll recommend a hook up?
-Terry
@oh23 Do you have experience with Arduino IDE?
The LilyGO T-Display S3 is a beautiful state of the art dev board, and is really an Arduino on steroids.
99% of all Arduino sensors will work on LilyGO T-Display S3 !
It is specifically an ESP32 S3.
With sensors I prefer i2c connected ones!
The A02YYUW you recommended works very well and is UART comm and water proof.
The other HC-SR04 is more for dry environments and I am not familiar with the trig/echo scheme, but it probably is supported by libraries.
My first choice would be a VL53L TOF sensor with i2c comms, but in a waterproof package.
-Terry
@gwer this site is the community site, answered most by other users!
You should raise an “Issue” on the github site.