-
Notifications
You must be signed in to change notification settings - Fork 38
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
How to set Pcmax #18
Comments
Using: Config::SetDefault ("ns3::LteUePowerControl::Pcmax", DoubleValue (31.0)); // does not fail However running simulations for PC1 with: And then position of the node Ue2 was changed to 1300 and 1400 m, the simulation returned the same number of Rx packets between PC3 and PC1 power levels. Ptr positionAllocUe1 = CreateObject (); For a distance of 1400m both PC1 and PC3 simulations show the same number of rx packets 2! At 1300m both PC1 and PC3 show all 30 packets: And at a distance of 1500 both PC1 and PC3 simulations show 0 rx packets. Clearly more needs to be done for a correct PC1 simulation. |
With power control, there are several places that configure the maximum transmit power. The following variable need to be modified: Config::SetDefault ("ns3::LteUePhy::TxPower", DoubleValue (23.0)); |
This works. |
Slightly modifying lte-sl-out-of-covrg-comm.cc for PC1 simulation.
Increased TxPower to 31, but results no different than 23.0 setting
Config::SetDefault ("ns3::LteUePhy::TxPower", DoubleValue (31.0)); // simulation results no different from 23.0 setting
Probably Pcmax must be increased however it is not obvious how to do it.
Config::SetDefault ("ns3::LteUePowerControl::SetPcmax", DoubleValue (31.0)); // does not work
'build' finished successfully (4.046s)
msg="Could not set default value for ns3::LteUePowerControl::SetPcmax", file=../src/core/model/config.cc, line=854
terminate called without an active exception
Any hint would be welcome, and if this will be enough for PC1 results.
The text was updated successfully, but these errors were encountered: