<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">Thanks for the explanation!</div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Verizon, Samsung Galaxy smartphone</div></div><div dir="auto"><br></div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: Dirk Koopman via Dxspider-support <dxspider-support@tobit.co.uk> </div><div>Date: 12/10/21 09:44 (GMT-06:00) </div><div>To: "Mike McCarthy, W1NR via Dxspider-support" <dxspider-support@tobit.co.uk> </div><div>Cc: Dirk Koopman <djk@tobit.co.uk> </div><div>Subject: Re: [Dxspider-support] DXSpider v 1.55 build 0.221 </div><div><br></div></div>There's an interesting little conundrum...<br><br>It turns out that this is (and now was) Mojo behaviour, which I clearly <br>put in deliberately, in July last year [ed: git blame is good here]) - <br>which then got back ported to master in order to get the set/width <br>command and auto sizing console.pl there as well as in mojo. I may not <br>have been completely awake at the time of the original mod.<br><br>Anyway, there is another problem which has been there since I started <br>putting stuff into these slots around the time field (ie since 2003), <br>which is that the slots were not treated independently from each other. <br>Which meant that the first of the [grid, itu, cq, us state] (depending <br>on whether they are set) that matched for the spot would win and if <br>there was no entry for available for the other slot in that category (eg <br>G working W or one has a known grid square and the other doesn't) then <br>it would prevent the other slot being filled with coarser (as in <br>location area) information. Also the order was wrong as usstate was <br>last, instead of second after grid square. So, as I was in there fixing <br>the reported problem and, given that this was the general idea in the <br>first place - which has never actually worked as I intended in 2003 - <br>and has been never addressed or noticed since. I have now fixed it thusly:<br><br>DX de W3LPL: 18085.3 OY1CT Heard in PA 14 1532Z FM19<br>DX de DL4MFF: 21074.0 AF4HX JN57IW<>EM85MM tnx <br>ft8 NC 1532Z 14<br>DX de EA8CPU: 7108.0 EA1GFC Especial Naviad inf ea1fdd <br>1cot. 14 1532Z 33<br>DX de F6ARC: 7007.0 VU2TMP CQ 22 1532Z 14<br>DX de SP5ELA: 3524.7 SM4CUQ CQN 14 1533Z KO02<br>DX de DM8MH: 7074.0 MW7CCS FT8 -09dB from IO81 699Hz <br>73! 14 1533Z JO51<br>DX de I3LTT: 7173.0 IT9JAV DMSM SM1743 + Strenna <br>Natale JM67 1533Z JN65<br>DX de W3PRL: 14254.0 HA8JV KN06 1533Z FN00<br>DX de TI3ATS: 7175.0 TI2BSH POTA ACTIVATION Call him <br>!! 7 1533Z EJ89<br>DX de UR6EM: 144360.0 DJ6OL MSK144 +2 dB CQ JO52 1534Z 16<br>DX de N6OKU: 14222.0 LA4UOA 59 in CA 14 1534Z CA<br>DX de OE6PID: 7173.0 IT9JAV DMSM SM1743 + Strenna <br>Natale JM67 1534Z JN77<br>DX de DM8MH: 7074.0 ON5MEV FT8 +03dB from JO10 2706Hz <br>73! 14 1534Z JO51<br>DX de LZ2YO: 3764.0 LZ5RO JJ00 1534Z KN13<br>DX de K6VHF: 50260.0 KI0E DM43<MS>DN13 ID 1534Z DM43<br>DX de F1TXI: 21074.0 K1TKS IN96<>FN42 MA 1535Z IN96<br><br>This is what set/dxgrid + set/usstate + set/dxcq or set/dxitu now gives <br>you.<br><br>Obviously you can have just one or two of these active at once. <br>Set/dxitu and set/dxcq remain mutually exclusive.<br><br>Enjoy<br><br>Dirk G1TLH<br><br>On 10/12/2021 12:56, Mike McCarthy, W1NR via Dxspider-support wrote:<br>> I needed to do an unset/dxgrid to see states<br>><br>> W1NR<br>><br>> On 12/10/2021 7:22 AM, Dirk Koopman via Dxspider-support wrote:<br>>> On my test master branch machine (callsign GB7TLH-1) it appears to be <br>>> working. Here is an (edited) example from<br>>> a few moments ago. It has a fresh usdb.<br>>><br>>> DX de DD0UM: 14157.0 W4RN VA 1213Z<br>>> DX de WZ1V: 50145.0 K9DRG FN31<>EN70 IN 1213Z CT<br>>> DX de W5EME: 144289.0 N5XO/B EM32AI<TR>EL09UM <br>>> 519 1214Z LA<br>>> DX de W5EME: 144275.0 AB5N/B EM32AI<TR>EM34LM <br>>> 599 1215Z LA<br>>> DX de W4HLR: 50145.0 WZ1V EM56JB<MS>FN31RH <br>>> tnx CT 1215Z TN<br>>> DX de PD5CZB: 14157.0 W4RN great signal 73, <br>>> usb VA 1216Z<br>>> DX de KC1GTK: 14270.0 MM0OPX 1217Z NH<br>>> DX de N2OIT: 14288.0 M0XXT 55 1217Z PA<br>>> DX de KC1GTK: 14195.0 R200NN 1218Z NH<br>>> DX de KD2WDR: 50260.0 K1SIX FN30GS<>FN43 -6dB 1495 Hz <br>>> hrd NH 1218Z NY<br>>><br>>> Dirk G1TLH<br>>><br>>> On 10/12/2021 12:12, Anthony (N2KI) via Dxspider-support wrote:<br>>>> Confirmed, No US State appended to an announcement bld221<br>>>><br>>>> Regards,<br>>>><br>>>> Anthony (N2KI)<br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>> On Fri, Dec 10, 2021 at 1:17 AM Steve - AA4U via Dxspider-support <br>>>> <dxspider-support@tobit.co.uk <mailto:dxspider-support@tobit.co.uk>> <br>>>> wrote:<br>>>><br>>>> Initially it appeared all was working properly after updating.<br>>>> But, I now see the 'set/usstate' command doesn't show the 2-letter<br>>>> state anymore. I verified the US Database is loading at cluster<br>>>> start-up.<br>>>><br>>>> I didn't change anything on the cluster, just did a 'git reset<br>>>> --hard' and 'git pull' (same process as has been done dozens of<br>>>> times in the past). Then, restarted the node.<br>>>><br>>>> I'm curious if anyone else has this issue after updating.<br>>>><br>>>> 73, Steve - AA4U<br>>>><br>>>><br>>>> Sent from my Verizon, Samsung Galaxy smartphone<br>>>><br>>>><br>>>> -------- Original message --------<br>>>> From: Steve - AA4U via Dxspider-support<br>>>> <dxspider-support@tobit.co.uk <br>>>> <mailto:dxspider-support@tobit.co.uk>><br>>>> Date: 12/9/21 22:02 (GMT-06:00)<br>>>> To: The DXSpider Support list <dxspider-support@tobit.co.uk<br>>>> <mailto:dxspider-support@tobit.co.uk>>,<br>>>> dxspider-support@dxcluster.org<br>>>> <mailto:dxspider-support@dxcluster.org><br>>>> Cc: Steve - AA4U <aa4u@mchsi.com <mailto:aa4u@mchsi.com>><br>>>> Subject: [Dxspider-support] DXSpider v 1.55 build 0.221<br>>>><br>>>><br>>>> Successfully updated from build 0.218 to 0.221 (non-MOJO)<br>>>><br>>>> Everything appears to be working properly.<br>>>><br>>>> 73, Steve - AA4U<br>>>><br>>>><br>>>> Sent from my Verizon, Samsung Galaxy smartphone<br>>>><br>>>><br>>>> _______________________________________________<br>>>> Dxspider-support mailing list<br>>>> Dxspider-support@tobit.co.uk <mailto:Dxspider-support@tobit.co.uk><br>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br>>>> <https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support><br>>>><br>>>><br>>>> _______________________________________________<br>>>> Dxspider-support mailing list<br>>>> Dxspider-support@tobit.co.uk<br>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br>>><br>>><br>>> _______________________________________________<br>>> Dxspider-support mailing list<br>>> Dxspider-support@tobit.co.uk<br>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br>>><br>><br>> _______________________________________________<br>> Dxspider-support mailing list<br>> Dxspider-support@tobit.co.uk<br>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br><br><br>_______________________________________________<br>Dxspider-support mailing list<br>Dxspider-support@tobit.co.uk<br>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br></body></html>