Multiband VS Singleband: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (13 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Multiband == | |||
{{Warning|This page is a draft}} | |||
=== Multiband pros === | === Multiband pros === | ||
* It is possible to configure more than one band | * It is possible to configure more than one band with the data available in just this one test. This makes it possible to show data traces of both (or more) bands in one graph | ||
* It is very easy to add/remove bands or adjust them, even band gaps or overlaps are easily to configure | * It is very easy to add/remove bands or adjust them, even band gaps or overlaps are easily to configure | ||
* It is much more clear which band is using which test equipment | * It is much more clear which band is using which test equipment | ||
| Line 12: | Line 16: | ||
* After a RE test it is still possible to add/remove LLF | * After a RE test it is still possible to add/remove LLF | ||
* After sweeps during a RE test it is possible for the end-user to manually adjust the peaks | * After sweeps during a RE test it is possible for the end-user to manually adjust the peaks | ||
* The use of different | * The use of different polarization in one test could be done | ||
* During RE test it is possible to adjust the 'Change order' to sort the bands on defined conditions | * During RE test it is possible to adjust the 'Change order' to sort the bands on defined conditions | ||
== Multiband cons == | === Multiband cons === | ||
* It is not possible to configure specific Amplifier protection(s) during test configuration. Which means, that any .COR file attached to the Amplifier is automatically used. | * It is not possible to configure specific Amplifier protection(s) during test configuration. Which means, that any .COR file attached to the Amplifier is automatically used. | ||
| Line 21: | Line 25: | ||
* Not all tests available as Single band test are already implemented in Multiband (especially GTEM) | * Not all tests available as Single band test are already implemented in Multiband (especially GTEM) | ||
== Singleband pros == | == Singleband == | ||
=== Singleband pros === | |||
* A progress bar and estimated test time is shown during a test | * A progress bar and estimated test time is shown during a test | ||
* It is possible to configure which amplifier protection should be taken into account (signal power protection is always on). | * It is possible to configure which amplifier protection should be taken into account (signal power protection is always on). | ||
* During the test the | * During the test the | ||
== Singleband cons == | === Singleband cons === | ||
* It is not (easily) possible to export measurement data to e.g. .COR or .CAL files. | * It is not (easily) possible to export measurement data to e.g. .COR or .CAL files. | ||
| Line 36: | Line 42: | ||
* It is not possible for the end-user to manually adjust the peaks found during a RE test | * It is not possible for the end-user to manually adjust the peaks found during a RE test | ||
* During RE test it is not possible to have a 'Change order' and sort the bands on defined conditions | * During RE test it is not possible to have a 'Change order' and sort the bands on defined conditions | ||
* See also: [[Single_band_limitations | Singleband Limitations]] | |||
[[Category:RadiMation]] | |||
Latest revision as of 12:56, 14 August 2014
Multiband[edit]
 |
Warning: | This page is a draft |
Multiband pros[edit]
- It is possible to configure more than one band with the data available in just this one test. This makes it possible to show data traces of both (or more) bands in one graph
- It is very easy to add/remove bands or adjust them, even band gaps or overlaps are easily to configure
- It is much more clear which band is using which test equipment
- Adding field probe(s) to your configuration is much more logically
- It is possible to easily export data to e.g. .COR files or even as .CAL files.
- The graph module is more advanced
- The automatic peak detection is more advanced
- The regulation algorithm is more advanced
- The manual mode GUI is much more clearer to the end-user
- After a RE test it is still possible to add/remove LLF
- After sweeps during a RE test it is possible for the end-user to manually adjust the peaks
- The use of different polarization in one test could be done
- During RE test it is possible to adjust the 'Change order' to sort the bands on defined conditions
Multiband cons[edit]
- It is not possible to configure specific Amplifier protection(s) during test configuration. Which means, that any .COR file attached to the Amplifier is automatically used.
- No progress bar or estimated test time is shown during a test
- Not all tests available as Single band test are already implemented in Multiband (especially GTEM)
Singleband[edit]
Singleband pros[edit]
- A progress bar and estimated test time is shown during a test
- It is possible to configure which amplifier protection should be taken into account (signal power protection is always on).
- During the test the
Singleband cons[edit]
- It is not (easily) possible to export measurement data to e.g. .COR or .CAL files.
- The graph module has basic functionalities
- Not easy to remove bands or adjust them, also band gaps or overlaps are not easily to configure; most of the time you have to configure different tests and sequences and combine them to your demands.
- Adding field probe(s) to your configuration is now requiring some steps which are not very obvious.
- It is not possible after a RE test to add/remove LLF
- It is not possible for the end-user to manually adjust the peaks found during a RE test
- During RE test it is not possible to have a 'Change order' and sort the bands on defined conditions
- See also: Singleband Limitations