PDA

View Full Version : Question Atoll GSM Prediction



b0r3l_1
2011-09-25, 02:05 PM
Hi All

I need your comments and suggestions. Whenever I calculate on GSM prediction, the output coverage is somewhat very ideal even though I imported the clutters and terrain data. Another thing is, the area of coverage is limited to 3km radius so every site is forming a circle. Is this really how atoll calculates or there something wrong with my data. Kindly refer to my attached captured image.

Thanks

ledhie
2011-09-25, 02:19 PM
Have you check propagation model?

b0r3l_1
2011-09-25, 04:22 PM
Yes, im using the default okumura-hata model. How will will I calibrate it? Thanks

tremalnike
2011-09-25, 06:04 PM
It's not related to calibration.For every transmitter In Transmitter properties --> Propagation increase Radius to value that you want. You can do that for all transmitters in transmitter table.

http://www.finetopix.com/picture.php?albumid=21&pictureid=110

b0r3l_1
2011-09-25, 07:48 PM
@tremalnike

I've already changed the radius before but still have the same result.

ledhie
2011-09-25, 08:00 PM
Maybe you can try another model, you can find some tool to do that in this forum, example Crosswave prop. model from this thread : http://www.finetopix.com/atoll/16087-t-o-l-l-3-1-here-5.html

post #42 by dimitry28... and maybe if you lucky you can get help from the expert there....( FYI, I'm not include "the expert" there)

After that you can compare for the result from your model and crosswave model, which one more realistic.

redendo
2011-09-25, 09:10 PM
This kind of simulation is appreciated in the initial network dimensionning for coverage and capacity issue, but after that a calibrated model or a ray tracing models like crosswave is much more needed to get more realistic prediction

Kind regards

b0r3l_1
2011-09-26, 09:59 AM
Hi

Anyone has the lic file for the crosswave propagation? thanks

kevin_h811
2011-09-26, 11:02 AM
B0r3l_1,

Have you input your drivetest logfiles in CSV form,it does help too.

br//

telwind
2011-09-26, 11:30 AM
it looks your terrain data is not imported properly or it is too flat.

change propagation models, calculation radius and resolution may give more better looking.