# Question about macro & Scheduler construction **URL:** \ **Category:** AllStarLink\ **Created:** [March 24, 2022, 2:07am UTC](https://community.allstarlink.org/t/question-about-macro-scheduler-construction/19286 "2022-03-24T02:07:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![kb0nhx](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kb0nhx/32/1986_2.png) [@kb0nhx](https://community.allstarlink.org/u/kb0nhx)\ **Post date:** [March 24, 2022, 2:07am UTC](https://community.allstarlink.org/t/question-about-macro-scheduler-construction/19286/1 "2022-03-24T02:07:30Z")
I am wanting to build a macro to connect 3 nodes to each other for a weekly net, then another to disconnect them when the net is over and create the scheduler setpoints to make it all happen. When creating the macro - do I need to write the macro at all nodes to connect to each other or just create the macro on one node to connect to the other two? I want traffic on each node to go out on the other two connected nodes For example: [macros] 1 = \*3xxxxxx \*3xxxxxx \*3xxxxx ; link nodes xxxxxx xxxxxx xxxxxx together for net [Schedule] 1 = 00 19 \* \* 4 ; Execute Macro 1 at 19:00 on Thursdays Would this be the correct format to link the nodes and then schedule them? Obviously not having to program this on all 3 nodes would be make it cleaner if it can be done this way. I’ve also ready about creating a hub Pi computer and connecting nodes to it instead. Is there an advantage to using a hub vs simply linking the 3 nodes together directly for our net? Thanks! James - KB0NHX ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [March 24, 2022, 2:40am UTC](https://community.allstarlink.org/t/question-about-macro-scheduler-construction/19286/2 "2022-03-24T02:40:08Z")
AllStar nodes will bridge the audio from all connected nodes. So a macro on your node that connects to the other two nodes will tie all three nodes together. You don’t need a hub. Your macro would look like: ```auto [macros] 1 = *3xxxxx*3yyyyy ; link to nodes xxxxx and yyyyy ``` ---
**Author:** ![kb0nhx](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kb0nhx/32/1986_2.png) [@kb0nhx](https://community.allstarlink.org/u/kb0nhx)\ **Post date:** [March 24, 2022, 11:56am UTC](https://community.allstarlink.org/t/question-about-macro-scheduler-construction/19286/3 "2022-03-24T11:56:04Z")
Great, thanks for explaining that! So am I thinking right about the code to use the scheduler to call the macro? I saw a post about using \*5 then the macro number to call a macro, but unsure of the syntax of the command to do so and the scheduler portion of wiki doesn’t indicate how to attach a macro to a scheduler command. James ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [March 29, 2022, 6:01pm UTC](https://community.allstarlink.org/t/question-about-macro-scheduler-construction/19286/4 "2022-03-29T18:01:34Z")
I’ve never used the scheduler but the rpt.conf comments explain how the scheduler works. Here is a clip of the scheduler stanza. The \* means every. So macro 2 will run at 0 minutes, 0 hours, every day of the month, every month and every day of the week. ```auto [schedule] ;dtmf_function = m h dom mon dow ; ala cron, star is implied ;2 = 00 00 * * * ; at midnight, execute macro 2. ``` I think your post > 1 = 00 19 \* \* 4 ; Execute Macro 1 at 19:00 on Thursdays is correct except the 4 should maybe be a 5.