Re: [wsjt-devel] Color Highlighting - works after reboot
Rebooted -- now seems to be working. So much for not having to reboot Linux. If you are switching between RC2 and RC3 on Linux it seems that you need to reboot. There is probably a file (the log file perhaps) still open. djb On 10/17/18 12:20 PM, Neil Zampella wrote: Could you explain .. "hopelessly broken" ... did you check to see if the 'worked B4' setting is checked under colors? Are you sure you didn't wipe out your log files with the install? More information is helpful so that the developers can figure if there is a problem or not. Neil, KN3ILZ On 10/17/2018 12:43 PM, Dave J Barnes wrote: Color highlighting for worked before status is broken too. RC2 worked, RC3 appears hopelessly broken. --- This email has been checked for viruses by AVG. https://www.avg.com ___ 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
[wsjt-devel] Color Highlighting
Color highlighting for worked before status is broken too. RC2 worked, RC3 appears hopelessly broken. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Color Highlighting
It works on some entries in my log but not others. It flags some LOTW users but ignores others, etc. Also the left panel flashes when updating. Doesn't matter what band. The log file was cleaned before I started using RC2. There should not be any bad entries in the log file. I switched back to RC2 to verify that highlighting my current log file works correctly. This is on Ubuntu 18.04. I'll switch back to RC3 to try to get some examples. djb On 10/17/18 11:58 AM, Bill Somerville wrote: On 17/10/2018 17:43, Dave J Barnes wrote: Color highlighting for worked before status is broken too. RC2 worked, RC3 appears hopelessly broken. Hi Dave, we need something more helpful that "appears hopelessly broken". Are any decodes being highlighted as not worked before? Is it just DXCC, or grids, or unique calls? Is it just the band specific versions that are not working or the all bands versions? Are the highlighting options you expect to see enabled in "Settings->Colors"? If you have a specific example with data to back your assertion i.e. the lines in your wsjtx_log.adi that are there/missing that make the highlighting wrong, that would be most helpful. 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
Re: [wsjt-devel] LoTW error
Worked before status color doesn't work either. Or, at least it works differently than RC2. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Color Highlighting - foreground color
Am I the only one that can not set the foreground color in anything other LOTW? I set the foreground color of "CQ in message" to blue: View color highlighting scheme shows the blue text. Text is still black in "Band Activity" panel. RC3 - Ubuntu 18.04 AMD64 djb ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Weird Auto Seq Bug?
Station A called CQ I answered Station A with my call and grid Station A sends report I send station A my R+ report below messages decoded together at same time on same frequency Apparently another station, B, was in contact with A previously - Station B sends station A 73 message Station A sends me RRR For some reason, my next message is to station B with my grid and not 73 to station A _ I should have saved the message window but I was caught off guard by the unusual sequence. If I see it again I'll save the screen. djb ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Color Highlighting
RC3 on Ubuntu 18.04 AMD64, empty log file so everything would be highlighted. (1) Highlighting NEW DX and NEW DX ON BAND does not work. Nothing highlighted. Yes those types are enabled in the color settings. (2) Can set foreground color on LOTW only. Can not set foreground colors elsewhere. Text color stays black regardless of foreground color in settings other than for LOTW. (3) If you set an LOTW background you can not change it back to transparent without resetting all of the other colors to default. (4) If you set an LOTW background then the left panel flickers like it is drawing the first color and then drawing the LOTW background color over it. (5) I want to set up: NEW DX -or- NEW DX ON BAND -or- NEW GRID -or- NEW GRID ON BAND -and- LOTW. Anything I set up gives trouble. For example, with the default settings, an LOTW station calling me would have a red background with red text on the right panel. You can not see who is calling. Similarly, a new GRID LOTW station calling CQ would have red text on an orange background in the left panel. Almost invisible. How is this new highlighting feature intended to be used? Can you set a default color scheme that works? djb ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] V2.0 - Extra Spaces
What are the extra spaces for? extra spaces v--v 032800 -10 0.1 1156 ~ CQ W0ERB EM19 U.S.A. 032800 1 0.1 2003 ~ CQ KG5HTH EM02 a1 U.S.A. 032800 -16 0.2 2799 ~ CQ ZS6CR KG43 S. Africa ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Contest: Problems with exchange info logging
Ubuntu 18.04 AMD64 4 contacts - first two had to enter "rpt sent" and "exch sent" in log dialog box. Exited and restarted wsjt-x. Second two, still had to enter "rpt sent" and "exch sent". Both fields blank. Log looks OK so far. djb ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Frequency selector dropdown
Bill, It looks like a Qt bug to me. I had deleted all of the UHF and above frequencies from the frequency list. That is why the combo box list was too narrow. I added a 10 GHz frequency back to the frequency list. Now the combo box list is wide enough for everything but the 10 GHz entry. HTH djb ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] RU Contest - crash when logging
Linux Ubuntu MATE 18.04.1 AMD64
Popup box: Subprocess error
Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a
/home/superman/.local/share/WSJT-X -t /tmp/WSJT-X
Process crashed
Console error:
[20181119 20:23:16.319 CST W] QProcess: Destroyed while process
("/usr/bin/jt9") is still running.
After I click OK in popup box:
Console error:
Error: Database Error: NOT NULL constraint failed:
cabrillo_log.exchange_sent Unable to fetch row
Note that contact is logged in wsjtx_log.adi
ZF1EJ EK99 FT8 559
559 20181120 022130
20181120 022300 40m 7.080491
WB4KDI EM63pj 0012
djb
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.0.1 - LOTW highlight bug?
Linux Ubuntu 18.04.2 AMD64 Version 2.0.0 worked fine. Version 2.0.1 doesn't properly highlight LOTW entries until a new lotw-user-activity.csv is downloaded. I have to download a new lotw-user-activity.csv every time version 2.0.1 is restarted. Has the lotw-user-activity.csv moved? Or is it being deleted somehow? Can WSJT-X 2.0.1 not open the file for some reason? My current lotw-user-activity.csv file is located at "~/.local/share/WSJT-X - K3" as I am using "--rig-name K3". djb ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.0.1: Hamlib NET rigctl regression?
This is 2.0.1 - 2.0.0 works fine. On 3/10/19 6:57 AM, Black Michael via wsjt-devel wrote: Fixed in WSJT-X 2.0.1 -- so please upgrade. On Saturday, March 9, 2019, 10:22:41 PM CST, Dave J Barnes wrote: Rig controlled with Quisk is Multus Proficio SDR. superman@WB4KDI-0:~$ rigctld-wsjtx -m 2 -r localhost:4532 -v Recommend using --vfo switch for rigctld rigctl and netrigctl will automatically detect vfo mode rigctld, Hamlib 4.0~git Report bugs to <mailto:hamlib-develo...@lists.sourceforge.net> rig_init called dummy: _init called rig_register called rig_register: rig_register (1) rig_register called rig_register: rig_register (2) rig_register called rig_register: rig_register (4) rig_register called rig_register: rig_register (5) netrigctl_init version 1.1b rig_open called port_open called network_open called network_open version 1.0 netrigctl_open called netrigctl_transaction: called len=9 network_flush called network_flush: len <= 0, len=0/0x0 write_block called write_block(): TX 9 bytes 5c 63 68 6b 5f 76 66 6f 0a \chk_vfo. read_string called read_string(): RX 8 characters 52 50 52 54 20 2d 34 0a RPRT -4. rig_open: error = Feature not implemented superman@WB4KDI-0:~$ On 3/9/19 9:59 PM, Black Michael via wsjt-devel wrote: What rig do you have? If you run rigctld-wstjx with 5 v's you can see what it's doing and let us see it too when it gets the error. rigctld-wsjtx -r com1 -s 9600 -v de Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto: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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.0.1: Hamlib NET rigctl regression?
Rig controlled with Quisk is Multus Proficio SDR. superman@WB4KDI-0:~$ rigctld-wsjtx -m 2 -r localhost:4532 -v Recommend using --vfo switch for rigctld rigctl and netrigctl will automatically detect vfo mode rigctld, Hamlib 4.0~git Report bugs to rig_init called dummy: _init called rig_register called rig_register: rig_register (1) rig_register called rig_register: rig_register (2) rig_register called rig_register: rig_register (4) rig_register called rig_register: rig_register (5) netrigctl_init version 1.1b rig_open called port_open called network_open called network_open version 1.0 netrigctl_open called netrigctl_transaction: called len=9 network_flush called network_flush: len <= 0, len=0/0x0 write_block called write_block(): TX 9 bytes 5c 63 68 6b 5f 76 66 6f 0a \chk_vfo. read_string called read_string(): RX 8 characters 52 50 52 54 20 2d 34 0a RPRT -4. rig_open: error = Feature not implemented superman@WB4KDI-0:~$ On 3/9/19 9:59 PM, Black Michael via wsjt-devel wrote: What rig do you have? If you run rigctld-wstjx with 5 v's you can see what it's doing and let us see it too when it gets the error. rigctld-wsjtx -r com1 -s 9600 -v de Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSJT-X 2.0.1: Hamlib NET rigctl regression?
Linux Ubuntu 18.04.2 AMD64 Connecting wsjtx to Quisk using Hamlib NET rigctl - "Feature not implemented?" Used to work with wsjtx 2.0.0. No info on console. Quisk is listening: State Recv-Q Send-Q Local_Address:Port Peer_Address:Port LISTEN 0 0 127.0.0.1:4532 0.0.0.0:* Has something changed in Hamlib? djb ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Split, K3 and TS-450 Rig Control
Any help for Linux users? On 12/1/21 10:16 PM, Black Michael via wsjt-devel wrote: Please try the latest dll. This version is due to be 4.4 to be released in the next few days. New hamlib for Windows installation directions #1 Shut down WSJTX #2 Download either the 32-bit or 64-bit DLL -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll #3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser. https://www.youtube.com/watch?v=AyVqCJrs9dk Mike W9MDB On Wednesday, December 1, 2021, 09:29:38 PM CST, Dave J Barnes via wsjt-devel wrote: I looked through the archives but I don't see any resolution to the rig control issues with using split on the TS-450. Split is broken on the K3 too. The only setting that works is "fake it". Using "rig" for split on the K3 will try to adjust the tx frequency to keep the tones in the passband but then quickly changes back to the receive frequency thus transmitting on the wrong frequency. I believe this bug is why the middle of the FT8 segment stays crowded. It used to work. I verified that 2.40 works as I remember -- "rig" split mode keeps the tx frequency adjusted for the passband. Is there an additional setting I need? wsjtx 2.5.2 Linux 64 bit Ubuntu 20.04 djb WB4KDI ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Split, K3 and TS-450 Rig Control
I looked through the archives but I don't see any resolution to the rig control issues with using split on the TS-450. Split is broken on the K3 too. The only setting that works is "fake it". Using "rig" for split on the K3 will try to adjust the tx frequency to keep the tones in the passband but then quickly changes back to the receive frequency thus transmitting on the wrong frequency. I believe this bug is why the middle of the FT8 segment stays crowded. It used to work. I verified that 2.40 works as I remember -- "rig" split mode keeps the tx frequency adjusted for the passband. Is there an additional setting I need? wsjtx 2.5.2 Linux 64 bit Ubuntu 20.04 djb WB4KDI ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Split, K3 and TS-450 Rig Control
So a new version of wsjtx is coming in a few days? On 12/1/21 10:49 PM, Black Michael via wsjt-devel wrote: You should be able to build it yourself from the tar.gz file. Just be sure to remove the hamlib package you already have installed as it installs in /usr/local Or you can configure it this way ./configure --prefix=/usr Mike W9MDB On Wednesday, December 1, 2021, 10:24:03 PM CST, Dave J Barnes via wsjt-devel wrote: Any help for Linux users? On 12/1/21 10:16 PM, Black Michael via wsjt-devel wrote: Please try the latest dll. This version is due to be 4.4 to be released in the next few days. New hamlib for Windows installation directions #1 Shut down WSJTX #2 Download either the 32-bit or 64-bit DLL -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll <http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll> http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll <http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll> #3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser. https://www.youtube.com/watch?v=AyVqCJrs9dk <https://www.youtube.com/watch?v=AyVqCJrs9dk> Mike W9MDB On Wednesday, December 1, 2021, 09:29:38 PM CST, Dave J Barnes via wsjt-devel <mailto:wsjt-devel@lists.sourceforge.net> wrote: I looked through the archives but I don't see any resolution to the rig control issues with using split on the TS-450. Split is broken on the K3 too. The only setting that works is "fake it". Using "rig" for split on the K3 will try to adjust the tx frequency to keep the tones in the passband but then quickly changes back to the receive frequency thus transmitting on the wrong frequency. I believe this bug is why the middle of the FT8 segment stays crowded. It used to work. I verified that 2.40 works as I remember -- "rig" split mode keeps the tx frequency adjusted for the passband. Is there an additional setting I need? wsjtx 2.5.2 Linux 64 bit Ubuntu 20.04 djb WB4KDI ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Late, much delayed, and missed decodes
System: Linux Ubuntu 22.10 8 Core CPU, 16GB Memory WSJTX 2.6.0, 2.6.1 Starting with RC5, seeing random cases where the decodes either get dropped or appear very late. See jt9.exe take 100% single core for up to 10 seconds into the next decode period. Have seen decode button stay highlighted through to the next decode cycle. jt9.exe ends or crashes but decode still highlighted. Decode sequence gets scrambled. See below: 031130 11 -0.2 2305 ~ CQ AC3DP FM19 U.S.A. 031145 Tx 2305 ~ AC3DP WB4KDI EM63 031215 Tx 2305 ~ AC3DP WB4KDI EM63 031200 15 -0.2 2305 ~ WB4KDI AC3DP +13 031217 Tx 2305 ~ AC3DP WB4KDI R+15 031245 Tx 2305 ~ AC3DP WB4KDI R+15 031230 6 -0.2 2305 ~ WB4KDI AC3DP RR73 ? a3 031315 Tx 2305 ~ AC3DP WB4KDI 73 031300 7 -0.2 2305 ~ WB4KDI AC3DP RR73 I have no idea what is going on. Happens at random. Weak signals or strong. Dave Barnes WB4KDI ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
