Just create a new topic with an appropriate title like “How to connect an E78 to TTN” - posts don’t have to be questions.
2 Likes
i updated my test setup again
- soldered thicker wires for VCC and GND
- added 1000uF close to the module (already mentioned)
now it looks stable, the test setup is supplied via a LDO from USB / USB-OTG
a simple docu with the test config:
Hello. Tell me please, what return is by the “AT+CGMR?” command?
My return is v1.0, and the command “AT+DTRX=0,1,10,0123456789” return “OK+SEND:05” (the packet length is 5 bytes, no 10), but nothing comes to my gateway
To be clear, uplinks on port 0 without an application payload are network housekeeping messages which have been sent by the device’s LoRaWan stack on its own, rather than as a result of a command to send application data.
Somtimes this housekeeping information can ride along on application data messages, other times it requires a message by itself. Some node software architectures mean the stack doesn’t really get a chance to do things on its own timing, so if requested to send application data but necessary housekeeping has to occur first, it may send a housekeeping message on port 0 instead of sending the requested data. (Some stacks will also do a join request in such situation if asked to send when not yet joined)…
In terms of the new posting:
nothing comes to my gateway
This thread is about uplinks of unexpected form and content. A gateway not receiving any uplink at all is a very different sort of problem and should be in its own thread.
Try this:
AT+DTRX=0,1,10,00010203040506070809
Then:
AT+DTRX=0,1,5,0123456789
And that’s supposed to be helpful how?
Hello,
I am trying to configure this exact module to send a uplink payload data of size 96 bytes to TTN. I have configured the correct data rate (SF7 BW125KHz). I also tried to split my data into 4 and queue them, but to no success. When I try to send my data in 96 byte format, I can only see 51 bytes on my console. When I queue them, I have to wait for the module’s response “OK+SENT” after I send my first part of data.
This sounds like typical limit under SF12 with EU868 scheme vs your SF7… check set-up/config…
Hello,
The module looks to be correctly configured, as I query data rate and receive window parameters. And gateway’s LoRa Channel configurations are set up as to be EU868 - SF7.
This payload size is exactly 51 bytes.
That’s just plain not appropriate on the community network, regardless if you split it into multiple pieces or not.
You’re probably running into some sort of limit in the stack or another, but the reality is that you just shouldn’t be trying to do this. If you actually need to move that much information, and can’t better compact it, then you need a different technology.
Why is it not appropriate to send uplink data of that size? I’m sending unconfirmed messages, for all its worth, by the way.
Because they take absurdly too much airtime.
If you need to move 96 byte packets, you’re into territory that LoRaWan especially as implemented in TTN simply isn’t meant to fill.
is it essential to use a microcontroller for driving the E78 module ? cant i use a serial port with the e78 module to transmit data ??
Dear @AbhipsitaTechnologie
The E78 can be programmed with an AT command firmware (GitHub - asrlora/alios-asr-lora) that allows you to send data from a computer or other serial terminal.
Kind regards
You don’t have to use a microcontroller, you can use a full size PC if you wish.
But you will need something to send the appropriate commands to the E78 module or you may, and I’ve not tried, be able to write your own firmware for it.
thanks you so much for the advice. I will be sending the AT commands to the e78 module from PC via cutecom terminal in fedora 30.
I have succesfully added a dragino lps8 as a gateway on the TTN network and it shows “connected”. However, while registering the e78-868lln22s module as an end device, and after putting all the required details as asked, TTN console shows “last seen info unavailabe” for the same. Could you suggest what is wrong ??
Thanks in advance.
Not without a whole heap more detail, like is it ABP or OTAA, what do you see on the device serial log, the gateway log, the gateway web console etc.
Please ensure all text items are copied & pasted as text, no screen shots and that you use the </> tool to format logs & serial output.
hello,
i used a standard win10pc with HTerm and an USB-UART adapter (CP2102),
maybe helpful:
following are the details:
1)network server address+application server address : eu1.cloud.thethings.network
2)lora wan version: MAC v1.0.3
3)freq plan: india 865-867 mhz
4)supports class C
there after i obtained the device address, generated an nwkskey. At the application layer, i also obtained appskey, and didnot enable the skip payload encryption and decryption.
the last msg at the device log shows “updated”, and at the gatewayconsole:connected.
when i type the AT commands as stated in the above comments by daa792.
Gateway log shows “devaddr:260B****,Fcnt:1, Fport:10,macpayload: E0 1C E1 D1, bandwidth:12500, snr:11, RSSI:-53, raw payload :8042AA0B268001000AE01CE1D1447AA6F0” for AT command AT+DTRX=1,2,4,00010203
Not sure why there is a MAC payload included - what is make & model of the gateway?