Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Writelog\s+and\s+756ProII\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Writelog\s+and\s+756ProII\s*$/: 3 ]

Total 3 documents matching your query.

1. [WriteLog] Writelog and 756ProII (score: 1): Author: Rick Stoneking <w2rds@arrl.net>; Date: Thu, 11 Mar 2004 13:45:51 -0500; All, During the ARRL DX SSB John, WA2C, and I ran a multi two from his place. We used Writelog with homebrew CI-V interfaces to the two 756ProII's that he has. I found that since Writelog (version 10; /archives//html/WriteLog/2004-03/msg00198.html (6,947 bytes)
2. Re: [WriteLog] Writelog and 756ProII (score: 1): Author: Jerry Pixton <jpixton@shentel.net>; Date: Fri, 12 Mar 2004 12:09:53 +0000; Rick, et al That is the way my 756 Pro II works. I think the issue is that the Icom reports the frequency of the active VFO. You can see this by just pressing the Main/Sub button and watch the freque; /archives//html/WriteLog/2004-03/msg00212.html (8,986 bytes)
3. Re: [WriteLog] Writelog and 756ProII (score: 1): Author: "Ric Plummer" <ricp@charter.net>; Date: Fri, 12 Mar 2004 13:13:32 -0000; This is a known architectural flaw in Icoms interface. That is you can write the split command but you can't read it back in order to find out it's state. This should NEVER be the case for any contro; /archives//html/WriteLog/2004-03/msg00214.html (11,306 bytes)

Current List: 1 - 3
Page: [1]