I noticed ‘lmic_slim.zip’ which is probably used as LoRaWAN library.
I have no experience with this library but is is not LoRaWAN compliant which is a problem with V3.
When adding an ABP device on V3 this will require manual addition of advanced device parameters in the console (search for V3 and ABP on the forum).
Another issue is that the LoRa32u4 board, actually its ATmega32u4 MCU has relatively little memory which makes it less suitable for more demanding projects that use the MCCI LMIC library (which is the preferred library for the SX1276 LoRa radio on these boards).
While it is possible to use MCCI LMIC with these boards, the sketches should not be too large or they won’t fit on the ATmega32u4.
Be prepared for some hurdles and learning curves to go through.
Maybe LMIC-node can help you make steps in the right direction.
Also see this thread for some tips to get MCCI LMIC working with 8-bit AVR (ATmega328, ATmega32u4) based boards.
Hi @bluejedi
thank you for your reply! I understand I am not using the right board for what I want to build.
For me it is no problem to change the board for another one, I got the Lora32u4 because of the easy-to-follow JuniorIOT guide in which this board is used, but I am willing to buy another one as long as there is a good how-to description for it … I need that for I am not that experienced
It would be great if you have a suggestion for an example GPS project for me that works on V3 TTN! Later on I can expand it with measurements of battery voltage, humidity, temperature and pressure.
In the mean time I will look into your suggestions to try with the Lora32u4.
Hi, thanks for the compliment!
First of all, we startred this project in 2016/2017 and had to create a LMIC adoption. The Lora32U4 indeed has a small memory, where our LMIC cmpetes with other libraries which we need to read our different sensors. This version of what you could call a library does the trick, however it is not a V3 implementation.
Our code with this ‘library’ is still working, we have rolled out new devices on this code, as late as feb 2021. They are on the V2 version of the network. Yes, we want to port them to V3, without stopping their existing ABP session (meaning, without recoding their keys). Such is possible, but I still have to do this. In the V3 console you will need to enter the ‘old’ settings, which means this approach officially is not advisable.
I have not recently updated the published version of our code. Mostly due to online discussion about not being a suppoerted library. Hmm-kay? However there does not seem to be an other approach to use this device, so maybe I should make things a bit nicer to use.
There are some learnings I need to add for you to make the code work. I believe one of them is that it halts on the serial initialization maybe- look at the // on that line. I have a bit more feedback sitting in my inbox which I can use to improve our flow if you’d like that.
The code does not look at downlinks. which means a setting of 1 second or 5 seconds, is all fine. The updated lora standard does not like that. So you need to set all 8 channels in the v3 console to prevent V3 to send these details as downlink to the device. There may be more. I understand using these devices is now frowned upon, so this can never grow into any commercial lora solution. But for our approach it works great. Until now.
Please send me your learnings.
Did you manage to receive data from your device into the V3 console?
I don’t have any specific suggestion for a board for you. It will depend (as usual) on what your requirements for the board and the software are.
Requirements can cover all kinds of things.
It will be good to define your own clear set of requirements. They will be useful to help you search what you are looking for and provides clear information for others to try help you.
In the mean time have a look at information about LoRaWAN and GPS already available on the forum (Search is your friend).
you are more than welcome, this really is a very nice well-written guide that helps folks like me to step into the world of Lora! I have not found another example/tutorial/guide that is as clear as this one.
I will send you my learnings in a PM, but to answer your question: I got everything running in a V2 console in feb/march 2021 but never in a V3 console.
Yes indeed, unfortunately I have no solution yet to share
The main issue for me now is the configuration of the device in my TTN console in V3. This project worked fine on TTN V2, however since V3 my device no longer works. So I deleted the device from the TTN console, and created a new one using the V3 console. My question is what configuration I should use for the Lora32u4 device: It is not a preconfigured Brand in the console, so I added it manually. Unfortunately a lot of the required info is not available here, nor here.
As I have no TTN coverage around my house, I need to try a configuration and drive a bit for TTN coverage and return to find no messages in the console
My current configuration is this:
LoraWANversion: MAC V1.1
Regional Parameters version: PHY 1.1 REV a
Frequency plan: Europe 863-870 MHz (SF9 for Rx 2 - recommended)
Activation mode: ABP
LoraWAN class capabilities: None (class A only)
Network defaults: use network’s Rx and frequency defaults.
Cluster settings: external LoraWan backend servers not checked
