eHam

eHam Forums => Computers And Software => Topic started by: KC2LYQ on April 21, 2007, 06:44:04 PM



Title: Logging Software
Post by: KC2LYQ on April 21, 2007, 06:44:04 PM
Hello,

I am looking for a new logging software.  The current one I am using just doesn't do it for me, and the new update is almost as much as the original software.  I was really most interested in the two loggers EasyLog 5 and LOGic 8, but I could'nt really tell the major differences between the two.  Would someone with more experience please help me?  Feel free to recommend other loggers as well.  Thank you very much for the help!

73 de KC2LYQ Mike


Title: Logging Software
Post by: KE4DRN on April 21, 2007, 06:55:47 PM
hi mike,

http://www.n3fjp.com/

nice software at great price.

73 james


Title: Logging Software
Post by: VE3VID on April 21, 2007, 11:47:26 PM
I'm with James, N3FJP has some nice software at great prices.  Download & test from their website.  I use their event software, then import to DXbase which is the main software.  DXbase is expensive ($100us), but it truly does it all.  73 & cheers!!!  David


Title: Logging Software
Post by: VA1CQ on April 22, 2007, 01:51:56 PM
For general operation, you owe it to yourself to first check Logger32. The program supports transmitting keyboard CW. It also supports most digital modes using your computer soundcard. It has packetcluster operation. And it logs contacts too. This is freeware so you won't find a better deal:
http://www.logger32.net/

Murray
VE7HA
7J1AQH


Title: Logging Software
Post by: AA6YQ on April 22, 2007, 10:09:47 PM
The DXLab Suite is free. Besides the usual logging, transceiver control, DX spot collection and digital mode features you'll find in most applications, DXLab

- provides operations that can alter many logged QSOs simultaneously without requiring the user to modify ADIF files -- e.g. performing callbook lookups on already-logged QSOs, or adjusting the start times of QSOs logged during a specific time range, or extracting QTH information from COMMENT fields, or...

- synchronizes with LotW and eQSL.cc, initiating upload and download operations with a single mouse click without requiring the user to manually invoke TQSL

- directly prints QSL labels and 4-to-a-page QSL cards

- directly prints addresses on envelopes or labels

- tracks confirmation and verification of QSOs for DXCC and TopList awards, highlighting needed DX spots, automatically generating outgoing QSLs that request confirmation of needed QSLs, identifying confirmed QSOs for submission to the ARRL DXCC desk, and generating DXCC submission paperwork

- reports progress towards DXCC, TopList, Challenge VUCC, Marathon, WAS, WAC, IOTA, WAZ, WPX, and county awards

- extracts address information from all 3 CDROM callbooks and QRZ.com

- provides one-click access to more than 100 web-accessible sources of QSL information

- displays frequency-dependent settings for devices like tuners and amplifiers

- provides both map-driven and callsign-driven operation of all known PC-controllable rotators

- captures DX spots from up to 6 sources (telnet clusters, packetclusters, DX Summit), creating and maintaining a local database with one entry for each active DX station that is color coded by "need" and LotW participation, and whose entries can be independently filtered and displayed in a table, on its world map, and on a zoomable bandspread

- extracts QSX frequencies from DX spot notes, enabling accurate transceiver setup for split frequency operation with one user action

- captures solar and geomagnetic data from WWV spots and uses this data to display easy-to-understand QST-style graphical propagation forecasts, and to depict the auroral oval on its world map

- monitors user-specified NCDXF/IARU HF beacon schedules to rapidly calibrate propagation forecasts with actual propagation

- decodes all PSK31 or PSK63 QSOs within your transceiver's bandpass and extract callsigns to create and maintain a "stations heard" window

- simultaneously runs soundcard RTTY (using the MMTTY engine) and an external modem (e.g. a KAM or PK232) to provide diversity decoding or the ability to simultaneously decode a DX station and callers

- supports PSK, RTTY, CW (generation only), and Phone (voice keying) with a single user interface and macro facility

- interoperates with with MultiPSK, MMSSTV, MMVARI, MMTTY, MixW, and DX Atlas

- is updated frequently, and downloads/installs upgrades with a single mouse click

- is driven by an active and friendly user community open to everyone

The DXLab Suite is available via http://www.dxlabsuite.com/

   73,

       Dave, AA6YQ


Title: Logging Software
Post by: W5GA on April 24, 2007, 10:02:51 AM
There are several large differences that I see between Easylog and Logic.  Easylog will interface to two radios, Logic will do 8.  Logic will also interface to band decoders.  Logic does up to 4 rotors, Easylog 2.  Probably the largest difference is in the searching and reporting capability.  Logic will search and report on ANY field (even user defined), and give you the results on PAPER.  I don't know about you, but I hate looking at that sort of thing on screen.  I've been using Logic since '92 (ver. 2)but periodically look at all the others I can find just to see if there is anything I just have to have.  So far, I haven't found anything that is nearly as flexible as Logic.  And that includes DX Lab, although DX Lab comes closer than anybody else has to date.

Logics shortcomings:
the contesting side shows that it really isn't made for it.  It'll do in a pinch, but lacks a couple necessary features to make it shine.  For this I use N3FJP.

High initial cost

Where Logic really shines:

searching and reporting.  Any of the canned reports (lots of them included) are user customizable.
QSL and label printing, same comment as above.
support, Dennis WN4AZY is just a phone call away and is always happy to help.
If you are familiar Xbase commands, you can really make it sit up and dance.  It has a command screen built in.  Conversely, if you don't know what you are doing you can really screw your log up!(voice of experience)  BACKUPS!!!!

Another plus - This has been on the market a LONG time.  I don't think you'll see it go away anytime soon.

Good luck!

Doug



Title: Logging Software
Post by: K1GMG on April 24, 2007, 10:28:03 AM
I use Ham Radio Deluxe and it's free.
http://hrd.ham-radio.ch
It's easy to use and easy to edit entries if you make a mistake.
Does more just logging.  Also does not require downloading a call sign database like other logging software, pulls call sign info from qrz.com


Title: Logging Software
Post by: AA6YQ on April 24, 2007, 10:59:37 AM
DXKeeper, the DXLab's Suite's logging component, will search and report on any field and, if desired, print the resulting report on paper. Access to the log using Structured Query Language (SQL) is available; a log can also be directly loaded into Microsoft Excel for data analysis, charting, etc.

   73,

       Dave, AA6YQ


Title: Logging Software
Post by: N8UZE on April 28, 2007, 10:45:00 AM
First you really need to define what you feel is lacking in your current software.  Is it too cumbersome to use?  What features do you like that you want to be sure the next software has?  What features do you feel it is lacking?  And so on.  Until you do that, it will be very difficult for others to recommend something and very difficult for you to make a choice.


Title: Logging Software
Post by: N8UZE on April 28, 2007, 10:45:26 AM
First you really need to define what you feel is lacking in your current software.  Is it too cumbersome to use?  What features do you like that you want to be sure the next software has?  What features do you feel it is lacking?  And so on.  Until you do that, it will be very difficult for others to recommend something and very difficult for you to make a choice.


Title: Logging Software
Post by: GM4AHW on May 07, 2007, 04:36:32 PM
Right on! Define your requirement, then - what? How the hell do you find out what programs actually deliver what you want? My guess? They won't.

Here's why. Computers really deliver everything. Hams are really into everything. So they try to deliver it via software. So the programs very quickly get totally over-bloated (like Word - you know what I mean).

Yes, I know about DXLab, and its granular structure, but actually, like all of these "super logger" programs,it doesn't deliver when it comes to the basics. Like for example, I contact a buddy on 80, and log his start time. Then another buddy crashes in, so I try to log him too, without closing the previous QSO. I have yet to see a PC package which allows that, without going back into the QSO entry and editing the stop time of the first QSO. PLEASE, if you know of one, let me know.

What I want (and again PLEASE, if you know of a program which does this well, tell me!) is control over the end time of each QSO. I envisage multiple QSO-entry panes all active (or preferably one which can switch between currently un-closed QSOs) into which I can command the end time of that particular QSO, rather than having the software decide that if a new QSO is started, then the old one must have stopped. ~Is that too much to ask?

And I absolutely DON'T want a package that handles QSOs in nets by deciding on a start or end time based on the start time of a previous QSO - that sucks. I want control.

And another thing. I log my test transmissions. Comes from an earlier era in the UK when ALL transmissions were logged, irrespective of whether or not they involved other people. I see no way of logging this kind of test transmission in the currently available "logger" programs, which all demand the involvement of a QSO. That sucks too.

And yet another thing! Sorry about this, but I'm on a roll now. I care not at all for DX contests, or any other contest for that matter. I have a logbook into which I have assiduously entered absolutely every RF emission from my shack since, well, since before you were born, probably. I'd like a computer version of that, with all the expected search and autofill facilities that computers can provide, but without the bells and whistles which go off every time a contest target approaches.

I don't want bloatware which will warn me that a particular DX location is the only one missing from my DXCC award - I don't care. I want an automatic, functioning, computer-based logbook. With the accent on LOG.

Too much to ask? Too little to ask? I guess the latter.


Title: Logging Software
Post by: AA6YQ on May 07, 2007, 05:21:59 PM
GM4AHW:

In DXKeeper (the logging component of DXLab),

1. For your "my buddy crashed in" scenario, adjusting the stop-time of the first QSO after you finish takes exactly 3 mouse clicks: 1 to select the previous QSO, and a double-click on the stop-time to update it to "now". This is exactly one mouse-click more than would be required in the solution you propose.

2. You can log a test transmission or any other RF emission by prepending an exclamation mark to a descriptive term you place in the callsign field, e.g. !TESTING or !Antenna_Test or !GridDipOscillator. Such entries provide autofill (e.g. frequency and mode from the transceiver) and are accessible via the standard search mechanisms.

3. Many options are provided to let you tailor the application to your needs. These are preconfigured "out of the box" so that a user can get started without first consulting the documentation, but they are available for anyone interested in performing the optimization.

   73,

       Dave, AA6YQ


Title: Logging Software
Post by: GM4AHW on May 07, 2007, 06:12:10 PM
Dave,

You entirely miss my point. The user interface is not about how many clicks it takes to do something. In a menu system, for example, if each level of the menu holds, say, ten items, then just three clicks of the mouse will allow you to access any one of a thousand items. Which isn't a selling point if you don't know exactly where each of these thousand items is hiding. The point is that no sane developer would have 1000 items lurking within a menu system, but nevertheless, the truth is that three clicks will navigate the complete space.

So counting clicks gets you nowhere.

You need to look at how operators interface to a real logbook, and replicate that interface as much as possible, while also of course providing the added value that computers can offer. So for example, in my "crashing buddy" scenario, I'd like to leave all QSOs open until I decide they are closed (and don't forget those buddies who keep coming pack at ya even though the have said thay are QRT), and then when I decide it's over, I double-click (in your world) the end time entry in the actual log to write the actual current time there, which is closely analogous to writing the end time in a real log. And if my buddy comes back at me after that, I can always do it again.

The point is that I shouldn't need to "call up" the QSO at all - it is still active, remember -  and I should be able to directly and rapidly manipulate individual fields IN THE LOG. And when I say "in the log" I don't mean in a popup window containing all sorts of irrelevant data which I have to scan through to find the one datum I want to modify - I have already clicked in the log book  on the field I want to change.


Title: Logging Software
Post by: AA6YQ on May 07, 2007, 06:37:55 PM
GM4AHW wrote:

"You entirely miss my point. The user interface is not about how many clicks it takes to do something. In a menu system, for example, if each level of the menu holds, say, ten items, then just three clicks of the mouse will allow you to access any one of a thousand items. Which isn't a selling point if you don't know exactly where each of these thousand items is hiding. The point is that no sane developer would have 1000 items lurking within a menu system, but nevertheless, the truth is that three clicks will navigate the complete space. So counting clicks gets you nowhere."

AA6YQ response:

There are no menus in any DXLab application. In the scenario you described, DXKeeper would present you with a table whose entries show you the data from your most recent QSOs. Clicking on one of these entries lets you modify that QSO's data; specifically, you could then double-click your first  QSO's end-time to update it to "now".

GM4AHW wrote:

"You need to look at how operators interface to a real logbook, and replicate that interface as much as possible, while also of course providing the added value that computers can offer. So for example, in my "crashing buddy" scenario, I'd like to leave all QSOs open until I decide they are closed (and don't forget those buddies who keep coming pack at ya even though the have said thay are QRT), and then when I decide it's over, I double-click (in your world) the end time entry in the actual log to write the actual current time there, which is closely analogous to writing the end time in a real log. And if my buddy comes back at me after that, I can always do it again."


AA6YQ response:

Replicating a pen-and-paper interface is no guarantee of ease-of-use. Should I artificialluy limit the number of QSOs simultaneously visible to the 25 or so shown on a typical paper logbook page?

In your "crashing buddy" scenario, the only thing DXKeeper does differently than you would wish is to set the stop-time of one QSO when you start the next one. You can easily update these stop-times when the group QSO actually finishes, just as you desire.


GM4AHW wrote:

"The point is that I shouldn't need to "call up" the QSO at all - it is still active, remember -  and I should be able to directly and rapidly manipulate individual fields IN THE LOG. And when I say "in the log" I don't mean in a popup window containing all sorts of irrelevant data which I have to scan through to find the one datum I want to modify - I have already clicked in the log book  on the field I want to change."

AA6YQ responded:

A list of your most recent QSOs -- including the ones you consider currently active -- is not "all sorts of irrelevant data". Have you actually tried using DXKeeper in this scenario?

   73,

       Dave, AA6YQ


Title: Logging Software
Post by: GM4AHW on May 07, 2007, 07:06:46 PM
Dave,

I really didn't intend to use this forum as a battleground, but I still feel you have missed my point.

I didn't say there were menus in DXLab. You were using a click count as an indicator of ease of use, and I was saying it ain't so.

I didn't say that you need to limit the number of visible QSOs to that shown on a traditional log page. Just the active ones will do, ie. those that I haven't closed with an end time.

Your definition of "easily update these stop times" is at the centre of my argument. I just disagree that a system which calls up a popup which contains data I don't want to update is not as user-friendly as clicking on the actual datum that I DO want to update. You have to agree that the popup necessarily contains data that I am not actually interested in at that point, ie. the point at which I want to close the QSO, even though the data contained therein may be of great interest to me at another time.

But I realise we won't see eye to eye on this. If you are the developer of this system, good work. It's just not intuitive enough for me, but don't get in a flap about that, there are plenty of other non-intuitive programs out there, and at least DXLab has the kudos of being one of the best.


Title: Logging Software
Post by: AA6YQ on May 07, 2007, 07:22:23 PM
GM4AHW wrote

"Your definition of "easily update these stop times" is at the centre of my argument. I just disagree that a system which calls up a popup which contains data I don't want to update is not as user-friendly as clicking on the actual datum that I DO want to update. You have to agree that the popup necessarily contains data that I am not actually interested in at that point, ie. the point at which I want to close the QSO, even though the data contained therein may be of great interest to me at another time."

AA6YQ response

DXKeeper does not display a popup, much less a popup containing data you don't want to update. Rather than repeat my description of how it works, I encourage you to download DXKeeper and give it a try; its entirely free. If you then have concrete suggestions for improvement, join us at

http://groups.yahoo.com/group/dxlab

   73,

       Dave, AA6YQ


Title: Logging Software
Post by: GM4AHW on May 07, 2007, 07:53:10 PM
Dave,

Yes, I have downloaded and installed DXKeeper, and I tried it for some time before posting. Please note that I'm not targetting DXKeeper here: I simply mentioned it in my original post as an example of software which is modular, as a way of counteracting the bloatware tendency of this type of software.

However, I take issue with your last post. You said:

"DXKeeper does not display a popup, much less a popup containing data you don't want to update."

and that's quite misleading. You don't have a popup, but you DO have a panel containing all the data I referred to, one of which is end time. This panel is populated when the required line in the log is clicked on. There is simply no functional difference here between that and a popup. And if you think there is, then there is nothing more I can contribute to this thread. I have said all I want to, and I will not repeat myself.


Title: Logging Software
Post by: AA6YQ on May 07, 2007, 09:54:10 PM
GM4AHW wrote:

"You don't have a popup, but you DO have a panel containing all the data I referred to, one of which is end time. This panel is populated when the required line in the log is clicked on. There is simply no functional difference here between that and a popup. And if you think there is, then there is nothing more I can contribute to this thread. I have said all I want to, and I will not repeat myself."

AA6YQ response:

A static set of panels whose contents display the details of the currently-selected QSO is not a pop-up. All it has in common with a pop-up is that it displays information -- which can be said of most any two user interface mechanisms.

Since you're familiar with DXKeeper, let's review your "burst in" scenario step-by-step:

1. You're working W1ABC, and have created a new entry in DXKeeper to capture the information from this QSO. The information you capture is shown in a set of detail panels, each of which collects related information -- QSL information, Award information, Contest information, etc. You've previously configured DXKeeper to display only those panels whose information you care about. Below these panels, DXKeeper displays a list of your most recent QSOs, with your current QSO with W1ABC shown as "selected".

2. W2DEF bursts in. You click DXKeeper's New button, which creates a new entry to capture W2DEF's information; the frequency, mode, and start-time are automatically captured and displayed in the detail panels. Below the detail panels, a new entry for your QSO with W2DEF appears on the "recent QSOs" list and is designated as "selected"; the entry for your QSO with W1ABC is right above it.

3. While working both stations, you can quickly display, modify, or add information in the W1ABC and W2DEF entries; you need only click on the appropriate entry in the "recent QSOs" list to select it, and then view, modify, or add information in the detail panels.

4. Your three-way QSO with W1ABC and W2DEF ends. You click DXKeeper's Log button, which automatically captures the end-time for the W2DEF QSO. You then click on the W1ABC entry in the "recent QSOs" list to select it, causing the detail panels to display the information for that QSO; you double-click on the end-time, thereby updating it to reflect the actual end time with W1ABC, and click the Log button.

With the above as context, please help me understand how you'd like DXKeeper to better support this scenario. Thanks...

This sort of interaction occurs 5 to 10 times each week on

http://groups.yahoo.com/group/dxlab

Sometimes, the application in question already provides a way to do what the user wants. Sometimes, I create a new release that provides the desired functionality. Sometimes, I decline to provide the requested functionality because its out-of-scope (e.g. real-time contest scoring) or would add user-perceived complexity not justified by its value.

    73,

        Dave, AA6YQ


Title: Logging Software
Post by: GM4AHW on May 08, 2007, 09:21:07 AM
Dave,

Since you said "With the above as context, please help me understand how you'd like DXKeeper to better support this scenario", I'll try to convince you that what you have is functionally no different from a popup:

1. The data area is remote from the area which calls it up, just like a popup;

2. The input focus needs to be changed from the area which calls up the data to the area which holds the data, just like a popup;

3. The data in the data area changes when a different item in selected, just like ... well, you get the idea.

If the methods of access to your data area are different from those of a popup, I'd be keen to hear what these differences are.

But actually, I don't care if you call it a popup, or a panel, or a frizbee: it's the method of use which I don't like. I want to modify the data IN THE LOG, not in a separate area which becomes available once I have clicked on the log entry.

Your software needs two changes before this will be possible (and please, I'm not asking you to make these changes):

1. Don't close a QSO just because another one has started;

2. Allow me to double-click the end time entry IN THE LOG to close the contact.

And if you extend that principle, that would mean that when I click NEW, the cursor would sit in the callsign column of a new log entry, with tabs passing input to the right. As you have said, I will have already configured the log to just display those data that I want; if I need to modify data not displayed, then I'm sure I will have access to a frizbee to do that, but for routine operations like starting and closing a contact, I want it right there, in the log, as above.

And harking back to an earlier comment, I certainly don't want to have to fudge an entry by using exclamation marks to try to convince the software that this log entry isn't a QSO. So if I type "Test", or anything else not recognised as a callsign in the call column, I don't expect the software to be sick all over the carpet. :-0)


Title: Logging Software
Post by: AA6YQ on May 08, 2007, 11:06:52 PM
GM4AHW wrote:

"...I'll try to convince you that what you have is functionally no different from a popup:

1. The data area is remote from the area which calls it up, just like a popup;

2. The input focus needs to be changed from the area which calls up the data to the area which holds the data, just like a popup;

3. The data in the data area changes when a different item in selected, just like ... well, you get the idea.

If the methods of access to your data area are different from those of a popup, I'd be keen to hear what these differences are."

AA6YQ response:

The distinguishing characteristic of a popup is that it has two states: invisible, and visible; the transition between these two states is what gives a popup its name. None of the panels that DXKeeper uses to display the details of the selected QSO ever "pop up" -- they are always visible. Yes, they display information. Yes, a popup displays information too. But declaring DXKeeper's detail panels to be a popup on that basis would be like saying "a jet plane is the same as a bicycle because they both have rubber wheels". Your logic is simply erroneous.

GM4AHW wrote:

"But actually, I don't care if you call it a popup, or a panel, or a frizbee..."

AA6YQ reponse:

Then why are you devoting so much energy to advocating a position that is so clearly incorrect?

GM4AHW wrote:

"...it's the method of use which I don't like. I want to modify the data IN THE LOG, not in a separate area which becomes available once I have clicked on the log entry.

AA6YQ response:

It would be trivial to implement this; all that would be required would be changing the "allow updates" property value on the grid control from "no" to "yes". However, experience shows this will result in a lot more unintentional mutations of logged QSOs when a user inadvertently types a character with the cursor focus in the list of QSOs. DXKeeper requires users to make the one additional mouse click needed to select a QSO so that its contents become editable in the detail panels -- a good tradeoff, in my view. If this one mouse click is more than you can bear, so be it; choose a logging application that lets you directly edit within the QSO list.

GM4AHW wrote:

Your software needs two changes before this will be possible (and please, I'm not asking you to make these changes):

1. Don't close a QSO just because another one has started;

AA6YQ response:

Requiring users to manually set a QSO's end time when its saved so another can be started would be suboptimal for the vast majority of DXKeeper users. The only way I'd do this would be to provide an option to disable the current automation.

GM4AHW wrote:

"2. Allow me to double-click the end time entry IN THE LOG to close the contact.

And if you extend that principle, that would mean that when I click NEW, the cursor would sit in the callsign column of a new log entry, with tabs passing input to the right. As you have said, I will have already configured the log to just display those data that I want; if I need to modify data not displayed, then I'm sure I will have access to a frizbee to do that, but for routine operations like starting and closing a contact, I want it right there, in the log, as above."

AA6YQ response:

I understand what you want, but think its a bad idea as explained above.

GM4AHW wrote:

And harking back to an earlier comment, I certainly don't want to have to fudge an entry by using exclamation marks to try to convince the software that this log entry isn't a QSO. So if I type "Test", or anything else not recognised as a callsign in the call column, I don't expect the software to be sick all over the carpet. :-0)

AA6YQ response:

DXKeeper won't "be sick all over the carpet" if you log a QSO whose callsign is TEST -- it will conclude that you worked a station in Costa Rica and update your award progress accordingly. If you don't care about award progress, then by all means log the QSO with a callsign of TEST. But for those users who do chase awards, its important to distinguish between a bona fide QSO with a station in Costa Rica and a test transmission; for such users, the ability to log a QSO whose callsign is !TEST is quite useful.

   73,

        Dave, AA6YQ


Title: Logging Software
Post by: N8UZE on May 09, 2007, 05:35:48 AM
To: GM4AHW

It sounds to me like your needs could best be met with a plain old Excel spreadsheet.  Since you are not interested in awards, etc. but just a plain old duplicate of a paper log, this will do exactly what you want.  You can click on any cell and change it.  You can leave any cell blank (e.g. end time) until you are ready to enter a value.


Title: Logging Software
Post by: GM4AHW on May 09, 2007, 06:56:45 AM
N8UZE said "It sounds to me like your needs could best be met with a plain old Excel spreadsheet."

No. I've worked with and developed all kinds of software both recreationally and professionally over the past 30 years, and if I thought that a spreadsheet woud do what I wanted, I would not have got involved in this thread. For example one thing on my wish list is autocompletion from previous entries - and I don't mean QRZ lookup, I mean from my own log. Yes, I know, there are loggers which do that, but they come with their own baggage.

And I'd rather not have to write my own application if something suitable already exists. I'm testing lots at the moment, in the hope that I'll find the right one. They all have very similar functionaslity, but in many cases the user interface is counter-intuitive (read "sucks").

AA6YQ, I give up. You just don't get it.


Title: Logging Software
Post by: N8UZE on May 09, 2007, 08:30:15 AM
I think that you will find that NONE of the available products simply let you click on and change the single bit of data that you want in the log display.  All of them will bring up a panel, popup, or something like that, which will show you all the QSO data and then allow you to change whatever you want to there.


Title: Logging Software
Post by: GM4AHW on May 09, 2007, 01:16:33 PM
N8UZE said "I think that you will find that NONE of the available products simply let you click on and change the single bit of data that you want in the log display. All of them will bring up a panel, popup, or something like that, which will show you all the QSO data and then allow you to change whatever you want to there."

Actually, Logger32 does. Every single field is directly editable, right there in the log entry. I obviously haven't checked ALL loggers, but I guess there will be others like that.

But for some reason, Logger32 also insists on closing the contact as soon as the contact is logged, and then I have to edit the end time if I'm in a net. Bizarrely, it allows you to specify that the start time occurs when the contact is logged too, so that both start and end are the same time.

So I'm still looking.


Title: Logging Software
Post by: K8ELR on May 16, 2007, 06:07:24 PM
Hi,

I use Ham Radio Deluxe for everyday logging. During our lsst QSO party I used n3fjp. I think that was a very good way to log the entries for the QSO party and other contests. I like HRD for the control of my rig and the features of that program. The best thing about HRD is it's free.
I'll probably get quite a bit of experience with n1mm. Thats the software my club has decided to use to log field day contacts. We plan on using it networked over a wireless lan.


73!
Jim  K8ELR


Title: Logging Software
Post by: N8UZE on May 17, 2007, 10:31:47 AM
N1MM is primarily intended for contest logging rather than general logging. As a result, it doesn't have award tracking features, etc as far as I know.  After a contest, one typically exports the data in adif format for importation into a general logging program.


Title: Logging Software
Post by: W8JWA on June 03, 2007, 07:48:33 AM
Yes,I agree,I've been using this software for a few years now and it's easy to understand and use,you can't go wrong with this software.


Title: Logging Software
Post by: K4FX on August 09, 2007, 06:37:49 AM
I have used every one mentioned here plus several not mentioned,

Winlog32 is the hands down best for general logging, 100% freeware, tracks all awards, the most user friendly, you can tell any stat in about 2 mouse clicks, great program.

N1MM is the best hands down for contesting. Nothing else comes close 100% free.

I am NOT basing my choices on these 2 being free, it just turned out that way, it seems the ones I paid for were the lamest of the bunch, go figure.....

Try them. You won't regret it. The 2nd best general logger is Logger 32, but it doesn't gather solar data from the cluster like Winlog, so I prefer G0CUZ's Winlog 32. It has the best Winkey interface I have ever used, including K1EL's apps! Great support from Colin too!

Good luck

K4FX

 


Title: Logging Software
Post by: G4TUG on December 02, 2007, 03:48:58 AM
Unable to find exactly that which I wanted, a friend and I developed a simple Access database that could be used in the same way as a paper log but could also rapidly show almost any statistics required. It has been in constant use for about six years without any hiccups.
To try it click on the link below:
http://www.zone5.plus.com/g4tug/rodlog.htm

73
Rod


Title: Logging Software
Post by: WA9YSD on December 14, 2007, 04:03:34 AM
I noticed that when I ran my list for DXCC submission, for the same country I have only 2 confirmations by two different call signs. One was from LOTW and the other was CARD confirmations. For some reason one time I run the list one call shows up. The other time I run it the other call shows up.

When I go to Output-Awards-DXCC In the Select Records From I have QSO Log ticked and Both Ticked.

Am I doing something wrong?
What can I do to keep this from happening?
Any one else experience this?


Title: Logging Software
Post by: WA9YSD on December 14, 2007, 04:05:01 AM
I am using DXBase 2007.

I noticed that when I ran my list for DXCC submission, I noticed that for the came country I have only 2 confirmations by two different call signs. One was from LOTW and the other was CARD confirmations. For some reason one time I run the list one call shows up. The other time I run it other call shows up.

When I go to Output-Awards-DXCC In the Select Records From I have QSO Log ticked and Both Ticked.

Am I doing something wrong?
What can I do to keep this from happening?
Any one else experience this?