Raspberry LoraWan EMB- LR1302 - mPCle-868MHz

Hello Everyone, does exist any tutorial how to configure EMB- LR1302 o raspberry? I’m new on this subject.


It would appear not.

But there is the documentation on the Embit site and there is every other Concentrator on Pi tutorial to go at - the only thing you need to find out is what the pin connections are for the HAT so you can set it in the software.

Oh, and the YouTube video that appears on the first page of Google.

@srjohny Believe its in the docs. (Same as the 1301 & 1303 cards for the reset pin if I recall)

Also IIRC covered in other Forum threads in the past (search) and again IIRC follow SEEED(?) implementation as an option? Sure I remember a SEEED implementation where the card/Pi i/o is effectively inverted/mirrored as the card is flipped over and to the side rather than mounted over top of the CPU card… one for OP to investigate as have no time to go digging back myself right now…

Looked at previously as have a few on my shelf from many months ago and was just waiting to pick up a couple of Pi’s to do the builds when I get chance…

I checked website, but on website I just found a brochure and I also found a video from embit, youtube video just have a JSON file. Can I use another tutorial, from example for IC880A i can found a step by step.

As above …

but on the website I found the data sheet which has all the pinouts …

Ok, didn’t help me but thank you.

You appear to have replied to yourself.

But if it was my post you are referring to, the point is that all the materials are there, you just have to try something - waiting for reassurance from people that don’t have an immediate answer because they don’t have the hardware you have is going to be a long wait …

This is how most of us learnt stuff. And generally if you are sensible, there’s no harm in trying as long as you don’t short circuit anything.

I’ve reach something but it’s not working,

for de documentation I guess this is the Pinout - PIN 22 SX1303_RESET Input SX1302/3 Reset Pin (Active High)

I’m getting these errors below

2023-07-11 21:39:20.133 [SYS:INFO] Logging     : stderr (maxsize=10000000, rotate=3)
2023-07-11 21:39:20.136 [SYS:INFO] Station Ver : 2.0.6(rpi/std) 2023-07-11 19:01:27
2023-07-11 21:39:20.138 [SYS:INFO] Package Ver : (null)
2023-07-11 21:39:20.139 [SYS:INFO] mbedTLS Ver : 2.28.0
2023-07-11 21:39:20.139 [SYS:INFO] proto EUI   : XXXX:XXXX:XXXX:XXXX    (station.conf)
2023-07-11 21:39:20.142 [SYS:INFO] prefix EUI  : ::1    (builtin)
2023-07-11 21:39:20.142 [SYS:INFO] Station EUI : XXXX:XXXX:XXXX:XXXX
2023-07-11 21:39:20.143 [SYS:INFO] Station home: ./     (builtin)
2023-07-11 21:39:20.143 [SYS:INFO] Station temp: /var/tmp/      (builtin)
2023-07-11 21:39:20.143 [SYS:WARN] Station in NO-CUPS mode
2023-07-11 21:39:20.351 [TCE:INFO] Starting TC engine
2023-07-11 21:39:21.045 [AIO:INFO] ./tc.trust:
cert. version     : 3
serial number     : 5E:XX:XX:A6:43:7F:A4:E0
issuer name       : CN=ACCVRAIZ1, OU=PKIACCV, O=ACCV, C=ES
subject name      : CN=ACCVRAIZ1, OU=PKIACCV, O=ACCV, C=ES
issued  on        : 2011-05-05 09:37:37
expires on        : 2030-12-31 09:37:37
signed using      : RSA with SHA1
RSA key size      : 4096 bits
basic constraints : CA=true
subject alt name  :
key usage         : Key Cert Sign, CRL Sign
certificate policies : An2023-07-11 21:39:21.048 [TCE:INFO] Connecting to INFOS: wss://eu1.cloud.thethings.network:8887
2023-07-11 21:39:22.065 [TCE:INFO] Infos: XXXX:XXXX:XXXX:XXXX muxs-::0 wss://eu1.cloud.thethings.network:8887/traffic/eui-BXXXXBFFFE059A61
2023-07-11 21:39:22.066 [AIO:DEBU] [3] ws_close reason=1000
2023-07-11 21:39:22.066 **[AIO:ERRO] Recv failed: SSL - The peer notified us that the connection is going to be closed**
2023-07-11 21:39:22.066 [AIO:DEBU] [3] WS connection shutdown...
2023-07-11 21:39:22.527 [AIO:INFO] ./tc.trust:
cert. version     : 3
serial number     : 5E:00:00:A6:43:7F:A4:E0
issuer name       : CN=ACCVRAIZ1, OU=PKIACCV, O=ACCV, C=ES
subject name      : CN=ACCVRAIZ1, OU=PKIACCV, O=ACCV, C=ES
issued  on        : 2011-05-05 09:37:37
expires on        : 2030-12-31 09:37:37
signed using      : RSA with SHA1
RSA key size      : 4096 bits
basic constraints : CA=true
subject alt name  :
key usage         : Key Cert Sign, CRL Sign
certificate policies : An2023-07-11 21:39:22.527 [TCE:VERB] Connecting to MUXS...
2023-07-11 21:39:23.521 [TCE:VERB] Connected to MUXS.
2023-07-11 21:39:23.551 [RAL:INFO] Lora gateway library version: Version: 5.0.1;
2023-07-11 21:39:23.597 [RAL:INFO] [LGW lgw1] clksrc=1 lorawan_public=1
2023-07-11 21:39:23.602 [RAL:INFO]  RX/TX RF0:    867.5MHz rssi_offset=-166.0 type=2 tx_notch_freq=0
2023-07-11 21:39:23.603 [RAL:INFO]  RX    RF1:    868.5MHz rssi_offset=-166.0 type=2 tx_notch_freq=0
2023-07-11 21:39:23.604 [RAL:INFO]  [mSF]   0:    868.1MHz rf=1 freq=-400.0 datarate=0
2023-07-11 21:39:23.606 [RAL:INFO]  [mSF]   1:    868.3MHz rf=1 freq=-200.0 datarate=0
2023-07-11 21:39:23.606 [RAL:INFO]  [mSF]   2:    868.5MHz rf=1 freq=  +0.0 datarate=0
2023-07-11 21:39:23.607 [RAL:INFO]  [mSF]   3:    867.1MHz rf=0 freq=-400.0 datarate=0
2023-07-11 21:39:23.608 [RAL:INFO]  [mSF]   4:    867.3MHz rf=0 freq=-200.0 datarate=0
2023-07-11 21:39:23.609 [RAL:INFO]  [mSF]   5:    867.5MHz rf=0 freq=  +0.0 datarate=0
2023-07-11 21:39:23.610 [RAL:INFO]  [mSF]   6:    867.7MHz rf=0 freq=+200.0 datarate=0
2023-07-11 21:39:23.612 [RAL:INFO]  [mSF]   7:    867.9MHz rf=0 freq=+400.0 datarate=0
2023-07-11 21:39:23.612 [RAL:INFO]  [STD]   8:    868.3MHz rf=1 freq=-200.0 datarate=2 bw=2
2023-07-11 21:39:23.613 [RAL:INFO]  [FSK]   9:    868.8MHz rf=1 freq=+300.0 datarate=50000 bw=0 sync_word=0/0
2023-07-11 21:39:23.613 [RAL:INFO] SX130x LBT not enabled
2023-07-11 21:39:23.613 [RAL:INFO] Station device: /dev/spidev0.0 (PPS capture disabled)
2023-07-11 21:39:23.614 [HAL:INFO] [lgw_spi_open:101] Setting SPI speed to 8000000
2023-07-11 21:39:23.615 [HAL:INFO] [lgw_spi_open:135] Note: SPI port opened and configured ok
2023-07-11 21:39:23.615 **[HAL:ERRO] [lgw_start:742] FAIL TO CONNECT BOARD**
2023-07-11 21:39:23.617 **[RAL:ERRO] Concentrator start failed: lgw_start**
2023-07-11 21:39:23.617 **[RAL:ERRO] ral_config failed with status 0x08**
2023-07-11 21:39:23.617 **[any:ERRO] Closing connection to muxs - error in s2e_onMsg**
2023-07-11 21:39:23.617 [AIO:DEBU] [3] ws_close reason=1000
2023-07-11 21:39:23.619 [AIO:DEBU] Echoing close - reason=1000
2023-07-11 21:39:23.673 [AIO:DEBU] [3|WS] Server sent close: reason=1000
2023-07-11 21:39:23.674 [AIO:DEBU] [3] WS connection shutdown...
2023-07-11 21:39:23.679 [TCE:VERB] Connection to MUXS closed in state -1
2023-07-11 21:39:23.679 [TCE:INFO] INFOS reconnect backoff 10s (retry 1)

Please edit your post and use the </> formatting tool for the logs

Failure to start concentrator usually (9/10 times) a problem with reset pin assignment - check your assumption on this. Also no need to hide your EUI - its public domain when operating. Also if masking a RPi dont bother with the BXXXXXB at the front - generally B8287EB so could reconstruct anyhow! :wink: Doesnt appear to be registered on line using eui-b8287ebfffe059a61, what GW ID have you used if different?


I configure this EUI on station.conf

 "routerid": "b827ebfffe059a61",

I think it’s the correct, I got that ID from

export MAC=`cat /sys/class/net/eth0/address`
export EUI=`echo $MAC | awk -F: '{print $1$2$3 "fffe" $4$5$6}'`
echo "The Gateway EUI is $EUI"

Regarding Reset Pin , I’ve a doubt because I have EMB-LR1302-mPCIe and I have EMB-RasPI-130x-Cape. The EMB-LR1302-mPCIe does not have Tech sheet , checking EMB-LR1301-mPCIe PIN 22 PERST# Input SX1301 Reset Pin, active low. But If i Open tech sheet from EMB-RasPI-130x-Cape I get this - PIN 7 GPIO04 Output SX1301 Reset Pin, active low

On /opt/ttn-station/bin/start.sh file I’ve already tried PIN 22 and PIN7, but the result is the same. should I try another PIN randomly?

On thethings.network Portal I can see this when I try to start.

Irrelevant and a derived EUI that is not correctly formatted as a locally administered address - you were asked for the gateway Id. However it appears from the console that the Pi is connected to the LNS, it’s the Pi ↔ Concentrator link that’s the issue.

Randomly trying pins could lead to the release of magic smoke from either one or both of the Pi or the concentrator card.

Can you ask the supplier of the card for technical details?

I’ve already sent an email to the provider asking Technical sheet.

I got tech Sheet and it’s the same as I mentioned above.

PIN Number: 22
Type: Input
Description: SX1302/3 Reset Pin, (active High)

From EMB-RasPI-130x-Cape I get this - PIN 7 GPIO04 Output SX1301 Reset Pin.

So, I believe my devices has a problem , because I already tested PIN 7 and PIN22.

any Idea?

You might want to consider a second copy or an alternative device, if you think the device has a problem :wink:

Yap, but for that I need to buy a new one. this is a private lab.

Or return the one you have. Or was it gifted to you? If not, why buy this card?

If you mean this money comes out of your own pocket, welcome to the community, that’s pretty much how it works for many of us. LoRaWAN comes with some base costs that get more expensive if you are starting out with stuff that’s not off-the-shelf. Sort of the reason for our existence is to provide recommendations prior to a purchase. There are many many Pi concentrator cards available that are fully documented & supported.

If you want to start out with a simple gateway that is almost guaranteed to work out the box, then get a TTIG. Guaranteed in terms of having a normal WiFi network.

If you don’t have a device, get an off the shelf sensor - or if you want something configureable then a Dragino LT-22222-L - or if you are confident with C & Arduino, an Adafruit Feather M0 with RFM95 so you can code your own device.

I bought that one because it was a recommendation from a user here. I bought on eBay. How many devices can I connect with TTIG?