ERROR: [main] failed to start the concentrator

brady_aiello · January 23, 2019, 5:23am

It’s still not working, but I got closer. There’s a discrepancy between how we talk about pins in the TTN packet forwarder and forks off of Semtech’s. TTN’s reset pin refers to GPIO #, whereas Semtech and others refers to the reset pin by pin #. GPIO 7 = pin 26, so setting that to 26 in reset_lgw.sh got me closer to working.

The last few lines of my verbose output are now:

lgw_spi_rb:373: BURST READ: to trans 1024 # chunk 1024 # transferred 8192 
Note: SPI burst read success
ERROR: Failed to load fw 1
Note: SPI read success
Note: SPI write success
Note: SPI write success
Note: SPI read success
Note: SPI write success
Note: SPI write success
Note: SPI write success
Note: SPI read success
ERROR: Version of calibration firmware not expected, actual:0 expected:2
21:18:55  ERROR: [main] failed to start the concentrator

sacchidanand_utech · February 20, 2020, 1:11pm

Hello ehsanmgh,
I am facing the same problem. can you please tell me how you RESET the ic880a-SPI board.

sacchidanand_utech · March 16, 2020, 1:55pm

Hello,
I already tried it but it didn’t worked.
Is any other solutions to start the concentrator ?
Any help ll be appreciating.
Thank you.

moji · August 26, 2020, 9:04am

Hi, I had the same issue, I could resolve it by resetting the CE0 and RESET pin before running the forwarder. Here is how i did it:


echo "Restarting the CE0 pin..."
CSPIN=8
echo "$CSPIN" > /sys/class/gpio/export
sleep 1
echo "out" > /sys/class/gpio/gpio$CSPIN/direction
echo "0" > /sys/class/gpio/gpio$CSPIN/value
sleep 1
echo "1" > /sys/class/gpio/gpio$CSPIN/value
echo "Done\n"
sleep 1

echo "Restarting the Concentrator..."
RSTPIN=17
echo "$RSTPIN" > /sys/class/gpio/export
sleep 1
echo "out" > /sys/class/gpio/gpio$RSTPIN/direction
echo "1" > /sys/class/gpio/gpio$RSTPIN/value
sleep 1
echo "0" > /sys/class/gpio/gpio$RSTPIN/value
echo "Done\nLaunching the forwarder..."
sleep 2

cd /PATH_TO_THE_GATEWAY_CODES/packet_forwarder/ && ./lora_pkt_fwd

Save this code in a shell file, change the path according to your own settings and make sure to run it with sudo
The full article can be found here

DylanSaenz · September 18, 2020, 9:37pm

Moji
I read your article thank you very much, but I have doubts about how to save or create the code in the console. I am a newbie

FranciscoOliveira · March 29, 2021, 9:38pm

Hello,

As you can see i have the ‘ftdi’. Where can i find the instructions to fix this?
i’am having the same error:
“ERROR: [main] failed to start the concentrator”

kersing · March 29, 2021, 9:46pm

Do you mean you have ftdi hardware? Or that you have SPI hardware and the wrong software version?
Which instructions have you used?

BTW the terminal output is ascii text, no need to use an image, just cut-and-paste the text as a quote/code block next time you post.

AbhijeetNatu · September 1, 2021, 11:18am

error_post Any idea how I might resolve this error ? I am using LORA gateway along with a risinghf module. What might be the solution to this?

Jeff-UK · September 1, 2021, 7:03pm

Be precise with details please if you expect help

Which model & configuration of hardware, which firmware, which packet forwarder…etc…

…and as last post above dont post images for such output…

AbhijeetNatu · September 2, 2021, 4:11am

@Jeff-UK Sorry Sir,
I am using RisingHF gateway “RHF2S025BH8-868” for my application to send data on iotsquare.xyz .
These are the steps I have followed:

Created application on cloud.iotsquare.xyz and got DevEUI, AppEUI, Application and Network Key.
Added gateway details and the Gateway ID onto cloud.iotsquare.xyz
Packet Forward is enabled.

After performing above steps, the gateway is still not showing status as online.

Firewall is disabled, checked IP and it is present in the DHCP client table.
Also the internet speed is sufficient. So, I am not understanding what exactly might be the issue here.
Please suggest a solution for this.

Jeff-UK · September 2, 2021, 9:15am

…and TTN fits in where exactly, and what have you done to register there (gw, application, device?), what are you seeing in logs there?

descartes · September 2, 2021, 9:28am

To make Jeff’s post totally clear, it appears that you are not using TTN and this is a TTN forum.

If you are not using TTN, this is not the forum you are looking for.

AbhijeetNatu · September 2, 2021, 9:58am

Okay Sir. Sorry about the post.

techatreyo · May 13, 2022, 12:50pm

Hi,

I am facing same problem. I am totally new to do this. Can you please describe in details how to resolve this?

warhade · June 14, 2024, 7:24pm

I’m having trouble setting up my LoRaWAN module (WM1302) with my BeagleBone. I’ve connected everything, but I keep getting these errors:
ERROR: sx1250 Image Calibration Error ERROR: radio calibration failed ERROR: radio calibration failed
ERROR: [main] failed to start the concentrator

kersing · June 14, 2024, 7:26pm

Have you checked all signals are available? I vaguely recall I needed to solder a jumper on a BeagleBone to enable some signal. (Sorry, too long ago to recall the details. I suggest you check the BeagleBone schematic for solder jumpers)

warhade · June 15, 2024, 4:04am

all signals are available and config the pin

using the sx1302_hal library as per guidance of seeed studio LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki

configure the those pin on beagle bone :

Current mode for P9_17 is: spi_cs

Current mode for P9_21 is: spi

Current mode for P9_18 is: spi

Current mode for P9_22 is: spi_sclk

Current mode for P9_11 is: gpio (reset pin)

but I’m still facing the same issue

debian@beaglebone:~/sx1302_hal/packet_forwarder$ ./lora_pkt_fwd -c global_conf.json.sx1250.EU868
*** Packet Forwarder ***
Version: 2.1.0
*** SX1302 HAL library version info ***
Version: 2.1.0;

INFO: Little endian host
INFO: found configuration file global_conf.json.sx1250.EU868, parsing it
INFO: global_conf.json.sx1250.EU868 does contain a JSON object named SX130x_conf, parsing SX1302 parameters
INFO: com_type SPI, com_path /dev/spidev0.0, lorawan_public 1, clksrc 0, full_duplex 0
INFO: antenna_gain 0 dBi
INFO: Configuring legacy timestamp
INFO: Configuring Tx Gain LUT for rf_chain 0 with 16 indexes for sx1250
INFO: radio 0 enabled (type SX1250), center frequency 867500000, RSSI offset -215.399994, tx enabled 1, single input mode 0
INFO: radio 1 enabled (type SX1250), center frequency 868500000, RSSI offset -215.399994, tx enabled 0, single input mode 0
INFO: Lora multi-SF channel 0> radio 1, IF -400000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 1> radio 1, IF -200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 2> radio 1, IF 0 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 3> radio 0, IF -400000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 4> radio 0, IF -200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 5> radio 0, IF 0 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 6> radio 0, IF 200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 7> radio 0, IF 400000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora std channel> radio 1, IF -200000 Hz, 250000 Hz bw, SF 7, Explicit header
INFO: FSK channel> radio 1, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate
INFO: global_conf.json.sx1250.EU868 does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to 1464464616316411
INFO: server hostname or IP address is configured to “eu1.cloud.thethings.network”
INFO: upstream port is configured to “1700”
INFO: downstream port is configured to “1700”
INFO: downstream keep-alive interval is configured to 10 seconds
INFO: statistics display interval is configured to 30 seconds
INFO: upstream PUSH_DATA time-out is configured to 100 ms
INFO: packets received with a valid CRC will be forwarded
INFO: packets received with a CRC error will NOT be forwarded
INFO: packets received with no CRC will NOT be forwarded
INFO: GPS serial port path is configured to “/dev/ttyS0”
INFO: Reference latitude is configured to 0.000000 deg
INFO: Reference longitude is configured to 0.000000 deg
INFO: Reference altitude is configured to 0 meters
INFO: Beaconing period is configured to 0 seconds
INFO: Beaconing signal will be emitted at 869525000 Hz
INFO: Beaconing datarate is set to SF9
INFO: Beaconing modulation bandwidth is set to 125000Hz
INFO: Beaconing TX power is set to 14dBm
INFO: Beaconing information descriptor is set to 0
INFO: global_conf.json.sx1250.EU868 does contain a JSON object named debug_conf, parsing debug parameters
INFO: got 2 debug reference payload
INFO: reference payload ID 0 is 0xCAFE1234
INFO: reference payload ID 1 is 0xCAFE2345
INFO: setting debug log file name to loragw_hal.log
WARNING: [main] impossible to open /dev/ttyS0 for GPS sync (check permissions)
CoreCell reset through GPIO11…
SX1261 reset through GPIO11…
CoreCell power enable through GPIO18…
CoreCell ADC reset through GPIO13…
Opening SPI communication interface
Note: chip version is 0xFF (v15.15)
ERROR: sx1250 Image Calibration Error
ERROR: radio calibration failed
ERROR: radio calibration failed
ERROR: [main] failed to start the concentrator

kersing · June 15, 2024, 9:15pm

Seeed lists two reset pins on the webpage. Are you using the right one to reset the SX1302?

warhade · June 17, 2024, 8:08am

give me the references of another reset pin
I’m refer the LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki seeed studio webpage

I’ve attach pin out Diagram here only one reset pin mention

kersing · June 17, 2024, 9:03am

The page you are referring to has a different table and lists reset pins at pin 10 and 22. Pin 22 should be the right one. Also make sure to drive the pin to the correct level.