Oms_FHSS_Initialize()
Abstract
This function will be called by a MAC process to indicate that FHSS should be used by that radio. Since the transmitter and receiver can have different hop sequences (different downlink and uplink channels), the MAC will initialize the transmitter and receiver separately. The FHSS parameters must be registered for each individual channel used by transmitter and receiver.
Syntax
Oms_FHSS_Initialize (tx_rx_type, fhss_attr_id, user_tx_state_ptr, tx_rx_id, tx_rx_chanid, bandwidth, num_unique_id, unique_id_array_ptr);
| Argument | Type | Description |
|---|---|---|
tx_rx_type |
OmsT_FHSS_Transceiver_Type |
Transmitter or Receiver Flag |
fhss_attr_id |
Objid |
FHSS compound attribute objid |
user_tx_state_ptr |
void* |
User Rx/Tx state pointer |
tx_rx_id |
Objid |
Tx/Rx objid |
tx_rx_chanid |
Objid |
Tx/Rx channel objid |
bandwidth |
double |
Channel bandwidth |
num_unique_id |
int |
Number of hop sequences |
unique_id_array_ptr |
double* |
Array of seeds |
Return Type
OmsT_FHSS_State_Info*
Details
Behavior:
- Read the FHSS attributes
- Create Tx/Rx state to store FHSS information
- Create hop sequences based on the attributes
- If hop sequence generation is contiguous, then create hop set starting form the low frequency value and incrementing by channel spacing until the high frequency is reached or the hop set size is reached.
- If hop sequence generation is random, then for each unique id, such as PRC net id, EPLRS initial frequency, etc., generate a random hop sequence with the unique id as seed. Note, since the seed will be the same for all nodes in a given network, all stations using the same unique id will create matching hop sequences.
- If FHSS model is "Abstract
- Calculate and store processing gain
Note: In the case of abstract FHSS modeling, the receiver needs only the processing gain to model the impact of FHSS. However, it is possible that the transmitter of this node can interfere with another receiver which has been configured to use detailed FHSS modeling and will have to use the hop sequence for channel matching. This is the reason for creating hop sequences, even if the node is configured to use abstract FHSS modeling.
Output
The Rx/Tx pointers, if allocated, will be accessible by the calling function.