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

Re: V4 Text Box

Expand Messages
  • la7um
    Rick, I agree with you also. I like viewing what can be viewed, and sometimes the brain makes the fill ins. 73. Finn/LA7UM
    Message 1 of 4 , Jun 22, 2012
    • 0 Attachment
      Rick, I agree with you also. I like viewing what can be viewed, and sometimes the brain makes the fill ins. 73. Finn/LA7UM

      --- In V4Protocol@yahoogroups.com, "Fred - w1wyc" <f_garside@...> wrote:
      >
      > Hi Rick,
      >
      > I agree with you. I have been able to interpret a lot of red strike-thru data to allow me to determine what was sent.
      >
      > 73,
      > Fred, W1WYC
      >
      > ----- Original Message -----
      > From: Rick Muething
      > To: V4Protocol@yahoogroups.com
      > Sent: Wednesday, June 20, 2012 4:21 PM
      > Subject: Re: [V4Protocol] V4 Text Box
      >
      >
      >
      >
      > Russ,
      >
      > Remember there are two modes that V4 Works in ...selectable by the user.
      >
      > 1) FEC mode. This tries to correct errors with V4’s FEC but there is no “back channel” so the receiving station cannot request a repeat. This mode is used primarily for broadcast (one sender to many recipients) and in that case most users would want to see the data even if a frame were corrupted. Much of the time you can still “read through” an uncorrectable error just as you can in RTTY or CW or phone. When V4 gets an error that the FEC can’t correct in FEC mode it shows that text in red strikethrough. It doesn’t know what characters in the frame are actually bad so it has no choice but to mark the entire frame bad.
      >
      > 2) ARQ mode. This is a “connected” protocol between two stations (and ONLY two stations) and the ARQ mechanism along with FEC insures the data is eventually perfect or else the link will time out eventually (about 2 minutes with no data flowing). In this mode V4Chat suppresses all errors showing only fully corrected text (you should never see strike through text when connected in ARQ mode). When you are in ARQ mode but not connected it works exactly like FEC mode so you can see text (even if it corrupted) or you can also monitor another FEC transmission.
      >
      > Although it is possible to but some display option to block all uncorrectable text I think it would generally not be good operating practice. E.g. a weak station is calling CQ but rarely decoding without errors. Most would choose to at least see everything received since you often get at least partial data that caries some information. I would like to get feedback on this from more users before putting in such an option because I am afraid it will cause more confusion (e.g. “I hear a station but I don’t see any printing” etc.)
      >
      > 73,
      >
      > Rick KN6KB
      >
      >
      > From: k1dow_4
      > Sent: Wednesday, June 20, 2012 3:54 PM
      > To: V4Protocol@yahoogroups.com
      > Subject: [V4Protocol] V4 Text Box
      >
      >
      > Rick;
      >
      > Good to see that you have found some time to devote to V4 again. Your work is enjoyed and appreciated by all of us V4 testers.
      >
      > One thing I do want to question though is the appearance of the following which I quote from the help files:
      >
      > "Received text (FEC or unconnected ARQ) with uncorrectable errors is Red strike through (log tag: {Rcv Text Err} )"
      >
      > As I sit here watching this accumulate in my Text Box I'm wondering why should this be cluttering up my text box anyway?
      >
      > I would prefer to only see correctly decoded text printed. Or at least have an option to turn off uncorrectable text being printed to the Text Box if I prefer not to see it.
      >
      > Could that be made possible?
      >
      > 73/Russ
      > K1DOW
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.