Difference between revisions of "OtherWindows"
m (Images.) |
m (Updating images.) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Raw Data Window = | = Raw Data Window = | ||
Accessible from View -> Raw Data Window. The Raw Data Window shows the "raw" decoded data being feed into ATCSMon, this is usually used for exploring new protocols or troubleshooint existing ones. Most people will never use this window. | Accessible from View -> Raw Data Window. The Raw Data Window shows the "raw" decoded data being feed into ATCSMon, this is usually used for exploring new protocols or troubleshooint existing ones. Most people will never use this window. | ||
| − | + | [[File:RawDataWindow.jpg]] | |
| − | |||
= Dispatcher Display = | = Dispatcher Display = | ||
| Line 10: | Line 9: | ||
Accessible from View -> Connection Window. The Connections Window show what server(s) you are connected to. | Accessible from View -> Connection Window. The Connections Window show what server(s) you are connected to. | ||
| − | + | [[File:ConnectionWindow.jpg]] | |
= Message Type Details = | = Message Type Details = | ||
Accessible from View -> Message Type Details. The Message Type Details window serves as a quick reference to the various message types, and their purpose. | Accessible from View -> Message Type Details. The Message Type Details window serves as a quick reference to the various message types, and their purpose. | ||
| − | + | [[File:MessageTypeDetails.jpg]] | |
= Server Log = | = Server Log = | ||
Accessible from View -> Server Log. The Server Log Window looks similar to the Connections window. This option is only available if you are running in server mode, and have "Enable server connection logging" in Option -> General. | Accessible from View -> Server Log. The Server Log Window looks similar to the Connections window. This option is only available if you are running in server mode, and have "Enable server connection logging" in Option -> General. | ||
| − | + | [[File:ServerLog.jpg]] | |
= Analyze Signal = | = Analyze Signal = | ||
Accessible from View -> Analyze Signal or using the green sine-wave button on the tool bar. The first three images below show a good signal level. Notice that the window will look different based on which protocol the application is decoding. You want to pay attention to the upper wave form in the display. You can adjust it using the slider at the bottom of the window. | Accessible from View -> Analyze Signal or using the green sine-wave button on the tool bar. The first three images below show a good signal level. Notice that the window will look different based on which protocol the application is decoding. You want to pay attention to the upper wave form in the display. You can adjust it using the slider at the bottom of the window. | ||
| − | [[File: | + | [[File:AnalyzeSignalWindow_ATCS.JPG]] |
| − | [[File: | + | |
| + | [[File:AnalyzeSignalWindow_ARES.jpg]] | ||
| − | + | [[File:AnalyzeSignalWindow genisys.jpg]] | |
The following two images all show problems with the signal level. | The following two images all show problems with the signal level. | ||
| Line 34: | Line 34: | ||
The first image shows to little signal/volume. This could either be because the slider is turned down all the way, or you don't have the scanner hooked up, (or tapped) correctly. In this image there isn't a scanner hooked up, so ATCSMon is picking up background noise through the built-in microphone. | The first image shows to little signal/volume. This could either be because the slider is turned down all the way, or you don't have the scanner hooked up, (or tapped) correctly. In this image there isn't a scanner hooked up, so ATCSMon is picking up background noise through the built-in microphone. | ||
| − | + | [[File:AnalyzeSignalWindow NoSignal.jpg]] | |
This is a good example of too much signal. You can see that the signal is "clipping" giving you flat spots on the top and bottom wave form. It's possible that you may still get decoded packets, however, you'll see higher error rates then with a properly adjusted signal. | This is a good example of too much signal. You can see that the signal is "clipping" giving you flat spots on the top and bottom wave form. It's possible that you may still get decoded packets, however, you'll see higher error rates then with a properly adjusted signal. | ||
| − | + | [[File:AnalyzeSignalWindow TooMuchSignal.jpg]] | |
Latest revision as of 11:34, 14 April 2017
Raw Data Window
Accessible from View -> Raw Data Window. The Raw Data Window shows the "raw" decoded data being feed into ATCSMon, this is usually used for exploring new protocols or troubleshooint existing ones. Most people will never use this window.
Dispatcher Display
Accessible from View -> Dispatchers Display. We all know what this is. :)
Connection Window
Accessible from View -> Connection Window. The Connections Window show what server(s) you are connected to.
Message Type Details
Accessible from View -> Message Type Details. The Message Type Details window serves as a quick reference to the various message types, and their purpose.
Server Log
Accessible from View -> Server Log. The Server Log Window looks similar to the Connections window. This option is only available if you are running in server mode, and have "Enable server connection logging" in Option -> General.
Analyze Signal
Accessible from View -> Analyze Signal or using the green sine-wave button on the tool bar. The first three images below show a good signal level. Notice that the window will look different based on which protocol the application is decoding. You want to pay attention to the upper wave form in the display. You can adjust it using the slider at the bottom of the window.
The following two images all show problems with the signal level.
The first image shows to little signal/volume. This could either be because the slider is turned down all the way, or you don't have the scanner hooked up, (or tapped) correctly. In this image there isn't a scanner hooked up, so ATCSMon is picking up background noise through the built-in microphone.
This is a good example of too much signal. You can see that the signal is "clipping" giving you flat spots on the top and bottom wave form. It's possible that you may still get decoded packets, however, you'll see higher error rates then with a properly adjusted signal.
