A couple of new wemos D1 Mini footprint devices
- Electroguard
- Posts: 886
- Joined: Mon Feb 08, 2021 6:22 pm
- Has thanked: 285 times
- Been thanked: 329 times
A couple of new wemos D1 Mini footprint devices
I've just noticed a couple of interesting wemos footprint devices which may interest others.
CiccioCB will need to let us know if the first item would be Annex compatible though...
esp32-C3 with Bluetooth LE RISC-V Single-Core CPU
12x I/O
1x RGB LED
1x LOLIN I2C Port
1x Battery port with 500mA charging
4MB Flash
ADC, I2C, SPI, UART, USB Serial
Compatible with LOLIN D1 mini shields
https://www.aliexpress.com/item/1005004 ... 5394%21rec
This other item should actually plug straight into it, or any other wemos footprint device.
What makes it stand out from the now unavailable 7 pixel neo shield is that these are an 8x8 matrix which could be used to display animated coloured messages from a table of your own-designed font characters if wished.
https://www.aliexpress.com/item/1005004 ... 763%21rec
Probably best to wait a few days before ordering though, cos they will be the worse for wear for a while (chinese new year - rabbit).
CiccioCB will need to let us know if the first item would be Annex compatible though...
esp32-C3 with Bluetooth LE RISC-V Single-Core CPU
12x I/O
1x RGB LED
1x LOLIN I2C Port
1x Battery port with 500mA charging
4MB Flash
ADC, I2C, SPI, UART, USB Serial
Compatible with LOLIN D1 mini shields
https://www.aliexpress.com/item/1005004 ... 5394%21rec
This other item should actually plug straight into it, or any other wemos footprint device.
What makes it stand out from the now unavailable 7 pixel neo shield is that these are an 8x8 matrix which could be used to display animated coloured messages from a table of your own-designed font characters if wished.
https://www.aliexpress.com/item/1005004 ... 763%21rec
Probably best to wait a few days before ordering though, cos they will be the worse for wear for a while (chinese new year - rabbit).
- cicciocb
- Site Admin
- Posts: 2095
- Joined: Mon Feb 03, 2020 1:15 pm
- Location: Toulouse
- Has thanked: 450 times
- Been thanked: 1385 times
- Contact:
Re: A couple of new wemos D1 Mini footprint deices
Hi Robin,
Normally -C3 is supported so it should work but it will be up to you to confirm it.
Even the neopixel shield should work (image will be rotated at 90°)
Normally -C3 is supported so it should work but it will be up to you to confirm it.
Even the neopixel shield should work (image will be rotated at 90°)
- cicciocb
- Site Admin
- Posts: 2095
- Joined: Mon Feb 03, 2020 1:15 pm
- Location: Toulouse
- Has thanked: 450 times
- Been thanked: 1385 times
- Contact:
- Electroguard
- Posts: 886
- Joined: Mon Feb 08, 2021 6:22 pm
- Has thanked: 285 times
- Been thanked: 329 times
Re: A couple of new wemos D1 Mini footprint deices
Thanks Francesco, that's what I thought ... I've just ordered some.
The neopixel shield has DOUT as well as the expected DIN, which means that several could be connected together side by side, eg: in a 'doubler' or 'tripler' shield to make a 2 or 3 digit display.
Which raises a question: if neo.setup reserves memory locations for the declared number of neopixels used, which is manipulated for changing the pixels rgb values, might it be possible for users to be able to directly access the pixel memory, instead of needing to replicate it in user memory ?
The neopixel shield has DOUT as well as the expected DIN, which means that several could be connected together side by side, eg: in a 'doubler' or 'tripler' shield to make a 2 or 3 digit display.
Which raises a question: if neo.setup reserves memory locations for the declared number of neopixels used, which is manipulated for changing the pixels rgb values, might it be possible for users to be able to directly access the pixel memory, instead of needing to replicate it in user memory ?
- cicciocb
- Site Admin
- Posts: 2095
- Joined: Mon Feb 03, 2020 1:15 pm
- Location: Toulouse
- Has thanked: 450 times
- Been thanked: 1385 times
- Contact:
Re: A couple of new wemos D1 Mini footprint deices
Annex32 supports these displays with the function NEOSCROLL, enabling the use of external fonts, bmp images and so on.[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Mon Jan 23, 2023 11:35 am Thanks Francesco, that's what I thought ... I've just ordered some.
The neopixel shield has DOUT as well as the expected DIN, which means that several could be connected together side by side, eg: in a 'doubler' or 'tripler' shield to make a 2 or 3 digit display.
Which raises a question: if neo.setup reserves memory locations for the declared number of neopixels used, which is manipulated for changing the pixels rgb values, might it be possible for users to be able to directly access the pixel memory, instead of needing to replicate it in user memory ?
Basically, the NEOSCROLL manages the neopixel matrix as a TFT display (more commands are under development)
As all the pixels are refreshed/written in a single shot, it is always required to have a mirror image in the local memory.
The RAM available is enough for most of the project and, in the worst case, you can still use a module with PSRAM.
Honestly, I did a 64x16 neopixels display scrolling bmp images with a ESP32-C3 (1024 pixels) without any problem.
- Electroguard
- Posts: 886
- Joined: Mon Feb 08, 2021 6:22 pm
- Has thanked: 285 times
- Been thanked: 329 times
Re: A couple of new wemos D1 Mini footprint deices
I've ordered 4 for the moment, cos I need some for colour-changing mood lights that double as battery powered emergency lighting during power fails. The pixels must be tiny to squeeze 64 into such a small space, so it will be interesting to see how much current they draw, and how many can be chained together.
While on the subject of NEO's, I created a user sub to split a combined RGB value into the individual R,G,B values, but I can't figure out a way to return the 3 component values without modifying 3 pre-existing global values.
Is there a way for Annex to return the 3 separate R,G,B values ?
Or can a function only return a single value ?
sub splitRGB(rgb)
r$=right$(hex$(rgb >> 16),2) ': r=val(r$)
g$=right$(hex$(rgb >> 8),2 ) ': g=val(g$)
b$=right$(hex$(rgb),2) ': b=val(b$)
'if dbug=1 then
' wlog "r="+r$'+", "+r
' wlog "g="+g$'+", "+g
' wlog "b="+b$'+", "+b
'endif
end sub
While on the subject of NEO's, I created a user sub to split a combined RGB value into the individual R,G,B values, but I can't figure out a way to return the 3 component values without modifying 3 pre-existing global values.
Is there a way for Annex to return the 3 separate R,G,B values ?
Or can a function only return a single value ?
sub splitRGB(rgb)
r$=right$(hex$(rgb >> 16),2) ': r=val(r$)
g$=right$(hex$(rgb >> 8),2 ) ': g=val(g$)
b$=right$(hex$(rgb),2) ': b=val(b$)
'if dbug=1 then
' wlog "r="+r$'+", "+r
' wlog "g="+g$'+", "+g
' wlog "b="+b$'+", "+b
'endif
end sub
- cicciocb
- Site Admin
- Posts: 2095
- Joined: Mon Feb 03, 2020 1:15 pm
- Location: Toulouse
- Has thanked: 450 times
- Been thanked: 1385 times
- Contact:
Re: A couple of new wemos D1 Mini footprint devices
Code: [Local Link Removed for Guests]
rgb = &h123456
r = (rgb >> 16) and 255
g = (rgb >> 8) and 255
b = rgb & 255
- Electroguard
- Posts: 886
- Joined: Mon Feb 08, 2021 6:22 pm
- Has thanked: 285 times
- Been thanked: 329 times
- Electroguard
- Posts: 886
- Joined: Mon Feb 08, 2021 6:22 pm
- Has thanked: 285 times
- Been thanked: 329 times
Re: A couple of new wemos D1 Mini footprint devices
These wemos footprint C3's with bluetooth might easily be missed cos they look so similar to the pink or purple S2's that don't have bluetooth.
https://www.aliexpress.com/item/1005004 ... 7865%21rec
https://www.aliexpress.com/item/1005004 ... 7865%21rec
Re: A couple of new wemos D1 Mini footprint devices
Oho my goodness £2.87 and £1.44 for shipping but where is the Flash memory? guess it's integrated.
Had been having nightmares after Francesco says we got migrate to ESP32 eventually , got a large estate
of ESP8266.
Looking at ESP32-C3 datasheet page 23, Table 9, Connection Between ESP32C3 and External Flash
Internal ROM is 384kb and 400kb of SRAM.
On the C3 mini v1.0.0 there is no Flash.
Thanks Electroguard for the link.
https://www.espressif.com/sites/default ... eet_en.pdf
Hanspeter
Had been having nightmares after Francesco says we got migrate to ESP32 eventually , got a large estate
of ESP8266.
Looking at ESP32-C3 datasheet page 23, Table 9, Connection Between ESP32C3 and External Flash
Internal ROM is 384kb and 400kb of SRAM.
On the C3 mini v1.0.0 there is no Flash.
Thanks Electroguard for the link.
https://www.espressif.com/sites/default ... eet_en.pdf
Hanspeter