![]() ![]() After a fair bit of Googling and experimenting, I figured out why: if you use the Generated parameter string, rigctld will not start, whether you pick Serial connected radio or Network connected radio. This was the part that I could not initially make work. On the used parameter string, use the following: "-model=4 -Z" (without the quotes) and then Save and apply. On the Hamlib tab, select RIG Model: FLRig FLRig Stable. On the Settings tab, select CAT Engine: Hamlib. This was also very easy: set the Rig to FLRig FLRig. And if I couldn't make WSJT-X work with FLRig, there was no point in continuing. I did this next for a couple of reasons: there were a lot more people using this combination successfully, so it was a good way to make sure that the networking side was working correctly. = (Optional) Configure WSJT-X to use FLRig. For me, I simply had to set the proper Rig (FT-450D), COM port (3), Baud (4800) and StopBits (1). Obviously, FLRig needs to be working 100% before you start trying to make Log4OM2 talk to it. = Install and configure FLRig and make sure it works. I was able to make this work with Log4OM2 2.24.0.0 and FLRig 1.4.7 (and WSJT-X 2.5.4). Using win10 home and all programs are the latest versions. I know how to setup log4om to work with hamlib + FT-891 + Fldigi but not toghether with Flrig. I can't get it working together for log4om + fldigi + flrig + FT-891 or only log4om + flrig + FT-891. The transceiver frequency is not displayed in the log4om window.ĭuring this time Fldigi, Flrig and FT-891 communicate with each other. I also try to click "open hamlib standalone", then ok (V) with the same results (connected only 1-2 seconds). When I click un green ok (V) in right lower corner, CAT status: Disconnected indicator turns green "Connected" for 1-2 seconds then turns off. I don't know what settings to do next for Flrig in the Hamlib window or in FLrig setup menu (serial parameters / TCP Radio parameters / TCP Connection, etc). In Hamlib I selected RIG Model: FLRig Stable. In log4om / CAT management I selected CAT engine - hamlib / autostart. I can't set the CAT/hamlib from log4om to work with the above setup. ![]() But, it is what it is, and there are not that many county lines anyhow.I connected Flrig with Fldigi and they work well together + FT-891. I was expecting it to copy the entire exchange over as one item. I had to type the other two counties in manually. However, clicking on the report only moves the individual county I clicked on to the N1MM ENTRY window. With the digital bonus, that is 24 points for one QSO! His report to me was NVNYE/NVCHU/NVLAN representing the three counties. I am on a county line and worked a station on PSK31 who was on a three county line for an equivalent of six contacts. When there is an issue, is it an N1MM thing, or an fldigi thing? N1MM automatically creates the necessary multiple entries for county lines. This is the problem I constantly run into. Like I said, I’m just curiousįrom: On Behalf Of WA7SKG via Groups.Io Sent: Sunday, 2:19 AM To: Subject: Re: Logging county line expedition Maybe I should go back and re-read everything. Regardless of points (or mode), doesn’t it give you a contact for each county (3), all during a single contact ? How does a single contact, on a Three County line, equal 6 contacts ? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |