Auto disconnect node after specified amount of inactivity time?

Is there a way to schedule the node to automatically disconnect all connected nodes after a specified amount of time with no activity? I’m assuming this could be programmed with a script of some sort, but I’m still new to AllStar and Linux and learning as I go.

73,
Larry
N6LKA

There is a way to disconnect when there’s no activity on your node. It called an Elke Link.

https://wiki.allstarlink.org/wiki/Elke_Link

Is that what you want?

Does that actually disconnect the linked node, or does it silence it and prevent the node from transmitting while asleep?

It prevents traffic from remote node keying up the local repeater. Or as you said it, it silences the linked node.

I think that what you are looking for might be one of these commands.

remote_inact_timeout=1800
remote_timeout=3600

I think the units are seconds and I think the commands are self explanatory. I have used these in my nodes and they work fine.

When they reach the timeout the remote node disconnects.

In the example it disconnects in one hour even if in use. It disconnects in 30 minutes if it is not being used.

Chuck

···

On Sat, Aug 24, 2019 at 4:22 PM Tim Sawyer via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:


wd6awp
ASL Admin

    August 24

It prevents traffic from remote node keying up the local repeater. Or as you said it, it silences the linked node.


Visit Topic or reply to this email to respond.


In Reply To


N6LKA

    August 23

Does that actually disconnect the linked node, or does it silence it and prevent the node from transmitting while asleep?


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

Thank you. That is what I was looking for. All the times I’ve edited the rpt.conf file I never saw those commented out. Lol

73,

Larry

N6LKA

···

From: Chuck Henderson via AllStarLink Discussion Groups noreply@community.allstarlink.org
Sent: Saturday, August 24, 2019 4:28:23 PM
To: n6lka@outlook.com n6lka@outlook.com
Subject: [AllStarLink Discussion Groups] [App_rpt-users] Auto disconnect node after specified amount of inactivity time?

Chuck_Henderson
Chuck_Henderson

August 24
I think that what you are looking for might be one of these commands.

remote_inact_timeout=1800
remote_timeout=3600

I think the units are seconds and I think the commands are self explanatory. I have used these in my nodes and they work fine.

When they reach the timeout the remote node disconnects.

In the example it disconnects in one hour even if in use. It disconnects in 30 minutes if it is not being used.

Chuck

···
(click for more details)

Visit
Topic
or reply to this email to respond.

In Reply To

wd6awp
wd6awp

ASL Admin

August 24
It prevents traffic from remote node keying up the local repeater. Or as you said it, it silences the linked node.

Visit
Topic
or reply to this email to respond.

To unsubscribe from these emails,
click here
.




I have those working on my very old system running the ACID versions, but I tried it on my rpi just now and it does not work there. They are designated as “remote base” functions but I had them working for normal nodes. Now I am wondering if to have them work for normal node connections, maybe I made a change to the code and recompiled. That was so long ago I don’t remember. I will have to dig into the code and see if I can figure out what I might have done or if the code has changed since then. In any case it might not work at this time. But let me know your results.
Chuck

···

On Sat, Aug 24, 2019 at 7:04 PM Larry AYCOCK via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:


N6LKA

    August 24

Thank you. That is what I was looking for. All the times I’ve edited the rpt.conf file I never saw those commented out. Lol

73,

Larry

N6LKA

··· (click for more details)


Visit Topic or reply to this email to respond.


In Reply To


Chuck_Henderson

    August 24

I think that what you are looking for might be one of these commands. remote_inact_timeout=1800 remote_timeout=3600 I think the units are seconds and I think the commands are self explanatory. I have used these in my nodes and they work fine. When they reach the timeout the remote node disconnec…


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

Is the remote link disconnect timer working for a regular link?

It is working on a very old ACID system that has not been updated since long before Jim passed. But it is not working on a Raspberry Pi system that was built in the last couple of months. The ACID system has many hand coded options, some done by me and some done by Jim Dixon doing a remote connection to the system. I never know if what he did to my system ever got rolled into the main code base.
Chuck

···

On Sun, Aug 25, 2019 at 9:22 AM Tim Sawyer via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:


wd6awp

      ASL Admin




    August 25

Is the remote link disconnect timer working for a regular link?


Visit Topic or reply to this email to respond.


In Reply To


N6LKA

    August 24

Thank you. That is what I was looking for. All the times I’ve edited the rpt.conf file I never saw those commented out. Lol 73, Larry N6LKA ··· (click for more details)


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

You probably have the modified source on your ACID system. Would like you like to find the remote timeout code and add that to the current source?

My next week is too full but I will try to find some time the week after to look into it further. The ACID system’s 1TB hard drive has dozens of versions of the code on it and they are not well organized. I usually tried to back up the code before it underwent surgery so I could later do diffs, but sometimes the diffs never got done. :frowning:

···

On Sun, Aug 25, 2019 at 6:29 PM Tim Sawyer via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:


wd6awp

      ASL Admin




    August 25

You probably have the modified source on your ACID system. Would like you like to find the remote timeout code and add that to the current source?


Visit Topic or reply to this email to respond.


In Reply To


Chuck_Henderson

    August 25

It is working on a very old ACID system that has not been updated since long before Jim passed. But it is not working on a Raspberry Pi system that was built in the last couple of months. The ACID system has many hand coded options, some done by me and some done by Jim Dixon doing a remote connect…


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

I had a thought on this. There is a setting in rpt.conf named connpgm which will run a script after any connection is completed. It passes the node numbers (us and them) to the script.

A script could be written which would start a timer and disconnect when the timer expires. However, I’m not sure how the timer could be bumped with activity… maybe the event system could do that.

K0KN has a bunch of AllStar related info and scripts on his QRZ page. You might find some ideas there.

I am attempting to accomplish this by using the inactivity timer to run a macro after the specified amount of elapsed time with no activity. It works if I set “lnkactmacro=*76” which will disconnect all linked nodes when the timer runs out. However, I want to create a macro instead which will disconnect all nodes, then reconnect a specified node.

For example:
I want the macro to do this sequence:
*930 to disable telemetry
*76 to disconnect all nodes
*73501265 to reconnect to node 501265
*932 to change telemetry on demand

I created the following macro:
0=*930 *76 *73501265 *932#

All the commands in the macro work, except the *76 to disconnect all nodes. For some reason, I cannot get *76 to work in a macro. I even tried creating a macro just for *76 for testing (0=*76#) but that didn’t work either.

Any suggestions on how to make this work in a macro?

73,
Larry
N6LKA

That looks like it should work, less the spaces. You can’t have any spaces in a macro. The # on the end has never been necessary even though the docs say it is.

Double check your [functions] stanza (for the individual node, if not shared) has
76=ilink,6 ; Disconnect all links

Funny thing about the spaces. Minus the *76, all the other commands worked in the macro, even with the spaces. I took out all the spaces, and nothing changed. All the commands, except the *76, execute properly. I just can’t get *76 to work in a macro. I even tried putting only *76 in a macro (0=*76#) and it still didn’t work. There’s something about that command that isn’t working in a macro.

I also double checked, and my *76 functions is the same as you listed. BTW, entering *76 from my radio executes the command without any problems. I just can’t get it to execute from within the macro.

76=ilink,6 ; disconnect all links

Is there a way to execute the command directly within a macro? i.e. using the ilink,6 command within the macro itself?

73,
Larry
N6LKA

No, you can’t put ilink,6 is a macro.

Try changing 76=ilink,6 to something else, 999=ilink,6 or anything that doesn’t exist.

Hi Tim,

I tried what you suggested, but got the same results. I tried a few other things just to see what was working.

I created a macro to execute the disconnect function.
99=76
This works when I key up and enter 599, the system disconnects all linked nodes. This shows that the disconnect function will work within a macro. So I thought I would try using the new macro in the first macro to see if it would work.
0=930599
73501265
932#
0=*930 *599 *73501265 *932#
0=*599 *73501265 *932#

None of the above macros worked to disconnect all links first. However, the link command to 501265 works every time. Then I tried altering the new disconnect macro.
99=*930 *76 *932

Again, this worked just fine along with the *930 and *932 commands. This proved that the disconnect macro/function works with other commands in the same macro. However, it seems like the disconnect command just doesn’t work if the macro also has a link command in it. I’m truly baffled by this.

73,
Larry
N6LKA

Well, I finally got this feature to work correctly. Turns out, you can enter all the commands directly in line for lnkactmacro. Rather than enter everything into an actualy macro, I entered all the commands like below, and it worked. When the inactivity timer runs out, it executes each of the commands, which will essentially reset my node (disconnect everything, then reconnect 501265).

lnkactmacro=9307673501265932

Note, the series of commands above still do not work when in a macro together. At least, the *76 does not work when grouped with another link command in a macro.

73,
Larry
N6LKA