Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    DrBomb
    @DrBomb
    But again, you will need to manage modem power yourself
    needlerp
    @needlerp
    Ok great thanks @DrBomb. By power do you mean sleeping the modem etc?
    And are you running them from battery?
    DrBomb
    @DrBomb
    No. I mean actual power. Because the modem is turned off when power is first applied to it
    There's a KEY pin that needs to be pulsed for a few seconds to get the modem to turn on
    needlerp
    @needlerp
    Ah ok. I was hoping to be able to put the esp32 to sleep and then get it to wake using an interrupt from the modem when a message/text is received. Have you come across that?
    DrBomb
    @DrBomb
    Nope
    But the modem has a RING pin I believe. You could use it to wake up the esp from sleep. Or perhaps create an ULP program that does the AT commands for you. But that seems more difficult
    needlerp
    @needlerp
    Ok. Sounds like I need to get myself one and have a play!!
    needlerp
    @needlerp
    @captasic I suspect I’ll actually end up using uBlox Sara as that seems to be what Vodafone are championing in the UK. What sort of timescale are you looking at?
    Myles McNamara
    @tripflex
    when it comes to MOS and PSRAM (specifically ESP-WROVER) for ESP32 … does anybody have any issues, concerns, or thoughts regarding it? Right now we’re using ESP-WROOM-32 but looking at maybe switching to a ESP-WROVER
    mainly looking for a way to connect an external antenna and realizes that since space isn’t really an issue for us, plus with advancements since we started dev on this project — that may be good to look at going a different module
    Found the ESP32-WROOM-32U which has a u.fl connector … but that’s when i noticed the WROVER and thought to myself … well why am i still using a WROOM instead of WROVER
    needlerp
    @needlerp
    @tripflex I’m using WROVER-IB specifically because of the u.fl as my module is housed in a metal enclosure. No issues other than my own ignorance so far...
    Myles McNamara
    @tripflex
    @needlerp yeah i was looking at those too, ours is in a plastic enclosure, but some locations we install them already have bad wifi signal so using the PCB MIFA isn’t cutting it
    we can get signal on phone (which is still low) but sometimes doens’t even show up on the ESP32
    when i saw the WROVER i figured well possibly get more memory, an external connector … seems like a no-brainer
    in regards to the PSRAM .. is that something just natively available in MOS with the device or is it something that you would have to write code specifically to use?
    Liviu
    @nliviu
    @tripflex Enable the PSRAM:
      ESP_IDF_SDKCONFIG_OPTS: >
        ${build_vars.ESP_IDF_SDKCONFIG_OPTS} 
          CONFIG_SPIRAM_SUPPORT=y
          CONFIG_SPIRAM_BOOT_INIT=y
          CONFIG_SPIRAM_CACHE_WORKAROUND=y
          CONFIG_SPI_MASTER_IN_IRAM=y
    In the build_vars section of mos.yml
    Myles McNamara
    @tripflex
    ahhh okay thank you @nliviu
    is this in the docs somewhere? If not ill add code snippet to my awesome mongoose os list
    Liviu
    @nliviu
    @mamuesp was the first who published these settings.
    No, no docs.
    Just digging in the esp-idf configuration files.
    Enable 16MB flash size + PSRAM
    build_vars:
      # enable 16MB flash size + PSRAM
      ESP_IDF_SDKCONFIG_OPTS: >
        ${build_vars.ESP_IDF_SDKCONFIG_OPTS} 
          CONFIG_ESPTOOLPY_FLASHSIZE_4MB=
          CONFIG_ESPTOOLPY_FLASHSIZE_16MB=y
          CONFIG_ESPTOOLPY_FLASHSIZE=16MB
          CONFIG_SPIRAM_SUPPORT=y
          CONFIG_SPIRAM_BOOT_INIT=y
          CONFIG_SPIRAM_CACHE_WORKAROUND=y
          CONFIG_SPI_MASTER_IN_IRAM=y
    Manfred Müller-Späth
    @mamuesp

    @tripflex - Didn’t we discuss this theme some month ago? :wink: I added this setting too:

        CONFIG_SPIRAM_MALLOC_ALWAYSINTERNAL=512

    and it works like a charm,even with two SPI ports active, I always have plenty of memory …

    Myles McNamara
    @tripflex
    discuss the theme? which one? about WROVER vs WROOM or regarding awesome mos repo?
    Manfred Müller-Späth
    @mamuesp
    PSRAM was a theme here some month ago … ;-) No problem to ask, did only mention the fact …
    Myles McNamara
    @tripflex
    ahhh yeah i must not have been apart of it or seen it :-\
    so yeah that could help me as well as the 4mb of ram become huge issue had to go through an optimize a lot of code to bring down ram usage
    Manfred Müller-Späth
    @mamuesp
    Well, if you write all code in C, the memory consumption will decrease … (I’m doing that stepwise now). And together with littlevglI may just remove my display routines also written partly in mJS - this gives a lot of ease. In the moment I’m working woth a combination of D32PRO and the Wemos touch screen - so WiFi settings would be entered directly onto the device.
    needlerp
    @needlerp

    @tripflex I was still having errors running out of memory (sloppy coding combined with mjs) and had to include a couple of others at the end:

    build_vars:
    ESP_IDF_SDKCONFIG_OPTS: >
    ${build_vars.ESP_IDF_SDKCONFIG_OPTS}
    CONFIG_TCPIP_TASK_STACK_SIZE=6144
    ESP32_DEFAULT_CPU_FREQ_240=y
    CONFIG_SPIRAM_SUPPORT=y
    CONFIG_SPIRAM_IGNORE_NOTFOUND=y
    CONFIG_SPIRAM_BOOT_INIT=y
    CONFIG_SPIRAM_CACHE_WORKAROUND=y
    CONFIG_SPI_MASTER_IN_IRAM=y
    CONFIG_BT_ALLOCATION_FROM_SPIRAM_FIRST=y
    CONFIG_WIFI_LWIP_ALLOCATION_FROM_SPIRAM_FIRST=y

    Myles McNamara
    @tripflex
    @mamuesp yeah i’ve started to but a lot of it is in mjs so don’t cost effective to switch over just yet, i just had to make sure to minimize excessive mjs code
    Manfred Müller-Späth
    @mamuesp
    @needlerp - If you combine these settings in the wrong way, you’ll have fun with a lot of core dumps … :wink: So my addition mentioned above solved my problems you described.
    Myles McNamara
    @tripflex
    @needlerp thanks i will check out each of those to see what may be applicable to me
    Manfred Müller-Späth
    @mamuesp
    … and IGNORE_NOT_FOUND is not quite a good idea ...
    Myles McNamara
    @tripflex
    yeah very true @mamuesp that’s why i’m going to check each individually one by one
    right now my main concern is just with devices not able to connect to wifi — but if i can solve that an any other minor issues or upgrades along the way .. well count me in lol
    needlerp
    @needlerp
    @DrBomb how much are you sourcing SIM7500A for? I can’t find anything less than about $30
    needlerp
    @needlerp
    @mamuesp have I done something stupid with my settings? I haven’t had any problems...
    Manfred Müller-Späth
    @mamuesp
    @needlerp - Not directly, but when the test fails, you’ll get memory problems without knowing what caused them in the first place. My personal rule: if I want to use PSRAM, it will be tested in the boot sequence.
    needlerp
    @needlerp
    Ah ok. For a while I was running the same firmware on both Wroom and Wrover and needed it to not crash when PSRAM wasn’t present.
    I’m through that stage now so should probably remove it.
    DrBomb
    @DrBomb
    @needlerp Well, I'm not the one taking care of the BoM I'm afraid. But $30 sounds about right. It is a very powerful modem that is somewhat wasted on an esp32 heh.
    needlerp
    @needlerp
    Yeah, and will also kill my profit margin!!! There don’t seem to be many NB-IoT alternatives around though.
    DrBomb
    @DrBomb
    Indeed! At least on the SIMCOM front most of the modems are clearly aimed at devices that have USB interfaces like a SBC
    But that's meant to change with the CAT-M1 modems. They are meant to have less bandwidth, less power and cheaper. But the 7500A is what works for us right now!
    And our company moves too fast to prototype a different modem :P
    Captain ASIC
    @captasic
    @needlerp its becoming the standard for LTE-NB, supports USB, UART, SPI, etc, its an awesome module. I am in th eprocess of trying to relocate right now, but i have alredy purchased the modules to test with, i just need time. I'm new to programming from scratch, so no real timeline yet, but i would hope to release a super buggy beta by end of the year.