[Dxspider-support] DXSpider v 1.55 build 0.221

Steve - AA4U aa4u at mchsi.com
Fri Dec 10 16:28:32 GMT 2021


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


More information about the Dxspider-support mailing list