Mel, Don & Duane, My radio settings were CI-V Transcieve off, and 1200 baud. I have the DTS option checked in dx4win, and did at times have both checked. The icom is the only item on the bus. I'll have to try the generic Icom definition tonight. For periods dx4win works well with the interface, it just seems to get a mind of it's own, I would think that when using a polling technique nothing would be changed on the radio and it would only perform queries unless I perform some activity to trigger a change. This is happening while I'm sitting back from the keyboard. I will construct a different interface and try that out in the coming weeks. Radio control from within dx4win would be a nice addition to my station, but I'll have to stick with hands and fingers controlling the radio until I find something more reliable.
Thanks for the help. 73 Michael At 04:33 AM 2/14/2003, Mel Martin \(VE2DC\) wrote: >Odd... I've seen peculiar behaviour in the past if DX4WIN receives >invalid data... The interface wasn't very "robust" in that regard... >Haven't seen it in the new release... > >Are there any other devices on the C-IV bus? >Have you set the baud rate to a fixed rate... I've heard of problems >with "auto"... I'd suggest 9600baud... Works flawlessly here... > >The transceive should be off... And there is no reason it should make it >worse... It sure sounds like the Pro is receiving corrupt data... > >Try the generic Icom definition... Has a few less commands configured... >Beyond that, you will have to debug... Perhaps with the program "CI-V >Commander" available on the net. I tracked down a problem with the 781 >with that tool... Works very well... > >Good luck... > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >On Behalf Of Michael McCarty >Sent: February 14, 2003 12:14 AM >To: Dx4win@mailman.qth.net >Subject: [Dx4win] Re: Troubles with Radio Control > > >Mel suggested that I turn off the CI-V Transciever setting on the Icom >746. This made no difference, in fact in may ways it got worse. DX4Win > >kept turning off split and my narrow filter settings. I'm still seeing >the >radio timeout dialog as well as the Access violation dialog. I was >however >manage to type a string into the Scanner Dialog description, so this was >an >improvement. > >73 Michael > >At 11:49 PM 2/12/2003, Michael McCarty wrote: > > >I'm having a few problems with some radio control aspects of > >6.02. Running XP Pro, NTFS, G3VGR CI-V > > interface for an Icom 746 and serial ports via a PCMCIA card. Baud > > rates of 1200, 9600, 19200 all produce the same results. The same > > interface works flawlessly with TR Log (under DOS), and a couple other > > > CI-V programs (under XP). I ran with them for a couple hours of >testing > > to verify it's not a problem with XP and the interface. > > > >The radio control giving a timeout message after a little while, it can > > >be > >2 minutes or 10 minutes. Simply starting the Radio again via the menu > >brings it back to working form. I've fiddled with the poll rate and >max > >tries and don't see a difference. I also don't see why it needs a poll > > >period since the radio reports any changes when the 'CI-V Transceive' >is > >set on. > > > >I'm unable to change the "Notes for Radio" text box. > > > >The Scanner Dialog doesn't want to accept anything more than a single > >letter for the description. Each typed letter replaces whatever was > >there. The dialog just doesn't give the feel that I'm in control of > >what's there. > > > >I've also seen an error dialog followed by the timeout dialog. "Access > >violation at address 0056CCE8. write of address 00000008." > > > >73, > >Michael K6MMC > > > >_______________________________________________ >Dx4win mailing list >Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
