LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki #2228

2025-02-24T05:39:12Z

giscus[bot]
bot Feb 24, 2025

LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki

Getting Started with LoRaWAN® Gateway Module WM1302.

https://wiki.seeedstudio.com/WM1302_module/

ranga1253 · 2025-02-24T05:39:13Z

ranga1253
Feb 24, 2025 — with giscus

nf.json.sx1250.US915
*** 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.US915, parsing it
INFO: global_conf.json.sx1250.US915 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 904300000, RSSI offset -215.399994, tx enabled 1, single input mode 0
INFO: radio 1 enabled (type SX1250), center frequency 905000000, RSSI offset -215.399994, tx enabled 0, single input mode 0
INFO: Lora multi-SF channel 0>  radio 0, IF -400000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 1>  radio 0, IF -200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 2>  radio 0, IF 0 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 3>  radio 0, IF 200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 4>  radio 1, IF -300000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 5>  radio 1, IF -100000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 6>  radio 1, IF 100000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 7>  radio 1, IF 300000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8, Explicit header
INFO: FSK channel 8 disabled
INFO: global_conf.json.sx1250.US915 does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to AA555A0000000000
INFO: server hostname or IP address is configured to "localhost"
INFO: upstream port is configured to "1730"
INFO: downstream port is configured to "1730"
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.US915 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)
./reset_lgw.sh: 26: echo: echo: I/O error
./reset_lgw.sh: 27: echo: echo: I/O error
./reset_lgw.sh: 28: echo: echo: I/O error
./reset_lgw.sh: 29: echo: echo: I/O error
./reset_lgw.sh: 32: cannot create /sys/class/gpio/gpio17/direction: Directory nonexistent
./reset_lgw.sh: 33: cannot create /sys/class/gpio/gpio5/direction: Directory nonexistent
./reset_lgw.sh: 34: cannot create /sys/class/gpio/gpio18/direction: Directory nonexistent
./reset_lgw.sh: 35: cannot create /sys/class/gpio/gpio13/direction: Directory nonexistent
CoreCell reset through GPIO17...
SX1261 reset through GPIO17...
CoreCell power enable through GPIO18...
CoreCell ADC reset through GPIO13...
./reset_lgw.sh: 45: cannot create /sys/class/gpio/gpio18/value: Directory nonexistent
./reset_lgw.sh: 47: cannot create /sys/class/gpio/gpio17/value: Directory nonexistent
./reset_lgw.sh: 48: cannot create /sys/class/gpio/gpio17/value: Directory nonexistent
./reset_lgw.sh: 50: cannot create /sys/class/gpio/gpio5/value: Directory nonexistent
./reset_lgw.sh: 51: cannot create /sys/class/gpio/gpio5/value: Directory nonexistent
./reset_lgw.sh: 53: cannot create /sys/class/gpio/gpio13/value: Directory nonexistent
./reset_lgw.sh: 54: cannot create /sys/class/gpio/gpio13/value: Directory nonexistent
Opening SPI communication interface
Note: chip version is 0x05 (v0.5)
ERROR: Failed to set SX1250_0 in STANDBY_RC mode
ERROR: failed to setup radio 0
ERROR: [main] failed to start the concentrator

I got this as an output trying to start my gateway using this guide

1 reply

ranga1253 Feb 24, 2025 — with giscus

Any help, or guidance would be greatly appreciated!

tonyleo723 · 2025-02-25T06:17:27Z

tonyleo723
Feb 25, 2025

Hi there,

The error you provided states that the Reset_lgw.sh script failed to run because the folder /sys/class/gpio/gpiox does not exist.

This is probably because you are using a version of Linux that has removed the sysfs interface for legacy calls to GPIOs, and the hal libraries provided by Semtech are not adapted for this change.

In WM1302 module: step4 run semtech sx1302 packer forwarder it is indicated what to do when your Linux system does not have a sysfs interface (For Linux without sysfs interface:), to which you can refer for handling.

Hope this will solve your problem!

2 replies

ranga1253 Feb 25, 2025 — with giscus

I am getting the same error with either process. To be fair I am attempting to get this to work with a RasPi 5.
I know it not listed as working but i haven't found any info saying it isn't just assumed no one has documented it work yet.

/sx1302_hal/packet_forwarder $ ./lora_pkt_fwd -c global_conf.json.sx1250.US915
...
WARNING: [main] impossible to open /dev/ttyS0 for GPS sync (check permissions)
./reset_lgw.sh: 26: echo: echo: I/O error
./reset_lgw.sh: 27: echo: echo: I/O error
./reset_lgw.sh: 28: echo: echo: I/O error
./reset_lgw.sh: 29: echo: echo: I/O error
./reset_lgw.sh: 32: cannot create /sys/class/gpio/gpio17/direction: Directory nonexistent
./reset_lgw.sh: 33: cannot create /sys/class/gpio/gpio5/direction: Directory nonexistent
./reset_lgw.sh: 34: cannot create /sys/class/gpio/gpio18/direction: Directory nonexistent
./reset_lgw.sh: 35: cannot create /sys/class/gpio/gpio13/direction: Directory nonexistent
CoreCell reset through GPIO17...
SX1261 reset through GPIO17...
CoreCell power enable through GPIO18...
CoreCell ADC reset through GPIO13...
./reset_lgw.sh: 45: cannot create /sys/class/gpio/gpio18/value: Directory nonexistent
./reset_lgw.sh: 47: cannot create /sys/class/gpio/gpio17/value: Directory nonexistent
./reset_lgw.sh: 48: cannot create /sys/class/gpio/gpio17/value: Directory nonexistent
./reset_lgw.sh: 50: cannot create /sys/class/gpio/gpio5/value: Directory nonexistent
./reset_lgw.sh: 51: cannot create /sys/class/gpio/gpio5/value: Directory nonexistent
./reset_lgw.sh: 53: cannot create /sys/class/gpio/gpio13/value: Directory nonexistent
./reset_lgw.sh: 54: cannot create /sys/class/gpio/gpio13/value: Directory nonexistent
Opening SPI communication interface
Note: chip version is 0x10 (v1.0)
INFO: using legacy timestamp
INFO: LoRa Service modem: configuring preamble size to 8 symbols
ERROR: AGC fw read/write check failed

@raspberrypi:~/sx1302_hal/packet_forwarder $ ls /sys/class/gpio
export  gpiochip512  gpiochip544  gpiochip548  gpiochip563  gpiochip569  unexport
--

#### when i run nano tools/reset_lgw.sh the following is the return.!/bin/sh

# This script is intended to be used on SX1302 CoreCell platform, it performs
# the following actions:
#       - export/unpexort GPIO23 and GPIO18 used to reset the SX1302 chip and to enable the LDOs
#       - export/unexport GPIO22 used to reset the optional SX1261 radio used for LBT/Spectral Scan
#
# Usage examples:
#       ./reset_lgw.sh stop
#       ./reset_lgw.sh start

# GPIO mapping has to be adapted with HW
#

SX1302_RESET_PIN=17     # SX1302 reset
SX1302_POWER_EN_PIN=18  # SX1302 power enable
SX1261_RESET_PIN=5     # SX1261 reset (LBT / Spectral Scan)
AD5338R_RESET_PIN=13    # AD5338R reset (full-duplex CN490 reference design)

WAIT_GPIO() {
    sleep 0.1
}

init() {
    # setup GPIOs
    echo "$SX1302_RESET_PIN" > /sys/class/gpio/export; WAIT_GPIO
    echo "$SX1261_RESET_PIN" > /sys/class/gpio/export; WAIT_GPIO
    echo "$SX1302_POWER_EN_PIN" > /sys/class/gpio/export; WAIT_GPIO
    echo "$AD5338R_RESET_PIN" > /sys/class/gpio/export; WAIT_GPIO

    # set GPIOs as output
    echo "out" > /sys/class/gpio/gpio$SX1302_RESET_PIN/direction; WAIT_GPIO
    echo "out" > /sys/class/gpio/gpio$SX1261_RESET_PIN/direction; WAIT_GPIO
    echo "out" > /sys/class/gpio/gpio$SX1302_POWER_EN_PIN/direction; WAIT_GPIO
    echo "out" > /sys/class/gpio/gpio$AD5338R_RESET_PIN/direction; WAIT_GPIO
}

reset() {
    echo "CoreCell reset through GPIO$SX1302_RESET_PIN..."
    echo "SX1261 reset through GPIO$SX1302_RESET_PIN..."
    echo "CoreCell power enable through GPIO$SX1302_POWER_EN_PIN..."
    echo "CoreCell ADC reset through GPIO$AD5338R_RESET_PIN..."

    # write output for SX1302 CoreCell power_enable and reset
    echo "1" > /sys/class/gpio/gpio$SX1302_POWER_EN_PIN/value; WAIT_GPIO

    echo "1" > /sys/class/gpio/gpio$SX1302_RESET_PIN/value; WAIT_GPIO
    echo "0" > /sys/class/gpio/gpio$SX1302_RESET_PIN/value; WAIT_GPIO

    echo "0" > /sys/class/gpio/gpio$SX1261_RESET_PIN/value; WAIT_GPIO

So it seems that my pins are set correctly. you are correct though this version of pios needed that and i did use that method but gave you more info here if that helps

tonyleo723 Feb 26, 2025

I'm not sure if there is a gpio/value folder in those gpiochipxxx folders you listed with the ls command.

As far as I know, the newer Raspberry Pi OSes have now deprecated this way of calling GPIOs, I've forgotten exactly from which Raspberry Pi OS kernel version this was changed.

You can try to control the GPIO using the commands provided by the Libgpiod package, here is a reference to reset_lgw.sh modified using the commands provided by the package.

SX1302_RESET_PIN=17     # SX1302 reset
SX1302_POWER_EN_PIN=18  # SX1302 power enable
SX1261_RESET_PIN=5     # SX1261 reset (LBT / Spectral Scan)


WAIT_GPIO() {
    sleep 0.1
}

reset() {
    echo "CoreCell reset through GPIO$SX1302_RESET_PIN..."
    echo "SX1261 reset through GPIO$SX1261_RESET_PIN..."
    echo "CoreCell power enable through GPIO$SX1302_POWER_EN_PIN..."

    # write output for SX1302 CoreCell power_enable and reset
    gpioset gpiochip0 $SX1302_POWER_EN_PIN=1; WAIT_GPIO
    
    gpioset gpiochip0 $SX1302_RESET_PIN=1; WAIT_GPIO
    gpioset gpiochip0 $SX1302_RESET_PIN=0; WAIT_GPIO

    gpioset gpiochip0 $SX1261_RESET_PIN=0; WAIT_GPIO
    gpioset gpiochip0 $SX1261_RESET_PIN=1; WAIT_GPIO
}

case "$1" in
    start)
    reset
    ;;
    stop)
    reset
    ;;
    *)
    echo "Usage: $0 {start|stop}"
    exit 1
    ;;
esac

exit 0

You can also manipulate the GPIOs in other ways, just make sure that the pins associated with the WM1302 module are properly reset.

batuhanky · 2025-04-07T12:04:15Z

batuhanky
Apr 7, 2025 — with giscus

Hi,
Where should I connect SX1262 CS pin? Should I use general purpose IO or SPI0 CS pin? Can you help?

1 reply

tonyleo723 Apr 8, 2025

Use the general-purpose IOs to control the SX1262_CS pin.

simon-jouet · 2025-05-19T10:25:54Z

simon-jouet
May 19, 2025 — with giscus

Hi,

Are GPIO6 and GPIO8 of the SX1302 available on some of the pins of the mpcie connector by any chance? They are necessary for libloragw to operate in interrupt mode but looking at the pin mapping table pin 6 (for GPIO6) and pin 28 (GPIO8) they look to be N/C.

Other modules have it exposed on those pins and asking to see if it's exposed and not documented or simply not available in the WM1302

3 replies

simon-jouet May 19, 2025 — with giscus

Alternatively that could be RX_ON (GPIO3) and TX_ON (GPIO5) that are sometimes exposed on LED_WLAN(pin 44) and LED_WPAN(pin 46) but they are also N/C on the seeed module

Jessie219-web May 23, 2025

yep, these are N/C on the WM1302, and from what I've seen, these GPIOs are typically N/C on other vendor modules as well

simon-jouet May 23, 2025

@Jessie219-web thanks for confirming. Actually from what i've seen it's the opposite and other vendors have them exposed on the mpcie connector. Anyway if it's not the case it's not the case, it's just a shame as having access to those GPIO would be really great

batuhanky · 2025-07-28T13:05:29Z

batuhanky
Jul 28, 2025 — with giscus

Hey, I'm using quectel ec25 and want to use EC25 GNSS port as an input to gateway so I modified the config file and gps driver (baudrate changed to 115200) but when I start the script there is # no valid GPS coordinates available yet# expression, so can anyone help?

0 replies

umamaheshrouthu · 2025-09-08T06:33:11Z

umamaheshrouthu
Sep 8, 2025 — with giscus

HI,
I was using wm1302 EU868 USB module from more than a year and is working fine.
recently procured WM1302 US915 USB module and see the module is receiving lorawan join request message(-20dBm) but not transmitting Lorawan Join accept signal.
I see from the sx1302_hal logs, that this message is scheduled to be transmitted. But I do not see any signal activity at that particular frequency.

However, when i replaced this US915 module with the EU868 module and using the same software at both endnode and gateway, I am seeing lorawan join accept message and lorawan join procedure is successful. ofcourse the rssi of the signals received at gateway is very bad (-100 dBm) as this is a EU868 module and signals are transmitted on US915 band.

EU is a MCU version 01.00.00 and US version is V01.00.05

Is this a known issue on the US915 USB modules?

1 reply

nfs0619 Sep 15, 2025
Maintainer

Hi, thank you for your feedback.
We’ve received your report and are arranging an investigation into this issue. For a faster and more detailed response, we recommend that you also contact our technical support team directly at sensecap@seeed.cc.

umamaheshrouthu · 2025-09-15T09:19:04Z

umamaheshrouthu
Sep 15, 2025

Adding ***@***.******@***.***> BELOW is the overview about issue: I was using wm1302 EU868 USB module from more than a year and is working fine. recently procured WM1302 US915 USB module and see the module is receiving lorawan join request message(-20dBm) but not transmitting Lorawan Join accept signal. I see from the sx1302_hal logs, that this message is scheduled to be transmitted. But I do not see any signal activity at that particular frequency. However, when i replaced this US915 module with the EU868 module and using the same software at both endnode and gateway, I am seeing lorawan join accept message and lorawan join procedure is successful. ofcourse the rssi of the signals received at gateway is very bad (-100 dBm) as this is a EU868 module and signals are transmitted on US915 band. EU is a MCU version 01.00.00 and US version is V01.00.05 Is this a known issue on the US915 USB modules?

…

________________________________ From: Frank Nie ***@***.***> Sent: Monday, September 15, 2025 6:22 AM To: Seeed-Studio/wiki-documents ***@***.***> Cc: Uma Maheswara ***@***.***>; Comment ***@***.***> Subject: Re: [Seeed-Studio/wiki-documents] LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki (Discussion #2228) EXTERNAL EMAIL - This email was sent by a person from outside your organization. Exercise caution when clicking links, opening attachments or taking further action, before validating its authenticity. Hi, thank you for your feedback. We’ve received your report and are arranging an investigation into this issue. For a faster and more detailed response, we recommend that you also contact our technical support team directly at ***@***.******@***.***>. — Reply to this email directly, view it on GitHub<https://checkpoint.url-protection.com/v1/r07/url?o=https%3A//github.com/Seeed-Studio/wiki-documents/discussions/2228%23discussioncomment-14399235&g=ZDQwODYyYjY5MDU2OTg1NA==&h=NDQ4NTZjNzRmYzJmYWY4OGQwZGNhMTYxM2FlMzAwNWFlMGJmZjgxNDcwMWMwNzE1NmY4YzY3OWRiNWQwMWM4Nw==&p=bWVjMTp0ZWNobm9sb2d5aW5ub3ZhdGlvbmluc3RpdHV0ZTpjOm86MWM0YTBkODQxODBiNTk2NmFmNTBjODVhNGU4MmQ0OGM6NzpoOlQ=>, or unsubscribe<https://checkpoint.url-protection.com/v1/r07/url?o=https%3A//github.com/notifications/unsubscribe-auth/BG3QLLDCQFJYAG2JPCR5KET3SYPFRAVCNFSM6AAAAABXXFVTGCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZZHEZDGNI&g=ODc4ZDMyMTY3ZjUxMmEzNw==&h=NDg1OTFiZmNhNTQ2MTliNWJlOTExOTUzZjFmNDI2MTAwYzMzOTMzZjU3ZDA0NTQyZTU2NGIxMzk2NTIzZWI5Mg==&p=bWVjMTp0ZWNobm9sb2d5aW5ub3ZhdGlvbmluc3RpdHV0ZTpjOm86MWM0YTBkODQxODBiNTk2NmFmNTBjODVhNGU4MmQ0OGM6NzpoOlQ=>. You are receiving this because you commented.Message ID: ***@***.***>

0 replies

umamaheshrouthu · 2025-09-15T10:04:26Z

umamaheshrouthu
Sep 15, 2025

Hello, Thank you for choosing Seeed Studio. Would you please provide the log of the issue device? It could help to solve the issue. Steve Li Field Application Engineer Seeed Studio Meshtastic-compatible products, we offer dev kits, devices, and solutions to meet different needs. Get yours NOW! From: Uma Maheswara Date: 2025-09-15 17:18 To: Seeed-Studio/wiki-documents; ***@***.***; Seeed-Studio/wiki-documents CC: Comment; Kavin Thangadorai; Michael Baddeley Subject: Re: [Seeed-Studio/wiki-documents] LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki (Discussion #2228) Adding ***@***.*** BELOW is the overview about issue: I was using wm1302 EU868 USB module from more than a year and is working fine. recently procured WM1302 US915 USB module and see the module is receiving lorawan join request message(-20dBm) but not transmitting Lorawan Join accept signal. I see from the sx1302_hal logs, that this message is scheduled to be transmitted. But I do not see any signal activity at that particular frequency. However, when i replaced this US915 module with the EU868 module and using the same software at both endnode and gateway, I am seeing lorawan join accept message and lorawan join procedure is successful. ofcourse the rssi of the signals received at gateway is very bad (-100 dBm) as this is a EU868 module and signals are transmitted on US915 band. EU is a MCU version 01.00.00 and US version is V01.00.05 Is this a known issue on the US915 USB modules? From: Frank Nie ***@***.***> Sent: Monday, September 15, 2025 6:22 AM To: Seeed-Studio/wiki-documents ***@***.***> Cc: Uma Maheswara ***@***.***>; Comment ***@***.***> Subject: Re: [Seeed-Studio/wiki-documents] LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki (Discussion #2228) EXTERNAL EMAIL - This email was sent by a person from outside your organization. Exercise caution when clicking links, opening attachments or taking further action, before validating its authenticity. Hi, thank you for your feedback. We’ve received your report and are arranging an investigation into this issue. For a faster and more detailed response, we recommend that you also contact our technical support team directly at ***@***.*** — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

0 replies

umamaheshrouthu · 2025-09-18T17:22:53Z

umamaheshrouthu
Sep 18, 2025

Hello Steve Li, Following are the logs I see at SX1302_hal regarding the Lorawan join request and join accept. However, the transmission of join accept message is not seen on the spectrum analyser.

…

--------------------------------------------------- logs from not working case: wm1302 usb us915 GATEWAY: JSON up: {"rxpk":[{"jver":1,"tmst":75884344,"chan":7,"rfch":1,"freq":905.300000,"mid": 9,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","rssis":-15,"lsnr":13.5,"foff":97,"rssi":-15,"size":23,"data":"AAQHBgUEA/7/9O7uu90A/900SrVms38="}]} JSON down: {"txpk":{"imme":false,"tmst":80884344,"freq":927.5,"rfch":0,"powe":26,"modu":"LORA","datr":"SF10BW500","codr":"4/5","ipol":true,"size":33,"ncrc":true,"data":"IJpaPzFfk7OgzT8tFe/8AtwKrbHSCP6EGZmmDUM7HUYx"}} WIO E5 Board: 30s045:TX on freq 905300000 Hz at DR 0 30s419:MAC txDone 35s405:RX_1 on freq 927500000 Hz at DR 10 35s456:MAC rxTimeOut 36s416:RX_2 on freq 923300000 Hz at DR 8 36s483:MAC rxTimeOut --------------------------------------------- regards Uma Mahesh

________________________________ From: sensecap(研发服务) ***@***.***> Sent: Monday, September 15, 2025 2:04 PM To: Uma Maheswara ***@***.***>; Seeed-Studio/wiki-documents ***@***.***>; Seeed-Studio/wiki-documents ***@***.***> Cc: Comment ***@***.***>; Kavin Thangadorai ***@***.***>; Michael Baddeley ***@***.***> Subject: Re: Re: [Seeed-Studio/wiki-documents] LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki (Discussion #2228) EXTERNAL EMAIL - This email was sent by a person from outside your organization. Exercise caution when clicking links, opening attachments or taking further action, before validating its authenticity. Hello, Thank you for choosing Seeed Studio. Would you please provide the log of the issue device? It could help to solve the issue.

________________________________ Steve Li Field Application Engineer Seeed Studio Meshtastic-compatible products, we offer dev kits, devices, and solutions to meet different needs. Get yours NOW!<https://checkpoint.url-protection.com/v1/r07/url?o=https%3A//bit.ly/3D9vBf4&g=YjY2MWQyZjAzOGU5ODE3OA==&h=MDhhZjY1ODIyYzFiMzAyYmEyOTYzOGY1NjNmYzFmNTBhYmFjNTlhNjAyMDFlZjRjYjI2Nzc1NDQ4NmIyMGU4Yg==&p=bWVjMTp0ZWNobm9sb2d5aW5ub3ZhdGlvbmluc3RpdHV0ZTpjOm86YzFmYzhhNTdlODA5ZDI4OTM2Zjg2ZGUxOGVlNTVhMzU6NzpoOlQ=> ***@***.*** From: Uma ***@***.***> Date: 2025-09-15 17:18 To: ***@***.***>; ***@***.******@***.***>; ***@***.***> CC: ***@***.***>; Kavin ***@***.***>; Michael ***@***.***> Subject: Re: [Seeed-Studio/wiki-documents] LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki (Discussion #2228) Adding ***@***.******@***.***> BELOW is the overview about issue: I was using wm1302 EU868 USB module from more than a year and is working fine. recently procured WM1302 US915 USB module and see the module is receiving lorawan join request message(-20dBm) but not transmitting Lorawan Join accept signal. I see from the sx1302_hal logs, that this message is scheduled to be transmitted. But I do not see any signal activity at that particular frequency. However, when i replaced this US915 module with the EU868 module and using the same software at both endnode and gateway, I am seeing lorawan join accept message and lorawan join procedure is successful. ofcourse the rssi of the signals received at gateway is very bad (-100 dBm) as this is a EU868 module and signals are transmitted on US915 band. EU is a MCU version 01.00.00 and US version is V01.00.05 Is this a known issue on the US915 USB modules?

________________________________ From: Frank Nie ***@***.***> Sent: Monday, September 15, 2025 6:22 AM To: Seeed-Studio/wiki-documents ***@***.***> Cc: Uma Maheswara ***@***.***>; Comment ***@***.***> Subject: Re: [Seeed-Studio/wiki-documents] LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki (Discussion #2228) EXTERNAL EMAIL - This email was sent by a person from outside your organization. Exercise caution when clicking links, opening attachments or taking further action, before validating its authenticity. Hi, thank you for your feedback. We’ve received your report and are arranging an investigation into this issue. For a faster and more detailed response, we recommend that you also contact our technical support team directly at ***@***.******@***.***>. — Reply to this email directly, view it on GitHub<https://checkpoint.url-protection.com/v1/r07/url?o=https%3A//github.com/Seeed-Studio/wiki-documents/discussions/2228%23discussioncomment-14399235&g=ZDQwODYyYjY5MDU2OTg1NA==&h=NDQ4NTZjNzRmYzJmYWY4OGQwZGNhMTYxM2FlMzAwNWFlMGJmZjgxNDcwMWMwNzE1NmY4YzY3OWRiNWQwMWM4Nw==&p=bWVjMTp0ZWNobm9sb2d5aW5ub3ZhdGlvbmluc3RpdHV0ZTpjOm86MWM0YTBkODQxODBiNTk2NmFmNTBjODVhNGU4MmQ0OGM6NzpoOlQ=>, or unsubscribe<https://checkpoint.url-protection.com/v1/r07/url?o=https%3A//github.com/notifications/unsubscribe-auth/BG3QLLDCQFJYAG2JPCR5KET3SYPFRAVCNFSM6AAAAABXXFVTGCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZZHEZDGNI&g=ODc4ZDMyMTY3ZjUxMmEzNw==&h=NDg1OTFiZmNhNTQ2MTliNWJlOTExOTUzZjFmNDI2MTAwYzMzOTMzZjU3ZDA0NTQyZTU2NGIxMzk2NTIzZWI5Mg==&p=bWVjMTp0ZWNobm9sb2d5aW5ub3ZhdGlvbmluc3RpdHV0ZTpjOm86MWM0YTBkODQxODBiNTk2NmFmNTBjODVhNGU4MmQ0OGM6NzpoOlQ=>. You are receiving this because you commented.Message ID: ***@***.***>

0 replies

pluzmedia · 2025-10-02T12:58:16Z

pluzmedia
Oct 2, 2025 — with giscus

Hello,

I can able to run packet_forwarder but blue LED won't turn on? there is no log printed or no packets where received from nodes.

0 replies

pluzmedia · 2025-10-05T09:09:27Z

pluzmedia
Oct 5, 2025 — with giscus

Will this model has LBT support ? Sx1261 chip is not responding.

2 replies

Kian-kang Oct 17, 2025

We support that. Could you send us the error report for review? Or contact our technical support email.
sensecap@seeed.cc

Kian-kang Oct 20, 2025

https://www.seeedstudio.com/WM1302-LoRaWAN-Gateway-Module-SPI-EU868-p-4889.html

Uh oh!

LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki #2228

Uh oh!

giscus[bot] bot Feb 24, 2025

LoRaWAN® Gateway Module WM1302 | Seeed Studio Wiki

Replies: 11 comments · 10 replies

Uh oh!

ranga1253 Feb 24, 2025 — with giscus

Uh oh!

ranga1253 Feb 24, 2025 — with giscus

Uh oh!

Uh oh!

ranga1253 Feb 25, 2025 — with giscus

Uh oh!

Uh oh!

batuhanky Apr 7, 2025 — with giscus

Uh oh!

Uh oh!

simon-jouet May 19, 2025 — with giscus

Uh oh!

simon-jouet May 19, 2025 — with giscus

Uh oh!

Uh oh!

Uh oh!

batuhanky Jul 28, 2025 — with giscus

Uh oh!

umamaheshrouthu Sep 8, 2025 — with giscus

Uh oh!

nfs0619 Sep 15, 2025 Maintainer

Uh oh!

Uh oh!

Uh oh!

Uh oh!

pluzmedia Oct 2, 2025 — with giscus

Uh oh!

pluzmedia Oct 5, 2025 — with giscus

Uh oh!

Uh oh!

giscus[bot]
bot Feb 24, 2025

Replies: 11 comments 10 replies

ranga1253
Feb 24, 2025 — with giscus

batuhanky
Apr 7, 2025 — with giscus

simon-jouet
May 19, 2025 — with giscus

batuhanky
Jul 28, 2025 — with giscus

umamaheshrouthu
Sep 8, 2025 — with giscus

nfs0619 Sep 15, 2025
Maintainer

pluzmedia
Oct 2, 2025 — with giscus

pluzmedia
Oct 5, 2025 — with giscus