@teastain Thanks for the reply!
I'm actually not too worried about the LCD failing, unless it fails in such a way that it takes down the whole unit. I'm only going to have the LCD enabled for the initial setup, then it will be off. I know Expressif lists the ESP32 operating range as -40C to +125C.
I'm also running a COM.LTE in it. The SIM7600 lists -40C to +85C.
I guess I'll need to stick one out in the back yard next month and see what happens :)
Looking at the pinout diagrams with some refreshed eyes and I see it now... "PA" is short for "Port A" and "PC" is short for "Port C". And PA has a red background, like the red Port A connector, and PC is in the same light blue as Port C's connector.
Hi @felmue!
Good news! I got this working using the most ridiculous solution. My 220KiB test firmware would write in about 105 seconds, so approximately 2KiB/sec. I enabled mod_ratelimit on Apache and gave a 2KiB/sec rate limit to my firmware directory.
<IfModule ratelimit_module>
SetOutputFilter RATE_LIMIT
SetEnv rate-limit 2
</IfModule>
Now the firmware gets written at roughly the same rate at which it downloads, keeping the TCP session active the whole time, instead of the "burst then die while idle" connection behavior from before.
Thank you for all your help!
Hi all!
I figured I'd update this thread with my findings. I've been running a unit in my non-insulated plastic shed for two months of Canadian winter with no problems whatsoever. The screen turned on immediately and is perfectly fine. No unexplained lockups, reboots, or other glitches.
It has been a relatively warm winter (unfortunate for my testing). Inside the shed, it got down to -15C one weekend, but for the rest of the time, it has been between 0C and -6C. Humidity has been an average of 78% with a peak at 97%.
Hi all,
I have a number of COM.LTE modems running successfully with CoreBasic units. I was just going through some of my code to make a list of which pins are available for use when I noticed a reference to pin 2 during the modem initialization.
I see it show up in almost every sample config and forum post like this:
SerialAT.begin(115200, SERIAL_8N1, 5, 13);
pinMode(2, OUTPUT);
digitalWrite(2, 0);
delay(3000);
digitalWrite(2, 1);
What is the purpose of pin 2 here? Many of the examples will have a comment along the lines of "set pin 2 high for using the modem (simulates a power button press)".
My code doesn't have the two digitalWrite lines, but a single modem.restart() and it has been working fine. As an experiment, I tried removing the pinMode(2, OUTPUT) line in my code and reassigning it as an input connected to a toggle switch, and everything still seems to be fine.
Thanks!
aezero
I just made another discovery. If you power it up with the factory demo software, go the home screen, and then tap on "CORES3" six times, it puts you into a factory test mode
And on further examination, there's the dark grey PB_IN and PB_OUT pins, at G8 and G9. The splash screen when you power it on shows G8 and G9 are on Port B (there's a typo, saying "Port.C" but it's in the position of the black Port B connector).
Looking at the pinout diagrams with some refreshed eyes and I see it now... "PA" is short for "Port A" and "PC" is short for "Port C". And PA has a red background, like the red Port A connector, and PC is in the same light blue as Port C's connector.
@felmue
Hi Felix! Good to hear from you again!
Thanks for the clarification! The second serial connection is the blue connector, right?
Hi all!
I just got my first CoreS3 yesterday. I've been using the original Core with COM.LTE modules for a product/project I've been working on. I'd really like to start using the CoreS3 instead, as it has so many more features that are perfect for my project. But it looks like the M-BUS connector has a slightly different pinout. Am I able to use the COM.LTE with the CoreS3?
By default, the COM.LTE uses pins 5 and 13, which are listed as the GPIO and IIS_WS pins, respectively. On the CoreS3, those same pins are PA_SCL G1 and GPIO G7. Is the PA_SCL pin the SCL on the external red I2C connector? I do need that for some sensors.
I could use the DIP switches to change from using pin 5 to using 15 or 16. 15 was formerly IIS_OUT but is now I2S_DOUT, which I'm assuming is for the speaker, which I need. 16 was formerly RXD2 but is now PC_RX G18. Not sure what that pin is for.
Thanks! I'm so excited to get this new unit going!
aezero
Hi all,
From what I've read, there isn't a way to monitor the battery level on a Basic Core ESP32 using the Arduino IDE. Is there at least a way to monitor if the battery is present (ie that it hasn't failed)? There's M5.Power.isCharging(), but that will show as true even with the battery removed.
Thanks!
Hi all!
I figured I'd update this thread with my findings. I've been running a unit in my non-insulated plastic shed for two months of Canadian winter with no problems whatsoever. The screen turned on immediately and is perfectly fine. No unexplained lockups, reboots, or other glitches.
It has been a relatively warm winter (unfortunate for my testing). Inside the shed, it got down to -15C one weekend, but for the rest of the time, it has been between 0C and -6C. Humidity has been an average of 78% with a peak at 97%.
Hi all,
I'm planning on rolling out a few hundred M5 Basics for a project, and I'm hoping to be able to offload as much of the grunt work as possible to the junior techs (lol). If I export my code as a .bin file, what's the easiest way to get them to flash it onto brand new units? I was thinking I could just make them a little bundle with the .bin, esptool, and a batch file for them to run. I don't want to have them install the Arduino IDE and give them the source, just in case someone accidentally entered some characters, or there was a library that changed.
If they could flash multiple simultaneously, that would be even better.
Thanks in advance!