Download
1 / 56
560 likes | 584 Views
The eQSL system is a competitor of the ARRL’s Logbook of the World. It is not as secure from a cheating perspective, as it is not a double-blind system of contact confirmation like LoTW. This has both disadvantages and advantages.
E N D
The eQSL system is a competitor of the ARRL’s Logbook of the World. It is not as secure from a cheating perspective, as it is not a double-blind system of contact confirmation like LoTW. This has both disadvantages and advantages. eQSL does use a very secure system, similar to that used by LoTW to verify its user’s identities. And beside simple contact verification the eQSL system allows what LoTW does not, the exchange of QSL card style pictures between hams to commemorate contacts made.
So lets do this backwards…. Let me do the “and were to find them” part first. www.eqsl.cc
If you click on a “Display” button you will see the eQSL card as per the example here. Note the Authenticity icon below the eQSL. It indicates that the maker has been authenticated, not the QSO itself.
This is the actual eQSL which can be downloaded, printed, and combined to produce shack artwork, screen backgrounds, and other displays. The card itself is 528x336 pixels, and the grayed in area at the bottom containing the QSO information is roughly 528x75 pixels. If you create your own card it is best to remember those dimension and plan accordingly. The background on this card is essentially ‘stock’ photography from eQSL, and thus will appear on dozens if not hundreds of nearly identical eQSL cards.
Rather than use stock photography, some hams prefer to use none at all. Here is an example of a very simple eQSL. Below are several more using various print styles and background colors.
But I believe most hams would prefer to have a unique eQSL of their own design. To enable you to use a unique uploaded design in .jpg or .png format will require a ‘Bronze’ membership in eQSL, which requires a minimum donation of $5 per year. FYI: The eQSL is designed to print at 3.5” x 5.5” (90mm x 140mm). This card is mine. It was made to resemble my paper QSL card using a combination of Paint Shop Pro, Photoshop and other graphics software.
If there is sufficient interest I will gladly host an eQSL hands-on workshop in the clubhouse later this month. I will bring my laptop equipped with Paint Shop Pro and Photoshop software. What I will need from you is some photography or graphics on thumb drive, and your good ideas. Please let me know ASAP if you are interested and which day or days would be best for you.
A Little History At Field Day 2015 I took over ‘networking’ from Steve Kelly who resigned, when he took on a Laurel VEC Team Leader position. It was our first year using HSMM MESH for that event, and I basically re-installed N3FJP on all computers to be used. That August I showed up to help operate the Maryland QSO Party and quickly discovered we could not locate any computer with the proper software installed. So ‘last minute’ I installed N3FJP for that event. Then this past year, renovations were started on the clubhouse ham shack, and I volunteered to help Jim Wallace with the computer logging for that location.
What Do We Need? The AARC needs a comprehensive logging plan, to include a combination of hardware and software to allow for multi-station operation in a variety of situations. This logging plan should be a simple to setup and maintain as possible, with special attention paid to network failure issues. This logging plan should be known to the membership so that essentially everyone can use it.
Point 1 – Hardware/Software Almost all modern rigs come with digital control capability. They have a serial port, USB or proprietary connection on the back. This is then connected to a computer using the appropriate cable, typically with a USB connection on the other end. This cable allows information on things like, band, frequency, and mode to flow to the logging computer, and allows the computer to control certain functions of the rig, dependent on the software used and rig’s capabilities.
Point 2 – Simple/Avoid Failure The logging system should be such that the average understands it. If the system is overly complex, then we severely limit the number of persons who can fix problems when they arise. We need to design our system to avoid failure. This sounds simple but it is not. As an example N3FJP’s software is designed to ‘forget’ the location of it’s master log file if N3FJP is re-started and the path to that log is not fully operational. This has caused the any number of re-configurings over the past 2 years.
Point 3 – Known to Membership Logging software needs to be ‘obvious’. By that I mean that once it’s started, the program should make basic logging as simple as possible. The average operator shouldn’t need a course to run the program. That being said, we need to train club members on the operation of non-contest logging software on a regular basis. Plus we need to hold training sessions prior to every contest event, on the use of the specific logging software to be used at that event.
Defining the Problem There are basically two types of logging programs, one is designed for daily use, the other designed for contest use. We need one of each, compatible in the sense that logs created by the contest software can be imported into the daily use software, following a contest, using the ADIF format. This allows the daily use software to handle things like award tracking, QSL cards, LoTW confirmations, and eQSLs as well as provide a permanent record of all contacts made by W3VPR. Meanwhile the contest software helps us compete more effectively by speeding operation.
Requirements For Both Software Types • Must provide multiple logging PC’s with access to a single logging database. • Must network easily while minimizing disconnection issues and configuration times. • Must be connectable to modern transceivers to provide auto-logging of things like band, mode and frequency. • Must provide connection to full featured PSK31 software and enable direct logging of PSK31 contacts. • Should also provide extra operational functionality, connection to DX spotting information, and connection to operator directories. • Must be ADIF compatible.
Daily Use Logging Software Requirements • Must link to LoTW with minimal effort. • Must link to eQSL with minimal effort. • Must be as full featured as possible. • Contest Logging Software Requirements • Must be quick and easy to learn and use. • Must be easily configurable. • Must be as reliable as possible.
The Contenders • Contest Logging Software • N3FJP (Paid for/suite of programs/one for each contest) • N1MM (Free/single program/configurable by contest) • Daily Use Logging Software • Ham Radio Deluxe (Free & Paid) • Log4OM (Free) • N3FJP Amateur Contact Log (Paid for) • DX Lab (Free) • Winlog32 (Free)
Contest Logging – N3FJP N3FJP is a group of programs, one for each contest. This means that if a logging computer is outfitted for 10 contests, it must have 10 programs installed, and each is configured separately. If a rig connection is enabled, then each program must be configured for connection port, baud rate, stop bits and such. Each program must also be configured to locate the ‘master logbook’ for the contest on a network ‘shared folder’, and this location data is erased any time a re-connection is attempted while the network path to that ‘shared folder’ is not accessible. Erased information must then be re-entered before the logging computer can be used.
Contest Logging – N3FJP This means if we have 10 computers needed for 10 contests we have 100 installations to accomplish, followed by 100 sets of configurations to enter. For internal clubhouse use, if the user does not ensure that the computer hosting the master log is up and running prior to starting the logging computer software, a reprogram will be necessary prior to operation. This also means that any power losses or disconnect during any contest could result in one or more logging computers being disabled until someone is able to re-enter the proper data path.
Contest Logging – N3FJP In 2015 we lost connection to the database just prior to our Field Day start time, resulting in reprogramming of all logging computers prior to operation. An intermittent Ethernet cable caused us to reprogram one computer at least a half dozen times before we were able to diagnose the problem. We did another system reprogram when changes were made to MESH unit settings. In 2016 we tried to solve the problem by putting UPS units on our master logging computer, and all MESH units, and by making sure all logging computer batteries were in good shape and charged. But it turned out many were defective, and most of our UPS units didn’t work. So we still had some disconnect issues.
Contest Logging – N3FJP There is one major advantage of using N3FJP that should also be mentioned. For PSK31 operation Chuck Tanner’s software of choice is DM-780, a part of the Ham Radio Deluxe suite of software. Chuck is able to log his PSK31 contacts using DM-780 and its direct connection to the HRD Logbook program. He then uses a Utility Gateway program to transfer this data in real time from HRD to the N3FJP software. This system is not available on N1MM software. However N1MM does have a similar direct connection from FLDigi, a free, relatively full featured program for PSK31 operation.
Contest Logging – N1MM This is the entry window for the N1MM program. It is a single program that can be used for a variety of contests, some of which can be programmed by a single mouse click. It has a series of windows that can be opened to display things like a score summary, the position of the gray line, telnet spotting data, dupesheet, general log, multipliers, network status and even a chat window to other logging computers involved in the same contest. As you can see it also has buttons for sending macros, both CW and SSB.
Contest Logging – N1MM This window provides color indications for new multipliers of various sorts, and even a color for dupes. It has separate modes for ‘running a frequency’ and ‘search and pounce’ operation. N1MM can also supply spotting data by frequency, and remove callsigns from that display as the stations are worked. If the full interface is connected, just clicking on the callsign will set your rig on frequency ready to work the station. The program also interfaces directly with Morse sending and decoding software.
Contest Logging – N1MM N1MM has a unique networking feature. As long as multiple copies of identical versions of N1MM are on the same network subnet, they can be set to network by simply opening the networking window and clicking to turn on networking. When networking, the logging computer holding the master log should be started normally, while the others are to be started “as administrator”. This will allow the master logging computer to provide time sync and other features for the entire network, to include spotting data.
Contest Logging – N1MM Further you can network N1MM in real time with stations not on the same subnet by supplying the name of the computer, and correct IP address. This includes stations connected over the Internet, provided the IP address does not change at either end of the connection during the contest. The ‘dark side’ of all this is that HSMM MESH requires separate subnets. Thus each computer would need its data programmed into each of the other network computers, and no computer could be relocated without reconfiguration.
So the choice is… Do we stay with N3FJP, knowing we must: Investing in UPS units and batteries to keep it stable. Commit to doing a massive number of installations and configurations. Realize that disconnects and loss of location for the master log are impossible to prevent totally Begin training as many club members as possible in how to reconnect to the master database. • Do we convert to N1MM, knowing we must: • Learn a new system. • Likely convert our PSK31 operation to FLDigi from DM-780 • Likely have to abandon HSMM MESH in favor of WiFi or wired connections to allow all station to be on the same subnet.
In either case we must…. Invest in the cables and time required to configure rigs to their respective logging computers. Keep good records of which computer is configured for use with which rig. This is doubly true with N3FJP as the configurations must be done for multiple programs.
Daily Use Logging – HRD Free Ham Radio Deluxe comes in two versions, ‘last free’ and latest. It was once a freeware suite of programs, and ‘last free’ is the final free version before new owners took over. Both versions are very full featured, and both allow for multiple operating positions to log to a single master log file. The best way to accomplish this is to convert the database used by HRD from MSAccess to MySQL. This simplifies configuration for use by multiple computers, and also speeds operation. So it’s a win-win.
Daily Use Logging – HRD Free Ham Radio Deluxe is the ‘logging system of choice’ for many members of this club. It has all the features we need with respect to logging, data transfer, LoTW and eQSL. HRD is a suite of programs including rig control in the main module, HRD Logbook, and DM-780 which is a full featured program for digital modes including RTTY, PSK31 and a host of others. HRD is capable of ‘rotor’ control when used with the right hardware and would be a real plus for our shack. We already have a number of operators skilled in it’s use.
Daily Use Logging – HRD Free The only down side of using HRD is the cost. A single purchase (just under $100) allows us to outfit all W3VPR computers with HRD. This fee includes use of the program for the life of the radio club, plus all program updates issued during the first year including all ‘fixes’ for product defects. The club would also receives one year of technical support, plus free ‘enhancement’ updates to the product for a year. Beyond 12 months they sell renewals, which include both software maintenance and support. Renewals cost $49.95 per year, and at that rate we could buy new every 2 years.
Daily Use Logging – Log4OM Log4OM is a free, and uses a SQLite database, but can easily be upgraded to MySQL. The upgrade allows multiple versions to access one db. The software integrates with eQSL, LoTW, HamQTH, QRZ.com, Club Log and HRDlog for upload and download. The program allows rigs to be controlled using Hamlib or OmniRig. It even integrates with SDR Radio Consul. It further integrates with DM-780 and FLDigi for digital mode contacts. Plus it has a special screen for ‘net’ operation. It’s major selling point is that it is free, its biggest drawback is that it will take some time to learn.
Daily Use Logging – N3FJP A.C.L. The Amateur Contact Log is a part of the N3FJP suite of programs. This program is not as full featured as HRD, but it is paid for and the AARC owns it. It does have a method of networking the shacks computers so that disconnects will not longer be an issue. This system likely may not work over HSMM MESH due to connection speeds, but again should be fine for in shack computers and daily use. Amateur Contact Log interfaces well with most current rigs.
Daily Use Logging – N3FJP A.C.L. The Amateur Contact Log does not store data like address, or city automatically nor does it download same from operator directories like QRZ.com. It keeps track of QSL’s sent and received but not eQSL’s or confirmations via LoTW. This program does interface well using the ADIF format, and connects easily to LoTW, eQSL and even Club Log but for uploads only. It does not keep nearly as wide a variety of information as HRD, or spin your antenna. The W3VPR log is currently stored on Amateur Contact Log.
Daily Use Logging – DX Keeper DX Keeper is a part of the DX Lab suite of programs. Like HRD it is very full featured. It would be an excellent choice except for one major drawback. As best I can tell, there is no way for multiple copies of this software to utilize the same logging database. If there, is it its not specified in their literature. Therefore it appears not to have the singular feature we need the most.
