@xykon Thanks for your confirmation - that will save me a lot of time. I'm going to wait for the official Nano gateway support then. Already pretty excited!

LoRaWAN is using a non-licensed shared frequency band. As long as you meet local regulations, e.g. in Europe max. 1% transmit duty cycle, do not exceed transmit power and bandwidth limits you are safe. It is not about LoRaWAN it is about local radio regulations. These rules are the same for single and 'normal' multi channel GW's.

I'm having a similar issue with mine - US, 915 mhz, on the dr=None allows the function to run but it never really joins.

@jmarcelino Hey, got it, thanks As you suggested I'll write a prog to quick send data and looks on my backend for frequencies of received packet ;-) Look like the faster way

@nicolac Yes, you have to update to the lastest firmware, which is like 1.17.3.b1 or later. You can tell the firmware version by the commands: import uos uos.uname()

Thanks @jmarcelino. Thus the encryption part is not something you get for free... At this point, would it still make sense to prefer LoRaWAN over LoRa-MAC for a standalone network?

@pierrot10 Hi, are you able to solve the issue?

@jmarcelino how do you make a denit() of LoRa or Sigfox please ?

@sameerchouksey do you know if the network is sending MAC commands to the device? If so there could be acknowledgements to send back, which would reduce the max available packet size. Not sure if those ACKs have priority over the payload though.

@robert-hh I got my FiPy nodes working with both The Things Network and Comcast MachineQ. To get it to work, I removed the code that modifies the channels before the connection https://github.com/pycom/pycom-libraries/blob/master/examples/lorawan-nano-gateway/otaa_node_US915.py#L23-L29

@juan-narvaezb95 Multi-hop is not supported by the LoRaWAN Specification.

@jmarcelino OK, i contact the owner of the gateway to see if it's possible to connect to that gateway. Thanks for all informations! we can close the post ;)

@jcaron said in LoRaWan receive window for downlink is mandatory for node ?: @bmarkus At least in the EU region, RX2 on the standard frequency has the advantage that it allows for a much higher use (10% duty cycle vs 1% in most other bands), and much higher power (if the gateway allows it). Depending on your data rate mix, you might be better off in RX2 than on RX1 RX2 is using a single channel with low data rate. It is obvious, that RX1 using 8 channels and various data rates, specially set automatically by the ADR algorithm offers much higher througput than RX2. Why to demage network performance if not necesary? It could be even better if the gateways allow higher transmit powers and you can use faster data rates than the default on RX2. Not sure I see the link between RX2 and 3G backhaul, unless you mean you need the additional time, but one could set RxDelay to a higher value for that (though that is definitely not a good thing for battery life) rather than pick one window over the other. 3G connections typically offering longer latency than 1s which makes RX1 unusable, and usually changing rapidly even going up to 3-5s. In a production environment it is not a good practice to change RX1 timing anyhow.

@gldoug I've likewise been disappointed at the lack of information on connecting to Canadian cell networks. I'm a project manager looking at purchasing a FiPy for evaluation purposes. This would be our first cellular IOT project. I'm in Calgary, Alberta and looking to deploy for industrial use in British Columbia. By "sort out the requirements", which requirements are you speaking of? I presume you are talking about communicating with the carrier, is this correct? And how did you contact them? Did you need to purchase a SIM card? If so, from who? Cheers

@jcaron said in What components are required to build a 915 mhz LoRaWAN Gateway on an Arduino: Note however that the LoPy is a single-channel device. A real LoRaWAN gateway needs to be able to listen on multiple channels at the same time, while the LoPy can only listen on one channel at a time. So you can build what is called a "nano-gateway" here, which will listen on a single channel, and is usable with devices that send on that single channel. If you want to support other devices: Not only single channel but single DR, can detect signal with one Data rate only, no multi-spreading.

@jcaron Thanks. Just to note this method works also for both a software reset AND powercycle.

@jmarcelino Thank you that appears to be correct! I get my push and pull acks now.

Solved! Thanks again everyone. The problem was indeed that the antenna was mounted according to the specification for the LoPy1r, so it was actually on the LoRa 433-510 MHz antenna slot. After a quick range test I now receive packets at at least 400 meters distance. Many thanks, I thought I had gone crazy there for a while!

Hi @daniel, just wanted to make sure these two issues will be addressed in the next release: save/restore channel mask fix MAC command buffers restore Let me know if you need/want issues filed in GitHub and/or PRs.

Yes, this is the way I was trying to implement it, without success until I realized there was an error with the device address. So now, it works fine many thanks !