Date   

Re: UDRC II Hotspot connect remotely to Icom Repeater for gateway access #udrc-ii #vhf

Johnny
 

Next I would check the wirings from UDRC to the icom 7000. I guess you are using the minidin 9600 baud connection to radio. I am not familiar with icom 7000, but may want to make sure it is set to 9600 baud. 
You may have an open in the tx part of the cable! 
2- The icom repeater may not be giving out the correct RPT1 and RPT2. The software in UDRC, needs the correct RPT1 and RPT2, in order to get keyed up. 



On Mar 8, 2018, at 12:10 PM, Lardizabal David D. via Groups.Io <davidlardizabal@...> wrote:

Correction no incoming transmissions as well as outgoing in the GATEWAY setting. 


Re: UDRC II Hotspot connect remotely to Icom Repeater for gateway access #udrc-ii #vhf

Lardizabal David D.
 

Correction no incoming transmissions as well as outgoing in the GATEWAY setting. 


Re: UDRC II Hotspot connect remotely to Icom Repeater for gateway access #udrc-ii #vhf

Lardizabal David D.
 

Hi Johnny,

Thanks for the response I have made the change but it still remains the same only outgoing transmission, but no incoming pass from/to UDRC to the VHF radio.


Re: Sound cards

Basil Gunn
 

The Pi's all have sound cards baked in... What is the drive to
purchase an expensive sound card? What problem am I missing?
RPi's have no audio input.

UDRC provides 2 channels with buffered PTT control on 2 different
connectors. Integrated solution using cables that plug into a HAT
provides a nice package for doing HAM digital modes.

The Ti TLV320AIC32X4 used by the UDRC is a good quality low power
stereo CODEC.

UDRC works well with direwolf at 1200/9600 & higher rates.

Compared to a Kantronics KPC3+ the UDRC solution is not expensive and
provides way better capabilities.

/Basil n7nix


Re: Sound cards

 

The Pi does not have audio input.

Matthew Pitts
N8OHU


On March 8, 2018 9:12:55 AM EST, Steve McGrane <temporarilyoffline@...> wrote:
I've seen a lot of talk about using sound cards with Ham radio (not just limited to the RPi experience, but my question applies broadly enough to catch the Pi anyway).

The Pi's all have sound cards baked in... What is the drive to purchase an expensive sound card?  What problem am I missing?

- Steve

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Sound cards

Steve McGrane <temporarilyoffline@...>
 

I've seen a lot of talk about using sound cards with Ham radio (not just limited to the RPi experience, but my question applies broadly enough to catch the Pi anyway).

The Pi's all have sound cards baked in... What is the drive to purchase an expensive sound card?  What problem am I missing?

- Steve


Re: UDRC II Hotspot connect remotely to Icom Repeater for gateway access #udrc-ii #vhf

Johnny
 

You can't have access point set to SIMPLEX. It should be set to GATEWAY in the software. The dstarrepeater repeater software will do the swapping of the RPT1 and RPT2, so that the UDRC software would be able to key up the repeater.


On Mar 8, 2018, at 7:50 AM, Lardizabal David D. via Groups.Io <davidlardizabal@...> wrote:

Hi,

My name is David Lardizabal (HQ2DDL), I am located in San Pedro Sula, Honduras.  I have a UDRC II sound card on a RPi 3+.  I have used the set up for a high power hotspot simplex (5 watts), it has worked great with and Icom 7000 and a Yaesu FT 8100R.  This setup has worked on a simplex frequency 147.100, I have received and transmitted with an Icom 4100A and Kenwood TH D74 at a distance of about 20 Km.  
The new project is to give gateway acces to DSTAR Icom repeater, because at site their is no internet access.  I have set up the ircddbgateway and a dstarrepeater 3 for this purpose.  The DSTAR Icom repeater is on 146.94 with -DUP of 0.600.  I have been able to get the UDRC II with the RPi 3+ and Icom 7000 to recieve signal from Kenwood TH D74 through the DSTAR Icom repeater  and it wil connect to what ever reflector or unlink just fine.  Once connected I have transmitted to the repeater with TH D74 and it sends signal to NODE/access point/hotspot set up and it will send to connected reflector.
When a transmission is sent from reflector and received,  the UDRC II does not keyup the PTT on the ICOM  7000 to send signal to the DSTAR repeater for broadcasting.  I have looked at all settings, but I can not see/find where or what setting I have missed to make this setup work on the RX part. 

Settings on dstarrepeater 3 are:
CALLSIGN TAB:
Callsign HQ2DDL C
Gateway HQ2DDL G
Mode simplex
Ack BER
Restrict Off
RPT1 Validation Off
DTMF Blanking On
Error Reply On
NETWORK TAB:
Gateway Address 127.0.0.1
Gateway Port 20010
Local Adress 127.0.0.1
Local Port 20013
Name UDRC
TIMERS TAB:
Timeout 150 sec
Act Time 200 ms
ANNOUCEMENT TAB:
Disabled
BEACON TAB:
Time 30 min
Message Star  UDRC
Voice Disabled
Language English
MODEM TAB:
Type Sound Card
Configure
Rx Device hw, 0,0 (udrc)
Tx Device hw, 0,0, (urdc)
Rx Inversion On
Tx Inversion Off
Rx Level % 100
Tx Level % 100
Tx Delay 150 ms
Tx Tail 50 ms
CONTROL 1 
Disabled
CONTROL 2
Nonething
CONTROLLER
None

I would appreciate any help in the matter.  At the moment I can not see where the error is, I am almost positive it has to do with a setting parameter.

Sincerely,

David Lardizabal
HQ2DDL


UDRC II Hotspot connect remotely to Icom Repeater for gateway access #udrc-ii #vhf

Lardizabal David D.
 

Hi,

My name is David Lardizabal (HQ2DDL), I am located in San Pedro Sula, Honduras.  I have a UDRC II sound card on a RPi 3+.  I have used the set up for a high power hotspot simplex (5 watts), it has worked great with and Icom 7000 and a Yaesu FT 8100R.  This setup has worked on a simplex frequency 147.100, I have received and transmitted with an Icom 4100A and Kenwood TH D74 at a distance of about 20 Km.  
The new project is to give gateway acces to DSTAR Icom repeater, because at site their is no internet access.  I have set up the ircddbgateway and a dstarrepeater 3 for this purpose.  The DSTAR Icom repeater is on 146.94 with -DUP of 0.600.  I have been able to get the UDRC II with the RPi 3+ and Icom 7000 to recieve signal from Kenwood TH D74 through the DSTAR Icom repeater  and it wil connect to what ever reflector or unlink just fine.  Once connected I have transmitted to the repeater with TH D74 and it sends signal to NODE/access point/hotspot set up and it will send to connected reflector.
When a transmission is sent from reflector and received,  the UDRC II does not keyup the PTT on the ICOM  7000 to send signal to the DSTAR repeater for broadcasting.  I have looked at all settings, but I can not see/find where or what setting I have missed to make this setup work on the RX part. 

Settings on dstarrepeater 3 are:
CALLSIGN TAB:
Callsign HQ2DDL C
Gateway HQ2DDL G
Mode simplex
Ack BER
Restrict Off
RPT1 Validation Off
DTMF Blanking On
Error Reply On
NETWORK TAB:
Gateway Address 127.0.0.1
Gateway Port 20010
Local Adress 127.0.0.1
Local Port 20013
Name UDRC
TIMERS TAB:
Timeout 150 sec
Act Time 200 ms
ANNOUCEMENT TAB:
Disabled
BEACON TAB:
Time 30 min
Message Star  UDRC
Voice Disabled
Language English
MODEM TAB:
Type Sound Card
Configure
Rx Device hw, 0,0 (udrc)
Tx Device hw, 0,0, (urdc)
Rx Inversion On
Tx Inversion Off
Rx Level % 100
Tx Level % 100
Tx Delay 150 ms
Tx Tail 50 ms
CONTROL 1 
Disabled
CONTROL 2
Nonething
CONTROLLER
None

I would appreciate any help in the matter.  At the moment I can not see where the error is, I am almost positive it has to do with a setting parameter.

Sincerely,

David Lardizabal
HQ2DDL


Re: UDRC not repeating

G3GJA
 

John

The

etc/opendv/dstarrepeaterd_1

file is attached. Suffix added for Notepad.

73

Clive G3GJA

===============================================================================================

Hi Clive,

 

A few more pieces of information would be helpful.

 

Is the DR-1X on VHF or UHF?  Did you select the matching choice on the Web Interface? (It affects the way it sees the incoming signal)

 

Is CTCSS/DCS set an analogue for FM?

 

What is output by cat /sys/firmware/devicetree/base/hat/product_ver

 

If you don't get it running, send me your /etc/opendv/dstarrepeaterd_1 file via email to look at.

 

 




 

On Sun, Feb 11, 2018 at 3:05 PM, CliveR <clive@...> wrote:

I've having another attempt to use the UDRC (original version) to get D-Star on a Yaesu DR-1X as it now has v1.10q firmware installed. I have installed the image from starbuck.hays.org., using the web interface to configure it.

Tthe ircDDB gateway links to the DCS reflectors and any activity there is relayed by the DR-1X and is received on my IC-E2820 or an ID-51. However, when I transmit D-Star on the repeater's uplink channel the repeater's display shows both Tx and Rx switching to FM (changes from both Red to both Yellow) and the Rx symbol goes green indicating signal received but the transmitter does not key up until the input signal de-keys and then the DR-1X sends the usual pip. In other words it relays network traffic but not RF. 

This problem does not always show and then a valid D-Star signal on the input is relayed. About 1 in 10 startups successfully relay D-Star RF. FM relaying works normally at all times. I have tried different SD cards and a different Raspberry Pi (a model 2B and a 3) with no difference. The repeater is set to wide deviation although it will need to use narrow FM when it goes into service.

A D-Star RF input signal produces 220mV pk-pk of D-Star data on pin 8 of the interface (discout) but there is 620mV pk-pk of audio when using FM; is there enough D-Star signal for the modem chip? pin 6 (tone in) has around 1v pk-pk when relaying the reflector.

Can anyone suggest why it won't relay D-Star RF please?

Clive G3GJA




 

--

 


John D. Hays
Edmonds, WA

K7VE

 

 

_._,_._,_

 

Clive

HESH Computer Services Limited Tel: (01482) 324936
12 Louis Pearlman Centre Web: www.hesh.co.uk
Goulton Street Registered in England No.: 3003479
Hull VAT No.: GB 647 3679 95
HU3 4DL

Disclaimer:
The information contained in this email may be legally privileged and/or confidential. If you are not the intended recipient, use of this information (including disclosure, copying or distribution) or any action taken, or omitted to be taken, in reliance on it is prohibited and may be unlawful; therefore please inform the sender and delete the message immediately. The views expressed in this email are those of the originator and not necessarily those held by HESH Computer Services Ltd, who do not accept liability for any action taken in reliance on the contents of this message or for the consequences of any computer viruses which may have been transmitted by this email.


Re: UDRC not repeating

G3GJA
 

John

The
/etc/opendv/dstarrepeaterd_1 file is attached.

73

Clive G3GJA

===============================================================================================

Hi Clive,

 

A few more pieces of information would be helpful.

 

Is the DR-1X on VHF or UHF?  Did you select the matching choice on the Web Interface? (It affects the way it sees the incoming signal)

 

Is CTCSS/DCS set an analogue for FM?

 

What is output by cat /sys/firmware/devicetree/base/hat/product_ver

 

If you don't get it running, send me your /etc/opendv/dstarrepeaterd_1 file via email to look at.

 

 



 

On Sun, Feb 11, 2018 at 3:05 PM, CliveR <clive@...> wrote:

I've having another attempt to use the UDRC (original version) to get D-Star on a Yaesu DR-1X as it now has v1.10q firmware installed. I have installed the image from starbuck.hays.org., using the web interface to configure it.

Tthe ircDDB gateway links to the DCS reflectors and any activity there is relayed by the DR-1X and is received on my IC-E2820 or an ID-51. However, when I transmit D-Star on the repeater's uplink channel the repeater's display shows both Tx and Rx switching to FM (changes from both Red to both Yellow) and the Rx symbol goes green indicating signal r eceived but the transmitter does not key up until the input signal de-keys and then the DR-1X sends the usual pip. In other words it relays network traffic but not RF. 

This problem does not always show and then a valid D-Star signal on the input is relayed. About 1 in 10 startups successfully relay D-Star RF. FM relaying works normally at all times. I have tried different SD cards and a different Raspberry Pi (a model 2B and a 3) with no difference. The repeater is set to wide deviation although it will need to use narrow FM when it goes into service.

A D-Star RF input signal produces 220mV pk-pk of D-Star data on pin 8 of the interface (discout) but there is 620mV pk-pk of audio when using FM; is there enough D-Star signal for the modem chip? pin 6 (tone in) has around 1v pk-pk when relaying the reflector.

Can anyone suggest why it won't relay D-Star RF please?

Clive G3GJA



 

--

 


John D. Hays
Edmonds, WA

K7VE

 


_._,_._,_

Clive

HESH Computer Services Limited Tel: (01482) 324936
12 Louis Pearlman Centre Web: www.hesh.co.uk
Goulton Street Registered in England No.: 3003479
Hull VAT No.: GB 647 3679 95
HU3 4DL

Disclaimer:
The information contained in this email may be legally privileged and/or confidential. If you are not the intended recipient, use of this information (including disclosure, copying or distribution) or any action taken, or omitted to be taken, in reliance on it is prohibited and may be unlawful; therefore please inform the sender and delete the message immediately. The views expressed in this email are those of the originator and not necessarily those held by HESH Computer Services Ltd, who do not accept liability for any action taken in reliance on the contents of this message or for the consequences of any computer viruses which may have been transmitted by this email.


Re: direwolf configuration file

John Spoonhower
 

Basil and Bernard,
all is well now. Thanks for the help. I will do a deviation test once I put together the necessary hardware.
again, 73, 
NX2I

On Fri, Feb 16, 2018 at 3:19 PM, Basil Gunn <basil@...> wrote:
Below is what you gave for your Position Beacon command. You are
trying to send out chan 0, that won't work. You need to set sendto=1
so that it uses the proper channel. You are using the mDin6 cable so
you must use channel 1.

PBEACON delay=1 sendto=0 every=10 overlay=R symbol="igate" lat=28^52.69N long=82^$
#PBEACON delay=1 sendto=1 every=10 overlay=S symbol="digi" lat=17^51.00N long=102$

Also set the PTT GPIO's back to the values I gave:

Chan 0 PTT GPIO 12
Chan 1 PTT GPIO 23


> I purchased the din 6 cable from the NW Digital Radio website at the
> same time I purchased the UDRC-II board. They arrived together.

Good

> Your suggestion for the direwolf.conf file does NOT key the radio.

Because your PBEACON command is wrong.

> However, if I reverse the PTT GPIO settings between the 2 channels
> the radio does key (PTT activated).

Because PBEACON is trying to send out channel 0 PTT works but the
audio is going out the wrong port.

> ./alsa-show.sh
> PCM         L:[6.00dB], R:[6.00dB]
> ADC Level L:[6.00dB], R:[6.00dB]
> LO Driver Gain  L:[0.00dB], R:[0.00dB]

PCM & ADC Level seem high but someone that has a working Yaesu radio
should chime in.

/Basil





Re: direwolf configuration file

Basil Gunn
 

Below is what you gave for your Position Beacon command. You are
trying to send out chan 0, that won't work. You need to set sendto=1
so that it uses the proper channel. You are using the mDin6 cable so
you must use channel 1.

PBEACON delay=1 sendto=0 every=10 overlay=R symbol="igate" lat=28^52.69N long=82^$
#PBEACON delay=1 sendto=1 every=10 overlay=S symbol="digi" lat=17^51.00N long=102$

Also set the PTT GPIO's back to the values I gave:

Chan 0 PTT GPIO 12
Chan 1 PTT GPIO 23


I purchased the din 6 cable from the NW Digital Radio website at the
same time I purchased the UDRC-II board. They arrived together.
Good

Your suggestion for the direwolf.conf file does NOT key the radio.
Because your PBEACON command is wrong.

However, if I reverse the PTT GPIO settings between the 2 channels
the radio does key (PTT activated).
Because PBEACON is trying to send out channel 0 PTT works but the
audio is going out the wrong port.

./alsa-show.sh
PCM L:[6.00dB], R:[6.00dB]
ADC Level L:[6.00dB], R:[6.00dB]
LO Driver Gain L:[0.00dB], R:[0.00dB]
PCM & ADC Level seem high but someone that has a working Yaesu radio
should chime in.

/Basil


Re: direwolf configuration file

Bernard f6bvp / ai7bg
 

Sorry picture did not follow on the list.

When din6 plug is oriented with vertical slot upward, the correct hole is the second one the left that is nearly horizontal.

73 de Bernard f6bvp

Le 16 févr. 2018 à 21:10, f6bvp <f6bvp@...> a écrit :

Hi,

Din6 plug looks like :


I guess you don’t have an oscilloscope to visualize electric audio signals. I suggest you connect an earphone wire into the left horizontal hole according to the figure and the other earphone wire to ground of RPi. Then you should be able to hear a tone when output is activated. Same with a male connector.

73 de Bernard f6bvp



<image1.jpeg>


Re: direwolf configuration file

Bernard f6bvp / ai7bg
 

Hi,

Din6 plug looks like :


I guess you don’t have an oscilloscope to visualize electric audio signals. I suggest you connect an earphone wire into the left horizontal hole according to the figure and the other earphone wire to ground of RPi. Then you should be able to hear a tone when output is activated. Same with a male connector.

73 de Bernard f6bvp


Re: direwolf configuration file

Bernard f6bvp / ai7bg
 

Hi,
Did you try to run measure.deviate script and see if audio output is ok ? You may still have to edit the script in order to trigger PTT.

73 de Bernard f6bvp

Le 16 févr. 2018 à 19:54, John Spoonhower <jpspoonhower@...>


Re: direwolf configuration file

John Spoonhower
 

Basil,
I purchased the din 6 cable from the NW Digital Radio website at the same time I purchased the UDRC-II board. They arrived together.
Your suggestion for the direwolf.conf file does NOT key the radio. However, if I reverse the PTT GPIO settings between the 2 channels the radio does key (PTT activated). The relevant portion of my direwolf.conf file now looks like the following (with PTT working OK):

ADEVICE plughw:CARD=udrc,DEV=0 plughw:CARD=udrc,DEV=0
ARATE 48000
ACHANNELS 2
#HD-15
CHANNEL 0
MYCALL NX2I-10
MODEM 1200
PTT GPIO 23
#DIN-6
CHANNEL 1
MYCALL NX2I-10
MODEM 1200
PTT GPIO 12

Transmitter keys, still no audio when listening on a second radio 9a handheld).
I ran the alsa-show script; the results, after lowering the LO Drive level are:

./alsa-show.sh
PCM         L:[6.00dB], R:[6.00dB]
ADC Level L:[6.00dB], R:[6.00dB]
LO Driver Gain  L:[0.00dB], R:[0.00dB]

I can confirm that LO DAC, LOR output, and LOL output all show "00", i.e not muted.

For my own sanity, I confirmed that FLDIGI still works and indeed produces a nice tone when the "Tune" button is activated.

FLDIGI reports the following, BTW, when starting:

I: start_alert_thread: started audio alert thread
I: set_gpio: Set GPIO ptt on /sys/class/gpio/gpio23/value HIGH
I: set_gpio: Set GPIO ptt on /sys/class/gpio/gpio23/value LOW


On Fri, Feb 16, 2018 at 11:51 AM, Basil Gunn <basil@...> wrote:
Your PTT GPIO & cable connection comment is still wrong.  Not your
fault, I believe the "UDRC and Direwolf Packet Modem" wiki is
incorrect.

Your config should be like this:

 HD15  is on right audio channel, Direwolf chan 0
 mDin6 is on left audio channel,  Direwolf chan 1

ARATE 48000
ACHANNELS 2

#HD-15
CHANNEL 0
MYCALL NX2I-10
MODEM 1200
PTT GPIO 12

# DIN-6
CHANNEL 1
MYCALL NX2I-10
MODEM 1200
PTT GPIO 23

You are only concerned with the mDin6 connection so left audio
channel, Direwolf chan 1.

Verify using alsamixer that LOL Outp is not muted ie. shows 00 not MM.
Also verify 'LO Drive' is around 0 dB or less.

I use a script to display just ADC Level, LO Drive Gain & PCM to make
sure those are reasonable.

https://github.com/nwdigitalradio/n7nix/blob/master/debug/alsa-show.sh

Someone who has an Yaesu FT-857 should comment on what those values
should be.  Sorry don't own any Yaesu's. John?

For my Kenwood I set the alsamixer settings like this:
'ADC Level' -2.0dB
'LO Driver Gain' 0dB
'PCM' 0.0dB

What is your source of the mDin6 cable? Hand made? or bought from?

/Basil

On Fri, 16 Feb 2018 10:52:37 -0500
John Spoonhower <jpspoonhower@...> wrote:

> Basil, (and others...),
> I have edited the direwolf.conf file as you suggested. The file now
> looks like this:
>
> ADEVICE plughw:CARD=udrc,DEV=0 plughw:CARD=udrc,DEV=0
> ARATE 48000
> ACHANNELS 2
> #DIN-6
> CHANNEL 0
> MYCALL NX2I-10
> MODEM 1200
> # note PTT is set to "BCM" value ; same is in fldigi
> PTT GPIO 23

> #HD-15
> # note channels set the same
> CHANNEL 1
> MYCALL NX2I-10
> MODEM 1200
> PTT GPIO 23





Re: direwolf configuration file

Basil Gunn
 

Your PTT GPIO & cable connection comment is still wrong. Not your
fault, I believe the "UDRC and Direwolf Packet Modem" wiki is
incorrect.

Your config should be like this:

HD15 is on right audio channel, Direwolf chan 0
mDin6 is on left audio channel, Direwolf chan 1

ARATE 48000
ACHANNELS 2

#HD-15
CHANNEL 0
MYCALL NX2I-10
MODEM 1200
PTT GPIO 12

# DIN-6
CHANNEL 1
MYCALL NX2I-10
MODEM 1200
PTT GPIO 23

You are only concerned with the mDin6 connection so left audio
channel, Direwolf chan 1.

Verify using alsamixer that LOL Outp is not muted ie. shows 00 not MM.
Also verify 'LO Drive' is around 0 dB or less.

I use a script to display just ADC Level, LO Drive Gain & PCM to make
sure those are reasonable.

https://github.com/nwdigitalradio/n7nix/blob/master/debug/alsa-show.sh

Someone who has an Yaesu FT-857 should comment on what those values
should be. Sorry don't own any Yaesu's. John?

For my Kenwood I set the alsamixer settings like this:
'ADC Level' -2.0dB
'LO Driver Gain' 0dB
'PCM' 0.0dB

What is your source of the mDin6 cable? Hand made? or bought from?

/Basil

On Fri, 16 Feb 2018 10:52:37 -0500
John Spoonhower <jpspoonhower@...> wrote:

Basil, (and others...),
I have edited the direwolf.conf file as you suggested. The file now
looks like this:

ADEVICE plughw:CARD=udrc,DEV=0 plughw:CARD=udrc,DEV=0
ARATE 48000
ACHANNELS 2
#DIN-6
CHANNEL 0
MYCALL NX2I-10
MODEM 1200
# note PTT is set to "BCM" value ; same is in fldigi
PTT GPIO 23
#HD-15
# note channels set the same
CHANNEL 1
MYCALL NX2I-10
MODEM 1200
PTT GPIO 23


Re: direwolf configuration file

John Spoonhower
 

Bernard,
I am using the din 6 cable I purchased from the NW Digital radio web site.
73, NX2I


On Thu, Feb 15, 2018 at 1:51 PM, f6bvp <f6bvp@...> wrote:
Hi,
The main question is which plug are you using : din6 or hd15 ? And what kind of cable. I guess you use din6 for you have selected GPIO 23 for channel 1.  If using din6 with a standard din6 cable you may need to use -n 1 parameter on Direwolf command line to get audio output. Careful you may need to change GPIO in case ptt does not work.
I suppose you have set correct  audio level of PCM in alsamixer ?
LOR level is also important. I prefere to set it to 0 (null) to get a more clean audio output.
Did you notice spurious letter i after 1200 on your first MODEM 1200 line ?

73 de Bernard f6bvp
> Le 15 févr. 2018 à 18:14, John Spoonhower <jpspoonhower@...> a écrit :
>
> CHANNEL 0
> MYCALL NX2I-10
> MODEM 1200i
> PTT GPIO 23






Re: direwolf configuration file

John Spoonhower
 

Bernard,
thanks for the reply. The alsamixer levels are PCM, ADC, and LO Drive all set to 6 dB.
the spurious "i" after MODEM 1200 was not in the file, but a typo in the note I sent.
I have also boosted the input gain somewhat from the default in the FT-857; there are menu settings to control packet, 
mic, etc. gain for various inputs. What do you mean by LOR?
73, John, NX2I

On Thu, Feb 15, 2018 at 1:51 PM, f6bvp <f6bvp@...> wrote:
Hi,
The main question is which plug are you using : din6 or hd15 ? And what kind of cable. I guess you use din6 for you have selected GPIO 23 for channel 1.  If using din6 with a standard din6 cable you may need to use -n 1 parameter on Direwolf command line to get audio output. Careful you may need to change GPIO in case ptt does not work.
I suppose you have set correct  audio level of PCM in alsamixer ?
LOR level is also important. I prefere to set it to 0 (null) to get a more clean audio output.
Did you notice spurious letter i after 1200 on your first MODEM 1200 line ?

73 de Bernard f6bvp
> Le 15 févr. 2018 à 18:14, John Spoonhower <jpspoonhower@...> a écrit :
>
> CHANNEL 0
> MYCALL NX2I-10
> MODEM 1200i
> PTT GPIO 23






Re: direwolf configuration file

 

Also look at your alsa output settings, the script should set them, but you can view them with alsamixer program.