It would be much better to roll the minor revision updates into a quarterly update so that there is less confusion. I have seen multiple versions released within the same week. My biggest complaint is the never ending minor revision updates. I know the program is written for several platforms, and that the author is promoting his way of use, but Windows users expect software to work within the Windows standards.
There doesn't appear to be any file associations so that the companion programs automatically work. For example, the program is only visible under the user account it was loaded under rather than all the user accounts on the computer. I was using FLDIGI on a Windows PC (XP, Vista and 7), and while the program worked, it was obvious that program wasn't designed for Windows as it doesn't follow the Windows design and security standards. Open source and open protocols should be something revered by ham radio is at the heart of why we exist.
I look forward to what this will be in another few years as it progresses further. There are alpha efforts to add packet functionality, digital voice modem implementations and other features. It is a really great system for sending forms based message data.īecause this project is open source, new features are being actively worked on and added all the time. The NBEMS system is still being worked on with tweaks and new modes added frequently. I highly recommend this software and the accompanying suite of utilities, flrig, flmsg, and flwrap. At least this software is actively maintained and extended.and you aren't paying for new features as they are added. No surprises.ĭouble clicking on setup.exe if new features or bug fixes are released is hardly an unreasonable hassle. It is purpose built and going from Linux to Mac to Windows, it behaves the same way on each platform. The interface simplicity of fldigi is one of its greatest features. Too many other software products focus on form over function and it is a waste of effort. This is hundreds of man hours in effort just for the sake of appearances adding nothing to function. Integrating the native appearance of an OS native tool kit requires maintaining completely separate code trees. Other reviewers obviously have no depth of experience in software and don't realize that for a cross platform tool kit, you will have the same look (of the toolkit) on any platform you run it on. It is a great example of open source contribution and project success. Open source, completely free software, very well maintained and a highly active community. Click it and restart the TCP session.This package is incredible. If for some reason the TCP link does not start you will see "Comm Services" at the bottom of the Log4OM window. Log4OM should now be monitoring the FLdigi logbook. Next press the green button on the communicator. Select the logbook you created in FLdigi above then save. Go into settings->Inbound->FLdigi Interface.
Click the Red button to stop the communicator. Log4OM monitors the file and everytime FLdigi posts and QSO Log4OM reads it and imports the data in its database. FLdigi's logbook is acutally an *.ADI or an ADIF file. (2) In FLdigi go into "Configure->Rig Control and make sure RigCAT, Hamlib, Hardware PTT are all UN-CHECKED. First select New, then select save to create the new logbook. Creating a logbook is a two step process. There are several things to check: (1) When you create a new logbook in FLdigi the file is stored in "C:->Users->XXX->fldigi.files/logs" where "XXX" is your user name.
0 kommentar(er)
