You are not logged in.
while analyzing wl_example_basic_txrx code in WARPlab reference design7.7.1 i came to know that 2.4 GHz band has 11 channels and 5GHz band has 23 channels which can be alloted to nodes using wl_interfaceCmd(nodes, ifc_ids.RF_ALL, 'channel', 2.4, 11);. I want to know that using the same syntax can we allot different bands to RFA and RFB of the same WARP node for instance
wl_interfaceCmd(nodes, ifc_ids.RF_A, 'channel', 2.4, 8);
wl_interfaceCmd(nodes, ifc_ids.RF_B, 'channel', 2.4, 1);
Will it work? If yes than how can we justify that which RF node is transmitting on which channel through plots or code itself? How can we sense the channels?
Offline
I want to know that using the same syntax can we allot different bands to RFA and RFB of the same WARP node for instance
wl_interfaceCmd(nodes, ifc_ids.RF_A, 'channel', 2.4, 8);
wl_interfaceCmd(nodes, ifc_ids.RF_B, 'channel', 2.4, 1);
Will it work?
Did you try it? The WARPLab code makes it easy to experiment - asking us to confirm every command is inefficient.
This is the correct syntax to tune the RF A and B interfaces to different channels. The WARP v3 hardware supports this.
Offline
Yes sir i tried it and it is executing correctly, but my question is how can i distinguish this thing that which RF node is transmitting on which channel of a particular band at the receiver end?
Offline
One more question is that I came across the syntax
read_tx_rx_state
Read the current state of the interface
Requires BUFF_SEL: Yes
Arguments: none
Returns: Current state of the buffer: TX, RX or STANDBY
How can i implement it to read the current state of the interface?
Offline
The state of the RF interface is whatever your MATLAB code last set. The WARPLab design executes commands sent from MATLAB - your M code has full control of the hardware.
Offline
When I used this command, it returns the value 2 for tx node and 1 for rx node.But as per the description it should return current state of the buffer: TX, RX or STANDBY. Why i am getting ans 2 & 1? Does it refers that the nodes are busy because when they are not transmitting or receiving it returns value 0.
Last edited by VATSALA SHARMA (2019-Jul-27 00:56:00)
Offline
Did you look at the source code? The STANDBY/RX/TX/ values are constants defined as 0/1/2.
Offline