@@ -4,7 +4,9 @@ It replaces a actual RF board driver.
...
@@ -4,7 +4,9 @@ It replaces a actual RF board driver.
As much as possible, it works like a RF board, but not in realtime: it can run faster than realtime if there is enough CPU or slower (it is CPU bound instead of real time RF sampling bound)
As much as possible, it works like a RF board, but not in realtime: it can run faster than realtime if there is enough CPU or slower (it is CPU bound instead of real time RF sampling bound)
#build
#build
## From build_oai
You can build it the same way, and together with actual RF driver
You can build it the same way, and together with actual RF driver
Example:
Example:
...
@@ -18,10 +20,19 @@ It is also possible to build actual RF and use choose on each run:
...
@@ -18,10 +20,19 @@ It is also possible to build actual RF and use choose on each run:
Will build both the eNB (lte-softmodem) and the UE (lte-uesoftmodem)
Will build both the eNB (lte-softmodem) and the UE (lte-uesoftmodem)
We recommend to use the option --ue-nas-use-tun that is much simpler to use than the OAI kernel driver.
We recommend to use the option --ue-nas-use-tun that is much simpler to use than the OAI kernel driver.
#usage
## Add the rfsimulator after initial build
After any regular build, you can compile the driver
```bash
cd <the_compilation_dir_from_bouild_oai_script>/build
make rfsimulator
```
Then, you can use it freely
# Usage
Setting the env variable RFSIMULATOR enables the RF board simulator
Setting the env variable RFSIMULATOR enables the RF board simulator
It should the set to "enb" in the eNB
It should the set to "enb" in the eNB
## 4G case
For the UE, it should be set to the IP address of the eNB
For the UE, it should be set to the IP address of the eNB
example:
example:
```bash
```bash
...
@@ -33,6 +44,23 @@ If you reach 'RA not active' on UE, be careful to generate a valid SIM
...
@@ -33,6 +44,23 @@ If you reach 'RA not active' on UE, be careful to generate a valid SIM