Sorry I’ve been away the last few weeks. I’ll be back more soon but I’m also working with the other devs so that people besides me can push out releases. The other devs have done some great things while I was away:
@a-f-G-U-C improved lots of GPS handling (and laid the groundwork for advance usages in the future)
@sachaw did work to update the Web UI to work with the latest device code
@claesg fixed sleep behavior on the RAK NRF52 boards
@osmanovv added support for a new board (which is mostly only used in Russia currently)
@ducky64 fixed T-Echo to work with these latest changes
I added some beginning support for BL602 based boards
If brave alpha testers could report back with their feedback on how this release works for them it would be appreciated. Over the weekend (if feedback seems good), I’ll push out an android build that includes this firmware and some other fixes.
I still have the problem where the T-echo disk will mount, it’s possible to drop the .uf2, but the screen still remains on the factory installed softrf.
If anyone knows how to factory reset a t-echo, I’d love to hear!
I tried installing the POST from the link you suggested, thanks. Strangely it didn’t work, but when I installed the v 1.0 of SoftRF, that seems to work on runs the POST screen. The screen then updates, it’s possible to switch between screens, but it flickers a lot, in tune with the LED blinking alternately blue and green.
Still no luck with meshtastic though…
I’m having trouble with persisting the fixed position coords via the python api not appearing to save now.
This is with the latest 1.2.40 version of the python API.
I’m wondering if the GPS location work unearthed a new bug possibly, or is work needed on the python api to change something now that the GPS changes are in the device code?
I’m having trouble with the web pages, meshtastic.local and meshtastic.local/static are completely blank. I was using the device-install.sh script. 1.2.44 is working just fine.
after more testing, T-Echo still seems to consistently freeze after some time. before, only disconnecting bluetooth was needed, now steps to reproduce are different:
for me only happened on battery power (not on USB power);
bluetooth connection & battery percentage doesn’t seem to matter (from 80% to 50%);
plugging USB cable seems to bring back from sleep (doesn’t require reset, like before).
behaves a lot as if the device had run out of battery (except it doesn’t display “Sleeping…” with Meshtastic version and logo).
This is the behaviour I saw on the RAK4631. It would go to sleep on a low battery reading after a few days even if the battery was above 50%. I added a counter for the low battery readings and if there was 4 low readings in a row then go to sleep. This change was introduced in the 1.2.46 build. I don’t think it can have made things worse for the T-Echo.
I had some temporary printouts added when I was implementing the counter but I think some printouts are there by default. The problem is that you need to have the usb cable attached to get the serial log and then it is charging. I tried to cut the red positive wire in the usbcable but then it disconnected. It looks like (on the RAK4631) the usbchip is powered from the usbcable.
To be able to track powerlevels I had another meshtastic device connected to the computer and ran ‘meshtastic --nodes’ every 20 minutes. Then you get a good view of battery level on all nodes in the network and you can see when one has gone to sleep and the last time it was seen.
My t-echos are still showing the usual no gps lock, no sats with 1.2.46 I’m afraid. They also need usb power to get a response from the buttons. As anyone tried to disable sleep? Thanks.
I still have the reset problem with my T-echos. The reset button only works when the device is powered by usb. The only version of Meshtastic firmware that fixed this problem was the one released by Lilygo github.
The gps still has the problem that the sign of the longitude value flips randomly. I am using an indoor gps repeater, and the gps works fine with SoftRF, so it’s definitely not due to hardware or weak gps signal.
Right now the Discord server is likely the best place to get timely help. Another option is open a bug on the projects git hub page, but that could take a while depending on if a dev other than geeksville sees it.
Thanks @AndreK for the summary. I had a question about the t-echo. I would like to use platformio to (possibly) understand more about why my t-echos are not working. However I need a J-link - as anyone a recommendation for which J-link to use? Thanks.
