You are missing the navigation menus and other features of this site because you have Javascript disabled in your browser. Please enable it.

Pending requests of modifications

These are some of the requests proposed by the registered users. I consider all of them interesting and I will do my best to include them in the future versions of the VQLog. If you have your own request please send it to VQLog's support (only registered users!)

Click here for requests already implemented

DL1ELY proposals:

I would like to QSL to every QSO on every new band in every new mode, but not to QSOs on the same band and in the same mode. But also seperated by own used QTH. If we worked a station from JO30EM on 2m SSB, he should get a second card if we work him from JO40BP on 2m SSB, or if we work him on 2m in CW from JO30EM. As we are doing 4 bands (the 5th is planned), I would like to send only ONE card, when someone works us in one contest on 2,3,4 bands, like they do on HF.
Is it possible to print more than one QSO with one station on one label? For example, when I work a station in a contest on 3 bands, I would like to send him a 3-line-label with all QSOs on it.

DL6ZBN proposals:

I suggest a different behaviour of the program when jumping to certain fields. For example, when I jump to the "Mode" field, I have to enter all three letters if I want to have SSB there, or I have to select the correct mode with the mouse, or I have to enter the first letter and then scroll with the up/down keys. In order to make it "short and sweet" (hi), would it be possible to automate it in the following way: when entering the first letter, the program automatically fills in the field with one of the possible list items. That is, when you hit the "S" key, the program fills in "SSB", and if you want to override it, you have to type in more letters. So if you type "SST", the program completes it to "SSTV". This would have the advantage that you only have to enter ONE letter for the mode and then go to the next field with the TAB key. This would also avoid the "Wrong mode" (or "Wrong type of propagation") messages when hitting the OK key, because you just cannot enter wrong things there. The same applies to the multi character fields "Type of propagation" and "QSO complete".
You could consider adding the possibility of choosing which data fields appear in the output files of the statistics. Sometimes I need start and end time, but not the comment field. I could think of adding a menu or button for the field selection and saving the selection to an INI-file that you don't have to select it again and again each time you call the function. The same is for the logbook listing.

DH6JL proposals:

How will it be when there is a key for /P ??? by the way it can be the "-" key or any other perhaps when it is programable...
A small contestlog useble for hf/vhf tests (Read note *1 from the author below)

EA3BTD proposals:

Possibility to print QSLs between to given times (not only days). And/or numbers of QSOs.
Possibility to enter QSO in contest-format (59001/ 59001), with automatic counter and then print the list for the organization (NOTE *1 from the author: You can register contest-format reports but VQLog is not intended to be a contest-program...there are already good programs specific for contest-loggin (Tac-Log, TCC...)...my idea is that the contacts entered in these programs can be later integrated (imported) to VQLog, that would be a general Log holding all the contacts.

EA8AJ proposals:

I would like to be able to search for a callsign ending with certain letters (For instance ¿¿8AJ)
I also would like o access all stations in a certain Zone, always with the possibility to filter by band
And also that this consultations could be listed.

GM4JJJ proposals:

It would also be nice if VQLog could look up station details from some of the popular EME station databases like SKD80 and EMEDIR.
I also wish the Map could be kept open along with the Entry panel
Colors for the squares on the maps - Worked/confirmed. Also perhaps show ES and T in different colors.
When a Map is printed out, there is no indication on the printout of what parameters we are printing, except "Map of Worked Squares by GM4JJJ on 2m". What would be nice would be "Worked squares on EME on 2m" or Worked Squares on Tropo". Also a little summary like Total Square worked = xxx and Total Confirmed = xxx.
A warning should be given if the user attempts to close the program. It is annoying if you do this by mistake and have to start it up again with the time it takes to start up...

IT9VDQ proposals:

The Fastlog 3.2/3.3 import option should fill in too the "My Locator" field with the locator in "Station data". In this way all statistics will work properly; i ask this to you becouse 90% of qso's are made from main Locator, and only a little part are from a different place! if for some qso's "My Locator" will be different, i can chang it manually; will be a very "extra work" to manually add the "My locator" for each qso.....

YO4AUL proposals:

To have the possibbility to browse the address book
Possibility to personalize summaries for certain contest so that you can obtain automatically the contest log, calculation of points, summary sheet, etc (Read above note *1 from the author)

DF2ZC proposals:

2. Export. It would be very helpful for me and sure many others if your software also contained an export feature (ASCII, as above). So the data could be used for many other purpose.

PA3BWE proposals:

I had a look into another log program and they had a nice little feature in it : 2D display of worldmap showing the day/night area, continously updating ( Logger program ) View of worldglobe showing the from/to connection by an arrow ( ?? program ) This way y've a more look and feel of the distance instead of a 2D map.

PE1OUC proposals:

Pop-up the dxcc country inmideatly after input of prefix: e.g.if i type EH, the dxcc window say's Spain before i select another field.
Make it possible to Auto-select mode based on the report, e.g. if my report say's 559 the mode is CW, 57 is USB, B5 is ATV etc.this mode should -in my opinion- override the carrying of the mode field.
I find it annoying to swap between DXCC and Dist/Bearing if i put an unknown call in the callsign field. Maybe it is possible to combine this very important fields together.
It is not very common, but on microwave frequencies are sometimes maidenhead locators with 8 figures in use e.g. JO22MD55. If you get this to work (optional?) you created the first logging program who supports this. The reason to use 8 maidenhead locator is that the 6 figure version is not exact enough to make a contact over short distances on microwave bands.

PE1OGF proposals:

Is it possible to make a change in the program when entering Name, Town/Village the program automatically uses Capitals for the first Character ? Also with the Report like R29 or O/RO 59A the program automatically uses capitals like you did when entering a callsign. In this way you don't have to think when to use the ShIfT BuTtOn.. yOU know what I mean..
Entering the US State, Is it possible to enter the US state in the "addition of records to the logbook" filed as field 25 ? Now I have to click Awards and enter the filed. Perhaps it's possible to make 1 or 2 fields which can be selected by the user in the "addition of records to the logbook" filed ?
When Importing a contest log ask for setting Random to all QSO, Normally all Contest QSO are random.

SM5WPW proposals:

Couldnt You make the VQlog to do this "non worked squares" (NWS HI) on all bands /separete) over 30MHz? It's always nice to tell the station that you are working, that his/her square is a new square for me, and its very good to have a list on NWS for all us square hunters. It cant be so much to change in program? :) I think that You can use the code from MWS.

ES1RF proposals:

What about CAT- system?
If more than one QSO with the same station, to print second (or may be also 3-d and 4-th, if label big enough) on the same label. In EQF case, the log must be sorted by call-sign.
Possibility to fix the TAB to "SAT", "MS" or another, so that it doesn't change from one QSO to the other
Possibility to carry the data in the "SAT", "MS", etc. tabs from one QSO to the following

G4IGO proposals:

Could you please look at widening the number of maps, perhaps allow the operator to define his own maps?
Also change the marker from a cross to a colour in the square??

K1UHF proposals:

The only thing It may not do is automatically select all of the QSO's in grids that I need confirmed but I have not sent a QSL to
Have is a rig control / communications feature that gets the frequency from the radio. Don't forget a table to allow for transverter offsets. (I use an Icom IC756 directly on six meters but I also use it on 10 meters with a 2 meter transverter. VQLog would have to "know" that 28 MHz = 144 MHz but 50 = 50)
It would be good if the QSO data had State after Town/Village so that it could be selected by the Tab key. Now it requires taking your hands off of the keyboard and with the mouse selecting Awards then WAS.

VK6XLR proposals:

Include Locator and Town/Village on the Personal Data form.

OH5YW proposals:

When I take i.e Summary of Squares, at the end is best distance row. Can you make it so that it shows best distance with different propagation modes? So I do not have to manually find them...

M0HEN/PC7CW proposals:

Maybe it is possible that you can choose by your self which info you can print or just some more options as fixed labels you can choose out. As pwr and rig.
Now all stickers are printed as “XXX confirms QSO”. Is it possible to arrange something that you have a choice to print ”XXX confirms SWL report”?
Add a new field "My QTH" for /P operations, near "My call" & "My locator"
And also an option to print it on QSL if you wish. Just direct behind my locator
Would it be possible if in the award overview you can see also the band you work the station?
The view will be as follow: Reference – worked – QSL – Date first QSO – Call – Mode – Band
As I send and receive QSL in bulk, do I regular get cards back with an “SK” indication.Is it possible to make on QSL indicators as well “SK” as valid mark?

PE1LWT proposals:

Another feature will be neat..acces to the EME dir, like you have now the access to dl8ebw's list

EI3IO proposals:

I'd also like some QSL filters. For example I'd like to be able to select on a per band basis new countries, new grid squares, even stations not worked before. And for HF QSLing it would be nice to say filter out European stations on 14 MHz etc. It's possible on VHF through the distance filter, calculated from grid squares, however there is no similar facility for HF. I hope these comments are of use. As you may have realised, I'm using the programme for generally 50 MHz and HF and would like to keep a careful record of my DXCC situation. I certainly wouldn't want to QSL for example every USA station worked during a contest on 14 MHz but I'd like to be able to QSL immediately any new states, zones or countries etc.
Include a print routine that will place a list in the print queue. E.g. print QSLs for all unconfirmed grid squares on 50 MHz or all new unconfirmed countries on 14 MHz

DL6LAU proposals:

Allow to enter the old European locators and convert them automatically

GU6AJE proposals:

There is a feature I have used on accounting packages that would be very useful here for changing time and date, and that is to highlight the box (date or time) then use + and - keys to scroll up and down by one day or one minute at a time. This would make entering the data much faster and easier.

OZ2Q proposals:

I do miss a for me very, very important thing. When I spot or hear a prefix on the air or on the cluster, I want to know if I worked that contry (not only the frefix)before, and if is confirmed or not - on any band - not only the band marked in the main window.

G0ISW proposals:

Lastly when a stations locator is inputted can a sepaerate window open up as an option showing a map of the squares?
Can please the Most Wanted Squares selection include by band?
Additionally can more than 1 locator be selected as I have moved house twice, but stayed within IO84 square i.e. IO84PP and IO84OQ.
if for example I have worked a square or county etc. more than once, then pending only displays the callsign of the first contact. Would it be possible to display the details of all the contects for that mssing square that I need a QSL card for? (In Summaries)
Ability to have azimuth automatically entered in field from distance/bearing indication, selectable on/off.
Meteor shower entry to automatically be input if date of MS QSO mode matches known shower, selectable on/off.
Meteor shower max length seconds to be changed to milliseconds as very few of my reflections heard are longer than 500ms often 160ms, 240ms etc.
How about a second tickbox to indicate somehow that I called but did not work the station?
The ability to send a formatted DXspot from VQLOG whether about a qso entered or station heard
The ability to filter certain VHF spots when linked to Live MUF i.e. 144.000-144.350 for example therby avoiding WSJT MS spots etc.
A really simple Windows CE version of VQLOG for PDAs, just the ability to record qsos ideal for portable/mobile operation.
Allow 4 character locators in "My locator"
Would it be possible for the data from a qso entered to automatically be used to calculate the MUF. The utility lets you do this, but that means entering the same data twice, if you see what I mean. it would be really neat to have an automatic MUF calculator as well as the utility.
Ability to show on a map historical QSOs with lines drawn from main station to locators worked in different colours for different modes. (This would be similar to your Dxcluster maps)
Map showing BOTH squares worked and squares confirmed at the same time (worked could be single diagonal red line, confirmed could be red cross that you use at present.)
Detect duplicate records when importing
enhanced support for the satellites and in particular doppler correction, if only for the few satellite dedicated rigs such as the Kenwood TS-2000, Yaesu FT-847.
Would it be possible in a future version to have a summary by azimuth option for propagation research i.e. 0-30 degrees, 30-60 degrees etc. to identify path obstructions etc.
Knife edge Diffraction (KED) Propagation mode added
Short-path Summer Soltice Propagation (SSS) mode added (seen several times on 50MHz reports in RadCom recently)
Auto send of eQSL (like MixW does) selectable
Meteor Scatter data to have several rows of boxes to record all pings and bursts during a MS qso i.e.

Length milliseconds Strength dB
260 4
320 6
1020 5
3000 4
Distance/ Bearing box to show small map too
Personal box to grab data from qrz.com like mixW does

DG3GAG proposals:

An option where I have a quick view if I have forgotten to sent a QSL card.( A quick summary of QSL cards not sent)
Integrate DX Atlas in VQLog

PA3HEN proposals:

And is it possible for selecting printing on selected country/DXCC??

DL1KDA proposals:

When I am in the QSO Input Screen, and I enter for example DF9KX (my Father), there appear all Qso´s in Past, his Name his QTH and Locater etc. Is it also Possible to show in the AWARD Screen his DOK (when it is entered in QSO´s bevore)
..AND would it be Possible, when I am enter a DOK that is a new one for me on that Band and Mode, that the Programm Shows me, NEW DOK (Like it is allready done when i am working a new DXCC)
How can i Manage more than one QSO ? For example when i am working some rounds or stations with more than one call? Is it right that i can open allways just one QSO Window, or is there a possibility to open more than one?

IZ1CCD proposals:

automatic recommended locator, perhaps corresponding to the country capital, for example Italy is jn61fv (Rome)
to add a modificable database, for IIA (italian islands) - IOTA - WAIP (italian provinces) - CDM (mediterranean country)
to add in the menu "import" CIT.EXE - SEZ.EXE - ARI.EXE (wich are the programmes I sent you and wich were used to make very famous ARI contests)
qso statistics according to the year, month, day, time, band, mode
exportable file log size .DBF besides ADIF
I'd want one statistic of the qsl in this mode:
QSL SEND: XX %
QSL RECEIVED: XX %
QSL DIRECT SEND: XX%
QSL DIRECT RECEIVED: XX%
QSL BUREAU SEND: XX%
QSL BUREAU RECEIVED: XX%
QSL "COUNTRY" SEND: XX%
QSL "COUNTRY" RECEIVED: XX%

COUNTRY: SPAIN, ITALY, FRANCE, ETC.

G0ISW proposals:

Summaries able to show propagation openings including SWL, as an option if wanted (useful to record and show openings missed due to work but reported by other amateurs i.e. to show dates for 2m ES or to show auroras etc.) At present SWL is not shown in propagation openings, nice to be able to include it as an option.
Auroral QSO's recorded to have a 28 day reminder appear on screen to alert operator to possibility of repeat opening.
Propagation openings to allow lines to be drawn between squares worked (to allow areas of ES to be calculated to assist research into likely cause i.e. thunderstorms over alps if that is where they all cross)

OZ2M proposals:

Distance is measured in kilometer, the right physical "abbreviation" for this is km, not Kms, which means Kelvin meter seconds. It is a common mistake to think that the prefix kilo is in capital, but it is not. Only time units are in plural form and no abbreviations have a plural "s" attached.
What Earth Model is used for distance calculation? GPS WGS-84 is recommended by IARU Region 1 for distance records. The "perfect" round earth is only recommended for contesting purposes.
Import of REG1TEST spec. also. This way 10 or more VHF and above contest logprograms are "importable" in one go.
Pure ASCII dump without page headers etc.

Address/personal info database: show also a picture of the operator if available.
Import paths are default from last import.
If window is manually resized it is "difficult" find "standard size." Perhaps a Default Size on a the menu.
TIMESTAMPING A QSO."If" you timestamp a QSO when the call is entered you cannot type ahead. What do I mean by that? Suppose you are part of a pile up then it might be worthwhile to type in as much information as possible prior to your actual QSO, i.e. DX station call, locator, name etc. and perhaps sent report also. Then, as I understand it, the QSO would be timestamped. But this is before the QSO takes place. Now, how to solve this problem? timestamp occurs when either received report is entered, or if no such occur, e.g. just listning to a station, when "OK" is pushed. Altertively it could be either sent or received report, or both. That would solve the IARU Region 1 requirements. In North America reports are not needed to complete a QSO, thus only call og "OK" will work.

Now what to do:
- make it selectable what triggers time, check boxes
    - "OK"
    - sent report
    - received report
    - call
TOP LIST ENTRY. Even though it is possible by executing multiple queries it would be realy nice if you could implement a "top list entry" query in one go. Like:

OZ1IEP status per 2001-11-23
----------------------------
        WWL    Sqr Msqr DXCC Tropo Aurora AEs Es   MS   F2    TEP
50 MHz JO55XU 551   52 113 1086   1318 2358 5832 1998 14053 9311
144 MHz JO55XU 288   14   48 1638   1372 1763 2328 1917     -    -
432 MHz JO55XU 134    7   27 1470      -    -    -    -     -    -

It would make it a lot easier for stations to update their entry with the toplist managers. Perhaps people will also update more frequently, for the benefit of all.

VK4CP proposals:

With VQLog I like the way I have the 5 information boxes "DXCC" "AWARDS" "DIST/BEARING" "QSOs" and "PERSONAL" when entering a QSO. Can all five of these choices be made available when retrieving a record? I don't like only having "DXCC" and "AWARDS" when recalling a QSO.
Map of Oceania

F6ETI proposals:

possibility to print on the QSL label rig infos (per band or per rig 1 to 15 ...)

H44PT / G8BCG proposals:

Is there any way to force the DXCC / countries worked reports to show long path distances?
I had a number of fantastic long path 50MHz QSOs from H44 to PY / LU / CX but the true distances do not show in reports. [In fact I cannot even see the distances without re-entering a QSO with the same station an lookinh at the Distance / Bearing Tab]
Would it be easy for you to provide a button to set a flag for long path in QSO entry at next update?

DG3GAG proposals:

I think the resolution of the euro gridmap is to less; it should be at least size 800x600. Of course you can change it by a picturesoftware but this is not fine for quality to print out.
The crosses of the worked squares disturb. I think better is a red point in the workedsquare.

KM5ES proposals:

On the frequencys rx and tx a drop down menu would be great and faster.

PA3ECU proposals:

Is it possible that by the map showing the locators quares you can see how many locators you have workt already?
Can I change the colors from the cross in the locators for a better vieuw?

EI3IO proposals:

I don't think I have any individual control over the establishment of a group of varied QSOs for which I wish to send a QSL.
To explain - in the print labels flag could you introduce a box: 'print only those marked with *B or *D'.

After use, the * designation could 'disappear'. I hope that gives you an idea of what I'm trying to achieve, if it's not clear please let me know and I'll try again. The background is that say I only wanted to QSL new countries on 28 MHz. I don't think there's a way of doing it, except individually, but I might suddenly decide to concentrate on the band and want to start distributing QSLs.
I know it's a big step and you'll probably suggest using CT or TAClog but do you see any possibility of a limited contest arrangement especially for those that arn't participating seriously but need to keep a record of serial numbers sent and any duplicate QSOs during the contest.

PA3GST proposals:

I had another logbook program in the past where the first letter of the name and qth was put into capital letters.
I know that it is possible to edit the setup for the qsl-card so that you do/don't see the locator when it is/isn't a qso on vhf/uhf/shf, but is there a way to do this with the equipment and power also ?

M0BKG proposals:

There is one thing that stops it from being legal for use in the UK, the power output is not printed on the LOGBOOK PRINT.

G1IOV proposals:

Would it be possible to include a WAZ map so that zones worked could be seen visually as well as listed.

DK8VR proposals:

Is it possible to save "the visible aerea of the map" on this place in the program for the next login ? and not in the nord-west from europe

GW8IZR proposals:

It would be nice to be able to use & make a much smaller radius map for 23cm and 13cm etc with ability to display sub squares
SIMPLE ENTRY WINDOW: For fast sporadic E type openings a simple entry window that allows the user to have just CALL, RSTin, RSTout, Locator and optional comments field.

Available without changing the normal configuration, just something like FILE -> SIMPLE ENTRY opens quick entry window.

If it were possible this simple window would also check the entry format string and place the entry into the appropriate field without TAB. An example might be if I key in IO73TI it automatically puts it into the LOC field and if I type 559 it automatically puts it into the RSTin window, RSTout could be hard coded 5nn :-) any other string GW8IZR etc would be assumed to be a CALL. User could edit highlighted text as normal to override automatic entry if required.

This means that the info from the QSO partner could be entered as it is sent without worrying about the order that it arrives.
A graphic implementation of how the DX-spots are shown and how to tune them automatically in the rig via CAT, as N1MM has.

G0RUZ proposals:

Propagation and mode defaults tied to reports. If I enter 599 the mode could change to CW and if I enter 26 R26 the the propagation is obviously MS and also the same with TMO reports and EME, perhaps this could be user configurable?

DM3ML proposals:

Allow the user to select whether or not the DXCC summaries should list the "deleted" entities, or list them separate.

K0GU proposals:

It would be helpful to have a table were the callsign of a station could be entered along with a country and the program would use that table to determine the country. For instance, in the table you would enter FO0CI=Clipperton Is. Then every time the program saw a past or future entry for FO0CI it would automatically count FO0CI as Clippertion.
On a manual country entry of FO0CI when you enter the correct DXCC country the CQ and ITU zone don't automacially change to the correct zone. If the program can figure out the zone it would be nice to have it automatically enter.
A grid map of the Pacific Ocean islands and Alaska would be nice :-).

G0MVP proposals:

Show the number of times (count) a station has been worked

HB9CRQ proposals:

It would be great if the user could format his own report-forms for special use.

PA3FYG proposals:

Extra selection: all HF-bands(10-160mtr) ,now only all or all(no WARC)

DK1CM proposals:

When I am inputing a QSO between 00:00 and 00:59UTC the option "Ending time of a QSO as start time of the following" does not work.The start time of the new QSO is the start time of the old QSO.......
The fields of awards are not filled in if there was a QSO before with the same station who has the same data. Also QSL-manager and remarks of the old QSO would be very interesting.
Exporting RIG and ANT-position for QSL-printing

M1CNK proposals:

When exporting an ADIF file from the QSL queue, you don't include all the data - in particular the power level is missing. I was looking at using the ADIF file to load into QSL maker by WB8RCR and this can use the power data.

N9LF proposals:

1) When logging a new QSO, the grid square is currently filled in automatically. This works fine for VHF and above QSOs, but is not necessarily appropriate for HF QSOs. I suggest the user have the option to enable or disable this feature for all HF QSOs.
2) Provide a report that shows all QSOs with all stations from needed (unconfirmed DXCC stations to assist with selecting which QSOs to QSL.

3) The option to determine whether electronic QSLs (LoTW, eQSL) are valid for awards needs to be settable on a per-award basis. For example, LoTW is valid for WAS and DXCC, but not for USA-CA (All US Counties).

4) When importing ADIF or other logs, produce a report of imported QSOs, including and indication of which QSOs represent new DXCC band/mode, US States, Grid (Locators), etc.

5) Support VE7CC AR User program for packet cluster spotting via TCP/IP local port (127.0.0.1) port 7300. At a minumum, support AR User via DDE directly (without shim programs).

6) Provide support for creating DXCC submissions. This process should create a QSL card selection check list and prepare printer-ready DXCC forms. The selection checklist should select QSOs for all confirmed entities to assist the user with the selection and sorting of the appropriate cards to be included on the DXCC submission. This will also require that a method of determining which DXCC bands and modes have previously been verified (i.e., submitted to DXCC card checkers).

7) Record the date in a QSO record when a QSL is sent or received.

8) At present, when both a paper QSL card and an electronic QSL is received (or sent), only one is saved in the QSO record. It should be possible to show that both paper and electronic QSLs have been sent/received.

9) Provide a method to allow the rapid entry of QSOs in real time when running stations (for example, running stations during an E-skip opening). This is similar in some ways to contest logging, but without points, multipliers, dupe checking, band map, etc. This might also be useful when manually entering a list of QSOs that were originally logged on paper.

10) When displaying a report on screen, allow the user to select the program used to view the report. Notepad is currently used and that is adequate in most cases, but I want to specify which program to use.

11) When creating a report, include a comma seperated value (CSV) format option. This allows one to easily import the report into Excel for additional sorting and analysis.

12) Provide a mechanism to automatically synchronize the log with Logbook of The World (LoTW). This process should upload QSOs to LoTW and download and apply LoTW QSL confirmations. Downloaded LoTW information should fill in missing QSO information. For example, if the LoTW QSL includes an IOTA reference and the QSO IOTA record is blank, the IOTA reference should be filled in.

Automatic fill will inevitably create the situation where the information for a QSO disagrees with the information in the LoTW QSL. I suggest a user configuration option that allows the user to select from three choices 1) LoTW always supercedes QSO data, 2) QSO data always supercedes LoTW data and 3) Prompt the user in each case.

G4CBW proposals:

After receiving a spot, can it be arranged that double clicking on the spotted call, will automatically enter the call-sign details into VQLog?
I have some suggestions for your ascii importer that would make it easier to use; is it possible to add an up/down arrow key say to the right of the screen that show the first line of text to be imported. The scroll keys would be very useful for testing various lines before importing. The other idea is for when positioning the mouse curser over any particular point on the line of text, will give the character position.

G4BVE proposals:

It would be good to have 2 remarks/comments fields. One field for private use within the logbook and one that gets put on the qsl card. I quite often want to make notes about the qso but don't want these notes to appear on the qsl card.
Default the Propagation, Power, Rig and Mode fields to be the same as the last entry on that band. That is the equipment is looked up after the frequency is entered in the same way that the name/locator etc is looked up when the callsign is entered.

K0KP proposals:

Be able to transfer a QSO's data from the Cluster Spots into VQLog without having to type the information in. Such as hi-lighting a spot, then with a tap of the spacebar have the QSO information transfer to VQLog.

N3UYI proposals:

For us folks in the US have you considered getting the Avery labels that are suitable for QSL info as a standard format in the program.? US software ie Microsoft uses the Avery form numbers as a "standard".

IK0WGF proposals:

Possibility of more kind research, many kind (ex: satellite's name).
Possibility of work on the research extracts (ex: awards for single sat or sat group).
Possibility of generation another archive from principal or from research extracts.

KD5IUG proposals:

Being able to trace progress for VUCC is nice. Just about have my first 100 confirmed grids on 6m. Since you may obtain an additional endorsement for each additional 25 (on 6m), will the program "lock" the grids used for each award and track the new ones - i.e., 101-125, 126-150, etc.??
Question on the "my locator" field. I have a number of 6m contacts while mobile. I know the first 4 characters of grid square but certainly not all six. VQLog won't take just the first 4 only. Any way to force it for the mobile/portable contacts? Not using the QSO for awards or anything but would just like to log them. I've just dummied in the last 2 letters so far. Also, the QSO's may carry across several subgrids. I guess as long as they are 50+ miles away from home QTH, they would be ignored in award tallies (VUCC or WAS, etc.)
Would it be possible to have the qso maps (vucc, etc.) display confirmed and pending using 2 different patterns or colors. Would be nice to see where you have worked and what is pending at same time.
In WSJT modes, we count same station worked from while they are in different four letter/character grid (or diferent DXCC) as an additional initial contact. I can get count by outputting a DBF file from backup of LOG.mdb and running my own program and index (unique) on call+grid. Would be useful addition for me to be able to do it from within VQLog. I've worked one 6m FSK441 friend from 11 grids now! - home and 10 as mobile or rover/portable from truck.
combination of modes and/or prop (e.g. m/s with FSK441 and JT6M and also adding in JT44 for qso's with combined WSJT modes)

K4RLK proposals:

Could the logbook printing be customized as to what fields will print?

EA5FY proposals:

Would it be possible to use a different packet link to the program like AGWPE (http://www.raag.org/sv2agw/inst.htm). I think this is also very popular and should be usable to plugin to the VQlog.

K4RLK proposals:

Have more than one user defined label

SP9SOU proposals:

If VQLog importing from ADIF file - to field "Remarks" (from tag COMMENT in ADIF file) is added one space at the end of field. If this is not by design - please delete this space.
To data about QSO please add field "Via" for information about repeaters on VHF/UHF/SHF. Now I must use for this field "Remarks".
Field "User text" in window "Configuration - QSL labels printout" not is functional. In this field I write information about my rigs. I must change this text for QSL for HF and VHF/UHF QSOs. May you add other fields "User text" for HF and VHF/UHF/SHF QSLs? Or may you add other fields for every band? Also please leave common field "User text" for all QSLs. Please add macros for inserting fields of QSO eg. "Name", "Town" or "Locator" to common field "User text".
Please note: I not want write information about rigs to field "Rig" of QSOs data. In different QSOs (eg. HF - VHF or on other HF bands) this information perhaps is also different. It force to constantly make changes in this field.
Every fields "User text" must be a multiline. Now is only one line. This is not much.

9H1PI proposals:

I set the siren to go only if there is a non worked dxcc only. What happens is that during a spot if the "SPOTTER" call is a new one it will sound the siren. Is there a way to remove it or better make it another sound so that I would know that it is the spotter call that it is interesting.
I would like to get the total of distances in the summaries, not only the best distance.

K6EID proposals:

The map could display both QSLed and worked. Maybe worked with the red "X" box like you have now but show the QSLed squares with a blue "X" or better yet, colored in, in a color like blue.I have done the latter manually and it looks great with dark blue covered QSLed squares.

PE1AHX proposals:

To make it easy to process a large stack of cards it would be nice if AFTER modifying the QSL status for a QSO the focus would immediately go back over the callsign. Currently the cursor is behind the call, it would be nice to have the call marked for replacement (blue), so you don't have to move the cursor back, but can immediately type the new call. This only happens if you do not specifically select the QSO (have only one entry for the callsign & immediately press the function key):

Example: Type callsign, Press ENTER, one QSO shows up, press F2,
result: cursor behind callsign.
I would like to see a feature whichs allows me to connect JPG images of received QSL cards to the contacts in the log. Nicest way if VQlog would also handle the scanning, but some easy way of storing filenames with the QSO and have the program launch a viewer would be an improvement. The path to these filenames should be somewhat flexible as some recent cards may be on a hard disk, older ones may be on a CD or DVD.... A single QSO may have multiple received cards, as well as front and backside.

G4DBX proposals:

Assume the remarks field, based on the information entered in that same field in the last QSO with that station.

M0KCM proposals:

When I work a new country I am told "new one on this band". Is it possible to also tell me "new one on ALL bands" (Being a new hf operator of only six months, I only have 130 countries worked and so ALL band new ones still happen every week).

K1DG proposals:

Create a PRINT option that will create a print queue containing BOTH the QSL label AND the address label (from the Callbook CDROM data) for all selected QSOs on the same sheet of labels?

NW7U proposals:

it would be nice to be able to select between portrait and landscape print modes, "print-to-fit-page" options, headers and footers.

EA5FY proposals:

I have just found out that VQLog does not automatically change from winter time to summer time and vice-versa. Is its possible to change it automatically (at the same time as windows makes the change) or at least put in the config window the dates of changes?

ES2NA proposals:

Possibility that log programm read frequency, mode from rig.
More then one user designed label.
When I type report 59, then program selected mode SSB (mostly used mode). When I type 599, then program selected mode CW. When I type 59A, then programm selected Type of propacation AUR.

KA1A proposals:

I would like to also print the log but in a DXCC order
In PRINT LOG - ability to print in record order, DXCC(callsign) order, and as it is now.
Just my thought - would prefer the QTH Locator to follow the callsign in the logbook screen and in the print log just after the callsign. There is plenty of room in the print log between the callsign and HIS RST.

KA2LIM proposals:

Make a option that will produce a list of countries NOT YET WORKED.
Print the log showing, date, time, call sign, (band), (country), rst, qls-s/r. The two that are in ( ) does not shown now.

WA2RZJ proposals:

Possibility to run WPX summaries for continents (Note from author...sorting them by contient in the summaries)

DG5BD proposals:

When accesing a QSO it would be nice to step to the next one, or to the former one, by pushing the up and down key.
Connection between the input window and the ES-Calculator

GW3ZCF proposals:

Providing the option for automatic entry of, for example, WAS and IOTA for stations worked before

SM7FJE proposals:

There should be a chance to change data directly in those lists
In the QSO document there should be an arrow to scroll 1 step forward and one step ahead (not only back to last QSO)
Award lists (DXCC, VUCC etc.) in a format that you could send them direct to the award manager
Award lists where you can mark which QSO's you have applied for earlier and which you want to add this time (for endorsements)
A chance to add and delete propagation modes
A chance to add and delete QSL sent/rec modes
A chance to add and delete traffic modes
A chance to choose large or small characters for all fields
A chance to search for parts of calls with * as a wild card
A chance to search for parts of locators with * as a wild card
A chance to search for new DXCC/loc/major loc worked but no QSL sent yet (to find those you missed to send a QSL to)
A generator where you can produce your own lists
QSO modification: arrows to jump to next or earlier QSO without going to the list (I enter the log after the day and if the same mistake is mad on all QSO's it takes long time to correct) Let the cursor stay in the same field when stepping one back/forward.

K0TV proposals:

Get QRG, mode, etc. from radios

DB5KN proposals:

Implement a column with the distance when browsing the log

N9BC proposals:

I would like to see 2 or 4 user definable fields. Example: YL's , State Caps, QRP, and drop down selection for Nets.
Then be able to make customized reports.

SV2BBO proposals:

If the SWL is cheked, the QSLlabel printing 1Way instead of 2Way

CT1CBI proposals:

Print several QSOs in the same label
In QSLs/Labels print the manager after the callsign, like "TS7N via DL6BCF"
Store the date in which the QSL was printed.

WK3C proposals:

Support "letter" size (8-1/2" x 11) for printing 4 QSLs in landscape pre-perforated sheets (Avery 8387)

KE4BMT proposals:

Possibility to use a TXT editor other than notepad for showing the summaries

IZ2EWV proposals:

Last (probably I just asked it to you): could you add to VQLog the option of an open communication protocol for the AZ/EL rotators control, like the EASYCOMM 1 or 2? It should be great to leave to the OM the freedom of choose between a commercial ready-to-use inteface - like ARSWIN is - and the possibility to develop a homebrew solution, like a certain number od EME'rs just did.
For instance, me! I've built a complete AZ/EL controller with speed-adjust feature able to be used locally and under the control of the PC, actually running the software made by F1EHN, thanks to the fact that Jean-Jacques left his communication protocol available to everybody. It is true that actually his software supports also the ARSWIN feature, but nevertheless he leaves two alternatives

OH3HTU proposals:

There should be feature: DXCC by band and by MODE. For digimodes there should be also a summary feature which combines/ handdles all digimodes as one mode.

E.g.
156 / 101 DXCC in 20 meters in SSB (Worked/Confirmed)
190 / 120 DXCC in 20 meters in CW
20 / 10 DXCC in 20 meters in digimodes
201 / 123 DXCC in 20 meters all modes

List about DXCC by band and by mode as same way ...maybe list of missing DXCC by mode and band also ?)

WK3C proposals:

Printing QSLs "4 up" on US Letter size (8.5 x 11 inch) Avery Postcard paper ...
The sheet is standard US "letter" size - 8-1/2 inches by 11 inches ... the postcards are 5-1/2 inches by 4-1/4 inches, with perforations to separate them. They divide the sheet into 4 equal areas.

Since "standard" QSL cards are slightly smaller, the easiest way to get standard size QSL cards would be to print the 4 cards right up to the perforations, with their corners meeting at the center of the page. That way a paper cutter could easily be used to cut the border all around the sheet before separating the cards using the perforations. (just a suggestion)

W5/DK1CM proposals:

If you start VQlog from the comand line is there any auxiliary to select the config- and logfile?
e.g.: C:\vqlog> vqlog20 -log:dk1cm.mdb -config:default.mdb

S51U proposals:

Print 2 or 3 qsos on one label as on sample is, I have 3 qsos with 3xy7c on 3,5 - 10 and 24 qnd I want to print only one label not 3.
Search log by qsl manager as I can browse by "remarks", I just want to see all qso which qsl mgr is KU9C for example - then I print all the qsl labels for him and send directly to USA....
Support SWL callsigns with formats like "UA3 - 155 - 75"

ON6AA proposals:

Use DXconcentrator from ON5OO to get the spots from DXCluster (DXC is on www.on5oo.com)

9H1EI proposals:

Print individual QSL cards directly (without using the print queue). From the log access window, etc.
Access the logbook by QSL-manager

M0ELS proposals:

i would like to see the inclusion of when in a qso with more than 1 station.ie in a net.....that their callsigns could be added to the dbase as well.this will prevent multible instances of vqlog being opened to add them to the logbook.perhaps even a smaller pop-up windows.

PA3BZL proposals:

When changing the DXCC assume the Zones/Continent of new DXCC
Automatic assignation of deleted DXCC when entering QSOs with old dates
Selection of the fields to print when printing the logbook
Selection of records to be printed when printing the logbook

DK8XT proposals:

When I print out QSL-Lables normaly a page of lables is not complete, a couble of lables are blank. It would be nice to tell the programm wich label is the first to be printed. For example "Begin in line 5 row 2".
When I work on an expedition, my reports are more or less "real", so I dont send 59(9) the whole time long. It would be nice to change report with one key, f.e. Alt+F5 = 57(9), Alt+F9 = 59(9) and do on. That would be much quicker.
It is possible to work with different Logs, for example DK8XT for my home-log, FP_DK8XT for my FP-log, OX_DK8XT for the last DXPedition to OX and so on. Unfortunately it is not possible to see which log is active! In the
headline I see only my normal Callsign. It would be fine if I can see the name of the log, something like a description.
When I change the log it is very easy to make a mistake and klick on "File" "New" "Log" insted of "File" "Open" "Log". There is no further question, a new log with the same name is created and all logdata is going to be deleted! No backup, no fun ;-)). Is it possible to have one or two security-Steps, questions (are you shure) or something like that?
In the pile-up you often hear fragments of zwo or three callsigns nearly at the same time. With a paper-log I write these fragments in the next lines and ask for the full callsign when the last QSO finished. It would be great to have something like that in the program! Somethink like a stack. With a key-stroke the last/first fragment of the stack moves to the callsign-field of the normal log.

VE3XK proposals:

Use "Field" instead of "Main Square" and "Grid" or "Locator" instead of "square".
Support of American label paper sizes
Support of Label printers (Seiko SLP 100 Smart Label Printer). Just a Print option after each QSO and it could print both QSO and address label with that latter info taken from the Call Book or QRZ CD-ROM
Direct control of Yaesu rotor
CAT interface for Kenwood TS-2000
Direct support of digital communications via sound card.

DG1CMZ proposals:

Possibility to get the summaries in ascending and descending order.
My problem is the following - an example: On June 1st I work VK9XX and he says "QSL only direct via QRZ.COM" So on December 1st I print my labels for QSL with VQLog. My Problem is now to know if this QSL can be sent via buro or has to be send direct. Same is with managers, some managers are avaible via buro (what i prefer) and some are only direct. And so I now start to check some hundred qsos with the cluster wheter it was a direct qsl or can be send via the buro.
So a Checkbox "Qsl only direct" would be great to easily see later when I print the labels if I have to send direct or of buro is possible.

PA2WJZ proposals:

Possibility to sort the "browse" windows for different fields (Date, Callsing, etc.)

NW7U proposals:

WAS --- It's important to know what states have NOT been confirmed. A "States Missing" list would be good.
ZONES & PREFIX --- It would be a nice touch if these were sent as part of the export function
Printing on Letter-size paper

M0BPQ proposals:

Ability to transfer the data from the DXtelnet window to the main log
Possibility to force the callsign rather than "insert XXX if none specified". I find that when importing a TACLOG .ADI file
I use a much reduced "received spots" window on top of the main logging window. A keep on top option would be great for me.
The option to work someone and then send a spot to the cluster without going into DX telnet and retyping would be useful
Bandmaps. I have grown to love the bandmap in N1MMs contest logging software. Perhaps not so useful outside of a contest, but I suggest that you download the freeware from www.n1mm.com and see how you feel about it

NA9D proposals:

It would be nice to be able to print address labels for all stations in the print que for QSL cards. Or it would be nice to be able to print labels like you do QSL cards.
I cannot set up particular print modes on my printer or change page orientation, etc. For example, if I want to print an address on an envelope, my printer requires me to put the evenlope in the printer in what would be landscape mode (the narrow part of the envelope is stuck into the printer). Your program only prints the address label in the portrait mode and I cannot change the page orientation.
It would be nice to have rig control available.

ZR6D proposals:

I wonder if you could include a place for IRLP contacts (possibly also echolink?)

VU2MHK proposals:

I am in India and needed to set the offset to UTC time by 5 and a 1/2 hours. The program does not seem to take decimal points (ie fractions of hours) in the UTC offset time in configuration. Would help if it could.
It would be neat if I could sort the log that I view in Browse mode. Then I could just click on the top of a particular column and be able to sort by any of the columns (just like Excel). Say I am not sure the towns I have spoken too and don't remember the spellings very well too. If I sort by Town column then I could browse thru quickly and easily and find whatever I was looking for. Of course this would not effect the order in which the records are stored. It would only be a temporary viewing in browse mode.
Now I may be asking a bit much but it would be great if the order of the columns could be shifted in the Browse mode too
In the maps view I could not see the whole of India. Wonder if that could be incorporated as I am mostly talking to Indian hams.

G8FXM proposals:

I've been using MixW the digital modes application latley and I note that there is now a gateway applet that interfaces with MixW and DXKeeper. As QSO's are made and saved in MixW they are entered into DXKeeper via the gateway applet. The applet is called Mix2DXLab (for MixW to DXLab) and the author is N2AMG, Rick Ellison.

WA6TMJ proposals:

I love the text listing but would like to see a colored fill in map of WAS states worked.

SM0TSC proposals:

Possibility of ”AUTOMAGIC” CLX-spotting with the data just entered in log
Automatic mode depending what u enter as report (similar to logger contest log) e.g. if you enter 599 mode should automatically be CW if you enter 59 it should be SSB (Or other of users choice)

DH4NWG proposals:

Support the UKW-EU-D award (complicated rules)

PY1RO proposals:

I want to go back to an approximate date to check what geographies I was then working on 6m. Obviously I don't know an exact date, so I need a way for VQ to take me to the ballpark of the date I am searching for. If I happen to specify a date on which there were no entries, VQ simply tells me that and doesn't take me anywhere. It would be nice if in this case VQ could take me to the closest logbook entry to the date that I specified. From there I can then use BROWSE.

N1JFU proposals:

Set default modes per satellite

G4PEL proposals:

Window Display (1024 x 768): I am placing the "Additions of Record's" Window top left, Callbook Lookup (Flying Horse CD) top right and shorten to same length as "Additions of Record's", and across the bottom remainder of the screen "Last QSO's. Each time I open VQlog I have to re-position the Windows , how do I save the window positions.
Previous QSO's. When I entered a new QSO in the Log it would be most useful to see previous QSO's with the same call automatically appear in a separate window, is this possible.

DL8EBW proposals:

1.) MS: As you know one idea ist still around the MS datas - I was thinking it might be nice to have such a tool as a normal text output, like:
```
MS Logbook:
Date Time Call Locator TX RX B P sec status remarks
13.03.2003 1112 ea6vq jm19xx R28 R26 10 12 0,3 complete nice refl.
```
Fine will be that you be able to sort on all inputs (like sort on call, sort on locator, sort on dates - time periodes... ) and /or be able to show the results on an map (europe) - statistical overview will be not so easy...
GPS total new idea - I have bought an GPS-USB-mouse (NMEA standard protocoll) - I t works with some amateurprogramms and is able to give me always exact longitude and latitude on my position. The mouse will work on USB ports 0 to 6 (the serial GPS mouses only up to 0 to 4) The idea is to have always the right position at the logbook and if you wantyou are able to use it instead typing the exact locator... it will be very nice on expeditions!!! A sample for such programms you can find at: http://www.user.fh-stralsund.de/~dl0hst/software.htm
He have written a short programm for it - Also some other Logbooks use it! they will have the input routines for LOCATOR or / and Long.+ Lat. - as I said - its very wellcome on expeditions...
Is possible to get the MS datas out??? I mean I wants to send an complete activitiy report from VQLOG:
--------------------------------------------------------------------------------
         DL 8 EBW - DL66a / JO31NF    MS-Aktivitaetsbericht 144MHz
--------------------------------------------------------------------------------
    DATUM     ZEITRUFZEICHEN      LOCATOR TX       RX       ART   P B sec QRB
--------------------------------------------------------------------------------
04/08/2006 04:28 LA4XGA           JP33VC 27       R28      FSK4 2 4 0,2 1321
08/08/2006 05:38 4O3T             JN92HM 27       R27      FSK4 M M 30! 1301
09/08/2006 19:50 RW3AC/1          KO78MS R26      26       FSK4 2 4 5! 1948
The Map for worked squares - will be nice to have not only a red cross! For worked I suggest yellow background - and red for worked and confirmed... check pse my homepage, its an very old but effective programm from DL2AOM...

W4WB proposals:

A way to force the VQlog window (small format) to have a docked position other than in the center of the screen upon startup?
Same for the VQcall
Link to the GOLIST database

VK3KOS proposals:

In sat data tab......can it be set to a default setting that will hold until it needs to alter it manually

N9DG proposals:

A way to directly edit the fields in the "Browse the logbook" view without having to use the "Modify" option to change individual entries. This should work something like a spreadsheet and allow block fills in any of the columns. The view should also sortable such that all QSO for a specific date range and frequency can be put into this edit-able view. This would be very useful for filling in rig and antenna data after contacts have been entered or imported in the log.
An option where the sent or received RST is automatically filled in to match the sent or received RST when it is entered.
Frequency and mode data automatically filled in from external radio control programs, an ability support several control programs simultaneously.
The frequency automatically sets the "Rig" and "Power" to settable defaults per band.

DJ7KG proposals:

More accurate frequencies (28.250.nn)
Possibility to select the ouput columns in a summary of QSOs

OZ1PIF proposals:

I suggest that you do the mapping of the WSJT modes into "Data" which is a legal mode for LoTW

VE3KLM proposals:

Possibility to disable the automatic jumping to the DXCC / Locator tab when a new one is worked.

DL1EJA proposals:

It there a chance that you write something that you do a combination of CAT and Station-Setup? I mean if you QSY to another band that the station setup like antenna and power will be changed automaticly? Or only the posebilities you put in the database for the choosen QRG are available.
Most Wanted Squares. Create someting for other bands like 2m? Here it is 6m, but would be nice for 70cm also...

W9KNI proposals:

I think it would help both you and me if you were to add support for my rotor controlls to your software.

Here are the necessary command instuctions for Rotor-EZ:

"Important note: The program you are using must insert leading zeros into bearing commands, such as “009” degrees, instead of “9” degrees. Most programs are already configured this way, but some are not in their default mode, and in such cases you must change the default setting or the RS-232 portion of Rotor-EZ will not work properly.

Rotor-EZ can also be commanded from any terminal having RS232 output, using the following configuration: 4800 baud, 8,N,1    Note that upper case/lower case must be used as listed for the commands below to work:

"AP1xxx<CR>" sets target bearing to "xxx" degrees where xxx are three digits between 000 and 360, and executes. A typical command to rotate to 080 degrees would be AP1080<CR> Note that the <CR> is often labeled <Enter> on many keyboards.

"AP1xxx;"    sets the target bearing but does not execute.
"AM1;"        executes rotation to the bearing set by the "AP1xxx;" command
"AI1;"         inquires current bearing; and responds with (000-359) degrees
";"        terminates rotation
"E"        enable endpoint option – effective immediately
"e"         disable endpoint option - effective immediately
"O"             enable overshoot option - effective immediately
"o"        disable overshoot option - effective immediately
"S"             enable unstick option - effective immediately
"s"             disable unstick option - effective immediately
"V"          reports version number
"J"             enable jam protection - effective immediately
"j"             disable jam protection – effective immediately - NOT recommended!

Note that during any rotation initiated by an RS232 command, the rotation can be halted and further rotation cancelled by a momentary press of the Brake paddle. Also, an RS232 operation can be overridden by using the pointing control during rotation; when the control is moved rotation will cease and the control will wait for a new command after the five second brake delay is completed."

That is the official set. Note that all you really need is "AP1XXX" followed by either "AM1" or <ENTER>

The "AI1" command might be useful when a user initiates the program after using the rotor manually, so that the program can find out where the rotor is presently pointed.

The other options need not be addressed in a loggin fprogram in my opinion.

OH3MBC proposals:

Support more accurate frequency in order to be able to set the QRG of the rig when passing a DX spot.

OH2LFM proposals:

How about providing a number of general free-form, user-nameable fields, that could be included by user selection in the QSL sticker printout? This feature could provide input for several active award-points -providers, like those travelling different IOTA-islands etc. Field information could stick like mode/frequency from QSO to the next QSO. This feature could accommondate many "could you add this field" -requests at once!

PA5BM proposals:

About the SWL however...It would be nice to be able to list which SWL's are in my log. Maybe per DXCC entity and during a time period or from different locator and callsign. Just like regular QSO's . But only a simple listing of which SWL's would be great.

PG2D proposals:

SWL numbers. When I do: "access by callsign to the log" and enter OE011/0388 or OE011/0367 in both cases I get a table of the log-entries for both callsigns. The same happens when I enter "OE011" without "/0388" or "/0367". When entering "OE1/0140"all is OK, I only get OE1/0140.

DIG member nrs and the DIG Award file DIG.MDB. When I enter "PA 8607" or "PA-8607" the program automaticely changes that into "PA/8607". However in "DIG.MDB" (the updated one) this callsign is given as "PA-8607", but other PA-SWLs are recorded as PA/9565 and PA/8766. Moreover: when I do : "Awards>>DIG>>All mode, all bands, worked or confirmed, To display or file or Print"....ALL SWLs ARE LEFT OUT. But they DO count for DIG-awards!

DG3FK proposals:

Allow selection of all HF Bands, incl. WARC
Show the heading in the DXCC tab

VE7YC proposals:

Possibility to change the label size from MM to Inches.
Or to use the Avery Label Number

WB4MNK proposals:

Setup A DDE for a real time interface with MixW

DB9UH proposals:

A way to display my log sorted by call sign and showing AT THE SAME TIME the qsl status (sent or not).

IZ3CGD proposals:

Posibility to display an azimuthal map
Link to DX-Atlas to show maps

WA6PYQ proposals:

Possibility to print a listing of all QSOs containing a certain text in the remarks field.

Martin Groth proposals:

If you print several pages of log-lables und there is paper-jam, it would be nice if it would be possible to chose the start-side. F.e. the first three sides are ok, side 4 is jamed, so I will start with page 4.
If I will chose another log (dxpedition f.e.) and I chose a wrong item ("create new log" instead of "open log") an empty log opens without any warning!

HB9PJT proposals:

make the DXCC list including the classic bands sw bands and the WARC bands.

OZ1O proposals:

What I miss is an option to select export of only QSO's which has not yet been QSL'ed.
And with and option of having these now exported QSO's marked as E for electronic QSL

G0KTN proposals:

Generate the same range of summaries and graphical statistics for SWL entries in the same way as for stations worked. (Note from the author: You can create a new log file just for storing the stations you received, and in that log don't tick the SWL box. You will be able to get all functionalities of the program for the stations heard. When you want to enter a QSO then you will have to open the former log file. So, two log files, one for QSO and another one for SWL. Use functions in menu "File - Open" or "File - New" to open or create different log files.)
Use COM port numbers above 8 for CAT.

DL2JWN proposals:

Posibility to export to ADIF selecting by record numbers.

HB9WAH proposals:

Support Yaesu FT-736R and FT-890

NP4X proposals:

Support integration with DX-Cluster using the sofware from DXSoft.com
Support integration with MixW

OE9ADW proposals:

option to print the actual printing date on the lists in the header

OH7NRW proposals:

Supporting CAT interface for Ten-Tec Orion. http://www.rfsquared.com/Orion/orionmain.htm

In addition N4PY had been working with the control software. That is a full control of the TCVR.
His site is: http://www.ralabs.com/n4py/

IK5QLO proposals:

Built in cluster monitoring program using a common TNC

N8FGX proposals:

Is there a way that I can set printing options, by paper selection, to print envelopes in a different orientation? I would like to insert the envelope into the printer with the return address side (left side when printed) going into the printer first.

G1NIM proposals:

Supporting the Yaesu FT-747GX

CU3AK proposals:

Supporting more than 30 awards at the same time.

F4JRC proposals:

add in the propagation mode: long path or short path he\'s a new 40 meters enthusiast, looking also for the 80 meters ...
in thoses bands, a morning qso with a vk5 should not be a short path on 40 or 80 ...
a voice keyer ...

K9DUR proposals:

I would like to see 2 additional fields in log.mdb. These fields would contain the date that a QSL was sent and the date that a QSL was received. By default, the fields could be automatically filled in with the current date when the QSL sent/received status is changed with the option to change the date if desired.

PA3C proposals:

That the DX-Spot windows assume the locator of both the spotter and DX and shows them in the "New/Not confimed" tab if any of them is new. (Note from author: This behaviour should be configurable (Don't assume / Assume always / Assume only for VHF&up bands)

DJ5RE proposals:

Don't show CW/Phone separate warnings for worked/confirmed DXCC's in HF bands (as it's done now for VHF bands). (Note from author: This behaviour should be configurable)

SM43XIH proposals:

Show the geographical area information also in the QSO lookup/modify window, not only in the QSO entry.

KC9GGV proposals:

See the possiblity to support connection with VE7CC's DX spotter program

SV8CS proposals:

Show the status of qsling (send and received) on summaries >summaries of QSO > All qso\'s or worked , as we can see in the EME initials

DF7RG proposals:

print out QSL's or QSL-labels sorted by DXCC (e.g. N / W / K / A is USA; AM / EA is Spain a.s.o.)

SM7GVF proposals:

A new tab in the DX-Cluster window listing the stations not worked before.

K2WO proposals:

Support the TenTec Orion. I am providing the URL for the TenTec Orion Programmers guide in PDF format. Her it is: http://www.rfsquared.com/cms-files/565prg%20Rev%201.2.pdf

WA2NXK proposals:

Possibility to enter my laser (light) contacts (300GHz) into VQLog. I believe that the correct way to enter this now would be 300000 MHz, but VQLog does not allow a frequency this high. Is it possible to allow for a larger number or have a GHz value in addition to MHz and KHz?
Also, the mode used for these contacts is PWM (Pulse Wave Modulation) at 18000 Hz. This mode is not valid in VQLog. Since there are so many different modes that are possible today including Echolink, IRLP, various WSJT modes (too many to keep up with), PWM, etc., can you allow the user to just type a mode name if it is not supplied in the pull down list?

G4ZWY proposals:

Interface with MULTIPSK. http://f6cte.free.fr/index_anglais.htms

F4EKV proposals:

Interface with some CAT program using DDE (Supercontrol / Hamradio Deluxe)

OZ4PH proposals:

I run PSK31 (using a PSK-20 rig from Small Wonder Labs), so I would like support for Digipan. I believe this is the most widely used PSK31 program. Several programs claim to support the program, but I have not located any technical info about integrating Digipan in other programs.
I would also like support for DX Atlas (see http://www.dxatlas.com/Dev/ ). Alternatively support for HAM Atlas.
I would also like support for CWGet (see http://www.dxsoft.com/dxs-exch.zip ).
Last, but not least, I would like to have better support for QRP. Several awards, including DXCC and WAS, are available in a QRP variant. As far as I can see, QRP QSO's are neither supported in the award "manager", nor in QSL printout.

AG4AN proposals:

Support BuckMaster's on-line lookup.

F4BKV proposals:

- a "contest version", not for use for the main contest, but mainly for contest where you can do both the contest and the award (i.e. the IOTA contest or the national contests ). Because in this case, it would be very nice to have directly the multipliers (normaly the provinces or the IOTA numbers) directly fill out on the correct award.
- if the above comment is not possible (because I know it's maybe too complicate to program), maybe an import function with more customs parameters where you can define exactly the fields and link them to thoses of the VQlog.
- the import version for N1MM contest log
- an export in cabrillo or other ascii format, because sometime the ADIF format is not useful.
- on the QSOs tab, this is nice to see it flashing where the station was already contacted, but if will be nice if, when you type the first 3 letters of callsign, then all QSO with stations with same 3 letters appears on this QSO window.

ZS2EZ proposals:

interactive linking with LoTW/EQSL.

N9LF proposals:

I noticed something when updating QSL Indicators from LoTW. It seems that everything works as expected, unless the times stored in VQlog are just slightly different in LoTW. In this case, the difference was just a few seconds, but that caused the minutes to be off my one. For example, an QSO that I recorded as 10:58 but LoTW shows it as 10:59. The QSL indicators did not update the QSO record as confirmed electronically.
When I noticed this behavior, I modified the QSO Time in VQlog and ran the update proceedure again. This time, it matched up the records and correctly updated the QSL Received flag.

While this isn\'t really a program bug, it would seem that it needs to be considered for a future version. I am not sure just how close the times should be in order to be recognized as a match, but I checked LoTW and they use 30 minutes.
Another enhancement that would be helpful is to use the LoTW QSO information (in the \'detailed\' report) to automatically update the awards for IOTA and STATE (WAS), just as I would do manually when I receive a paper QSL card.

HB9CRQ proposals:

It would be very nice to have a format to display the log including initials, DXCC and SQR count which could be used to post the stations worked on internet

SM2GCR proposals:

When a pileup suddenly comes, it would be nice just to mark a checkbox and then you are in pileupmode with less info to write down.

LA3ZA proposals:

It would be nice to sort contacts, worked status etc by power level in order to answer questions like: How many DXCC entities have I worked using QRP-level etc
Likewise it would be nice to sort confirmed QSO's according to whether they have been confirmed by card only, or by lotw only etc.
Last, this is something I have never seen in a log-book program (but I havent's tried them all): For a HF DX'er it would be nice to read the current solar flare index and A/K-index automatically from the internet and store it with the QSO. It can be read from e.g. http://www.sel.noaa.gov/ftpdir/latest/wwv.txt

G0ISW proposals:

QSL received via field (Add SK - Silent Key feature, for cards that will not be received due to the passing away of an amateur. QSLs marked in this way should appear as SK in the \'list not confirmed\', or otherwise be indicated. My thinking is that I have just used vQlog to list as a web page QSL cards needed for contacts as far back as 1995 and a web search has revealed that at least 2 of the OMs are now SK.

Alternatively a QSL card option of 0 (zero) or N (No qsl) to indicate that a QSL will never be received from them. Or whatever symbol you want if you think it is a good idea!

If a locator square has been worked more than once with several different stations, but no QSL cards back so far then the callsign shown for \'list not confirmed\' should ignore and not show the SK card or the card that will never be sent, but instead show the callsign of the next station from that square with the QSL card you need.
Ability to draw on map selectable distance radius circles i.e. 2200km as maximum single hop distance.
Meteor Scatter: Have previously suggested modifying the time from seconds to milliseconds due to most pings being very short. Now suggest in addition to a box to show ping length, have a second box showing maximum strength in dB. This is because everyone seems to use convention after completion of sending a summary by talk mode of cluster such as \'1b 2p 560/13\' which means 1 burst 2 pings maximum time 560 milliseconds and maximum strength 13dB.
Internet linking: I had a qso yesterday on 145.5125 MHz FM with VE7TDA. He had connected to a local EchoLink simplex node 2km away from me and I used my radio to speak to him. For logging purposes I can enter his callsign the band and mode, but need a way to show it was via EchoLink otherwise the programme will show I have worked Canada on 2m FM! I have to log him because I was on the radio. Need a checkbox similar to the SWL box so that I can click into it and the QSO does not count.
Propagation studies: Would like to see new facility of viewing colour charts by distance/mode, for example distances in blocks of 100km i.e. 900-1000, 1000-1100, 1100-1200km and in each block the ability to have number of qso\'s by mode for that distance. Difficult to explain in words, but DK5AI website uses these charts and others to show spread of distances by mode such as ES or Aurora. Very good to help understand propagation on VHF better.
Would also like ability to see month/mode chart so that ES, TRD, AU modes can be historically seen by band again for propagation understanding.

K4NNX proposals:

Support the DXCC challenge.

WD0AKO proposals:

support to do call lookup on the free callsign databases available from the FCC available for US calls and the RAC data for Canadian calls?
Since the data is free I would even be interested to pay a bit more for this support. These databases are updated weekly, but if the user updated a couple times a year would be fine.
These links below are from the following website
http://www.n3fjp.com/ACLog.htm*
ftp://ftp.fcc.gov/pub/Bureaus/Wireless/Databases/uls/complete/l_amat.zip
**ftp://ftp.rac.ca/pub/cdncaldb.zip

DD0VF proposals:

I would like change the output columns in the summaries -> eme initials, but seems there is no way. I would like have the mode for example, but there is only NUM. DATE TIME CALLSIGN LOCAT. TX RX S/R REMARKS QRB. btw, it would be nice to configure the output form of the summaries completly by the user

K8GUN proposals:

The call book window provides me with a station's address. I would like to send that address to the print que. After I have looked up enough calls this way, I could fill the que for a full sheet of labels. Presently I only see that I can print a single label from the call book window.

CT1FJC proposals:

Would it be possible for a future version of VQ log to have maps like DX Atlas, and to be able to mark Squares worked or confirmed on the same map. Either by colour change or hash marking

SQ1K proposals:

It would be nice when IF transverter frequency could be adjustable as for ex. 14.001.6 same as is shown in main Log window. My transverter have 1.6khz difrence and then I can`t adjust it only 14.001

ON4BCB proposals:

Possibility to print QSL only for new EME initials.

DG1NFS proposals:

I have a wish for futured VQ Log Versions. I Make QSL Print, then i see in the QSL List, i have 900QSL for Printing but on one QSL-Card i can Printing 3 or 4 QSOs with one Station of another Band/Mode. Can you make an other Counter for the Reality required QSl-Cards by the Printing?

IW1QN proposals:

the Support of VQLOg to use ADIF File of the LoTW Report for Update QSL Index for Fill Info in QSO? This is an Example part of ADIF of LoTW Report: IW1QN IW1QN VP2E 20M SSB 20090329 202309 Y 20090405 12 8 11 NA-022 FK88 Is a Good Idea if VQLog, when make the Update QSL Index, fill all Info of the QSO, like WAS or other Award

IW3GOW proposals:

in the configurations option is possibile selected if the e-QSL are valid like the D and B, buth these option is not practicable - we must not mix up the E-qsl with Lotw and other QSL. We have 4 possibilities to send and confirm the QSO: 1) Bureau (qsl valid for all awards) 2) Direct (qsl valid foe all awards) 3) E-QSL (qsl valid for CQ Awards like CQ DX, WAZ, WPX, USA-CA) CQ accepts electronic confirmations for all awards for contacts confirmed via eQSL.cc (limited to confirmations from eQSL “Authenticity Guaranteed” members). For details, click here or see March 2009 CQ, page 92. CQ plans to give award credit for contacts confirmed via the ARRL's Logbook of the World (LoTW) system, once that system is set up to support non-ARRL awards. We are working with the League officials to help make that happen. These will likely come online one award at a time. We will update this page when there are any changes. 4) LoTW (qsl valid for ARRL Awards like WAS, WAC,DXCC,..) For QSL SEND it would be good to write all modes, including all four : B,D,E,L and N For QSL RCVD it would be good to write all modes, including all four : B,D,E,L and N and in the summary's SELECTED a pleasure, making the program more complete and flexible. for exemple I send all qsl via LoTW and Bureau the most important also direct ( 3qsl x 1qso) and receive olso 3qsl)

G4RRA proposals:

It would be really useful to be able to search the log for counties worked in a particular state. At the moment I have to search by county and so its difficult to see what counties are missing from what states without going through all of the counties listed. I would love to be able to see what counties are missing from a particular state for example "What do I need in California"?

SM7GVF proposals:

implement a status for the QSL as \"A\" for approved by ARRL when counting DXCC? This would be very good, tracking what has actually been sent in (and accepted) for the award

PA2KW proposals:

I use the F5 shortcut very often, but by accident I hit the F4 button. This resulted already 5 times in entering multiple qso\'s with the wrong time last year. It might be an idea to ask an extra confirmation when changing between Hand or PC time mode. Of course it is my stupidity but I pull my hair when a new DXCC becomes invalid due to time mistake

Click here to go to VQLog's home-page
Join VQLog's Mailing List !