Allmon3 showing incorrect mode(s) when placing node into Monitor

[KD5KNR]

Describe the bug
Using iaxRpt as the primary connection to a node, if one connects another node into Monitor Mode, Allmon3 will show all connections as being in Monitor mode. But when one runs "rpt xnode " the response in RPT_ALINKS shows the iaxRPT node is in Transcieve mode (which it should be).

Also, if one changes a node to "Local Monitor" the mode for that node is displayed as UNSET and is not heard by anything.

Expected behavior

1. Nodes that are in Transceive should remain in Tranceive, recardless of the settings of other nodes.
2. Nodes specifically placed into Monitor Mode should be changed appropriately. Placing any one node into Monitor Mode should not change or affect any other nodes.
3. Changing a node to Local Monitor should change any other node, just the one being changed to Local Monitor.

Screenshots

Output from "rpt xnode 451050"
RPT_TXKEYED=0
RPT_NUMLINKS=20
RPT_LINKS=20,TKD5KNR,R516220,R3372418,RKB5GLV,R473543,RKD5KNR,RKB5GLV,RWD5M,R590981,RKB5GLV,RWD5M,RWD5M,R473542,RWD5M,RKB5GLV,RKD5KNR,R473541,RWD5M,RKB5GLV,RKD5KNR
RPT_NUMALINKS=2
RPT_ALINKS=2,KD5KNRTU,516220RU
RPT_ETXKEYED=0
RPT_RXKEYED=0
RPT_AUTOPATCHUP=0

Version Info
Allmon v3 1.4.1

[jxmx]

if one changes a node to "Local Monitor" the mode for that node is displayed as UNSET and is not heard by anything.

I"m not sure what you mean by this? Are you talking about an Allmon3 display issue or are you talking about a functional issue with app_rpt?

[KD5KNR]

Jason, Yes, I was referring to the Allmon3 display. The NWS Fort Worth Radio Desk SKYWARN Team utilizes AllStarLink and Remote Bases located at the Weather Forecast Office to provide us with remote capabilities to all our radios located at the NWS, as well as several Remote Bases located elsewhere in our 46 County Warning Area. Many of us utilize iaxRpt to connect to the RB or other AS Nodes as needed. Many time we have several connections our individual AS Nodes and change the Modes from either Transceive, Monitor, or Local Monitor as needed. This allows an operator to monitor several radios at one time and prevents cross-linking of all the connected nodes and/or radios. I noticed last night, during a severe weather event, that when I would connect to multiple nodes in Monitor Mode that Allmon3 would show my iaxRpt connection as being in Monitor Mode. This appeared to be a bug as I was still able to transmit from my AS Node via my iaxRPT connected computer to a node that was in Transceive mode. And, if I placed any of the “monitored” nodes into “Local Monitor” mode their status changed to “UNSET”. Unfortunately, this morning I cannot duplicate the same problem as I tried to describe in the report last night. The only thing I can confirm is that when placing a node into “Local Monitor” the mode is displayed as UNSET. In the image below, KD5KNR is my iaxRPT computer connection, 473546 is a RB at the NWS Radio Desk, and 55436 is a Wide-Area linked repeater system (connected as Local Monitor mode). ***@***.*** Regards, = = = Billy Mason From: Jason McCormick ***@***.***> Sent: Tuesday, November 5, 2024 09:06 To: AllStarLink/Allmon3 ***@***.***> Cc: Billy Mason ***@***.***>; Author ***@***.***> Subject: Re: [AllStarLink/Allmon3] Allmon3 showing incorrect mode(s) when placing node into Monitor (Issue #260) You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> if one changes a node to "Local Monitor" the mode for that node is displayed as UNSET and is not heard by anything. I"m not sure what you mean by this? Are you talking about an Allmon3 display issue or are you talking about a functional issue with app_rpt? — Reply to this email directly, view it on GitHub<#260 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM4UE6MK4I5MBMNLW7EHXLLZ7DNFXAVCNFSM6AAAAABRFLLYQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXGQYTOOJSHA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[jxmx]

Ok. THanks for the clarification. I'll do some testing. The Local Monitor mode is not commonly used.

[KD5KNR]

Thanks so much for Looking into this. Billy Mason

…

________________________________ From: Jason McCormick ***@***.***> Sent: Tuesday, November 5, 2024 10:28:41 AM To: AllStarLink/Allmon3 ***@***.***> Cc: Billy Mason ***@***.***>; Author ***@***.***> Subject: Re: [AllStarLink/Allmon3] Allmon3 showing incorrect mode(s) when placing node into Monitor (Issue #260) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Ok. THanks for the clarification. I'll do some testing. The Local Monitor mode is not commonly used. — Reply to this email directly, view it on GitHub<#260 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM4UE6OJC5W5WK4UDOIJA4TZ7DW3TAVCNFSM6AAAAABRFLLYQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXGYZTQNRSGU>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[wd5m]

Billy and I volunteer together for the WX5FWD team. After looking at this further, the reason this occurs is because the node list returned in LinkedNodes from AMI includes nodes connected to adjacent connected nodes. Our IaxRpt client may be connected to both the monitoring hub, e.g. 516220, and remote base node(s), e.g. 473541, which is also connected to the hub node in monitor mode. This results in LinkedNodes containing multiple entries for our IaxRpt node(s), and those may have the "T" or "R" flag. We select the hub node in IaxRpt when monitoring multiple remote bases, then we select the desired remote base node on IaxRpt to transmit.

The RPT_ALINKS list of nodes only contains adjacent connected nodes. If the status flag is pulled from that list, it should display correctly in Allmon3. I modified Supermon locally to do exactly this, and it works. RPT_ALINKS is returned from AMI by "xstat", while LinkedNodes is returned by "sawstat".

As for the UNSET being displayed, nodes connected in Local Monitor mode are not included in the LinkedNodes or RPT_ALINKS lists. Perhaps change code to display "Local Monitor" instead of UNSET when the node connected but not found in the RPT_ALINKS/LinkedNodes list, and the mode is left unset ?

Thanks for your work on Allmon3!

Regards,
David McAnally, WD5M
WX5FWD SKYWARN Team

[jxmx]

The connections table is built using the xstat AMI command with the value being set looping through the LinkedNodes attribute. It will not display adjacent nodes's links but there may be a special case for linking in loops. However the status will always follow a "last one wins" strategy if a node appears more than once. I'm not able to replicate your issue however.

[jxmx]

When allmon3 is showing the weirst status, can you stop the allmon3 process and run it manually as allmon3 --debug and capture a few cycles of the output?