It took me a while today, but with the new version 3.1 of fldigi, was able to get the Windows version to work with the xml file to my ICOM 756 Pro 2.
For the average ham, I think that there would need to be a lot more explanation, perhaps more of a cookbook approach where even the most basic information needs to be explained. Otherwise it can take many hours of sperimentin' HI. Dave, W1HKJ in a recent post on another group pointed out that you can find out the available ports by holding your cursor over the open rig control config menu. I did not realize that, but knew that my West Mountain rig talk USB to CI-V was set on COM6. So you need to know the COM port your interface is using. Then you need to download the correct xml file and edit it. I rarely have ever edited an xml file, but finally realized that I did not have to get some special program, but could use Wordpad (not Notepad) to bring up the file and make the necessary changes and save them. What I did not realize until experimenting for many hours, was that this file does not seem to go into your main file with the program, but instead needs to be placed in separately located folder depending upon whether it is for Vista or XP. In my case, using XP, it is under Local Disk C:/ Documents and Settings/<my name>/ fldigi.files which stores many of these variables. I was not able to use COM port with numbers. It may be that it only accepts the Linux type of structure which is /dev/ttySx. If you are not familiar with how this works under Linux, you need to subtract one number from the COM port number to get the ttySx number because Linux starts naming ports starting with zero. Thus, in my case it was the COM6 port I needed, and I then changed the xml file to insert /dev/ttyS5. The case is mandatory so all lower case except for the capital S. As you mentioned, users must rename the file from the original name to rig.xml which must be present for the program to see these variables. Hopefully this may help? Perhaps others know additional things that are not spelled out in the documents yet. I think eventually they will have a separate doc file for Windows vs the other platforms. The ability to actually have the first cross platform program of this type is quite impressive in itself. It supports not only GNU/Linux variants and Win XP SP2 and Vista, but also OS X, and FreeBSD! I don't think we have any other multimode digital programs that can do this. I am sure I speak for many of us who owe a tremendous debt of gratitude to Dave and all the others who are working together to come up with such interoperability with not only a multimode digital program, but one that solves many of the public service and emergency communications messaging issues. 73, Rick, KV9U w4lde wrote: > Ross, > > Right after I sent my email there was a new version 3.1 released, so far > the same issues for me. The newer version was to correct the com > issues. I've downloaded the FT1000 XML file, edited it to meet my com > port selection, renamed it to "rig" as per the help file and still no > initialization. Is there one for the MP? May have to skip and go on to > something that works? Looks like a fantastic package. > > 73 de > > Ron W4LDE > > Ross wrote: > >> Ron, >> I have a similar problem, trying to get FLdigi to work with a US >> Interface Navigator, the computer >> is running XP and I am trying to operate the PTT on a K3. >> The Vista version works perfectly with Navigator and my Orion II. >> Ross >> ZL1WN >> >> >> ----- Original Message ----- >> *From:* w4lde <mailto:[EMAIL PROTECTED]> >> *To:* [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ; >> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >> *Sent:* Tuesday, August 19, 2008 7:08 AM >> *Subject:* [digitalradio] fldigi windows version and MicroHam >> micro keyer >> >> Thought I would look over the windows 3.0 version of fldigi and the >> different array of available modes. >> >> Was able to get fldigi open and running, decoding and receiving OK, >> however, I can not get it to talk to the rig which is a Ft1000mp with >> support through a microham USB micro keyer. >> >> fldigi apparently doesn't see the rig through the micro keyer, anyone >> out there that may have successfully set up fldigi through a micro >> keyer? >> >> 73 de >> Ron W4LDE >> >> >> >> __________ Information from ESET NOD32 Antivirus, version of virus >> signature database 3365 (20080818) __________ >> >> The message was checked by ESET NOD32 Antivirus. >> >> http://www.eset.com <http://www.eset.com> >> >> >> > > ------------------------------------ > > Announce your digital presence via our Interactive Sked Page at > http://www.obriensweb.com/sked > > Check our other Yahoo Groups.... > http://groups.yahoo.com/group/dxlist/ > http://groups.yahoo.com/group/contesting > http://groups.yahoo.com/group/themixwgroup > Yahoo! Groups Links > > > > > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.138 / Virus Database: 270.6.5/1618 - Release Date: 8/18/2008 > 6:51 AM > > > >
