<html><head><style id="eMClientCss">blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
.plain pre, .plain tt { font-family: monospace; font-size: 100%; font-weight: normal; font-style: normal;}
a img { border: 0px; }body {font-family: Tahoma;font-size: 12pt;}
.plain pre, .plain tt {font-family: Tahoma;font-size: 12pt;}
</style><style></style>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
</head>
<body scroll="auto" class=""><div>Hi Luke,</div><div> </div><div>I was coming around myself to believing that the problem must be that the necessary hooks for the CW features are just not there, or do not work, in the current Hermes firmware. I can't see how anything in my particular setup could be responsible. I hate to seem to throw brickbats because the whole HPSDR project has been so enormously successful as a whole and with such a huge amount of effort by the individuals contributing the hardware design and software development. However there are clearly problems in the coordination of changes made to the firmware/software. It is called configuration control in my professional world. I know of another instance involving a VNA application where there was competition for space in the Hermes FPGA and one interface got dropped in favor of adding another feature without much coordination.</div><div> </div><div>I have not really exercised RX2. Superficially it looks as though it works in my setup. My main interest actually is to play with the low speed digital modes like PSK31. The CW problem is not actually a show stopper for me. Just an unexpected finding.</div><div> </div><div>You'd think Apache would want to take control of the configuration for the systems they sell. I see no evidence of that on their web site. However their most current hardware seems to be a development from Hermes and may be now on a separate software release path.</div><div> </div><div>My Hermes, assembled by Apache about a year ago, did come with an earlier firmware release. I should reload that and check if that solves the CW problem. </div><div> </div><div>73, Dick</div><div>W0QM</div><div> </div>
<div>------ Original Message ------</div>
<div>From: "List Mail" <<a href="mailto:mail10@barefoothorse.com.au">mail10@barefoothorse.com.au</a>></div>
<div>To: <a href="mailto:hpsdr@lists.openhpsdr.org">hpsdr@lists.openhpsdr.org</a></div>
<div>Sent: 4/21/2017 6:55:17 PM</div>
<div>Subject: Re: [hpsdr] PowerSDR on Hermes</div><div> </div>
<div class="plain" id="x44e39558291741d0a3c9b48058ae806c"><blockquote class="cite2" cite="377E90A4DEB941418E8EC4C68E4F041F@LukeNetbook" type="cite">
<tt><div>***** High Performance Software Defined Radio Discussion List *****</div><div> </div><div><div>Dick,</div><div> </div><div>I have OpenHPSDR Atlas system, and experience most of the symptoms you describe with your Hermes.</div><div> </div><div>I found the problem with the transmit control and CW Options has existed since the change in architecture that addressed the CW sidetone latency issue – around two years. The CW sidetone is good on my system. The change really made that work well, but the other issues have been an irritation ever since. My system is workable, but the transmit control (via the external PTT line out of Penelope) doesn’t work properly.</div><div> </div><div>My system is otherwise stable, so I have been reluctant to move from Power SDR mRx PS v3.3.9. Oh, and the Rx2 doesn’t work either, but that really doesn’t bother me.</div><div> </div><div>73,</div><div> </div><div>Luke VK3HJ</div><div> </div><div><span><div style='color: rgb(0, 0, 0); font-family: "Calibri"; font-size: small; font-style: normal; font-weight: normal; text-decoration: none; display: inline;'><div style="font: 10pt/normal tahoma; font-size-adjust: none; font-stretch: normal;"><div style="background: rgb(245, 245, 245);"><div style="font-color: black;"><b>From:</b><a title="rgrubb@computer.org">Richard Grubb</a></div><div><b>Sent:</b> Friday, April 21, 2017 4:52 AM</div><div><b>To:</b><a title="hpsdr@lists.openhpsdr.org">hpsdr@lists.openhpsdr.org</a></div><div><b>Subject:</b> Re: [hpsdr] PowerSDR on Hermes</div></div></div><div> </div></div><div style='color: rgb(0, 0, 0); font-family: "Calibri"; font-size: small; font-style: normal; font-weight: normal; text-decoration: none; display: inline;'>***** High Performance Software Defined Radio Discussion List *****<br><br><p><hr><style id="eMClientCss"></style><style></style><div> </div><div>I have a Hermes card purchased from Apache about a year ago. I have just started to use it as a transceiver with the ANAN-10 PA as opposed to a VNA and just a receiver. All the receiver functions I have tried work fine. However I tried to set up the CW options in PowerSDR. None of them take any effect. The connection for a straight key remains sleeve and ring and sidetone does not work. I cannot turn off break-in mode. I have the latest Firmware installed on Hermes (3.2) and am using the latest PowerSDR I can find (3.3.9). I am probably doing something stupid. Can anyone please suggest what it is. Thanks.</div><div id="x678fc295a1024ae4a7e367ed06655a4f"><blockquote class="cite2" cite="em28c20495-9423-4696-a479-50b95af3ba11@rgrubb-pc" type="cite"><div> </div><div>Dick, W0QM.org/pipermail/hpsdr-openhpsdr.org/</div></blockquote></div></div></span></div></div>
<div> </div>
</tt>
</blockquote></div>
</body></html>