Return Welcome End of page
SK3BG - Sundsvall Radioamateurs - SRA, SWEDEN
Internat. flags

SM3CER Contest Service

 TR Log Wish List  Item # 71 - 156

[ Go to item # 1 - 70 ]

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

New releases are made approximately monthly - or as required to fix critical bugs. Updates are available one of three ways:

  1. E-mail on the internet with a uuencoded .zip file (about 600K). To get on the list contact or in Europe, contact

  2. 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.

  3. 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


71. Example of ADIF output:

Exported using TR Version 6.05, conforming to ADIF specification 1.0<eoh>
<time_on:4>2101<comment:30>2B NB6G 57 SV <eor>
<time_on:4>2102<comment:30>2A KW4E 64 NNJ <eor>
<time_on:4>2102<comment:30>2Q 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,

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,

(Perhaps this can be done if the footswitch 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,

75. In POST, having more than 256 QSO points per page gives incorrect page totals. - Dave, K1HT,

Fixed in version 6.10.

76. I can consitently 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 key stroke gets it further. - Ron, KK1L (ex N1PBT),

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 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,

Done. Use HOUR DISPLAY parameter.

78. Change Auto-CQ feature to stop a CQ if callsign entered while a CQ is in progress.

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?

80. Transmit lockout option when using multiple computers in multi-single?


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

82. CQ EXCHANGE not working with DVK (a bug).

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

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

85. Improve POST’s documentation in the manual. N1RUI

86. Is is necessary to have 10 QSOs to RECEIVE QTCs?

87. QTC function missing in manual (there used to be a section on it). WD9GGY

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

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

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

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

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

93. TR still doesn`t send greetings to portable stations.

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)...

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. -

97. Add sunrise/sunset times.

98. Add split information to bandmap.


99. Make packet spots split aware - receive.


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 a while 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.


108. Allow specification of I/O port address for the various com ports. Bill, K5ZQ,

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.

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

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

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 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 maybe 2 memories as well..Ill bet the A/B vfo will screw that up.

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.

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, 903 MHz, that only does USB and CW, those would be the only mode choices you have on that band. KM5FA

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

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

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

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


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).



121. Way to use packet link with network. OK2FD

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

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

124. Hows things in respect to the 120 minutes between qso's? John

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:

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

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

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

129. Allow serial port I/O address to be selected instead of port number.


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


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

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

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

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

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

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

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

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

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 next contest 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


141. Also, with the 1000MP, the mode stayed CW all the time but the sideband would change sometimes when I came back from the other radio. That one is kinda hard to notice! (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. (Monte Stark)

143. Look for the 1 kHz change over a longer period of time. K9MA

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

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

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

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.

148. Add adjustment to the rate that QSY and RIT commands are issued.

149. Reverse order of mode and frequency commands to Yaesu FT1000MP.

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

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.

156. Adjustable length of time for rate calculations.

[ Go to item # 1 - 70 ]

If there is something you think should be added to this list, please post your request to the trlog reflector or e-mail to


Thoughts about the home pages of SRA? Get in contact with:
Jan-Eric Rehn - SM3CER

Copyright © 1997 Jan-Eric Rehn - SM3CER
This page was created November 4 1997
Most recent revision November 23 1997
Top of page Welcome Return