The most obvious techno-lurch suspicion is that, predictably and most likely necessarily, the P3 introduced a timing delay in the response to the commands, and that HRD has a timeout and clips the response on this longer exchange. Since it appears to be interpreting other commands, it clearly is not a connection problem.
The only real fix is for the software author to make an adjustment in his self-described beta software, in the timing loop, for what is no longer a "private" comm channel. Since I'm sure other Elecraft products will share this channel, the real solution is for HRD to default at startup to longer waits and dynamically reduce these to some overage on the delays actually experienced. IMHO it's unrealistic to expect Elecraft to take on the burden of adjusting central code for all wrinkles in all external add-on software. To the extent that Elecraft CAN and does do so, that's nice and wildly appreciated, but "parasitic" applications will need to adopt and creatively manage the burden to stay current with their host hardware. I have seen instances where add-on app coders became obdurate and would not adjust to morphing equipment and foundational software. That behavior is a fast track to obsolescence. Some well know logging software has and is in process of driving their app off the cliff. My personal experience in hardware/software timing issues resulted in an unshakable conviction that hardware code is no place for the weak, the faint-of-heart, the impatient, the easily insulted, or those looking for any kind of one time code-it, keep-it-forever software. The only thing for sure about hardware code is that 1) what worked this week, next week won't, 2) those needing fixes are only calling you because what worked last week, this week doesn't, and thousands of people are sitting on their hands being paid for doing nothing until you fix it. In the software business, you either keep up or die, no prisoners taken. 73, Guy. On Tue, Aug 24, 2010 at 1:42 PM, David Robertson <[email protected]> wrote: > Mike, > After reading your e-mail I tested HRD while my P3 was on and working. I had > no problem with the HRD frequency readout or any DMC functions while the P3 > was working. I have 0032 firmware installed. I also can use MIXW while the P3 > is working with no problems with either. As a matter of information I am > running Windows XP Prof. and am using a real serial connection (not USB to > Serial). ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
