Node take a long time about 4 o 5 minutos show data on application ttn

mangulo · August 27, 2019, 11:17am

I have mounted a minigateway and a node with TTGO ESP32 oled lora v2

when i receive the ttn application data it takes a long time about 4 or 5 minutes.

I also don’t receive the payload “hello world” in my application. I receive code in hexadecimal

why take it long time to receive data on the applicacion of the device?

IMG_20190827_122215

the code of my applicacion ttn-abp =>

greets.

BoRRoZ · August 27, 2019, 11:29am

you have a single channel gateway ?
if I look at your screenshot one in every 8 packets is received.
So what you can do is edit the ttn-abp file so you use only one channel, the same one as your gateway is listening

mangulo · August 27, 2019, 12:27pm

Thank for you reply BoRRoZ

In my file ttn-abp I have put it as #define SINGLE_CHANNEL 1
include <lmic.h>
#include <hal/hal.h>
#include <SPI.h>
#include <U8x8lib.h>
#define BUILTIN_LED 25
#define SINGLE_CHANNEL 1 // Set to 1 to force single channel

github.com

Mangulomx/lora-ttn-abp/blob/master/ttn-abp/ttn-abp.ino


/*******************************************************************************
 * Copyright (c) 2015 Thomas Telkamp and Matthijs Kooijman
 *
 * Permission is hereby granted, free of charge, to anyone
 * obtaining a copy of this document and accompanying files,
 * to do whatever they want with them without any restriction,
 * including, but not limited to, copying, modification and redistribution.
 * NO WARRANTY OF ANY KIND IS PROVIDED.
 *
 * This example sends a valid LoRaWAN packet with payload "Hello,
 * world!", using frequency and encryption settings matching those of
 * the The Things Network.
 *
 * This uses ABP (Activation-by-personalisation), where a DevAddr and
 * Session keys are preconfigured (unlike OTAA, where a DevEUI and
 * application key is configured, while the DevAddr and session keys are
 * assigned/generated in the over-the-air-activation procedure).
 *
 * Note: LoRaWAN per sub-band duty-cycle limitation is enforced (1% in

This file has been truncated. show original

But in the file gateway I don’t have put SINGLE_CHANNEL 1. I will have to put it.

github.com

Mangulomx/minigateway-/blob/master/ESP-sc-gway/ESP-sc-gway.h



// 1-channel LoRa Gateway for ESP8266
// Copyright (c) 2016, 2017 Maarten Westenberg version for ESP8266
// Version 5.0.1
// Date: 2017-11-15
//
// Based on work done by Thomas Telkamp for Raspberry PI 1ch gateway and many others.
// Contibutions of Dorijan Morelj and Andreas Spies for OLED support.
//
// All rights reserved. This program and the accompanying materials
// are made available under the terms of the MIT License
// which accompanies this distribution, and is available at
// https://opensource.org/licenses/mit-license.php
//
// Author: Maarten Westenberg (mw12554@hotmail.com)
//
// This file contains a number of compile-time settings that can be set on (=1) or off (=0)
// The disadvantage of compile time is minor compared to the memory gain of not having
// too much code compiled and loaded on your ESP8266.

This file has been truncated. show original

Greets.

UdLoRa · August 27, 2019, 1:21pm

Such gateway is already single channel. In the sw there is a flag for strict 1ch behaviour but is related to downlinks .
The node is the issue: it sends on 8 different channels. I do not know the effect of the SINGLE_CHANNEL flag: in the code seems not used. If you are in EU, you may simply disable 7 of the 8 channels used:

//disable other channels - for single gateway
LMIC_disableChannel(1);
LMIC_disableChannel(2);
…