Eric Blossom wrote: > What your asking for would be hard to do using the existing framework.
I still don't understand where you want to do this from. That is, which code would be making the determination that it was time to pause or unpause the timer.
For instance, a new node enters a backoff state and decides that it needs to wait for the channel to be idle for 10ms before it can transmit (802.11 like). It starts a one shot timer for 10ms, and with each new RSSI reading from the PHY, which comes at variable times due to processing and queues, the protocol checks if the new RSSI reading is greater than some CCA threshold. If it's greater, it needs to pause the timer because the timer represents the time at which the node must wait when the channel is idle, not busy. Once the RSSI drops below the CCA threshold, it can then resume the timer. Once the timer fires, the node attempts to transmit.
- George _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
