1. 07 Feb, 2018 1 commit
  2. 06 Feb, 2018 2 commits
  3. 01 Feb, 2018 1 commit
  4. 31 Jan, 2018 1 commit
  5. 30 Jan, 2018 2 commits
  6. 24 Jan, 2018 1 commit
  7. 22 Jan, 2018 1 commit
  8. 18 Jan, 2018 2 commits
  9. 15 Jan, 2018 1 commit
  10. 14 Jan, 2018 1 commit
  11. 12 Jan, 2018 1 commit
  12. 11 Jan, 2018 1 commit
  13. 04 Jan, 2018 1 commit
  14. 03 Jan, 2018 2 commits
  15. 25 Dec, 2017 1 commit
  16. 23 Dec, 2017 1 commit
  17. 20 Dec, 2017 1 commit
  18. 27 Nov, 2017 1 commit
  19. 23 Nov, 2017 1 commit
  20. 14 Nov, 2017 2 commits
  21. 13 Nov, 2017 1 commit
  22. 06 Nov, 2017 1 commit
  23. 05 Nov, 2017 2 commits
  24. 03 Nov, 2017 1 commit
  25. 02 Nov, 2017 2 commits
  26. 01 Nov, 2017 1 commit
  27. 30 Oct, 2017 2 commits
  28. 28 Oct, 2017 1 commit
  29. 27 Oct, 2017 1 commit
  30. 25 Oct, 2017 2 commits
    • David Price's avatar
      Crashes around msg4 time, but understand that need to get the ACK for the UE... · 7a577094
      David Price authored
      Crashes around msg4 time, but understand that need to get the ACK for the UE UL of msg3 back to UE within 4ms
      7a577094
    • Cedric Roux's avatar
      bugfix: fix timing advance · 6da42658
      Cedric Roux authored
      - remove global variables in the function lte_est_timing_advance_pusch
      - do the smoothing logic that was in lte_est_timing_advance_pusch
        in rx_sdu (is it necessary? is it correct?)
      - put back the value 100 in prach_procedures for the test on prach energy
      - change the value of timing_advance_update
      
        it was:
      
           timing_advance_update                  = sync_pos - eNB->frame_parms.nb_prefix_samples/4; //to check
      
        it is now:
      
           timing_advance_update                  = sync_pos; // - eNB->frame_parms.nb_prefix_samples/4; //to check
      
        this should be checked somehow. The computation looked suspicious. Maybe
        the new one is wrong.
      6da42658
  31. 23 Oct, 2017 1 commit