Open JoobyPM opened 6 years ago
Hello. How do you plan to use these features?
Mostly this feature will be very useful for developers of the devices and those who will create and use the interoperability checking tool (over connector).
If the developer can see the log of all the RX / TX meta-data, together with the raw PHYPayload, it will create the space for external (or internal) compact LoraWan packet analyzer which can work over the connector.
For example in ThingPark (by Actility) they have the Wireless logger - documentstion, it is exactly the LoraWan packet analyzer which shows the developer or administrator of the network the packets in a readable format. Additionally, to that, they have the interoperability tool - InteropEngine - User Guide, to go over the company and test your in a readable format device complies with selected LoraWan standards, by testing mac commands behaviours - documentstion Also, they have «MAC commands generator API».
People can use it to debug the behaviour of the device on the transport level - to see what mac commands network server wants to apply, how the device evaluates them (what response, what channel using), etc...
By the way, @gotthardp how do you plan to manage the interoperability between the LoraWan standards, mostly different in LoRaWAN Mac Version? Do you plan to add the setting for the profiles/devices?
I think it may be better to extend the Frames list and display all the frame details there. To have the frame analyzer integrated.
Once I add support for lora 1.1 I will need to add also the protocol selector to the device Profile.
Hi @gotthardp , It will be great if you can add a new field for handlers:
Publish «downlinks» sent by the server: