[wsjt-devel] Reference Spectrum Data
What are the headings for the data fields (columns) in the refspec.dat file that is generated by the Reference Spectrum tool? Robert Rearden ae...@att.net ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Suggestion regarding colors
Suggestion regarding colors. I really love what was done in 2.0. Finally a great logger, many thanks! I miss one enhancement though. When I see a message from one station to another (without CQ or my call), it is in white. It will be very nice if the second call in this message was highlighted, telling me if I worked this station before or not on this band. Example: K1AA ZS1ABC -10. I don’t care about the first station, which I may not ever copy. But since I am receiving ZS1ABC, it would be very nice to know if I worked him before or not. If I did not, I will probably wait till he is done with K1AA and then call him. Otherwise I have to open the adif file and look there manually, which is a hassle. Most of the semi-rare stations hardly call CQ. 73, W0IZ “IZ” ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Mac Mini (late 2014) Problem with 1.9 and 2.0 with Mojave 10.14.2
Aloha David: Ooops, that was just a key stroke error on my part. It really is 8192. I copy/pasted everything, except the last line (by accident), noticed the omission, and then keyed in the remainder, with the last two numbers reversed. Sorry for the confusion, and thanks for finding my error. 73, Jim K6MIO > On Dec 21, 2018, at 6:22 AM, David Tiller > wrote: > > My values are exactly the same as yours except for that last one, so if the > config tests don't solve your issue you might give changing that to 8192 a > shot. > >> On Dec 20, 2018, at 23:01, David Tiller >> wrote: >> >> >>> kern.sysv.shmall: 8129 >> >> For what it's worth, that value looks like a typo - it probably ought to be >> 8192, a power of 2. >> >> >>> On Dec 20, 2018, at 20:13, Jim Kennedy wrote: >>> >>> kern.sysv.shmall: 8129 >> >> >> ___ >> 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 mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] grid square & nonstandard callsign
> On Dec 21, 2018, at 09:44, DX Jami via wsjt-devel > wrote: > > can extra bits be obtained by omitting the worked station's call sign? This can really cause problems when trying to confirm that the report is from the station you think it is from. The idea is to make sure you don’t get a bogus report. This is especially important when working MSK144 as often there are several stations o the same frequency at the same time. Integrity of the exchange comes into question when you leave the “from” field out of the report. Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] grid square & nonstandard callsign
On 12/21/2018 8:44 AM, DX Jami via wsjt-devel wrote: nonstandard call signs such as mine - W4/AH6FX ... or AH6FX/W4 Hi Danny, US callsigns, with no / identifiers, are valid anywhere in the US. While using one is legal, it is completely un-necessary. Your call is AH6FX anywhere in the US, and I view it as a nuisance. I live in California, and my call is K9YC anywhere in the US. The only time that you or I have a good reason to sign /anything would be if we were operating in a contest from a different DXCC entity than our prefix implied. 73, Jim K9YC ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] grid square & nonstandard callsign
> On Dec 21, 2018, at 10:27, Bill Somerville wrote: > > nevertheless sending a grid without the /W4 suffix may still be the best > option if it is legal to do so. And, as others have done, sending free text occasionally with the added info for those who bother to read would help. Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] grid square & nonstandard callsign
On 21/12/2018 16:57, Bill Somerville wrote: I am not fully up to date on FCC regulations but I believe you don't need to sign /W4 with your call. Hi Danny, having read your bio on QRZ.COM I do see that my suggestion may not be such a good idea with Jim, AD1C's, CTY.DAT database as you do operate from Hawaii occasionally, nevertheless sending a grid without the /W4 suffix may still be the best option if it is legal to do so. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] grid square & nonstandard callsign
On 21/12/2018 16:57, Bill Somerville wrote: (there are already several already which I include a sample of below). Hi Danny, I should have added that those sample overrides locate the calls specified in the lower 48 and define their CQ and ITU Zones. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] grid square & nonstandard callsign
On 21/12/2018 16:44, DX Jami via wsjt-devel wrote: Joe, you and I corresponded a few months ago about a similar nonstandard call sign problem - which was overcome. I recently encountered and researched my problem of grids not showing in the new WSJT-X ver 2 for nonstandard call signs such as mine - W4/AH6FX ... or AH6FX/W4. Got dangerous and read the November 26, 2018, /Quick Start Guide/ and postings from this forum. I understand non-grid for those with nonstandard calls is built into ver 2 because of a real estate problem - the 77 bit message payload limitation. Hi Danny, I am not fully up to date on FCC regulations but I believe you don't need to sign /W4 with your call. This may seem perverse but you could then do two more things to help yourself, firstly you can send your grid in CQ calls and replies to CQ calls and secondly you can ask Jim, AD1C, to add an override for your call into his CTY.DAT database which we use for calculating stations DXCC Entity (there are already several already which I include a sample of below). I believe those two steps would cause you far less issues than using a compound callsign that disallows you sending grid squares in standard FT8 exchanges. 73 Bill G4WJS. ,=AH2BW(4)[7],=AH2BY(4)[7],=AH6ES/0(4)[7],=AH6FY(4)[7],=AH6MD(4)[7],=AH6N(4)[7], =AH6N/0(4)[7],=AH6O(4)[7],=AH6OS(4)[7],=AH6RS(4)[7],=AL0G(4)[7],=AL3E(4)[7],=AL6E(4)[7], =AL7BX(4)[7],=AL7FU(4)[7],=AL7GQ(4)[7],=AL7LL(4)[7],=AL7NY(4)[7],=AL7O/0(4)[7],=AL7OC(4)[7], =AL7QQ(4)[7],=AL7QQ/P(4)[7],=AL9DB(4)[7],=KH0EX(4)[7],=KH2CZ(4)[7],=KH2JK(4)[7],=KH2OP(4)[7], =KH2OP/0(4)[7],=KH2SL(4)[7],=KH6DM(4)[7],=KH6GN(4)[7],=KH6HNL(4)[7],=KH6HTV/0(4)[7],=KH6JEM(4)[7], =KH6JFH(4)[7],=KH6NM(4)[7],=KH6NR(4)[7],=KH6RON(4)[7],=KH6SB(4)[7],=KH6TL(4)[7],=KH6UC(4)[7], =KH6VHF(4)[7],=KH6VO(4)[7],=KH7AL/M(4)[7],=KH7AL/P(4)[7],=KH7BU(4)[7],=KH7GF(4)[7],=KH7HA(4)[7], =KH7HY(4)[7],=KH7QI(4)[7],=KH7QJ(4)[7],=KH7QT(4)[7],=KH8CW(4)[7],=KL0DW(4)[7],=KL0EQ(4)[7], =KL0FOX(4)[7],=KL0GP(4)[7],=KL0GQ(4)[7],=KL0MW(4)[7],=KL0UP(4)[7],=KL0WIZ(4)[7],=KL1HT(4)[7], =KL1IF(4)[7],=KL1IF/M(4)[7],=KL1J(4)[7],=KL1LD(4)[7],=KL1PV(4)[7],=KL1TU(4)[7],=KL1V/M(4)[7], =KL1VN(4)[7],=KL2A/0(4)[7],=KL2FU(4)[7],=KL2GR(4)[7],=KL2QO(4)[7],=KL2SX(4)[7],=KL3LY(4)[7], =KL3MA(4)[7],=KL3MB(4)[7],=KL3MC(4)[7],=KL3QS(4)[7],=KL3SM(4)[7],=KL3VN(4)[7],=KL4IY(4)[7], =KL4JN(4)[7],=KL7DE(4)[7],=KL7DTJ(4)[7],=KL7ED(4)[7],=KL7EP(4)[7],=KL7EP/0(4)[7],=KL7GKY/0(4)[7], =KL7GLK(4)[7],=KL7GLK/0(4)[7],=KL7GLK/B(4)[7],=KL7IEI(4)[7],=KL7IXI(4)[7],=KL7JGJ(4)[7], =KL7JIE(4)[7],=KL7JIM(4)[7],=KL7JR/0(4)[7],=KL7MH(4)[7],=KL7MV(4)[7],=KL7NW(4)[7],=KL7PE/M(4)[7], =KL7QW(4)[7],=KL7QW/0(4)[7],=KL7RH(4)[7],=KL7RZ(4)[7],=KL7SB/0(4)[7],=KL7SFD(4)[7],=KL7UV(4)[7], =KL7XH(4)[7],=KL7YL(4)[7],=KL7YY/0(4)[7],=KL7ZD(4)[7],=KL7ZT(4)[7],=KP4ATV(4)[7],=KP4MLF(4)[7], =KP4XZ(4)[7],=NH2LH(4)[7],=NH6CF(4)[7],=NH6WF(4)[7],=NH7CY(4)[7],=NH7FI(4)[7],=NH7XM(4)[7], =NH7ZH(4)[7],=NL7AS(4)[7],=NL7BU(4)[7],=NL7CQ(4)[7],=NL7FF(4)[7],=NL7FU(4)[7],=NL7XT(4)[7], =NL7XU(4)[7],=NP4AI(4)[7],=NP4AI/0(4)[7],=VE4AGT/M(4)[7],=VE4XC/M(4)[7],=WH2S(4)[7],=WH6AKZ(4)[7], =WH6ANH(4)[7],=WH6BLT(4)[7],=WH6BUL(4)[7],=WH6BXD(4)[7],=WH6CTU(4)[7],=WH6CUE(4)[7],=WH6CYM(4)[7], =WH6CZI(4)[7],=WH6CZU(4)[7],=WH6DCJ(4)[7],=WH6DUV(4)[7],=WH6EAE(4)[7],=WH6ENX(4)[7],=WH6LR(4)[7], =WH6MS(4)[7],=WH6QS(4)[7],=WH7DA(4)[7],=WH7IR(4)[7],=WH7MZ(4)[7],=WH7PV(4)[7],=WH9AAH(4)[7], =WL0JF(4)[7],=WL1ON(4)[7],=WL7AEC(4)[7],=WL7AJA(4)[7],=WL7ANY(4)[7],=WL7ATK(4)[7],=WL7BT(4)[7], =WL7CEG(4)[7],=WL7CLI(4)[7],=WL7CPW(4)[7],=WL7CQF(4)[7],=WL7CRT(4)[7],=WL7CY(4)[7],=WL7JB(4)[7], =WL7LZ(4)[7],=WL7LZ/M(4)[7],=WL7RV(4)[7],=WL7YM(4)[7],=WP2B/0(4)[7],=WP3QH(4)[7],=WP3Y(4)[7], =WP4BTQ(4)[7],=WP4GQR(4)[7],=WP4HRK(4)[7],=WP4LC(4)[7],=WP4NPV(4)[7], =AH2V(5)[8],=AH2W(5)[8],=AH6BV(5)[8],=AL0A(5)[8],=AL1O(5)[8],=AL4V(5)[8],=AL6I(5)[8],=AL6L(5)[8], =AL6M(5)[8],=AL7EL(5)[8],=AL7LV(5)[8],=AL7QS(5)[8],=AL8E(5)[8],=KH2EH(5)[8],=KH6GR(5)[8], =KH6HZ(5)[8],=KH6IKI(5)[8],=KH6JUK(5)[8],=KH6RF(5)[8],=KH6RF/1(5)[8],=KH6RF/M(5)[8],=KH7CD(5)[8], =KH7CD/1(5)[8],=KH8AC(5)[8],=KH8AC/1(5)[8],=KL1OC(5)[8],=KL1T(5)[8],=KL1WD(5)[8],=KL2A/1(5)[8], =KL2DM(5)[8],=KL2GA(5)[8],=KL2IC(5)[8],=KL2KL(5)[8],=KL7CE(5)[8],=KL7CE/1(5)[8],=KL7IXX(5)[8], =KL7JHM(5)[8],=KL7JJN(5)[8],=KL7JR/1(5)[8],=KL7JT(5)[8],=KL7LK(5)[8],=KL7USI/1(5)[8],=KL8DX(5)[8], =KP4ANG(5)[8],=KP4BLS(5)[8],=KP4BPR(5)[8],=KP4DGF(5)[8],=KP4EC/1(5)[8],=KP4G(5)[8],=KP4GVT(5)[8], =KP4MR(5)[8],=KP4NPL(5)[8],=KP4NW(5)[8],=KP4R(5)[8],=KP4RCD(5)[8],=NH0H(5)[8],=NH6IH(5)[8], =NH6XW(5)[8],=NH6ZB(5)[8],=NL7FJ(5)[8],=NL7MO(5)[8],=NL7NJ(5)[8],=NL7OI(5)[8],=NL7OT(5)[8], =NL9H(5)[8],=NP2FZ(5)[8],=NP2FZ/1(5)[8],=NP2GG(5)[8],=NP2PN(5)[8],=NP3IV(5)[8],=NP3LN(5)[8], =NP4AO(5)[8],=NP4AZ(5)[8],=NP4ER(5)[8],=VE1BES/M(5)[8],=VE3CMB/M(5)[8],=VE4CCN/M(5)[8],
[wsjt-devel] grid square & nonstandard callsign
Hello, Joe, you and I corresponded a few months ago about a similar nonstandard call sign problem - which was overcome. I recently encountered and researched my problem of grids not showing in the new WSJT-X ver 2 for nonstandard call signs such as mine - W4/AH6FX ... or AH6FX/W4. Got dangerous and read the November 26, 2018, Quick Start Guide and postings from this forum. I understand non-grid for those with nonstandard calls is built into ver 2 because of a real estate problem - the 77 bit message payload limitation. I am hoping you all will fix the issue in some way. I understand the bit allocation and limitation. Wondering if you all considered trade offs to allow non-standard calls to show grids. Are there any unnecessary QSO exchanges? For instance in TX3, can extra bits be obtained by omitting the worked station's call sign? Or maybe truncate the call to its prefix. After all, the QSO handshake has been made so why transmit the other station's call again [just for nonstandard calls]. Maybe there are other areas for trading bits. Also, perhaps including nonstandard call sign stations in the Advanced tab under Special Operating Activity. Perhaps a unique, but permanent, block can remain checked allowing "special" message formatting such as those for contests, field days, et al? Wonder if KH1/KH7Z would have a non-grid problem ... or does fox & hound resolve that issue? [perhaps it is important to allow the "nonstandard call" box to remain checked when also checking "Hound" or "ARRL Field Day," etc.] Lastly ... maybe something can be done on the receive side for real estate management purposes. Perhaps a database of nonstandard call types may be linked to the grid square pop up, log, and logging screens showing the grid. For instance, P5/K1ABC appears as grid PN30 in North Korea. [[granted - maybe the database generates a "center of mass" or capital city grid ... but the correct grid may be user-obtained from QRZ and substituted for the "placeholder grid."]] The shortfall here would be the grid only visible in the grid square pop up log and QSO log ... and not displayed in the standard message sequence portion of the Band Activity screen. But maybe that shortfall can be overcome too by making everything seamlessly normal for nonstandard call signs. Most of my P5 comments seem to relate to the receive station ... the sending P5/K1ABC station ideally includes the grid in his transmission sequence - but the receive side work around is intended if there is no fix for nonstandard calls generating grids. Just a few thoughts. I am sure I am not alone with this problem. My challenge on the east coast with a Hawaiian call is controlling expectation. Even with versions 1.8.* and 1.9.* working perfectly ... I still have hams emailing me for Hawaiian QSLs, or insisting I was in Hawaii. I am dealing with that. Also as version 2 is currently programmed, everyone must lookup my grid in QRZ or just slam in a fake grid just to save the QSO to a log. Thanks very much for your consideration. I am very appreciative of what you all have done for the ham radio community. Season's Greetings, Danny AH6FX/W4 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Mac Mini (late 2014) Problem with 1.9 and 2.0 with Mojave 10.14.2
My values are exactly the same as yours except for that last one, so if the config tests don't solve your issue you might give changing that to 8192 a shot. > On Dec 20, 2018, at 23:01, David Tiller wrote: > > >> kern.sysv.shmall: 8129 > > For what it's worth, that value looks like a typo - it probably ought to be > 8192, a power of 2. > > >> On Dec 20, 2018, at 20:13, Jim Kennedy wrote: >> >> kern.sysv.shmall: 8129 > > > ___ > 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] Log popup grid/freq
Shouldn't your grid and frequency be the log QSO popup?Seems to me all the information.that goes int the ADIF log should be in the popup. de Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
