[App_rpt-users] Low Band Remote Base

[Jim Duuuude]

are you using the current sources from SVN?

From: monty at ke7jvx.com
Date: Fri, 16 Dec 2011 11:55:17 -0700
To: app_rpt-users at ohnosec.org
Subject: Re: [App_rpt-users] Low Band Remote Base

Been working off list with David on this issue.  Tried the manual split in the memory channel:

06 = 53.720,136.5,1000,h-t

Still will only do a 0.5 mhz split, even tried 2000 just to make sure.  In Checking the source, it looks like that only applies to Kenwood radios in 2m/70cm.  My question is could this capability be added to accommodate the low band Syntors with the Xcat?


Monty



On Sat, Dec 10, 2011 at 9:42 PM, David KE6UPI <dshaw at ke6upi.com> wrote:


it does look like 2/70 and kenwood only.


David

On Fri, Dec 9, 2011 at 8:42 PM, Monty <monty at ke7jvx.com> wrote:



I searched app_rpt.c and found this:

static int setkenwood(struct rpt *myrpt)
{
char rxstr[RAD_SERIAL_BUFLEN],txstr[RAD_SERIAL_BUFLEN],freq[20];



char mhz[MAXREMSTR],offset[20],band,decimals[MAXREMSTR],band1,band2;


int myrxpl,mysplit,step;
    
int offsets[] = {0,2,1};
int powers[] = {2,1,0};

    if (sendrxkenwood(myrpt,"VMC 0,0\r",rxstr,"VMC") < 0) return -1;
    split_freq(mhz, decimals, myrpt->freq);





    mysplit = myrpt->splitkhz;
    if (atoi(mhz) > 400)
    {
        band = '6';
        band1 = '1';
        band2 = '5';
        if (!mysplit) mysplit = myrpt->p.default_split_70cm;





    }
    else
    {
        band = '2';
        band1 = '0';
        band2 = '2';
        if (!mysplit) mysplit = myrpt->p.default_split_2m;
    }
Looks to be only for 2m and 70cm.






Monty



On Fri, Dec 9, 2011 at 2:50 PM, David KE6UPI <dshaw at ke6upi.com> wrote:





You can check the code (app_rpt.c) and see if there. I bet it is. I don't think Jim would have limit for just 2m/70cm bands.

David



On Fri, Dec 9, 2011 at 12:03 PM, Monty <monty at ke7jvx.com> wrote:

I know in the config program there is a split that is set, so I might have to play with that.  From the webpage you referenced it looks to be only for 2m and 440.






Monty



On Fri, Dec 9, 2011 at 8:44 AM, David KE6UPI <dshaw at ke6upi.com> wrote:








Hello Monty, Sorry I don't know to much about your hardware. I do know that the offset works on my TM-G707 kenwood. Could it be a Syntor problem?

David



On Wed, Dec 7, 2011 at 8:02 PM, Monty <monty at ke7jvx.com> wrote:

Hey David,
Thanks for your response.  I tried this:

06 = 53.720,136.5,1000,h-t

When I call it up, it still splits to 0.5 mhz (53.220).  Made sure I rebooted the node as well.  So for grins I tried this:












06 = 53.720,136.5,2000,h-t

Still it transmits at 53.220 instead of 52.720.

Monty



On Wed, Dec 7, 2011 at 9:26 AM, David KE6UPI <dshaw at ke6upi.com> wrote:











Check out this webpage.http://ohnosec.org/drupal/node/175












You may also specify the offset in a memory channel

by adding an additional parameter before the options,

for example:
01 = 147.435,103.5,1035,h-t  ; This would be for W6NUT in Los Angeles with input of 146.40












David

On Sun, Dec 4, 2011 at 2:37 PM, Monty <monty at ke7jvx.com> wrote:



Hello Everyone,
I have successfully integrated a Low Band Syntor X with an Xcat to app_rpt using CI-V.  I have a problem though.  There are currently 6 6m repeaters here in Arizona, 3 have 0.5 mhz split and the other 3 have 1 mhz splits.  I have only been successful in programing the 0.5 split frequencies in App_Rpt memories.  Is there a trick to make it split to 1 mhz or is that not possible?














Monty


_______________________________________________

App_rpt-users mailing list

App_rpt-users at ohnosec.org

http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users



















_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20111216/6ceb366f/attachment.html>