Closed vfylyk closed 3 years ago
If you would like to create a PR for this, that would be much appreciated :+1:
Where the LNS Protocol docs mention that the LNS must answer, I think it makes sense to let the ChirpStack Gateway Bridge respond with the gps timestamp.
The github.com/brocaar/lorawan/gps
package provides an utility to convert from a time.Time
to GPS time (time.Duration
): https://pkg.go.dev/github.com/brocaar/lorawan@v0.0.0-20200903101545-e07a1f3df89c/gps
E.g.
gpsTime := gps.Time(time.Now()).TimeSinceGPSEpoch()
Thanks @brocaar, I'll give it a try when a get a moment.
Summary
It seems like the current Basic Station implementation does not include support for the LNS @timesync@ message type, so it would be great if it could be included.
This is what happens currently:
What is the use-case?
The most recent Cisco IXM gateway comes with Basic Station support, using GPS and @timesync@ messages to provide timestamps. Whenever possible I prefer to have timestamps applied at the gateway as they more accurately tell when a payload has been received.
Implementation description
The LNS Protocol indicates how this is implemented.
Can you implement this by yourself and make a pull request?
I can give it a try.