LWN-Simulator
LWN-Simulator copied to clipboard
UniCT-ARSLab
Problems with Simulated Devices on ChirpStack
Good Morning!
I’m new to ChirpStack and the LWN simulator. I followed the 'IdealBit' tutorials to set up LWN and connect gateways/devices with ChirpStack, but I can’t access the device frames, and my device shows the status “Never seen.”
Any advice, recommendations, or help would be greatly appreciated!
Have you added the values in the Activation tab? Either the OTAA field or the 3 other keys should match in both the simulator and Chirpstack, I think.
Please check both your Simulator configuration (gateway and devices) and Chirpstack configuration. As said by @mmmaske check activation fields and DevUIs
Hello! thanks for your responses. Yes, the OTAA is the same in both ChirpStack and LWNSimulator. The only thing I’ve changed is the region (from EU868 to AU915). Maybe I’m missing something because it works when I use EU868 and set the latitude and longitude values to 0. I noticed that even if I specify the region, the Region ID and Region common-name are still set to EU868. Is it possible I have to change something on Chirpstack's configuration?
This screenshot is from my previous configuration (test1).
This other one is what I see when using the EU868 region (test2).
I have recently joined the development of this project, so I am still learning, but I have seen some code related to your problem. I am working on a new release that aims to clean up the code from the recent PRs, unfortunately it has not been completed yet.
If I understand correctly, your problem is related to https://github.com/UniCT-ARSLab/LWN-Simulator/pull/18
Are you using the latest compiled binary released or are you compiling from source?
The compiled binary is quite old and does not incorporate the contributors' patches. Compile the master branch and let me know if it works for you.
Currently the #18 somehow breaks the Chirpstack connection, so I skipped it for now
Hello, I was compiling from the source code posted in the releases section. Now, I cloned the GitHub repo on my PC, but the problem persists.
Therefore, #18 is not related to your problem.
It requires a deeper investigation.
Hi all, any progress on this issue? I am facing the same. Region EU868
Region EU868 is not supposed to be affected by this issue. Please provide your configuration files.
Please remember to use the latest release from the "Releases" page or compile yourself the dev branch.
I am also facing the same issue with Regio : EU868. Any way to debug the issue ?
We need the configuration to try the simulation of the same environment and check the issue. Anyway, the 868 is supported, right now only the Australian channels are not supported (we need to implement the new frequencies)
