So, LilyGO have a new T-Beam version 1.1, but detailed information appears lacking (again).
My experience with LilyGO is that they are very poor at providing and updating documentation. I also can’t remember having ever seen documentation that describes what’s new and other changes for new releases of their products. So we probably will have to rely on experiences from users of this board for more information.
LilyGO shows below pinout of the T-Beam v1.1 on the product page on their AliExpress shop but information about v1.1 (and even older versions) is not available on their T-Beam GitHub repository (yet).
T-Beam v1.1 pinout diagram:
To see full image size: Right-click image and select ‘open image in new tab’.
If someone has more information about the new T-Beam v1.1 then please share in this topic.
I compared the descriptions of v1.0 and v1.1. What I found in the v1.1 description which is not in the v1.0 one is the following:
There are 4 LEDs show the battery status in real time
Add reverse battery protection module
As I don’t have my T-Beam yet, does the v1.0 have 4 LEDs for battery indication and a battery protection module?
I ordered a v1.0 a few days ago, I thought that this is the newest version. Nevertheless, I hope that the differences are not that big. But at the moment, the v1.1 cost a little bit more than the v1.0. I ordered my v1.0 with an OLED screen for around 23$ (with shipping). I find the v1.1 one without an OLED screen for around 27$ (with shipping).
Hopefully they will come with written documentation that also describes what’s new and differences with different/previous versions of same products. (Until recently it was mostly ‘search the differences’ left up to the customer.)
v1.0 (luckily) does not have a 4-LED battery level indicator.
Hey guys. I’m a little late to the party but im having some issues with kizniche’s tracker sketch. I’ve been reading the issue requests on his Github and none of them are really helping me.
The problem I’m having is that I only get the activation message in TTN Console -> data, so im wondering what’s faulty about my setup.
I’ve used the right credentials for OTAA, set up my band in mcci project config and everything else thats provided in his readme.
Also, my end node is trying to activate itself over and over again with no uplink coming through.
This is the output from my activation tab:
Your example is about LoRa point-to-point connections while this forum is about The Things Network (TTN) and LoRaWAN. With LoRaWAN nodes send messages to gateways which forward the messages to a central TTN backend server where they are picked up by user applications.
LoRaWAN does not support point-to-point connections and latter are not supported on the forum.
There are not so many changes in schematics / parts of the most recent T-Beam v1.1 revision for paying attention to.
However, the PCB layout has been altered a little bit. Which makes older 3D enclosure for v1.0 to be no longer appropriate for v1.1
This is an illustration of all the ‘exterior’ updates:
I need help in case of OTAA. It just stays on EV_JOINING. I am using the hottimuc mapper. It works with ABP, though. What could that be? The frame counter looks a bit odd, too. Do you still need to reset frame counter when using OTAA? When I choose SF8 it says “OP_TXRXPEND, not sending”, what does that mean?
Sorry for the black bar on the top, that’s due to the refresh rate of the display.
I’ve edited the configuration to use the European frequency and i can see the join request on my gateway with the right device code app etc etc and i saw that the network server accept the join request but it seems nothing received back by my device.