makermoekoe / picoclick-c3 Goto Github PK

Hello,
I've built an similar picoclick based on yours. I want to flash some Arduino Sketch over the native USB (gpio 18/19). Flashing with an external USB/Serial converter works great, but with Native USB windows say that the device was not recognized properly and not Port is showing up. What am I doing wrong?
Thanks!

Hey, am I just blind or where is the full BOM of the C3? I know there kinda is one for main components, but none for smaller ones. Also a lot of Info for actually building it seems to be missing from the Gitbook. It's not impossible, but I would love for some additional information.

I managed to assemble the top part of the PCB today with some minor hiccups. Please don't pay too much attention to the solder joints. All components are sourced from Digikey and Mouser with some replacements for parts which were not available.
The hardest part was finding the reference designators on the board drawing and the only workaround was loading the board file into an online viewer and trying to match it. A graphic with good readable reference designators would be a huge help.

Another small problem was trying to find the right orientation of U2 as I couldn't find a dot on the PCB to match the component. After checking the documention of the component and the schematics I was able to narrow it down.

I can try to update the footprint after getting familiar with Eagle and commit a merge request if that helps you.

Greetings!
Considering your store is often out of stock of those, I wanted to know if you'd be willing to add the pick and place for PCBway as one of the files?
I'm sadly not good enough yet in soldering to work with such small components but I could actually use such a small IOT Button.

Thanks,
Fedack

Hi, I noticed two things while opening the project in Eagle:

1. There are some ad-hoc libraries missing for Eagle.
   

2. The BOM doesn't have the precise manufacturer codes of the components and is harder to find the exact components on Digikey or LCSC.
   

In the README it says that most standby current is used by the voltage divider connected to the battery which according to the schematics is connected only to the ESP32. However in the code I can find no usage of that pin except for the defines. Is there maybe some other place where this information is used? I plan to create my own iot button inspired by you project and if it is not need I consider dropping the voltage divider.

Thanks for this awesome project!!

I was wondering - what steps do you take to flash the firmware via USB over JTAG?

Thanks in advance!

1.) On the question if you could improve the performance:
Are there still boot messages if you look at the serialport? Because if there are you could try to completely disable them as this wastes time during startup. --> https://esp32.com/viewtopic.php?t=24244 and https://www.esp32.com/viewtopic.php?t=1658 (don't know if it is the same procedure as for the c3)

2.) How much longer is the boot time if you validate the boot image, because this could be a possible backdoor?

3.) May I use you your design for a private project? (I want to try to build a kind of opensource alternative to this --> https://freedrum.rocks/)

Just found. your awesome project, impressive and nice idea.
As you can see on my profile I'm also doing a lot of stuff on ESP32 core and I'm moving now all my boards from Micro USB to USB-C, but I had some issues with some of them so I was wondering if you will able to share reference of your if it works. I'm using eagle also so it could just fit on my board as is.
What MPN or manufacturer reference are you using to order the USBC_C393939 connector?

Thanks fr your help

If i would add a second button, would this be correct:

Hello, sorry to bother but I am making my own ESP32-C3 board and now I am concerned about one thing.
Can I flash the board via USB by just connecting my USB connector to GPIO 18 and 19? Do I need to hold some pin high or low to upload specifically? Thanks in advance for any reply.

hi, thank you for the great project.

I've been waiting for months for a new drop and was wondering whether you'll ever produce more?

I just finished watched the YouTube video and came to check for the schematics. However they do not seem to be pushed yet.

Can you tell when we can expect to see them?

I use ESPRESSIF IDF v4.3.2 for software development. This allows the Picoclick_C3T_hwtest_v2 example to be compiled successfully.

With ESPNOW_master and Picoclick_ESPNOW_slave I always get the following error:

FAILED: ESPNOW_master.elf cmd.exe /C "cd . && C:\Users\Markus\Documents\esp\.espressif\tools\xtensa-esp32-elf\esp-2021r2-8.4.0\xtensa-esp32-elf\bin\xtensa-esp32-elf-g++.exe -mlongcalls -Wno-frame-address @CMakeFiles\ESPNOW_master.elf.rsp -o ESPNOW_master.elf && cd ." c:/users/markus/documents/esp/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: esp-idf/freertos/libfreertos.a(port_common.c.obj):(.literal.main_task+0x14): undefined reference to `app_main' c:/users/markus/documents/esp/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: esp-idf/freertos/libfreertos.a(port_common.c.obj): in function `main_task': C:/Users/Markus/Documents/esp/.espressif/frameworks/esp-idf-v4.3.2/components/freertos/port/port_common.c:129: undefined reference to `app_main' collect2.exe: error: ld returned 1 exit status ninja: build stopped: subcommand failed. ninja failed with exit code 1

So I just received a batch of 3 Picoclick-C3 devices.
The device is really well made, great job @makermoekoe !!

The thing I'm now stuck with is that I don't see an easy path for integrating the devices into my Home Assistant setup?

• I have many ESPHome-based devices around the house, but that doesn't look like a great option, ESPHome will likely kill the battery life - even with deepsleep.
• MQTT might be an option, but I have zero experience with the Arduino-IDE...
• ... ?

So, is anyone using the Picoclick-C3 with Home Assistant? How?

Failing anyone with Home Assistant experience, what would be the best way to achieve this ?

I saw the previous issue #19 and decided to try this anyway. I don't need crazy fast as for this one I just want it as an easy button to log when medication is taken.

It works perfectly if I solder the usb jumper and power it that way. But when I put the battery on I need to hold the button for a second. From what I've read I guess I need to be pulling up a pin?

esphome:
  name: c3-sonia-pill
  platform: ESP32
  board: esp32-c3-devkitm-1
  # on_boot:
  #   priority: 400
  #   then:
  #     - light.turn_on:
  #         id: ledClk
  #         color_mode: RGB
  #         brightness: 100%
  #         green: 100%
  
substitutions:
  use_address: !secret ip_pc_01
  name: pc01
  ip: !secret ip_pc_01

mqtt:
  broker: 10.5.10.100
  username: picoclick
  password: !secret mqtt_pass_pc
  on_connect:
    then:
      - binary_sensor.template.publish:
          id: resetPill
          state: ON
      - delay: 5s
      - binary_sensor.template.publish:
          id: resetPill
          state: OFF
      - light.turn_on:
          id: ledClk
          color_mode: RGB
          brightness: 100%
          red: 100%
          green: 0
      # - deep_sleep.enter: deepSleep

# <<: !include common/api.yaml        
<<: !include common/wifi.yaml
<<: !include common/ota.yaml

# Enable logging
logger:

deep_sleep:
  id: deepSleep
  run_duration: 30s
  
# light:
#   - platform: fastled_spi
#     chipset: APA102
#     data_pin: GPIO7
#     clock_pin: GPIO6
#     num_leds: 2
#     rgb_order: BGR
#     name: "Picoclick state"
#     id: ledClk

sensor:

  # update this to do a sampling and average
  - platform: adc
    pin: 4
    name: "Sonia Pill Button Voltage"
    update_interval: 60s
    filters:
      - lambda: return x * 1.43 + 0;

binary_sensor:
  - platform: gpio
    pin: 5
    name: "Sonia Pill Button"
    on_release:
      - deep_sleep.enter: deepSleep
    on_press:
      - deep_sleep.prevent: deepSleep

  - platform: template
    name: "Reset Pill"
    id: resetPill

Hello,

I would like to add a second button to the schematic.
If possible have the same wake-up functionality as the first button.
Do I need to duplicate the below schematic completely for a second button?

I noticed there is no value for the capacitor C5. Was this something you were tweaking for the antenna? Did you find a good value?

Hi,
Could you share with us the PCB design file, which we can download and modify ourselves if we want?
Thanks!

What part F1 and F2 ?

thankyou

I cannot find a proper antenna or any matching circuit in the schematics and/or picture at all so was wondering how good the range on these devices will be (both the C3 and the C3T)?

Hi, according to the schematic the BUTTON line could get ~3.8V when pressing the on board button, which would be more than the Max Input Voltage specified for the ESP32 as VDD+0.3 V which would mean 3.6V in this case. Did you run into any problems with this setup so far?

Hi,
thanks for sharing this great project. Some sources recommend quit large capacitors (>1000uF) for applications with WiFi & BLE in order to prevent "random" reboots and similar errors. Have you experienced any issues with your board, i.e. wouldn't it make sense to add bigger capacitors (sacrificing some of the small footprint)?
Thanks!

The direction of the battery monitoring mosfet it seems like not good. The current flow is in opposite direction so how the controller get the value ?

Hey is it possible to buy one or more. We could use it in our Hackerspace :). Greetings nice project.

The part named F2 in schematic and BOM has a value of 0. What would be the correct value here?

(also: since I can‘t find any info on this anywhere, do you know the impedance of the ESP32-C3 itself?)

Is there enough room (GPIO) to adapt this board this to either:

• rotary encoder
• rotary encoder with push button

DuckDuckGo: electronics rotary push button

Cheers

Paul

It'd be cool to break out some (minimum 4) extra pins, as pads or as pin holes or as a miniature JST connector

How come the low discharge rate of such a small battery doesn't cause a brownout when it draws 200+ mA at boot?

Can someone link the appropriate XTAL? Can’t seem to find the right one. Thank you!

How did you make the 360 degree rotating gif of the board?

So...I bought 3 pcs a couple of months ago...and I managed to brick 2 of them trying to flash ESPHome onto them.

After flashing serial log (Termite) shows :

Using 'COM11' as serial port.
Connecting...
Detecting chip type... ESP32-C3
Connecting...

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-C3 (revision 3)
 - Number of Cores: 1
 - Max CPU Frequenc... (96 %)Writing at 0x000b8e68... (100 %)Wrote 709504 bytes (420762 compressed) at 0x00010000 in 9.8 seconds (effective 578.8 kbit/s)...
Hash of data verified.

Leaving...
Hard Resetting...
Hard resetting via RTS pin...
Done! Flashing is complete!

Showing logs:
[10:33:43]invalid header: 0xffffffff
[10:33:43]invalid header: 0xffffffff
[10:33:43]invalid header: 0xffffffff
[10:33:43]invalid header: 0xffffffff
...line repeats hundreds of times...
[10:33:44]invalid header: 0xffffffff
[10:33:44]invalid header: 0xffffffff
[10:33:44]invalid header:ESP-ROM:esp32c3-api1-20210207
[10:33:44]Build:Feb  7 2021
[10:33:44]rst:0x7 (TG0WDT_SYS_RST),boot:0xf (SPI_FAST_FLASH_BOOT)
[10:33:44]Saved PC:0x4004c0dc
[10:33:44]invalid header: 0xffffffff
[10:33:44]invalid header: 0xffffffff
[10:33:44]invalid header: 0xffffffff
...line repeats hundreds of times...

What is going on ?
Perhaps someone could post a detailed step-by-step ?

Do I need a driver for the picoclick to show up in PlatformIO win Windows11?
I have tried a variety of cables, the picoclick lights up but nothing shows up in platformio or in the device manager.

I was browsing around some ESP32 troubleshooting and found this interesting issue over at Espressif's GitHub espressif/esp-idf#5777 but I don't know if this pertains to the C3 as well.

By calibrating only when necessary, ESP32 wakeup to app_main entry is reduced from 27ms to 17ms; more significantly, ESP32-S2 is reduced from 90ms to 17ms.

Cheers!