Lilygo watch s3 issue #256
Comments
|
The AXP2101 battery management used by T-Watch-S3 is not calibrated for the battery, so the fuel gauge is inaccurate. It is more direct to get the voltage directly |
|
Ok, so how do I have this display more accurately?
Also what about my other question about it randomly powering up whenever it
wants with no reason?
…On Thu, Feb 6, 2025 at 11:54 PM Lewis He ***@***.***> wrote:
The AXP2101 battery management used by T-Watch-S3 is not calibrated for
the battery, so the fuel gauge is inaccurate. It is more direct to get the
voltage directly
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QIBAV5QZOUJWYOYYJ32ORREFAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGE3TOMBQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Random startup? Is it in shutdown mode? Or in sleep mode?The percentage cannot be accurate, which requires the support of xpower, which is not available to individuals. |
|
When it is completely off ( Golding crown for 6 seconds).
Sometimes come in and it has powered on itself…
What would cause this?
Last night I even tested this. Turned 10 watches off. Came back into
office this memory and 3 of them were on.
…On Thu, Feb 6, 2025 at 11:58 PM Lewis He ***@***.***> wrote:
Random startup? Is it in shutdown mode? Or in sleep mode?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QICATK2SB4TJS3SAZL2ORRTBAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGE4DMMRRHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Oh! This is not normal. If you long-press to turn off the phone, it shouldn't wake up. How long will it take for it to automatically turn on? Can you test it? |
|
There is no way for me to test it because it is just random sometimes.
Maybe 1-4 hours later and I notice one or 2 are on.
…On Fri, Feb 7, 2025 at 12:05 AM Lewis He ***@***.***> wrote:
Oh! This is not normal. If you long-press to turn off the phone, it
shouldn't wake up. How long will it take for it to automatically turn on?
Can you test it?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QKR2KEM4XQYXJFMR7L2ORSMLAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGE4TQNBQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I mean, does it always turn on automatically? Or sometimes it does and sometimes it doesn't? |
|
Sometimes it does, sometimes it doesn’t. Not always. And not all of the
watches…..no reason, just random.
Also our firmware is just lvgl and using your own library from GitHub.
…On Fri, Feb 7, 2025 at 12:09 AM Lewis He ***@***.***> wrote:
I mean, does it always turn on automatically? Or sometimes it does and
sometimes it doesn't?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QNGTMTJBR7ZHSTRD6T2ORS4RAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGIYDKOBWHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Also how do we get a battery meter to work properly?
And how would you optimize for battery longevity?
We are only able to get 2 hours or so right now which is way too little.
We need WiFi on for our esp32 to work and constantly receiving signals..,
On Fri, Feb 7, 2025 at 12:11 AM Matthew Alleva <
***@***.***> wrote:
… Sometimes it does, sometimes it doesn’t. Not always. And not all of the
watches…..no reason, just random.
Also our firmware is just lvgl and using your own library from GitHub.
On Fri, Feb 7, 2025 at 12:09 AM Lewis He ***@***.***> wrote:
> I mean, does it always turn on automatically? Or sometimes it does and
> sometimes it doesn't?
>
> —
> Reply to this email directly, view it on GitHub
> <#256 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BPH64QNGTMTJBR7ZHSTRD6T2ORS4RAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGIYDKOBWHE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
There are a few problems. Contact the customer service to resend them to you. Turning on wifi is bound to not save power. The average current consumption of turning on wifi is above 170mA. |
|
Which customer service? Resend what to me?
Also what do you mean current consumption of turning on WiFi is above
170mA?
17mah per what? Per hour?
I beleive the WiFi is mandatory for esp32 to work correct?
…On Fri, Feb 7, 2025 at 12:21 AM Lewis He ***@***.***> wrote:
There are a few problems. Contact the customer service to resend them to
you.
Turning on wifi is bound to not save power. The average current
consumption of turning on wifi is above 170mA.
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QJK5YNVVOS2SIZQH3T2ORUJBAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGIZDQNRSGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
|
Why do you think the brand new watches are faulty?
How do we get a calibrated battery meter?
How do we optimize to get more then 2 hours?
Why do the watches discharge at different rates with the same firmware?
…On Fri, Feb 7, 2025 at 12:26 AM Lewis He ***@***.***> wrote:
1. There are several devices with problems. Contact the dealer to
resend them to you.
2. The power consumption of turning on wifi is very high. You can
refer to the esp32s3 design manual.
image.png (view on web)
<https://github.com/user-attachments/assets/6004d4c0-346a-4932-994d-6165fde331ae>
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QJESKMIH537MQ3TL5T2ORU5DAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGIZTQOBXGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
A normal watch cannot automatically turn on after being completely turned off, so I judged it to be a malfunction. As I said, the fuel gauge is not calibrated, so the percentage has no reference value |
|
How do we calibrate? Is there a way to improve this or is it just a
useless feature?
How do we optimize to get more then 2 hours?
Why do the watches discharge at different rates with the same firmware?
…On Fri, Feb 7, 2025 at 12:58 AM Lewis He ***@***.***> wrote:
A normal watch cannot automatically turn on after being completely turned
off, so I judged it to be a malfunction.
As I said, the fuel gauge is not calibrated, so the percentage has no
reference value
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QKHNPMONGM463W6PTT2ORYUFAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGMYDGMZWGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
???
On Fri, Feb 7, 2025 at 1:00 AM Matthew Alleva <
***@***.***> wrote:
… How do we calibrate? Is there a way to improve this or is it just a
useless feature?
How do we optimize to get more then 2 hours?
Why do the watches discharge at different rates with the same firmware?
On Fri, Feb 7, 2025 at 12:58 AM Lewis He ***@***.***> wrote:
> A normal watch cannot automatically turn on after being completely turned
> off, so I judged it to be a malfunction.
>
> As I said, the fuel gauge is not calibrated, so the percentage has no
> reference value
>
> —
> Reply to this email directly, view it on GitHub
> <#256 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BPH64QKHNPMONGM463W6PTT2ORYUFAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGMYDGMZWGI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Are they? Or is that just the calibration issue? Have you tried running them to power off? |
|
What parameter do you mean by discharge rate? Have you tested the discharge current between devices with different discharge rates? Your application requires the wifi to be turned on for a long time, and it cannot be optimized too much. And if the wifi is turned on for a long time, it is obvious that this product is not suitable for this scenario. |
|
Also, while plugged in…why do some watches just turn on? Is it because
they are full charge?
…On Fri, Feb 7, 2025 at 5:51 PM Lewis He ***@***.***> wrote:
What parameter do you mean by discharge rate?
Have you tested the discharge current between devices with different
discharge rates?
Your application requires the wifi to be turned on for a long time, and it
cannot be optimized too much. And if the wifi is turned on for a long time,
it is obvious that this product is not suitable for this scenario.
You need to change to a device that supports a larger battery capacity.
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QLFTY5HNVE76JF3YYD2OVPIZAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBUGQZDANZUGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
PMU has the function of automatically turning on when USB is plugged in, and cannot be turned off |
|
Well…while plugged in, some will turn off. Some will not allow turning off…
…On Mon, Feb 10, 2025 at 10:42 PM Lewis He ***@***.***> wrote:
PMU has the function of automatically turning on when USB is plugged in,
and cannot be turned off
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QJH7MFCYYFTCOBZAY32PGLWHAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBZHE2DSOBUGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Also, when will the 940mah version of the t watch be available for
purchase?
On Mon, Feb 10, 2025 at 10:43 PM Matthew Alleva <
***@***.***> wrote:
… Well…while plugged in, some will turn off. Some will not allow turning
off…
On Mon, Feb 10, 2025 at 10:42 PM Lewis He ***@***.***>
wrote:
> PMU has the function of automatically turning on when USB is plugged in,
> and cannot be turned off
>
> —
> Reply to this email directly, view it on GitHub
> <#256 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BPH64QJH7MFCYYFTCOBZAY32PGLWHAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBZHE2DSOBUGQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
We have multiple t watches here by lilygo. We cannot get the lora to work.
We are on the correct frequency, and have flashed 2 watches with the
correct firmware supplied by lilygo. They still will not communicate with
each other.
Our own firmware also does not work, even though we flash our firmware to
other lora devices and it works just fine.
Here are even 2 examples from lilygo which won’t work on our t watch s3s
examples\radio\SX1262\SX126x_Receive examples\radio\SX1262\SX126x_Transmit
These examples
On Mon, Feb 10, 2025 at 10:43 PM Matthew Alleva <
***@***.***> wrote:
… Also, when will the 940mah version of the t watch be available for
purchase?
On Mon, Feb 10, 2025 at 10:43 PM Matthew Alleva <
***@***.***> wrote:
> Well…while plugged in, some will turn off. Some will not allow turning
> off…
>
> On Mon, Feb 10, 2025 at 10:42 PM Lewis He ***@***.***>
> wrote:
>
>> PMU has the function of automatically turning on when USB is plugged in,
>> and cannot be turned off
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#256 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/BPH64QJH7MFCYYFTCOBZAY32PGLWHAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBZHE2DSOBUGQ>
>> .
>> You are receiving this because you authored the thread.Message ID:
>> ***@***.***>
>>
>
|
|
Did you write directly into the example? Did you change the frequency setting? What does the serial display show? |
|
Yes, I did. No, frequency is set correctly to watch.
Serial display?
…On Mon, Feb 17, 2025 at 1:45 AM Lewis He ***@***.***> wrote:
Did you write directly into the example? Did you change the frequency
setting? What does the serial display show?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QOXDJ5QBB55BG7RL6L2QGVTDAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRSGU3TCNZVGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
Did you write directly into the example? Did you change the frequency
setting? What does the serial display show?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QOXDJ5QBB55BG7RL6L2QGVTDAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRSGU3TCNZVGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
The receive example doesn't show up on the screen but prints on the serial, can you post the example you used? |
|
The example has been updated, you can test it |
|
Why are we perfectly capable of getting the esp32 to work on the watches
but not the Lora? It seems like a hardware issue.
We would just continue to use esp32 except it is unreliable at times with
signals, and the battery drain is massive.
Please help!
…On Mon, Feb 17, 2025 at 1:50 AM Lewis He ***@***.***> wrote:
The example has been updated, you can test it
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QL4NY27YHTFBFEP6BD2QGWEXAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRSGU4DGMZWGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
The example has been updated, you can test it
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QL4NY27YHTFBFEP6BD2QGWEXAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRSGU4DGMZWGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Why can't LoRa run? Can't the above two examples run? ESP32's wifi consumes a lot of power. This is a known problem. There is no other solution. |
|
And is this transmitter or receiver?
…On Mon, Feb 17, 2025 at 11:40 PM Lewis He ***@***.***> wrote:
build.zip <https://github.com/user-attachments/files/18840792/build.zip>
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QPYH3NOU562BZ2Y4WT2QLPYLAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUHAZTKMRRGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
build.zip <https://github.com/user-attachments/files/18840792/build.zip>
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QPYH3NOU562BZ2Y4WT2QLPYLAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUHAZTKMRRGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
There are two firmwares, corresponding to sending and receiving. These are the firmwares for the two functions. esptool flashing, address 0x0 |
What does that mean? |
|
What frequency is on these firmware?
…On Tue, Feb 18, 2025 at 12:30 AM Samuel Sieb ***@***.***> wrote:
They won’t run.
What does that mean?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QI5UH4K3HNAKZIWFJ32QLVSRAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUHEZDQMRUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: ssieb]*ssieb* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
They won’t run.
What does that mean?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QI5UH4K3HNAKZIWFJ32QLVSRAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUHEZDQMRUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
No need to select other options, just write this file to address 0x0, no other options. If you use espdownloadtool, no need to select other options, just keep the default |
|
Yes this file seems to communicate. But what frequency is this on? We
need to adjust our own transmitters to meet your watches. I need frequency
please.z
…On Tue, Feb 18, 2025 at 12:46 AM Lewis He ***@***.***> wrote:
No need to select other options, just write this file to address 0x0, no
other options. If you use espdownloadtool, no need to select other options,
just keep the default
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QP2M4YTNBFBKL37NID2QLXNHAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUHE3DAOBQGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
No need to select other options, just write this file to address 0x0, no
other options. If you use espdownloadtool, no need to select other options,
just keep the default
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QP2M4YTNBFBKL37NID2QLXNHAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUHE3DAOBQGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This one uses 868M |
|
We have gotten the lore module to work. But the range seems terrible.
How much range distance should the lilygo watch be capable of?
…On Tue, Feb 18, 2025 at 12:51 AM Lewis He ***@***.***> wrote:
This one uses 868M
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QKBLZRRO32MNKCPG232QLYB3AVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUHE3TEOJSHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
This one uses 868M
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QKBLZRRO32MNKCPG232QLYB3AVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUHE3TEOJSHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
The open distance is at least one kilometer. If there are obstacles in the middle, the distance will be lost a lot. |
|
Well, we just used our hardware with added internal antenna. 50 feet lost
connection, no signals being accepted by the watch.
Rssi - 25 with 1 foot distance.
Rssi- 60 with 10 foot distance
Rssi - 118 with 30 foot distance.
No signals at 50 feet…..
…On Tue, Feb 18, 2025 at 11:15 PM Lewis He ***@***.***> wrote:
The open distance is at least one kilometer. If there are obstacles in the
middle, the distance will be lost a lot.
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QO3R5IZZHSISC6XFFT2QQVQZAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXG4YDAMRSG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
The open distance is at least one kilometer. If there are obstacles in the
middle, the distance will be lost a lot.
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QO3R5IZZHSISC6XFFT2QQVQZAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXG4YDAMRSG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
are you saying 1km with Lora? Or loRaWAN?
On Tue, Feb 18, 2025 at 11:17 PM Matthew Alleva <
***@***.***> wrote:
… Well, we just used our hardware with added internal antenna. 50 feet
lost connection, no signals being accepted by the watch.
Rssi - 25 with 1 foot distance.
Rssi- 60 with 10 foot distance
Rssi - 118 with 30 foot distance.
No signals at 50 feet…..
On Tue, Feb 18, 2025 at 11:15 PM Lewis He ***@***.***>
wrote:
> The open distance is at least one kilometer. If there are obstacles in
> the middle, the distance will be lost a lot.
>
> —
> Reply to this email directly, view it on GitHub
> <#256 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BPH64QO3R5IZZHSISC6XFFT2QQVQZAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXG4YDAMRSG4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
> [image: lewisxhe]*lewisxhe* left a comment
> (Xinyuan-LilyGO/TTGO_TWatch_Library#256)
> <#256 (comment)>
>
> The open distance is at least one kilometer. If there are obstacles in
> the middle, the distance will be lost a lot.
>
> —
> Reply to this email directly, view it on GitHub
> <#256 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BPH64QO3R5IZZHSISC6XFFT2QQVQZAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXG4YDAMRSG4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
Of course it refers to LoRa. If there is LoRaWAN, the distance is farther. What parameters and frequencies did you use? BW,CW, SF, TX POWER, these key parameters affect the distance. If you don’t understand, please check the relevant parameters of lora. This example tells you how to set these parameters. |
|
Our issue now, is watch to watch is fine, bitcwatch to our own pcb is not.
If using the stock firmware on watch it is getting very poor rssi from our
pcb. But if we try to adjust ANY parameters on the watch firmware then it
no longer receives signals…
…On Tue, Feb 18, 2025 at 11:21 PM Lewis He ***@***.***> wrote:
Of course it refers to LoRa. If there is LoRaWAN, the distance is farther.
What parameters and frequencies did you use?
BW,CW, SF, TX POWER, these key parameters affect the distance. If you
don’t understand, please check the relevant parameters of lora.
This example tells you how to set these parameters.
https://github.com/Xinyuan-LilyGO/TTGO_TWatch_Library/tree/t-watch-s3/examples/radio/SX1262/SX126x_Settings
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QKD3ZUUN2N5LDEIFTD2QQWGPAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXG4YDSMZWGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
Of course it refers to LoRa. If there is LoRaWAN, the distance is farther.
What parameters and frequencies did you use?
BW,CW, SF, TX POWER, these key parameters affect the distance. If you
don’t understand, please check the relevant parameters of lora.
This example tells you how to set these parameters.
https://github.com/Xinyuan-LilyGO/TTGO_TWatch_Library/tree/t-watch-s3/examples/radio/SX1262/SX126x_Settings
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QKD3ZUUN2N5LDEIFTD2QQWGPAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXG4YDSMZWGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
What type of LoRa does your PCB use? |
|
Sx1262
…On Thu, Feb 20, 2025 at 2:25 AM Lewis He ***@***.***> wrote:
What type of LoRa does your PCB use?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QMVTCSRX7NTEOGQXTL2QWUQXAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGA3TIMZWGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
What type of LoRa does your PCB use?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QMVTCSRX7NTEOGQXTL2QWUQXAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGA3TIMZWGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
What parameters are used, is the LoRa at a uniform frequency, and does the hardware pre-filter match the frequency set by the software? |
|
If we use the stock firmware you provided, and our firmware on PCB, it gets
extremely poor signal. Then if we adjust your firmware or parameters even 1
thing, we get white screen upon boot up with no “waiting for transmission”
message.
On serial monitor, the watch seems fine and says it’s “searching” but
receives nothing.
On Thu, Feb 20, 2025 at 2:25 AM Matthew Alleva <
***@***.***> wrote:
… Sx1262
On Thu, Feb 20, 2025 at 2:25 AM Lewis He ***@***.***> wrote:
> What type of LoRa does your PCB use?
>
> —
> Reply to this email directly, view it on GitHub
> <#256 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BPH64QMVTCSRX7NTEOGQXTL2QWUQXAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGA3TIMZWGU>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
> [image: lewisxhe]*lewisxhe* left a comment
> (Xinyuan-LilyGO/TTGO_TWatch_Library#256)
> <#256 (comment)>
>
> What type of LoRa does your PCB use?
>
> —
> Reply to this email directly, view it on GitHub
> <#256 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BPH64QMVTCSRX7NTEOGQXTL2QWUQXAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGA3TIMZWGU>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
Whenever we set these parameters on both the watch, and the transmitter,
then we receive no messages.
radio.setSpreadingFactor(12); radio.setCodingRate(6);
radio.setBandwidth(125.0); radio.setPreambleLength(8);
…On Thu, Feb 20, 2025 at 2:28 AM Lewis He ***@***.***> wrote:
What parameters are used, is the LoRa at a uniform frequency, and does the
hardware pre-filter match the frequency set by the software?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QOCMWPKFDYDTMQ6BKL2QWU4NAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGA4DCNZSGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
What parameters are used, is the LoRa at a uniform frequency, and does the
hardware pre-filter match the frequency set by the software?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QOCMWPKFDYDTMQ6BKL2QWU4NAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGA4DCNZSGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
To solve the problem, please post your minimal test code. And tell us your test setup. |
|
We’ve got lots paired to the watch. The main issue now is:
Anytime we change some parameters, the watch stops getting signals all
together from the transmitter.
Also, it will get smaller messages, but anything more than 5 character
message it will not receive?
…On Thu, Feb 20, 2025 at 10:29 PM Lewis He ***@***.***> wrote:
To solve the problem, please post your minimal test code. And tell us your
test setup.
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QNLUEU4OLB372ZBYW32Q3BTDAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZTGU4DONBXGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
To solve the problem, please post your minimal test code. And tell us your
test setup.
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QNLUEU4OLB372ZBYW32Q3BTDAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZTGU4DONBXGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
The transmitter and receiver of LoRa must use the same parameters to receive. Do you know this? Any different parameters will be filtered out. The maximum payload is 255. The larger the payload, the longer the transmission time. If the transmission speed is too high, some messages will definitely be lost. |
|
How our issues are different. Seems like it takes a long time sometimes to
get response from your technical team.
Currently with Lora are only getting 3 hours of battery life which is
terrible. Even esp32 got 3.5….
What could cause such a massive draw?
…On Mon, Feb 24, 2025 at 1:10 AM Lewis He ***@***.***> wrote:
The transmitter and receiver of LoRa must use the same parameters to
receive. Do you know this? Any different parameters will be filtered out.
The maximum payload is 255. The larger the payload, the longer the
transmission time. If the transmission speed is too high, some messages
will definitely be lost.
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QL4ZFOJCWWHHRPKMI32RLOW7AVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZXHAYDIMZYGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
The transmitter and receiver of LoRa must use the same parameters to
receive. Do you know this? Any different parameters will be filtered out.
The maximum payload is 255. The larger the payload, the longer the
transmission time. If the transmission speed is too high, some messages
will definitely be lost.
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QL4ZFOJCWWHHRPKMI32RLOW7AVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZXHAYDIMZYGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Under what circumstances was the 3-hour lifespan estimated? Screen status? WiFi status? LoRa on? How do you control so many peripherals? Is there deep sleep? Or light sleep? Is the operating frequency reduced? What is the backlight level? |
|
Let’s start by discussing.
When I told you my issue, you said to switch over to Lora and it would
drastically improve battery life over esp32.
After $2,000, and 10 days of rebuilding, That is not the case….same UI,
same everything.
…On Mon, Feb 24, 2025 at 5:22 PM Lewis He ***@***.***> wrote:
Under what circumstances was the 3-hour lifespan estimated?
Screen status? WiFi status? LoRa on? How do you control so many
peripherals? Is there deep sleep? Or light sleep? Is the operating
frequency reduced? What is the backlight level?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QIY4SYNWGYRNFKWTED2RPAVZAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBQGEZDANBQGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
Under what circumstances was the 3-hour lifespan estimated?
Screen status? WiFi status? LoRa on? How do you control so many
peripherals? Is there deep sleep? Or light sleep? Is the operating
frequency reduced? What is the backlight level?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QIY4SYNWGYRNFKWTED2RPAVZAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBQGEZDANBQGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
|
What is the default current limit on the LoRa?
…On Mon, Feb 24, 2025 at 5:31 PM Lewis He ***@***.***> wrote:
1. It is generally accepted that LoRa consumes less current than WiFi
during transmission
2. What kind of optimization have you done to improve the lifespan?
Just like the question I mentioned above, what have you done to save power
consumption?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QIANBWTWLGNSVKCJIL2RPBVTAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBQGEZTANZSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: lewisxhe]*lewisxhe* left a comment
(Xinyuan-LilyGO/TTGO_TWatch_Library#256)
<#256 (comment)>
1. It is generally accepted that LoRa consumes less current than WiFi
during transmission
2. What kind of optimization have you done to improve the lifespan?
Just like the question I mentioned above, what have you done to save power
consumption?
—
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPH64QIANBWTWLGNSVKCJIL2RPBVTAVCNFSM6AAAAABWVIQRK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBQGEZTANZSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Spreading factor - 9 |
|
Saving power consumption is achieved by sleeping, turning off the screen, reducing the backlight, reducing the operating frequency, and turning off unnecessary peripherals, rather than saving power by setting LoRa parameters. LoRa consumes a large current only when Tx, and maintains a current of several mA at other times |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have uploaded our own firmware onto these watches. It seems with no rhyme or reason, occasional a watch will turn itself on without me turning it on. Is there something in the hardware making it do this?
We also have noticed the battery being volatile.
I opened 10 brand new watches directly from lilygo and charged them to 100%.
Turn them all on, set them all on the test table.
2 hours later, some of them are 10-15%, one st 38%, some in 50-60%c and one at 89%.
How is this possible? Faulty batteries from lilygo? Something drawing the battery heavily?
Please help. Thanks.
The text was updated successfully, but these errors were encountered: