Last updated on 13 November 1997
This is a list of the items that are being considered for future releases of TR Log. This is the list that I will work from when I sit down to work on the program. Sometimes, other features will be added that are not on this list because they are easy or sound like fun. The items are shown in no particular order.
If you know of something that should be on this list, please either post it to the trlog reflector, or send e-mail to tree@contesting.com.
New releases are made approximately monthly - or as required to fix critical bugs. Updates are available one of three ways:
E-mail on the internet with a uuencoded .zip file (about 600K). To get on the list contact n6tr@contesting.com or in Europe, contact sm3ojr@pobox.com.
From the TR Log BBS at (503) 658-6116. If you haven't logged in before, you will need to setup your password, and then send a mail message to the SYSOP asking to have your privileges upgraded so you can access the updates. This is normally done the same day.
From any of the distributors via floppy disk. Normally a small amount is charged to cover expenses.
Check out the N6TR home page for other interesting stuff.
73 Tree N6TR
1. Frequency in log file: I think I have been convinced to allow a mode to print the frequency instead of band. However, this does take up more room and might push the log entries beyond 80 characters. CT got around this problem by not printing the sent information, but I don't think this is a good idea. As you might have heard, there were some disqualification's in the All Asian test from people that used CT because of this. Also, I know the CQ Contest committee is concerned about the same issue. K1EA appears to be working on improving his log format in response.
As everyone has point out - this format will not be downloadable into the after contest logging programs. You will have to bug them to come up with a new routine. I might take another look at the ADIF format and see if it makes sense to use that.
This has been implemented in version 6.10. The QSO number field is used to show the frequency without the megahertz part. A decimal point is used to make it clear that it isn't a QSO number. Routines will be added to POST to reformat the frequency into different formats for your final log. This technique made implementation much easier as the rest of the log format doesn't change.
2. Editing QSOs beyond the last five: This is one of the prices paid for using an ASCII file. Unless I keep the file in memory and rewrite the whole file after every QSO (which would force me to use a binary file because you can write a binary file much faster), we are going to have to live with it. I still believe that this isn't something you should be doing very often - and you can still exit the program, make your changes and then restart. Perhaps I can reduce the cost of restarting by saving the band map somewhere.
Step 1: The band map is now
being saved when you exit the program (6.10).
Step2 : Version 6.11 loaded this file in when starting (sorry).
3. POST not easy to use: Concerning POST - occasionally I put effort into making POST an easier to use tool. Perhaps I will do this again sometime soon, but please understand it is a secondary priority compared to TR. Another way of saying that is my primary focus will always be what happens during the contest. POST will not be competitive with other after the contest programs in areas of QSL Labels and record keeping. The minimal features in these areas will be supported, but not expanded.
The INSTALL program comes after POST!
Currently the following things are being looked at with respect to post:
4. Time stamp of packet spots that are displayed as they come in.
5. Get split frequency data from radio - TR needs some work to learn how to ask the various radios for the QSX frequency and if you are in the split mode. This is likely to be supported initially in the Kenwood radios first (since I have them and can test it) and then the radios that have the best documentation. Split info needs to be added to the band map as well.
Done.
6. QSX support for packet (both receiving and sending) - decode QSX from packet spots - put into packet memory and band map, send QSX info when doing a spot - allow the spot to be edited before it goes out.
Done.
7. Highlight band map entries that are multipliers.
This is still under investigation.
8. Improve POST support for VHF contests - many of the procedures only work for HF.
9. Better IOTA support (G3KMA request).
10. Look at VK/ZL contest to see if I can improve scoring - request from VK5GN. Separate SSB/CW weekends - RST + serial number (3 digits). Multiplier Oceania prefixes if outside of Oceania - in Oceania: all prefixes except own country. QSO points - 80m - 10 pts, 40m = 5, 20m = 1, 15m = 2, 10m = 3. Multiplier by band.
11. Try to understand why the IC737 split works different than others - IC781 works, but the 737 is different. Problem reported by AJ5M.
vfo A active (listening) on 7.050
Pressed - and entered 7240
Vfo B became active (listening) at 7.240
Vfo A was at 7.050 but now is xmit vfo
12. Fix band map being rewritten twice under some circumstances - takes up time on slow computers.
Done in version 6.10.
13. Improve frequency memory and allow user configurability - LU6BEG request and also VHF considerations - also there might be a bug here to fix as I am not sure the memory is working all of the time.
Done in version 6.10. The frequency memory works again (if you enable it) and you can specify the default frequencies used when you QSY to a band. So you can specify 7060 as the default when you QSY to 40 SSB.
14. ARCI scoring improvements (maybe too hard) - 5 pts per QSO minimum?
15. Show dates of CTY.DAT files when asking if you want to overwrite - this is in install program.
16. Show time of last QSO on bands/modes - to help you decide if you can change bands if you have a ten minute rule to worry about. Also look at counting band changes since the new hour started (for ARRL DX multi-single).
17. Execute LOGCFG.DAT type files while contest running - maybe also allow them to be scheduled. Add commands for clearing dupesheet - transfer DVP files - ???.
Done in version 6.10. The Control-V command (which was duplicated by the INSERT key) will now do this.
17A. Allow all changes recently made using the Control-J command to be written to a file which can be executed with the Control-V command.
This is done in version 6.10. When you use the Alt-G command in Control-J (save all changes made), you will be asked what filename you want to save the changes to. If you enter nothing, it will append the changes to the LOGCFG.DAT file like before. If you enter a filename, the changes are appended to that file. You can then run those changes again with the Control-V command.
17B. Add commands to LOGCFG.DAT to move files around.
Done.
17C. Add command to LOGCFG.DAT to allow the dupesheet to be cleared.
Done in version 6.10. The command is CLEAR DUPESHEET = TRUE and will only function if you are running the file with the Control-V command.
17D. Add ability to execute specific config file via function key memory command.
Done in version 6.10, the CW command is EXECUTE=filename.
18. Jump into S&P mode if VFO tuned - similar to two radio jump feature. This should be pretty straightforward. Will add a flag to the control-J menu to disable/enable the feature. The default will be FALSE (off).
Done in version 6.10. Jumps if you tune 1 kHz or more in a second.
20. Band map saved to a file (separate from RESTART.BIN).
Done in version 6.10. The file is called bandmap.bin.
21. Simple keystroke to get to end of log with Control-L.
Doesn't the END key do this? Or were we looking for something to execute the Control-L command AND put you at the end of the log with only one keystroke?
22. More multi-multi stuff (long list):
23. Control-down arrow to access band map?
I didn't understand why this was different than using Control-PageDn to get to the band map. I am told it is because Control-PageDown is hard to hit with only one hand. I will investigate this.
Control DownArrow doesn't generate a keystroke - so this is on hold until I figure out if there is a better key - or a different way to detect it.
24. FT736 rig interface - after looking into this, this radio does not lend itself to a computer interface. It is impossible to ask the radio for frequency or mode information. Therefore, this feature will not be implemented.
Ignore.
25. Abbreviated frequency input (036 goes to 7036 if you are on 40).
Done in version 6.10.
26. Allow footswitch to act like start sending now key.
Done in version 6.10.
27. Pseudo RIT using two VFOs (LU6BEG request) - feasibility needs to be studied.
28. VHF dupesheets (ongoing things to do with POST to make it work for VHF contests).
Done in version 6.10.
29. Way to disable automated messages which get sent in response to non function keys. This would allow non experienced (or CT challenged) users to use the program with a minimum of frustration. This should be fairly easy to implement and will be included in the next release.
Done in version 6.10. I think this will be a very useful feature for some people.
30. Move Grid map center with mouse?
A mouse isn't powerful enough to move your grid. Perhaps a Moose?
31. Key to restart simulator without having to restart program. The simulator will stop if any key is pressed. This would allow it to be started up again without having to exit the program and restart.
Done in version 6.10. Type DEBUG in the call window and hit RETURN.
32. Allow Control-Enter to be mapped to a function key (and footswitch?).
Done in version 6.10. Actually, it was already there for the function key command - it just wasn't documented. Added to footswitch.
33. Check column dupesheet enable - is it broken?
Done in version 6.10. It was broken (sometimes - depended on how memory came up). Also fixed a problem where the last callsign might be out of order.
34. Allow TAB to move to next word instead of next field when editing past QSOs - make configurable.
Done in version 6.10. The new parameter TAB MODE can either be NORMAL or CONTROLF. When CONTROLF, the tab key will work the same as the ControlF key does now (move to start of next word).
35. DVP files not being saved in local directory when exiting program? Some clean up needed here.
Done.
36. Noticed something unusual in IARU this weekend - was trying to make use of the two radios,(1000D and 1000mp) both interfaced so just toggling between them with Alt R. Pressing Alt M would toggle the mode and VFO but each time that was done, the cw freq came up 1 khz and the SSB went down 1 khz. Did this on the 'MP (didn't check it on the 'D) using v6.05. Something strange going on with my set up or ???? - VE6JY
37. I also noted the 10m band map showed the info for other bands as well, which someone had commented on earlier. - VE6JY/SM0TXT.
Done in version 6.10.
38. I would see three options: Bandmap only, Bandmap/dupesheet, dupesheet only. When I currently use both together, it gets a little overwhelming. I believe that the bandmap info could be contained within an expanded dupesheet. I don't care where the information flashes, as long as I know who I'm tuning up on. Also, I'd like to see unworked bandmapped signals appear in a separate column that the cursor would go to first, as they would represent the frequencies I'd like to seize. There in on reason to cursor up and down a list of stations already worked! Dupes and bandmapped dupes in the first X columns, unworked bandmapped stations in the far right column. The Control PgDn (or Cntl Down Arrow) always goes to this column first. - KB8N.
39. IARU HF initial CQ exchange using CQ ZONE, not ITU zone.
Done in version 6.10.
40. It would be nice to be able to enter 14026.3 either with decimal or just as 140263. Way to enter frequency in tenths of hertz - K3WW.
Done in version 6.10. This was working with QSX split entering, but hadn't been included when you type a frequency in the call window. You can enter hundredths or tenths - so 14026.35 will work.
41. Scoring difference between the program and summary sheet for POST. my question has to do with hw the sw scores......the log window says 640K and the summary sheet says 650K.
This issue was created because of some edits made to the log. No plans to do anything more about it.
42. Explain in manual that carriage return is used to change Control-J parameters (isn't that on the screen?).
Done in version 6.10. The help information when executing the Control-J command has been extended to two lines and is much more useful. It mentions that ENTER is used to modify the highlighted entry.
43. We also had this problem with the HQ stations. Several would return the same string of junk from the exchange memory.
44. Why oh 'great ones' do you have 3 lines shown if IN SSB mode, and FOUR lines if you do an ALT-M and go to CW mode ????? - AA4NU.
CW is more important than SSB. Did this happen because there were no QSOs on SSB, but there were some on CW? The display will show either the active totals, or those on other modes if there is a non zero value to show.
45. In last European VHF contest, I met another strange thing: when I worked (say) OK1MEQ, (in CQ mode), TR accepted only first four characters (OK1ME) and then sent exchange. The same thing happened with almost any another OK (Chech Republic) calls: OK2UAS/P were logged as OK2UA, etc. There were short, but noticeable delay after 4th character and following exchange. And, that happens *only* with OK calls (another ones were all ok, no matter how long the call were), so there couldn't be any relation with the database size (that happens *only* with calls still existing in the database). After I increased SCP Min. Letters to 4, anything worked smooth! - S57AD
46. Before I went to SV, I complained something about problems with Icom radios support - radio didn't followed commands from PC. After I returned home, I got back one of interfaces I build, with short note 'It doesn't work!'. After I connected it to PC and IC-751A, I found that radio actually follows commands from PC, but program doesn't read frequency, unless Icom Command Pause is increased to 300 and Response Time-out to somewhere around 500. It seems Icom requires 'fine tuning' case by case - IC-756 and IC-775 (with baud rate 4800) requires different settings than old IC-751A or IC-735. - S57AD.
Done in version 6.10. The default times have been changed to these values.
47. Improve frequency adder for multiple bands?
48. Field Day summary sheet and dupesheet format change needed?
49. Use sheet of labels for QSL labels - K8BK. (Please refer to item #3).
50. NZART not working for IARU test? - WH6CQH (wh6cqh@interpac.net)
51. [ (wait for strength) not working? - K8KFJ (k8kfj@aol.com)
Fixed.
52. Display last QTC sent - kd4d@radix.net
53. Turn on/off bandmap (and VGA mode) with program running (aa0cy@robertwanderer.gardnerville.nv.us)
This turns out to be "too hard" for the benefit. It would require repainting the whole screen, something that would require a great deal of work and potential for new bugs.
54. Table to show time QSO made on each band/mode.- LU6BEG
55. Show run/mult status as 160 80 40 MULT *7* 10. So you can see that there's 7 min left to be able to QSY from 15m AND you can QSY to any band but 20m - LU6BEG.
56. When I use DVP the menu "CQ MENU" is not displayed - in SSB mode only. When you erase RESTART.BIN, for the first time the "CQ MENU" is displayed, but after change to S&P mode and back, it is not displayed again. - OK1FUA
Fixed in version 6.10.
57. When FOOT SWITCH MODE = NORMAL, CW port is not keying. - OK1FUA.
Fixed in version 6.10.
58. When the path of DVP is set (for example to E:\) and AUTO BACKUP = TRUE, than Alt-6 .. Alt-0 saves only one file at the same QSO (the last) - for example not 123.BCP, 123A.BCP, 123B.BCP... but only 123.BCP. When DVP PATH is not set, this function works corrently.- OK1FUA.
Done.
59. Next tips for WAE Contest: When I need to edit QTCs (before saving), it is not easy: * There is difficult to move to right column (only by rows or tab through some "fields") * The keys "Delete" and "Insert" does not function There would be good a possibility to change sending texts specialized for WAE (exchange QTCs and so on). There is nowhere shown, if the station written in Call Window is EU or DX (after dupe check), until log QSO. - OK1FUA
60. Way to turn off CW with one keystroke until repeated. - SM0TXT.
Done in version 6.10. Several new function key commands do this. One will turn the CW off (using the CW ENABLE parameter), another will turn it on, and a third one will toggle it (on to off, off to on).
61. When I don't want to send a QTC series I type <esc> and it sends QTC anyway... - LU6BEG.
62. Would it be possible to add an "extra protocol" to the multi port so that we could connect a regular packet modem to it, and let the computers talk via radio? It can be don today, providing that short range modems with radio ports are used, but they are expensive. Packet modems are cheaper but they require a proper syntax. - SM3OJR
63. Access DVK in FT-920 (can it be done?) - Bob kf9yh@qsl.net.
I have not been able to get an answer from Yaesu about this. I don't believe it can be done - but if someone knows more, I would like to hear from them.
64. Verify TRMASTER.DTA for errors when program starts up.
65. - POST thinks JIDX uses ITU zones instead of prefectures. - vr2bg@pop.asiaonline.net
66. - Support the German Contest WAG (worked all Germany). Rules at http://www.systemtechnik.tu-ilmenau.de/HAMINFO/contest/wag_1995.- Kurt - DF3HU Simon63@Ibm.Net
67. Change Icom response delay default to 350 milliseconds (required by the 781).
Done in version 6.10. See item #46.
68. Example 1: AD5H is in TRMASTER.DTA, with
only his state, WI. As soon as I enter ad5h in the call window,
WI appears in the exchange window, but the mult needed window
still shows "mult needs for ad5h." If I move the cursor
in the exchange window, the mult needed window properly updates
to show "mult needs for WI." Example 2: AG9A is in
TRMASTER.DTA, along with his name and state, MARK, IL. As soon as
I enter ag9a in the call window, MARK IL appears in the exchange
window, and the mult needed window still shows "mult needs
for ag9a." Now when I move the cursor in the exchange
window, the mult needed window updates to MASSACHUSETTS, because
Mark begins with the letters MA. The same thing happens with any
other name that looks like a state; Mike, Scott, Mitch, Larry,
Moe (but not Shemp and Curly), Carl, etc.
I guess my suggestion would be to have the mult needed window
update without having to move the cursor, and of course to update
on the state, rather than the name. - k6ll@juno.com.
69. Switching radios without Alt-R - because of tuning? Even with TWO RADIO MODE = FALSE? - Mike KB5YVT@aol.com .
Fixed in version 6.10.
70. Updated trmaster.dta file with the names from the NAQP log and had no problem. However, when I ran the program again to update the QTH data, the program freezes at the line, "updating xxxx" and I then need to warm boot. Nothing will get the program to update the file for QTH. The call which freezes is always the last call in the log. I reduced the log to 10 contacts to see if that would do anything and again the last call in the mini-log freezes upon the updating bulletin. Hope this helps in your work to debug TR and POST. If you have any ideas regarding updating my trmaster.dta with QTH data, please let me know since I find it very helpful during the contests. - Mike N1MD@snet.net
71. Example of ADIF output:
Exported using TR Version 6.05, conforming to
ADIF specification 1.0<eoh>
<call:4>NB6G<freq:6>28.000<mode:2>CW<qso_date:8>19911102<time_on:4>2101<comment:30>2
B NB6G 57 SV <eor>
<call:4>KW4E<freq:5>7.000<mode:2>CW<qso_date:8>19911102<time_on:4>2102<comment:30>2
A KW4E 64 NNJ <eor>
<call:6>WA3INC<freq:5>7.000<mode:2>CW<qso_date:8>19911102<time_on:4>2102<comment:30>2
Q WA3INC 67 ENY <eor>
72. two or three times I experienced a minor keying problem---if pushing return to send an exchange or QSL message (CQ or S&P didn't seem to matter) at the same time as packet was receiving, keying went into a mode of continuous keydown. Solution was ESC (or ESC, ESC) and start Q over. Only happened two or three times in 4.5 hours, but it was unnerving. Anybody else see anything like this? TS940S, Radio Control Port 1 (4800 baud), Packet Port 2 (1200 baud), Keying LPT1 (usually 25 to 28 WPM), Paddle Port LPT1 connected but not used. 386/387 33MHz machine.- Bill, W1HIJ, new_century@earthlink.net
I believe this was fixed in 6.15.
73. I just finished using 6.05 for the 10-10 QSO party. It is the first time I really used Auto CQ with my W9XT card. Is there a way for TR to see me keying the transmitter and stop sending CQ rather then having to hit ESC? - Dave N9SSG - n9ssg@pobox.com (Perhaps this can be done if the footswtich input is used on the parallel port - N6TR).
74. I have been having trouble generating the multiplier list. It seems to format it OK but it will only print about half the list. Also, POST R has two L menu entries. (in All Asian) - John N6MU N6MU1@aol.com
75. In POST, having more than 256 QSO points per page gives incorrect page totals. Dave, K1HT dave_hoaglin@abtassoc.com
Fixed in version 6.10.
76. I can consistently freeze TR by restarting the program with a TOTAL SCORE MESSAGE set to display at a value less than the total score of the current log.dat. The program will stop with the appropriate message on the screen and that is it...no key stroke gets it further. - Ron KK1L (ex N1PBT) rrossi@btv.ibm.com
I have not been able to reproduce this problem. The program does stop for 2 seconds when displaying the TOTAL SCORE MESSAGE, but then it continues. What version was this?
I noticed item #76 on the wish list is mine and you commented on it. I agree that it does not fail for this anymore. I don't know what version I tried it with, but it was the week following this past NAQP phone. So I rebuilt a directory with 6.05, 6.10, and 6.11...it did not fail. It must have been something else I was doing! I refused to believe I was not patient enough to wait the 2 seconds the message spends displayed =:-)
This issue is considered closed.
77. Option to show total QSOs in last 60 minutes - W7YAQ norin@ideal.jf.intel.com
Done. Use HOUR DISPLAY parameter.
78. Change Auto-CQ feature to stop a CQ if callsign entered while a CQ is in progress. aa0cy@contesting.com
Done in version 6.10. Pressing a key will stop the CW in progress. This was actually a very good idea - not sure why I didn't do it like this the first time.
79. WAE QTCs with multiple computers? igor@sokol.pssr.e-burg.su
80. Transmit lockout option when using multiple computers in multi-single? igor@sokol.pssr.e-burg.su
81. Way to do RIT for radios that don't support increments. When I use the RIT via the computer, I would only want to use the computer, i.e, I really would not use the actual control. Since the RIT can be set, but not increased, what about using each press of the shift key to change the RIT a set frequency. In other words, the program keeps a counter incremented by the right key, and decremented by the left key. If the right shift key has been hit 5 times, that would be (5*<selected granularity>). If the user then hits the left shift key, the offset would be (4*<selected granularity>). Periodically during the polling cycle (perhaps every 5 radio polls), the radio could interrogate the RIT and make any corrections to the counter. I guess for total control the granualarity would have to be small enough to match the resolution of the RIT offset read back, so if the granularity was .1 hz (or whatever) each step would adjust that much. Tom NY4I ny4i@hotmail.com
82. CQ EXCHANGE not working with DVK (a bug). w0mu@sprynet.com
Fixed in version 6.10.
83. Possible prefix key to allow name to be entered in any place of a name and QTH exchange (i.e., '). KK1L rrossi@btv.ibm.com
84. Set DISPLAY MODE = MONO & portions of the screen are still written in color if one is using a VGA card - such as the bandmap, SCP window dupes, possible calls, etc. Unfortunately, there are no colors to set in MONO mode, so you can imagine what this can look like with a monochrome VGA monitor. Brett vr2bg@pop.asiaonline.net
85. Improve POST's documentation in the manual. N1RUI n1rui@together.net
86. Is is necessary to have 10 QSOs to RECEIVE QTCs? sm3ojr@pobox.com
87. QTC function missing in manual (there used to be a section on it). WD9GGY thehalls@ix.netcom.com
88. Found a small bug using multi that I thought I might post. If you update your TRMASTER.DTA on one computer make sure you move that updated file to the other computers. If you don't and are using INITIAL EXCHANGE = XXX, computer 2 will crash when you enter a callsign that is in the DTA file. Mike K5NZ K5NZ@aol.com
This sounds unbelivable at first - investigation to follow.
89. I have now noticed in more than 1 log, from more than one pc, that (it seems like) the first OK station logged is actually logged in the LOG.DAT as an oK (small o big K). Where the contest had mults that qso was not creditted as a mult. For sure this happened in G5LPs CQ WPX log and our MW7Z IOTA log. Fred Fred.Handscombe@europe.simoco.com
90. TRLog worked great in the ARI contest this weekend using the ari.dom file that I had generated. However, there is one (at least) error in the file that I emailed you. That file had two entries for BI and should have one for BI and the next one for BL. You mentioned that you might want to include this file in the next release of TRLog, so I thought you would like to make the correction. John W4AU junger@usgs.gov
This is pretty old - but I wasn't sure I had addressed it yet, so it is on here.
I don't seem to have a copy of the ARI.DOM file, therefore there is nothing for me to fix! If you provide it, I will include it with the program.
91. Separate speed control for the paddle? LU6BEG lu6beg@canopus.com.ar
Is it just me, or is the paddle already sending a little slower than the program?
92. In CQWW and IARU contests, TR checks zone in TRMASTER database first, and if it is not found there, it checks zone in CTY.DAT file. How to add same feature for QTF (beam headings)? Headings are calculated from grid statement, so it would be possible to check database first for grid, and when grid is not found, then QTF could be calculated from datas in CTY.DAT file. Beam heading accuracy is no vy important on SW (or even in USA V.UHF contests), but is very important in European VHF contests. For example - for us in S5, I stations are spreaded from 120 to 270 dgs, and DLs from 330 to 10 dgs, etc. (BTW, I put more than 13000 grids in my TRMASTER database and made it available to all registered TR users in Slovenia)... S57AD s57ad@s55tcp.ampr.org
93. TR still doesn`t send greetings to portable stations. s57ad@s55tcp.ampr.org
Fixed. This was addressed several releases ago.
94. In simulator mode sometimes come back stations with double slash (/) in the callsign, say OZ/DH8AAF/P. I type in the call and send my exchange, but simulator comes back with something like "pse correct my call - my call is OZ/DH8AAF/" (without "P"). (And, of course, there doesn`t exists "OZ/DH8AAF/" call in the database)...s57ad@s55tcp.ampr.org
This is pretty old - but I wasn't sure I had addressed it yet, so it is on here.
95. There are some names, longer than 8 chars, in the database, i.e. Sebastian. TR sends name correctly, but name is not displayed on the screen, or there are displayed only few chars of it, i.e. "TIA"... Suppose that name field on the screen is a bit short for such long names, :-)
Fixed in version 6.10. The name window has been increased in size by 2 characters.
96. SAC scoring Do you think you could make the program "fool proof" for us Scandinavians? We are not allowed to QSO other Scandinavian stations, but the program still hands out points and mults if I work one by mistake. - sm3ojr@pobox.com
97. Add sunrise/sunset times.
98. Add split information to bandmap.
Done.
99. Make packet spots split aware - receive.
Done.
100. Make packet spots split aware - transmit.
Done. Manual entry - but easy.
101. Show number of dupe QSOs.
102. Use sound card for simulator.
103. Does control-dash (dualing CQ) tell you what is going on via the prompt window?
104. Option to send complete 4 letter call if only one letter changed (when using the } character).
105. Update dupesheet if corrected call in editable window.
Fixed. This has been working for awhile now.
106. When you are interlinked with the other bands, the QSO totals are different. The band you are operating counts dupes in the total, but does not count dupes from other bands. Therefore each total contains the dupes from that band, and all the bands have different totals.
107. Use sequenced numbers when POST does anything to log files - instead of just the logback.dat which only goes back one level.
Done.
108. Allow specification of I/O port address for the various com ports. Bill, K5ZQ, wosborne@utdallas.edu.
Done. Created COM5 and COM6 for which you can specify any I/O address.
109. During a couple of recent contests I have worked AA3B. When I go to POST to generate a dupesheet, his call is listed 1st of course, but it's always listed *twice*. Any ideas why this should occur? The attached file is an example of this from the Sept. 7th Sprint. K8KFJ@aol.com
110. I had a p43p call and want to know if there would be a way to start messages DRU messages in his TS-870s - it has some sort of DVK in it (like the ts-850 option) and he has a laptop (no more room) and wants a way to fire the messages with the F-Keys.
The 870 does allow this to happen. It is not supported on the 850 or 950 however. This will probably be added in the next release.
111. For some contests like SS, TR is able to parse the exchange line including possible callsign changes, so it is really easy to make corrections without hitting those awful keys by just retyping the field that needs correcting. For other contests where TR cannot figure out whether TEX is a name or qth, I now have to resort to the awful keys. One solution for me would be the inclusion of a vi editor mode for editing fields; I doubt if Tree will include that. However, another possibility could be something like typing q=tex or n=tex to indicate what the correction is for. That is if the exchange is name qth, you could type tom ok n=tex --- which would change the name from tom to tex tom ok q=tex --- which would change the qth from ok to tex q=ok n=tex --- which would let you enter the fields out of order. - Kevin w9cf@ptolemy.la.asu.edu
112. Sometimes I log a contact and see immediately that I have typed the wrong info. I find editing the 5 line log clumsy. Solutions are: a. I could learn how to use the current editing commands better (unlikely to happen) b. Tree could change to vi editing commands (even less likely to happen) c. Have a keystroke that would overwrite the last log entry keeping the correct time and not send cw/dvp. That is if I have logged something incorrectly for the last qso, I hit the relog key and then type in the call and exchange just as if I were making the QSO again. I realize that I can delete the last QSO, turn off cw, relog it, and turn on cw, now, but that's as hard as editing the log and if I do that, when I delete the entry, the information dissappears from the log window, so I can't read the good stuff off the log line, and the new time shown is slightly wrong. Kevin w9cf@ptolemy.la.asu.edu
113. Really nice feature that NO one has would be to have a little scratch memory that when you grab a spot you can toggel back and forth...CQ CQ on run freq hit a key and be on spot freq with call there ..try to work him...zippo toggel back to run freq and cq cq cq bounce back and forth without much problem...could even leave a call in the RUN window possibly. Not much different than your dualing CQs but on one radio not 2. Maybe could do that already with proper setup of 2 radios actually being the same...HUMMM Ill investigate that see if can put same radio on same port as A and B ???? I think you have the scratch memory or whatever to keep info from 2 radios..so maybe 2 memories as well..Ill bet the A/B vfo will screw that up. k3ww@pop.fast.net
114. The band map is cluttered. if it worked perfect the CT scrolling method is very nice...but the perfect compromise between the Alt U for packet and the band map for band mapping would be to merge them.. then have OPTIONS...QUICK EASY TO SWITCH OPTIONS>
1. Full band map everything you worked, everything Packet spotted, everything you manually entered with the space bar...pretty well what it is now. (an hour may be a bit fast..Europeans set in one spot all day just like we East coast guys do). The color aging is a nice touch.
2. MULTS NEEDED ONLY quickly turn off the other stuff and you can mouse or toggel form one mult to the next with a quick sweep of a band. (both packet spots and stuff you couldnt bust the pileup on would show up in this mode)
3. NEEDED QSOs Just needed QSOS Mults or not but not the worked stuff. This would provide a less cluttered band map for the quick spin across the band. TRULY slick would be for the ALREADY WORKED guys that are not visible to pop up when you stop on their freq, just like they do now.
A little flag showing BANDS I'M NOT ON that have MULTS I NEED in their band maps.
Of course we want to remember this when we reboot. k3ww@pop.fast.net
115. I would like a way to designate somewhere which VHF+ bands I have equipment for. So, as I switch between bands, the only choices I would have are those bands I have for which I have equipment (so I'm not constantly stepping over 222 all the time because I don't have it, for instance.) It might be nice, also, to designate the modes by band for this, so that if you have a transverter setup on, say, 903MHz, that only does USB and CW, those would be the only mode choices you have on that band. KM5FA kharker@cs.utexas.edu
116. Lacks support for ARRL UHF contest. Specific differences from the ARRL VHF QSO Parties are that only 222MHz and up QSOs are allowed for points, and the base QSO points for different bands are higher than the base QSO points for the same bands in the VHF QSO Parties (i.e. in the VHF QSO Party, the base QSO points for 70cm is 2, whereas in the UHF contest 70cm base QSO points are. KM5FA kharker@cs.utexas.edu
117. Finally, your generated Summary Sheet lacks indication of the operator's ARRL section. I got a letter from the ARRL contest coordinator because I failed to notice this. KM5FA kharker@cs.utexas.edu
118. Re #14: ARCI 'tests exchange are: RST, State/Province/Country, and string (either all numbers, which would be ARCI member number, worth 5 points (e.g. 691) - or number(s) plus "W" (e.g. 100W or 5W) which would be power output and worth 2 points). If there is some way to recognize the presence of the "W" as a clue for scoring, that would seem to be the way to go. W6ZH w6zh@ix.netcom.com
119. Last time I tried it, the software would accept Y and Z in the last two letters of the grid locator - these are not valid locators. Andy cookar2@btlip16.bt.co.uk
Done.
120. How about an output to run antenna switches? Pull down a pin on the printer port for each band. (HF) Example: (Defaults) 160 = pin (X) 80 = pin (X+1) 40 = pin (X+2). KU7Y ku7y@sage.dri.edu
121. Way to use packet link with network. OK2FD ok2fd@contesting.com.
This is the same as item #62.
122. OK2BUG reported a bug in ARI Contest counting points. Please look on that, all I/IS/IT stations should be counted for 10 points, multipliers are countries and Italian provinces, etc. For stations outside Italy, of course. OK2FD ok2fd@contesting.com
123. VHF REMEMBRANCE DAY CONTEST...There is another very popular contest down under also....Its called the JOHN MOYLE contest...VHF,UHF with 3hours between reworking. I will send a bit more info soon. When you have the RD contest (vhf-uhf) stuff sorted out I will furnish you with my VISA card Number so we can get things rolling along....Also, the W9XT card you mention....Tell me more about that also.....Curciut diagrams ETC maybe?...I can get PCB's made here if need be...I guess its up to you people in the States... John vk5po@sugarland.ampr.org
124.Hows things in respect to the 120minutes between qso's? John vk5po@sugarland.ampr.org
125. The thing is that we have a Contest in Spain called CONCURSO NACIONAL DE TELEGRAFIA, and we do the multipliers as the provinces of Spain and the districts. I have always done this contest with the " SP DX" option of your program, and when it has finished I just check for the right districts or provinces that not appear as multipliers. So the question is if it could be possible to run some "prearranged contest" in the TR that I can configurate with only the Spanish provinces and districts as multipliers ? The contest take place the last weekend of this month of September, if you think we can do anything, it would be of great help for me, TNX! 73 de Josep EA6ACC Replays to: Josep. EA6ACC Mailto: eb6aok@jet.es.
126. How about making the time/diff a variable controllable from the logcfg? I know this may be taking it to extremes, but it sure seems like I went more than 1khz in a second many times with no change. Maybe the polling update or increasing my data rate (am at 1200 presently) would help?? Tom k1ky@bellsouth.net.
127. I worked N6ZZ on 20 and then again on 40. For the first QSO my log has PHIL Tx, but for the second it has KEN Ca! I'm sure I copied Phil's exchange and logged it correctly, and I had Exchange Memory turned on, so I'm baffled at this. Dave K1HT dave_hoaglin@abtassoc.com.
128. I worked KP3L on 40. At that point (0213Z) his signal was weak here (having my beam pointing west didn't help), and I had to ask for a couple of repeats to make sure I had his exchange (LU PR). My LOG.DAT file says LU Nc with KP4 in the Mults column! Any idea about how the program could take PR from the Exchange Window, put KP4 in the Mults column, and put Nc in the Qth column? BTW, I was using 6.05. I had a very busy week, so I decided not to install 6.10 and tackle some of the new features that should be useful for the Sprint. Dave K1HT dave_hoaglin@abtassoc.com
129. Allow serial port I/O address to be selected instead of port number.
Done.
130. I had the relay control port set to "none". It still changes state whenever I transmit. When I set the relay control port to "1" (LPT1) then it will stay with whatever radio 1 or 2 that is selected with ALT R command. I don't need it to switch when it should be disabled. Does it normally switch when transmitting using a one radio setup ?? This is not a big problem (I could always disable the switching). Any additional thoughts ?? I have the ckt bd layout completed but wanted to test some of the port things before I commit to copper ! I did some more investigation this A.M. and found the following. When radio #1 is selected pin 14 goes high, and strobe goes low whentransmitting. When radio #2 is selected pin 14 goes low, and strobe stays low when transmitting. Is there any way the program could be configured for radio #1 low and radio #2 high on pin 14 ? The strobe could be set low for each radio. This would let the radio 1/2 relay be de-energized when radio 1 was active, and energized when radio 2 was selected. Thanks, Jerry, KE9I jend@midway.uchicago.edu
131. One thing you might want to put on your wish list is a little indicator which will let you know when you are recording a CQ or exchange, and also a indicator that tells you a message is playing. These would be good to use for SSB tests (yuck) but would be very helpfull. Wouldn't matter at the start of the contest but after battling pig farmers for hours at a time even the best ops can get a little punchy ! And yes we have the pig farmers report here nightly on 1.830 (sometimes AM) and on the weekend mornings at 1.815 ! Hey good for DX ! 73, CUL Jerry, KE9I jend@midway.uchicago.edu
132. What keys do I use to go to grab a new Dxspot that has just came in and back to the original freq quickly ? G0SAH G0SAH@aol.com
133. Got the xt version of 6.10 Thanks very much everything is fine except that control J does not edit the logcfg but just acts like the cr key (sounds familiar ;-) The other control and alt keys seem to be fine. Version 5.50 worked fine. VE7CQK paul1@wizard.ucs.sfu.ca
134. I have tried to import one of the trmaster files that are available for download. I would like to import this data without changing the hits count in my trmaster. Even if I set the hits update flag to false the hits count still increments. Am I doing someting wrong, or is this "a feature". Leon ni2p@panix.com
135. > One problem that still hasn't been fixed (despite my whining): > > Shifting between radio's with Alt-R does not return you to the previous mode > (CQ vs. S&P). Very annoying. N2IC smlondon@lucent.com
136. When I'm operating split, I put a call in the call window, enter it into the band map and call, leaving the cursor in the call window. The call disappears during xmit, and does not come back even though the band map entry is flashing. Yes, I know if I hit enter and call I'm OK, but I don't do that all the time in SSB. Is this what you planned to happen? K5YA dmowers@texanet.net
137. Why not use SHIFT/TAB as a universal toggle to switch between modes no matter what has been entered where and when. Then when the ENTER key is pressed the proper S&P or CQ message will be sent for the field the cursor in. A coding nightmare? Lou ljp@mcs.com
138. The TAIL END KEY when pressed will log the contact, send the TAIL END MESSAGE and send call characters as you enter them. This would normally be used if someone tailends and you want to come back to him without sending a QSL message. So - Yes you are correct the appendix has the sequence of what happens a bit out of order - we will fix that in the next manual.
139. Here's something for the very bottom of the list...In the call and exchange windows the delete key only works when insert is active. If overwrite is enabled the delete key only deletes the character it is over, but not the space. KK1L rrossi@btv.ibm.com
140. I ran the Check log file size parameter over the weekend with a 286 (yeah, I know I'm gonna get a better computer before nextcontest season - for sure)...It seemed like the check log message appeared several times even though the log was o.k. The message seemed to appear after I had entered a number of notes using the Ctrl-N key. Does the parm just take the number of QSO's and multiply by the record length to determine the "check size" to compare (without taking notes into account)? Eric Hall ERIC.HALL@gecapital.com
141. Also, with the 1000MP, the mode stayed CW all the time but the sideband would change sometimes when I cameback from the other radio. That one is kinda hard to notice! ku7y@sage.dri.edu (Monte Stark)
142. S&P vs RUN. I like the little mark but it would be nice if I didn't have to put it into Excel to work with the data. >t would be nice for Post to tell you how many were which and the % of each. ku7y@sage.dri.edu (Monte Stark)
143. Look for the 1 kHz change over a longer period of time. K9MA sdelling@facstaff.wisc.edu
144. If you just type in 9A50CT, the program parses it just fine. It's only when the 50CT comes in from the database that it hiccups. The info is already available to the program that the 50CT is a check and section, you would think that parsing it in this case would be easy money. K6LL k6ll@juno.com
145. Quite a few of the packet spots came in and were displayed in the band map without an asterisk when in fact they were dupes. Made me look like the fool several times when calling dupes. Chad kurscj@oampc12.csg.mot.com
146. How come ALT-I doesn't ever work? Didn't work for CQP, didn't work for SS. I know that some contests would be hard to impliment (like SS), but for CQP it should have been pretty easy. I think it's been broken for a long time now. Also, I would think that it should work for SS too. (Yeah, I know you big guns don't ever get beat out so you don't have to worry about ALT-I. But with our tiny 24 element array on 15M, we have to wait a long time so I'd find ALT-I useful.) Chad kurscj@oampc12.csg.mot.com
147. Out of consistancy and to save having to learn and remember another keystroke combination, it would be nice if Shift-Tab also changed from CQ mode to S&P mode, with call window contents left intact. That would make Shift-Tab a mode toggle, rather than a one-way thing. Tab and Esc could be left as-is. ae2t@bigfoot.com
148. Add adjustment to the rate that QSY and RIT commands are issued.
149. Reverse order of mode and frequency commands to Yaesu FT1000MP. ve6jy@freenet.edmonton.ab.ca
150. Way to have RESTART.BIN be ignored if the contest name changes.
151. Add check multi port to more keystroke loops (Control-J, Alt-P).
152. Check check log file size - needs more room?
153. FT1000MP in wrong USB/LSB in CW mode when doing two radios?
154. Auto non-insert mode if ? in callwindow. K5NA k5na@bga.com
155. Using 6.12, I found that "00" was accepted as a JA prefecture number & even counted as a mult. Valid prefecture numbers are 01 to 50. vr2bg@pop.asiaonline.net
156. Adjustable length of time for rate calculations. kg5u@hal-pc.org
If there is something you think should be added to this list, please post your request to the trlog reflector or e-mail to tree@contesting.com.