Для "дрыгания" ногами heltec v4 и heltec t114 нужно собрать firmware самостоятельно с опцией удаленного управления gpio.
Ну собственно все заработало.
#мештастик #meshtastic #heltecv4 #heltecht114 #heltect114v2

#MeshCore v1.14.1 is out with a fix that regularly syncs time via GPS.

The reason: clock drift especially with powersaving on 🌞🔋

https://github.com/meshcore-dev/MeshCore/pull/1350

This confirms the clock drift of 30+ minutes that I'm seeing after a week or so on my #HeltecV4 (esp32) with powersaving on.

Unfortunately these small devices do not come with a GPS module by default and the GPS module itself would also use up more power:

https://chaos.social/@djh/116240840413091152

Does not look good for solar repeaters ☹️

@finn What a coincidence! I'm trying to tackle this very issue right now. My #heltecv4 reboots on TX if the battery is under 3.7V and power is set to 22 dBm+.

I tried to insert a 1000uF cap just like you did, but it didn't work. I measured the voltage sag and it takes way longer to recover to baseline, whereas the capacitor can handle it just for a fraction of a second.

I wonder what I'm doing wrong... My temp solution was reducing TX power, which negates the only advantage of having a V4 😮‍💨

My remote #HeltecV4 #MeshCore solar repeater has a clock drift of about 20+ minutes after a week already.

On meshcore v1.14 with powersaving on. Tried clkreboot and synced clock already; second week and just happened again.

Anyone else experiencing massive clock drift on their heltec v4?

Товарищи радиолюбители, а кто знает, как мне прикрутить в #heltecv4 или в #heltect114 какой-то датчик или несколько и типа удаленно запрашивать их состояние?
Тут наверное вопрос даже не в конкретной реализации для конкретного датчика, а есть ли API в #мештастик #meshtastic для этого?
Датчики могут быть разные, лазерный дальномер, датчик силы тока и напряжения, разные. SPI и I2C в основном.
#lora

Interesting tx power measurements for #HeltecV4 on #MeshCore 🔋

Summary: Set tx to 10-17 dBm; bigger tx values increases power consumption by a lot for very little benefit:

https://github.com/meshcore-dev/MeshCore/issues/1708

That plus powersaving changes in v1.13 and now v1.14 will make these devices viable solar powered repeaters 😍

Heltec V4: Measured TX Power Output Table (firmware setting vs actual conducted dBm) · Issue #1708 · meshcore-dev/MeshCore

Heltec V4: Measured TX Power Output Table (firmware setting vs actual conducted dBm) Update: @towerviewcams followed up with a more rigorous test using a calibrated Rohde & Schwarz NRX power meter ...

GitHub

Idea: Something like the #HeltecV4, but in m.2 form. it would expose a serial interface with which the host OS can communicate. Bonus points for separate rx and tx antennas.

This would enable us to deliver the whole solution in a single enclosure (a #Protectli appliance).

Quite confused as to how I'm supposed to get the #HeltecV4 EEPROM back in a good state after using rnodeconf --eeprom-wipe.

I'm getting this kind of error when trying to use rnodeconf on the device post-flash:

[19:13:23] Reading EEPROM...
[19:13:24] This device contains a valid firmware, but EEPROM is invalid.
[19:13:24] Probably the device has not been initialised, or the EEPROM has been erased.
[19:13:24] Please correctly initialise the device and try again!
``

#Reticulum

I ordered 2x #HeltecV4 devices a few days ago. They're supposed to arrive today, but it hasn't even left the origination facility.

Either way, I'm excited to toy around with #Reticulum and #MeshCore with them.

I also bought two outdoor solar kits, so I'm hoping these will be permanent fixtures. I also need to figure out what can survive a harsh Colorado hail storm.

If this next test goes well, I'll acquire a #LoRaWAN device and start experimenting with that.

I'm inching closer towards an initial proof-of-concept set of hardware gear for use in the #HardenedBSD censorship- and surveillance-resistant low-cost (or free in certain cases) mesh network.