Log & Packet Interaction |
Top Previous Next |
This topic covers the most interesting interactions between the log and packet facilities in both directions: From packet to log and vice versa. These interactions is what makes TurboLog 4 verify its name as a turbo- powered log and the discerning DXer's sound decision.
From Packet to Log:
It is of greatest importance to QSY the rig to a spot's frequency and to prepare everything for logging the spotted station if there is urgent need for this one for DXCC, IOTA or any other purpose. One should have logged the station before the crowds arrive and the pile builds up. This feature is implemented in TurboLog 4 by two methods, either by mouse drag & drop or even faster by just one keystroke. A focused spot will deliver the call right away into the call field of any open loginput line and QSY the rig to the spot's frequency (if Automode is activated) on pressing Ctrl+G, where the G stands for Grab.
Please note: If MultMode is in progress the spot's information will also be transferred into the log input line of the MuliMode window. This is of particular benefit while running a RTTY contest. The same applies for the Drag & Drop operation (see below).
The focus will jump onto the call field and you will find the spot's call along with information from the spot's comment field being entered. You only need to work the station and press Enter and the "prey" will be logged. If you don't hear the station because it is gone already or the spot was a fake you may wish to return to where you came from. This is no problem: Just press Ctrl+G again and you will be back. The call, however, will remain in the call field's input stack for future use during the current session.
A similar action is available from the Packet Screen. Pressing the Grab button on the control panel will transfer the latest or highlighted spot into the call field.
If a Packet spot was matching a preset call alarm you will receive an alarm message which is displayed on conspicuous red background in the Alarms & Messages window. If you were away from the screen for a while and now realize there was an alarm you may want to get to the spot the fastest way. You do not need to search for the spot in the packet grid. Just click the alarm message in order to select it. If you next click the Grab button or press Ctrl+G your rig will immediately QSY to the spotted frequency.
Likewise you can click a spot and drag it by keeping the left mouse key pressed while moving the mouse in order to drop the spot on the call field by releasing the key ( Drag & Drop action ). This yields the same results: •The rig will QSY to the spot's frequency, •The focus will jump onto the call field of all active log input lines and •The spot's call is being entered. •The spot's call being placed in the call field's input stack. • This Drag & Drop action, however, cannot be reversed.
Please note: Both procedures are available globally. They will work in every packet grid. Moreover, they will even work from the log window in review mode. In the latter case, however, the rig will not QSY since one should anticipate that the user is only interested in picking up the call from an earlier QSO for the sake of a fast entry to the call field.
From Log to Packet:
The log automatically provides valuable data for sending spots and other packet cluster communications. A call entered in the call field of the log input line will be transferred into the template for sending a DX spot. In a addition to this the frequency will be read automatically from the CAT facility and placed in the frequency field.
If the call field of the log input line should be empty while sending a DX spot is activated the focused frame is interrogated whether it possesses a call field. If it exists and it contains a valid call string this one will be read and placed in the template. If no such field exists the user has to enter the call in the template manually.
The same applies to the frequency. If no valid number can be read from the CAT while the log input line is focused the user has to enter it manually in the template. If, however, a spot would have been focused the frequency would be read from there along with the call.
Besides these utilities the log also provides the DXCC information against which the packet facility checks the "value" of a spot with respect to the user's DXCC achievements. This is extremely important information for the user since it will trigger off his activity or leave him relaxed.
CLICKABLES and HOTSPOTS:
KEYS:
This topic was last edited on Monday, 03-Jul-2023, at 23:57
|