Loading ...
Sorry, an error occurred while loading the content.

Re: [dxatlas] oddity in MR 1.5

Expand Messages
  • Alex, VE3NEA
    Hi Ian, This is not a bug, he-he... If the calling operator thinks that you busted his call, hit F5 (His Call) and F3 (TU), no need to re-enter the callsign or
    Message 1 of 5 , Jun 5, 2005
    • 0 Attachment
      Hi Ian,

      This is not a bug, he-he...

      If the calling operator thinks that you busted his call, hit F5 (His Call)
      and F3 (TU), no need to re-enter the callsign or re-send the exchange. The
      program remembers the last saved call until you enter a new one.

      73 Alex VE3NEA





      > All,
      >
      > Have any of you experienced this? I wonder if it's possible to go back to
      > an
      > earlier rev., say, 1.4.. .
      >
      > When running a pileup using 1.5, I am frequently running into the
      > following:
      >
      >
      > 1. I call CQ
      > 2. I pick out a station to answer
      > 3. I CORRECTLY copy/enter the call, give the exchange, and hit enter to
      > log
      > 4. The calling station then starts going on as if I've busted his call,
      > and...
      > 5. The only way to stop him from sending is call again and again is to
      > enter
      > it again
      > As though I was answer a new station, give the exchange again, let him
      > say "r"
      > And have to listen to him give his report all over again. At this
      > point I can hit
      > F3 and the "NIL" on the previous line will go away.
      >
      > Is this a flaw or one of Alex's "improvements" to the LIDs feature??
      >
      > I LOVE the adjustable monitor level, although I'd love it even more if it
      > could go one notch lower ;) But with this new and most irritating
      > situation,
      > I'd happily go back to 1.4 (where I never had this issue come up) and sit
      > there with the phones halfway off my head :)
      >
      > 'zm
      >
      > --
      > Parsons... Ian Parsons
    • Ian Parsons
      Hehe.. Tnx. Now my head won t hurt so much next time ;) _____ From: dxatlas_group@yahoogroups.com [mailto:dxatlas_group@yahoogroups.com] On Behalf Of Alex,
      Message 2 of 5 , Jun 5, 2005
      • 0 Attachment
        Hehe.. Tnx. Now my head won't hurt so much next time ;)



        _____

        From: dxatlas_group@yahoogroups.com [mailto:dxatlas_group@yahoogroups.com]
        On Behalf Of Alex, VE3NEA
        Sent: Sunday, 05 June, 2005 6:27 PM
        To: dxatlas_group@yahoogroups.com
        Subject: Re: [dxatlas] oddity in MR 1.5



        Hi Ian,

        This is not a bug, he-he...

        If the calling operator thinks that you busted his call, hit F5 (His Call)
        and F3 (TU), no need to re-enter the callsign or re-send the exchange. The
        program remembers the last saved call until you enter a new one.

        73 Alex VE3NEA





        > All,
        >
        > Have any of you experienced this? I wonder if it's possible to go back to
        > an
        > earlier rev., say, 1.4.. .
        >
        > When running a pileup using 1.5, I am frequently running into the
        > following:
        >
        >
        > 1. I call CQ
        > 2. I pick out a station to answer
        > 3. I CORRECTLY copy/enter the call, give the exchange, and hit enter to
        > log
        > 4. The calling station then starts going on as if I've busted his call,
        > and...
        > 5. The only way to stop him from sending is call again and again is to
        > enter
        > it again
        > As though I was answer a new station, give the exchange again, let him
        > say "r"
        > And have to listen to him give his report all over again. At this
        > point I can hit
        > F3 and the "NIL" on the previous line will go away.
        >
        > Is this a flaw or one of Alex's "improvements" to the LIDs feature??
        >
        > I LOVE the adjustable monitor level, although I'd love it even more if it
        > could go one notch lower ;) But with this new and most irritating
        > situation,
        > I'd happily go back to 1.4 (where I never had this issue come up) and sit
        > there with the phones halfway off my head :)
        >
        > 'zm
        >
        > --
        > Parsons... Ian Parsons




        _____

        Yahoo! Groups Links

        * To visit your group on the web, go to:
        http://groups.yahoo.com/group/dxatlas_group/

        * To unsubscribe from this group, send an email to:
        dxatlas_group-unsubscribe@yahoogroups.com
        <mailto:dxatlas_group-unsubscribe@yahoogroups.com?subject=Unsubscribe>

        * Your use of Yahoo! Groups is subject to the Yahoo!
        <http://docs.yahoo.com/info/terms/> Terms of Service.



        [Non-text portions of this message have been removed]
      • Michael Pfeuffer
        You re evil. I like it. :) Now, if we could just customize the keys to match different contesting programs... 73! --Mike WQ5C
        Message 3 of 5 , Jun 5, 2005
        • 0 Attachment
          You're evil. I like it. :)

          Now, if we could just customize the keys to match different contesting
          programs...

          73!
          --Mike WQ5C



          At 08:27 PM 6/5/2005, Alex, VE3NEA wrote:
          >Hi Ian,
          >
          >This is not a bug, he-he...
          >
          >If the calling operator thinks that you busted his call, hit F5 (His Call)
          >and F3 (TU), no need to re-enter the callsign or re-send the exchange. The
          >program remembers the last saved call until you enter a new one.
          >
          >73 Alex VE3NEA
          >
          >
          >
          >
          >
          > > All,
          > >
          > > Have any of you experienced this? I wonder if it's possible to go back to
          > > an
          > > earlier rev., say, 1.4.. .
          > >
          > > When running a pileup using 1.5, I am frequently running into the
          > > following:
          > >
          > >
          > > 1. I call CQ
          > > 2. I pick out a station to answer
          > > 3. I CORRECTLY copy/enter the call, give the exchange, and hit enter to
          > > log
          > > 4. The calling station then starts going on as if I've busted his call,
          > > and...
          > > 5. The only way to stop him from sending is call again and again is to
          > > enter
          > > it again
          > > As though I was answer a new station, give the exchange again, let him
          > > say "r"
          > > And have to listen to him give his report all over again. At this
          > > point I can hit
          > > F3 and the "NIL" on the previous line will go away.
          > >
          > > Is this a flaw or one of Alex's "improvements" to the LIDs feature??
          > >
          > > I LOVE the adjustable monitor level, although I'd love it even more if it
          > > could go one notch lower ;) But with this new and most irritating
          > > situation,
          > > I'd happily go back to 1.4 (where I never had this issue come up) and sit
          > > there with the phones halfway off my head :)
          > >
          > > 'zm
          > >
          > > --
          > > Parsons... Ian Parsons
          >
          >
          >
          >
          >Yahoo! Groups Links
          >
          >
          >
          >
        • Alex, VE3NEA
          Hi Mike, You have yet to see some other evil tricks MR has learned :-) For example, in the new version the op does NOT always correct you if you bust the call.
          Message 4 of 5 , Jun 5, 2005
          • 0 Attachment
            Hi Mike,

            You have yet to see some other evil tricks MR has learned :-) For example,
            in the new version the op does NOT always correct you if you bust the call.
            Guessing callsigns is now dangerous, like in the real world.

            Perhaps I can make the mapping between the F keys and the messages
            configurable, but I cannot allow editing the message text. Remember that
            there are not human operators behind the calling stations. The program can
            copy what you send, but it cannot understand what the message means, it just
            checks which F key you pressed. When I figure out how to write a program
            that understands free format messages, I will probably create a robot that
            will work in the contests for me ;-)

            73 Alex VE3NEA






            > You're evil. I like it. :)
            >
            > Now, if we could just customize the keys to match different contesting
            > programs...
            >
            > 73!
            > --Mike WQ5C
            >
            >
            >
            > At 08:27 PM 6/5/2005, Alex, VE3NEA wrote:
            >>Hi Ian,
            >>
            >>This is not a bug, he-he...
            >>
            >>If the calling operator thinks that you busted his call, hit F5 (His Call)
            >>and F3 (TU), no need to re-enter the callsign or re-send the exchange. The
            >>program remembers the last saved call until you enter a new one.
            >>
            >>73 Alex VE3NEA
          • Gary Hinson
            Alex, Entering European Field Day the weekend just past led me to think about my top twenty examples of incompetent contestants that you might like to simulate
            Message 5 of 5 , Jun 7, 2005
            • 0 Attachment
              Alex,

              Entering European Field Day the weekend just past led me to think about my
              top twenty examples of incompetent contestants that you might like to
              simulate in Morse Runner. This is - unfortunately - only a partial list:

              1) Alligators (all mouth, no ears) who either hear nothing at all or ask for
              repeats, sometimes more than once, sometimes once more ...

              2) Touch-typos who get our call wrong (and sometimes refuse to acknowledge
              the call correction), and occasionally get their own call wrong, forget the
              /P, send the wrong serial number (any digit wrong)

              3) Sonically-challenged lids who start calling CQ on 'our' frequency with no
              QRL?, or who are selectively deaf if we respond to the QRL? with anything at
              all (you've got those already Alex, but how about letting us tell them to
              QSY, or QSY ourselves a bit to slide out of trouble, if there is room to
              move without colliding with someone else?)

              4) Squinters - off-channel callers (MR does this well already, but sometimes
              they move frequency between overs to keep us on our toes!)

              5) Red Zone callers who push the rig and amp to the very limits of
              performance and often well beyond. Their sigs are as far from perfect sine
              waves as it is possible to get. Raspy T1 notes, drifty wanderers,
              multiple-tones, we hear the lot in every Field Day and many fixed contests
              too, so it's not all down to battery power.

              6) Dupes we've already worked already. We have already worked them. We
              have worked them before. But still they keep calling back.
              6a) Phantom Dupes who claim we've worked before, but haven't (often because
              of a busted QSO) ... and yes, this includes those who answer our CQs
              6b) Phantom Dupes who want to correct the serial number they gave us one or
              two QSOs ago [Alex, is it too difficult to be able to move the cursor up a
              few QSOs to correct the log? Doing this well without messing up the QSO in
              progress is another hard-won contesting skill.]

              7) Me Me's who try to complete a QSO even when we are quite clearly and
              adamantly working someone else, causing loads of QRM

              8) Tone Deaf tuner-uppers who choose 'our' frequency to try to melt their PA
              valves

              9) QRPers and DX callers who specialise in drifting vaguely around the noise
              floor

              10) Meter-misers whose electricity runs out half way through a QSO and
              suddenly go QRT (maybe to re-fill the generator?) leaving us hanging ...

              11) CBers who want to tell us their name, rig, QSL info and so forth, and
              have no idea we are in a contest, nor what a contest is

              12) Slotters who want us to QSY and work them on another band, often when
              there is no propagation

              13) Zero Beaters who call at exactly the same time and frequency as each
              other on each over

              14) QLFs who send dots, dashes and other indeterminate bits and gaps in a
              random sequence not resembling any known Morse characters

              15) Repeaters who send their calls several times, and sometimes our call too
              for good measure

              16) Autobiographers who seem to want tell me their entire life stories:
              "G4iFB DE M0LID - TNX RPRT OM - UR RST 599 5NN 599 - OP HERE SIMON SIMON -
              QTH BIGGINSWADE - WX WET AND WINDY - GL IN CONTEST ..."

              17) Life's-too-shorters who don't leave gapsbetweenwords, and even worse
              don't leave gaps between charactrz because it saves a few milliseconds

              18) Gadget-boys who love to send 5NN and TEST at a zillion wpm but can't
              receive at the same speed

              19) Strokers who try all possible variations of bits and spaces in a
              desperate attempt to send /P [after too few hours sleep, I'm usually in this
              category myself by Sunday morning!]

              20) Breakers on QSK who drop bits into our stream in an attempt to stop us
              sending, but then get all mixed up when we actually stop for them

              One thing I've noticed in MR but almost never in Real Life is that if we
              send a partial call but the real caller doesn't respond, MR leaves us
              hanging in silence, listening to white noise, QRM and QRN. In Real Live,
              usually, someone else will jump in to any gap within a short while with
              their own call, even though it bears no relation to the partial. They
              usually call during the first quiet period more than a few milliseconds
              long, and almost always it's a complete free-for-all on the second partial
              attempt (as if we have just called CQ all over again). Usually a "?" will
              coax them out of hiding if it all goes quiet, but not in MR.

              But the biggest request of all, Alex, is for a new mode: S&P
              (search-and-pounce). I suspect even the biggest of monster stations with
              the most exotic callsigns don't CQ all the time but need to hunt around for
              new mults etc. from time to time. There's definitely an art to S&P
              efficiently. I have in mind a QSY facility that works just like the
              'tuneable IF' idea you already have, perhaps, or else a pair of QSY up/down
              buttons. Then we can zero beat on people calling CQ and try to work them.

              My trusty old Morse Machine runs the Doctor DX program to simulate contests.
              It lets you change bands, and makes a reasonable attempt to change the
              callers to reflect the different propagation on each band ... This maybe
              just a bit sophisticated for free MR but it's maybe another idea to
              consider.

              With all those wish-list items off my mind, let me just say that I am not
              trying to overload the poor programmer and certainly don't expect to see
              these wishes met unless others agree. Most of all, I would hate to
              compromise MR's beautifully realistic audio simulation that beats any other
              morse sim I have *ever* used hands-down. And all this for free! Alex,
              you're a star.

              73
              Gary
              G4iFB (also the weaker half of G3GRS/P and an insignificant element of M6T
              GW8GT G0FBB/P XT2DX GJ2A etc. etc.)


              [Non-text portions of this message have been removed]
            Your message has been successfully submitted and would be delivered to recipients shortly.