[arm-allstar] cw ID on second node problems

[Doug Crompton]

Stan,

 As far as I know there is no Allstar reason for this not working assuming
you have the ID setup correctly for your second node in rpt.conf. It should
look like this -

idrecording=|iDE WA3XYZ/L

With of course your call. That is a vertical bar and lowercase i followed
by your call.

BUT the other thing you need to check and this might be the answer is the
morse=morse  statements in your node definitions. The parameter it is equal
to has to exist as a stanza further down in the file. Look at your first
node. It probably has a statement of  morse-morsexxxxx  - where xxxxx is
your first node number. In the second node you have to make it the same, as
this refers to the morse stanza further down in the file which would be
labelled  [morsexxxxx]  where xxxxx is your first node number. My guess is
you changed the morse=morsexxxxx in your second node definition to its node
number and there would be no stanza definition for that unless you created
it.

The reason for the value=value statements in the node definitions is so you
can have different parameters for each node by calling a specific stanza.

Here is an example...

[40000]

morse=morse4000


[40001]

morse=morse40001


[morse40000]
speed=20
frequency=800
amplitude=4096
idfrequency=750
idamplitude=1024

In this example the first node would use the values for speed and amplitude
etc. The second node would have no definitions. If you changed the second
node to  morse=morse40000  then both would use the same definition. There
would generally not be a reason to have two morse definitions unless you
wanted different amplitudes or speed on different nodes.

Note this also applies to other stanzas like functions. If you only have
one [functionsxxxxx] stanza and the second node does not refer to it you
will no functions definitions for the second node!

The setup routine leaves all morse=morsexxxxx for both the first and second
node at the first node number. So if you were to use the method changing
all 1999 to the second node number the second node would retain all of the
first nodes definitions which is generally what you would want at least to
start out. So I would recommend changing all xxxxx=yyyyynnnnn  in the
second to to reflect the nnnnn (node number) of the first node.

Hopefully that is clear.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*



On Fri, Dec 8, 2017 at 11:47 PM, "stan siems via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Any one know how to fix the ID on the second node  sounds like clicks,
> first node ID works fine.
>
> --
> Thanks
>  Stan Siems
> WB0EMJ
>  The difficult we do right away the impossible just takes a little longer
> and the words it can't be done should never be spoken!
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org