Still Don't Get It...14 Dec 2022 17:51
Redeye says, Extract,
"Expanding the offering
In our view, the collaboration enables Wyld to access use cases that require two-way data communication. We believe these types of use cases can be found, for example, among utilities that need to take direct action on the data sent from the modules or sensors. For instance, it could be a switch that needs to be turned on or off, depending on the data/information received. With the current license-free spectrum (via LoRa and LoRaWAN) it is not possible to send two-way data. Astocast uses the L-Band spectrum, which enables two-way data communication. However, this type of data is much more expensive than data sent one way via an unlicensed spectrum. Therefore, we think that the most likely customers are within the utilities sector, where budgets and the need for two-way data communication can be found. We think the agreement will complement the other two satellite-provide agreements with Eutelsat and Lacuna Space. We find it encouraging that Wyld is proceeding according to its growth plan, expanding into new use cases and new markets. Now, we want to see the order book increase accordingly since we believe this agreement was occasioned by customer demand."
Access to the L-Band gives Wyld the opportunity the provide two way communication that the Lorawan Specification does not supply...
However,
https://lora-alliance.org/about-lorawan/
Under the Topology Tab.
"*All modes are capable of bi-directional communication*, and there is support for multicast addressing groups to make efficient use of spectrum during tasks such as Firmware Over-The-Air (FOTA) upgrades or other mass distribution messages."
But. Under the Classes Tab there are three defined classes. Class A, Class B and Class C. It's a bit confusing because of the way it defines, or rather does not, end devices. However all of them are capable of bi-directional operation it just appears to be a question of relative power consumption.
Define the uplink as the sensor and define the downlink as the satellite.
Class A requires the downlink to be always available. Lowest Power.
Class B requires the downlink to be periodically available. It is but the latency is, up to, 128 seconds.
Class C requires the uplink to listen continuously for the downlink. Highest power.
With A the satellite is not always there.
With B the satellite is not there often enough.
With C your battery gets stuffed.
Either way, as Mr Rees surmises it just does or should not work if there is not a means of synchronization once communications are initiated. There are permitted timeslices available within any period of communication. I could be wrong...
However. I cannot imagine that you are not allowed to bend or break B by extending the 128 second limit and still live within the specification. All you have to do is change the timing so you listen for the satellite every 128 seconds at the time the satellite is available and go to sleep other
Sign In
Follow the stocks
