Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

Lost Dots with PGXL and 6600M

James Charlton
James Charlton Member ✭✭

I received my PGXL a couple of weeks ago, connected it up to my router and 6600M (all hardwired, no wifi) and it seemed to work great. But as I worked faster CW contests (CWops) I discovered a problem wit leading dots.

My call sign, AD0AB, begins with a dot, but people were answering me as TD0AB indicating my leading dot was missing. This problem seems to occur above about 28-30wpm.

Using an oscilloscope, I looked at the RF coming out of the PGXL and sure enough, the leading dot was occasionally either missing or foreshortened. I checked the RF coming out of the 6600M and there was no sign of missing dots all the way up to 60wpm.

I found that if I operate the push to talk on the 6600M with an external switch which turns the PGXL on before it sees the first dot, the problem is gone. Note that this problem does not occur with a string of dots or dots and dashes as the 6600M/PGXL stay on for the duration of the string. Therefore I believe that this problem has something to do with the speed at which the PGXL switches from receive to transmit.

My setup is a paddle driving an external Winkeyer connected as a straight key to my 6600M. I do not use the 6600M's internal keyer. The 6600M is connected to the PGXL exactly as specified in the instructions. They communicate via hard-wired Ethernet connections to a Netgear Nighthawk X10 router.

What can I do to stop losing the leading dots?


Jim Charlton AD0AB


  • KD0RC
    KD0RC Member, Super Elmer Moderator

    Hi Jim, Can you dial in a little delay so that the 6600 waits for the PGXL to be ready?


    Len, KD0RC

  • Hi Len,

    Thanks for the suggestion. I would try that, but I'm not sure what setting to change. The PGXL instructions say that the appropirate delay is already incorporated when the amp is connected to a Flex radio.



  • KD0RC
    KD0RC Member, Super Elmer Moderator

    There is a TX Delay if you go to Settings, Radio Setup TX tab. At 40 WPM a dot is 6 ms, so that might be a good starting point.


  • WX7Y
    WX7Y Member ✭✭✭

    Would be helpful to know what version of SmartSDR and PGXL firmware your running?

    running any TX Delay?

    Running Ethernet Keying on the AMP or a PTT line?

    for now you might try adding about 15-20MS on TX-Delay and give that a go until a firmware is released to fix this.

    With the newness of the AMP it is VERY important to update to the latest release firmware.

  • Sergey KN7K
    Sergey KN7K Member ✭✭✭

    Thats what i use with PGXL - no problem

    Sergey, KN7K

  • Len, Bret, Sergey,

    Thanks for the suggestions, I'll try them. The transceiver is running version 3.1.12 software and the amp is running v3.4.16. I believe these are the latest versions.

    Currently, there are no transmit delays set in the transceiver. I will try the suggestions.

    PTT is provided via the Ethernet connection as described in the amp's manual. I have not yet tried running a separate PTT connection from the transceiver to the amp. But I will.

    I'll also try the TX Tab set up shown above.

    Thanks for the suggestions, I'll post what I find.


    Jim Charlton AD0AB

  • K5XH
    K5XH Member ✭✭

    You might check out a previous post: https://community.flexradio.com/discussion/7877351/flexradios-cw-failings

    This has been reported before. Might not be the exact circumstances that you are encountering. If I remember correctly the problem showed up after 2.4.9.

    I have not encountered this but I run a much slower CW speeds.

    73, Mark K5XH

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.