I really wish you did Echolink. I appreciate your enthusiasum about Allstar. I just wish someone New would go all in to explain Echolink, for new users, like you do. I still think Echolink is more user friendly, than Allstar. But both have a lot of followers.
there are videos on Echolink on how to set them up and connect. I would like to give a piece of advise on Echolink to all users. Please when connecting to any repeater callsign-R give it time and listen then Please ID your call there is no one talking. I have seen to many connect then 5 to 15 secs later disconnect without IDing. we should always ID when keying up a repeater even if we are testing.
Please make an updated video for ASL3. The structure of the file is quite different, and the data markers conveyed in this video do not match the ASL3 implementation. Thank you.
Nice video! I'm new to Allstar, and though the macro, as just implemented here, works from on-air dtmf and executes on startup as well, it does not consider the startup_macro_delay value that I added to rpt.conf. I guess my next stop on this train is to look at or around the startup script to see if there's a startup_macro_delay loop present. At this point, I'm thinking this is the problem. It's been about a decade or more since I was on the Linux wagon train, so I'm asking, where's my Flint McCullough?
Hi thanks for a very helpful video, i wonder wether I could as you how I can get my node to change the voice announce of my call sign to morse announcement instead I believe I need to edit the rpt.conf file but not sure how and what lines to edit 🤔
one thing Fred you do not need to specify a macro. you can do this an accomplish the same thing startup_macro=*3nodenumber,*3nodenumber just separate the nodes you are connecting to with a comma. there is no need to do a permanent connect as a standard connect will do just fine. you can still use the delay to delay the connection to the nodes without problems. I have been doing this way for 4 years and never had an issue. Also get with me for a script that checks to see if your connected to a node and if not it will auto reconnect you and that you can run it in your crontab at any time interval (like 15 minutes) to test and it will create a log as well.
Is there a way the node shutting down gracefully at a specific set time ? ie I want my gateway node to shut down at midnight but I’m usually asleep at that time 😊
I will strive to get you an answer. But let me ask you this. Do you want it to power down so that it can be manually powered back on or are you wanting it to power down and power itself back on which I’m not sure as possible without a smart plug. But an alternative could be is for the*server to shut down leaving the raspberry pie running and at a crown job maybe to turn the*server back on at a certain time. This would effectively make the node unusable during its downtime. Although you may be wanting it to power off altogether, what do you think?
@@HamRadioCrusader hi thanks for your quick response..yes I can manually power it back on again in the mornings …Iv got it to automatically to connect to Hubnet on boot up from the help of one of your videos ..so it’s the midnight shutdown only ..👍
What I was thinking is that I wanted the node to automatically shut off . As if I was pushing the manual shut down button connected to the raspberry pi ( as not to corrupt the sd card) I was wondering wether there is a setting in hamviop to shut the node off at a given time ? I can then set the the the Wi-Fi socked to switch off which will shut down the power supply, node and tx completely and safely….
Here is a shutdown script that I have tested on my node. www.hamradiolife.org/cpsspftware/shutdown_pi.sh Once you download the file put it into the /etc/asterisk/local/ directory and the run this command. chmod 755 shutdown_pi.sh and hit enter, this makes the file executable. Then you need to make a crontab entry to run the file from that directory at the desired date and time. Hope this helps 73 DE KD5FMU@@barbsblogs1563
![เปิดบ้าน โคตรสวย ป๋องกพล รู้จักตั้งนาน เพิ่งรู้ว่ารวย!!! l [Nickynachat]](http://i.ytimg.com/vi/tmgCF_2HfYI/mqdefault.jpg)
Thanks Freddie. I set this up as I was playing the video. Very easy and straight forward.
Good explanation. There's so much buried in there. I had to chase around to find this when I set up my portable node. Thanks Freddie!
Great info Freddie! 73!
Freddie Mac...When are you doing a video with Fannie Mae?
I tried to get my wife to be Fannie Mae and she wasn't having it 🤣
I really wish you did Echolink. I appreciate your enthusiasum about Allstar. I just wish someone New would go all in to explain Echolink, for new users, like you do.
I still think Echolink is more user friendly, than Allstar. But both have a lot of followers.
I will think about, EchoLink wasn't kind to me back in the day. But I will seriously consider it.
there are videos on Echolink on how to set them up and connect. I would like to give a piece of advise on Echolink to all users. Please when connecting to any repeater callsign-R give it time and listen then Please ID your call there is no one talking. I have seen to many connect then 5 to 15 secs later disconnect without IDing. we should always ID when keying up a repeater even if we are testing.
Great video!! Love your content. KEEP IT UP!!
As usual very nice video Freddie Mac. I would like to suggest that you consider producing a video on how to autoconnect to nets and disconnect
Here you go th-cam.com/video/gCsjouIKnNU/w-d-xo.htmlsi=hZZ-ipY-9tAH_cMH
Please make an updated video for ASL3. The structure of the file is quite different, and the data markers conveyed in this video do not match the ASL3 implementation. Thank you.
Nice video! I'm new to Allstar, and though the macro, as just implemented here, works from on-air dtmf and executes on startup as well, it does not consider the startup_macro_delay value that I added to rpt.conf. I guess my next stop on this train is to look at or around the startup script to see if there's a startup_macro_delay loop present. At this point, I'm thinking this is the problem. It's been about a decade or more since I was on the Linux wagon train, so I'm asking, where's my Flint McCullough?
Hi thanks for a very helpful video, i wonder wether I could as you how I can get my node to change the voice announce of my call sign to morse announcement instead I believe I need to edit the rpt.conf file but not sure how and what lines to edit 🤔
Great video. Cant wait to try it
one thing Fred you do not need to specify a macro. you can do this an accomplish the same thing
startup_macro=*3nodenumber,*3nodenumber
just separate the nodes you are connecting to with a comma. there is no need to do a permanent connect as a standard connect will do just fine. you can still use the delay to delay the connection to the nodes without problems. I have been doing this way for 4 years and never had an issue. Also get with me for a script that checks to see if your connected to a node and if not it will auto reconnect you and that you can run it in your crontab at any time interval (like 15 minutes) to test and it will create a log as well.
Stop being a sad ham
Good evening, Brad! I'd like to see that reconnect script of yours. Thanks!
Do you know how update supermon too 7 +
Is there a way the node shutting down gracefully at a specific set time ?
ie I want my gateway node to shut down at midnight but I’m usually asleep at that time 😊
I will strive to get you an answer. But let me ask you this. Do you want it to power down so that it can be manually powered back on or are you wanting it to power down and power itself back on which I’m not sure as possible without a smart plug. But an alternative could be is for the*server to shut down leaving the raspberry pie running and at a crown job maybe to turn the*server back on at a certain time. This would effectively make the node unusable during its downtime. Although you may be wanting it to power off altogether, what do you think?
@@HamRadioCrusader hi thanks for your quick response..yes I can manually power it back on again in the mornings …Iv got it to automatically to connect to Hubnet on boot up from the help of one of your videos ..so it’s the midnight shutdown only ..👍
@@barbsblogs1563 let me do some research
What I was thinking is that I wanted the node to automatically shut off . As if I was pushing the manual shut down button connected to the raspberry pi ( as not to corrupt the sd card) I was wondering wether there is a setting in hamviop to shut the node off at a given time ? I can then set the the the Wi-Fi socked to switch off which will shut down the power supply, node and tx completely and safely….
Here is a shutdown script that I have tested on my node. www.hamradiolife.org/cpsspftware/shutdown_pi.sh Once you download the file put it into the /etc/asterisk/local/ directory and the run this command. chmod 755 shutdown_pi.sh and hit enter, this makes the file executable. Then you need to make a crontab entry to run the file from that directory at the desired date and time. Hope this helps 73 DE KD5FMU@@barbsblogs1563
PLEASE no music ESPECISLY MUSACK