Info for those interested in this topic. 73, Radi F6GNZ
----- Mail transféré ----- >De : Jim Hargrave <w5...@gvtc.com> >À : Mel <ve...@videotron.ca> >Cc : DX4WIN Refelector <dx4win@mailman.qth.net>; supp...@dx4win.com; John >Sweeney <johns...@comcast.net>; "Radivoj Kar, F6GNZ" <f6...@yahoo.com> >Envoyé le : Lundi 18 Juillet 2011 15h24 >Objet : RE: [Dx4win] IC735 remote control > >Mel, > >Let me offer some insight about the IC-735. I have had my IC-735 since the >early 1980's. >I have used it with several radio control programs. > >The IC-735 and a couple of other early ICOM radios use a first generation >CI-V protocol. This is a 4 bit system, whereas the later models all use a 5 >bit version. As such it is more limited in available commands. > >The IC-735 comes with CI-V factory default of 1200 baud with Transceive ON. >The CI-V address is set at 04(hex). All three of these parameters are >changeable with jumpers inside the radio. I have configured my IC-735 to run >at 9600 baud rate. It is much less prone for data collisions at this speed. > >Now the Transceive issue. The IC-735 will NOT send CI-V Data with Transceive >OFF. It will only receive commands, but not respond to polls. This is >different than later model ICOM Radios. Hence there is more of a possibility >of data collisions with the IC-735. This can easily be verified by using an >RS-232 line tester. I have found this tester a very valuable tool for >troubleshooting CAT/CI-V behavior. > >I run my ICOM IC-735 in an SO2R configuration with Logger32. I have found >that at 9600 baud with 2 stop bits, a poll interval of 250ms is the fastest >it will run and avoid data collisions. This polling interval might differ >with different control programs, depending on the complexity of the poll >data word and expected response. > >I have never used DX4WIN. I had a demo copy of ver 8.01 and it worked fine >with my IC-735. To assist Radi in his problem, I downloaded a demo copy of >ver 8.05. That is when I discovered the ICOM 735.rig file did not work. I >copied the rig file from my 8.01 version into the 8.05 folder and it then >worked. > >I am not a member of the DX4WIN group. Please feel free to post this on that >group if you feel it of any value to other IC-735 users. > > 73s de Jim > W5IFP > > > > -----Original Message----- > > From: Mel [mailto:ve...@videotron.ca] > > Sent: Sunday, July 17, 2011 6:33 PM > > To: Radivoj Kar, F6GNZ > > Cc: DX4WIN Refelector; supp...@dx4win.com; John Sweeney; Jim Hargrave > > Subject: Re: [Dx4win] IC735 remote control > > > > > > re 1. That's interesting. The 735 and some Ten Tecs use the Icom > > protocol but the frequency string is one byte shorter. I used the 735 > > years ago without issue so I wouldn't have suspected the rig file. Good > > catch! > > > > 2. This doesn't make any sense. Any polling rate should work providing > > it is not too short for the radio to respond. with 5000ms it > > will update > > every 5 seconds. You do need retries, with older Icoms they will ignore > > polling requests if they are busy, for example spinning the dial. I > > typically use 4 and timeouts are rare... but any number should work. > > With a number too low the rig might time out occasionally.Newer > > rigs can > > time out too but you almost have to go out of your way to trigger a > > timeout because of the faster processors. It has happened with my 7700 > > doing some major knob spinning (never think to use the keypad > > ;-) In any > > case, you should not have to play with these values to make it work. > > I've used from 500ms to 2 seconds without trouble. I never tried faster > > than 1 second with my old 751A. > > > > 3. It is not actually necessary to change this value in the rig file, > > all it does is change the "default" speed. You can override in > > preferences. > > > > I believe CI-V should be OFF for reliable performance with DX4Win. With > > older rigs (probably including the 735) leaving this on can cause data > > collisions and corrupt data which results in erroneous > > frequencies being > > reported. This can be dangerous if using amps or tuners relying on C-IV > > for frequency information. > > > > I should mention that this has not happened to me recently... I no > > longer have my 781 which was the last radio with which I experienced > > this problem. My IC910H did not have this issue which is why I suspect > > the newer radios are "better" at detecting collisions. > > > > Can someone confirm if this data collision problem still happens with > > older Icoms with V8.05? I seem to remember it did in 8.01 causing the > > bandmap to shift erratically, but Paul did some tweaking in subsequent > > versions. > > > > > > On 2011-07-17 17:37, Radivoj Kar, F6GNZ wrote: > > > Hi, > > > > > > With a precious help of Jim Hargrave , W5IFP, the problem was solved! > > > > > > 1. Original IC735.rig files in dx4win versions 8.04 and 8.05 > > are WRONG! Rig timeouts occur regularly with these versions, > > whatever polling time and retries numbers are chosen. Good file > > was found by Jim in version 8.01 and maybe was also good in > > earlier dx4win versions. > > > > > > 2. With the good dx4win ver 8.01 rig file, to > > > obtain log window's band/mode to reflect changes on the rig > > selections, a > > > lot of combinations of polling times/retries were tried. In some of > > > them, like with default polling time of 5000ms, it was > > required to open > > > the radio frequency setup window and click on "read" to make logging > > > window reflect the changes. The combination that works > > automatically and FB, without having to open the frequency > > setup window, , is 350ms and 3 retries (set in Radio > > Preferences). Some other close to these numbers may work also, > > but this one works all the time in my case) > > > > > > 3. Speed in ic735.rig file and preferences was changed from > > 1200 bps to > > > 9600 bps and JU22 in radio was also set to 9600 bps (left position > > > contacts). Also, "ci-v transceive" jumper in radio ( the last > > contacts on the > > > right) was left ON. > > > > > > RMX: transceiver band/frequency will not be reflected > > correctly in logging window if radio is tuned to a frequency > > out of HAM band limits, which is OK. > > > > > > > > > Now, I am haaaaappy again...... :) > > > > > > 73, > > > Radi F6GNZ > > > > > > > ______________________________________________________________ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
