[digitalradio] fldigi 3.01 posted on www.w1hkj.com
Hi all from [EMAIL PROTECTED], 73 de LA5VNA Steinar -- 1. Corrected serial port discovery process for Windows. 2. Added OS-X compilation switches. For Windows users. You can download the new zip file for your version of Windows and simply extract and overwrite the existing executable and dynamic link library files. For Linux binary users. You can download, untar, and replace your existing binary with the new one. 73, Dave, w1hkj
[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
Re: [digitalradio] fldigi windows version and MicroHam micro keyer
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 To: [EMAIL PROTECTED] ; [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
Re: [digitalradio] fldigi windows version and MicroHam micro keyer
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
Re: [digitalradio] fldigi windows version and MicroHam micro keyer
I use a Microkeyer and a Kenwood TS2000 with FLDIGI 3.01 . In the set up area fro FLDIGI I have the following Com 3 same as PTT port in Microkeyer device router PTT= TTY selected RTS selected Hamlib is selected (I don't understand this, but it works) Andy K3Uk On Mon, Aug 18, 2008 at 4:43 PM, w4lde [EMAIL PROTECTED] 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 -- Andy K3UK www.obriensweb.com (QSL via N2RJ)
Re: [digitalradio] fldigi windows version and MicroHam micro keyer
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
Re: [digitalradio] fldigi windows version and MicroHam micro keyer
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.obriensw eb.com/sked Check our other Yahoo Groups http://groups. yahoo.com/ group/dxlist/ http://groups. yahoo.com/ group/contesting http://groups. yahoo.com/ group/themixwgro up 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
[digitalradio] Success with FLdigi
I have been trying to make FLDigi work on my K3, finally it does... I searched for all the cygwin1.dll files and deleted them, then searched the hard drive for any fldigi remnants, found a few and deleted them. Deleted the fldigi I had extracted, and extracted a new fldigi3.01. Put in RTS and Com 4 and it works perfectly. Obviously bits from a previous fldigi had been hanging about preventing the program working correctly. Congratulations and thanks to Dave W1HKJ for all his hard work, now for the fun of using the program. Regards to all Ross ZL1WN
[digitalradio] Move away from PSK63 /31 in NBEMS?
I note the new release of FL-Digi does not list PSK31 or 63 under NBEMS modes. I realize that Dave , Skip, and others never really intended NBEMS to have much use on HF , hence PSK250/125, but was wondering why the option of slower PSK modes has been removed. -- Andy K3UK www.obriensweb.com (QSL via N2RJ)
Re: [digitalradio] Success with FLdigi
Congratulations Ross and thanks for the response to my questions earlier, do you or anyone know if 3.01 will work with a Ft1000mp through the microkeyer? I have 3.01 working correctly with the PPT function in microkeyer but the program with the built in CAT function does not discover the com port for the CAT function. Once I get it to discover the CAT port then I can begin to use the rig.xml file. I did select the correct port in the rig.xml file to match the setup for the microkeyer but can not seem to get the internal rig cat function to discover the FT1000mp through the microkeyer. Did it discover the K3 through the microkeyer using the internal RigCat method? Andy (K3UK) has successfully got his CAT function working through the HAMlib but I wish I don't have to move in that direction. Anyone else out there in digi world using 3.01 with a MicroHam microkeyer and has had luck with the internal RigCat function of discovery? 73 de Ron W4LDE Ross wrote: I have been trying to make FLDigi work on my K3, finally it does... I searched for all the cygwin1.dll files and deleted them, then searched the hard drive for any fldigi remnants, found a few and deleted them. Deleted the fldigi I had extracted, and extracted a new fldigi3.01. Put in RTS and Com 4 and it works perfectly. Obviously bits from a previous fldigi had been hanging about preventing the program working correctly. Congratulations and thanks to Dave W1HKJ for all his hard work, now for the fun of using the program. Regards to all Ross ZL1WN
Re: [digitalradio] Move away from PSK63 /31 in NBEMS?
On Mon, 18 Aug 2008 21:04:22 -0400, Andrew O'Brien [EMAIL PROTECTED] said: I note the new release of FL-Digi does not list PSK31 or 63 under NBEMS modes. I realize that Dave , Skip, and others never really intended NBEMS to have much use on HF , hence PSK250/125, but was wondering why the option of slower PSK modes has been removed. There is nothing special about the NBEMS modes submenu. It lists modes that NBEMS users are likely to want to use, but nothing that is not also available elsewhere in the main Op Mode menu -- it's just a convenience. I suppose you could use any of the modes that can handle the ARQ protocol, including the slower PSK modes. 73, Stelios, M0GLD. --
Re: [digitalradio] Move away from PSK63 /31 in NBEMS?
I note the new release of FL-Digi does not list PSK31 or 63 under NBEMS modes. I realize that Dave , Skip, and others never really intended NBEMS to have much use on HF , hence PSK250/125, but was wondering why the option of slower PSK modes has been removed. Andy, PSK31 and PSK63 are still there for use in QSO's but neither mode is as good as MFSK16 or MFSK32, or our new Thor modes, for ARQ messaging when high static conditions on 80m or 40m exist, which is most of the time in the summer or before and after a hurricane, so MFSK16 or MFSK32, wider, but the same speeds as PSK31 and PSK63, are recommended for NBEMS messaging over PSK31 and PSK63. The MFSK16 and MFSK32 modes are not your grandmother's MFSK modes, but have been made more robust under static conditions on HF when PSK63 and PSK31 get pulled off frequency by the AFC if there is a static crash between ARQ transmissions. It was a tough decision not to include PSK63 in the recommended NBEMS mode list, but the job of NBEMS is to accomplish the most reliable messaging for any given speed, and the modified MFSK modes are simply more reliable, although they are wider. For VHF messaging, PSK31 and PSK63 lose out again over DominoEx11 and DominoEx22 at the same speed, because many VHF multimode transceivers have no TCXO and drift too much to maintain tuning on 2 meters during an ARQ transfer, whereas DominoEx has a wide tolerance to mistuning or drift, such that no AFC is needed and provides a lower minimum S/N than the PSK modes at the same speed. PSK31 and PSK63 are easier to recongnize among the background noise on VHF, so it is often best to establish tuning with PSK41 or PSK63, check to see if there is no adjacent frequency activity, and then switch to DominoEx for the ARQ transfer. The popular IC-746Pro, for example, drifts 100 Hz between receiving and start of transmitting, unless a TCXO is added, causing the loss of the first few characters or words on PSK63, so I have switched our 2 meter digital net from PSK63 to DominoEx. 73, Skip KH6TY NBEMS Development Team
