Why did you chose LoRaWAN for this - what is the scenario that requires this choice?
It’s in the Learn section (“End device activation”), which also includes a section on Duty Cycle which is the bit that will prevent you from talking to Ofcom about your local use of the radio spectrum. Ofcom usually turns up with Plod.
As to the interface between MCU and the module, how did you connect to the Grove module?
But the most important thing, apart from the really important “we don’t do student homework but do answer laser sharp focused questions from students”, is if a volunteer asks a question, answer it. At present @Johan_Scheepers still doesn’t know what the status of your gateway is, nor do the rest of us.
Sorry I got lost and didn’t see the question. I have checked and I have a gateway right next to my house. I am unsure how to check the connectivity of this. The gateway I am trying to use is green-minds-university-of-plymouth
I have connected the Grove module via UART using the Expansion Board. I chose LoRaWAN for this since I plan for this to be a remote device and therefore I thought LoRaWAN would be the best choice as the data can travel far and I can visualise this data quite easily
This is asked about once per fortnight, hundreds have tried before you & come un-stuck developing a device when they don’t have access to a gateway console, but it’s not impossible if you get lucky.
“Right next to my house” is a relative term. Metres far less so. RF coverage is a dark art and can be easily upset by heavy rain, cats, blocks of flats and, ironically, being so close you are under the polar ‘umbrella’ of the antenna.
The good news is that gateway is online and as it’s a university gateway, whilst it is mysteriously not on the maps, it’s not totally unreasonable for you to be given read-only access to the console.
But it is sooooooo much easier to have your own.
So you’ve actually got the LoRa-E5 interfaced to the MCU already - what is the issue here?
How far do you actually need? There may be simpler radios to use.
This is not a function of LoRaWAN, it’s a transport medium, it doesn’t make it easy to process & present the data, it can’t be reasoned with, it doesn’t feel pity, or remorse, or fear. And it absolutely will not stop… ever.
So in terms of interfacing with the Lora Module, I suppose I have been successful since I have received a response indicating a successful connection to the device. However I am unsure if I set up the application wrong on the TTN register device page or if I am even sending anything correctly. In terms of distance, I don’t have a specific goal in mind but I was thinking around 5-10km which is the reason I thought of LoRaWAN in the first place, I understand that this is a transport medium but it feels like it is a good one since it is already a built up network that once I get started would be useful. Also it is another skill that I would like to gain just understanding different technologies. In terms of distance away the gateway is 300m away but I should also be able to access the Devonport Column as that is another gateway however that is 3.2km away
Good spot. Although to be fair I already knew that but I needed it to be surfaced by the OP.
@dhyanshyam3, you are transmitting so fast that you are breaking the law as well as breaching the FUP.
Please do not post pictures when the text can be copied & pasted.
Between the Learn section, the Devices & Gateways getting started docs and the code + setup instructions that Seeed provide for the product, setup is pretty much gift wrapped for you.
Please be totally 100% assured, everyone that asks about using a community gateway when setting up a device ends up with access to the console of one, if only to see if the device is being heard by a gateway. Many also protest that they are “in range”, but you have no way of knowing without access to the console. I’d reasonably expect the one 300m away to work if you can see the building it’s in. The one 3.2km depends on the ground clutter - technically called the Fresnel Zone - and line of sight. There’s also two at the church and one at the sailing club that you could loiter outside of.
You’ve entered the standard “it’s an appliance of science” assumption trap but LoRaWAN is definitely not, it’s not designed like a home router to “just work”. You will struggle until you’ve read the basics.
Suspending thread pending confirmation of adherence to the Fair Use Policy as detailed in the Learn section as advised by Jac in post #20.
When using the sample code given by SEEED Studio here: Grove - Wio-E5 TTN Demo | Seeed Studio Wiki I get an output saying the E5 is unfound which is why I tried looking at different libraries but I have found a datasheet and I am reading through them now
The different libraries are irrelevant - they both talk AT commands to the module - they just wrap them up in different ways. There will be something silly in the Seeed code that’s not connecting to the board.
The fundamentals of the DevEUI, JoinEUI and AppKey still stand so the Seeed info on setup is entirely valid.
But your biggest worry is Ofcom / University / TTI taking exception to your lack of understanding of the legal limitations & FUP. Please tell us what you have read and confirm you are working to it.
for you.