Brendan I am using the ICOM756ProII with WindowsME at 19200/8/1 No Parity with ICOM CT-17. But since WriteLog has the address for the Pro instead of the Pro II I have set my Pro II to the Pro address and am typically using the 756Pro_VFO_A_Only definition. I do not care for the program to set up split for me, because it doesn't do it the way I want anyway (I prefer dual watch on split op).
I worked on all of the 756 and 781 definitions, improving them and timing them to be reliable in DXbase2003. The versions you have are the ones I finally settled on and were put on the CD. As provided on the 2003 CD they are completely reliable on my equipment. There is a compromise between speed of set up and reliability and to achieve reliability I had to cut them back from maximum performance. You will find a variable called PACING in the radios.ini definitions for these radios. For the 756 series the value set is 5. You can try increasing this, a first try might be setting it at 10. This will slow down set up quite a bit, so if 10 is reliable, you could then try, say 7 or 8. The additional parm which is associated with timing are the 'eoc(nnn)''s you will find scattered in the code. I think they are all eoc(100) except those that are eoc(0). The ones which are 100, you may want to try 150. Again this will slow set up, but might help you. I have run these definision with the minimum timings, they were on the edge of working, then I bumped them up more than adequately. It doesn't seem possible that timings would vary on one Pro II to another Pro II but..... When making changes in Radios.ini, you must have first closed DXBase2003. Use NotePad to edit radios.ini. I would save my original Radios.ini in a separate directory for safety. Radios.ini appears to be read once at startup of DXBase2003. Ron N5IN ----- Original Message ----- From: "Brendan Minish" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, October 11, 2002 11:52 AM Subject: [DXBase] Radio interface problems Win2k ( & ICOM?) > Hi everyone > > I am wondering if anyone else is having radio interface problems with ICOM > radios or indeed other radios under win2k (or possibly XP??) > > the symptoms are that DXBASE will occasionally (every 10 to 50 radio > commands) report that the radio is not responding even though often when > you clear the error message the radio will then respond if clicking on a spot. > Errors occur when logging and when clicking on spots or making spots > > I am using DXB 2003 although I also had this problem with DXB2002. > I have tried the following things to try to make the problem go away, > nothing has cleared it up so far > > various com port speeds from 1200 Baud up > > 2 different interfaces (com's CT-17 and a home made level converter) > > Hardware handshaking on and off (no difference & none expected as the icom > serial interface is a 2 wire standard with no handshaking available) > > Driver X disabled (this helped reduce the occurrence of errors ) > > 3 different computers (all running win2k ) same on all machines (even on > 1GHZ P4 laptop) > > 2 different radios 756PRO and 756PRO2 > > Turning on and off CI-V transceve on the radio > > WIN2k, WIN2k SP1, WIn2kSP2, WIn2kSP3 > > normal motherboard comp ports, USB com ports and a special High speed PCI > com port board > > It's not RF in the shack as it happens on all band and often during RX > > It is important to note that I have had no problems whatsoever with either > radio on any computer I tired with writelog (I can log entire 48 hr > contests without a single com port/ radio error) or logEQF (dos, running in > a dos compatibility box) or even Airmail (which just uses the port to set > radio frequencies. DXB2003 is the only program I run that has any problems. > > If anyone else has these problems have you found anything that helped? > > 73 > Brendan EI6IZ > > _______________________________________________ > DXBase Reflector - Please visit us on the web at www.dxbase.com > - - - - - - - - - - - - - - - - - - - - - - - > To UNSUBSCRIBE please visit: > http://mailman.qth.net/mailman/listinfo/dxbase >
