macOS version 10.9 (Mavericks) RUMtrol for Mac: Download (32. macOS version 10.11 (El Capitan) RUMlogNG 3.6.2: Download Min. macOS version 10.13 (High Sierra) RUMlogNG 3.12.2: Download Min. macOS version 10.13 (High Sierra) RUMlogNG 4.3.2: Download Min. K3 for 10 years now and thinking it’s time to replace it. macOS version 10.13 (High Sierra) RUMlogNG 4.7: Download Min.
I’m considering getting one or the other. No negative experience just asking about pro’s and con’s since he had worked Getting close to pulling the cord however.Ĭc: Julia Tuttle Re: ELECRAFT K3-F P3-F & SP3.Ĭoncur that at this price level no amount of due diligence is unreasonable.Ĭhecking bank balance here after taxes paid this year! I have a lot of classic radios I’ve used for years in the garage. I’ve been inactiveįor a few months so getting back into and trying to figure out what I want toĭo. Both are really good radios, as is the K3. It’s a hard decision! I’ve been looking at YouTube and talking to people that
Message delivered to ELECRAFT K3-F P3-F & SP3. If so, let me know what you are using (offlist). Is anyone using a ready made cable to interface the Ameritron RCS-12 auto Subject: using K3 with Ameritron RCS-12 antenna switch The DB-DB15HE, in case anyone else is looking.
Message delivered to WTB K3-K3S 200hz Or 250hz Filter.Īmeritron does make a cable to interface its tuners and switches to an Elecraft How much power out are you running the K3 on FT8 without overheating etc?ĭarrell AB2E (portable VP9 from 24-29May) I've read a couple old posts about PSK, so I'm wondering what the group is I'm leaving for VP9 on Wed, and taking my trusty K3.Ī little time will be devoted to FT8 so my question is what is the duty cycle Message delivered to question K3 digital duty cycle power FT8 > Darrell AB2E (portable VP9 from 24-29May) > How much power out are you running the K3 on FT8 without overheating etc? > I've read a couple old posts about PSK, so I'm wondering what the group is > A little time will be devoted to FT8 so my question is what is the duty cycle > I'm leaving for VP9 on Wed, and taking my trusty K3. To local environment, it'll reduce output to protect itself. I use (rarely) less than 100 watts, all the way up to band legal limit. Using Fldigi to control the rig is OK, but I would prefer to keep RumlogNG in control, just so I don’t need to have Fldigi running when not using digital modes.To: Re: question K3 digital duty cycle power FT8ġ3 seconds of transmit, 17 seconds of receive = 43% duty cycle. In searching this list archives, I see a number of similar problems raised in the past about this interface with Fldigi. The POTA database tries to identify Park to Park contacts automatically by matching two QSOs between two operators in different parks within a certain timeframe. In general, submitting a plain ADIF file is sufficient, but may not give you all the Park to Park credits you’ve earned. In asking about this on the RumlogNG forum, it appears this problem has been experienced by others. In RUMlogNG, this is done using the Logbook>New menu item, or N.
#Rumlogng vs dogpark serial#
Using RUMlogNG with USB interface for audio, CAT control and PTT.Īlso running CubicSDR as a panadapter using the TS-590’s serial port for CAT control
#Rumlogng vs dogpark mac osx#
Mac OSX 11.4 on a 2016 Macbook pro, 3.3 Ghz i7, 16GB memory On the other hand, if I configure Fldigi to control CAT using rigcat, and send its data to RumlogNG, it’s very stable and works great. Other times it will crash at random after only a few minutes. If youve forgotten and/or need to reset your password, please enter your Callsign and use. Timing seems random - sometimes it will run fine for 30 minutes or more, through several QSO’s. Sometimes it locks up and requires a force-quit, but most times it just crashes. If I configure the two programs so that RumlogNG is controlling CAT and sending data to Fldigi, it all works, but Fldigi crashes randomly. I am a new Fldigi user, and am having a problem with CAT control by RumlogNG, and passing TRX data to Fldigi via the XMLRPC interface.
0 kommentar(er)
