That looks like a nice antenna connector construction.
The U.FL/IPEX is default and if you want to have SMA instead an SMA connector can be mounted? (and in your preferred own direction)
I think that U.FL/IPEX LoRa antenna connector construction is also preferred for the LoRa32 V2.1.
I gives more flexibility for positioning the device in an enclosure.
Yes , they just replace the SMA connector by an U.fl .
they made the requested changes because that don’t change the PCB layout.
Now I ask for PCB modifications , just waiting for they answer ( min Order and condition ).
We need lot of Lora32 V2.1 board ,( will be tested as an one buton call system for our lone workers )
So if any modifications needed , just ask , i can suggest them . ( and yes , the first one I asked is the SMA replacement )
I have not been able to get ‘next to zilch’ results here. See below. Maybe redo some tests?
I performed tests on 9 OLED I2C display modules. 6x SSD1306 0.96" 128x64, 2x SSD1306 0.91" 128x32 and 1x SH1106 1.3" 128x64. Tests were performed with two different libraries: U8x8 (U8g2) and Adafruit SSD1306 + Adafruit GFX Library. The libraries made no difference for power usage.
Tests were performed with OLED display modules powered from 3.7V Li-Ion battery via HT7333 3.3V voltage regulator (different power source than MCU). Currents were measured with EEVBlog uCurrent Gold (mA range used for display on, uA range used for display off/power-save).
Results:
Display Type All pixels off 50% pixels on 100% pixels on
Display on/off Display on/off Display on/off
A 0.96" 128x64 1.4mA / 13.7uA 8.7mA / 13.7uA 11.4mA / 13.7uA
B 0.96" 128x64 1.5mA / 12.8uA 9.6mA / 12.8uA 13.2mA / 12.8uA
C 0.96" 128x64 1.6mA / 7.7uA 14.7mA / 7.7uA 24.3mA / 7.7uA
D 0.96" 128x64 1.5mA / 32.5uA 9.9mA / 32.5uA 14.1mA / 32.5uA
E 0.96" 128x64 1.5mA / 7.0uA 16.4mA / 7.0uA 29.4mA / 7.0uA
F 0.96" 128x64 1.5mA / 8.4uA 16.1mA / 8.4uA 27.9mA / 8.4uA
G 1.3" 128x64 2.2mA / 7.4uA 22.4mA / 7.4uA 30.1mA / 7.4uA
H 0.91" 128x32 2.2mA / 8.3uA 16.7mA / 8.3uA 21.8mA / 8.3uA
I 0.91" 128x32 2.0mA / 8.1uA 18.7mA / 8.1uA 33.1mA / 8.1uA
Conclusions
It does not matter how many pixels are on when display is off/in power-save (as expected).
Quite some differences in power usage, both in normal display mode and with display off/low-power.
Lowest power usage of the 9 displays with display off/in power-save is 7.0 uA.
Highest power usage of the 9 displays with display off/in power-save is 32.5 uA.
For best low-power results one should switch off the display power.
Why would I need to do more tests, there was nothing wrong with the ones I did already ?
I will be rebuilding a new version of the board in the next couple of weeks which includes the resistors to keep the LoRa device current down, I removed them from the current board.
My ESP32 board (now without LoRa device) with a FRAM, TC74 temperature sensor and SSD1306 display has a total sleep current of 7.7uA.
All my OLED modules have an on-board XC6206 (‘662k’) low-power LDO voltage regulator.
This may be of influence on the display module’s power consumption but according to the datasheet the XC6206’s power consumption is only 1uA typical and 3uA max.
Not sure what you mean. The HT7333 was used to separately power the display modules with 3.3V during the tests (separate from MCU power). The display modules were directly powered from a Li-Ion cell via HT7333 (without using any switching buck or boost converters in between).
I only measured currents used by the display modules (isolated). Any losses caused by HT7333 are not part of the measured results. The measured results are independent from internal losses of the HT7333, so there is no need to swap it.
Hmm, so what’s your secret sauce to bring the board down to 7 microamps in sleep mode, if only the OLED draws 7-8 microamps? Do you have a switch for the OLED?
Carefully studying the pictures reveals that, unfortunately, (when compared to V2) several pins and GPIO ports have been removed. The previous V2.1 was even worse in that aspect.
anyone with a TTGO LORA32 with GPS (think at least @Verkehrsrot and @Charles got one?) happens to know if there’s working ttn-mapper-code yet? ordered one and had hoped someone would have started working on that by the time it arrives, but it came sooner than expected will be on a roadtrip to poland on monday which would be a nice … well … testdrive, but with my limited coding abilities it’s definitly too little time to get anything working from scratch by then…
thanks for any hints.