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

Chat 0.1.7.0 Beta uploaded to Auto Update Server, Yahoo FTP and Winlink FTP sites

Expand Messages
  • Rick Muething
    All, I have uploaded the latest beta version to the above servers. This is still a FEC only version though it has many small and important enhancements noted
    Message 1 of 11 , Nov 4, 2013
    • 0 Attachment

      All,

       

      I have uploaded the latest beta version to the above servers.  This is still a FEC only version though it has many small and important enhancements noted below.

       

      If there are serious problems please let me know.  The help has all been updated and should be current with the new version.  With the exception of some issues or expansion of the radio control for some radios this should be very functional.  It includes some new utilities and tuning code to handle much wider range of sound card errors (up to about 4000 ppm).

       

      I am working on the ARQ version.  This will take some time but is progressing.  I want to get the base of the FEC version working very solid and functional before introducing any ARQ versions.

       

      Significant Changes:

                                      Save/Recall of AutoID to Chat.ini file

                                      Improve Session text box readability

                                      Add Rx and Tx throughput calculation

                                      Add frequency readback for Yaesu FT-920 (need confirmation on this)

                                      Modify sync detect thresholding

                                      Improve sync and symbol tracking

                                      Add Busy channel detection and out bound Queue control

                                      Update Chat and H4TNC Help

                     

      I will keep my beacons operational on 10123.00 or 28230.00 USB dial

       

      Thanks for your support and feedback.

       

      73,

       

      Rick KN6KB

       

       

       

      Chat Revision History

       

      Date:                     Rev        Change Summary

       

      Nov 4, 2013         0.1.7.0   Beta release of 0.1.6.1

       

      Nov 3, 2013         0.1.6.1   Change Beacon Setup: Max length to 80 (was 70). Range 5-60 sec (was 10-120). Step 5 sec (was 10)

                                                      Modify Radio.ProcessKenwood [remove commands to clear Beat canceller, Noise Blanker, Noise Reducer,

                                                      Do not disable tuner if Enable Internal Tuner unchecked.(leave as set in radio) ]

                                                      Modify Main.tmr Poll to use blnPTT variable to block Radio frequency read request if PTT active.

                                                      Change Session text box sent text from green normal to green italic text. (matches font style in Keyboard text box)

                                                      Add save/recall of AutoID status to Chat.ini file

                                                      Change ScrollLock auto reset to 10 seconds (was 30)

                                                      Add extra vbLF to bottom of display to improve last line readability.

                                                      Update RX throughput calculation to 30 sec rolling avg and 450 bytes/min (75 words/min) max.

                                                      Change spelling of "7Bit" to a consistent "7BIT" in ASCII encoding definitions.

                                                      Add Frequency Read back for Yaesu FT-920 in Radio.GetFrequency (' Op code needs verification)

       

      Oct 22, 2013        0.1.6.0   Release of 0.1.5.1

       

       

       

       

       

      H4FSK TNC Revision History

       

      Date:                     Rev                        Change Summary

       

      Nov 4, 2013         0.1.7.0                   Beta release if 0.1.6.1

       

      Nov 4,2013          0.1.6.1   Trial version to evaluate mods to reduce false tune detection.

                                                                      Ratio multiplier calculation changed from Thresh/10 to Thresh/5  (increases the importance of two equal tones in Sync)

                                                                      Threshold of dblPriorCor in ProcessNewSamples changed to (1 - Squelch/10)  was .5 (requires stronger value for low thresholds)

                                                                      Add logic in H4FSKInterface.Poll to abort if playing (FEC mode) 

                                                                      Add debug logging for unbounded SampleResyncOffset in H4Demod.AdjSymbolSync62BMix to log sync drift per frame.  (re assess bound limits)

                                                                      Expand bounded sync adjustment in AdjSymbolSync62Bmix from +/- 14 to +/- 40

                                                                      Change required sample length in ProcessNewSampes.Capture Stat Track from 1536 + 192 to 1536 + 288 to insure at least one pass.

                                                                      Add H4Demod.SRCompensation to use phase difference in pairs of the same tone to determine correction for pointer.

                                                                      (handles larger SR errors up to 4000 ppm) [ needs on air verification]

                                                                      Add Average Sample rate calculation and display on Help drop down list.

                                                                      Add utility in Test drop down list to make an approximate measurement of playback rate.

                                                                      Change amplitude of 4FSK data and leader (mult x .707) to make same RMS value of sync.(constant output power)

                                                                      Change polling timer in Interface from 20 ms to 64 ms (reduces CPU loading)

                                                                      Change Tuning range control in Basic setup to cover range 10 to 100 (was 50 to 150)

                                                                      Modify  H4FECMod.SendFECBytes to echo back sent data before appending EOT.

                                                                      Modify H4FECDemod.ProcessNewSamples to not send characters with value < 31 to host in FEC mode (blocks non printing chars)

                                                                      Added RED busy indicator to right end of main menu line on Interface form. (Triggers with sync detect and sets blnChannelBusy.

                                                                      Clears busy in 1.1 sec of no sync detect)

                                                                      Block sending of OB Queue if blnChannelBusy

                                                                      Mod H4FECDemod.ProcessNewSamples to make small adjustment in detection threshold for Tune and Track states

                                                                      Update Help 

       

      Oct 22, 2013        0.1.6.0                   Release of 0.1.5.1

       

    • W6IDS
      Rick, knowing your busy, etc etc. . . . let me make a comment. I am unable to wrap my mind around the concept of having my transmitted text appear “twice”
      Message 2 of 11 , Nov 4, 2013
      • 0 Attachment
         
        Rick, knowing your busy, etc etc. . . . let me make a comment.
         
        I am unable to wrap my mind around the concept of having my transmitted text
        appear “twice” locally.  I know there’s probably a reason for it as requested by
        “someone.”  However, that someone would be in a fix if running a normal TNC
        with Pactor or  something else I suppose if they need this type of visual aid.
         
        I’m finding it distracting, especially when trying to root out who’s sending back
        to me with their own comments.  Visually, it’s sort of cluttered to ME and of
        course IMHO.  I don’t know if anyone else is bothered by it but I am for the sake
        of discussion and I thought I’d pass my comments along.
         
        Howard W6IDS
        Richmond, IN EM79NV
         
        Sent: Monday, November 04, 2013 5:01 PM
        Subject: [V4Protocol] Chat 0.1.7.0 Beta uploaded to Auto Update Server, Yahoo FTP and Winlink FTP sites


        All,

        I have uploaded the latest beta version to the above servers.  This is still a FEC only version though it has many small and important enhancements noted below.

        If there are serious problems please let me know.  The help has all been updated and should be current with the new version.  With the exception of some issues or expansion of the radio control for some radios this should be very functional.  It includes some new utilities and tuning code to handle much wider range of sound card errors (up to about 4000 ppm).

        I am working on the ARQ version.  This will take some time but is progressing.  I want to get the base of the FEC version working very solid and functional before intro ducing any ARQ versions.

        <SNIP> <SNIP>

      • enkitec
        Is there a way of running Chat and HRD at the same time? Mark Jordan PY3SS ...     Is there a way of running Chat and HRD at the same time?     Mark
        Message 3 of 11 , Nov 4, 2013
        • 0 Attachment

              Is there a way of running Chat and HRD at the same time?

              Mark Jordan PY3SS


          On 05-Nov-13 00:30, W6IDS wrote:
           
          Rick, knowing your busy, etc etc. . . . let me make a comment.
           
          I am unable to wrap my mind around the concept of having my transmitted text
          appear “twice” locally.  I know there’s probably a reason for it as requested by
          “someone.”  However, that someone would be in a fix if running a normal TNC
          with Pactor or  something else I suppose if they need this type of visual aid.
           
          I’m finding it distracting, especially when trying to root out who’s sending back
          to me with their own comments.  Visually, it’s sort of cluttered to ME and of
          course IMHO.  I don’t know if anyone else is bothered by it but I am for the sake
          of discussion and I thought I’d pass my comments along.
           
          Howard W6IDS
          Richmond, IN EM79NV
           
          Sent: Monday, November 04, 2013 5:01 PM
          Subject: [V4Protocol] Chat 0.1.7.0 Beta uploaded to Auto Update Server, Yahoo FTP and Winlink FTP sites


          All,

          I have uploaded the latest beta version to the above servers.  This is still a FEC only version though it has many small and important enhancements noted below.

          If there are serious problems please let me know.  The help has all been updated and should be current with the new version.  With the exception of some issues or expansion of the radio control for some radios this should be very functional.  It includes some new utilities and tuning code to handle much wider range of sound card errors (up to about 4000 ppm).

          I am working on the ARQ version.  This will take some time but is progressing.  I want to get the base of the FEC version working very solid and functional before intro ducing any ARQ versions.

          <SNIP> <SNIP>


        • Rick Muething
          Mark, Howard, Re Session text Box: The concept I used in the session text box (which is always logged to the Chat .log) has the full text of the QSO
          Message 4 of 11 , Nov 5, 2013
          • 0 Attachment

            Mark, Howard,

             

            Re  Session text Box:

            The concept I used in the session text box (which is always logged to the Chat <date>.log) has the full text of the QSO along with status info contained in one text window. This includes the text sent (now in Green Italic type) and the text received (in normal black type for FEC). In the log (which is not rich text to reduce log bulk) the sent and received text are indicated by keys e.g. {Rcvd FEC text} etc.  This permits going back in the log and being able to read in time sequence the text (from both ends) as it was sent and received.

             

            Unless you are using full duplex (not likely at least on HF) or just testing with full duplex audio)  the sent and received text will not be the same in the Session window (e.g. Your receiver is usually blanked when the transceiver is keyed unless you have a RF monitor enabled. ) If you are using an audio loop back (sound card audio out connected directly (or acoustically) to sound card audio in) you of course will see the Sent (green italic text) immediately followed by the received text (black normal text). But this is not the normal way the program is used with a radio.

             

            The reason transmitted text is entered into a separate window is to allow editing (backspace, delete etc.) BEFORE text is committed to the outbound Queue which then becomes un editable. The cursor control is set up so that you can’t go back and edit text already sent to the outbound Queue (though you can Capture it to the clipboard).

             

            I am open for other ways to do this but this has been worked out (similar version in the old V4Chat) and generally has been well received by users.   The one customizing feature that is asked for is various ways to “commit” the text to the output queue so there are now 4 options to select this …its really a matter of personal preference.  I personally use the CR or double space as the “commit text” option.

             

            Re HRD:

            The problems with this and other similar third-party interface programs are this:

            1.       Often they introduce delay (due to polling cycles etc.) that can delay the commands 100-200 ms or more.  That may not seem like a lot but in an ARQ mode adding 100 + ms and the additional uncertainty due to polling (timing ambiguity) requires substantially increasing the timing guard bands on ARQ cycles and that has a significant impact on ARQ throughput and makes it difficult to build in accurate round trip measurement and compensation. As an aside Pactor ARQ requires a hardware PTT control with < 50 ms delay ….there is a reason for that and why it is very difficult to implement Pactor in PC software and why Pactor can’t use software control of PTT.     

            2.       There are functions like Click to tune, Aux Mux control,  and frequency read back that are not always supported by some interfaces.

            3.       It adds an uncontrolled third-party piece of software in the tight Chat<> Radio interface. I have no control over how or when they implement functions or new radios.  I cannot force them to implement a change to accommodate some needed feature or timing. E.g.  Radios with built in sound cards (Icom 7100, 7200, 7600, Kenwood TS590S) require specific AUX mux commands that may not be implemented in some of these interfaces.

             

            Hope this addresses some of your questions/issues.

             

            73,


            Rick KN6KB

             

            From: V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com] On Behalf Of enkitec@...
            Sent: Monday, November 04, 2013 9:37 PM
            To: V4Protocol@yahoogroups.com
            Subject: Re: [V4Protocol] Chat 0.1.7.0 Beta uploaded to Auto Update Server, Yahoo FTP and Winlink FTP sites

             

             


                Is there a way of running Chat and HRD at the same time?

                Mark Jordan PY3SS


            On 05-Nov-13 00:30, W6IDS wrote:

             

            Rick, knowing your busy, etc etc. . . . let me make a comment.

             

            I am unable to wrap my mind around the concept of having my transmitted text

            appear “twice” locally.  I know there’s probably a reason for it as requested by

            “someone.”  However, that someone would be in a fix if running a normal TNC

            with Pactor or  something else I suppose if they need this type of visual aid.

             

            I’m finding it distracting, especially when trying to root out who’s sending back

            to me with their own comments.  Visually, it’s sort of cluttered to ME and of

            course IMHO.  I don’t know if anyone else is bothered by it but I am for the sake

            of discussion and I thought I’d pass my comments along.

             

            Howard W6IDS

            Richmond, IN EM79NV

             

            Sent: Monday, November 04, 2013 5:01 PM

            Subject: [V4Protocol] Chat 0.1.7.0 Beta uploaded to Auto Update Server, Yahoo FTP and Winlink FTP sites




            All,

            I have uploaded the latest beta version to the above servers.  This is still a FEC only version though it has many small and important enhancements noted below.

            If there are serious problems please let me know.  The help has all been updated and should be current with the new version.  With the exception of some issues or expansion of the radio control for some radios this should be very functional.  It includes some new utilities and tuning code to handle much wider range of sound card errors (up to about 4000 ppm).

            I am working on the ARQ version.  This will take some time but is progressing.  I want to get the base of the FEC version working very solid and functional before intro ducing any ARQ versions.

            <SNIP> <SNIP>

             

          • Ron Wenig
            Hi Rick, I learn something everyday in this hobby :-) I have a Kenwood TS-590 using the built in USB sound card. When I turn on the monitor feature of the
            Message 5 of 11 , Nov 5, 2013
            • 0 Attachment
              Hi Rick,

              I learn something everyday in this hobby :-)

              I have a Kenwood TS-590 using the built in USB sound card.  When I turn on the monitor feature of the radio, so I can hear what is being transmitted, in the text window I will get black normal text and the green Italic text, which I thought was the way the program was designed and a little confusing because of all of the activity in the text window.  I guess this is called full duplex audio.  If I turn off the monitor feature then I don't get the black type just the green type.   I'll have to see which one I like because it's nice to hear your transmission but turning it off will make the receive window easier to read.

              73, Ron ny3j

              On 11/5/2013 5:28 AM, Rick Muething wrote:
               

              Mark, Howard,

               

              Re  Session text Box:

              The concept I used in the session text box (which is always logged to the Chat <date>.log) has the full text of the QSO along with status info contained in one text window. This includes the text sent (now in Green Italic type) and the text received (in normal black type for FEC). In the log (which is not rich text to reduce log bulk) the sent and received text are indicated by keys e.g. {Rcvd FEC text} etc.  This permits going back in the log and being able to read in time sequence the text (from both ends) as it was sent and received.

               

              Unless you are using full duplex (not likely at least on HF) or just testing with full duplex audio)  the sent and received text will not be the same in the Session window (e.g. Your receiver is usually blanked when the transceiver is keyed unless you have a RF monitor enabled. ) If you are using an audio loop back (sound card audio out connected directly (or acoustically) to sound card audio in) you of course will see the Sent (green italic text) immediately followed by the received text (black normal text). But this is not the normal way the program is used with a radio.

               

              The reason transmitted text is entered into a separate window is to allow editing (backspace, delete etc.) BEFORE text is committed to the outbound Queue which then becomes un editable. The cursor control is set up so that you can’t go back and edit text already sent to the outbound Queue (though you can Capture it to the clipboard).

               

              I am open for other ways to do this but this has been worked out (similar version in the old V4Chat) and generally has been well received by users.   The one customizing feature that is asked for is various ways to “commit” the text to the output queue so there are now 4 options to select this …its really a matter of personal preference.  I personally use the CR or double space as the “commit text” option.

               



            • Rick Muething
              Ron, Well yes I guess we do learn something every day…I have a TS-590S too and never fiddled with or knew there was a receive monitor! I don’t think the
              Message 6 of 11 , Nov 5, 2013
              • 0 Attachment

                Ron,

                 

                Well yes I guess we do learn something every day…I have a TS-590S too and  never fiddled with or knew there was a receive monitor!

                 

                I don’t think the TS590S (or most HF radios) can really operate full duplex well…that is Listen to one DISTANT  station on one frequency while SIMULTANEOUSLY  transmitting on a DIFFERENT frequency on the same or another band.   Most HF radio receivers will overload and anyway you would need two separate antennas.  The H4TNC will support that full duplex operation (On FEC mode the Playback (Send) and Capture (Receive) functions are independent and can operate simultaneously) but normally it would not be used for monitoring your OWN transmission (except for testing).

                 

                If it really is a problem (with the confusing double text) I can easily put an option to suppress the full duplex function (Disable receive if PTT is active) but that should be selectable since “back-to-back audio” connections are useful for local testing and for training (e.g. Two laptops…Speaker output  of each going to the mic input of the other) .  I have used such kind of setups in training for WINMOR before.

                 

                ARQ is a different animal. It is much more complex to try and provide full duplex ARQ and since it is not very practical “over the air”  it seems like a lot of effort and complexity for no real gain or purpose.   Creating a full duplex ARQ protocol on HF is tricky (both sides would have to be both ISS (sending station) and IRS (receiving station) SIMULTANEOUSLY!)  

                 

                Thanks for the feedback.

                 

                73,


                Rick KN6KB

                 

                 

                From: V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com] On Behalf Of Ron Wenig
                Sent: Tuesday, November 05, 2013 8:05 AM
                To: V4Protocol@yahoogroups.com
                Subject: Re: [V4Protocol] Chat 0.1.7.0 Beta uploaded to Auto Update Server, Yahoo FTP and Winlink FTP sites

                 

                 

                Hi Rick,

                I learn something everyday in this hobby :-)

                I have a Kenwood TS-590 using the built in USB sound card.  When I turn on the monitor feature of the radio, so I can hear what is being transmitted, in the text window I will get black normal text and the green Italic text, which I thought was the way the program was designed and a little confusing because of all of the activity in the text window.  I guess this is called full duplex audio.  If I turn off the monitor feature then I don't get the black type just the green type.   I'll have to see which one I like because it's nice to hear your transmission but turning it off will make the receive window easier to read.

                73, Ron ny3j

                On 11/5/2013 5:28 AM, Rick Muething wrote:

                 

                Mark, Howard,

                 

                Re  Session text Box:

                The concept I used in the session text box (which is always logged to the Chat <date>.log) has the full text of the QSO along with status info contained in one text window. This includes the text sent (now in Green Italic type) and the text received (in normal black type for FEC). In the log (which is not rich text to reduce log bulk) the sent and received text are indicated by keys e.g. {Rcvd FEC text} etc.  This permits going back in the log and being able to read in time sequence the text (from both ends) as it was sent and received.

                 

                Unless you are using full duplex (not likely at least on HF) or just testing with full duplex audio)  the sent and received text will not be the same in the Session window (e.g. Your receiver is usually blanked when the transceiver is keyed unless you have a RF monitor enabled. ) If you are using an audio loop back (sound card audio out connected directly (or acoustically) to sound card audio in) you of course will see the Sent (green italic text) immediately followed by the received text (black normal text). But this is not the normal way the program is used with a radio.

                 

                The reason transmitted text is entered into a separate window is to allow editing (backspace, delete etc.) BEFORE text is committed to the outbound Queue which then becomes un editable. The cursor control is set up so that you can’t go back and edit text already sent to the outbound Queue (though you can Capture it to the clipboard).

                 

                I am open for other ways to do this but this has been worked out (similar version in the old V4Chat) and generally has been well received by users.   The one customizing feature that is asked for is various ways to “commit” the text to the output queue so there are now 4 options to select this …its really a matter of personal preference.  I personally use the CR or double space as the “commit text” option.

                 

                 

                 

              • Ron Wenig
                Rick, It s easier to turn off the monitor feature in the 590. It actually makes for a quieter operation. I thought the monitor was just a local receive
                Message 7 of 11 , Nov 5, 2013
                • 0 Attachment
                  Rick,

                  It's easier to turn off the monitor feature in the 590.  It actually makes for a quieter operation.  I thought the monitor was just a local receive function but it looks like there is feedback to the USB connection as well.  Thanks for the information, very interesting.

                  73, Ron ny3j

                  On 11/5/2013 9:28 AM, Rick Muething wrote:
                   

                  Ron,

                   

                  Well yes I guess we do learn something every day…I have a TS-590S too and  never fiddled with or knew there was a receive monitor!

                   

                  I don’t think the TS590S (or most HF radios) can really operate full duplex well…that is Listen to one DISTANT  station on one frequency while SIMULTANEOUSLY  transmitting on a DIFFERENT frequency on the same or another band.   Most HF radio receivers will overload and anyway you would need two separate antennas.  The H4TNC will support that full duplex operation (On FEC mode the Playback (Send) and Capture (Receive) functions are independent and can operate simultaneously) but normally it would not be used for monitoring your OWN transmission (except for testing).

                   

                  If it really is a problem (with the confusing double text) I can easily put an option to suppress the full duplex function (Disable receive if PTT is active) but that should be selectable since “back-to-back audio” connections are useful for local testing and for training (e.g. Two laptops…Speaker output  of each going to the mic input of the other) .  I have used such kind of setups in training for WINMOR before.

                   

                  ARQ is a different animal. It is much more complex to try and provide full duplex ARQ and since it is not very practical “over the air”  it seems like a lot of effort and complexity for no real gain or purpose.   Creating a full duplex ARQ protocol on HF is tricky (both sides would have to be both ISS (sending station) and IRS (receiving station) SIMULTANEOUSLY!)  

                   

                  Thanks for the feedback.

                   

                  73,


                  Rick KN6KB

                   

                   


                • Rick Muething
                  Ron, Yes I really like these radios with the built in sound cards. We have done some testing with them and the sample rate accuracy and stability of the sound
                  Message 8 of 11 , Nov 5, 2013
                  • 0 Attachment

                    Ron,

                     

                    Yes I really like these radios with the built in sound cards.  We have done some testing with them and the sample rate accuracy and stability of the sound cards are excellent.  Also of course they are much more “RF resistant” for the audio and you can’t beat the one cable plug and play.  It probably only adds a few bucks to the cost of the radio so I suspect we’ll see most of the newer HF radios including the USB interface and built in sound card.  The only downside is they require some radio model specific control codes to toggle the Aux port between Internal Sound card and External AUX input. (of course this can be done by menu on the radio too if needed)

                     

                    Rick KN6KB

                     

                  • Don Poaps
                    Ft 920. Still not picking up VFO data from ft 920. USB Digital com 3 4800 enable RTS check enable DTR check. Nothing changed from previous version. I
                    Message 9 of 11 , Nov 5, 2013
                    • 0 Attachment
                      Ft 920. Still not picking up VFO data from ft 920. > USB Digital > com 3 > 4800 enable RTS check > enable DTR check. Nothing changed from previous version. 

                       I notice that it's not going into USB digital even though in radio setup it's checked

                      Don va7dgp

                      On Tuesday, November 5, 2013, Rick Muething wrote:
                       

                      Ron,

                       

                      Yes I really like these radios with the built in sound cards.  We have done some testing with them and the sample rate accuracy and stability of the sound cards are excellent.  Also of course they are much more “RF resistant” for the audio and you can’t beat the one cable plug and play.  It probably only adds a few bucks to the cost of the radio so I suspect we’ll see most of the newer HF radios including the USB interface and built in sound card.  The only downside is they require some radio model specific control codes to toggle the Aux port between Internal Sound card and External AUX input. (of course this can be done by menu on the radio too if needed)

                       

                      Rick KN6KB

                       



                      --
                      Don Poaps
                      New Westminster, BC
                      VA7DGP
                      Satern Member
                      Vector Member
                      Surrey Amateur Radio
                      Metrotown Salvation Army Community Church Member
                       
                       

                    • Rick Muething
                      Don, Well the Yaesu documentation is so poor it make Icom s look good (and they aren t!) I have the manual for the 920 and I thought I have the right op code
                      Message 10 of 11 , Nov 5, 2013
                      • 0 Attachment

                        Don,

                         

                        Well the Yaesu documentation is so poor it make Icom’s look good (and they aren’t!)   I have the manual for the 920 and I thought I have the right op code and format.  Is the setting frequency, setting mode  and readback not working?  If readback is working the frequency should show on the bottom of the waterfall of the H4TNC and follow as you move the receiver dial.

                         

                        Thanks,

                         

                        Rick

                         

                         

                        From: V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com] On Behalf Of Don Poaps
                        Sent: Tuesday, November 05, 2013 11:03 AM
                        To: V4Protocol@yahoogroups.com
                        Subject: Re: [V4Protocol] Chat 0.1.7.0 Beta uploaded to Auto Update Server, Yahoo FTP and Winlink FTP sites

                         

                         

                        Ft 920. Still not picking up VFO data from ft 920. > USB Digital > com 3 > 4800 enable RTS check > enable DTR check. Nothing changed from previous version. 

                         

                         I notice that it's not going into USB digital even though in radio setup it's checked

                         

                        Don va7dgp

                        On Tuesday, November 5, 2013, Rick Muething wrote:

                         

                        Ron,

                         

                        Yes I really like these radios with the built in sound cards.  We have done some testing with them and the sample rate accuracy and stability of the sound cards are excellent.  Also of course they are much more “RF resistant” for the audio and you can’t beat the one cable plug and play.  It probably only adds a few bucks to the cost of the radio so I suspect we’ll see most of the newer HF radios including the USB interface and built in sound card.  The only downside is they require some radio model specific control codes to toggle the Aux port between Internal Sound card and External AUX input. (of course this can be done by menu on the radio too if needed)

                         

                        Rick KN6KB

                         



                        --

                        Don Poaps

                        New Westminster, BC

                        VA7DGP

                        Satern Member

                        Vector Member

                        Surrey Amateur Radio

                        Metrotown Salvation Army Community Church Member

                         

                         

                         

                      • David Michael Gaytko // WD4KPD
                        hello rick.... same problems here with ft920. there be no response from the rig to the inquires. the cat let on the rig is not blinking as it should when a
                        Message 11 of 11 , Nov 5, 2013
                        • 0 Attachment
                          hello rick....

                          same problems here with ft920. there be no response from the rig to the
                          inquires. the "cat" let on the rig is not blinking as it should when a
                          connection has been made to a program. i would ask you to check in the
                          guts to see if the number of stop bits is set to "2".

                          fldigi/dxlab commander and many other programs do work fine.

                          david/wd4kpd




                          On 11/5/2013 6:30 PM, Rick Muething wrote:
                          >
                          >
                          > Don,
                          >
                          > Well the Yaesu documentation is so poor it make Icom’s look good (and
                          > they aren’t!) I have the manual for the 920 and I thought I have the
                          > right op code and format. Is the setting frequency, setting mode and
                          > readback not working? If readback is working the frequency should show
                          > on the bottom of the waterfall of the H4TNC and follow as you move the
                          > receiver dial.
                          >
                          > Thanks,
                          >
                          > Rick
                          >
                          > *From:*V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com]
                          > *On Behalf Of *Don Poaps
                          > *Sent:* Tuesday, November 05, 2013 11:03 AM
                          > *To:* V4Protocol@yahoogroups.com
                          > *Subject:* Re: [V4Protocol] Chat 0.1.7.0 Beta uploaded to Auto Update
                          > Server, Yahoo FTP and Winlink FTP sites
                          >
                          > Ft 920. Still not picking up VFO data from ft 920. > USB Digital > com 3
                          > > 4800 enable RTS check > enable DTR check. Nothing changed from
                          > previous version.
                          >
                          > I notice that it's not going into USB digital even though in radio
                          > setup it's checked
                          >
                          > Don va7dgp
                          >
                          > On Tuesday, November 5, 2013, Rick Muething wrote:
                          >
                          > Ron,
                          >
                          > Yes I really like these radios with the built in sound cards. We have
                          > done some testing with them and the sample rate accuracy and stability
                          > of the sound cards are excellent. Also of course they are much more “RF
                          > resistant” for the audio and you can’t beat the one cable plug and
                          > play. It probably only adds a few bucks to the cost of the radio so I
                          > suspect we’ll see most of the newer HF radios including the USB
                          > interface and built in sound card. The only downside is they require
                          > some radio model specific control codes to toggle the Aux port between
                          > Internal Sound card and External AUX input. (of course this can be done
                          > by menu on the radio too if needed)
                          >
                          > Rick KN6KB
                          >
                          >
                          >
                          > --
                          >
                          > Don Poaps
                          >
                          > New Westminster, BC
                          >
                          > VA7DGP
                          >
                          > Satern Member
                          >
                          > Vector Member
                          >
                          > Surrey Amateur Radio
                          >
                          > Metrotown Salvation Army Community Church Member
                          >
                          >
                          >
                          >

                          --
                          -- But when a long train of abuses and usurpations, pursuing invariably
                          the same Object evinces a design to reduce them under absolute
                          Despotism, it is their right, it is their duty, to throw off such
                          Government, and to provide new Guards for their future security. --
                        Your message has been successfully submitted and would be delivered to recipients shortly.