Skip to content

Releases: tschudin/vossbol

T-Beam firmware 20230731

31 Jul 21:48
Compare
Choose a tag to compare
Pre-release

Image for flashing the T-Beam. Has default LoRa settings only (AU915)

Flash as follows (replace port with your setup)

% esptool --chip esp32 --port /dev/tty.wchusbserial1234 --baud 921600 \
   --before default_reset --after hard_reset \
   write_flash -z --flash_mode dio --flash_freq 80m --flash_size 4MB \
   0x0 tinySSB-tbeam-firmware-0.1-20230731.bin

20230728 VoSSBoL

28 Jul 16:05
Compare
Choose a tag to compare
20230728 VoSSBoL Pre-release
Pre-release

VoSSBoL - Voice over tinySSB over LoRa

For BLE to work, the Android device must have Bluetooth and Location enabled.

20230621 VoSSBoL

21 Jun 13:29
Compare
Choose a tag to compare
20230621 VoSSBoL Pre-release
Pre-release

VoSSBoL - Voice over tinySSB over LoRa

For BLE to work, the Android device must have Bluetooth and Location enabled.

20220907 VoSSBoL (Android frontend and T-beam mesh firmware)

07 Sep 06:21
Compare
Choose a tag to compare

VoSSBoL - Voice over tinySSB over LoRa

This release contains both the firmware for T-Beam devices (ESP device with WiFi, LoRa and BT radios) and the Android app.

The app provides a user-facing interface to the tinySSB replication mesh, can capture text and voice messages, replicate them towards the mesh, and can replay them. The LoRa promise only applies to the mesh but we nevertheless call this the VoSSBoL app. The APK is provided in debug mode, hence is not signed nor optimized.

The T-Beam devices form, without need for configuration, a replicating wireless mesh, syncing their content among each other with Longrange Radio, and with Smartphones using BLE or WiFi. The firmware is packaged as a Zip file and ready to be used with the esp32-flash-tool. The Zip files also contains a 10-line shell script to flash your T-Beam devices without this tool.

What functions this release includes:

  • WiFi interface (using IP multicast) to the mesh of T-beam devices
  • Bluetooth Low Energy interface (no address config nor connect nor pairing actions needed)
  • the replication mesh supports up to 100 feeds and 2.5MB total feed storage

This is mostly a demo version and has zero management tools.

For BLE to work, the Android device must have Bluetooth and Location enabled. Note that a T-beam device can only serve one Android client at the time (this is a limitation of BLE on the T-beam devices - the use case is anyway that different Smartphones are syncing their data either with T-beam devices at different locations, or at different times).

20220905 VoSSBoL (Android frontend and T-beam mesh firmware)

05 Sep 04:57
Compare
Choose a tag to compare

VoSSBoL - Voice over tinySSB over LoRa

This release contains both the firmware for T-Beam devices (ESP device with WiFi, LoRa and BT radios) and the Android app.

The app provides a user-facing interface to the tinySSB replication mesh, can capture text and voice messages, replicate them towards the mesh, and can replay them. The LoRa promise only applies to the mesh but we nevertheless call this the VoSSBoL app. The APK is provided in debug mode, hence is not signed nor optimized.

The T-Beam devices form, without need for configuration, a replicating wireless mesh, syncing their content among each other with Longrange Radio, and with Smartphones using BLE or WiFi. The firmware is packaged as a Zip file and ready to be used with the esp32-flash-tool. The Zip files also contains a 10-line shell script to flash your T-Beam devices without this tool.

What functions this release includes:

  • WiFi interface (using IP multicast) to the mesh of T-beam devices
  • Bluetooth Low Energy interface (no address config nor connect nor pairing actions needed)
  • the replication mesh supports up to 100 feeds and 2.5MB total feed storage

This is mostly a demo version and has zero management tools.

For BLE to work, the Android device must have Bluetooth and Location enabled. Note that a T-beam device can only serve one Android client at the time (this is a limitation of BLE on the T-beam devices - the use case is anyway that different Smartphones are syncing their data either with T-beam devices at different locations, or at different times).