I am experimenting with Class B operation on the V3 servers. Should this be working? So far I can place my device in Class B operation and receive beacons OK. Uplink packets reach the server. Downlink packets reach the device in Class A but not in Class B. (I generate a single byte payload on port…

[image] How do I format my forum post? [HowTo] How to get started The TTN forum is using Discourse , which supports several ways to format your post: Markdown BBCode HTML Any combination of the above Quite often you’ll need an empty line above specific formatting to make…

[image] acutetech: the message is rejected (in the V3 Device Live Data feed) because “gateway time is not GPS synchronized” (AFAIK the GPS is working fine). Can you show some raw uplink reports from this gateway and check if they include valid GPS times?

Hmmm… behaviour is complex and I get different results with different attempts at sending the downlink message. Once the downlink packet arrived. Usually it does leave TTN. It is difficult for me to keep an eye on my device’s console, my local gateway packet forwarder and two TTN consoles (gateway a…

[image] acutetech: I am happy to work with TTN on this, but not this way: it has taken an hour to write this post. Perhaps you can watch my consoles from your office, while I push buttons on my device, and share a screen? You are aware you are using the community network for free and 99% of t…

Here is some more information. It is only a partial picture, but it accounts for some of what I am seeing and perhaps points towards an explanation and solution. First, Jac asks: [image] kersing: In the statistics overview, does the packet forwarder state it has a valid GPS position? I can …

I thought I would check if ACK downlink packets worked OK. They do. When in class B the server appears to receive and respond to both unconfirmed and confirmed uplink messages. That is, it sends downlink packets to the gateway with the ACK response and these are passed to my device. It looks like th…

[image] acutetech: As before, an attempt to send a downlink message from the TTN device console gives the “Failed to schedule” error with “gateway time is not GPS synchronized”. It seems like you see this when there isn’t a recent uplink with GPS timing information in it - so it seems the net…

I looked at what the packet forwarder messages contain with and without GPS. For the “stat” messages the only difference is the “lat”, “long” and “alti” fields which are absent without GPS. In both cases the “stat” messages contain “time” fields which I guess must come from somewhere else in the abs…

[image] acutetech: TTN’s servers report a problem: what is the algorithm? (is it open-source?). The back-end code for V3 is open source and has been so from the start. (As was most of V2 and predecessors) [image] GitHub - TheThingsNetwork/lorawan-stack: The Things Stack, an Open Sour…

[image] acutetech: Also, IMHO, the server should not withold the downlink message. If it thinks your gateway’s GPS fix is wrong, then, no, it most definitely needs to witthold the request, transmitting a timed downlink at even slightly the wrong time would be quite problematic. As far as th…

Class B Downlink fails: (in 2 different ways)

Uncategorized

descartes (Nick McCloud) March 23, 2021, 8:50am 2