I might be wrong of course.Ĭonsequently, I would expect Proprietary messages to have only a payload field that is the bytes of the MACPayload or something similar and a custom server to know how to handle this. The reason for this is that as you said, it should work for every message type except Proprietary and I don't think that there is any guarantee that there will be FHDR in a Proprietary message (or that you can assume anything more than the fact that it will have MHDR and MIC). If I am correct, I believe that the option with MType is the way to go. Am I misunderstanding the implementation? Uplink broadband (speed) and downlink broadband (speed) is asymmetric, generally the downstream speed is greater than the speed of the upstream. In that case I think that the current implementation will not work correctly. Uplink broadband (speed) refers to the speed of the upload, while the downlink broadband (speed) refers to the download data is several times. In this case the antenna that receives the packet will provide it to the bridge as PushData. I believe it is possible, for example, to receive an Unconfirmed Data Down send from another antenna (if two antennas are close enough). Answer (1 of 4): The way I see it, the transmission from an earth station towards a satellite is the uplink. In the current implementation it seems to me that whenever a packet is received on the UDP port and it is PushData, it is assumed to be uplink ( this part of the implementation approximately). I have a question related to this one (related to uplink field in PHYPayload). Really nice job with the packet parser and this bridge (and also the server □)!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |