@bmarkus
You know how it is - if something is only prohibited and no one checks. I am confident that users will use it in excess. This is the same as for parking. If one would not controlled despite the paid parking zones one would not pay for it ;-)

@bmarkus
You know how it is - if something is only prohibited and no one checks. I am confident that users will use it in excess. This is the same as for parking. If one would not controlled despite the paid parking zones one would not pay for it ;-)

One more sample:
In my country one operator prohibit use of LTE(normal LTE) to talking without person. You know person is only autorized no device to device talking. This is for me really virtual regulation ;-)

Note that although LoPy and TTN are "a match made in heaven" they are not actually maried :-)

You should however always take into account local duty cycle regulations, in EU typically max 1% (14 minutes per day), see also this document (in Dutch).

In general the more airtime you will be using per node the less nodes you can support. But note that a gateway can receive multiple LoRa encoded packets simultaneously because it can decode multiple channels at the same time, but also multiple spreading factors within a single channel.

But for start in this way, I still would like to know how many LoPy devices can one LoPy (as gateway) to support?
Project 1: The idea is that each LoPy device send 100KB each 5-10 minutes.
Project 2: The idea is that each LoPy device send ~20bytes each second.
Project 3: The idea is that each LoPy device send 100KB each day.

Thank you.

No way.

Project 1: It is not for LoRaWAN even not for an 8-channel professional GW. LoRaWAN is not for 100KB data transmission, it is for sensor network sending low volume data in most cases in one direction w/o confirmation much less frequently..

But for start in this way, I still would like to know how many LoPy devices can one LoPy (as gateway) to support?
Project 1: The idea is that each LoPy device send 100KB each 5-10 minutes.
Project 2: The idea is that each LoPy device send ~20bytes each second.
Project 3: The idea is that each LoPy device send 100KB each day.

Thank you.

No way.

Project 1: It is not for LoRaWAN even not for an 8-channel professional GW. LoRaWAN is not for 100KB data transmission, it is for sensor network sending low volume data in most cases in one direction w/o confirmation much less frequently..

But for start in this way, I still would like to know how many LoPy devices can one LoPy (as gateway) to support?
Project 1: The idea is that each LoPy device send 100KB each 5-10 minutes.
Project 2: The idea is that each LoPy device send ~20bytes each second.
Project 3: The idea is that each LoPy device send 100KB each day.

Thank you.

No way.

Project 1: It is not for LoRaWAN even not for an 8-channel professional GW. LoRaWAN is not for 100KB data transmission, it is for sensor network sending low volume data in most cases in one direction w/o confirmation much less frequently..

But for start in this way, I still would like to know how many LoPy devices can one LoPy (as gateway) to support?
Project 1: The idea is that each LoPy device send 100KB each 5-10 minutes.
Project 2: The idea is that each LoPy device send ~20bytes each second.
Project 3: The idea is that each LoPy device send 100KB each day.

Thank you.

No way.

Project 1: It is not for LoRaWAN even not for an 8-channel professional GW. LoRaWAN is not for 100KB data transmission, it is for sensor network sending low volume data in most cases in one direction w/o confirmation much less frequently..

But for start in this way, I still would like to know how many LoPy devices can one LoPy (as gateway) to support?
Project 1: The idea is that each LoPy device send 100KB each 5-10 minutes.
Project 2: The idea is that each LoPy device send ~20bytes each second.
Project 3: The idea is that each LoPy device send 100KB each day.

Thank you.

No way.

Project 1: It is not for LoRaWAN even not for an 8-channel professional GW. LoRaWAN is not for 100KB data transmission, it is for sensor network sending low volume data in most cases in one direction w/o confirmation much less frequently..

I'm insterest too to do a very large network using LoRa (in this case LoPy), as gateway and client. So, I need to know if LoPy can be works as a complete LoRa gateway for others LoPy (as clients) and if are there some restriction. And, how many LoPy clients one LoPy gateway support.

LoRaWAN nodes, when transmitting, must chose a channel at random (there are several of them). This makes it easier for different users to share the spectrum.

So, in order to build a real LoRaWAN gateway you need a receiver capable of listening to several channels simultaneously and decoding several coding schemes rather than being fixed on one.

The LoRa subsystem you need to to this is far more complex than the "node" oriented chip present in the LoPy (and other LoRa devices) which is configured for one channel and one coding rate. That's the reason why LoRaWAN gateways are much more expensive than end nodes with an average price of around 500 euro.

That said, you can still do LoRa, which means using the interesting transmission methods employed in LoRaWAN, but just not the whole protocol stack.

The number of devices you can support will depend on how often your nodes communicate with the nano gateway, how much data they send of course, and your coding rate which will depend on your intended range.

All right, I will need a real LoRaWAN gateway, that LoPy can't to do that because the chip limitation.

So, my idea for now is to use LoPy as gateway just for other LoPy devices. And when I have many LoPy devices that LoPy not support more, I will to buy one real LoRaWAN gateway and change all LoPy devices to connect to the new 200/500 euro LoRaWAN gateway. That's is fine?

But for start in this way, I still would like to know how many LoPy devices can one LoPy (as gateway) to support?
Project 1: The idea is that each LoPy device send 100KB each 5-10 minutes.
Project 2: The idea is that each LoPy device send ~20bytes each second.
Project 3: The idea is that each LoPy device send 100KB each day.

I'm insterest too to do a very large network using LoRa (in this case LoPy), as gateway and client. So, I need to know if LoPy can be works as a complete LoRa gateway for others LoPy (as clients) and if are there some restriction. And, how many LoPy clients one LoPy gateway support.

Thanks.

If you want to deploy a very large LoRa network, use LoRaWAN compatible gateways equipped with SX130x chips. You can get an indoor GW for cca. 200 EUR. LoPy is not soutable for LoRaWAN compatible GW.

All right. Now I understand that LoPy is not possible to works as LoRaWAN GW. It is a chip limitation.
What means indoor GW, what is difference to the outdoor GW? Why I can't to use a indoor GW as outdoor GW? Just because the indoor is not rain proof, or what?

Also for end devices LoPy in its current state doesn't work. Use a proven, certified module using e.g. RN2483 or similar.

I like so much of LoPy as device because I can write software in Python.

Actually LoPy is not a matured solution. Hope it will be but it will take 6 mionths or so if ever will get documentation and a working LoRaWAN stack as I see.

But what is the problem with LoPy as device? The chip is not capable (there are limitations) to be a real LoRaWAN device, like as GW? Or the chip is fine to works as a real/compatible LoRaWAN device, but just software/firmware from Daniel is still missing features?

In the LoRaWAN terminology a gateway is a device which forwards packets received by the radio board and sends them to a network server without evaluating them, just checking sync byte, 0x34 for public networks and CRC and transmitting packets from the network server to the air. By default a GW is is using the Semtech Packet Forwarder UDP protocol to communicate to network server.

Yes, that's how it will work. With ABP I meant that we won't be supporting OTAA joins (this involved replying with the join accept and handling the proper timing). Sorry for the confusion.

When you say nano gateway, it is a gateway which can be connected to a network server of a service provider like Loriot or TTN or/and it has a built in network server?

As a first stage it will just be an UDP packet forwarder, but the ultimate goal is to provide a small built-in network server as well in order to connect to TTN.

I just called it that way here to explain the difference with the raw-LoRa one. During the KS campaign we said it was not going to be LoRaWAN compatible and we made it clear that it was going to have the single channel limitation.

At first only joining via ABP will be supported on the nano-gateway so there will be a method to add the node and its keys.

Daniel, can you make a clarification what is the functionality of the nano gateway?

In the LoRaWAN terminology a gateway is a device which forwards packets received by the radio board and sends them to a network server without evaluating them, just checking sync byte, 0x34 for public networks and CRC and transmitting packets from the network server to the air. By default a GW is is using the Semtech Packet Forwarder UDP protocol to communicate to network server.

ABP has nothing to do with GW, it is a higher network server layer. When you say nano gateway, it is a gateway which can be connected to a network server of a service provider like Loriot or TTN or/and it has a built in network server?

I am not able to offer a time frame for the LoRaWAN nano-gateway example and the documentation, as we are still working on the implementation. The example Roberto posted is for a raw LoRa nano-gateway.

The way the LoRaWAN nano-gateway works requires the node to only transmit on one channel, for this the LoRa stack needs to be modified a bit to make the 3 default channels the same and remove the rest. There's going to be a third mode on the LoRa class called NANO_GW. At first only joining via ABP will be supported on the nano-gateway so there will be a method to add the node and its keys.

Cheers,
Daniel

Daniel,

that's fine. But please, do not call it LoRaWAN gateway to avoid misunderstandings, there are too much already. It will not compatible with standard LoRaWAN devices (nodes).

I am not able to offer a time frame for the LoRaWAN nano-gateway example and the documentation, as we are still working on the implementation. The example Roberto posted is for a raw LoRa nano-gateway.

The way the LoRaWAN nano-gateway works requires the node to only transmit on one channel, for this the LoRa stack needs to be modified a bit to make the 3 default channels the same and remove the rest. There's going to be a third mode on the LoRa class called NANO_GW. At first only joining via ABP will be supported on the nano-gateway so there will be a method to add the node and its keys.

A TELCO grade outdoor GW is costing cca. 1,000 EUR. Good news is that cheap professional indoor gateways are coming to the market in 2017Q1 thanks to the new Semtech SX1308 chip, you can expect them around 250-300 EUR.

Another solution to get a LoRaWAN concentrator board e.g. from IMST for cca. 150 EUR and connect it to a Raspberry Pi. It is just a board, so I would wait for the new indoor generation.