author
10CommentsColorado Joined February 14th, 2016
Software developer
  • ISS Globe- Blinks When the ISS Passes Overhead

    Have this working somewhat. In testing, I'm using Blynk button. The blinking operation starts but doesn't stop after 30 sec. Have to restart to stop blinking. Blynk project identical to yours. Didn't make any code changes except auth, ssid and p/w. Thought you might have idea. Thanks Dan

    View Instructable »
  • dpcons commented on Donny Terek's instructable Simple Portable Bluetooth Speaker4 months ago
    Simple Portable Bluetooth Speaker

    Beautiful job. Very nice instructable. Where is the volume controlled?

    View Instructable »
  • dpcons commented on arihantj8's instructable Open Source Data Logger (OPENSDL)5 months ago
    Open Source Data Logger (OPENSDL)

    Looks like a fun project. Where can I get the code?

    View Instructable »
  • dpcons commented on 陳亮's instructable M5Cam X M5Stack10 months ago
    M5Cam X M5Stack

    Thanks very much for fixing the issues I described. Everything works very well. I appreciate your quick response. Thanks for posting.

    View Instructable »
  • dpcons commented on 陳亮's instructable M5Cam X M5Stack10 months ago
    M5Cam X M5Stack

    More info concerning my problem getting the referenced M5Cam software to flash and run properly.Issue #1 - I fell back and flashed the .bin from the M5Cam-firmware.zip to the camera module. It appears to work better, in that is doesn't fire-off I2C errors and the set frame error. It actually connects and sends video to my Windows browser. Unfortunately, when I disconnect from the M5Cam AP, the firmware doesn't reset for a new connection. In order to make another connection, the module must be rebooted. Is this normal?Issue #2 - Having some limited success, I tried running the viewer app on my M5-Core Black system. The camera module AP connects but fails to GET any data. I get timeouts, followed by disconnections. I tried another M5-Core White system with the same result. I've a...

    see more »

    More info concerning my problem getting the referenced M5Cam software to flash and run properly.Issue #1 - I fell back and flashed the .bin from the M5Cam-firmware.zip to the camera module. It appears to work better, in that is doesn't fire-off I2C errors and the set frame error. It actually connects and sends video to my Windows browser. Unfortunately, when I disconnect from the M5Cam AP, the firmware doesn't reset for a new connection. In order to make another connection, the module must be rebooted. Is this normal?Issue #2 - Having some limited success, I tried running the viewer app on my M5-Core Black system. The camera module AP connects but fails to GET any data. I get timeouts, followed by disconnections. I tried another M5-Core White system with the same result. I've attached JPGs to show serial log data from both camera and viewer..Question #1 - What version of ESP-IDF did you use to create the .bin in the M5Cam-firmware.zip?Question #2 - Did you use the referenced version of the source to build the .bin?Thanks, Dan

    View Instructable »
  • dpcons commented on 陳亮's instructable M5Cam X M5Stack10 months ago
    M5Cam X M5Stack

    Thanks for the response. I tried to build demo using ESP-IDF. Had no problem. Downloaded and ran Make MenuConfig and Make Flash. Compiled and downloaded fine. After flash, used puTTY to view startup. System failed. Sorry for the length of this message, but I guess you can't upload files to this site. Anyway...got the following:=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.09.15 14:52:21 =~=~=~=~=~=~=~=~=~=~=~=ets Jun 8 2016 00:22:57rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)configsip: 0, SPIWP:0xeeclk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00mode:DIO, clock div:2load:0x3fff0010,len:4load:0x3fff0014,len:6060load:0x40078000,len:9392load:0x40080400,len:6136entry 0x4008076cI (171) boot: ESP-IDF v3.2-dev-1016-gd56a40070 2nd stage bootloader...

    see more »

    Thanks for the response. I tried to build demo using ESP-IDF. Had no problem. Downloaded and ran Make MenuConfig and Make Flash. Compiled and downloaded fine. After flash, used puTTY to view startup. System failed. Sorry for the length of this message, but I guess you can't upload files to this site. Anyway...got the following:=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.09.15 14:52:21 =~=~=~=~=~=~=~=~=~=~=~=ets Jun 8 2016 00:22:57rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)configsip: 0, SPIWP:0xeeclk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00mode:DIO, clock div:2load:0x3fff0010,len:4load:0x3fff0014,len:6060load:0x40078000,len:9392load:0x40080400,len:6136entry 0x4008076cI (171) boot: ESP-IDF v3.2-dev-1016-gd56a40070 2nd stage bootloaderI (172) boot: compile time 14:42:02I (173) boot: Enabling RNG early entropy source...I (193) boot: SPI Speed : 40MHzI (206) boot: SPI Mode : DIOI (219) boot: SPI Flash Size : 4MBI (232) boot: Partition Table:I (243) boot: ## Label Usage Type ST Offset LengthI (265) boot: 0 nvs WiFi data 01 02 00009000 00006000I (289) boot: 1 phy_init RF data 01 01 0000f000 00001000I (312) boot: 2 factory factory app 00 00 00010000 00100000I (336) boot: End of partition tableI (348) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x18c5c (101468) mapI (596) esp_image: segment 1: paddr=0x00028c84 vaddr=0x3ffb0000 size=0x03354 ( 13140) loadI (629) esp_image: segment 2: paddr=0x0002bfe0 vaddr=0x3ffb3354 size=0x00000 ( 0) loadI (631) esp_image: segment 3: paddr=0x0002bfe8 vaddr=0x40080000 size=0x00400 ( 1024) loadI (654) esp_image: segment 4: paddr=0x0002c3f0 vaddr=0x40080400 size=0x03c20 ( 15392) loadI (718) esp_image: segment 5: paddr=0x00030018 vaddr=0x400d0018 size=0x6e134 (450868) mapI (1691) esp_image: segment 6: paddr=0x0009e154 vaddr=0x40084020 size=0x0e5e8 ( 58856) loadI (1844) esp_image: segment 7: paddr=0x000ac744 vaddr=0x400c0000 size=0x00000 ( 0) loadI (1845) esp_image: segment 8: paddr=0x000ac74c vaddr=0x50000000 size=0x00000 ( 0) loadI (1932) boot: Loaded app from partition at offset 0x10000I (1932) boot: Disabling RNG early entropy source...I (1935) cpu_start: Pro cpu up.I (1945) cpu_start: Starting app cpu, entry point is 0x40081104I (1) cpu_start: App cpu up.I (1978) heap_init: Initializing. RAM available for dynamic allocation:I (1999) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAMI (2018) heap_init: At 3FFB9438 len 00026BC8 (154 KiB): DRAMI (2037) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAMI (2057) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAMI (2077) heap_init: At 40092608 len 0000D9F8 (54 KiB): IRAMI (2096) cpu_start: Pro cpu start user codeI (28) cpu_start: Starting scheduler on PRO CPU.I (0) cpu_start: Starting scheduler on APP CPU.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! errors started hereE (1718) sccb: i2c write reg=0xa7 err=0x107E (1718) sccb: i2c write reg=0xa7 err=0xffffffffE (1718) sccb: i2c write reg=0xa7 err=0x107E (1718) sccb: i2c write reg=0xa7 err=0xffffffffE (1718) sccb: i2c write reg=0xa7 err=0xffffffffE (1728) sccb: i2c write reg=0xa7 err=0xffffffffE (1738) sccb: i2c write reg=0xa7 err=0xffffffffE (1738) sccb: i2c write reg=0x7f err=0xffffffffE (1748) sccb: i2c write reg=0xe5 err=0xffffffffE (1748) sccb: i2c write reg=0xe1 err=0xffffffffE (1758) sccb: i2c write reg=0xdd err=0xffffffffE (1758) sccb: i2c write reg=0xc2 err=0xffffffffE (1768) sccb: i2c write reg=0xff err=0xffffffffE (1768) sccb: i2c write reg=0x12 err=0xffffffffE (1778) sccb: i2c write reg=0x03 err=0xffffffffE (1778) sccb: i2c write reg=0x32 err=0xffffffffE (1788) sccb: i2c write reg=0x17 err=0xffffffffE (1788) sccb: i2c write reg=0x18 err=0xffffffffE (1798) sccb: i2c write reg=0x19 err=0xffffffffE (1798) sccb: i2c write reg=0x1a err=0xffffffffE (1808) sccb: i2c write reg=0x3d err=0xffffffffE (1808) sccb: i2c write reg=0x35 err=0xffffffffE (1818) sccb: i2c write reg=0x22 err=0xffffffffE (1828) sccb: i2c write reg=0x37 err=0xffffffffE (1828) sccb: i2c write reg=0x34 err=0xffffffffE (1838) sccb: i2c write reg=0x06 err=0xffffffffE (1838) sccb: i2c write reg=0x0d err=0xffffffffE (1848) sccb: i2c write reg=0x0e err=0xffffffffE (1848) sccb: i2c write reg=0xff err=0xffffffffE (1858) sccb: i2c write reg=0x05 err=0xffffffffE (1858) sccb: i2c write reg=0xe0 err=0x107E (1868) sccb: i2c write reg=0xc1 err=0xffffffffE (1868) sccb: i2c write reg=0x8c err=0x107E (1878) sccb: i2c write reg=0x53 err=0xffffffffE (1878) sccb: i2c write reg=0x54 err=0xffffffffE (1888) sccb: i2c write reg=0x51 err=0x107E (1888) sccb: i2c write reg=0x52 err=0xffffffffE (1898) sccb: i2c write reg=0x55 err=0xffffffffE (1898) sccb: i2c write reg=0x57 err=0x107E (1908) sccb: i2c write reg=0x86 err=0xffffffffE (1908) sccb: i2c write reg=0x50 err=0xffffffffE (1918) sccb: i2c write reg=0xd3 err=0x107E (1918) sccb: i2c write reg=0x05 err=0xffffffffE (1928) sccb: i2c write reg=0xe0 err=0xffffffffI (1928) camera_demo: Detected OV2640 camera, using JPEG formatE (1938) sccb: i2c write reg=0xff err=0xffffffffE (1948) sccb: i2c write reg=0xe0 err=0x107E (1948) sccb: i2c write reg=0xda err=0xffffffffE (1958) sccb: i2c write reg=0xd7 err=0xffffffffE (1958) sccb: i2c write reg=0xe1 err=0xffffffffE (1968) sccb: i2c write reg=0x44 err=0xffffffffE (1968) sccb: i2c write reg=0xe0 err=0x107E (3008) sccb: i2c write reg=0xff err=0x107E (3008) sccb: i2c write reg=0x05 err=0xffffffffE (3008) sccb: i2c write reg=0x5a err=0xffffffffE (3008) sccb: i2c write reg=0x5b err=0xffffffffE (4008) sccb: i2c write reg=0x5c err=0x107E (4008) sccb: i2c write reg=0xff err=0xffffffffE (4008) sccb: i2c write reg=0x11 err=0x107E (4008) sccb: i2c write reg=0xff err=0x107E (4008) sccb: i2c write reg=0x12 err=0xffffffffE (4018) sccb: i2c write reg=0x03 err=0xffffffffE (4018) sccb: i2c write reg=0x32 err=0x107E (4028) sccb: i2c write reg=0x17 err=0xffffffffE (4028) sccb: i2c write reg=0x18 err=0xffffffffE (4038) sccb: i2c write reg=0x19 err=0xffffffffE (4048) sccb: i2c write reg=0x1a err=0xffffffffE (4048) sccb: i2c write reg=0x3d err=0xffffffffE (4058) sccb: i2c write reg=0x35 err=0xffffffffE (4058) sccb: i2c write reg=0x22 err=0xffffffffE (4068) sccb: i2c write reg=0x37 err=0xffffffffE (4068) sccb: i2c write reg=0x34 err=0xffffffffE (4078) sccb: i2c write reg=0x06 err=0xffffffffE (4078) sccb: i2c write reg=0x0d err=0xffffffffE (4088) sccb: i2c write reg=0x0e err=0x107E (4088) sccb: i2c write reg=0x42 err=0x107E (4098) sccb: i2c write reg=0xff err=0xffffffffE (5098) sccb: i2c write reg=0x05 err=0x107E (5098) sccb: i2c write reg=0xe0 err=0xffffffffE (5098) sccb: i2c write reg=0xc0 err=0xffffffffE (6098) sccb: i2c write reg=0xc1 err=0x107E (6098) sccb: i2c write reg=0x8c err=0xffffffffE (6098) sccb: i2c write reg=0x53 err=0xffffffffE (6098) sccb: i2c write reg=0x54 err=0x107E (6098) sccb: i2c write reg=0x51 err=0x107E (6108) sccb: i2c write reg=0x52 err=0x107E (6108) sccb: i2c write reg=0x55 err=0x107E (7118) sccb: i2c write reg=0x57 err=0x107E (7118) sccb: i2c write reg=0x86 err=0xffffffffE (8118) sccb: i2c write reg=0x50 err=0x107E (8118) sccb: i2c write reg=0xd3 err=0xffffffffE (8118) sccb: i2c write reg=0x05 err=0x107E (8118) sccb: i2c write reg=0xe0 err=0x107E (8118) sccb: i2c write reg=0xff err=0x107E (8128) sccb: i2c write reg=0x05 err=0x107E (8158) camera: Failed to set frame sizeE (8158) camera_demo: Camera init failed with error 0x20002I'm using the standard M5Stack Camera, nothing custom.I browsed the setup in the menuconfig and everything looked OK. Did I miss something? Do I need to change any configuration info? Thanks for your help

    I left out some information. I'm using the standard M5Stack Camera, nothing custom.I browsed the setup in the menuconfig and everything looked OK. Did I miss something? Do I need to change any configuration info? Thanks for your help.

    I left out some information. I'm using the standard M5Stack Camera, nothing custom.I browsed the setup in the menuconfig and everything looked OK. Did I miss something? Do I need to change any configuration info? Thanks for your help.

    View Instructable »
  • dpcons commented on 陳亮's instructable M5Cam X M5Stack10 months ago
    M5Cam X M5Stack

    Is the M5stack cam demo firmware required to be burned into the M5 camera? In other words, will the viewer software work with the M5Cam-test firmware already in the camera? Thanks alot for posting this project.

    View Instructable »
  • Make Your Own Spy Bug (Arduino Voice Recorder)

    Implemented system as described. Works well except audio playback is at a higher rate.(i.e chipmunk voice). I'm using Windows media player. Do I need to modify something.Thanks, nice project.

    View Instructable »
  • dpcons followed photography, leds, fishing, backyard and 36 others channel 3 years ago