Menu

Windows 11

2021-12-24
2022-01-08
<< < 1 2 (Page 2 of 2)
  • brownrb

    brownrb - 2021-12-29

    As admin I clicked the wrong icon for the attached file you did and hence unable to read the text output

    If it was giving values, then what it tells me is there is something not right about the library folder - this used the files in the same folder as the sketch .ino

    And before using the installed library from documents/arduino/libraries did not work
    So I would say
    delete documents/arduino/libraries /myMLX90614AF
    folder

    then use arduino library manager to load the myMLX90614AF.zip file

     
  • Ralf Dinkelmeyer

    Hi,
    did exactly, as you said.
    1. Test with the text_mlx90614 from the firmware.zip -> stopping after start task timer:

    13:20:54.053 -> ets Jun 8 2016 00:22:57
    13:20:54.053 ->
    13:20:54.053 -> rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
    13:20:54.053 -> flash read err, 1000
    13:20:54.053 -> ets_main.c 371
    13:20:54.394 -> ets Jun 8 2016 00:22:57
    13:20:54.394 ->
    13:20:54.394 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
    13:20:54.394 -> configsip: 0, SPIWP:0xee
    13:20:54.394 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
    13:20:54.437 -> mode:DIO, clock div:1
    13:20:54.437 -> load:0x3fff0018,len:4
    13:20:54.437 -> load:0x3fff001c,len:1216
    13:20:54.437 -> ho 0 tail 12 room 4
    13:20:54.437 -> load:0x40078000,len:10944
    13:20:54.437 -> load:0x40080400,len:6388
    13:20:54.437 -> entry 0x400806b4
    13:20:54.517 -> start: I2C
    13:20:54.517 -> start: mlx90614
    13:20:54.517 -> start: task timer

    1. I changed this test: I blocked the main loop and copied the lines from "the older test" which was working (see ino attached):

    13:31:46.554 -> ets Jun 8 2016 00:22:57
    13:31:46.554 ->
    13:31:46.554 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
    13:31:46.554 -> configsip: 0, SPIWP:0xee
    13:31:46.554 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
    13:31:46.597 -> mode:DIO, clock div:1
    13:31:46.597 -> load:0x3fff0018,len:4
    13:31:46.597 -> load:0x3fff001c,len:1216
    13:31:46.597 -> ho 0 tail 12 room 4
    13:31:46.597 -> load:0x40078000,len:10944
    13:31:46.597 -> load:0x40080400,len:6388
    13:31:46.597 -> entry 0x400806b4
    13:31:46.714 -> start: I2C
    13:31:46.714 -> start: mlx90614
    13:31:46.714 -> start: task timer
    13:31:48.719 -> Sky ambient: 25.59, Sky object: 40.91
    13:31:50.682 -> Sky ambient: 26.03, Sky object: 45.13
    13:31:52.698 -> Sky ambient: 26.37, Sky object: 31.57
    13:31:54.714 -> Sky ambient: 26.27, Sky object: 26.49
    13:31:56.688 -> Sky ambient: 26.23, Sky object: 26.41
    13:31:58.693 -> Sky ambient: 26.21, Sky object: 26.29
    13:32:00.687 -> Sky ambient: 26.21, Sky object: 26.17
    13:32:02.698 -> Sky ambient: 26.19, Sky object: 29.29
    13:32:04.698 -> Sky ambient: 26.19, Sky object: 24.11
    13:32:06.693 -> Sky ambient: 26.21, Sky object: 22.31
    13:32:08.731 -> Sky ambient: 26.21, Sky object: 32.39
    13:32:10.714 -> Sky ambient: 26.23, Sky object: 23.29

    So there is somthing not working in the blocked section?
    I attached the complete folder of the changed saved working sketch.

     
    • brownrb

      brownrb - 2021-12-29

      1. Test with the textmlx90614 from the firmware.zip -> stopping after start task timer:

      The other test program, in the tests folder, for the mlx90614, is not necessary now,

      It is replaced with the test_mlx90614 (I posted here just before) which does not rely on the task timer,

      So don't worry, the mlx90614 is working.

      So now we need to move on and address the issue of the chip rebooting

      I would like to see your controllerconfig file, can you please post it.

      Now - addressing the reboot you seem to be having.

      1, How are you powering the ESP32? This reset is often caused by insufficient voltage and current to the ESP32
      2. GPIO 12 connected to something (that is D12)?

      So this is the way ahead (please change your settings to match this)
      1. send me the controllerconfig.h file to look at
      2. Load the firmware file .ino again. enable accesspoint and webserver and tsl2591
      3. The target board should be ESP32 Dev Module
      4. The partition scheme should be Default 4MB with spiffs (1.2MB APP, 1.5MB SPIFFS)
      5. BEFORE programming the esp32, in the arduino IDE, select tools, Core debug level and set that to error
      6. Upload the sketch to the esp32
      7. Once the upload is finished, then do next step
      8. Tools, ESP32 data sketch upload
      9. When finished
      10. Open the serial port monitor
      11. Press the reset button on the ESP32
      12. When/if it crashes, copy all the text from the serial monitor window, paste it into a text file and post it so I can take a look.

      regards
      Robert

       
  • Ralf Dinkelmeyer

    I am not the specialist in this things, but I compared both sketches:
    on the left: the blocked (not working section) and on the right the working sektion
    on the left: the lines of the serial printing are missing, so its obvious, why there is no output on the serial monitor.

     
  • Ralf Dinkelmeyer

    Added Light-Sensor, adapted controllerconfig
    Bootlog, see attachement
    Serialmonitor, almost nothing, see attachement
    Added OLED, adapted controllerconfig, see attachement
    The OLED switches through the pages, pg9 only after some sec. black screen.
    Can connect via accesspoint, app hangs at Status Message "Get rtc"
    Dissabled ALL Real-Time-Clock (ESP32RTC was enebled, factory setting, didn't change)
    Then it seems to work:
    - Lux, Sky Object/Ambient shows changing vaules, Object raising to 33C while covered by hand (Cloud stay 100%, but I am indoor...)
    - Logging is running
    - Can set e.g. display settings.
    - Can sent "RTC to PC-Date/Time", but RTC stays 01-01-1900, even when I press "get"

    RTC from ESP32 seems not to work. I will test the external module ....

    Hope this will help us.
    Regards Ralf

    P.S. what's the reason for the silly green LED on my light-board, can one switch it off? Or do I have to cover with black paint?

     
  • Ralf Dinkelmeyer

    Added Light-Sensor, adapted controllerconfig
    Bootlog, see attachement
    Serialmonitor, almost nothing, see attachement
    Added OLED, adapted controllerconfig, see attachement
    The OLED switches through the pages, pg9 only after some sec. black screen.
    Can connect via accesspoint, app hangs at Status Message "Get rtc"
    Dissabled ALL Real-Time-Clock (ESP32RTC was enebled, factory setting, didn't change)
    Then it seems to work:
    - Lux, Sky Object/Ambient shows changing vaules, Object raising to 33C while covered by hand (Cloud stay 100%, but I am indoor...)
    - Logging is running
    - Can set e.g. display settings.
    - Can sent "RTC to PC-Date/Time", but RTC stays 01-01-1900, even when I press "get"

    RTC from ESP32 seems not to work. I will test the external module ....

    Hope this will help us.
    Regards Ralf

    P.S. what's the reason for the silly green LED on my light-board, can one switch it off? Or do I have to cover with black paint?

     
  • Ralf Dinkelmeyer

    P.S.
    Perhaps you will ask for the installed library: see attachement

     
  • brownrb

    brownrb - 2021-12-30

    not all esp32 chips wil run using the esp32time library.
    I do not have a list of them though.

    Dissabled ALL Real-Time-Clock (ESP32RTC was enebled, factory setting, didn't change)
    RTC from ESP32 seems not to work. I will test the external module ....

    you cannot change the state of the RTC because it is disabled,

     

    Last edit: brownrb 2021-12-30
  • elythomaslumber

    elythomaslumber - 2021-12-30

    P.S. what's the reason for the silly green LED on my light-board, can one switch it off? Or do I have to cover with black paint?

    I covered them with a black 3D printed plastic cap. Another way could be to desolder them or the easy way just to remove them with a wire cutter...
    There is no way to switch them off because they are not connected to a controller.

     
  • elythomaslumber

    elythomaslumber - 2022-01-06

    Hey guys,
    don´t know if Ralf has given up....?
    However just a short response from my side. After some weeks of waiting I received my IR-sensor. Out of the box after exnabling in the FW it works in combination with the BME280 from Adafruit and the TSL2591 from Adafruit. I tested the IR-sensor with an ice-cube holding above and the cloud cover values instantly drops from 100% to 0%.
    Regards and Happy new year to you all,
    Hardy

     
  • brownrb

    brownrb - 2022-01-07

    Well that is good news all round.
    We are busy working on the next public release at present., no firm date on when it will be posted here though.

    regards
    Robert

     
  • Ralf Dinkelmeyer

    Hey,
    yesterday the "real" BME280 arrived. Added also an external RTC. It is working!!!!
    Thanks for the support!
    Have to set up wonderground...

    I am working now on a project with an ESP32-CAM to realize alarm, photo+data transmission and remote control (power, dustcover, roof) of my remote observatory via telegram bot.

    regards Ralf

     
  • elythomaslumber

    elythomaslumber - 2022-01-08

    Hi Ralf,
    great to hear about your success finally! I'm soldering my final copper strip PCB board currently and after that I will design a special housing. Did some tests overnight especially with cloud detection. Sky temperature is changing rapidly when clouds arrive or disappear.
    My next project on this is the integration in my home automation system (DOMOTICZ) where I will switch some LED lamps as a warning signal if clouds will appear during a astro-photography session.
    Regards,
    Hardy

     
<< < 1 2 (Page 2 of 2)

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.