Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Possible\s+Problem\s+with\s+10\.56C\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Possible\s+Problem\s+with\s+10\.56C\s*$/: 7 ]

Total 7 documents matching your query.

1. [WriteLog] Possible Problem with 10.56C (score: 1): Author: "JE Brown" <W4LC@fuse.net>; Date: Fri, 2 Dec 2005 14:54:48 -0000; In setting up for TARA, I am noticing that there seems to be a problem with Writelog detecting the rig. When the program first starts, the rig and correct frequency ARE displayed. After making a freq; /archives//html/WriteLog/2005-12/msg00019.html (7,129 bytes)
2. Re: [WriteLog] Possible Problem with 10.56C (score: 1): Author: "JE Brown" <W4LC@fuse.net>; Date: Fri, 2 Dec 2005 19:09:02 -0000; Dick, It is definately something to do with the new v10.56C. As a test, I reverted to v10.55D, and the problem disappeared. BTW, I have noticed, in the past, that when quickly tuning the radio up or; /archives//html/WriteLog/2005-12/msg00020.html (8,588 bytes)
3. Re: [WriteLog] Possible Problem with 10.56C (score: 1): Author: n5po@juno.com; Date: Fri, 2 Dec 2005 21:09:51 -0600; Having the same problem here with 10.56C. One other local ham here also has the exact same problem. Seems to happen after you "save configuration" Had to go back to 10.55D and everything is normal. U; /archives//html/WriteLog/2005-12/msg00027.html (7,209 bytes)
4. Re: [WriteLog] Possible Problem with 10.56C (score: 1): Author: Steve AI9T <steve@ai9t.com>; Date: Fri, 02 Dec 2005 23:38:05 -0500; Having the same problem here with the new version here. Having to keep an eye on it during the TARA contest. Every time it looses rig have to save configuration to get it back. Like the com port is g; /archives//html/WriteLog/2005-12/msg00030.html (9,961 bytes)
5. Re: [WriteLog] Possible Problem with 10.56C (score: 1): Author: "JE Brown" <W4LC@fuse.net>; Date: Sat, 3 Dec 2005 14:50:21 -0000; Lee, It seems to have something to do with tuning speed. Tune slow, and it seems to work ok. Tune fast and the rig disappears. Clicking on spots works ok, and the rig shows the correct freq. Looks li; /archives//html/WriteLog/2005-12/msg00031.html (8,710 bytes)
6. Re: [WriteLog] Possible Problem with 10.56C (score: 1): Author: "JE Brown" <W4LC@fuse.net>; Date: Sat, 3 Dec 2005 14:53:41 -0000; Stevem Exactly. Slow tuning seems to help. Tune quickly and the rig disappears. I have found that going into port setup, then out again will restore the freq. Looks like a patch is needed. Jim W4LC -; /archives//html/WriteLog/2005-12/msg00032.html (9,967 bytes)
7. Re: [WriteLog] Possible Problem with 10.56C (score: 1): Author: Steve AI9T <steve@ai9t.com>; Date: Sat, 03 Dec 2005 10:08:36 -0500; One thiing I did was change the baud rate from Auto to 9600 baud on rigs, and the program that seems to help. It still disapears every once in a while but not as bad. Never did that before I upgraded; /archives//html/WriteLog/2005-12/msg00033.html (8,753 bytes)

Current List: 1 - 7
Page: [1]