error in component

[aasif bashir dar]

hi all;

i got confused with the contineous wave laser component in the optisytem.
i was operating at the frequency of 193.1 THz…that by calculation

lambda= velocity of light/frequency=3000000000/193.1THz=1553.6nm (approx)

but when changed laser frequency units from THz to nano meter(nm) …. to my surprise it shows 1552.524381149663nm

this is huge error in component or may be i am doing some thing wrong(plesae check all )

please admin reply this
with regards

[aasif bashir dar]

hi all,
i am currenty using optisytem 14 (evaluation and licensed both)..

i am attaching the screen shots for better understanding;
look in figure 1 the unit is THZ

and in fiqure 2 the unit is change to nm and it should be arround 1553.6 nm , but it far less than that…. then fiqures are colured for better visvalization….

with regards

Attachments:

1. 

   12.png
   

2. 

   21.png
   

[FAYIQA NAQSHBANDI]

HELLO AASIF BASHIR..

I completely agree with you and it is an important point you have made here..actually i myself get confused sometimes when this happens it is not only with changing frequency.. i have seen this happening with power conversion also.. if you change power from dbm to milliwatts you get one value and when u convert same result back to dbm , there is variation by some decibels but it is manageable in that case..
bt in case of frequency to wavelength conversion it is a big issue since even .1 implies to huge values..

Thanks & regards

[aasif bashir dar]

yeah fayiqa naqshbandi,

it is actually ;

but optiwave people should respone to this problem here;;; so that our confusions are clear.
i also now it during power conversion processes… you are right about that fayiqa…

with regards

[FAYIQA NAQSHBANDI]

HI AASIF BASHIR..

You know it is not such a big problem in some some parameter conversions..however, in physical layout parameters like bit rate, frequency and wavelength this is a problem because as i mentioned in previous comment that in these cases even .1 decimal of difference means a lot while in other cases it is manageable.. still i hope the matter is cleared.

Thanks & regards

[burhan num mina llah]

Hi All

I was also facing the same problem. I won’t say problem coz it didn’t make much difference in regards to my project . I did attempt to change the frequency from THz to nm the value changed to some unexpected value but as u have mentioned in my case the value that i got for changing 193.1 THZ was not what i was expecting so i edited the values and took my results accordingly. I too would like to know hoq to overcome this.

Regards

Burhan

[FAYIQA NAQSHBANDI]

HELLO BURHAN..

I think you have done the right thing by changing the values again to the desired values and i think this is the easiest and go to way to overcome this problem.. One should definitely check the values after converting them to other units and if the values are unexpected we should make sure we replace them with correct values…it has an impact on the results too..

Thanks & regards

[Naazira Badar]

Hi all..
Yeah that surely happens. But I don’t think that would bring any significant variation in the results.
May be they round off the values as per component compatibility.

Regards.
Naazira .

[aasif bashir dar]

hi all,

i at first thought that it is only my problem, but now looks that it is problem in software
i think this can not not overcome in any way @ burhan num minallah, because it is inherent in software.

i is problem of software.. hope the optiwave people look on that

with regards

[burhan num mina llah]

Hi All

Aasif I don’t know how does it affect your project but in my case i had to just analyse the spectrum and i just forund that the spectrum just was smoother and hence a better result in regards to my project . Anyways best of luck with your case .

Regards

Burhan

[Sanjeev kumar]

thanks for the valuable suggestions friends

[SAHIL SINGH]

Hi Sanjeev Kumar,

Indeed you are welcome… And thanks everybody for your valuable suggestions…

Regards

Sahil Singh

[Damian Marek]

aasif bashir dar,

The velocity of light is not equal to 3E8 m/s. It is actually 299792458 m/s:

https://en.wikipedia.org/wiki/Speed_of_light

Try the calculation again!

[SAHIL SINGH]

Hi Aasif Bashir,

Indeed i agree with Damian about the numerical value as far as numerical value of velocity of light is concerned…. Also see the link as suggested in the previous post… It indeed will be very helpful to you..

Regards

Sahil Singh

[aasif bashir dar]

hi all

then calculations will be

lambda=299792458/193.1THz=1552.524381nm
…………….
thanks damain sir

with regards

[SAHIL SINGH]

Hi aasif bashir,

You are indeed right… Hope your problem is solved…

Regards

Sahil Singh

[Ranjeet Kumar]

Hi Aasif sir,
WDM wavelengths are positioned in a grid having exactly 100 GHz (about 0.8 nm) spacing in optical frequency, with a reference frequency fixed at 193.10 THz (1552.52 nm). The main grid is placed inside the optical fiber amplifier bandwidth, but can be extended to wider bandwidths. Today’s DWDM systems use 50 GHz or even 25 GHz channel spacing for up to 160 channel operation.
According to you “lambda= velocity of light/frequency=3000000000/193.1THz=1553.6nm (approx) but when changed laser frequency units from THz to nano meter(nm) …. to my surprise it shows 1552.524381149663nm”
The difference is nearly 0.8 nm.
It is due to channel spacing because by default channel spacing is 100 ghz(0.8 nm).
http://www.fiberoptic.com/adt_dwdm.htm

[Author]

Posts