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

Chat 0.1.5.0 Uploaded to Yahoo FTP, Winlink FTP server and Autoupdate server.

Expand Messages
  • Rick Muething
    All, Persistence pays off!!! I finally found and fixed the major bug limiting the tuning range. With 0.1.5.0 the automatic tuning range as specified in the
    Message 1 of 9 , Oct 21, 2013
    • 0 Attachment

      All,

       

      Persistence pays off!!!  I finally found and fixed the major bug limiting the tuning range.  With 0.1.5.0 the automatic tuning range as specified in the Chat setup is fully operational.  A good operating point is 50 Hz (Tunes for offsets of +/- 50 Hz) but this can be set anywhere from 10 to 100 Hz.  A recommended squelch value is 4 or 5.  Squelch values of 3 or even 2 can be used for very weak signal copying but these will increase the amount of “open” printing.

       

      I will be heading out of town for about 10 days on Thurs (Oct 24th ) so probably won’t be able to make many more updates.  This seems pretty solid and I will now start to work on the ARQ mode (probably will be a month or so).

       

      The full install package is available on the Yahoo V4Protocol FTP site and the Winlink FTP site ftp://autoupdate.winlink.org/User%20Programs/

       

      Appreciate your feedback and comments.   I will leave my beacon on at 10123.00 USB dial running 10 watts.

       

      73,

       

      Rick KN6KB

       

       

       

       

      Chat Revision History

       

      Date:                     Rev        Change Summary

       

      Oct 21, 2013        0.1.5.0   Release of 0.1.4.1

       

      Oct 20, 2013        0.1.4.1 Clean up Exception logging with respect to file system errors and capture error # to Exception log.

                                                      Indicate when beacon sent on main log (purple)

                                                      Change Globals.TimestampEX to not show decimal seconds.

                                                      Add detect and recovery code in grdContacts_MouseClick to handle exception if grid is right clicked without a row selected. 

       

      Oct 19, 2013        0.1.4.0   Release with H4TNC main menu bar backcolor changed to accomodate classic windows setup (was too dark). No changes to Chat from 0.1.3.0

       

      Oct 18, 2013        0.1.3.0   Release of 0.1.2.1 to beta

       

      Oct 16, 2013        0.1.2.1 Change default leader length from 200 ms to 128 ms

                                                      Change default Tuning range from 100 to 50 Hz.

                                                      Allow call signs to include Prefix (e.g. "XE2/") or postfix (e.g. "/MM") in addition to -ssids.

                                                      Hold off any beacons for beacon interval minutes in FEC mode after manual keyboard entry.

                                                      Change default character set to ASCII (7 bit)

                                                     

       

       

       H4FSK TNC Revision History

       

      Date:                     Rev                        Change Summary

       

      Oct 21, 2012        0.1.5.0                   Release of 0.1.4.1

       

      Oct 21, 2013        0.1.4.1                   Make mods in H4Demod.ProcessNewSamples to base detection of sync in TUNE state dependent on prior and next cor values. This

                                                                      Improves tuning accuracy, sync detection and reduces "open" printing on low values of squelch.

                                                                      Redcuce and cleanup Debug logging.

                                                                      Modify H4Demod.TrackTwoTone62BMix to use squelch to compute ratio and use uninterpolated bin values for dblMaxCor calculation.

                                                                      Fix H4Demod.SearchForSymbolSync62BMix to use mixed data and bin 6 for Goertzel phase search.(was bin 12) Now have full tuning range. 

       

      Oct 19, 2013        0.1.4.0                   Change of backcolor on H4TNC menu line to Gradient Active to avoid too dark a background in classic windows setup. No other changes. 

       

      Oct 18, 2013        0.1.3.0                   Release of 0.1.2.1 to beta

       

      Oct 18, 2013        0.1.2.1                   Allow call signs to include Prefix (e.g. "XE2/") or postfix (e.g. "/MM") in addition to -ssids.

                                                                      Change Rcvd Frame lables to "Sync" and "Data" (was "FEC Sync" and "FEC Data") in preparation for ARQ mode.

                                                                      Replace H4Demod.Decode8BitCharacter with MixDecode8BitCharacter using NCO (nominal frequency 1125 Hz) to mix

                                                                      filtered data down to 375 Hz (center bin) for wider "tuning" and more optimal center-of-bin decoding.

                                                                      Add second overload of H4Demod.GoertzelRealImag for floating input

                                                                      Add H4Demod.TrackTwoTone62BMix to replace TrackTwoTone62B with floating point mixing to 375 Hz center.

                                                                      Add menu display and toggle of current character set.

                                                                      Added current MY CALL to the main window description.

                                                                      In H4Mod.GenerateSync62Baud Reduce peak amplitude of sync to same as 4FSK tones to reduce opportunity of sync amplitude distortion.

                                                                      Extensive modifications in H4Demod.SearchForSymbolSync62BMix, SearchForSync62B, TrackTwoTone62BMix for improved signal acquisition and tracking

                                                                      Modify SearchForTwoTone63BG to add (H4CB.Squelch/10) to the ratio calculation

                                                                      Fix Interface.TWOTONETEST function to allow repeats. (now works either from TNC menu or Chat Setup menu correctly)

                                                                      Update Help

                                                                     

    • k1dow_4
      Excellent improvement in Chat 0.1.5.0 Rick! Printing your beacon and a handful of others this Monday afternoon in Arcadia, FL. A small suggestion regarding the
      Message 2 of 9 , Oct 21, 2013
      • 0 Attachment

        Excellent improvement in Chat 0.1.5.0 Rick! Printing your beacon and a handful of others this Monday afternoon in Arcadia, FL. 


        A small suggestion regarding the choice of RX text color on the RX screen. It appears as green on a pale orange background here. For my vision black would be a lot easier to read. Understood though if there is a need for the color of the text being set as it is now. No problem. The MAIN THING is that the decode and expanded capture area on the WF is mucho improved! Congratulations on your persistence Rick! :-)


        73/Russ

        K1DOW

        Arcadia, FL





        ---In V4Protocol@yahoogroups.com, <v4protocol@yahoogroups.com> wrote:

        All,

         

        Persistence pays off!!!  I finally found and fixed the major bug limiting the tuning range.  With 0.1.5.0 the automatic tuning range as specified in the Chat setup is fully operational.  A good operating point is 50 Hz (Tunes for offsets of +/- 50 Hz) but this can be set anywhere from 10 to 100 Hz.  A recommended squelch value is 4 or 5.  Squelch values of 3 or even 2 can be used for very weak signal copying but these will increase the amount of “open” printing.

         

        I will be heading out of town for about 10 days on Thurs (Oct 24th ) so probably won’t be able to make many more updates.  This seems pretty solid and I will now start to work on the ARQ mode (probably will be a month or so).

         

        The full install package is available on the Yahoo V4Protocol FTP site and the Winlink FTP site ftp://autoupdate.winlink.org/User%20Programs/

         

        Appreciate your feedback and comments.   I will leave my beacon on at 10123.00 USB dial running 10 watts.

         

        73,

         

        Rick KN6KB

         

         

         

         

        Chat Revision History

         

        Date:                     Rev        Change Summary

         

        Oct 21, 2013        0.1.5.0   Release of 0.1.4.1

         

        Oct 20, 2013        0.1.4.1 Clean up Exception logging with respect to file system errors and capture error # to Exception log.

                                                        Indicate when beacon sent on main log (purple)

                                                        Change Globals.TimestampEX to not show decimal seconds.

                                                        Add detect and recovery code in grdContacts_MouseClick to handle exception if grid is right clicked without a row selected. 

         

        Oct 19, 2013        0.1.4.0   Release with H4TNC main menu bar backcolor changed to accomodate classic windows setup (was too dark). No changes to Chat from 0.1.3.0

         

        Oct 18, 2013        0.1.3.0   Release of 0.1.2.1 to beta

         

        Oct 16, 2013        0.1.2.1 Change default leader length from 200 ms to 128 ms

                                                        Change default Tuning range from 100 to 50 Hz.

                                                        Allow call signs to include Prefix (e.g. "XE2/") or postfix (e.g. "/MM") in addition to -ssids.

                                                        Hold off any beacons for beacon interval minutes in FEC mode after manual keyboard entry.

                                                        Change default character set to ASCII (7 bit)

                                                       

         

         

         H4FSK TNC Revision History

         

        Date:                     Rev                        Change Summary

         

        Oct 21, 2012        0.1.5.0                   Release of 0.1.4.1

         

        Oct 21, 2013        0.1.4.1                   Make mods in H4Demod.ProcessNewSamples to base detection of sync in TUNE state dependent on prior and next cor values. This

                                                                        Improves tuning accuracy, sync detection and reduces "open" printing on low values of squelch.

                                                                        Redcuce and cleanup Debug logging.

                                                                        Modify H4Demod.TrackTwoTone62BMix to use squelch to compute ratio and use uninterpolated bin values for dblMaxCor calculation.

                                                                        Fix H4Demod.SearchForSymbolSync62BMix to use mixed data and bin 6 for Goertzel phase search.(was bin 12) Now have full tuning range. 

         

        Oct 19, 2013        0.1.4.0                   Change of backcolor on H4TNC menu line to Gradient Active to avoid too dark a background in classic windows setup. No other changes. 

         

        Oct 18, 2013        0.1.3.0                   Release of 0.1.2.1 to beta

         

        Oct 18, 2013        0.1.2.1                   Allow call signs to include Prefix (e.g. "XE2/") or postfix (e.g. "/MM") in addition to -ssids.

                                                                        Change Rcvd Frame lables to "Sync" and "Data" (was "FEC Sync" and "FEC Data") in preparation for ARQ mode.

                                                                        Replace H4Demod.Decode8BitCharacter with MixDecode8BitCharacter using NCO (nominal frequency 1125 Hz) to mix

                                                                        filtered data down to 375 Hz (center bin) for wider "tuning" and more optimal center-of-bin decoding.

                                                                        Add second overload of H4Demod.GoertzelRealImag for floating input

                                                                        Add H4Demod.TrackTwoTone62BMix to replace TrackTwoTone62B with floating point mixing to 375 Hz center.

                                                                        Add menu display and toggle of current character set.

                                                                        Added current MY CALL to the main window description.

                                                                        In H4Mod.GenerateSync62Baud Reduce peak amplitude of sync to same as 4FSK tones to reduce opportunity of sync amplitude distortion.

                                                                        Extensive modifications in H4Demod.SearchForSymbolSync62BMix, SearchForSync62B, TrackTwoTone62BMix for improved signal acquisition and tracking

                                                                        Modify SearchForTwoTone63BG to add (H4CB.Squelch/10) to the ratio calculation

                                                                        Fix Interface.TWOTONETEST function to allow repeats. (now works either from TNC menu or Chat Setup menu correctly)

                                                                        Update Help

                                                                       

      • Rick Muething
        Thanks for the feedback Russ. Well there is a need to support several colors on the received text (currently Green, Red, Navy, Black, Purple). When I
        Message 3 of 9 , Oct 21, 2013
        • 0 Attachment

          Thanks for the feedback Russ.  Well there is a need to support several colors on the received text (currently Green, Red, Navy, Black, Purple).  When I switched the background over to the beige and light blue I didn’t change any of the text colors.  I’ll play with that some.  There are probably better choices.


          Rick

           

           

           

           

          From: V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com] On Behalf Of russtower@...
          Sent: Monday, October 21, 2013 3:15 PM
          To: V4Protocol@yahoogroups.com
          Subject: [V4Protocol] RE: Chat 0.1.5.0 Uploaded to Yahoo FTP, Winlink FTP server and Autoupdate server.

           

           

          Excellent improvement in Chat 0.1.5.0 Rick! Printing your beacon and a handful of others this Monday afternoon in Arcadia, FL. 

           

          A small suggestion regarding the choice of RX text color on the RX screen. It appears as green on a pale orange background here. For my vision black would be a lot easier to read. Understood though if there is a need for the color of the text being set as it is now. No problem. The MAIN THING is that the decode and expanded capture area on the WF is mucho improved! Congratulations on your persistence Rick! :-)

           

          73/Russ

          K1DOW

          Arcadia, FL

           

           



          ---In V4Protocol@yahoogroups.com, <v4protocol@yahoogroups.com> wrote:

          All,

           

          Persistence pays off!!!  I finally found and fixed the major bug limiting the tuning range.  With 0.1.5.0 the automatic tuning range as specified in the Chat setup is fully operational.  A good operating point is 50 Hz (Tunes for offsets of +/- 50 Hz) but this can be set anywhere from 10 to 100 Hz.  A recommended squelch value is 4 or 5.  Squelch values of 3 or even 2 can be used for very weak signal copying but these will increase the amount of “open” printing.

           

          I will be heading out of town for about 10 days on Thurs (Oct 24th ) so probably won’t be able to make many more updates.  This seems pretty solid and I will now start to work on the ARQ mode (probably will be a month or so).

           

          The full install package is available on the Yahoo V4Protocol FTP site and the Winlink FTP site ftp://autoupdate.winlink.org/User%20Programs/

           

          Appreciate your feedback and comments.   I will leave my beacon on at 10123.00 USB dial running 10 watts.

           

          73,

           

          Rick KN6KB

           

           

           

           

          Chat Revision History

           

          Date:                     Rev        Change Summary

           

          Oct 21, 2013        0.1.5.0   Release of 0.1.4.1

           

          Oct 20, 2013        0.1.4.1 Clean up Exception logging with respect to file system errors and capture error # to Exception log.

                                                          Indicate when beacon sent on main log (purple)

                                                          Change Globals.TimestampEX to not show decimal seconds.

                                                          Add detect and recovery code in grdContacts_MouseClick to handle exception if grid is right clicked without a row selected. 

           

          Oct 19, 2013        0.1.4.0   Release with H4TNC main menu bar backcolor changed to accomodate classic windows setup (was too dark). No changes to Chat from 0.1.3.0

           

          Oct 18, 2013        0.1.3.0   Release of 0.1.2.1 to beta

           

          Oct 16, 2013        0.1.2.1 Change default leader length from 200 ms to 128 ms

                                                          Change default Tuning range from 100 to 50 Hz.

                                                          Allow call signs to include Prefix (e.g. "XE2/") or postfix (e.g. "/MM") in addition to -ssids.

                                                          Hold off any beacons for beacon interval minutes in FEC mode after manual keyboard entry.

                                                          Change default character set to ASCII (7 bit)

                                                         

           

           

           H4FSK TNC Revision History

           

          Date:                     Rev                        Change Summary

           

          Oct 21, 2012        0.1.5.0                   Release of 0.1.4.1

           

          Oct 21, 2013        0.1.4.1                   Make mods in H4Demod.ProcessNewSamples to base detection of sync in TUNE state dependent on prior and next cor values. This

                                                                          Improves tuning accuracy, sync detection and reduces "open" printing on low values of squelch.

                                                                          Redcuce and cleanup Debug logging.

                                                                          Modify H4Demod.TrackTwoTone62BMix to use squelch to compute ratio and use uninterpolated bin values for dblMaxCor calculation.

                                                                          Fix H4Demod.SearchForSymbolSync62BMix to use mixed data and bin 6 for Goertzel phase search.(was bin 12) Now have full tuning range. 

           

          Oct 19, 2013        0.1.4.0                   Change of backcolor on H4TNC menu line to Gradient Active to avoid too dark a background in classic windows setup. No other changes. 

           

          Oct 18, 2013        0.1.3.0                   Release of 0.1.2.1 to beta

           

          Oct 18, 2013        0.1.2.1                   Allow call signs to include Prefix (e.g. "XE2/") or postfix (e.g. "/MM") in addition to -ssids.

                                                                          Change Rcvd Frame lables to "Sync" and "Data" (was "FEC Sync" and "FEC Data") in preparation for ARQ mode.

                                                                          Replace H4Demod.Decode8BitCharacter with MixDecode8BitCharacter using NCO (nominal frequency 1125 Hz) to mix

                                                                          filtered data down to 375 Hz (center bin) for wider "tuning" and more optimal center-of-bin decoding.

                                                                          Add second overload of H4Demod.GoertzelRealImag for floating input

                                                                          Add H4Demod.TrackTwoTone62BMix to replace TrackTwoTone62B with floating point mixing to 375 Hz center.

                                                                          Add menu display and toggle of current character set.

                                                                          Added current MY CALL to the main window description.

                                                                          In H4Mod.GenerateSync62Baud Reduce peak amplitude of sync to same as 4FSK tones to reduce opportunity of sync amplitude distortion.

                                                                          Extensive modifications in H4Demod.SearchForSymbolSync62BMix, SearchForSync62B, TrackTwoTone62BMix for improved signal acquisition and tracking

                                                                          Modify SearchForTwoTone63BG to add (H4CB.Squelch/10) to the ratio calculation

                                                                          Fix Interface.TWOTONETEST function to allow repeats. (now works either from TNC menu or Chat Setup menu correctly)

                                                                          Update Help

                                                                         

        • Harry Gilling
          Have had a successful QSO using H4. I have the following problems: When entering text into the text box it is not blue. It is grey and remains grey after
          Message 4 of 9 , Oct 21, 2013
          • 0 Attachment
            Have had a successful QSO using H4.  I have the following problems:

            When entering text into the text box it is not blue.  It is grey and remains grey after transmission

            Transmit data does not appear in the beige session box

            OB Queue does not appear

            Scroll is not locked

            Did I miss something in the setup?

            Thanks  Harry  W9IB
          • Bastress, David G
            Harry, Tnx for the short qso around 1 PM EDST. Had to get back to work. There were several other stations in there at about the same time. I don t think
            Message 5 of 9 , Oct 21, 2013
            • 0 Attachment
              Harry,
               
              Tnx for the short qso around 1 PM EDST.  Had to get back to work.
               
              There were several other stations in there at about the same time.  I don't think everyone was copying each other.
               
              H4 seems to be working ok on my old XP computer.
              73,
              Dave K3GAU 


              On Mon, Oct 21, 2013 at 4:11 PM, Harry Gilling <w9ib73@...> wrote:
               

              Have had a successful QSO using H4.  I have the following problems:

              When entering text into the text box it is not blue.  It is grey and remains grey after transmission

              Transmit data does not appear in the beige session box

              OB Queue does not appear

              Scroll is not locked

              Did I miss something in the setup?

              Thanks  Harry  W9IB


            • Rick Muething
              Harry, There are some minor issues that I am cleaning up but some of your comments don t apply. First you have 4 choices of how to enter text and queue it.I
              Message 6 of 9 , Oct 21, 2013
              • 0 Attachment

                Harry,

                 

                There are some minor issues that I am cleaning up but some of your comments don’t apply.

                 

                First you have 4 choices of how to enter text and queue it…I would recommend using CR to start (send on a CR). You can play with the other …personal preference.  When you enter text BEFORE it is sent it is blue italic in the lower box.  You can edit it there before it is sent.  When it is transferred to the H4 TNC for transmission (CR, Ctrl CR, Word, etc) it is changed to gray and can no longer be edited (it is being sent).

                 

                Received text is shown in the upper window as received. It is currently green …may change that on next rev for improved readability.   The transmitted data is NOT shown in the beige box currently. I’ll look into that …it might make it more readable

                 

                I will try and confirm everything works like above before the next release…but no one reporting any problems with it and I made several QSOs today.

                 

                OB Queue was not implemented on that last rev 0.1.5.0.   Will be on the next.  It buffers allowing you to send while things are still being sent …they just queue up and show in the outbound queue.  Once sending is finished (EOT sent) if there is anything in the out bound queue it will be sent.  I have this working now here.  I will also have the auto ID feature working on the next rev.

                 

                One of the challenges here is there are umpteen ways to show text, colors, sizes etc and it is impossible to please everyone and making it completely customizable is a big effort. I have tried to put in the more useful options (e.g. Send commands and text size)  but at this stage of the program I don’t want to get bogged down in all the frills of text display. It may look simple but handling scrolling rich text boxes of multiple colors is a real programming challenge.

                 

                Thanks for your feedback.


                Rick KN6KB

                 

                 

                From: V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com] On Behalf Of Harry Gilling
                Sent: Monday, October 21, 2013 4:11 PM
                To: V4Protocol@yahoogroups.com
                Subject: [V4Protocol] RE: Chat 0.1.5.0 Uploaded to Yahoo FTP, Winlink FTP server and Autoupdate server.

                 

                 

                Have had a successful QSO using H4.  I have the following problems:

                 

                When entering text into the text box it is not blue.  It is grey and remains grey after transmission

                 

                Transmit data does not appear in the beige session box

                 

                OB Queue does not appear

                 

                Scroll is not locked

                 

                Did I miss something in the setup?

                 

                Thanks  Harry  W9IB

              • oh5rm
                Hi Rick, Have been testing 0.1.5.0 on 80m with OH hams. Some garbage letters but mostly good copy. Prints Scandinavian letters OK with Latin-1 chr-set. 73
                Message 7 of 9 , Oct 22, 2013
                • 0 Attachment

                   Hi Rick,


                  Have been testing 0.1.5.0 on 80m with OH hams.


                  Some garbage letters but mostly good copy.

                  Prints Scandinavian letters OK with Latin-1 chr-set.


                  73 Jouko OH5RM



                  ---In v4protocol@yahoogroups.com, <rmuething@...> wrote:

                  Harry,

                   

                  There are some minor issues that I am cleaning up but some of your comments don’t apply.

                   

                  First you have 4 choices of how to enter text and queue it…I would recommend using CR to start (send on a CR). You can play with the other …personal preference.  When you enter text BEFORE it is sent it is blue italic in the lower box.  You can edit it there before it is sent.  When it is transferred to the H4 TNC for transmission (CR, Ctrl CR, Word, etc) it is changed to gray and can no longer be edited (it is being sent).

                   

                  Received text is shown in the upper window as received. It is currently green …may change that on next rev for improved readability.   The transmitted data is NOT shown in the beige box currently. I’ll look into that …it might make it more readable

                   

                  I will try and confirm everything works like above before the next release…but no one reporting any problems with it and I made several QSOs today.

                   

                  OB Queue was not implemented on that last rev 0.1.5.0.   Will be on the next.  It buffers allowing you to send while things are still being sent …they just queue up and show in the outbound queue.  Once sending is finished (EOT sent) if there is anything in the out bound queue it will be sent.  I have this working now here.  I will also have the auto ID feature working on the next rev.

                   

                  One of the challenges here is there are umpteen ways to show text, colors, sizes etc and it is impossible to please everyone and making it completely customizable is a big effort. I have tried to put in the more useful options (e.g. Send commands and text size)  but at this stage of the program I don’t want to get bogged down in all the frills of text display. It may look simple but handling scrolling rich text boxes of multiple colors is a real programming challenge.

                   

                  Thanks for your feedback.


                  Rick KN6KB

                   

                   

                  From: V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com] On Behalf Of Harry Gilling
                  Sent: Monday, October 21, 2013 4:11 PM
                  To: V4Protocol@yahoogroups.com
                  Subject: [V4Protocol] RE: Chat 0.1.5.0 Uploaded to Yahoo FTP, Winlink FTP server and Autoupdate server.

                   

                   

                  Have had a successful QSO using H4.  I have the following problems:

                   

                  When entering text into the text box it is not blue.  It is grey and remains grey after transmission

                   

                  Transmit data does not appear in the beige session box

                   

                  OB Queue does not appear

                   

                  Scroll is not locked

                   

                  Did I miss something in the setup?

                   

                  Thanks  Harry  W9IB

                • Bastress, David G
                  GM Jouko, What frequency do you use on 80 meters? Dave K3GAU ... GM Jouko, á What frequency do you use on 80 meters? á Dave K3GAU On Tue, Oct 22, 2013 at
                  Message 8 of 9 , Oct 22, 2013
                  • 0 Attachment
                    GM Jouko,
                     
                    What frequency do you use on 80 meters?
                     
                    Dave K3GAU


                    On Tue, Oct 22, 2013 at 8:41 AM, <jn@...> wrote:
                     

                     Hi Rick,


                    Have been testing 0.1.5.0 on 80m with OH hams.


                    Some garbage letters but mostly good copy.

                    Prints Scandinavian letters OK with Latin-1 chr-set.


                    73 Jouko OH5RM



                    ---In v4protocol@yahoogroups.com, <rmuething@...> wrote:

                    Harry,

                     

                    There are some minor issues that I am cleaning up but some of your comments don’t apply.

                     

                    First you have 4 choices of how to enter text and queue it…I would recommend using CR to start (send on a CR). You can play with the other …personal preference.  When you enter text BEFORE it is sent it is blue italic in the lower box.  You can edit it there before it is sent.  When it is transferred to the H4 TNC for transmission (CR, Ctrl CR, Word, etc) it is changed to gray and can no longer be edited (it is being sent).

                     

                    Received text is shown in the upper window as received. It is currently green …may change that on next rev for improved readability.   The transmitted data is NOT shown in the beige box currently. I’ll look into that …it might make it more readable

                     

                    I will try and confirm everything works like above before the next release…but no one reporting any problems with it and I made several QSOs today.

                     

                    OB Queue was not implemented on that last rev 0.1.5.0.   Will be on the next.  It buffers allowing you to send while things are still being sent …they just queue up and show in the outbound queue.  Once sending is finished (EOT sent) if there is anything in the out bound queue it will be sent.  I have this working now here.  I will also have the auto ID feature working on the next rev.

                     

                    One of the challenges here is there are umpteen ways to show text, colors, sizes etc and it is impossible to please everyone and making it completely customizable is a big effort. I have tried to put in the more useful options (e.g. Send commands and text size)  but at this stage of the program I don’t want to get bogged down in all the frills of text display. It may look simple but handling scrolling rich text boxes of multiple colors is a real programming challenge.

                     

                    Thanks for your feedback.


                    Rick KN6KB

                     

                     

                    From: V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com] On Behalf Of Harry Gilling
                    Sent: Monday, October 21, 2013 4:11 PM
                    To: V4Protocol@yahoogroups.com
                    Subject: [V4Protocol] RE: Chat 0.1.5.0 Uploaded to Yahoo FTP, Winlink FTP server and Autoupdate server.

                     

                     

                    Have had a successful QSO using H4.  I have the following problems:

                     

                    When entering text into the text box it is not blue.  It is grey and remains grey after transmission

                     

                    Transmit data does not appear in the beige session box

                     

                    OB Queue does not appear

                     

                    Scroll is not locked

                     

                    Did I miss something in the setup?

                     

                    Thanks  Harry  W9IB


                  • Rick Muething
                    Thanks Jouko, One of the objectives I have for the protocol and Chat Host is to work well with all the main character sets. The Latin-1 ASCII extension and
                    Message 9 of 9 , Oct 22, 2013
                    • 0 Attachment

                      Thanks Jouko,

                       

                      One of the objectives I have for the protocol and Chat Host is to work well with all the main character sets.  The Latin-1 ASCII extension and the UTF-8 (multi-byte) character sets allow many non-English characters and languages.  Hopefully this will promote adoption in foreign languages (I may ask for volunteers for help with multi language help etc!!!)

                       

                      With FEC there can always be some character errors (there is no automatic “back channel” to request repeats).  The amount of FEC I selected was (as always) an engineering compromise between speed (using weaker and less Robust FEC) and error correction capability (using stronger FEC coding).  I think the current selection is pretty close to optimum for normal signal level work.  With more time it should be possible to continue with small improvements in the tuning, sync and character decoding. Once the ARQ mode is working it will permit sessions with zero errors but of course it only permits two stations to be in communication not a net like FEC does and the throughput will only be about 60-70% or so of the current FEC mode which is now about 68 words per minute.

                       

                      73,

                       

                      Rick KN6KB

                       

                       

                      From: V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com] On Behalf Of jn@...
                      Sent: Tuesday, October 22, 2013 8:42 AM
                      To: V4Protocol@yahoogroups.com
                      Subject: [V4Protocol] RE: Chat 0.1.5.0 Uploaded to Yahoo FTP, Winlink FTP server and Autoupdate server.

                       

                       

                       Hi Rick,

                       

                      Have been testing 0.1.5.0 on 80m with OH hams.

                       

                      Some garbage letters but mostly good copy.

                      Prints Scandinavian letters OK with Latin-1 chr-set.

                       

                      73 Jouko OH5RM



                      ---In v4protocol@yahoogroups.com, <rmuething@...> wrote:

                      Harry,

                       

                      There are some minor issues that I am cleaning up but some of your comments don’t apply.

                       

                      First you have 4 choices of how to enter text and queue it…I would recommend using CR to start (send on a CR). You can play with the other …personal preference.  When you enter text BEFORE it is sent it is blue italic in the lower box.  You can edit it there before it is sent.  When it is transferred to the H4 TNC for transmission (CR, Ctrl CR, Word, etc) it is changed to gray and can no longer be edited (it is being sent).

                       

                      Received text is shown in the upper window as received. It is currently green …may change that on next rev for improved readability.   The transmitted data is NOT shown in the beige box currently. I’ll look into that …it might make it more readable

                       

                      I will try and confirm everything works like above before the next release…but no one reporting any problems with it and I made several QSOs today.

                       

                      OB Queue was not implemented on that last rev 0.1.5.0.   Will be on the next.  It buffers allowing you to send while things are still being sent …they just queue up and show in the outbound queue.  Once sending is finished (EOT sent) if there is anything in the out bound queue it will be sent.  I have this working now here.  I will also have the auto ID feature working on the next rev.

                       

                      One of the challenges here is there are umpteen ways to show text, colors, sizes etc and it is impossible to please everyone and making it completely customizable is a big effort. I have tried to put in the more useful options (e.g. Send commands and text size)  but at this stage of the program I don’t want to get bogged down in all the frills of text display. It may look simple but handling scrolling rich text boxes of multiple colors is a real programming challenge.

                       

                      Thanks for your feedback.


                      Rick KN6KB

                       

                       

                      From: V4Protocol@yahoogroups.com [mailto:V4Protocol@yahoogroups.com] On Behalf Of Harry Gilling
                      Sent: Monday, October 21, 2013 4:11 PM
                      To: V4Protocol@yahoogroups.com
                      Subject: [V4Protocol] RE: Chat 0.1.5.0 Uploaded to Yahoo FTP, Winlink FTP server and Autoupdate server.

                       

                       

                      Have had a successful QSO using H4.  I have the following problems:

                       

                      When entering text into the text box it is not blue.  It is grey and remains grey after transmission

                       

                      Transmit data does not appear in the beige session box

                       

                      OB Queue does not appear

                       

                      Scroll is not locked

                       

                      Did I miss something in the setup?

                       

                      Thanks  Harry  W9IB

                    Your message has been successfully submitted and would be delivered to recipients shortly.