Hi Ben,
Super.
I tried it with esp32 MCU and SSD1306 display.
I have attached the program in which 3 VL53L0X sensors work on the same I2C bus. It works very well.
Thank you very much.
Regards,
Sasi
Search found 41 matches
- Wed May 08, 2024 1:47 pm
- Forum: General
- Topic: 5 VL53L0X sensors on one I2C line. [SOLVED]
- Replies: 4
- Views: 140
- Tue May 07, 2024 5:09 pm
- Forum: General
- Topic: 5 VL53L0X sensors on one I2C line. [SOLVED]
- Replies: 4
- Views: 140
Re: 5 VL53L0X sensors on one I2C line.
Hello Ben, Thank you for your suggestion. I was not familiar with this circuit before. I thought of a similar solution, with 2 pieces 4051 analog multiplexers, until I found examples of re-addressing on the Internet. The VL53L0X sensors do have a fixed I2C address, but this can be changed after powe...
- Sun May 05, 2024 6:05 pm
- Forum: General
- Topic: 5 VL53L0X sensors on one I2C line. [SOLVED]
- Replies: 4
- Views: 140
5 VL53L0X sensors on one I2C line. [SOLVED]
Hello, I would like to ask for a little help. I want to use 5 VL53L0X sensors on one I2C line. Can this be solved somehow with the current component macro? If not, would you modify it so that the sensors are individually addressable? It would also be nice if the modified version did not have the XSH...
- Tue Jan 02, 2024 11:26 am
- Forum: Bug Reports
- Topic: ST7789 Font problem [SOLVED]
- Replies: 4
- Views: 956
Re: ST7789 Font problem
Thank you very much. It works!
- Tue Jan 02, 2024 11:06 am
- Forum: Bug Reports
- Topic: PIC24FJ1024GB610 I2C Channel3 problem
- Replies: 2
- Views: 687
Re: PIC24FJ1024GB610 I2C Channel3 problem
That's right.
There is only a problem with channel 3.
But I don't think it's a chip bug because I get an error message from the compiler about references to undeclared variables.
There is only a problem with channel 3.
But I don't think it's a chip bug because I get an error message from the compiler about references to undeclared variables.
- Mon Jan 01, 2024 8:55 pm
- Forum: General
- Topic: Flowcode10 reacts very slowly when I want to edit Variables [SOLVED]
- Replies: 5
- Views: 7189
Re: Flowcode10 reacts very slowly when I want to edit Variables [SOLVED]
Flowcode v10.1.0.38 update solved this.
- Mon Jan 01, 2024 8:42 pm
- Forum: Bug Reports
- Topic: ST7789 Font problem [SOLVED]
- Replies: 4
- Views: 956
ST7789 Font problem [SOLVED]
Hello,
I am using ST7789 display with PIC24FJ1024GB610 MCU.
When I compile the attached project, I get an error message if I use the "Verdana Number 24" font.
Regards,
Sasi
I am using ST7789 display with PIC24FJ1024GB610 MCU.
When I compile the attached project, I get an error message if I use the "Verdana Number 24" font.
Regards,
Sasi
- Mon Jan 01, 2024 8:16 pm
- Forum: Bug Reports
- Topic: PIC24FJ1024GB610 SPI bus problem
- Replies: 0
- Views: 2132
PIC24FJ1024GB610 SPI bus problem
Hello, I am using ST7789 display with PIC24FJ1024GB610 MCU. The attached project only works if the SPI channel is emulated by software. If I select channel 1, 2, or 3 in the Component Properties window, the program seems to hang during the initialization phase of the SPI interface. (After the reset,...
- Mon Jan 01, 2024 7:34 pm
- Forum: Bug Reports
- Topic: PIC24FJ1024GB610 I2C Channel3 problem
- Replies: 2
- Views: 687
PIC24FJ1024GB610 I2C Channel3 problem
Hello, Happy New Year to everyone! I tried the SHT-31 sensor on the Clicker2 panel. The MCU type is PIC24FJ1024GB610. If I select Channel 3 in the "Grove Component SHT31" Component Properties window, I get the attached error message from the compiler. Regards, Sasi PIC24FJ1024GB610 I2C_test.fcfx Com...
- Thu Nov 16, 2023 4:34 pm
- Forum: General
- Topic: Flowcode10 reacts very slowly when I want to edit Variables [SOLVED]
- Replies: 5
- Views: 7189
Re: Flowcode10 reacts very slowly when I want to edit Variables
Thanks for the quick response.
I think it would also be useful if the one-time execution of this check could be triggered by a button.
Is there a way to temporarily disable continuous monitoring?
I think it would also be useful if the one-time execution of this check could be triggered by a button.
Is there a way to temporarily disable continuous monitoring?