-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LTE NLOS > 5000 #160
Comments
Hi @rtobi, can you share your scenario with us, e.g. by pushing it to a branch on GitHub? Having the same setup helps a lot to track down the reason for this issue. |
Thanks for the quick reply @riebl! |
I can confirm that adding a position offset (of 6000m, for example) to each eNodeB in lte-blackice/omnetpp.ini triggers the following error message: "Error NLOS urban macrocell path loss model is valid for d <5000 m -- in module (LtePhyUeD2D)" This is not a segmentation fault, but an error emitted deliberately by the SimuLTE model. I cannot say if SimuLTE supports out-of-coverage communication. Maybe @anupama1990 has some idea? |
I tried with the newest setup and can confirm your observations. Sorry for the confusion @riebl! So probably the segfault was solved somewhen in the past.
Still, it would be interesting to know from where the 5000 limitation comes from. As it is hardcoded, it seems there is no intention to increase/decrease this value. |
I don't know the reasoning behind the 5000m constant, but the SimuLTE developer @giovanninardini can probably give you details. I am not sure if he receives a notification when he is mentioned here, so you may ask directly on the SimuLTE project site. |
Hi,
Your error arises from LteRealisticChannelModel.cc::computeUrbanMircro() method.
Using the distance value, the path loss is calculated.
Regards,
Anupama
…________________________________
From: Raphael Riebl <notifications@github.com>
Sent: Monday, 22 February 2021 14:35:17
To: riebl/artery
Cc: Hegde, Anupama; Mention
Subject: Re: [riebl/artery] LTE NLOS > 5000 (#160)
I don't know the reasoning behind the 5000m constant, but the SimuLTE developer @giovanninardini<https://github.com/giovanninardini> can probably give you details. I am not sure if he receives a notification when he is mentioned here, so you may ask directly on the SimuLTE project site.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#160 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARV7JUFVZ2UJX2YIE5W57YTTAJMRLANCNFSM4X2EIK7A>.
|
Hi everyone, thanks @riebl for tagging me in this conversation, I don't get notifications for this repository. Best regards. |
Thanks @giovanninardini for your clarification, much appreciated! |
Thanks for clarification @riebl, @giovanninardini , @anupama1990! |
@rtobi SimuLTE only supports network-controlled D2D and we have no plans of adding out-of-coverage D2D in SimuLTE. To be fair, it is likely that SimuLTE will not be enhanced with new features at all, since we will probably migrate to the upcoming Simu5G. |
@giovanninardini thanks a lot for this information! Looking forward to Simu5G! |
Hi,
I am facing some issues when using a network of multiple eNodeBs. Vehicles are in range (distance < 5000) of one, but not of all base stations. Tolerating the distance violation (tolerateMaxDistanceViolation=true, LteChannelModel.ned) stops throwing the distance error, but comes along with a segmentation fault in the setup of the LTE network which I am not able to isolate.
The problem may be more related to the extern package simulte, but maybe someone faced similar issues and found a solution?
Many thanks in advance and best regards,
rtobi
The text was updated successfully, but these errors were encountered: