New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fuota-test-01 McGroupSetupReq Not happening (Need Help).. #827
Comments
Following... |
Last week I tried for the first time the recent implementation of the FUOTA packages by ChirpStack. In my case the Multicast session was setup correctly but, then the Fragmentation session setup failed.
Please, remark that for the embedded side I'm confident that there is no issue (but, we never know) as this firmware has been used by different network stack providers while performing interoperability tests. All the network stack providers being part of those tests reported that everything was OK for the tested scenario. On the other side the FUOTA support on ChirpStack is pretty recent and I currently don't know what is the development status of this feature on the server. Please note, that the first tests done on the packages provided by this repository were done using a previous version of ChirpStack and by following the instructions provided by this mbed project. I had to change the |
Hi mluis, Thanks for the reply and i had used your modification on the loraserver.js file to run it. Can you show me your output of the loraserver.js on a successful run?? |
I had similar issues . Make sure that gateway_ID in packet forwarder and ChirpStack Application Server (in Gateway configuration tab) are the same. @sathishkumarparthiban |
I was trying FUOTA as well and got:
then some class C downlink frame...
It will receive several more downlink frames, but doesn't handle them because the state it FRAG_SESSION_NOT_STARTED. It also doesn't switch back to class A (and set IsMcSessionStarted to false). |
@KaDw i get the Clocksync on the topic "join"
After this i can see the msg flow , but i dont get the fPort parameters in the msg.
|
@sathishkumarparthiban Sorry can't help you with loraserver.js script. Newest versions of loraserver (I think 3.0+) supports FUOTA from user interface, and this is what I'm using. |
@KaDw thats fine.. How do you debug the msg flow on the gateway with user interface.. The problem i see is that my gateway isn't responding back for the device time sync. I'm able find this when i debugged the code from the script... |
@sathishkumarparthiban Check app server or network server logs, https://www.chirpstack.io/application-server/install/debian/#chirpstack-application-server-log-output |
Just to inform that I was able to successfully run the fuota-test-01 with ChirpStack. The interoperability test specification provided by the LoRa-Alliance uses a 1KB file which is split in 21 fragments of 50 bytes with a redundancy of 5 fragments. The ChirpSatck server on the other hand takes the 1KB file and splits it into fragments of maximum payload size for the used datarate. Run the test using ChirpStak:
Note I used the code provided on develop branch (commit b4b37db) and just changed the Below the end-device serial terminal output Click to expand!
|
Hello, has anyone tried FUOTA process using Chirpstack server and fuota-test-01 example lately? I've been trying to set it up and test it but have come to an issue I can't overcome. Im using LmHelper files provided by semtech that implement FUOTA steps (Multicast, clock sync and fragmentation) but seem to have an issue of having different MC_NWK_S_KEY and MC_APP_S_KEY being generated on end-device side and on application server side. Did anyone else come across the same issue or at least can confirm that the example is working with Chirpstack server? |
Hi ,
I'm trying to get the fuota-test-01 example to work. Steps i followed.
After this i dont see "McGroupSetupReq & Ans" happening. after sometime i get a error message saying "The device failed to provision the remote multicast setup". (attached image)
Project : fuota-test-01
Board : B-L072Z-LRWAN1
Gateway : n-fuse 868Mhz (IN865-867 region).
Server: loraserver
I
The text was updated successfully, but these errors were encountered: