An error occurred fetching the project authors.
  1. 02 Jun, 2019 1 commit
  2. 15 May, 2019 2 commits
  3. 09 May, 2019 1 commit
  4. 06 May, 2019 1 commit
  5. 29 Apr, 2019 2 commits
  6. 26 Apr, 2019 1 commit
  7. 18 Apr, 2019 1 commit
  8. 17 Apr, 2019 2 commits
  9. 16 Apr, 2019 1 commit
  10. 12 Apr, 2019 1 commit
  11. 11 Apr, 2019 1 commit
  12. 10 Apr, 2019 1 commit
  13. 05 Apr, 2019 2 commits
  14. 04 Apr, 2019 1 commit
  15. 03 Apr, 2019 1 commit
    • Cedric Roux's avatar
      bugfixes for the ue T tracer · 4905a5e8
      Cedric Roux authored
      Not much major changes. In openair1/PHY/LTE_UE_TRANSPORT/dci_tools_ue.c,
      in the function generate_ue_dlsch_params_from_dci,
      'harq_pid' was removed and dci_info_extarcted.harq_pid is now used for
      all cases.
      
      The ue T tracer only deals with PHY signals (no MAC, RLC, PDCP, RRC).
      4905a5e8
  16. 27 Mar, 2019 1 commit
  17. 19 Mar, 2019 2 commits
    • Cedric Roux's avatar
      PHY: add parameter end_of_burst_delay for TDD · 275e5b3a
      Cedric Roux authored
      end_of_burst_delay is used to stop TX only "after a while".
      If we stop right after effective signal, with USRP B210 and
      B200mini, we observe a high EVM on the S subframe (on the
      PSS).
      A value of 400 (for 30.72MHz) solves this issue. This is
      the default.
      
      This default value can be changed in the configuration file.
      For example:
      
      RUs = (
          {
             local_rf       = "yes"
               nb_tx          = 1
               nb_rx          = 1
               att_tx         = 20
               att_rx         = 0;
               bands          = [7];
               max_pdschReferenceSignalPower = -27;
               max_rxgain                    = 105;
               eNB_instances  = [0];
               sf_extension = 312;
               end_of_burst_delay = 200;
          }
      );
      
      Here we would set a value of 200.
      
      The value to put in the configuration file is for
      30.72MHz. The value is scaled accordingly at runtime
      (thus only one value to set for every RB configuration,
      25, 50 or 100, leading to less problems when adapting
      configuration files).
      
      This option is for experts and should not be changed
      randomly.
      275e5b3a
    • Cedric Roux's avatar
      PHY: make sf_extension a parameter · ee5b7390
      Cedric Roux authored
      This parameter is meaningful in TDD, to decide
      when to start DL at eNB side. Since there is a
      need for the PA to be operational, we need to
      transmit a bit before the DL subframe coming
      after an UL subframe. (We transmit zeros.)
      
      We used to use N_TA_offset which may be too much.
      Default value is now N_TA_offset/2 and can be
      changed in the configuration file, in the RUs
      section, like:
      
      RUs = (
          {
             local_rf       = "yes"
               nb_tx          = 1
               nb_rx          = 1
               att_tx         = 0
               att_rx         = 0;
               bands          = [7];
               max_pdschReferenceSignalPower = -27;
               max_rxgain                    = 105;
               eNB_instances  = [0];
               sf_extension = 312;
          }
      );
      
      N_TA_offset is 624 (for 30.72MHz). In the example
      above, we set sf_extension = 312, which is also
      the default.
      
      The value to put in the configuration file is for
      30.72MHz. The value is scaled accordingly at runtime
      (thus only one value to set for every RB configuration,
      25, 50 or 100, leading to less problems when adapting
      configuration files).
      
      This option is for experts and should not be changed
      randomly.
      ee5b7390
  18. 15 Mar, 2019 1 commit
  19. 13 Mar, 2019 1 commit
  20. 12 Mar, 2019 1 commit
  21. 09 Mar, 2019 1 commit
  22. 08 Mar, 2019 2 commits
  23. 05 Mar, 2019 1 commit
  24. 04 Mar, 2019 1 commit
  25. 02 Mar, 2019 1 commit
  26. 28 Feb, 2019 1 commit
  27. 26 Feb, 2019 2 commits
  28. 25 Feb, 2019 4 commits
  29. 22 Feb, 2019 1 commit
  30. 19 Feb, 2019 1 commit