Administrator
|
KX2 beta firmware rev. 2.77 is now available on our KX2 firmware/software page (http://www.elecraft.com/KX2/kx2_software.htm). See full details in the release notes below.
A number of KX2 owners have been testing the new logging feature and have found that it works well for casual QSOs as well as for SOTA activations, etc. If your KX2 has the KXIO2 option installed, the log time stamps will use data from the KXIO2’s real time clock. 73, Wayne N6KR * * * KX2 MCU rev. 2.77 BUILT-IN LOGGING (CW and DATA MODES): When using the KX2 hand-held, logging may be difficult. The KX2 can now capture up to 2048 transmitted characters, along with time, band, and mode, so you can update a paper or electronic log later on. To enable logging, set MENU:LOGGING to ON. Logging applies to CW (C), PSK-D (P) and FSK-D (F) modes, and only when using the internal keyer. To take advantage of time stamping, either set the time (MENU:TIME) on every power-up of the KX2, or install a KXIO2, which includes a real-time clock powered by the internal battery. When logging is enabled, the DVR icon (above the S-meter) flashes slowly. Outgoing text decode is turned on, allowing you to make sure you’ve sent call signs accurately. If you fill the log, LOG FULL will be shown briefly, and the DVR icon will stop flashing. To review logged text, tap DISP and rotate VFO B to find the LOG display. The VFO A knob can then be used to scroll through text. Time/mode/band are shown on VFO A (e.g., “0023 C14”); text is shown on VFO B. Holding CLR erases the entire log. To “dump” the log, send “LG;” to the KX2 via KX2 Utility’s Command Tester screen. Tips: To conserve space, use message buffers (MSG) to send CQs, name/QTH, etc. Messages are not recorded in the log. To start/stop logging quickly, assign the LOGGING menu entry to a programmable function switch (PF1-PF4). ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Hi Wayne,
Testing the new logging feature in 2.77. A couple of suggestions: When dumping the log using LG; can the dump stop after dumping the last valid character, rather then a long string of "-------" ? Can the memory keyer operations be logged. Maybe just a M# or some other character string which can be identified as a memory keyer with number operation. Maybe an "R" for repeat. John KN5L ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
This post was updated on .
In reply to this post by wayne burdick
Wayne,
I have had good success with the KX2 logging function for CW SOTA. Works well and quite easy to review and transfer using the LG; command in KX2 Utility. The only issue I have is storage, even using memory for CQs it's full after 50 of my short SOTA exchanges. Is there any way storage could be doubled, or even 3K rather than 2K? If 2K is all that is available, perhaps the Band, Mode and time could just be embedded into the main stream like <0951> rather than having using half of the memory with its own stream? Here is the top of my latest log, not much surplus information in there 73 Gavin GM0GAV 0948C10 0949 0950 K K K K SP9AMH SP9AMH 5NN BK SP9AMH SP9AMH 5NN BK RRR OK FB TNX 73 0951 73 DE GM0GAV/P DL4FDM DL4FDM 5NN OK 73 GM0GAV/P EA2DT EA2DT 5NN 0952 OK73 DE GM0GAV/P DJ1YFK DJ1YFK GM FABIAN 5NN BK OK CU 73 GM0GAV/P 0953 PB2T PB2T 5NN BK OK 73 GM0GAV/P F6EAZ F6EAMI 5NN F6EAZ 5NN OK73 GM 0954 0GAV/P OK2PDT OK2PDT 5NN OKTNX73GM0GAV ? GM0GAV/P DL3FT DL3FT 5NN 0955 |
Free forum by Nabble | Edit this page |