Implement 433 MHz ISM Band for Rest of the World

Question

Implement 433 MHz ISM Band for Rest of the World

k30r88 opened this issue 9 years ago · 23 comments

This is a separate thread to request implementation for 433 MHz ISM Band for Rest of the World. Thanks

Answer 1 · 2016-07-24T15:47:43.000Z

Hi @mkurnadi, I've added a test-implementation in https://github.com/brocaar/loraserver/tree/test_eu433. For convenience you can download pre-compiled binaries here: https://www.dropbox.com/sh/27n77z9i37jyzob/AACKICcESHiMZ1W5YN6akOM9a?dl=0. To start loraserver with the EU 433 band, use the --band EU_433 flag.

Could you let me know if the following works?

data up (node -> server)
data down (server -> node)
otaa (over-the air activation)

Answer 2 · 2016-07-29T19:28:16.000Z

Hi @mkurnadi I'm looking forward to your test-results :-)

Answer 3 · 2016-08-01T02:39:49.000Z

hi @brocaar, I am getting multi channel gateway and just arrived from overseas. I have been using single channel gateway in last few month. I will try the multi GW with your development software. Many thanks.I will update you again.

Answer 4 · 2016-08-05T08:20:55.000Z

Hi @brocaar, I'm helping @mkurnadi to setup loraserver.
I've followed your documentation and install this specific build for 433 band.

I've executed default start command and the server is working and can accessed from browser.
but if I try to add --band option
sudo systemctl start loraserver --band 443_EU

this is the response

systemctl: unrecognized option '--band'

How can I solved this?

Thanks

Answer 5 · 2016-08-05T13:58:03.000Z

You're passing the argument to systemctl, not loraserver. You should change
the loraserver.service file and add the flag there :)

On Fri, Aug 5, 2016, 10:21 dashracer notifications@github.com wrote:

Hi @brocaar https://github.com/brocaar, I'm helping @mkurnadi
https://github.com/mkurnadi to setup loraserver.
I've followed your documentation and install this specific build for 433
band.

I've executed default start command and the server is working and can
accessed from browser.
but if I try to add --band option
sudo systemctl start loraserver --band 443_EU

this is the response

systemctl: unrecognized option '--band'

How can I solved this?

Thanks

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#49 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKGeaJPBVCcKtiAHtAQd_NgW7PWxs7Oks5qcvJngaJpZM4JTSk6
.

Answer 6 · 2016-08-06T02:03:20.000Z

Hi @brocaar ,

LoraServer is working with new band.

Thanks for the support 👍

Answer 7 · 2016-08-06T07:17:08.000Z

Nice! Could you confirm both data up and down is working (e.g. confirmed data up or OTAA)?

Answer 8 · 2016-08-13T05:01:18.000Z

Dear @brocaar, we still trying to test this. However we would like to know if lora-gateway-bridge need to be installed in the server or in the gateway ?

Answer 9 · 2016-08-13T07:44:29.000Z

That is up to you to decide, both ways are possible. See also https://docs.loraserver.io/lora-gateway-bridge/getting-started/#strategies

Answer 10 · 2016-08-14T02:44:56.000Z

@brocaar we have successfully do data up (node -> server). We monitor the payload by subscribe to topic gateway/b827ebffffa39301/rx

{
"rxInfo": {
"mac": "b827ebffffa39301",
"time": "0001-01-01T00:00:00Z",
"timestamp": 3081371443,
"frequency": 433500000,
"channel": 0,
"rfChain": 0,
"crcStatus": 1,
"codeRate": "4/5",
"rssi": -88,
"loRaSNR": -1,
"size": 48,
"dataRate": {
"modulation": "LORA",
"spreadFactor": 7,
"bandwidth": 125
}
},
"phyPayload": "QG4E8geABAABEJrIQ8DdJLtPAzXd2cgnKSYhjTMkQdHR/AF0oc1PEHC5q8FJ6T9O"
}
gateway id : b827ebffffa39301 in lora-server web app is known as what ?
We still trying to figure out how to retrieve data from lora-server API.

Answer 11 · 2016-08-14T07:27:07.000Z

Hi @k30r88, LoRa Server doesn't have any knowledge about gateways. However, you should create an application and node in LoRa Server (web-interface or API). When configuring your node with the same AppEUI, DevEUI and AppKey you should be able to do an OTAA. Could you let me know if that works?

Receiving data: https://docs.loraserver.io/loraserver/receiving-data/
Sending data: https://docs.loraserver.io/loraserver/sending-data/

Answer 12 · 2016-08-14T07:28:49.000Z

Hi @dashracer I'm looking forward to hear from you if you were be able to send any data from the server to the node and / or were able to perform an OTAA.

Answer 13 · 2016-08-14T10:07:16.000Z

@brocaar . I work together with @dashracer , Application have successfully received data on the server side :

However we test it using single channel device, frequency only at 4335000.
We will try to perform OTAA. Perhaps you can guide us some tips ?

Answer 14 · 2016-08-14T10:14:22.000Z

@k30r88 ah great! Regarding OTAA, just provision your node with the DevEUI, AppEUI and AppKey and perform a mac join otaa (for the RN2483, this command might be different if you're using a different node). You should see a message on the application/+/node/+/join mqtt topic, and your node should be able to send uplink data afterwards.

Answer 15 · 2016-08-20T04:10:11.000Z

hi @k30r88 , can you share where is the file you make the changes to support 433? I need to start one similar for 919-928 range. Thanks.

Answer 16 · 2016-08-20T07:02:45.000Z

@shmrymbd see this diff for the changes needed: https://github.com/brocaar/loraserver/compare/test_eu433?expand=1

Note that the band config lives here: https://github.com/brocaar/lorawan/tree/master/band

Answer 17 · 2016-09-28T18:54:03.000Z

@k30r88 @dashracer could you please tell us if both the uplink and downlink is working with this config? Would be great it we finally can merge this band :-)

Answer 18 · 2016-09-30T00:52:19.000Z

@brocaar uplink seems to be working, we will try downlink next week. Do you have any suggestion on how to do downlink test ? Is downlink similar to OTAA ?

Answer 19 · 2016-09-30T06:57:43.000Z

Downlink is sending data to your node :-) But if you managed to get OTAA
working, you already sent a downlink payload to your node (in this case not
data but a join-accept message).

On Fri, Sep 30, 2016, 02:52 k30r88 notifications@github.com wrote:

@brocaar https://github.com/brocaar uplink seems to be working, we will
try downlink next week. Do you have any suggestion on how to do downlink
test ? Is downlink similar to OTAA ?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#49 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKGeQTkiKyKTNJEmKR6XCEep_xro0Nsks5qvF1DgaJpZM4JTSk6
.

Answer 20 · 2016-12-13T04:45:39.000Z

OS: Arch Linux
loraserver: 0.8.2-1-gf6e02d3
lora-gateway-bridge: 2.1.2

RPi 2: Arch Linux ARM
gateway: RHF0M301
packet_forwarder: 2.2.1

Moteino MEGA + RN2483(RN2483 1.0.1 Dec 15 2015 09:38:09)
Arduino library: TheThingsNetwork-0.17.0, pached for 433MHz

Both ABP and OTAA join ok, and uplink/downlink ok
When I use ABP and reset Moteino, must goto LoRa Server UI, set FCnt to zero

But when I use packet_forwarder-3.1.0, I got the error message:
JSON down: {"txpk":{"imme":false,"tmst":290279995,"freq":433.175,"rfch":0,"powe":10,"modu":"LORA","datr":"SF7BW125","codr":"4/5","ipol":true,"size":17,"data":"IDa54Qt8+kbrNUOSMVNrq74="}}
ERROR: Packet REJECTED, unsupported RF power for TX - 7

Answer 21 · 2017-01-08T12:43:51.000Z

@ksuie hmm, I'm not sure if that error is an issue with the packet-forwarder config or with the band config (given that it worked before). I'll add the EU 433 band config in the next release (+ some more bands). In case you're still experiencing any errors, could you open a new issue?

Answer 22 · 2018-02-06T12:58:37.000Z

Hello, does lora.kyrio.com support the 433 MHz band communication?

Answer 23 · 2018-02-23T12:15:44.000Z

Hi is the 433mhz support still working?