Better than a screenshot, I present to you my config file. This entire exchange has felt like the time when Yaesu called me everything except a HAM radio operator because their bad sourcing of finals in their FT-100Ds caused repeated failures of the final amplifier ICs. I never did get my money back, or an apology from Yaesu for their "customer service" personnel's behavior both on the telephone and in email, and they lost a customer for life because of it.
So, rather than being accused of spreading more rubbish, this will be my last communication regarding this on this list. My email address is good on QRZ if you need any more information. 73 de AI8W, Chris SKCCLogger.ini SKCCLogger Initialization File Version: v03.00.14 Linux 64-bit Compiler: 2019r1.1 Build: 2020-02-20 at 09:40:29 ET Filename: /home/chris/Documents/SKCCLogger/SKCCLogger.ini Written: 2020-06-07 12:19:39Z RST RX: RST TX: TX Pwr: 100 Contest ID: 20838T Callsign: AI8W SKCC_Nr: 20838T Op Callsign: AI8W Gridsquare: EN82jg Key Type: SS Maximum Recent Log Count: 5 Membership Age Reminder: 7 Radio Frequency Read Period: 1 SKCC Web Waiting Period: 60 GridSquare Details Column Count: 5 SPC Details Column Count: 10 GMT Correction: 0.0 Preferred Font: Monospace Preferred Font Size: 11 Sprint Centurion Points per Band: 5 Sprint Tribune Points per Band: 10 Sprint Senator Points per Band: 15 Sprint Bonus Station Points per Band: 25 Copy SKCC to Comment: YES Refill Log ListBox After Resize: YES Remember Window Positions: YES Auto Log Option: YES Auto Fill Option: YES Sprint Logging: NO QSY Field Auto-Clear: YES Callsign Partial Matches: YES Log Mode Option: NO Use PC Time: YES Time End When Logged: YES Award Email Reminder: NO Logging Mode: CW Default Brag Month: Previous CallList Window: 0;0;0;0 GridSquareDetails Window: 0;0;0;0 LogEdit Window: 427;2237;500;555 LogEntry Window: 1489;2656;475;555 Main Window: 1797;1946;359;1471 ProgramOptions Window: 429;2025;600;510 QSONotes Window: 0;0;0;0 QSOTimer Window: 462;39;175;300 RadioSetup Window: 403;1954;540;600 SPCDetails Window: 243;32;400;555 TKAKeyCounts Window: 0;0;0;0 Log List Column Widths: DBKey:0; RowNr:50; Date:85; Time_On:80; Time_Off:73; Call:75; Name:103; Freq:75; Band:50; Mode:50; RST_TX:60; RST_RX:60; SKCC:80; QTH:148; State:55; Country:110; DXCC:60; QSL_SR:0; Grid:0; TXPwr:0; RXPwr:0; Key:50; Comment:200 Radio Configuration: Icom IC-7300 Radio Connected: YES Radio Model Name: Icom IC-7300 Radio Model Number: 19 Radio Protocol: 2 Radio COM Port: /dev/ttyUSB0 Radio Baud Rate: 19200 Radio CIVPort: 94 Radio Parity: None Radio Stop Bits: 1.0 Radio CTS-FC: ON Radio DTR-FC: OFF Radio Xon/Xoff: OFF Radio DTR: OFF Radio RTS: OFF My Callsign: AI8W My SKCC: 20838T My SKCC Nr: 20838 My First Name: Chris My Last Name: Petty My QTH: Dearborn Heights My SPC: MI My DX Code: 291 My Mbr Date: 20190731 My Cent Date: 20191126 My Trib Date: 20191209 My Tx8 Date: My Sen Date: Last Log: /home/chris/Documents/SKCCLogger/Logs/logfile.adi Recent Log: /home/chris/Documents/SKCCLogger/Logs/skcc.adif Recent Log: /home/chris/Documents/SKCCLogger/Recovered-Log.adi Recent Log: /home/chris/Downloads/skcc/SKCCLogger_Linux_64-Bit/Logs/logfile.adi Recent Log: /home/chris/Documents/SKCCLogger/Logs/logfile.adi de AI8W, Chris -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/CM/CC/E/IT/TW d-@ s+:+ !a C++$@ UBLVSCX*++++(on)$>$ P++>$ L+++$ E+@ W++>$ N+++ o+@ K+++ w@ O+@ M-@ V@>$ PS+@ PE@ Y+ PGP++ t+ 5+ X++ R@* tv++ b+>$ DI++ D+ G++ e h r+++ y+++ ------END GEEK CODE BLOCK------ On Sun, Jun 7, 2020 at 4:44 AM Bill Somerville <g4...@classdesign.com> wrote: > Hi Mike, > > you may be correct. Of course Chris had the option not to use the > rigctld-wsjtx provided with WSJT-X, instead reverting to the older rigctld > provided in some other package. If that is the case then some version > incompatibility between Hamlib internal network rig control protocols may > be the case. Such a breakdown seems self-inflicted to me, running the > version of rigctld that works with the most applications being the choice > available. Rather ironic given that original complaint was a wish to use > the latest possible unreleased version of Hamlib from the Hamlib web-site. > > 73 > Bill > G4WJS. > > On 07/06/2020 04:58, Black Michael via wsjt-devel wrote: > > It sounds like SKCClogger was talking to WSJT-X rigctld-wsjtx....is that > possible? > Otherwise I don't see how it could have any effect. > > As another test move the WSJT-X into a subdirectory in WSJT-X and then > move them back one at a time and see if any particular file breaks things. > Most likely to be rigctld-wsjtx. > Can you send a screen shot of SKCClogger's setup referring to hamlib? > > Mike W9MDB > > > > > On Saturday, June 6, 2020, 10:53:26 PM CDT, Topher Petty > <ai8...@gmail.com> <ai8...@gmail.com> wrote: > > > Apparently the statically linked WSJT-X with its own hamlib does... > Neither FLDIGI nor the SKCClogger does these things on startup.. > As SKCClogger is written in Python and references my local copy of hamlib, > this shows that hamlib most likely isn't the issue. > But you're right... I should contact the hamlib team about symptoms that > only appear when I use a software that is statically linked to hamlib and > is the only place where the symptoms occur. > > > On Sat, Jun 6, 2020, 20:17 Bill Somerville <g4...@classdesign.com> wrote: > > On 07/06/2020 01:08, Topher Petty wrote: > > For example: > > I won't report that, for some reason, 2.2.1 seems to cycle my 7300 > > from VFO A to VFO B and back to VFO A on startup, which makes me need > > to press the "TUNE" button again to get the auto-tuner back in sync > > with the radio. I won't report that changing bands to a band 15m and > > above using the dropdown in WJST-X automatically turns my preamp on.. > > sometimes it's Preamp1, others Preamp2, and sometimes not at all. > > I also won't report that both of these behaviors are undesirable. > > de AI8W > > Chris, > > I suggest you report all those issues to the Hamlib team, WSJT-X doesn't > do any of that. > > 73 > Bill > G4WJS. > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
