Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Heltec Capsule Sensor V3 to the Meshtastic source code #4086

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

Heltec-Aaron-Lee
Copy link
Contributor

This commit includes the following functions for Capsule Sensor V3:

  • Add Heltec Capsule Sensor V3 hardware definition,
  • Button status read.
  • Battery level read,
  • Charging status detection.

The following functions are tested before submission:

  • The whole project compile, build, and firmware update,
  • Bluetooth connect to an Android/IOS phone,
  • GPS read;
  • LoRa transmission and reception,
  • Mesh network communication.

Going to do in the next PR:

  • Various sensor drives and running on Capsule Sensor V3;
  • Sensor data read, monitor, and transmit.

@caveman99 caveman99 merged commit 78fd17c into meshtastic:master Jun 12, 2024
84 of 85 checks passed
@meshtastic-bot
Copy link

This pull request has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/heltec-capsule-sensor-v3/10638/51

@nolith
Copy link

nolith commented Jul 23, 2024

Hello @Heltec-Aaron-Lee

I was playing with an heltec sensor capsule v3 with GPS.

I was hoping to run it as a TRACKER mode where the device sends the position and then goes into a sleep mode until the next event.

From the battery runtime I have the impression that the device isn't sleeping. Is this a limitation of the firmware or the hardware?

For my project it will be ok even to use a deep sleep state as long as the device can get back online, get a fix, and send a position on a given interval.

@thebentern
Copy link
Contributor

Hello @Heltec-Aaron-Lee

I was playing with an heltec sensor capsule v3 with GPS.

I was hoping to run it as a TRACKER mode where the device sends the position and then goes into a sleep mode until the next event.

From the battery runtime I have the impression that the device isn't sleeping. Is this a limitation of the firmware or the hardware?

For my project it will be ok even to use a deep sleep state as long as the device can get back online, get a fix, and send a position on a given interval.

Device role of Tracker and power.is_power_saving true will give you the behavior you want.

@nolith
Copy link

nolith commented Jul 23, 2024

Thanks @thebentern

In the iOS UI that setting is not available for the heltec sensor capsule, but I was able to set it using the python CLI and the admin channel.

I'll report back on battery usage.

If I understood correctly, now my only relevant setting is the positon broadcast interval, that one will set my sleep schedule, is that correct?

@andres-a-git
Copy link

As with today's state, is it safe to use the Heltec V3 from Meshtastic web flasher or should we use something else from here or use the FW from Heltec page?

@fifieldt
Copy link
Contributor

fifieldt commented Nov 5, 2024

@andres-a-git , should work fine!

@andres-a-git
Copy link

@andres-a-git , should work fine!

I was already trying to flash it over wifi serial, but did not finalize the flashing. I assumed that the serial over wifi could be also used, but discovered that the Arduino IDE may not help. Luckily stumbled to the FW page:
https://github.com/meshtastic/meshtastic.github.io/tree/master/firmware-2.5.9.936260f

From here I found the special capsule FW and downloaded the update version.
image

The update .bin wth long name was not accepted by the Heltec WiFi flasher page, so I renamed it to firmware.bin and uploaded it to the capsule over Wifi. Now the capsule works as before, but with new FW :)

Would it be possible to add the option for Capsule to download the FW bin already from the flasher.meshtastic.org page like it is done with UF2 files on RAK devices?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants