Ttgo T-beam


#21

UPDATE the config.h file in the same folder WITH YOUR TTN KEYS AND ADDR.


(Costel) #22

thank you. it works
is there a way to see on an oled display wich gateway saw me and how far away by calculathng the distance between t-beam gps and the location of the gateway?


#23

you can create an application that receives MQTT from the TTN backend (a dedicated RPI ?) and then calcultae a distance between two points and transmits the result over lorawan or maybe a webpage which you can see on your mobile.

it’s done by someone here but I can’t find the link now


(Costel) #24

thank you.


(Coeus) #25

As I was about to get a couple of TTGO T-Beam, I realise there are two different versions with a different GPS chip (NEO-6M & NEO M8N) - I am not sure if there’s any difference in the schematic that would influence the possibility of going idle / sleep on low power.
Anyone has any knowledge about that? Or any success in achieving low power consumption?

I was speaking with apparently the manufacturer representative in WeChat, if I can gather any information about that I will keep everyone in the loop.


(Roeland54) #26

No I think it is just the GPS chip that is changed.

Tried to use serial to configure the NEO-6M on my ttgo t-beam but had no succes. Very strange I wonder if its a fake one.


(Verkehrsrot) #27

Same here with NEO-6M on board. I also wonder if the NEO is a fake.


(Costel) #28

hello,
t-beam was working fine untill 2 days ago…i have no data ever since.
i tried to reflash butt still no luck
i get this on the serial monitor…it seems like it is on endless restart loop

Rebooting…
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:812
load:0x40078000,len:0
load:0x40078000,len:11572
entry 0x40078a5c
assertion “entry < ENTRY_COUNT” failed: file “/Users/ficeto/Desktop/ESP32/ESP32/esp-idf-public/components/nvs_flash/src/nvs_page.hpp”, line 188, function: uint32_t nvs::Page::getEntryAddress(size_t) const
abort() was called at PC 0x400d93e3 on core 0

Backtrace: 0x40091428:0x3ffce520 0x40091603:0x3ffce540 0x400d93e3:0x3ffce560 0x400dd72b:0x3ffce590 0x400ddd0f:0x3ffce5b0 0x400dea71:0x3ffce600 0x400dcf0e:0x3ffce660 0x400dca2a:0x3ffce6b0 0x400dcac3:0x3ffce6d0 0x400dcb0e:0x3ffce6f0 0x400d5170:0x3ffce710 0x401150bf:0x3ffce730 0x400da2ca:0x3ffce760

Rebooting…
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:812
load:0x40078000,len:0
load:0x40078000,len:11572
entry 0x40078a5c
assertion “entry < ENTRY_COUNT” failed: file “/Users/ficeto/Desktop/ESP32/ESP32/esp-idf-public/components/nvs_flash/src/nvs_page.hpp”, line 188, function: uint32_t nvs::Page::getEntryAddress(size_t) const
abort() was called at PC 0x400d93e3 on core 0

Backtrace: 0x40091428:0x3ffce520 0x40091603:0x3ffce540 0x400d93e3:0x3ffce560 0x400dd72b:0x3ffce590 0x400ddd0f:0x3ffce5b0 0x400dea71:0x3ffce600 0x400dcf0e:0x3ffce660 0x400dca2a:0x3ffce6b0 0x400dcac3:0x3ffce6d0 0x400dcb0e:0x3ffce6f0 0x400d5170:0x3ffce710 0x401150bf:0x3ffce730 0x400da2ca:0x3ffce760


(Linar) #29

One of LilyGO’s AliExpress stores is doing a promo sale of the T-Beam boards right now -

p2-ae-discount-eu


#30

Did anybody already find a suitable industrial casing for this device?


#31

I have suggested LilyGo to provide T-Beam with IPEX/UFL connector.
That will make them easier to fit in different types of enclosures and enables more flexible antenna placement.


(Meshla) #32

I just got my Ttgo T-beam, i tried in deep sleep mode, using 44mA, and i think it using power gps module, because it is not power down, and i look in data sheet of Neo-6M-0-001 it is not possible to turn off with out physically connection, i will try later to use on board transistor and one pin of board to turn on off.


#33

5 posts were merged into an existing topic: TOOLS for TINKERERS


(CovraWorkS) #34

I had a problema with two modules bought on aliexpress… One of them was a 433 instead a 868. Asking about that to the seller , he told me that if you tear off the label, you can see a dot on the chip if it is the 433 versión:t_beam_close


(CovraWorkS) #35

I have another issue and I dont know if the problem comes from node or Gateway does.

  • Gateway: LoRaGo Dock v1.1 single channel from SandboxElectronics with its own firmware LoRaGoDOCK-Gateway with this parameters:
    #define _SPREADING SF10
    #define _CAD 1
    #define _STRICT_1CH 1

  • Node: TTGO T-Beam 868eu T22-v05 20180608, firmware: TTNMapper-T-Beam from DeuxVis (who helped me a lot).
    I had to modify the firmware changing these lines:

    LMIC_setDrTxpow(DR_SF10, 14)
    and
    LMIC_setupChannel(0....8, 868100000, DR_RANGE_MAP(DR_SF10, DR_SF10), BAND_CENTI); // g-band

    in order to link with the single cannel Gateway.

Both are up for 14 hours aprox. The gateway uplinks about 1/3 of the data packets sended by T-beamc (it sends 1 each 2 minuts) , but at the TTN console i see a strange behaviour with the traffic data… I can see now in “My device>Overview”
Status: 12 minutes ago /Frames up: 712
In “Gateways>Mygateway”
Status connected
Last Seen 1 minute ago
Received Messages 95
Transmitted Messages 0
But no application data…

Update: Meanwhile I am writing this post, suddenly appears 3 data on my device:

‎15‎:‎03‎:‎487181
payload:B845047FC3C6001307altitude:48.64hdop:0.07latitude:27.9992longitude:-375.1041


‎15‎:‎00‎:‎067121
payload:B845047FC3C6000008altitude:0hdop:0.08latitude:27.9992longitude:-375.1041


‎14‎:‎57‎:‎377081
payload:B845077FC3C2000007altitude:0hdop:0.07latitude:47.66longitude:-401.3185

(wrong gps data…)

  • Any idea why so few packages appear in the log?

  • Any idea why gps data is wrong?
    function Decoder(b, port) {

    var lat = (b[0] | b[1]<<8 | b[2]<<16 | (b[2] & 0x80 ? 0xFF<<24 : 0)) / 10000;
    var lon = (b[3] | b[4]<<8 | b[5]<<16 | (b[5] & 0x80 ? 0xFF<<24 : 0)) / 10000;
    var alt = (b[6] | b[7]<<8 | (b[7] & 0x80 ? 0xFF<<16 : 0)) / 100;
    var hdop = b[8] / 100;
    
    return {
      
        latitude: lat,
        longitude: lon,
        altitude: alt,
        hdop: hdop
      
    };
    

    }

PS: I have just read the wire question between GPIO32 and LoRa1… but I get data… then???


(CovraWorkS) #36

This function is wrong, I updated and it now works

Still, dissapear and few data packets…:frowning:

log_gatewaylog_gateway_ttn

note that webserver is gmt


(Deux Vis) #37

Hey covra, I’m glad you made some progress.

Can you please rephrase in a single sentence what is the problem you are asking help with ? I don’t understand it clearly.


(CovraWorkS) #38

Sorry about that… Actually, I was writing the post while things were happening…:sweat_smile:

My problem is that very few data packets arrive (sometimes two in an hour) to the server even though the ttgo transmits every 60 seconds and, really, I do not know if it’s from the SF, or the Single channel gateway, or for a bad configuration of the ttgo in the lorawan protocol …

Also, despite having read tons of documentation, nothing appears in the TTMapper (I think it is because TTN does not show the SCGs on the map and therefore can not draw the lines from the gw to the node)

Now I’m testing the integration with Cayenne, to see if, at least, I can show the GPS data there, but I still do not clearly know if I have to modify the code in my firmware to be compatible with Cayenne lpp or TTN does it in its integration … Many questions …

thank you anyway


(Jac Kersing) #39

TTN knows nothing about your data (format) so they are unable to change your data to lpp format. You need to change your firmware.

Has your node been programmed to only transmit on the channel your single channel ‘gateway’ uses? If not that will explain missing packets. Do you use OTAA? That will set the node to use 8 channels.

For you ‘gateway’, don’t set it to strict 1 channel, RX2 transmissions use another frequency, setting strict mode disables switching to that frequency.


(CovraWorkS) #40

TTN knows nothing about your data (format) so they are unable to change your data to lpp format. You need to change your firmware.

I was some confused about that, but now I am writing a header file for my gps application based on TTN_arduino>src>CayenneLPPclass

Has your node been programmed to only transmit on the channel your single channel ‘gateway’ uses? If not that will explain missing packets. Do you use OTAA? That will set the node to use 8 channels

First, I use ABP in order to avoid uplink messages (works in that way?:sweat_smile:) and about node firmware, yes:

… Node: TTGO T-Beam 868eu T22-v05 20180608, firmware: TTNMapper-T-Beam 2 from DeuxVis (who helped me a lot).
I had to modify the firmware changing these lines:
LMIC_setDrTxpow(DR_SF10, 14)
and
LMIC_setupChannel(0....8, 868100000, DR_RANGE_MAP(DR_SF10, DR_SF10), BAND_CENTI); // g-band
in order to link with the single cannel Gateway…

For you ‘gateway’, don’t set it to strict 1 channel, RX2 transmissions use another frequency, setting strict mode disables switching to that frequency

But, I dont need RX2 transmissions… it is a tracker application, the node dont need hear nothing, only needs to send gps data… Am I wrong?