James, I'll be around tomorrow afternoon .. headed into NYC for some
jazz this evening so will be sleeping in tomorrow :)

I'd be happy to give you an on-the-phone walkthrough (and I'll take
notes and use them for a page on my website), I'll look for updates
tomorrow ..

de w1rt/john

On Fri, Oct 16, 2009 at 3:51 PM, James French <w8iss@...> wrote:
> On Friday 16 October 2009 15:05:34 John D'Ausilio wrote:
>> I'll see if I can make some time to document some of this stuff soon ..
>>
>> distro/wm/fm shouldn't make much difference IMHO
>>
>> de w1rt/john
>>
>> On Fri, Oct 16, 2009 at 2:20 PM, Tom Mayo <tmayo6@...> wrote:
>>
>> >
>> >
>> > In addition to info from Jacob, I intend on becoming more of an expert
>> > on running RoverLog on Linux again. I have migrated completely to
>> > Windows, but I do not want to lose the ability to support Linux users.
>> > This won't be immediate, however, so any help from others will be
>> > appreciated.
>> >
>> > It would be helpful for any successful Linux users to report their
>> > distribution (Debian, Ubuntu, etc.) the window manager they are using
>> > (KDE, Gnome, etc.) the file manager they use to navigate around and see
>> > icons, any additional packages they needed to install (Tcl/Tk, etc.) and
>> > any tweaks they needed to make to be able to double-click on the icons
>> > to run RoverLog (chmod, etc).
>> >
>> > Thanks!
>
> I am just bringing this up as I am totally linux at home and the only windows
that I
> use is at work (begrudgingly). I am basically an enduser that knows a little
and still has
> a LOT to learn under a *nix systems but get by enough to get things working
for what
> I want it to do.
>
> I don't begrudge Windows users as thats still the major player out there and
for 95%
> of everyone that uses computers, that is all they have ever used.
>
> I am going to be installing Roverlog on a few Linux systems locally where I
operate from
> so that others can get used to it. It also helps that I do have a very good
Linux Users
> Group locally < http://www.lugwash.org > that I can go to when I get stumped
for answers.
>
> I will keep the group posted as I get things running.
>
> James W8ISS
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Just installed the newest windows Roverlog running under wine on my
Ubuntu 9.04 system last night and entered my 10GHz cumulative QSO's.
Comments inserted below:

--- In RoverLog@yahoogroups.com, Steve Meuse <smeuse@...> wrote:
>
> Hey Tom, I tried out the new 10g.ini file this weekend, but I think
> I may have found an issue with the score calculation. From the ARRL
> 10g rules page, wrt scoring:
>
> "6.2. QSO points: Count 100 QSO points for each unique call sign
> worked per band. Portable indicators added to a call sign are not
> considered as making the call sign unique."
>
> I think as it stands now it's counting each QSO as a new callsign,
> not *unique* callsigns.
>
> So, for example this week I made 53 Q's with maybe 20 unique calls,
> but the QSO points were 5300 in the scoring summary, when it should
> have been 2000 (or however many unique x100). I can send you my log
> direct if that would be helpful.

I entered all my paper log entrys into the database and kept track of
the scoring. It seems to be working now for the newest version for
proper scoring.

>
> Also, a few other cool things to consider for the "nice to have" list:
>
> - In the calc window, have the option to change to Kilometers vs.
> Miles
> - In the main log window, add a Kilometers column at the end.

I think this would be nice also.

>
> Although the cabrillo format isn't required for this contest, I'm
> trying to interpret the rules to figure out if you need to report
> the Km per contact, or if a total Km is adequate. This is the quote
> from the rules page:
>
> "8.2. Electronic entries must include the required information from
> the ARRL summary sheet (available online) completely filled out and
> a log file indicating band, date, time, call sign, the exchange
> information plus distance of contacts in km. The Cabrillo format is
> not required for the 10 GHz and Up Contest."
>
> I can't tell if they mean distance per QSO or total Kilometers.

The way I interpret the rules is that they want the mean distance in
a seperate column after everything else that is shown on the line in
the file which is what I did with a manual edit before I sent it in.
(Just let me know if anyone wants to look at my log file and I will
send it directly.)

>
> Anyhow, I'm excited to see this capability in RoverLog! Soon I can
> get rid of my paper logging...
> -Steve
>

I am going to have to give this a try just for the fun of it on my
laptop and just go out and make a few contacts to see how well it does
work in the field for me. Right now it looks like it will do what I
need and want it to do even for a fixed station. I just may give up
using xlog during the other contests. That will depend on how well the
networking works also which I haven't had the chance to try yet.

The one thing I can't figure out is how to do a summary sheet yet. I
find it listed in the manual but with a comment about the "OLD" way of
doing things. For this contest, I just downloaded the summary form
from the ARRL and edited it as a text file and attached it with the
log that Roverlog created and that I did a few edits of before submitting. On
this I probably need to just get Roverlog running on my
Ubuntu system outside of wine and that may cure that issue. I still
have a learning curve that dwindles as I use a program more and more.

James W8ISS

PS - Thanks for a great program and the hard work that has gone into it.

I had a nice response to this earlier, but I hit the wrong button when
I attempted to send it to the list..:( I'll try again now.

I had loaded the latest version last night and loaded in my log from
the 10GHz cumulative. Comments follow below:

--- In RoverLog@yahoogroups.com, Steve Meuse <smeuse@...> wrote:
>
> Hey Tom, I tried out the new 10g.ini file this weekend, but I think
> I may have found an issue with the score calculation. From the ARRL
> 10g rules page, wrt scoring:
>
> "6.2. QSO points: Count 100 QSO points for each unique call sign
> worked per band. Portable indicators added to a call sign are not
> considered as making the call sign unique."
>
> I think as it stands now it's counting each QSO as a new callsign,
> not *unique* callsigns.
>
> So, for example this week I made 53 Q's with maybe 20 unique calls,
> but the QSO points were 5300 in the scoring summary, when it should
> have been 2000 (or however many unique x100). I can send you my log
> direct if that would be helpful.

The latest version seems to keep track of things accurately and the
scores added up properly. The one thing I saw was that if I had milage
of 191.4, it rounded down and for a score of 191.7, it rounded up. I
think that anything that comes up as xxx.x should be rounded up to the
next whole amount. But I going to assume that the author of the soft-
ware has a reason for that and probably has all ready talked to the
ARRL about that and has gotten an answer to that question.

This just threw me for a loop last night because things just were not
adding up when comparing the programs totals and my paper logs totals.

>
> Also, a few other cool things to consider for the "nice to have"
> list:
>
> - In the calc window, have the option to change to Kilometers vs.
> Miles
> - In the main log window, add a Kilometers column at the end.
>

That would be nice also even just for info sake ...:)

> Although the cabrillo format isn't required for this contest, I'm
> trying to interpret the rules to figure out if you need to report
> the Km per contact, or if a total Km is adequate. This is the quote
> from the rules page:
>
> "8.2. Electronic entries must include the required information from
> the ARRL summary sheet (available online) completely filled out and
> a log file indicating band, date, time, call sign, the exchange
> information plus distance of contacts in km. The Cabrillo format is
> not required for the 10 GHz and Up Contest."
>
> I can't tell if they mean distance per QSO or total Kilometers.

My interpretation of the rules is that they want to know what the
milage is for each contact and then on the summary sheet a combined
total milage score. I manually went in and edited the xxx.log file and
added a column at the end of each line with the milage added on.

I am having problems with the program creating a summary sheet for me
though. I looked in the manual and found that a few comments about the
'old' style of generating the sheet. The paragraph from the manual:
If "old" rules are selected, a summary file is generated that must be
edited prior to submitting your log. The .sum file is named with the
same root name as the log file.
This is on page 8. But I couldn't find the file and couldn't figure
out how to create it either. I probably just don't have it configured
correctly either. Something that I need to read more about in the man-
ual as I go along. So I just downloaded the summary sheet from the
ARRL website and turned it into a text file and edited it and sent it
in with my log file.

> Anyhow, I'm excited to see this capability in RoverLog! Soon I can
> get rid of my paper logging...
> -Steve
>

I will still rely on paper logs as I have had the expereince last year
asking the stations on the Illinois/Wisconsin side of Lake Michigan to
just start calling CQ towards us so that we could find them on each of
our stations of the group I was with. Well, it did work but it sound-
ed like as if I was listening to a 20m pile up for a rare DX country
or expedition..<L> This year conditions across the lake were much
better. We could even here the Wisconsin/Illinois side with paper
clips as antennas even on 24GHz at the beginning of the day. 24Ghz
then dropped out after those contacts but 10GHz stayed wide open al-
most all of the second weekend.

As for getting to use Roverlog during actual contests conditions, I
won't be able to say anything till next years VHF+ season starts up
again. From what I have seen so far, it just may replace xlog that I
have been using for the past few years.

James W8ISS

On Friday 16 October 2009 15:05:34 John D'Ausilio wrote:
> I'll see if I can make some time to document some of this stuff soon ..
>
> distro/wm/fm shouldn't make much difference IMHO
>
> de w1rt/john
>
> On Fri, Oct 16, 2009 at 2:20 PM, Tom Mayo <tmayo6@...> wrote:
>
> >
> >
> > In addition to info from Jacob, I intend on becoming more of an expert
> > on running RoverLog on Linux again. I have migrated completely to
> > Windows, but I do not want to lose the ability to support Linux users.
> > This won't be immediate, however, so any help from others will be
> > appreciated.
> >
> > It would be helpful for any successful Linux users to report their
> > distribution (Debian, Ubuntu, etc.) the window manager they are using
> > (KDE, Gnome, etc.) the file manager they use to navigate around and see
> > icons, any additional packages they needed to install (Tcl/Tk, etc.) and
> > any tweaks they needed to make to be able to double-click on the icons
> > to run RoverLog (chmod, etc).
> >
> > Thanks!

I am just bringing this up as I am totally linux at home and the only windows
that I
use is at work (begrudgingly). I am basically an enduser that knows a little and
still has
a LOT to learn under a *nix systems but get by enough to get things working for
what
I want it to do.

I don't begrudge Windows users as thats still the major player out there and for
95%
of everyone that uses computers, that is all they have ever used.

I am going to be installing Roverlog on a few Linux systems locally where I
operate from
so that others can get used to it. It also helps that I do have a very good
Linux Users
Group locally < http://www.lugwash.org > that I can go to when I get stumped for
answers.

I will keep the group posted as I get things running.

James W8ISS

In addition to info from Jacob, I intend on becoming more of an expert
on running RoverLog on Linux again.  I have migrated completely to
Windows, but I do not want to lose the ability to support Linux users.
This won't be immediate, however, so any help from others will be
appreciated.

It would be helpful for any successful Linux users to report their
distribution (Debian, Ubuntu, etc.) the window manager they are using
(KDE, Gnome, etc.) the file manager they use to navigate around and see
icons, any additional packages they needed to install (Tcl/Tk, etc.) and
any tweaks they needed to make to be able to double-click on the icons
to run RoverLog (chmod, etc).

Thanks!

w8iss wrote:
>
>
> Hello Jacob.
>
> I have just started using roverlog on my Ubuntu 9.04 64bit system and
> have been running the windows version under wine with very few problems.
>
> But I have the same issues you had and don't see anything saying what
> you did to fix it.
>
> Did you chmod the couple of .tcl files to make them work?
> If not, what was the work around?
>
> I would much prefer to run roverlog not as a windows app if I can as I
> know already that there will be a few issues with the soundcard and
> the serial port that I have found with other windows apps running
> under wine. I don't have need for the rotor control yet but plan on
> wanting to use the soundcard for the keyer and voice apps.
>
> James W8ISS
>
> --- In RoverLog@yahoogroups.com <mailto:RoverLog%40yahoogroups.com>,
> Jacob Tennant <k8jwt@...> wrote:
> >
> > Thanks to a quick telephone call from W1RT I am up and running on
> > Roverlog so no more questions, for now. . .
> >
> > And at his suggestion, I am going out today to buy a linux manual so as
> > to learn more and ask less newbie questions.
> >
> > Thanks again to all that helped.
> >
> > Jacob Tennant - K8JWT
> >
>
>

Hello Jacob.

I have just started using roverlog on my Ubuntu 9.04 64bit system and
have been running the windows version under wine with very few problems.

But I have the same issues you had and don't see anything saying what
you did to fix it.

Did you chmod the couple of .tcl files to make them work?
If not, what was the work around?

I would much prefer to run roverlog not as a windows app if I can as I
know already that there will be a few issues with the soundcard and
the serial port that I have found with other windows apps running
under wine. I don't have need for the rotor control yet but plan on
wanting to use the soundcard for the keyer and voice apps.

James W8ISS

--- In RoverLog@yahoogroups.com, Jacob Tennant <k8jwt@...> wrote:
>
> Thanks to a quick telephone call from W1RT I am up and running on
> Roverlog so no more questions, for now. . .
>
> And at his suggestion, I am going out today to buy a linux manual so as
> to learn more and ask less newbie questions.
>
> Thanks again to all that helped.
>
> Jacob Tennant - K8JWT
>

Apparently you can configure the K3 to report the exact RF frequency to
you, i.e. to talk about 2304.1 MHz instead of putting an offset into
RoverLog.  I was accommodating folks that want to do it that way.

John D'Ausilio wrote:
>
>
> hey tom .. curious what you had to change re: elecraft k2/3? I've been
> using it just fine with an offset equal to the GHz portion of the
> frequency (e.g. for 5G the offset is 5000), which gives me a correct
> display up to the 100MHz digit ..
>
> de w1rt/john
>
> On Tue, Sep 22, 2009 at 10:10 AM, hbyipo <tmayo6@...
> <mailto:tmayo6@...>> wrote:
>
>
>
>     Folks,
>
>     I finally got around to making a release with a few fixes that
>     have accumulated over time:
>
>     * Added an option to make RoverLog stay on top of other windows.
>     * Corrected sending microwave frequencies to Elecraft K2 and K3 rigs.
>     * Corrected distance-based scoring to properly count only unique
>     calls per band.
>     * Renamed the old Log Header Editor and skipped creation of a link
>     to it during installation to prevent making old Version 2.0
>     Cabrillo headers.
>
>     Please visit http://roverlog.2ub.org <http://roverlog.2ub.org> to
>     get it.
>
>     Tom, N1MU.
>
>
>

Folks,

I finally got around to making a release with a few fixes that have accumulated
over time:

* Added an option to make RoverLog stay on top of other windows.
* Corrected sending microwave frequencies to Elecraft K2 and K3 rigs.
* Corrected distance-based scoring to properly count only unique calls per band.
* Renamed the old Log Header Editor and skipped creation of a link to it during
installation to prevent making old Version 2.0 Cabrillo headers.

Please visit http://roverlog.2ub.org to get it.

Tom, N1MU.

hbyipo expunged (tmayo6@...):
> Steve,
>
> I finally got around to looking into this, and I believe I have a fix which
will be included in the next release of RoverLog.
>
> Would it help you (or any others) for me to do a release including fixed
distance-based scoring immediately?

That would be great Tom, i just finished the second 10GHz weekend, and I can
plug in all my contacts and see how it works...

I was going to send you my complete log when I had it ready, but the 2m Sprint
last night got in the way :)

-Steve
N1JFU

--- In RoverLog@yahoogroups.com, Steve Meuse <smeuse@...> wrote:
>
> Hey Tom, I tried out the new 10g.ini file this weekend, but I think I may have
found an issue with the score calculation. From the ARRL 10g rules page, wrt
scoring:
>
> "6.2. QSO points: Count 100 QSO points for each unique call sign worked per
band. Portable indicators added to a call sign are not considered as making the
call sign unique."
>
> I think as it stands now it's counting each QSO as a new callsign, not
*unique* callsigns.
>
> So, for example this week I made 53 Q's with maybe 20 unique calls, but the
QSO points were 5300 in the scoring summary, when it should have been 2000 (or
however many unique x100). I can send you my log direct if that would be
helpful.
>
> Also, a few other cool things to consider for the "nice to have" list:
>
> - In the calc window, have the option to change to Kilometers vs. Miles
> - In the main log window, add a Kilometers column at the end.
>
> Although the cabrillo format isn't required for this contest, I'm trying to
interpret the rules to figure out if you need to report the Km per contact, or
if a total Km is adequate. This is the quote from the rules page:
>
> "8.2. Electronic entries must include the required information from the ARRL
summary sheet (available online) completely filled out and a log file indicating
band, date, time, call sign, the exchange information plus distance of contacts
in km. The Cabrillo format is not required for the 10 GHz and Up Contest."
>
> I can't tell if they mean distance per QSO or total Kilometers.
>
> Anyhow, I'm excited to see this capability in RoverLog! Soon I can get rid of
my paper logging...
> -Steve
>

Steve,

I finally got around to looking into this, and I believe I have a fix which will
be included in the next release of RoverLog.

Would it help you (or any others) for me to do a release including fixed
distance-based scoring immediately?

Tom.

--- In RoverLog@yahoogroups.com, "w1rzf62" <w1rzf62@...> wrote:
>
> --- In RoverLog@yahoogroups.com, "w1rzf62" <w1rzf62@> wrote:
> >
> > Hi Recently change rigs to a flex 5000a. Got the frequency control working
for the serial and xvrtr selection working with the parallel port. Dont see how
to set up the cw. Thanka art w1rzf
> >
> Hi agn using the transparent method, I connected line out from thepc to line
in on the flex 5000. this works. However, theyh only alow one audio input a t
atime, so Imustcall up a mixer menue and swith feom mike input to line input.
Not very practical in a contest.
>
> Flex offers virtual audio cables .I have tried that, but I don't see how to
connect roverlog to the virtual cable. Any Ideas? thanks art w1rzf
>

Art,

Have a look in the manual in the section about QuickMix.  This may solve your
issue.  Let us know what you think after checking it out.

Tom.

--- In RoverLog@yahoogroups.com, "w1rzf62" <w1rzf62@...> wrote:
>
> I have a problem, sometimes in the rush of running stations through the bands,
I forget to hit the log qso button, thus dont log the qso. Could there be an
option that once you have filled in the call and report that you must hit log
before any other action like changing the band?  thanks art w1rzf
>

Art,

There's no way to implement this without making it a pain in the neck for people
that don't have this issue.

How does RoverLog know if you are changing the band before or after you worked
the QSO?  Maybe you haven't worked anything yet and you are just getting all the
fields set up to enter the first QSO with the guy.  Do you really want some
distracting dialog popping up every time you go to change a QSO parameter? 
Yuck.

There is an "HCO light" invented by Jeff, WA1HCO, that makes the call and grid
red if it is different and has not yet been logged.  Try that out for now.

Tom.

 

I have a problem, sometimes in the rush of running stations through the bands, I forget to hit the log qso button, thus dont log the qso. Could there be an option that once you have filled in the call and report that you must hit log before any other action like changing the band? thanks art w1rzf

I have a problem, sometimes in the rush of running stations through the bands, I
forget to hit the log qso button, thus dont log the qso. Could there be an
option that once you have filled in the call and report that you must hit log
before any other action like changing the band?  thanks art w1rzf

--- In RoverLog@yahoogroups.com, "w1rzf62" <w1rzf62@...> wrote:
>
> Hi Recently change rigs to a flex 5000a. Got the frequency control working for
the serial and xvrtr selection working with the parallel port. Dont see how to
set up the cw. Thanka art w1rzf
>
Hi agn using the transparent method, I connected line out from thepc to line in
on the flex 5000. this works. However, theyh only alow one audio input a t
atime, so Imustcall up a mixer menue and swith feom mike input to line input.
Not very practical in a contest.

Flex offers virtual audio cables .I have tried that, but I don't see how to
connect roverlog to the virtual cable. Any Ideas? thanks art w1rzf

Hi Recently change rigs to a flex 5000a. Got the frequency control working for
the serial and xvrtr selection working with the parallel port. Dont see how to
set up the cw. Thanka art w1rzf

Thanks to a quick telephone call from W1RT I am up and running on
Roverlog so no more questions, for now. . .

And at his suggestion, I am going out today to buy a linux manual so as
to learn more and ask less newbie questions.

Thanks again to all that helped.

Jacob Tennant - K8JWT

Before doing anything else, verify that you have tcl and tk installed
on your machine. - Duffey


--
KK6MC
James Duffey
Cedar Crest NM

OK I have tried everthing you mentioned and I get "Permission Denied"
evertime. I have the folder for roverlog on the desktop.

jacob Tennant - K8JWT

On Sat, 2009-08-22 at 14:34 -0400, John D'Ausilio wrote:
>
> You probably don't have tcl and tk installed (and I believe you need a
> library or two if you want to use sound card DVK)
>
> the tcl scripts should be executable .. just cd into the roverlog dir
> and type "./roverlog.tcl" or "./inied.tcl" and they should launch
>
> if that doesn't work try "wish" at a command line .. if that doesn't
> work then you have to find RPMs for your distribution (sorry, I avoid
> redhat-type distros) and get tcl and tk installed
>
> de w1rt/john
>
> On Sat, Aug 22, 2009 at 2:15 PM, Jacob Tennant<k8jwt@...>
> wrote:
> >
> >
> > 3. Run inied.tcl to configure RoverLog for your use.
> >
> > OK, I have clicked on this and all it does is bring up the file in a
> > text editor?
> >
> > Also, I have read the manual as I learned long ago that the manual
> is
> > there for a real good reason.
> >
> > Jacob Tennant - K8JWT
> >
> >
>
>
>
>

OK now I have a place to start!

Jacob Tennant - K8JWT
>
>
> the tcl scripts should be executable .. just cd into the roverlog dir
> and type "./roverlog.tcl" or "./inied.tcl" and they should launch
>
> if that doesn't work try "wish" at a command line .. if that doesn't
> work then you have to find RPMs for your distribution (sorry, I avoid
> redhat-type distros) and get tcl and tk installed
>
> de w1rt/john
>

>

You probably don't have tcl and tk installed (and I believe you need a
library or two if you want to use sound card DVK)

the tcl scripts should be executable .. just cd into the roverlog dir
and type "./roverlog.tcl" or "./inied.tcl" and they should launch

if that doesn't work try "wish" at a command line .. if that doesn't
work then you have to find RPMs for your distribution (sorry, I avoid
redhat-type distros) and get tcl and tk installed


de w1rt/john

On Sat, Aug 22, 2009 at 2:15 PM, Jacob Tennant<k8jwt@...> wrote:
>
>
> 3. Run inied.tcl to configure RoverLog for your use.
>
> OK, I have clicked on this and all it does is bring up the file in a
> text editor?
>
> Also, I have read the manual as I learned long ago that the manual is
> there for a real good reason.
>
> Jacob Tennant - K8JWT
>
>

3. Run inied.tcl to configure RoverLog for your use.

OK, I have clicked on this and all it does is bring up the file in a
text editor?

Also, I have read the manual as I learned long ago that the manual is
there for a real good reason.

Jacob Tennant - K8JWT

Jacob - I don't run Roverlog on linux, but I do on a Mac.

If you have already read the manual and are still having problems, I
apologize for this reply. But if you haven't read the manual, just
follow the instructions. Here is what it says for non-windows versions:

Non-Windows:
1. Install Tcl/Tk. This is different depending on what operating
system you use.
2. Unzip the RoverLog distribution.
3. Run inied.tcl to configure RoverLog for your use.
a. Set your Callsign.
b. Set your Default Grid.
c. Set your log file name. Usually it's your callsign with ".log"
appended. Your log file
“lives” in the folder in which RoverLog was installed.
d. Set the Contest .ini file name to make sure your score is
calculated properly.
e. Review the other settings and verify they are correct.
4. Optionally, run logheaded.tcl to initialize your log file and header.
5. To start RoverLog, run ./roverlog.tcl from the shell prompt or
double-click if you have
associated .tcl files with the wish Tk interpretter.

All:
1. Ensure that your system clock is set to the correct time. RoverLog
uses UTC time for all
references.  It calculates the difference between your local time and
UTC using the time
zone you have set for your operating system.
2. If you wish to use RoverLog modules (Keyer, Rotor, Rig, GPS, or
Clock), select them in
inied.tcl before running RoverLog so they will start automatically
when you start
RoverLog.
3. The Modules (except Clock) can interface to different devices via a
serial port on your
computer.  Make sure the .ini files for each module are set up for the
correct serial port
(COMx: for Windows and /dev/ttySx for Linux for example).

I hope that this helps. If you have further problems, you may need to
get a linux user involved, but give the above a try if you already
haven't. - Duffey

--
KK6MC
James Duffey
Cedar Crest NM

OK I am new to linux (Fedora 11) and just setup a brand new install
yesterday and I have no idea how to get things started in TCL/TK.

I have verified that everything needed is installed.

So I hate to ask for you help but I must, as the September VHF contest
is only a few weeks away and it will be my debut as a rover station.

Jacob Tennant - K8JWT

Eric,

Thanks for the feedback.

I looked for a dialog box about the GPS and could not find one given the
information you quoted.  Do you have the latest version of RoverLog?

If you recreate the issue and take screen shots, I can help.

The alert mechanism I expect is that the "From GPS" selection radio
button turns red and the Manual button is selected instead.

Tom.

Eric Watkins wrote:
>
>
> Hello all,
>
> So I used roverlog in the past weekend's UHF contest. Love the quick
> band changes and easy editing functions! One small request in
> relation to the "from GPS" radio box and GPS server functionality. I
> was updating the GPS coordinates from the GPS server, which had some
> trouble getting data from xport (software serial splitter.) In the
> middle of several important contacts I had a modal dialog box pop up
> complaining about the lack of ability to sync time and get the GPS
> coords from the GPS server. I wish I'd taken some
> pictures/screenshots, but I was busy getting it out of the way and
> getting the contact in the log. Heat of the contest and all. In any
> case, can we have dialogs like that be a) non modal and b) somehow
> less intrusive? I do like knowing that the GPS coords aren't spot on
> and that the clock isn't up to date, but is this the sort of message
> that could flash in the window header or footer? Even if we could
> just have this dialog box not be modal, that'd be better than having
> to scramble for the mouse. It seems like I have a ton of screen space
> with only 16 or 32 contacts showing, there should be room for a
> status section for communication fail/success with the rotor/gps/rig
> modules. Well, that's my .02 cents post contest.
>
> Thanks for writing such awesome software,
>
> Eric
>
>

Thanks for the feedback, Steve.

Please send me your log and what you think the score should be so I have
an example to work by.

I will look at the other requests and get them on the to do list.

Steve Meuse wrote:
>
>
> Hey Tom, I tried out the new 10g.ini file this weekend, but I think I
> may have found an issue with the score calculation. From the ARRL 10g
> rules page, wrt scoring:
>
> "6.2. QSO points: Count 100 QSO points for each unique call sign
> worked per band. Portable indicators added to a call sign are not
> considered as making the call sign unique."
>
> I think as it stands now it's counting each QSO as a new callsign, not
> *unique* callsigns.
>
> So, for example this week I made 53 Q's with maybe 20 unique calls,
> but the QSO points were 5300 in the scoring summary, when it should
> have been 2000 (or however many unique x100). I can send you my log
> direct if that would be helpful.
>
> Also, a few other cool things to consider for the "nice to have" list:
>
> - In the calc window, have the option to change to Kilometers vs. Miles
> - In the main log window, add a Kilometers column at the end.
>
> Although the cabrillo format isn't required for this contest, I'm
> trying to interpret the rules to figure out if you need to report the
> Km per contact, or if a total Km is adequate. This is the quote from
> the rules page:
>
> "8.2. Electronic entries must include the required information from
> the ARRL summary sheet (available online) completely filled out and a
> log file indicating band, date, time, call sign, the exchange
> information plus distance of contacts in km. The Cabrillo format is
> not required for the 10 GHz and Up Contest."
>
> I can't tell if they mean distance per QSO or total Kilometers.
>
> Anyhow, I'm excited to see this capability in RoverLog! Soon I can get
> rid of my paper logging...
> -Steve
>
>

Hey Tom, I tried out the new 10g.ini file this weekend, but I think I may have
found an issue with the score calculation. From the ARRL 10g rules page, wrt
scoring:

"6.2. QSO points: Count 100 QSO points for each unique call sign worked per
band. Portable indicators added to a call sign are not considered as making the
call sign unique."

I think as it stands now it's counting each QSO as a new callsign, not *unique*
callsigns.

So, for example this week I made 53 Q's with maybe 20 unique calls, but the QSO
points were 5300 in the scoring summary, when it should have been 2000 (or
however many unique x100). I can send you my log direct if that would be
helpful.

Also, a few other cool things to consider for the "nice to have" list:

- In the calc window, have the option to change to Kilometers vs. Miles
- In the main log window, add a Kilometers column at the end.

Although the cabrillo format isn't required for this contest, I'm trying to
interpret the rules to figure out if you need to report the Km per contact, or
if a total Km is adequate. This is the quote from the rules page:

"8.2. Electronic entries must include the required information from the ARRL
summary sheet (available online) completely filled out and a log file indicating
band, date, time, call sign, the exchange information plus distance of contacts
in km. The Cabrillo format is not required for the 10 GHz and Up Contest."

I can't tell if they mean distance per QSO or total Kilometers.

Anyhow, I'm excited to see this capability in RoverLog! Soon I can get rid of my
paper logging...
-Steve

Hello all,

So I used roverlog in the past weekend's UHF contest. Love the quick
band changes and easy editing functions!  One small request in
relation to the "from GPS" radio box and GPS server functionality. I
was updating the GPS coordinates from the GPS server, which had some
trouble getting data from xport (software serial splitter.) In the
middle of several important contacts I had a modal dialog box pop up
complaining about the lack of ability to sync time and get the GPS
coords from the GPS server. I wish I'd taken some
pictures/screenshots, but I was busy getting it out of the way and
getting the contact in the log. Heat of the contest and all. In any
case, can we have dialogs like that be a) non modal and b) somehow
less intrusive? I do like knowing that the GPS coords aren't spot on
and that the clock isn't up to date, but is this the sort of message
that could flash in the window header or footer? Even if we could
just have this dialog box not be modal, that'd be better than having
to scramble for the mouse. It seems like I have a ton of screen space
with only 16 or 32 contacts showing, there should be room for a
status section for communication fail/success with the rotor/gps/rig
modules. Well, that's my .02 cents post contest.

Thanks for writing such awesome software,

Eric