> On Jan 1, 2019, at 2:01 PM, Daniel VE3NI <dgoodier@...> wrote:

> 

> This however has not resolved the fact that gpsd service does not start automatically on startup until I either issue a systemctl start gpsd.service or run gpsmon.

> 

> I believe that this is still under investigation.

If you haven’t already checked, make sure that as part of the GPSD_OPTIONS variable in /etc/default/gpsd, it includes the “-n” flag.  It should read something like:

GPSD_OPTIONS="-n -G”

This line will cause gpsd to start as a daemon and to answer queries from outside of the Pi (if, for example, you wanted to use it as a GPS source for Xastir or YACC).

--

Annaliese McDermond (NH6Z)

nh6z@...

> Cheers,

> Daniel  VE3NI / NI2D

It appears to me that you have incorrect settings in your config.txt file.  I will make this very explicit because I’m not sure I’ve made myself clear before:

*ORDER MATTERS IN LINES IN config.txt*

If you do not get the directives in the correct order, the OS kernel will not load the correct drivers for you.

If you intend to use the onboard audio on the Pi, the line

dtparam=audio=on

*MUST* come after the lines

dtoverlay=
dtoverlay=draws

Otherwise the device tree will not be loaded correctly and you won’t get a proper driver set.

--
Annaliese McDermond (NH6Z)
nh6z@...

On Jan 1, 2019, at 3:56 PM, Joseph Vilardo <jvilardo@...> wrote:

Basil

I ran your suggested procedures and I am still where I was when I started.  When I run FLDIGI, after doing all the prerequisites for shutting down  DIREWOLF and and running ./ax25-stop , I still cannot select a sound card from the fldigi audio setup menu.  To select the the codec from the fldigi audio set up I must have #dtparam=audio=on commented out in the config.txt file. With dtparam=audio=on commented out with the # symbol I can then select urdc: - (hw:0,0) , not urdc: - (hw:0,1) for capture and urdc:-(hw:0,0) for playback. This result is what you said enumerates with dtparm=audio=on commented out, only hw 0,0 will enumerate. 

When following the new draw "getting started doc "DRAWS Raspberry PI image"  from the wiki and run "aplay-l I" do not get the same results shown in the example of the doc. 

This what I see:


**** List of PLAYBACK Hardware Devices ****

card 
0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]

  
Subdevices: 7/7

  
Subdevice #0: subdevice #0

  
Subdevice #1: subdevice #1

  
Subdevice #2: subdevice #2

  
Subdevice #3: subdevice #3

  
Subdevice #4: subdevice #4

  
Subdevice #5: subdevice #5

  
Subdevice #6: subdevice #6

card 
0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]

  
Subdevices: 1/1

  
Subdevice 
#0: subdevice #0

Your example shows the following which I do not get:


 card 1: udrc [udrc], device 0: Universal Digital Radio Controller tlv320aic32x4-hifi-0 []

  
Subdevices: 0/1

  
Subdevice #0: subdevice #0

I have tried re formatting the micro sd card, changing sd cards,  re burning the image, changing the RPi 3 B+ to a different RPi B+, powering the RPi/DRAWS board from 12 volt supply. I am out of ideas and because of the anomaly in the results from aplay -l I think the problem it is a hardware failure of the DRAWS Board.

If you have any suggestions I am ready to try them.

Best regards and happy New Year,

Joe K3JV





On 12/30/2018 1:08 AM, Basil Gunn wrote:

Joe,
Thanks for all the information.

I have been successful in verifying the core operation of Beta 6 and
have Direwolf/YAAC running without issue on port 0. I also have FLDIGI
running on port 0 (left hand port on the draws board) without a
problem but had to deviate from the information in
DRAWS_CONFIG.md. The directions in the verify document tell us to
remove the # from dtparm=audio=on to "Test analog audio" . I do that
by removing the # in the config.txt file for the Rpi and the test runs
and I get the results indicated. The same is true for "TEST OF HDMI
AUDIO" . By the way there is a minor error in the information the beta
6 release doesn't have a file named "silence.wav" in $
/usr/share/xastir/sounds.

Yes I see that. I'll fix it.
For now just copy it from n7nix/xastir/silence.wav to the
/usr/share/xastir/silence.wav

Here is the question. When I complete the verify core test and
shutdown --ax25

You need to run a script in your local bin called. ax25-stop

and then start FLDIGi and try to configure the sound
card FLDIGI fails and shuts down.

Try this.
You should see the process id of direwolf the first time you run pidof
and not the second time.

cd
cd bin
sudo su
pidof direwolf
./ax25-stop
pidof direwolf

Now run fldigi

In fldigi under the choices in the
audio selection menu there is no udrc audio choice available.

I just tried it & Fldigi enumerates:
udrc: -(hw:1,0)

without the enabled RPi sound device the udrc will enumerate like this:
udrc: -(hw:0,0)

I have a feeling you are not shutting down direwolf.
The next image will have direwolf unloaded by default.

IF I go
back to CONFIG.TXT and comment out, put the # in, for the line
dtparam=audio=on, reboot, start FLDIGI I can then select the udrc 0
port and complete the configuration of fldigi without issue and fldigi
runs just fine. Am I overlooking something in your instructions?
Or are we to comment out the dtparam=audio=on in the config.txt of the
RPi

There should be no problem enabling the BCM2835 RPi sound device.
I use it with Xastir for the sound alerts.

I am making some progress with WSTX I can receive and decode but not
transmit yet. I need to recheck the cable I made that goes from the
6pin mini din of the draws board to the 13 pin Din of my TS 590.

Thanks,
K3JV Joe

On Dec 31, 2018, at 1:34 PM, Jack Spitznagel <kd4iz@frawg.org> wrote:

Hi Basil,

Again Thanks!!!
I understand these differences. Not confusing. I have been leaving the base config alone for now, but with the info from Annaliese yesterday and yours below, is speculative experimentation fair game now 😊?

Her notes on the implementation of the TI CODEC chip brought up these questions:
1. Should we disable the port not in use if only using 1 of them?? Annaliese suggests this would eliminate possibility of crosstalk. Is there a description of how you do this in the DRAWS wiki or your github pages? I missed it.

2. The info she sent about the PTM-P1/2/3 (DAC Left|Right Playback Powertune) settings for selecting the max output level suggests that the PTM-P1 setting should be default for the sensitive radios like the 7000. I look forward to seeing that available in Beta7. Where is it defaulting to now?

3. Her description of the three resistances associated with configuring input routing appear to be for the input only, I assume input from the rig?

Do they also impact the output to the rig? What you say below implies that... I am a little confused on this now.

For the record, I am doing everything at 1200 for the initial testing here thus focusing on IN2. IN1 - 9600/GMSK will come later once I know things work the way I want.

Assume you mean the 7000 below, not the 7100? They appear similar as far as the data port specs are concerned, I just have not played with the 7100 all that much other than using its internal sound device for HRD/DM780 ops and as a modem for Spectrum Lab.

In the DRAWS implementation here, the IC-7000 and the FT-817 will get used (max portability), both of which I have used with audio/data and GMSK/data in the past. The IC-7100 here is happy as is, mostly acts as #2 in an SO2R set up, providing 144/440 coverage and HF D-STAR. The primary HF radio can't do that.

If you have something specific you would like me to look at, or a possible solution you want to test for one of these radios (assuming not all are available to you), please ask. I have or can scrounge pretty much any needed test equipment. I also have a PDF copy of the service manual for the IC-7000 which may provide more clarity for that radio if you think it might help.

KD4IZ
Jack Spitznagel
FM19oo

so I found out about this problem quite by accident... if you run
xastir that was installed by apt from the repository and you want to
build from the source (for version 2.1.1 or later) you have to
rename/modify/delete xastir.cnf in ~/.xastir/config to point to
/usr/local/share/xastir instead of /usr/share/xastir.

Also, as of this writing the beta images come with the binary version
of xastir (version 2.0.8)

I ran your suggested procedures and I am still where I was when I
started. When I run FLDIGI, after doing all the prerequisites for
shutting down DIREWOLF and and running ./ax25-stop , I still cannot
select a sound card from the fldigi audio setup menu. To select the the
codec from the fldigi audio set up I must have #dtparam=audio=on
commented out in the config.txt file. With dtparam=audio=on commented
out with the # symbol I can then select urdc: - (hw:0,0) , not urdc: -
(hw:0,1) for capture and urdc:-(hw:0,0) for playback. This result is
what you said enumerates with dtparm=audio=on commented out, only hw 0,0
will enumerate.

When following the new draw "getting started doc "DRAWS Raspberry PI
image" from the wiki and run "aplay-l I" do not get the same results
shown in the example of the doc.

This what I see:

|****ListofPLAYBACK HardwareDevices****card 0:ALSA [bcm2835 ALSA],device
0:bcm2835 ALSA [bcm2835 ALSA]Subdevices:7/7Subdevice#0: subdevice
#0Subdevice#1: subdevice #1Subdevice#2: subdevice #2Subdevice#3:
subdevice #3Subdevice#4: subdevice #4Subdevice#5: subdevice
#5Subdevice#6: subdevice #6card 0:ALSA [bcm2835 ALSA],device 1:bcm2835
ALSA [bcm2835 IEC958/HDMI]Subdevices:1/1Subdevice#0: subdevice #0 Your
example shows the following which I do not get: |

**

*|card 1:udrc [udrc],device
0:UniversalDigitalRadioControllertlv320aic32x4-hifi-0[]Subdevices:0/1Subdevice#0:
subdevice #0|*

**

I have tried re formatting the micro sd card, changing sd cards, re
burning the image, changing the RPi 3 B+ to a different RPi B+, powering
the RPi/DRAWS board from 12 volt supply. I am out of ideas and because
of the anomaly in the results from aplay -l I think the problem it is a
hardware failure of the DRAWS Board.

If you have any suggestions I am ready to try them.

On Jan 1, 2019, at 3:56 PM, Joseph Vilardo <jvilardo@verizon.net> wrote:

Basil

I ran your suggested procedures and I am still where I was when I started. When I run FLDIGI, after doing all the prerequisites for shutting down DIREWOLF and and running ./ax25-stop , I still cannot select a sound card from the fldigi audio setup menu. To select the the codec from the fldigi audio set up I must have #dtparam=audio=on commented out in the config.txt file. With dtparam=audio=on commented out with the # symbol I can then select urdc: - (hw:0,0) , not urdc: - (hw:0,1) for capture and urdc:-(hw:0,0) for playback. This result is what you said enumerates with dtparm=audio=on commented out, only hw 0,0 will enumerate.

When following the new draw "getting started doc "DRAWS Raspberry PI image" from the wiki and run "aplay-l I" do not get the same results shown in the example of the doc.

This what I see:


**** List of PLAYBACK Hardware Devices ****

card
0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]


Subdevices: 7/7


Subdevice #0: subdevice #0


Subdevice #1: subdevice #1


Subdevice #2: subdevice #2


Subdevice #3: subdevice #3


Subdevice #4: subdevice #4


Subdevice #5: subdevice #5


Subdevice #6: subdevice #6

card
0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]


Subdevices: 1/1


Subdevice
#0: subdevice #0

Your example shows the following which I do not get:


card 1: udrc [udrc], device 0: Universal Digital Radio Controller tlv320aic32x4-hifi-0 []


Subdevices: 0/1


Subdevice #0: subdevice #0

I have tried re formatting the micro sd card, changing sd cards, re burning the image, changing the RPi 3 B+ to a different RPi B+, powering the RPi/DRAWS board from 12 volt supply. I am out of ideas and because of the anomaly in the results from aplay -l I think the problem it is a hardware failure of the DRAWS Board.

If you have any suggestions I am ready to try them.

Best regards and happy New Year,

Joe K3JV





On 12/30/2018 1:08 AM, Basil Gunn wrote:

Joe,
Thanks for all the information.

I have been successful in verifying the core operation of Beta 6 and
have Direwolf/YAAC running without issue on port 0. I also have FLDIGI
running on port 0 (left hand port on the draws board) without a
problem but had to deviate from the information in
DRAWS_CONFIG.md. The directions in the verify document tell us to
remove the # from dtparm=audio=on to "Test analog audio" . I do that
by removing the # in the config.txt file for the Rpi and the test runs
and I get the results indicated. The same is true for "TEST OF HDMI
AUDIO" . By the way there is a minor error in the information the beta
6 release doesn't have a file named "silence.wav" in $
/usr/share/xastir/sounds.

Yes I see that. I'll fix it.
For now just copy it from n7nix/xastir/silence.wav to the
/usr/share/xastir/silence.wav

Here is the question. When I complete the verify core test and
shutdown --ax25

You need to run a script in your local bin called. ax25-stop

and then start FLDIGi and try to configure the sound
card FLDIGI fails and shuts down.

Try this.
You should see the process id of direwolf the first time you run pidof
and not the second time.

cd
cd bin
sudo su
pidof direwolf
./ax25-stop
pidof direwolf

Now run fldigi

In fldigi under the choices in the
audio selection menu there is no udrc audio choice available.

I just tried it & Fldigi enumerates:
udrc: -(hw:1,0)

without the enabled RPi sound device the udrc will enumerate like this:
udrc: -(hw:0,0)

I have a feeling you are not shutting down direwolf.
The next image will have direwolf unloaded by default.

IF I go
back to CONFIG.TXT and comment out, put the # in, for the line
dtparam=audio=on, reboot, start FLDIGI I can then select the udrc 0
port and complete the configuration of fldigi without issue and fldigi
runs just fine. Am I overlooking something in your instructions?
Or are we to comment out the dtparam=audio=on in the config.txt of the
RPi

There should be no problem enabling the BCM2835 RPi sound device.
I use it with Xastir for the sound alerts.

I am making some progress with WSTX I can receive and decode but not
transmit yet. I need to recheck the cable I made that goes from the
6pin mini din of the draws board to the 13 pin Din of my TS 590.

Thanks,
K3JV Joe

Joe,
Thanks for all the information.

I have been successful in verifying the core operation of Beta 6 and
have Direwolf/YAAC running without issue on port 0. I also have FLDIGI
running on port 0 (left hand port on the draws board) without a
problem but had to deviate from the information in
DRAWS_CONFIG.md. The directions in the verify document tell us to
remove the # from dtparm=audio=on to "Test analog audio" . I do that
by removing the # in the config.txt file for the Rpi and the test runs
and I get the results indicated. The same is true for "TEST OF HDMI
AUDIO" . By the way there is a minor error in the information the beta
6 release doesn't have a file named "silence.wav" in $
/usr/share/xastir/sounds.

Yes I see that. I'll fix it.
For now just copy it from n7nix/xastir/silence.wav to the
/usr/share/xastir/silence.wav

Here is the question. When I complete the verify core test and
shutdown --ax25

You need to run a script in your local bin called. ax25-stop

and then start FLDIGi and try to configure the sound
card FLDIGI fails and shuts down.

Try this.
You should see the process id of direwolf the first time you run pidof
and not the second time.

cd
cd bin
sudo su
pidof direwolf
./ax25-stop
pidof direwolf

Now run fldigi

In fldigi under the choices in the
audio selection menu there is no udrc audio choice available.

I just tried it & Fldigi enumerates:
udrc: -(hw:1,0)

without the enabled RPi sound device the udrc will enumerate like this:
udrc: -(hw:0,0)

I have a feeling you are not shutting down direwolf.
The next image will have direwolf unloaded by default.

IF I go
back to CONFIG.TXT and comment out, put the # in, for the line
dtparam=audio=on, reboot, start FLDIGI I can then select the udrc 0
port and complete the configuration of fldigi without issue and fldigi
runs just fine. Am I overlooking something in your instructions?
Or are we to comment out the dtparam=audio=on in the config.txt of the
RPi

There should be no problem enabling the BCM2835 RPi sound device.
I use it with Xastir for the sound alerts.

I am making some progress with WSTX I can receive and decode but not
transmit yet. I need to recheck the cable I made that goes from the
6pin mini din of the draws board to the 13 pin Din of my TS 590.

Thanks,
K3JV Joe

I was messing around last night and I think that if you don't remove 'require' at the end of the gps line it won't update based on the ntp server time chrony just hangs.

testing:
- shutdown pi
- remove gps antenna
- wait 10+ minutes
- boot pi
- use chronyc sources to verify

if you add the -v flag you get this output:


one of the time servers should be selected (either * or +).

Yes this is a change with DRAWS. Left audio to left DIN. 

On Mon, Dec 31, 2018, 12:01 f6bvp <f6bvp@...> wrote:

Hi,

With DRAWS I noticed that PBEACON sendto=0 is sending APRS beacon on
left DIN6 (CHANNEL 0).

This is absolutely correct and in accordance with n7nix
measure_deviate.sh deviation script that sends modulation wav through sox.

However when using UDRC II modem and the same direwolf configuration
file, direwolf is sending beacon via HD15 plug.

If someone wants to send beacon via DIN6 when using UDRC II, PBEACON
sendto=1 must be used.

Is UDRC II CHANNEL inversion the result of a hardware difference between
UDRC II and DRAWS or a bug in UDRC II firmware ?


73 de Bernard, f6bvp

Le 31/12/2018 à 05:18, Annaliese McDermond a écrit :
> I have just posted the following article to the UDRC/DRAWS Wiki:
>
>
>
Bernard, F6BVP
http://f6bvp.org

---

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Basil Gunn
Sent: Monday, December 31, 2018 15:18
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Draws and IC-7000 #draws #ic7000 #miniDIN6

Hi Jack,

Thanks for all the info.

Just a couple of points. HF/VHF/UHF radios like the IC-7000, Yaesu FT-817, FT-857, Kenwood TS-2000 etc. need some understanding of their VHF/UFH packet & HF AFSK digital modes.

At least some of these radios route their vhf/uhf packet audio through their discriminator output & their HF AFSK output through AFOUT. The digital mode determines the pin used on the mDin6 connector so you need to route these pin properly with ALSA mixer settings. With the IC-7100 I think you have the option of setting the 1200 or 9600 bps output independent of the digital mode.

ALSA settings for routing to DISCOUT or AFOUT

IN1 (left & right) is for discriminator out (DISCOUT)

IN2 (left & right) is for audio out (AFOUT) These controls have the following options, 'Off' '10 kOhm' '20 kOhm' '40 kOhm' so you might try the different resistor values to knock down your signal level.

Also in the next couple of days with Beta7 image release you will have 2 more controls that will allow setting the output level, LO Playback Common Mode control and DAC Left & Right Playback PowerTune control.

In the IC-7100 manual there is a warning to never apply data levels over 0.6Vp-p  for TX audio in (DATA IN)

* 0.4 Vp-p (0.2 Vrms): recommended level

* 0.2-0.5 Vp-p (0.1-0.25 Vrms): acceptable level

I need to do more research for you wsjt-x problem.

/Basil

Jack Spitznagel <kd4iz@...> writes:

> Hopefully this experiment provides some useful info:

> 

> I built a breakout strip to help solve the issues with overdrive of

> the

> IC-7000 in fldigi. As I began to put things together I went to the

> ICOM manual (version 5 English) to confirm how they label their pin

> position numbers on the diagram.

> 

> Used a couple of "half cables" that I had from other projects in the

> past, rang out the pin connections, and lined them up on a proto strip

> so a jumper connected each together. This worked same as the mini Din6 cables supplied.

> IC-7000 pinout diagram is at the end of the email for those interested.

> 

> Substituted a junk box 500KOhm pot in for the DATA IN jumper (probably

> overkill for what might really be needed). Ends of the resistor to the

> Pi side cable and to the cable shield/GND, the wiper was to the Radio

> side cable on DATA IN. The pot was initially set so there was no

> resistance in

nn> the DATA IN line.

> 

> After boot, tested Xastir (my control state) first at the original

> alsamixer

> settings:

> 

> PCM               L:[-21.50dB],    R:[-21.50dB

> ADC Level         L:[-2.00dB],     R:[-2.00dB]

> LO Driver Gain    L:[-6.00dB]      R:[-6.00dB]

> IN1               L:[10kOhm],      R:[10kOhm]

> IN2               L:[Off],         R:[Off]

> 

> 

> 

> Xastir worked to spec in FM mode RX and TX.

> 

> 

> 

> Killed AX25, then tested fldigi in USB mode at same alsamixer

> settings. As before, overdrove the radio input causing ALC reading to be high.

> 

> 

> 

> Then increase resistance while transmitting into a dummy load and was

> able to reduce ALC reading considerably while maintaining output

> power. Signal looked clean on Spectrum Lab fed from another receiver.

> 

> 

> 

> Shut down fldigi and restarted AX25/Direwolf. No longer enough audio

> there to drive the rig in FM mode. Sending with Xastir would key rig

> (using flrig) but no signal was TX. Removed the pot, put the jumper

> back in and Xastir could transmit as before.

> 

> 

> 

> Key Findings:

> 

> 

> 

> 1.         There is a difference between the audio input level the IC-7000

> wants for clean FM and for "ALC free SSB". Based on the position of

> the pot, that was a drive signal reduction of about 40 to 50%.

> 2.         For fldigi, the alsamixer PCM and LO Drive settings could be

> increased well above the -30dB noise floor (PCM to 0.00, LO Drive to

> 0.00) tweeking the pot a bit got ALC to essentially zero with rig

> power at ~30% (approximately 25 Watts) and still looking very clean.

> 3.         To confuse the issue, I still have found no way to get wsjt-x to TX

> with sufficient audio regardless of the settings of alsamixer. This

> apparent drive signal attenuation has got to be something wsjt-x is

> doing. Does not make sense.

> 

> 

> 

> It would be great to find the "half-way point" where both HF programs

> and Direwolf use identical alsamixer settings.

> 

> 

> 

> KD4IZ

> 

> Jack Spitznagel