Date   

Re: Custom Decode Not Working

David Cameron - IRLP
 

Easy:

in dtmffastdial, change

/home/irlp/bin/dial --tone-time 105 --volume 30 --silent-time 105 "$1"

to

aoss /home/irlp/bin/dial --tone-time 105 --volume 30 --silent-time 105 "$1"

On 2019-12-22 3:24 p.m., Teton Amateur Radio Repeater Association (TARRA) wrote:

Okay, hopefully these attachments work. It isn't working to receive or send DTMF commands or tones.

Mick - W7CAT
Node 3464

----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 03:48:55 PM
Subject: Re: [IRLP] Custom Decode Not Working

The reason i ask is that ALL dtmf codes are processed through
custom_decode. So if nothing works, then there is something causing errors in the custom_decode script. You are going to have to post this sync_rc210 script and we can help you find where you need to modify it to work on the newer systems. Dave Cameron




-------- Original message --------From: "Teton Amateur Radio
Repeater Association (TARRA)" Date: 12/22/19 2:29 PM (GMT-08:00) To: IRLP@irlp.groups.io Subject: Re: [IRLP] Custom Decode Not Working
The sync program does it by sending DTMF tones.

I can connect to the test reflectors and other nodes. I don't
consider those as "custom". The commands that I do have in my
custom_decode aren't working. For example, sending a set of DTMF
tones to cause the time to be set, no DTMF tones are sent but
there is a couple of PTT at the end of the script.

Mick - W7CAT
Node 3464

----- Original Message -----

From: David Cameron - IRLP

To: IRLP@irlp.groups.io

Sent: Sunday, December 22, 2019 03:17:14 PM

Subject: Re: [IRLP] Custom Decode Not Working


Well you have not explained what the script exactly does
besides syncing
the time on the controller. Does it do it via serial port or
using DTMF
audio somehow?

Using aoss is not too hard - you just prefix any command that
throws an
error about /dev/dsp with aoss. If you attach the script,
that is a start.


You mention an issue with custom_decode, but you didn't
answer the
questions I was asking. If you enter a code like 9990, what
happens?
What is not working with DTMF?

Dave Cameron

On 2019-12-22 2:13 p.m., Teton Amateur Radio Repeater
Association
(TARRA) wrote:
I haven't found anything that works.
Not sure how much needs to be changed to use aoss or
aplay. Does it
matter which one of the two?
The updating of the node has broken enough things that I
may just go
back to the old computer and software that worked.
Mick - W7CAT
Node 3464
----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 02:34:48 PM
Subject: Re: [IRLP] Custom Decode Not Working
Does nothing work on the node, or just one code?
Sending the

custom_decode script would tell a lot.
That sync_rc210 script will need to be rewritten to
support aoss or use

aplay. It looks like it is trying to write direct
to /dev/dsp.

David Cameron
On 2019-12-22 1:04 p.m., Teton Amateur Radio
Repeater Association

(TARRA) wrote:
I still can't get custom decode to work. I
even did a complete

reinstall of Debian 10 and all the same
problems came up as the

previous time. And still the custom decode
doesn't work. All of the

DTMF LEDs light accordingly and also
everything show up correctly
with
readinput.
Probably related, if I run ./sync_rc210 to
sync the time for a

repeater controller here is what I get.
Looks like a permission issue, and probably is
for both things, but I

don't know where to look or what it should be.
Mick - W7CAT
Node 3464
--
Untitled Document
--
Untitled Document

--

Untitled Document













--
Untitled Document


Re: Custom Decode Not Working

Teton Amateur Radio Repeater Association (TARRA)
 

Okay, hopefully these attachments work. It isn't working to receive or send DTMF commands or tones.

Mick - W7CAT
Node 3464

----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 03:48:55 PM
Subject: Re: [IRLP] Custom Decode Not Working

> The reason i ask is that ALL dtmf codes are processed through custom_decode. So if nothing works, then there is something causing errors in the custom_decode script. You are going to have to post this sync_rc210 script and we can help you find where you need to modify it to work on the newer systems. Dave Cameron 
>
>
>
>
> -------- Original message --------From: "Teton Amateur Radio Repeater Association (TARRA)" Date: 12/22/19 2:29 PM (GMT-08:00) To: IRLP@irlp.groups.io Subject: Re: [IRLP] Custom Decode Not Working
> The sync program does it by sending DTMF tones.
>
> I can connect to the test reflectors and other nodes. I don't
> consider those as "custom". The commands that I do have in my
> custom_decode aren't working. For example, sending a set of DTMF
> tones to cause the time to be set, no DTMF tones are sent but
> there is a couple of PTT at the end of the script.
>
> Mick - W7CAT
> Node 3464
>
> ----- Original Message -----
>
> From: David Cameron - IRLP
>
> To: IRLP@irlp.groups.io
>
> Sent: Sunday, December 22, 2019 03:17:14 PM
>
> Subject: Re: [IRLP] Custom Decode Not Working
>
>
> > Well you have not explained what the script exactly does
> besides syncing
> > the time on the controller. Does it do it via serial port or
> using DTMF
> > audio somehow?
>
> >
> > Using aoss is not too hard - you just prefix any command that
> throws an
> > error about /dev/dsp with aoss. If you attach the script,
> that is a start.
>
> >
> > You mention an issue with custom_decode, but you didn't
> answer the
> > questions I was asking. If you enter a code like 9990, what
> happens?
> > What is not working with DTMF?
>
> >
> > Dave Cameron
>
> >
> > On 2019-12-22 2:13 p.m., Teton Amateur Radio Repeater
> Association
> > (TARRA) wrote:
>
> > > I haven't found anything that works.
>
> > >
>
> > > Not sure how much needs to be changed to use aoss or
> aplay. Does it
> > > matter which one of the two?
>
> > >
>
> > > The updating of the node has broken enough things that I
> may just go
> > > back to the old computer and software that worked.
>
> > >
>
> > > Mick - W7CAT
>
> > > Node 3464
>
> > >
>
> > > ----- Original Message -----
>
> > > From: David Cameron - IRLP
>
> > > To: IRLP@irlp.groups.io
>
> > > Sent: Sunday, December 22, 2019 02:34:48 PM
>
> > > Subject: Re: [IRLP] Custom Decode Not Working
>
> > >
>
> > > > Does nothing work on the node, or just one code?
> Sending the
>
> > > > custom_decode script would tell a lot.
>
> > > >
>
> > > > That sync_rc210 script will need to be rewritten to
> support aoss or use
>
> > > > aplay. It looks like it is trying to write direct
> to /dev/dsp.
>
> > > >
>
> > > > David Cameron
>
> > > >
>
> > > >
>
> > > > On 2019-12-22 1:04 p.m., Teton Amateur Radio
> Repeater Association
>
> > > > (TARRA) wrote:
>
> > > > >
>
> > > > > I still can't get custom decode to work. I
> even did a complete
>
> > > > > reinstall of Debian 10 and all the same
> problems came up as the
>
> > > > > previous time. And still the custom decode
> doesn't work. All of the
>
> > > > > DTMF LEDs light accordingly and also
> everything show up correctly
> > > with
>
> > > > > readinput.
>
> > > > >
>
> > > > > Probably related, if I run ./sync_rc210 to
> sync the time for a
>
> > > > > repeater controller here is what I get.
>
> > > > >
>
> > > > > Looks like a permission issue, and probably is
> for both things, but I
>
> > > > > don't know where to look or what it should be.
>
> > > > >
>
> > > > > Mick - W7CAT
>
> > > > > Node 3464
>
> > > > >
>
> > > > > --
>
> > > > > Untitled Document
>
> > > > >
>
> > > > >
>
> > > >
>
> > > >
>
> > > >
>
> > > >
>
> > > --
> > > Untitled Document
>
> > >
>
> > >
> >
> >
>
> >
> >
>
> --
>
> Untitled Document
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--


Re: Custom Decode Not Working

 

Didn't I say this a couple of hours ago? :)

>< Dave Parks ><
WB8ODF@...
http://wb8odf.com



On Sunday, December 22, 2019, 5:49:08 PM EST, David Cameron - IRLP <dcameron@...> wrote:


The reason i ask is that ALL dtmf codes are processed through custom_decode. So if nothing works, then there is something causing errors in the custom_decode script. 

You are going to have to post this sync_rc210 script and we can help you find where you need to modify it to work on the newer systems. 

Dave Cameron 

-------- Original message --------
From: "Teton Amateur Radio Repeater Association (TARRA)" <tarra@...>
Date: 12/22/19 2:29 PM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Custom Decode Not Working

The sync program does it by sending DTMF tones.

I can connect to the test reflectors and other nodes. I don't consider those as "custom". The commands that I do have in my custom_decode aren't working. For example, sending a set of DTMF tones to cause the time to be set, no DTMF tones are sent but there is a couple of PTT at the end of the script.

Mick - W7CAT
Node 3464

----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 03:17:14 PM
Subject: Re: [IRLP] Custom Decode Not Working

> Well you have not explained what the script exactly does besides syncing
> the time on the controller. Does it do it via serial port or using DTMF
> audio somehow?
>
> Using aoss is not too hard - you just prefix any command that throws an
> error about /dev/dsp with aoss. If you attach the script, that is a start.
>
> You mention an issue with custom_decode, but you didn't answer the
> questions I was asking. If you enter a code like 9990, what happens?
> What is not working with DTMF?
>
> Dave Cameron
>
> On 2019-12-22 2:13 p.m., Teton Amateur Radio Repeater Association
> (TARRA) wrote:
> > I haven't found anything that works.
> >
> > Not sure how much needs to be changed to use aoss or aplay. Does it
> > matter which one of the two?
> >
> > The updating of the node has broken enough things that I may just go
> > back to the old computer and software that worked.
> >
> > Mick - W7CAT
> > Node 3464
> >
> > ----- Original Message -----
> > From: David Cameron - IRLP
> > To: IRLP@irlp.groups.io
> > Sent: Sunday, December 22, 2019 02:34:48 PM
> > Subject: Re: [IRLP] Custom Decode Not Working
> >
> > > Does nothing work on the node, or just one code? Sending the
> > > custom_decode script would tell a lot.
> > >
> > > That sync_rc210 script will need to be rewritten to support aoss or use
> > > aplay. It looks like it is trying to write direct to /dev/dsp.
> > >
> > > David Cameron
> > >
> > >
> > > On 2019-12-22 1:04 p.m., Teton Amateur Radio Repeater Association
> > > (TARRA) wrote:
> > > >
> > > > I still can't get custom decode to work. I even did a complete
> > > > reinstall of Debian 10 and all the same problems came up as the
> > > > previous time. And still the custom decode doesn't work. All of the
> > > > DTMF LEDs light accordingly and also everything show up correctly
> > with
> > > > readinput.
> > > >
> > > > Probably related, if I run ./sync_rc210 to sync the time for a
> > > > repeater controller here is what I get.
> > > >
> > > > Looks like a permission issue, and probably is for both things, but I
> > > > don't know where to look or what it should be.
> > > >
> > > > Mick - W7CAT
> > > > Node 3464
> > > >
> > > > --
> > > > Untitled Document
> > > >
> > > >
> > >
> > >
> > >
> > >
> > --
> > Untitled Document
> >
> >
>
>
>
>
--


Re: Custom Decode Not Working

David Cameron - IRLP
 

The reason i ask is that ALL dtmf codes are processed through custom_decode. So if nothing works, then there is something causing errors in the custom_decode script. 

You are going to have to post this sync_rc210 script and we can help you find where you need to modify it to work on the newer systems. 

Dave Cameron 

-------- Original message --------
From: "Teton Amateur Radio Repeater Association (TARRA)" <tarra@...>
Date: 12/22/19 2:29 PM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Custom Decode Not Working

The sync program does it by sending DTMF tones.

I can connect to the test reflectors and other nodes. I don't consider those as "custom". The commands that I do have in my custom_decode aren't working. For example, sending a set of DTMF tones to cause the time to be set, no DTMF tones are sent but there is a couple of PTT at the end of the script.

Mick - W7CAT
Node 3464

----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 03:17:14 PM
Subject: Re: [IRLP] Custom Decode Not Working

> Well you have not explained what the script exactly does besides syncing
> the time on the controller. Does it do it via serial port or using DTMF
> audio somehow?
>
> Using aoss is not too hard - you just prefix any command that throws an
> error about /dev/dsp with aoss. If you attach the script, that is a start.
>
> You mention an issue with custom_decode, but you didn't answer the
> questions I was asking. If you enter a code like 9990, what happens?
> What is not working with DTMF?
>
> Dave Cameron
>
> On 2019-12-22 2:13 p.m., Teton Amateur Radio Repeater Association
> (TARRA) wrote:
> > I haven't found anything that works.
> >
> > Not sure how much needs to be changed to use aoss or aplay. Does it
> > matter which one of the two?
> >
> > The updating of the node has broken enough things that I may just go
> > back to the old computer and software that worked.
> >
> > Mick - W7CAT
> > Node 3464
> >
> > ----- Original Message -----
> > From: David Cameron - IRLP
> > To: IRLP@irlp.groups.io
> > Sent: Sunday, December 22, 2019 02:34:48 PM
> > Subject: Re: [IRLP] Custom Decode Not Working
> >
> > > Does nothing work on the node, or just one code? Sending the
> > > custom_decode script would tell a lot.
> > >
> > > That sync_rc210 script will need to be rewritten to support aoss or use
> > > aplay. It looks like it is trying to write direct to /dev/dsp.
> > >
> > > David Cameron
> > >
> > >
> > > On 2019-12-22 1:04 p.m., Teton Amateur Radio Repeater Association
> > > (TARRA) wrote:
> > > >
> > > > I still can't get custom decode to work. I even did a complete
> > > > reinstall of Debian 10 and all the same problems came up as the
> > > > previous time. And still the custom decode doesn't work. All of the
> > > > DTMF LEDs light accordingly and also everything show up correctly
> > with
> > > > readinput.
> > > >
> > > > Probably related, if I run ./sync_rc210 to sync the time for a
> > > > repeater controller here is what I get.
> > > >
> > > > Looks like a permission issue, and probably is for both things, but I
> > > > don't know where to look or what it should be.
> > > >
> > > > Mick - W7CAT
> > > > Node 3464
> > > >
> > > > --
> > > > Untitled Document
> > > >
> > > >
> > >
> > >
> > >
> > >
> > --
> > Untitled Document
> >
> >
>
>
>
>
--


Re: Custom Decode Not Working

Teton Amateur Radio Repeater Association (TARRA)
 

The sync program does it by sending DTMF tones.

I can connect to the test reflectors and other nodes. I don't consider those as "custom". The commands that I do have in my custom_decode aren't working. For example, sending a set of DTMF tones to cause the time to be set, no DTMF tones are sent but there is a couple of PTT at the end of the script.

Mick - W7CAT
Node 3464

----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 03:17:14 PM
Subject: Re: [IRLP] Custom Decode Not Working

> Well you have not explained what the script exactly does besides syncing
> the time on the controller. Does it do it via serial port or using DTMF
> audio somehow?
>
> Using aoss is not too hard - you just prefix any command that throws an
> error about /dev/dsp with aoss. If you attach the script, that is a start.
>
> You mention an issue with custom_decode, but you didn't answer the
> questions I was asking. If you enter a code like 9990, what happens?
> What is not working with DTMF?
>
> Dave Cameron
>
> On 2019-12-22 2:13 p.m., Teton Amateur Radio Repeater Association
> (TARRA) wrote:
> > I haven't found anything that works.
> >
> > Not sure how much needs to be changed to use aoss or aplay. Does it
> > matter which one of the two?
> >
> > The updating of the node has broken enough things that I may just go
> > back to the old computer and software that worked.
> >
> > Mick - W7CAT
> > Node 3464
> >
> > ----- Original Message -----
> > From: David Cameron - IRLP
> > To: IRLP@irlp.groups.io
> > Sent: Sunday, December 22, 2019 02:34:48 PM
> > Subject: Re: [IRLP] Custom Decode Not Working
> >
> > > Does nothing work on the node, or just one code? Sending the
> > > custom_decode script would tell a lot.
> > >
> > > That sync_rc210 script will need to be rewritten to support aoss or use
> > > aplay. It looks like it is trying to write direct to /dev/dsp.
> > >
> > > David Cameron
> > >
> > >
> > > On 2019-12-22 1:04 p.m., Teton Amateur Radio Repeater Association
> > > (TARRA) wrote:
> > > >
> > > > I still can't get custom decode to work. I even did a complete
> > > > reinstall of Debian 10 and all the same problems came up as the
> > > > previous time. And still the custom decode doesn't work. All of the
> > > > DTMF LEDs light accordingly and also everything show up correctly
> > with
> > > > readinput.
> > > >
> > > > Probably related, if I run ./sync_rc210 to sync the time for a
> > > > repeater controller here is what I get.
> > > >
> > > > Looks like a permission issue, and probably is for both things, but I
> > > > don't know where to look or what it should be.
> > > >
> > > > Mick - W7CAT
> > > > Node 3464
> > > >
> > > > --
> > > > Untitled Document
> > > >
> > > >
> > >
> > >
> > >
> > >
> > --
> > Untitled Document
> >
> >
>
>
>
>
--


Re: PiRLP ERRORCODE 40

ve7mmg@...
 

A BIG thanks it works perfectly.

I have been working on it since last night and could not find the answer and as a last attempt I posted and voila it worked in less than 5 minutes.

Your the best.

Thanks again,

Mike
NODE 1492


Re: Custom Decode Not Working

David Cameron - IRLP
 

Well you have not explained what the script exactly does besides syncing the time on the controller. Does it do it via serial port or using DTMF audio somehow?

Using aoss is not too hard - you just prefix any command that throws an error about /dev/dsp with aoss. If you attach the script, that is a start.

You mention an issue with custom_decode, but you didn't answer the questions I was asking. If you enter a code like 9990, what happens? What is not working with DTMF?

Dave Cameron

On 2019-12-22 2:13 p.m., Teton Amateur Radio Repeater Association (TARRA) wrote:
I haven't found anything that works.

Not sure how much needs to be changed to use aoss or aplay. Does it matter which one of the two?

The updating of the node has broken enough things that I may just go back to the old computer and software that worked.

Mick - W7CAT
Node 3464

----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 02:34:48 PM
Subject: Re: [IRLP] Custom Decode Not Working

Does nothing work on the node, or just one code? Sending the
custom_decode script would tell a lot.

That sync_rc210 script will need to be rewritten to support aoss or use
aplay. It looks like it is trying to write direct to /dev/dsp.

David Cameron


On 2019-12-22 1:04 p.m., Teton Amateur Radio Repeater Association
(TARRA) wrote:

I still can't get custom decode to work. I even did a complete
reinstall of Debian 10 and all the same problems came up as the
previous time. And still the custom decode doesn't work. All of the
DTMF LEDs light accordingly and also everything show up correctly
with
readinput.

Probably related, if I run ./sync_rc210 to sync the time for a
repeater controller here is what I get.

Looks like a permission issue, and probably is for both things, but I
don't know where to look or what it should be.

Mick - W7CAT
Node 3464

--
Untitled Document



--
Untitled Document


Re: Custom Decode Not Working

Teton Amateur Radio Repeater Association (TARRA)
 

I haven't found anything that works.

Not sure how much needs to be changed to use aoss or aplay. Does it matter which one of the two?

The updating of the node has broken enough things that I may just go back to the old computer and software that worked.

Mick - W7CAT
Node 3464

----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 02:34:48 PM
Subject: Re: [IRLP] Custom Decode Not Working

> Does nothing work on the node, or just one code? Sending the
> custom_decode script would tell a lot.
>
> That sync_rc210 script will need to be rewritten to support aoss or use
> aplay. It looks like it is trying to write direct to /dev/dsp.
>
> David Cameron
>
>
> On 2019-12-22 1:04 p.m., Teton Amateur Radio Repeater Association
> (TARRA) wrote:
> >
> > I still can't get custom decode to work. I even did a complete
> > reinstall of Debian 10 and all the same problems came up as the
> > previous time. And still the custom decode doesn't work. All of the
> > DTMF LEDs light accordingly and also everything show up correctly with
> > readinput.
> >
> > Probably related, if I run ./sync_rc210 to sync the time for a
> > repeater controller here is what I get.
> >
> > Looks like a permission issue, and probably is for both things, but I
> > don't know where to look or what it should be.
> >
> > Mick - W7CAT
> > Node 3464
> >
> > --
> > Untitled Document
> >
> >
>
>
>
>
--


Re: PiRLP ERRORCODE 40

David Cameron - IRLP
 

This has just been covered. It is a holdover from using an OLD environment file on a new install.

When moving from an older setup to a new one, I highly suggest the "clean install" option as it puts in a new environment file and just copies the stationID and callsign.

You need to add, or make sure these two lines exist in the environment file:

As root, edit the environment file:

pico /home/irlp/custom/environment

The lines are:

export USE_APLAY="YES"
export USE_AOSS="YES"

This will fix your issue.

Dave Cameron

VE7LTD

On 2019-12-22 2:07 p.m., ve7mmg@... wrote:
My IRLP computer finally gave up after some 10 years, it was running CentOS 5, I decided to go the Pi route.

Following the instructions all was going great and now I get an ERRORCODE 40, I am NOT a fluent Linux user, I manage to a certain point.

I ran the IRLP troubleshooting script and I passed all the steps except the EchoIRLP "That's OK as that part is not important for me at this time"

I was able to adjust the TX  level and it TX the NODE ID.

I am using a Pi 3 B+ and loaded the latest Raspbian Buster Lite and also using the recommended SYBA USB sound adapter.

Any help or direction is appreciated,

Mike NODE 1492


PiRLP ERRORCODE 40

ve7mmg@...
 

My IRLP computer finally gave up after some 10 years, it was running CentOS 5, I decided to go the Pi route.

Following the instructions all was going great and now I get an ERRORCODE 40, I am NOT a fluent Linux user, I manage to a certain point.

I ran the IRLP troubleshooting script and I passed all the steps except the EchoIRLP "That's OK as that part is not important for me at this time"

I was able to adjust the TX  level and it TX the NODE ID.

I am using a Pi 3 B+ and loaded the latest Raspbian Buster Lite and also using the recommended SYBA USB sound adapter.

Any help or direction is appreciated,

Mike NODE 1492


Re: Custom Decode Not Working

David Cameron - IRLP
 

Does nothing work on the node, or just one code? Sending the custom_decode script would tell a lot.

That sync_rc210 script will need to be rewritten to support aoss or use aplay. It looks like it is trying to write direct to /dev/dsp.

David Cameron

On 2019-12-22 1:04 p.m., Teton Amateur Radio Repeater Association (TARRA) wrote:

I still can't get custom decode to work. I even did a complete reinstall of Debian 10 and all the same problems came up as the previous time. And still the custom decode doesn't work. All of the DTMF LEDs light accordingly and also everything show up correctly with readinput.

Probably related, if I run ./sync_rc210 to sync the time for a repeater controller here is what I get.

Looks like a permission issue, and probably is for both things, but I don't know where to look or what it should be.

Mick - W7CAT
Node 3464

--
Untitled Document


Re: Custom Decode Not Working

John
 

Be more specific Mick..
WHICH custom decode won't work?
Can you run it from the console - what errors are produced?

John @ 6163

On 23/12/2019 7:04:23 AM, Teton Amateur Radio Repeater Association (TARRA) (tarra@...) wrote:
I still can't get custom decode to work. I even did a complete reinstall
of Debian 10 and all the same problems came up as the previous time. And still the custom decode doesn't work. All of the DTMF LEDs light accordingly and also everything show up correctly with readinput.
Probably related, if I run ./sync_rc210 to sync the time for a repeater controller here is what I get.
Looks like a permission issue, and probably is for both things, but I don't know where to look or what it should be.
Mick - W7CAT
Node 3464
--
Untitled Document


Re: New install

David Cameron - IRLP
 

It should be 0v when the logic pin is low. 3.3v is the high state. 

Dave Cameron 

-------- Original message --------
From: Craig - K1BDX - Node 8724 <k1bdx.craig@...>
Date: 12/22/19 1:08 PM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] New install

That voltage is not changing in a significant way

If the initial voltage is high (around 3.26 volts)  then the
"asserted" voltage (low) should be down around 1 volt or less.


On 12/22/19, William Phillips <bphillips.nnh@...> wrote:
>
> That pin varies between 3.26 to 3.29 when dtmf tone sent. I checked it on
> the pi as well as the irlp board it was the same on both ends.
>>
>>
>> On Dec 22, 2019, at 6:22 AM, Craig - K1BDX - Node 8724
>> <k1bdx.craig@...> wrote:
>>
>> The first binary bit  D0 seems to be stuck in the "asserted" condition.
>>
>> I'm wondering if the wire between the pi and the irlp interface board is
>> broken
>>
>> According to Dave Cameron's diagram
>>
>> D0 is pin number 7 or the Raspberry Pi header
>>
>> monitor the voltage on that pin while you send tones and see if it
>> changes state properly
>>
>>
>>> On 12/22/19, William Phillips <bphillips.nnh@...> wrote:
>>>
>>> Well I tried a different raspberry 4 did an install all works except the
>>> dtmf tones are incorrect and the same as before
>>>
>>> Pressed : Seen
>>> 1:nothing
>>> 2:3 when released 1
>>> 3:3 when released 1
>>> 4:5 when released 1
>>> 5:5 when released 1
>>> 6:7 when released 1
>>> 7:7 when released 1
>>> 8:9 when released 1
>>> 9:9 when released 1
>>



Re: Custom Decode Not Working

 

My next move would be to write a complete NEW custom_decode and put something simple in it to test.


>< Dave Parks ><
WB8ODF@...
http://wb8odf.com



On Sunday, December 22, 2019, 4:04:42 PM EST, Teton Amateur Radio Repeater Association (TARRA) <tarra@...> wrote:


I still can't get custom decode to work. I even did a complete reinstall of Debian 10 and all the same problems came up as the previous time. And still the custom decode doesn't work. All of the DTMF LEDs light accordingly and also everything show up correctly with readinput.

Probably related, if I run ./sync_rc210 to sync the time for a repeater controller here is what I get.

Looks like a permission issue, and probably is for both things, but I don't know where to look or what it should be.

Mick - W7CAT
Node 3464

--


Re: New install

Craig - K1BDX - Node 8724
 

That voltage is not changing in a significant way

If the initial voltage is high (around 3.26 volts) then the
"asserted" voltage (low) should be down around 1 volt or less.

On 12/22/19, William Phillips <bphillips.nnh@...> wrote:

That pin varies between 3.26 to 3.29 when dtmf tone sent. I checked it on
the pi as well as the irlp board it was the same on both ends.


On Dec 22, 2019, at 6:22 AM, Craig - K1BDX - Node 8724
<k1bdx.craig@...> wrote:

The first binary bit D0 seems to be stuck in the "asserted" condition.

I'm wondering if the wire between the pi and the irlp interface board is
broken

According to Dave Cameron's diagram

D0 is pin number 7 or the Raspberry Pi header

monitor the voltage on that pin while you send tones and see if it
changes state properly


On 12/22/19, William Phillips <bphillips.nnh@...> wrote:

Well I tried a different raspberry 4 did an install all works except the
dtmf tones are incorrect and the same as before

Pressed : Seen
1:nothing
2:3 when released 1
3:3 when released 1
4:5 when released 1
5:5 when released 1
6:7 when released 1
7:7 when released 1
8:9 when released 1
9:9 when released 1


Custom Decode Not Working

Teton Amateur Radio Repeater Association (TARRA)
 

I still can't get custom decode to work. I even did a complete reinstall of Debian 10 and all the same problems came up as the previous time. And still the custom decode doesn't work. All of the DTMF LEDs light accordingly and also everything show up correctly with readinput.

Probably related, if I run ./sync_rc210 to sync the time for a repeater controller here is what I get.

Looks like a permission issue, and probably is for both things, but I don't know where to look or what it should be.

Mick - W7CAT
Node 3464

--


Re: New install

David Cameron - IRLP
 

The problem is likely in the gpio cable to db25 on the irlp board. 

Verify continuity between pin 7 on the pi and pin 15 on the db25.

Alternately, measure the same voltage at pin 15 on the db25.

Dave Cameron 

-------- Original message --------
From: Craig - K1BDX - Node 8724 <k1bdx.craig@...>
Date: 12/22/19 6:23 AM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] New install

The first binary bit  D0 seems to be stuck in the "asserted" condition.

I'm wondering if the wire between the pi and the irlp interface board is broken

According to Dave Cameron's diagram

D0 is pin number 7 or the Raspberry Pi header

monitor the voltage on that pin while you send tones and see if it
changes state properly




On 12/22/19, William Phillips <bphillips.nnh@...> wrote:
> Well I tried a different raspberry 4 did an install all works except the
> dtmf tones are incorrect and the same as before
>
> Pressed : Seen
> 1:nothing
> 2:3 when released 1
> 3:3 when released 1
> 4:5 when released 1
> 5:5 when released 1
> 6:7 when released 1
> 7:7 when released 1
> 8:9 when released 1
> 9:9 when released 1




Re: New install

William Phillips
 

That pin varies between 3.26 to 3.29 when dtmf tone sent. I checked it on the pi as well as the irlp board it was the same on both ends.

On Dec 22, 2019, at 6:22 AM, Craig - K1BDX - Node 8724 <k1bdx.craig@...> wrote:

The first binary bit D0 seems to be stuck in the "asserted" condition.

I'm wondering if the wire between the pi and the irlp interface board is broken

According to Dave Cameron's diagram

D0 is pin number 7 or the Raspberry Pi header

monitor the voltage on that pin while you send tones and see if it
changes state properly




On 12/22/19, William Phillips <bphillips.nnh@...> wrote:
Well I tried a different raspberry 4 did an install all works except the
dtmf tones are incorrect and the same as before

Pressed : Seen
1:nothing
2:3 when released 1
3:3 when released 1
4:5 when released 1
5:5 when released 1
6:7 when released 1
7:7 when released 1
8:9 when released 1
9:9 when released 1


<IRLP_GPIO_Wiring.png>


Re: New install

Teton Amateur Radio Repeater Association (TARRA)
 

I don't know that radio, just trying to make sure it wasn't one of the Chinese radios that have problems.

Mick - W7CAT
Node 3464

----- Original Message -----
From: William Phillips
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 09:06:40 AM
Subject: Re: [IRLP] New install

> Yaesu FT1XD
> > On Dec 22, 2019, at 6:16 AM, Teton Amateur Radio Repeater Association (TARRA) wrote:
> >
> > I don't think I asked this before, even though I was going to, what are you using for a radio to send the DTMF tones???
> >
> > Mick - W7CAT
> > Node 3464
> >
> > ----- Original Message -----
> > From: William Phillips
> > To: IRLP@irlp.groups.io
> > Sent: Sunday, December 22, 2019 01:02:01 AM
> > Subject: Re: [IRLP] New install
> >
> > > Well I tried a different raspberry 4 did an install all works except the dtmf tones are incorrect and the same as before
> > >
> > > Pressed : Seen
> > > 1:nothing
> > > 2:3 when released 1
> > > 3:3 when released 1
> > > 4:5 when released 1
> > > 5:5 when released 1
> > > 6:7 when released 1
> > > 7:7 when released 1
> > > 8:9 when released 1
> > > 9:9 when released 1
> > > > On Dec 21, 2019, at 9:08 PM, Teton Amateur Radio Repeater Association (TARRA) wrote:
> > > >
> > > > Yes. If you are watching readinput it should show whichever tone (digit) you send except for "D".
> > > >
> > > > Mick - W7CAT
> > > > Node 3464
> > > >
> > > > ----- Original Message -----
> > > > From: William Phillips
> > > > To: IRLP@irlp.groups.io
> > > > Sent: Saturday, December 21, 2019 10:03:55 PM
> > > > Subject: Re: [IRLP] New install
> > > >
> > > > > it looks like the reinstall fixed the audio issue. should the dtmf tones match what is pressed on the radio?
> > > > >
> > > > > > On Dec 21, 2019, at 8:41 PM, Teton Amateur Radio Repeater Association (TARRA) wrote:
> > > > > >
> > > > > > I don't see any issue with the wiring.
> > > > > >
> > > > > > Mick - W7CAT
> > > > > > Node 3464
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: William Phillips
> > > > > > To: IRLP@irlp.groups.io
> > > > > > Sent: Saturday, December 21, 2019 07:26:47 PM
> > > > > > Subject: Re: [IRLP] New install
> > > > > >
> > > > > > > The radio connections are as follows
> > > > > > >
> > > > > > > Radio Irlp board
> > > > > > > Pin 2 9
> > > > > > > Pin 3. 2
> > > > > > > Pin 7. 6
> > > > > > > Pin 8. 7
> > > > > > > Pin 11. 8
> > > > > > >
> > > > > > > I have a 10uf capacitor on pin 9 irlp to pin 2 radio. I have radio programmed for cos pin 8 active low and the board matches. I tried another radio I have same issue. I also confirmed this radio works with signalink on an EchoLink I had set up. I have a mike connected with the hangup plate attached.
> > > > > > > > On Dec 21, 2019, at 6:11 PM, Teton Amateur Radio Repeater Association (TARRA) wrote:
> > > > > > > >
> > > > > > > > I would like to know exactly what connections you are using on the radio and on the IRLP board and what is connected to what. It shouldn't be complicated.
> > > > > > > >
> > > > > > > > Keep in mind it doesn't matter what is connected to pin 8 if there isn't a shorting plug in the microphone connector.
> > > > > > > >
> > > > > > > > Mick - W7CAT
> > > > > > > > Node 3464
> > > > > > > >
> > > > > > > > ----- Original Message -----
> > > > > > > > From: Darin Lehnert
> > > > > > > > To: IRLP@irlp.groups.io
> > > > > > > > Sent: Saturday, December 21, 2019 02:11:59 PM
> > > > > > > > Subject: Re: [IRLP] New install
> > > > > > > >
> > > > > > > > > Hi William,
> > > > > > > > > Is this a 8 channel 16 channel Motorola ? If it is a 16 channel you need to
> > > > > > > > > program
> > > > > > > > > pin 8 on the Motorola to Select PL/DPL & CSQ Detect and active low
> > > > > > > > > You also need to make sure your active low on the IRLP board
> > > > > > > > > and I always use a 10k resistor on the pink side of the sound fob.
> > > > > > > > >
> > > > > > > > > Good Luck !!
> > > > > > > > >
> > > > > > > > > Darin
> > > > > > > > > kc7tig
> > > > > > > > >
> > > > > > > > > On Sat, Dec 21, 2019 at 12:44 PM William Phillips
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Would the audio be a separate issue? Could this be a software issue should
> > > > > > > > > > I try reinstalling?
> > > > > > > > > > > On Dec 21, 2019, at 11:28 AM, Nosey Nick VA3NNW
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > William Phillips wrote:
> > > > > > > > > > >> Pressed : Seen
> > > > > > > > > > >> 1:nothing
> > > > > > > > > > >> 2:3 when released 1
> > > > > > > > > > >> 3:3 when released 1
> > > > > > > > > > >> 4:5 when released 1
> > > > > > > > > > >> 5:5 when released 1
> > > > > > > > > > >> 6:7 when released 1
> > > > > > > > > > >> 7:7 when released 1
> > > > > > > > > > >> 8:9 when released 1
> > > > > > > > > > >> 9:9 when released 1
> > > > > > > > > > >
> > > > > > > > > > > Sounds a lot like DTMF 1 is stuck "high", and adding 1 to otherwise-even
> > > > > > > > > > > numbers.
> > > > > > > > > > >
> > > > > > > > > > > Check (I think) D0 / GPIO 4 / Pin 15 for possible shorts?
> > > > > > > > > > >
> > > > > > > > > > > Nick
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > "Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209.
> > > > > > > > > > > use Std::Disclaimer; sig@...
> > > > > > > > > > > I checked the Internet to see how long a possum can hold its breath.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > --
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > --
> > > >
> > >
> > >
> > >
> > >
> > --
> >
>
>
>
>
--


Re: New install

William Phillips
 

Yaesu FT1XD


On Dec 22, 2019, at 6:16 AM, Teton Amateur Radio Repeater Association (TARRA) <tarra@...> wrote:

I don't think I asked this before, even though I was going to, what are you using for a radio to send the DTMF tones???

Mick - W7CAT
Node 3464

----- Original Message -----
From: William Phillips
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 01:02:01 AM
Subject: Re: [IRLP] New install

> Well I tried a different raspberry 4 did an install all works except the dtmf tones are incorrect and the same as before
>
> Pressed : Seen
> 1:nothing
> 2:3 when released 1
> 3:3 when released 1
> 4:5 when released 1
> 5:5 when released 1
> 6:7 when released 1
> 7:7 when released 1
> 8:9 when released 1
> 9:9 when released 1
> > On Dec 21, 2019, at 9:08 PM, Teton Amateur Radio Repeater Association (TARRA) wrote:
> >
> > Yes. If you are watching readinput it should show whichever tone (digit) you send except for "D".
> >
> > Mick - W7CAT
> > Node 3464
> >
> > ----- Original Message -----
> > From: William Phillips
> > To: IRLP@irlp.groups.io
> > Sent: Saturday, December 21, 2019 10:03:55 PM
> > Subject: Re: [IRLP] New install
> >
> > > it looks like the reinstall fixed the audio issue. should the dtmf tones match what is pressed on the radio?
> > >
> > > > On Dec 21, 2019, at 8:41 PM, Teton Amateur Radio Repeater Association (TARRA) wrote:
> > > >
> > > > I don't see any issue with the wiring.
> > > >
> > > > Mick - W7CAT
> > > > Node 3464
> > > >
> > > > ----- Original Message -----
> > > > From: William Phillips
> > > > To: IRLP@irlp.groups.io
> > > > Sent: Saturday, December 21, 2019 07:26:47 PM
> > > > Subject: Re: [IRLP] New install
> > > >
> > > > > The radio connections are as follows
> > > > >
> > > > > Radio Irlp board
> > > > > Pin 2 9
> > > > > Pin 3. 2
> > > > > Pin 7. 6
> > > > > Pin 8. 7
> > > > > Pin 11. 8
> > > > >
> > > > > I have a 10uf capacitor on pin 9 irlp to pin 2 radio. I have radio programmed for cos pin 8 active low and the board matches. I tried another radio I have same issue. I also confirmed this radio works with signalink on an EchoLink I had set up. I have a mike connected with the hangup plate attached.
> > > > > > On Dec 21, 2019, at 6:11 PM, Teton Amateur Radio Repeater Association (TARRA) wrote:
> > > > > >
> > > > > > I would like to know exactly what connections you are using on the radio and on the IRLP board and what is connected to what. It shouldn't be complicated.
> > > > > >
> > > > > > Keep in mind it doesn't matter what is connected to pin 8 if there isn't a shorting plug in the microphone connector.
> > > > > >
> > > > > > Mick - W7CAT
> > > > > > Node 3464
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: Darin Lehnert
> > > > > > To: IRLP@irlp.groups.io
> > > > > > Sent: Saturday, December 21, 2019 02:11:59 PM
> > > > > > Subject: Re: [IRLP] New install
> > > > > >
> > > > > > > Hi William,
> > > > > > > Is this a 8 channel 16 channel Motorola ? If it is a 16 channel you need to
> > > > > > > program
> > > > > > > pin 8 on the Motorola to Select PL/DPL & CSQ Detect and active low
> > > > > > > You also need to make sure your active low on the IRLP board
> > > > > > > and I always use a 10k resistor on the pink side of the sound fob.
> > > > > > >
> > > > > > > Good Luck !!
> > > > > > >
> > > > > > > Darin
> > > > > > > kc7tig
> > > > > > >
> > > > > > > On Sat, Dec 21, 2019 at 12:44 PM William Phillips
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Would the audio be a separate issue? Could this be a software issue should
> > > > > > > > I try reinstalling?
> > > > > > > > > On Dec 21, 2019, at 11:28 AM, Nosey Nick VA3NNW
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > William Phillips wrote:
> > > > > > > > >> Pressed : Seen
> > > > > > > > >> 1:nothing
> > > > > > > > >> 2:3 when released 1
> > > > > > > > >> 3:3 when released 1
> > > > > > > > >> 4:5 when released 1
> > > > > > > > >> 5:5 when released 1
> > > > > > > > >> 6:7 when released 1
> > > > > > > > >> 7:7 when released 1
> > > > > > > > >> 8:9 when released 1
> > > > > > > > >> 9:9 when released 1
> > > > > > > > >
> > > > > > > > > Sounds a lot like DTMF 1 is stuck "high", and adding 1 to otherwise-even
> > > > > > > > > numbers.
> > > > > > > > >
> > > > > > > > > Check (I think) D0 / GPIO 4 / Pin 15 for possible shorts?
> > > > > > > > >
> > > > > > > > > Nick
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > "Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209.
> > > > > > > > > use Std::Disclaimer; sig@...
> > > > > > > > > I checked the Internet to see how long a possum can hold its breath.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > --
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > --
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > --
> >
>
>
>
>
--