I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. This is an error in the documentation. The name should start with the prefix "gr" and it must be in lower case, NOT the single letter "g". The documentation mistake has already been fixed back in 2005 in the TeX code, unfortunately the online web page version was never updated to reflect that.
This bug is a duplicate of https://sourceforge.net/p/mmtl/bugs/15/
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. This is an error in the documentation. The name should start with the prefix "gr" and it must be in lower case, NOT the single letter "g". The documentation mistake has already been fixed back in 2004 in the TeX code, unfortunately the online web page version was never updated to reflect that.
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. This is an error in the documentation. The name should start with the prefix "gr" and it must be in lower case, NOT the single letter "g". The documentation mistake has already been fixed back in 2004 in the source code, unfortunately the online web page version was never updated to reflect that.
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. This is an error in the documentation. The name should start with the prefix "gr" and it must be in lower case, NOT the single letter "g". The documentation mistake has already been fixed back in 2004, unfortunately the online web page version was never updated to reflect that.
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. This is an error in the documentation. The name should starts with lower case "gr" instead of the letter "g". The documentation mistake has already been fixed back in 2004, unfortunately the online web page version was never updated to reflect that.
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. Basically, MMTL's main field solver BEM calculates L and C by solving the mutual capacitance and mutual inductance of the transmission line using the Boundary Element Method. And speaking of R and G, the BEM solver does not consider the effect of dielectric loss or conductor loss when solving the fields, so G is out. Although it does try to calculate conductor...
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. At low frequencies, crosstalk increases linearly, but high frequencies, transmission line resonance effect starts to take over. MMTL calculates the crosstalk solely based on the mutual capacitance, mutual inductance, and propagation velocity, thus, resonance effects are completely neglected. This can be seen from the source code: bem/src/nmmtl_xtk_calculate.cpp....
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. At low frequencies, crosstalk increases linear-in-dB, but high frequencies, transmission line resonance effect starts to take over. MMTL calculates the crosstalk solely based on the mutual capacitance, mutual inductance, and propagation velocity, thus, resonance effects are completely neglected. This can be seen from the source code: bem/src/nmmtl_xtk_calculate.cpp....
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. At low frequencies, crosstalk increases linear-in-dB, but high frequencies, transmission line resonance effect starts to take over. MMTL calculates the crosstalk solely based on the mutual capacitance, mutual inductance, and propagation velocity, thus, resonance effects are completely neglected. This can be seen from the source code: bem/src/nmmtl_xtk_calculate.cpp....
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. At low frequencies, crosstalk increases linear-in-dB, but high frequencies, transmission line resonance effect starts to take over. MMTL calculates the crosstalk solely based on the mutual capacitance, mutual inductance, and propagation velocity, thus, resonance effects are completely neglected. This can be seen from the source code: bem/src/nmmtl_xtk_calculate.cpp....
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. At low frequencies, crosstalk increases linear-in-dB, but high frequencies, transmission line resonance effect starts to take over. MMTL calculates the crosstalk solely based on the mutual capacitance, mutual inductance, and propagation velocity, thus, resonance effects are completely neglected. This can be seen from the source code: bem/src/nmmtl_xtk_calculate.cpp....
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. At low frequencies, crosstalk increases linear-in-dB, but high frequencies, transmission line resonance effect starts to take over. MMTL calculates the crosstalk solely based on the mutual capacitance, mutual inductance, and propagation velocity, thus, resonance effects are completely neglected. This can be seen from the source code: bem/src/nmmtl_xtk_calculate.cpp....
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. At low frequencies, crosstalk increases linear-in-dB, but high frequencies, transmission line resonance effect starts to take over. MMTL calculates the crosstalk solely based on the mutual capacitance, mutual inductance, and propagation velocity, thus, resonance effects are completely neglected. This can be seen from the source code: bem/src/nmmtl_xtk_calculate.cpp....
I know this is an old thread and that the project is unmaintained. But as another user of TNT-MMTL, I think it's useful to answer this question. BEM can be invoked manually in the command-line by running the executable "bem" with the following command-line arguments: bem <filename> <c-seg> <p-seg> <filename> - name of the graphic file <c-seg> - number of contour segments <p-seg> - number of plane/dielectric segments <filename> is the xsctn file generated by MMTL, without the .xsctn extension name....
I have noticed that the FEXT crosstalk seems to be proportional to the rise time in the simulation results. If we look at a FEXT s-parameter curve in another simulator, we can notice that FEXT linearly increases with the knee frequency (f=0.35/trise), but only up to fmax=0.5/t_pd. bove that it goes up and down periodically, and lingers around -60...-20dB. On a 5" trace that limit is 0.5GHz. TNT MMTL still gives me linearly increasing FEXT as I keep changing the rise time parameter in the range of...
Coplanar Feature Not Working
drag-drop onto windows icon does not towk
best iteration not found
Build fix for modern gcc.