December 2014 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] Remote Base questionw
by Sam Nabkey 27 Dec '14

27 Dec '14

Pretty sure the FOB issue is you need to connect to it first to get the light to blink. Mike.. Tell me about the way you configure yours to allow multiple connects? Sam On Dec 27, 2014 9:11 AM, <mike(a)midnighteng.com> wrote: > > Sam and Corey, > > I did just want to point out that the one node connect is only valid if > you use the > node=remote base option. > > 29261 = radio(a)127.0.0.1/29261,NONE,y ;y=remote base > > Without the "Y" many nodes can connect to the remote base node. > > What I did was put the control in a main node and use only use the audio > paths for the remote base node then I do not have to connect to it in > control mode to control it. > This way I don't have to connect to it at all to control it. > May not be suitable for everyone's config though. > > And Sam may be right about the reset line, I have never connected it > myself. > Something to try. > > But I doubt it has any bearing on a FOB issue. > > I have no issues with DH-RBI > > ...mike/kb8jnm > > > -------- Original Message -------- > > Subject: Re: [App_rpt-users] Remote Base question > > From: Sam Nabkey <sam.nabkey(a)gmail.com> > > Date: Sat, December 27, 2014 8:46 am > > To: mike(a)midnighteng.com > > Cc: Allstar app_rpt-users Group <app_rpt-users(a)ohnosec.org> > > > > > > Corey.... > > > > I just went through this... > > > > here is what I have learned... > > > > The URI light will not blink until you connect to the Remote with another > > node or iaxrpt. after that, it appears to stay blinking, however, I > believe > > it shoud go out again when you disconnect? Mine doesn't.. > > > > You need to use the *4xxx controlling the far node routine to manipulate > > the remote from a connect node. OR you can use IAXRPT to test. > > > > I sometimes have to stop and restart asterisk to correct an issue where > the > > remote stops responding to anything. I think it has something to do with > > the URI not disconnecting and the light stopping when you disconnect. > > > > Only one node at a time can connect with the Remote Base. the other > > attempts will fail. > > > > The Icom 706 needs Memories 50-99 entered and saved with the RPT TONE > set.. > > Starting at 67.0 at Memory 50 and going up each tone till you reach the > > last tone and memory 99. I used 146.520 simplex in every memory and just > > changed the tone incrementing 1 up till I hit 99 and the end of the > > available tones IF you don't do this, you will get "invalid frequency" > > everytime. > > > > The RBI remote base works but I had to disconnect pin 4 it appears in my > > case anyways, the logic level is backwards? As soon as I removed the > reset > > pin 4, it took right off. I am going to have to work on this because the > > RBI operates with fewer mishaps when its connected. > > > > The Kenwood TMD-700a works the best for me so far. > > > > Corey, I run my nodes in a private invironment so I have removed most of > > the band edge and authlevel safegards that maybe should be included, but > I > > wanted to get it to work before I added that back in. I am using a USB > > Serial interface or a USB Icom interface in the case of the 706. > > > > here are my working examples. I hope it at least gets you started. Your > > mileage may vary, CAUTION! Beverage may be HOT! (insert favorite > > disclaimer here..) > > > > ------ > > > > Example #1: For the IC-706: > > > > [582]; IC-706 Remote Base > > rxchannel=SimpleUSB/usb ; Rx audio/signalling channel > > duplex=1 > > context = radio > > accountcode=RADIO > > functions = functions > > memory = memory > > > > remote = ic706 > > ioport = /dev/ttyUSB0 > > civaddr = 88 > > authlevel=0 > > > > [functions] > > 0=remote,1 ; Retrieve Memory > > 1=remote,2 ; Set freq. > > 2=remote,3 ; Set tx PL tone > > 3=remote,4 ; Set rx PL tone > > 6=remote,6 ; Set Mode 1=FM 2=USB 3=LSB 4=AM > > 40=remote,100 ; Rx PL off > > 41=remote,101 ; Rx PL on > > 42=remote,102 ; Tx PL off > > 43=remote,103 ; Tx PL on > > 44=remote,104 ; Low Power > > 45=remote,105 ; Medium Power > > 46=remote,106 ; High Power > > 711=remote,107 ; Bump -20 > > 714=remote,108 ; Bump -100 > > 717=remote,109 ; Bump -500 > > 713=remote,110 ; Bump +20 > > 716=remote,111 ; Bump +100 > > 719=remote,112 ; Bump +500 > > 721=remote,113 ; Scan - slow > > 724=remote,114 ; Scan - quick > > 727=remote,115 ; Scan - fast > > 723=remote,116 ; Scan + slow > > 726=remote,117 ; Scan + quick > > 729=remote,118 ; Scan + fast > > 79=remote,119 ; Tune > > 51=remote,5 ; Long status query > > 52=remote,140 ; Short status query > > 67=remote,210 ; Send a * > > 69=remote,211 ; Send a # > > > > [memory] > > init = 14.250,67.0,u ; 14.250MHz upper sideband > > 00 = 146.460,100.0,sht > > 01 = 146.940,100.0,-l > > 02 = 14.250,100.0,u ; 14.250MHz upper sideband > > > > [nodes] > > 582 = radio(a)127.0.0.1/582,NONE,y > > > > [nodes](+) > > #include nodes.include > > > > > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > > > EXAMPLE #2 For the RBI... > > > > [582]; Doug Hall RBI-1 > > rxchannel=SimpleUSB/usb ; Rx audio/signalling channel > > duplex=1 > > context = radio > > functions = functions > > memory = memory > > > > remote=rbi > > iobase=0x378 > > > > authlevel=0 > > > > [functions] > > 0=remote,1 ; Retrieve Memory > > 1=remote,2 ; Set freq. > > 2=remote,3 ; Set tx PL tone > > 3=remote,4 ; Set rx PL tone > > 5=remote,140 ; short status query > > 6=remote,5 ; Long Status Query > > > > 730=remote,100 ; Rx PL off > > 731=remote,101 ; Rx PL on > > 720=remote,102 ; Tx PL off > > 721=remote,103 ; Tx PL on > > 740=remote,104 ; Low Power > > 741=remote,105 ; Medium Power > > 742=remote,106 ; High Power > > > > [memory] > > init = 146.520,94.8,sht > > 26 = 147.260,94.8,+ltr > > 27 = 145.270,94.8,-ltr > > 11 = 145.110,94.8,-ltr > > 52 = 146.520,94.8,sh > > > > [nodes] > > 582 = radio(a)127.0.0.1/582,NONE,y > > > > [nodes](+) > > #include nodes.include > > > ______________________________________________________________________________ > > > > Example #3 For the Kenwood TMD-700a > > > > [582]; Kenwood TMD-700a > > rxchannel=SimpleUSB/usb ; Rx audio/signalling channel > > duplex=1 > > context = radio > > callerid = "K8SN 582" <6164389073> > > accountcode=RADIO > > functions = functions > > memory = memory > > > > remote = tmd700 > > ioport = /dev/ttyUSB0 > > > > authlevel=0 > > > > [functions] > > 0=remote,1 ; Retrieve Memory > > 1=remote,2 ; Set freq. > > 2=remote,3 ; Set tx PL tone > > 3=remote,4 ; Set rx PL tone > > 40=remote,100 ; Rx PL off > > 41=remote,101 ; Rx PL on > > 42=remote,102 ; Tx PL off > > 43=remote,103 ; Tx PL on > > 44=remote,104 ; Low Power > > 45=remote,105 ; Medium Power > > 46=remote,106 ; High Power > > 51=remote,5 ; Long status query > > 52=remote,140 ; Short status query > > 67=remote,210 ; Send a * > > 69=remote,211 ; Send a # > > > > [memory] > > init = 146.520,94.8,sht > > 26 = 147.260,94.8,+ltr > > 27 = 145.270,94.8,-ltr > > 11 = 145.110,94.8,-ltr > > 52 = 146.520,94.8,sht > > > > [nodes] > > 582 = radio(a)127.0.0.1/582,NONE,y > > > > [nodes](+) > > #include nodes.include > > > > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > > > On Sat, Dec 27, 2014 at 6:11 AM, <mike(a)midnighteng.com> wrote: > > > > > > > > > > > Corey, > > > > > > As we have talked on this before, > > > It really does not make any sense but here is a checklist. > > > > > > Look at usbradio.conf and > > > usbxxxxx.conf > > > Other than looking for type errors, make sure the fob is addressed > > > properly. > > > > > > You might also add a > > > memory=memoryxxxxx section and provide a default freq load string for > > > the node (rpt.conf). > > > > > > init=146.520,100.0,l > > > > > > It's a start anyway... > > > > > > ...mike/kb8jnm > > > > > > > -------- Original Message -------- > > > > Subject: [App_rpt-users] Remote Base question > > > > From: Corey Dean <n3fe(a)repeater.net> > > > > Date: Sat, December 27, 2014 12:09 am > > > > To: Allstar app_rpt-users Group <app_rpt-users(a)ohnosec.org> > > > > > > > > > > > > A few different times I have attempted to get a remote base going. > I am > > > > using a Doug Hall Box. I am sure I have it wired correctly. On the > > > > Parallel port I have pin 2 as serial data, 3 as serial clock and 4 as > > > > reset. > > > > > > > > If I define remote = rbi asterisk will start but the light on the > usb FOB > > > > stop blinking. Once I comment out the remote = line and restart > > > asterisk, > > > > the sound fob will start to blink again and the doug hall will > reset. I > > > > decided to try defining any type of remote such as y or even ic706 > and > > > the > > > > same thing happens. > > > > > > > > When I do define remote=rbi it still will not program the kenwood > radio > > > > either. > > > > > > > > I did upgrade to the latest acid svn to test as well because prior to > > > > upgrading if any remote at all was defined, asterisk wouldn't even > start. > > > > It would bomb right out. At least now it start. I know this has to > be > > > > something simple. Any one have any ideas as to where to start > looking? > > > > > > > > I did define a remote-base stanza for functions and the only things I > > > added > > > > other than that was. > > > > > > > > remote = rbi > > > > iobase = 0x378 > > > > authlevel = 0 > > > > > > > > I am also using usbradio. > > > > > > > > Corey N3FE<hr>_______________________________________________ > > > > App_rpt-users mailing list > > > > App_rpt-users(a)ohnosec.org > > > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > > > > To unsubscribe from this list please visit > > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll > down > > > to the bottom of the page. Enter your email address and press the > > > "Unsubscribe or edit options button" > > > > You do not need a password to unsubscribe, you can do it via email > > > confirmation. If you have trouble unsubscribing, please send a message > to > > > the list detailing the problem. > > > _______________________________________________ > > > App_rpt-users mailing list > > > App_rpt-users(a)ohnosec.org > > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > > To unsubscribe from this list please visit > > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll > down > > > to the bottom of the page. Enter your email address and press the > > > "Unsubscribe or edit options button" > > > You do not need a password to unsubscribe, you can do it via email > > > confirmation. If you have trouble unsubscribing, please send a message > to > > > the list detailing the problem. > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down > to the bottom of the page. Enter your email address and press the > "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email > confirmation. If you have trouble unsubscribing, please send a message to > the list detailing the problem. >

2 1

Re: [App_rpt-users] Remote Base question
by mike＠midnighteng.com 27 Dec '14

27 Dec '14

Corey, As we have talked on this before, It really does not make any sense but here is a checklist. Look at usbradio.conf and usbxxxxx.conf Other than looking for type errors, make sure the fob is addressed properly. You might also add a memory=memoryxxxxx section and provide a default freq load string for the node (rpt.conf). init=146.520,100.0,l It's a start anyway... ...mike/kb8jnm > -------- Original Message -------- > Subject: [App_rpt-users] Remote Base question > From: Corey Dean <n3fe(a)repeater.net> > Date: Sat, December 27, 2014 12:09 am > To: Allstar app_rpt-users Group <app_rpt-users(a)ohnosec.org> > > > A few different times I have attempted to get a remote base going. I am > using a Doug Hall Box. I am sure I have it wired correctly. On the > Parallel port I have pin 2 as serial data, 3 as serial clock and 4 as > reset. > > If I define remote = rbi asterisk will start but the light on the usb FOB > stop blinking. Once I comment out the remote = line and restart asterisk, > the sound fob will start to blink again and the doug hall will reset. I > decided to try defining any type of remote such as y or even ic706 and the > same thing happens. > > When I do define remote=rbi it still will not program the kenwood radio > either. > > I did upgrade to the latest acid svn to test as well because prior to > upgrading if any remote at all was defined, asterisk wouldn't even start. > It would bomb right out. At least now it start. I know this has to be > something simple. Any one have any ideas as to where to start looking? > > I did define a remote-base stanza for functions and the only things I added > other than that was. > > remote = rbi > iobase = 0x378 > authlevel = 0 > > I am also using usbradio. > > Corey N3FE<hr>_______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

2 1

Remote Base question
by Corey Dean 27 Dec '14

27 Dec '14

A few different times I have attempted to get a remote base going. I am using a Doug Hall Box. I am sure I have it wired correctly. On the Parallel port I have pin 2 as serial data, 3 as serial clock and 4 as reset. If I define remote = rbi asterisk will start but the light on the usb FOB stop blinking. Once I comment out the remote = line and restart asterisk, the sound fob will start to blink again and the doug hall will reset. I decided to try defining any type of remote such as y or even ic706 and the same thing happens. When I do define remote=rbi it still will not program the kenwood radio either. I did upgrade to the latest acid svn to test as well because prior to upgrading if any remote at all was defined, asterisk wouldn't even start. It would bomb right out. At least now it start. I know this has to be something simple. Any one have any ideas as to where to start looking? I did define a remote-base stanza for functions and the only things I added other than that was. remote = rbi iobase = 0x378 authlevel = 0 I am also using usbradio. Corey N3FE

1 0

Re: [App_rpt-users] Need a clarification -- please
by mike＠midnighteng.com 27 Dec '14

27 Dec '14

Larry, It was meant to be clear enough for those that stumble on it looking at the mail archives. Was not trying to be-little you in any way... sorry if I gave that impression. I can only add a fact of my own experience to this... When I do a lot of switching between tx and rx on a node, It sometimes gets a bit buggy, I have always thought it was just something in my nodes or config but, If you do the same, you might be on the watch for long hang time building up on the connected node when in tx if you are switching back and forth (tx/rx - *2/*3/*2) a lot. I do not get this when I fully disconnect from mon *1/*71 and then con for tx *3. Perhaps someone else may have noticed this ? I have not had the time to track it down as a system reboot (not asterisk restart) is a quick fix when not at the console. ..mike/kb8jnm > -------- Original Message -------- > Subject: Re: [App_rpt-users] Need a clarification -- please > From: larry <larry(a)n7fm.com> > Date: Fri, December 26, 2014 11:38 am > To: app_rpt-users(a)ohnosec.org > > > Thanks Stan and Mike, > > Being able to toggle between modes is what I needed to know. > > Mike, I did understand about node numbers needing to be part of the *3 > or *2 command but thanks for including that information in your explanation. > Since I didn't include the full command structure inside my question > your answer may clarify that point for someone that I may have confused > by not doing so. > > Larry - N7FM > > > > > On 12/26/2014 01:57 AM, mike(a)midnighteng.com wrote: > > > > Larry, > > > > Yes for the most part... > > > > *2 29283 -con mon > > *3 29283 -con tx-rx > > > > *3 alone will do nothing > > > > *1 29283 -disconnect only 29283 > > *1 -alone will do nothing > > *71 -will disconnect every node connected to you mon or tx > > > > Command is the same live or macro. > > > > You do not need to disconnect (*71 or *1xxxxx) from monitor to switch > > the same node to tx. > > > > Just issue the *3xxxxx > > > > > > ...mike/kb8jnm > > > > > >> -------- Original Message -------- > >> Subject: [App_rpt-users] Need a clarification -- please > >> From: larry <larry(a)n7fm.com> > >> Date: Fri, December 26, 2014 2:52 am > >> To: app_rpt-users(a)ohnosec.org > >> > >> > >> Going to create some macros but need to understand this sequence before > >> hand. > >> > >> I want to create a macro that connects a node to another node/hub in the > >> (*2 monitor only) mode. > >> > >> Later if I wish to change that same connection to a (*3 transceive) mode. > >> Would a macro need to first issue a *1 disconnect and then reconnect > >> with a *3 function or can you just issue the *3 command and toggle > >> directly from monitor to transceive? > >> > >> I assume whatever sequence works in one direction would hold true if > >> going in reverse from tranceive to monitor only. > >> > >> Thanks > >> Larry - N7FM > >> > >> > >> > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users(a)ohnosec.org > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >> > >> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > >> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users(a)ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

4 5

Re: [App_rpt-users] Need a clarification -- please
by mike＠midnighteng.com 27 Dec '14

27 Dec '14

Ken, If I understand what you are saying and state it in a different way... You can place "0" for the node number and it will act as a wild token for the last node given a connect/disconnect command. Would I be correct ? Nice to learn something new ! Would make it easier when switching modes on a node you can't remember the number. Great stuff. ...mike/kb8jnm > -------- Original Message -------- > Subject: Re: [App_rpt-users] Need a clarification -- please > From: Kenneth Grimard <n1dot1(a)gmail.com> > Date: Fri, December 26, 2014 5:05 pm > To: app_rpt-users(a)ohnosec.org > > > hi larry > > just wanted to let you know that there is also a shortcut to the *1 *2 > *3 commands. if you use a 0 instead on the node number. > asterisk will act upon the last node the command was sent to also. > > example. > > *328162 to go to tx. after you send that command to that node. You can > use the short cut of *20 or *10 to go to monitor or > disconnect. the 0 can be used in place of the node number to send a > command to the last node that was accessed. > asterisk or app_rpt which is part of the allstar asterisk remembers the > last node you sent the command to. > > the 0 is used as a shortcut. it is not documented very well and not a > lot of sysop's know about this. > > ken n1dot > > > > On 12/26/2014 4:43 PM, larry wrote: > > Mike, > > > > I did not take anything wrong ... My intention was compliment you on > > answering with a full explanation when I failed to state my question > > properly. > > I had overlooked that others might search this list for the > > information I was asking about. After noting your reply it dawned on > > me my poorly worded request might lead someone to believe that a plain > > *1, *2, *3 would suffice as a full command rather than a full *328162 > > required for a tranceive mode connection to Node 28162. > > Your answer clarified my oversight. WELL DONE! > > > > I also appreciate the heads up about the delay possibility you mention. > > Things like that was part of the reason for my asking. I will keep > > watch. > > > > My main concern is the time delay switching to the tranceive mode on a > > monitored link. Returning to the monitor only mode, transition time > > shouldn't be an issue. > > Perhaps the monitor only macro should first disconnect then do a fresh > > reconnect process. Doing it that way should prevent duplicate > > processes from accumulating over time yet allow a single speedy > > tranceive transition to occur. > > > > If I learn anything usefull I'll let you know. > > > > Regards > > Larry - N7FM > > > > > > > > > > > > > > On 12/26/2014 10:29 AM, mike(a)midnighteng.com wrote: > >> Larry, > >> > >> It was meant to be clear enough for those that stumble on it looking at > >> the mail archives. > >> Was not trying to be-little you in any way... sorry if I gave that > >> impression. > >> > >> I can only add a fact of my own experience to this... > >> > >> When I do a lot of switching between tx and rx on a node, > >> It sometimes gets a bit buggy, > >> > >> I have always thought it was just something in my nodes or config but, > >> > >> If you do the same, you might be on the watch for long hang time > >> building up on the connected node when in tx if you are switching back > >> and forth (tx/rx - *2/*3/*2) a lot. > >> > >> I do not get this when I fully disconnect from mon *1/*71 and then con > >> for tx *3. > >> > >> Perhaps someone else may have noticed this ? > >> I have not had the time to track it down as a system reboot (not > >> asterisk restart) is a quick fix when not at the console. > >> > >> ..mike/kb8jnm > >> > >> > >>> -------- Original Message -------- > >>> Subject: Re: [App_rpt-users] Need a clarification -- please > >>> From: larry <larry(a)n7fm.com> > >>> Date: Fri, December 26, 2014 11:38 am > >>> To: app_rpt-users(a)ohnosec.org > >>> > >>> > >>> Thanks Stan and Mike, > >>> > >>> Being able to toggle between modes is what I needed to know. > >>> > >>> Mike, I did understand about node numbers needing to be part of the *3 > >>> or *2 command but thanks for including that information in your > >>> explanation. > >>> Since I didn't include the full command structure inside my question > >>> your answer may clarify that point for someone that I may have confused > >>> by not doing so. > >>> > >>> Larry - N7FM > >>> > >>> > >>> > >>> > >>> On 12/26/2014 01:57 AM, mike(a)midnighteng.com wrote: > >>>> Larry, > >>>> > >>>> Yes for the most part... > >>>> > >>>> *2 29283 -con mon > >>>> *3 29283 -con tx-rx > >>>> > >>>> *3 alone will do nothing > >>>> > >>>> *1 29283 -disconnect only 29283 > >>>> *1 -alone will do nothing > >>>> *71 -will disconnect every node connected to you mon or tx > >>>> > >>>> Command is the same live or macro. > >>>> > >>>> You do not need to disconnect (*71 or *1xxxxx) from monitor to switch > >>>> the same node to tx. > >>>> > >>>> Just issue the *3xxxxx > >>>> > >>>> > >>>> ...mike/kb8jnm > >>>> > >>>> > >>>>> -------- Original Message -------- > >>>>> Subject: [App_rpt-users] Need a clarification -- please > >>>>> From: larry <larry(a)n7fm.com> > >>>>> Date: Fri, December 26, 2014 2:52 am > >>>>> To: app_rpt-users(a)ohnosec.org > >>>>> > >>>>> > >>>>> Going to create some macros but need to understand this sequence > >>>>> before > >>>>> hand. > >>>>> > >>>>> I want to create a macro that connects a node to another node/hub > >>>>> in the > >>>>> (*2 monitor only) mode. > >>>>> > >>>>> Later if I wish to change that same connection to a (*3 > >>>>> transceive) mode. > >>>>> Would a macro need to first issue a *1 disconnect and then reconnect > >>>>> with a *3 function or can you just issue the *3 command and toggle > >>>>> directly from monitor to transceive? > >>>>> > >>>>> I assume whatever sequence works in one direction would hold true if > >>>>> going in reverse from tranceive to monitor only. > >>>>> > >>>>> Thanks > >>>>> Larry - N7FM > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> App_rpt-users mailing list > >>>>> App_rpt-users(a)ohnosec.org > >>>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >>>>> > >>>>> To unsubscribe from this list please visit > >>>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and > >>>>> scroll down to the bottom of the page. Enter your email address > >>>>> and press the "Unsubscribe or edit options button" > >>>>> You do not need a password to unsubscribe, you can do it via email > >>>>> confirmation. If you have trouble unsubscribing, please send a > >>>>> message to the list detailing the problem. > >>>> _______________________________________________ > >>>> App_rpt-users mailing list > >>>> App_rpt-users(a)ohnosec.org > >>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >>>> > >>>> To unsubscribe from this list please visit > >>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and > >>>> scroll down to the bottom of the page. Enter your email address and > >>>> press the "Unsubscribe or edit options button" > >>>> You do not need a password to unsubscribe, you can do it via email > >>>> confirmation. If you have trouble unsubscribing, please send a > >>>> message to the list detailing the problem. > >>>> > >>> _______________________________________________ > >>> App_rpt-users mailing list > >>> App_rpt-users(a)ohnosec.org > >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >>> > >>> To unsubscribe from this list please visit > >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll > >>> down to the bottom of the page. Enter your email address and press > >>> the "Unsubscribe or edit options button" > >>> You do not need a password to unsubscribe, you can do it via email > >>> confirmation. If you have trouble unsubscribing, please send a > >>> message to the list detailing the problem. > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users(a)ohnosec.org > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >> > >> To unsubscribe from this list please visit > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll > >> down to the bottom of the page. Enter your email address and press > >> the "Unsubscribe or edit options button" > >> You do not need a password to unsubscribe, you can do it via email > >> confirmation. If you have trouble unsubscribing, please send a > >> message to the list detailing the problem. > >> > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users(a)ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > To unsubscribe from this list please visit > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll > > down to the bottom of the page. Enter your email address and press the > > "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email > > confirmation. If you have trouble unsubscribing, please send a message > > to the list detailing the problem. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

2 1

Re: [App_rpt-users] Need a clarification -- please
by mike＠midnighteng.com 26 Dec '14

26 Dec '14

Larry, Yes for the most part... *2 29283 -con mon *3 29283 -con tx-rx *3 alone will do nothing *1 29283 -disconnect only 29283 *1 -alone will do nothing *71 -will disconnect every node connected to you mon or tx Command is the same live or macro. You do not need to disconnect (*71 or *1xxxxx) from monitor to switch the same node to tx. Just issue the *3xxxxx ...mike/kb8jnm > -------- Original Message -------- > Subject: [App_rpt-users] Need a clarification -- please > From: larry <larry(a)n7fm.com> > Date: Fri, December 26, 2014 2:52 am > To: app_rpt-users(a)ohnosec.org > > > Going to create some macros but need to understand this sequence before > hand. > > I want to create a macro that connects a node to another node/hub in the > (*2 monitor only) mode. > > Later if I wish to change that same connection to a (*3 transceive) mode. > Would a macro need to first issue a *1 disconnect and then reconnect > with a *3 function or can you just issue the *3 command and toggle > directly from monitor to transceive? > > I assume whatever sequence works in one direction would hold true if > going in reverse from tranceive to monitor only. > > Thanks > Larry - N7FM > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

2 1

Need a clarification -- please
by larry 26 Dec '14

26 Dec '14

Going to create some macros but need to understand this sequence before hand. I want to create a macro that connects a node to another node/hub in the (*2 monitor only) mode. Later if I wish to change that same connection to a (*3 transceive) mode. Would a macro need to first issue a *1 disconnect and then reconnect with a *3 function or can you just issue the *3 command and toggle directly from monitor to transceive? I assume whatever sequence works in one direction would hold true if going in reverse from tranceive to monitor only. Thanks Larry - N7FM

2 1

Re: [App_rpt-users] Subject: Linking private network nodes to hub
by Doug Crompton 25 Dec '14

25 Dec '14

Mike, That is correct. If the port is not 4569 you must add it as you have show and also forward that port in the router if the connection is out of your lan. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Wed, 24 Dec 2014 16:32:18 -0500 Subject: Re: [App_rpt-users] Subject: Linking private network nodes to hub From: mike.lussier(a)gmail.com To: doug(a)crompton.com Thank you Doug, I fully understand the Nat setup. I already had that in place. Do I understand correctly on the rpt.conf file. I need to add the UDP port of the node Like I have demonstrated here ? [nodes] ; Note, if you are using automatic update for allstar link nodes, ; no allstar link nodes should be defined here. Only place a definition ; for your local nodes, and private (off of allstar link) nodes here. 1000 = radio@10.135.58.67:4570/1000,NONE 1001 = radio@10.148.195.129:4571/1001,NONE Mike On Wed, Dec 24, 2014 at 4:12 PM, Doug Crompton <doug(a)crompton.com> wrote: Mike, OK, you do need to make sure all nodes have the proper informatio9n to connect in BOTH directions. If private that would be specific node entries in rpt.conf. Also make sure you use the port when defining if not 4569. Of course wherever you are trying to connect to has to be connectible and the port of the node you are connecting to has to have its port forwarded if it is behind a NAT. Happy Holidays! 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Wed, 24 Dec 2014 15:31:24 -0500 From: mike.lussier(a)gmail.com To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] Subject: Linking private network nodes to hub Doug, Thank you . I'm making progress here. I do see where the one node 41470 states connecting. and nothing shows on 41201. The problem could be the mesh nodes and I need open ports for the connect to complete. I bounced the 41201 hub that didn't seem to help. Any thoughts ? Mike Merry Christmas and a happy holiday season to ALL !! -- "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. -- "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan

1 0

Subject: Linking private network nodes to hub
by Mike Lussier 24 Dec '14

24 Dec '14

Doug, Thank you . I'm making progress here. I do see where the one node 41470 states connecting. and nothing shows on 41201. The problem could be the mesh nodes and I need open ports for the connect to complete. I bounced the 41201 hub that didn't seem to help. Any thoughts ? Mike Merry Christmas and a happy holiday season to ALL !! -- *"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan*

2 1

(no subject)
by Ken Reynolds 24 Dec '14

24 Dec '14

Good morning I just installed Asterix a bare boned form. Does anyone have a basic confiquration so I can get started with Allstar? Ken Reynolds 73 KA1EZH http://kenreynolds.weebly.com/

2 1