sp9unb
/
meshtastic-firmware
sforkowany z mirror/meshtastic-firmware
1
0
Forkuj 0
Kod Zgłoszenia Oczekujące zmiany Packages Projekty Wydania Wiki Aktywność
1 476 Commity
8 Gałęzie
195 Tagi
44 MiB
Wykres commitów

37 Commity (4b9ea4f8086e5bded68396598eb35d2174655f8a)

Autor SHA1 Wiadomość Data
Kevin Hester 4b9ea4f808 Merge branch 'dev' into coroutine 2020-10-10 09:22:23 +08:00
Kevin Hester 95cb6b06e4 fix #462 publish immediately on any GPS state change 
(don't wait until end of aquisition window)
 2020-10-10 09:20:38 +08:00
Kevin Hester 2044427e97 coroutines: wip compiles but does not link 2020-10-09 14:16:51 +08:00
Kevin Hester 4a70ba1f7a fix nodeinfo stored times (I think) for @lgoix 2020-10-09 10:01:13 +08:00
Kevin Hester 023f1c24fb RTC: add notion of 'quality' for different time sources 
Allow use of mesh based time until a GPS time arrives
 2020-10-08 07:46:20 +08:00
Kevin Hester f00d07baa3 RTC: pull rtc code into own file for cleanup 2020-10-08 07:28:57 +08:00
Kevin Hester 7480eb1826 Change to use zeros for timeout values that are 'default' 2020-10-06 09:43:00 +08:00
geeksville 3c0429deee Add new factory_reset preferences option clients can set 2020-09-19 11:19:42 -07:00
geeksville d3e28e3e2c Merge branch 'dev' 2020-09-17 11:20:41 -07:00
geeksville 8e988cc926 fix #397 from @a-f-G-U-C - bogus GPS positions during locking could be reported 
btw - from my read of the NMEA, the lowest value that means 'has a valid
position' is 1 not 2.  But I only know this because you pointed me at
it ;-)

Thanks!
 2020-09-16 09:18:44 -07:00
geeksville 8c240b59f6 fix #393. immediately save node db to disk if user changes name 2020-09-16 09:08:35 -07:00
geeksville 2a067e7f6b make gps optional. Portduino almost works in sim! 2020-09-06 14:45:43 -07:00
geeksville fefd3d78f3 Portduino WIP now compiles but does not link 2020-09-05 12:34:48 -07:00
geeksville 9b25818a50 fix #249: report battery levels even if no GPS lock 
@professr I noticed you added a "newStatus" observable to the GPS class.
Do you remember why you didn't remove the old GPS status (which seemed
to be dumber).  Is it just because you didn't want to risk breaking
MeshService?  (I assume) In this change I removed the old Observable
and all seems well (just using newStatus everywhere).
 2020-08-12 15:51:57 -07:00
geeksville ed589727d6 Update NRF52 build to work again 2020-07-09 19:57:55 -07:00
grcasanova 9803141fe7 merged with master 2020-07-06 21:53:10 +02:00
grcasanova 92b30ebec6 fixes now compiles 2020-07-06 10:45:55 +02:00
Professr f5b7c33d4e Refactored status handlers and merged 2020-06-28 18:17:52 -07:00
Professr 542b8b26ce Abstracted statuses, made display event-driven 2020-06-27 21:19:49 -07:00
geeksville 60470211e5 expose battery level via the standard BLE battery service 2020-06-22 10:04:26 -07:00
geeksville c5851a4a0c Report battery level to other nodes in mesh (and apps). 
Also today I'll turn back on the the standard "has a battery" BLE
device profile, so the locally connected radio should show up in the
phone's bluetooth popup of battery levels (similar to how a BLE
headphone battery level appears)

cc @lgoix - using code from @professr

```
meshtastic --info
Connected to radio...
my_node_num: 2883444536
has_gps: true
num_channels: 13
region: "unset"
hw_model: "tbeam"
firmware_version: "unset"
packet_id_bits: 32
current_packet_id: 91018534
node_num_bits: 32
message_timeout_msec: 300000
min_app_version: 172

preferences {
  position_broadcast_secs: 900
  send_owner_interval: 4
  wait_bluetooth_secs: 120
  screen_on_secs: 300
  phone_timeout_secs: 900
  phone_sds_timeout_sec: 7200
  mesh_sds_timeout_secs: 7200
  sds_secs: 31536000
  ls_secs: 3600
}
channel_settings {
  tx_power: 23
  modem_config: Bw125Cr48Sf4096
  psk: "\324\361\273: )\007Y\360\274\377\253\317Ni\277"
  name: "Default"
}

Nodes in mesh:
{'num': 2883444536, 'user': {'id': '!2462abdddf38', 'longName': 'Unknown df38', 'shortName': '?38', 'macaddr': 'JGKr3d84'}, 'position': {'altitude': 96, 'batteryLevel': 100, 'latitudeI': 375210641, 'longitudeI': -1223090398, 'time': 1592843564, 'latitude': 37.5210641, 'longitude': -122.3090398}}
```
 2020-06-22 09:36:19 -07:00
geeksville aadba1f694 add printPacket for debug printing packets 2020-06-14 15:30:42 -07:00
geeksville e124d2094f PROTOCOL CHANGE! activate 32 bit nodenums/packetids 2020-06-06 13:16:36 -07:00
geeksville 829e0b6e26 fix extra free 2020-05-25 08:19:14 -07:00
geeksville 9dd88281af reliable broadcast now works 2020-05-21 16:34:16 -07:00
geeksville 8bf4919576 wip reliable unicast (1 hop) 2020-05-19 11:56:17 -07:00
geeksville 976bdad067 sniffReceived now allows router to inspect packets not destined for this node 2020-05-18 17:57:58 -07:00
geeksville 26d3ef529e Use the hop_limit field of MeshPacket to limit max delivery depth in 
the mesh.
 2020-05-18 17:35:23 -07:00
geeksville b6a202d68e runs again with new protobufs 2020-05-12 13:35:22 -07:00
geeksville 1cc24de787 stub encryptor seems nicely backwards compatible with old devices and apps 2020-05-09 17:51:20 -07:00
geeksville 933d5424da abstract out the UBlox GPS driver 2020-05-04 11:15:05 -07:00
geeksville 9b309fe0a0 Use int based lat/long from now on in the device code 
for https://github.com/meshtastic/Meshtastic-device/issues/124
 2020-05-04 08:09:08 -07:00
geeksville ad2f639195 don't leak messages if they are handled locally 2020-05-02 19:53:13 -07:00
geeksville 5a4fab2506 start msg sequence numbers with a random number each boot 2020-05-01 08:51:53 -07:00
geeksville 82c1752d85 less logspam 2020-05-01 08:31:52 -07:00
geeksville 0096f54ae9 better debug output 2020-04-30 22:53:21 -07:00
geeksville dec4870649 begin cleaning up mesh library layer so that it could be split someday 2020-04-27 07:54:19 -07:00