Setup is Icom IC-746PRO, Writelog 10.42C. Has worked fine in the past, though I had to change the rig's CI-V addr to 56h to make it think it was an IC-746 "non-pro", to match what Writelog expected.
More details on my IC-746PRO stuck in xmit (original post below): I am now running 10.48F -- it did not make a difference with the problem. No matter what rig I pick, either with the Rigblaster on CO
This is similar to my problem, except that mine is a 1-rig setup, IC-746PRO, with a Rigblaster. Gets stuck in xmit whenever I start Writelog, because the PTT light on the Rigblaster goes on. ANY info
Several days ago, I wrote about my Rigblaster getting PTT turned on, causing rig to go into xmit. A few folks had ideas, but nothing turned up to fix the problem. I asked the Rigblaster folks, and si
I tried the older 10.37B on a different PC -- a new Dell running WinXPpro -- same thing happens -- Rigblaster Pro's PTT and CW light come on continuously. This was true even with DisableCommPTT=YES.
This has been fixed. [big sigh of relief!] It was Writelog telling the Rigblaster to go into PTT/CW, but it wasn't a Writelog software problem, but rather a Writelog Setup issue on my part. I thought