Date   

Re: Brief Introduction and Some Generic Information #ft817 #din6 #audio

 


On Sat, Dec 15, 2018, 21:12 Roderick Wayne Hart Sr. <rod.hart@... wrote:
What's the logname and password for the beta os image? I downloaded it and the raspberry defaults are not accepted.

Rod Hart
wa3mez

On December 15, 2018, at 7:19 PM, Annaliese McDermond <nh6z@...> wrote:

I figured I’d post this since we seem to have some new folks on this list that might benefit.

My name is Annaliese McDermond (you can call me Anna), and I’m one of the software folks that’s involved with NW Digital Radio.  I’m the one who does a lot of the low level things like grubbing around the kernel to try to make the tlv320aic3204 driver work correctly, get the device tree correct for the draws hat so that the serial port works with the GPS and taking care of the udrc-dkms package and build process.  I’ve been a ham for pretty much all of my adult life since getting my license when I was 14 in high school, and I’ve been doing computing even longer.  I have interests in digital communications and SDR.  I was involved with the OpenHPSDR project for a long time and wrote a bit of software to drive their hardware using a Mac.  I also wrote Buster which is a D-STAR reflector client for the Mac.

Unlike many hams these days, I’m not retired so I have a day job that consumes much of my time.  This makes my availability to answer questions and provide fixes sometimes limited.  Many times I have to prioritize my free time so that I don’t go absolutely insane.

I also wanted to point out some resources that intrepid folks can use to find answers and play with the system.

The most important is that NW Digital Radio has a GitHub account where we keep all of our code.  It is at https://github.com/nwdigitalradio.  There is code for nearly everything we do there.  This includes things like the Linux kernel source we use for the udrc driver, to the pi-gen setup that we use to create compass linux images.  We are committed to open source and put pretty much everything we do in this repository.  If you’re looking to “use the source Luke”, this is where to go.  If there’s something you don’t see there for whatever reason, let us know and chances are we’ve just forgotten to push it into Github from our various development systems.

I’m generally happy to answer technical questions for people on how the system works.  Please post them to one of our mailing lists so that others can get the benefit from my answers.  If you e-mail me directly, you chances of a response go way down.

I’d like to thank all the early adopters.  Seeing folks play with something that I and the whole NWDR team have worked so hard on for a number of years is greatly gratifying.  Know that we really want to put out a product that we’re proud of, and when things don’t work as expected, we’re more disappointed than you are.  Thanks for your patience while we work through documentation and software issues that have fallen out of the hardware release.

--
Anna McDermond, J.D.
NH6Z
nh6z@...









Re: Brief Introduction and Some Generic Information #ft817 #din6 #audio

Basil Gunn
 

What's the logname and password for the beta os image? I downloaded it
and the raspberry defaults are not accepted.
login: pi
pw: nwcompass

Rod Hart
wa3mez

On December 15, 2018, at 7:19 PM, Annaliese McDermond <nh6z@...> wrote:

I figured I’d post this since we seem to have some new folks on this list that might benefit.


Re: Brief Introduction and Some Generic Information #ft817 #din6 #audio

Roderick Wayne Hart Sr.
 

What's the logname and password for the beta os image? I downloaded it and the raspberry defaults are not accepted.

Rod Hart
wa3mez

On December 15, 2018, at 7:19 PM, Annaliese McDermond <nh6z@...> wrote:

I figured I’d post this since we seem to have some new folks on this list that might benefit.

My name is Annaliese McDermond (you can call me Anna), and I’m one of the software folks that’s involved with NW Digital Radio. I’m the one who does a lot of the low level things like grubbing around the kernel to try to make the tlv320aic3204 driver work correctly, get the device tree correct for the draws hat so that the serial port works with the GPS and taking care of the udrc-dkms package and build process. I’ve been a ham for pretty much all of my adult life since getting my license when I was 14 in high school, and I’ve been doing computing even longer. I have interests in digital communications and SDR. I was involved with the OpenHPSDR project for a long time and wrote a bit of software to drive their hardware using a Mac. I also wrote Buster which is a D-STAR reflector client for the Mac.

Unlike many hams these days, I’m not retired so I have a day job that consumes much of my time. This makes my availability to answer questions and provide fixes sometimes limited. Many times I have to prioritize my free time so that I don’t go absolutely insane.

I also wanted to point out some resources that intrepid folks can use to find answers and play with the system.

The most important is that NW Digital Radio has a GitHub account where we keep all of our code. It is at https://github.com/nwdigitalradio. There is code for nearly everything we do there. This includes things like the Linux kernel source we use for the udrc driver, to the pi-gen setup that we use to create compass linux images. We are committed to open source and put pretty much everything we do in this repository. If you’re looking to “use the source Luke”, this is where to go. If there’s something you don’t see there for whatever reason, let us know and chances are we’ve just forgotten to push it into Github from our various development systems.

I’m generally happy to answer technical questions for people on how the system works. Please post them to one of our mailing lists so that others can get the benefit from my answers. If you e-mail me directly, you chances of a response go way down.

I’d like to thank all the early adopters. Seeing folks play with something that I and the whole NWDR team have worked so hard on for a number of years is greatly gratifying. Know that we really want to put out a product that we’re proud of, and when things don’t work as expected, we’re more disappointed than you are. Thanks for your patience while we work through documentation and software issues that have fallen out of the hardware release.

--
Anna McDermond, J.D.
NH6Z
nh6z@...


Re: (longer) DRAWS power cable? #draws #power

Brian Badger
 

I do not recommend large gauge pigtails.   You don’t want the connectors on the board to be the point of failure.  What we need is a case design that has a securely mounted powerpole or barrel connector.  Then the pigtail won’t matter.


On Dec 15, 2018, at 3:44 PM, John D Hays - K7VE <john@...> wrote:

Be careful to get the right polarity, to match the pins on the DRAWS board.  We have seen some with the black and red wires switched from what DRAWS is expecting.

We are looking at some options, so don't overdo it on buying a bunch of pigtails.

BTW, pigtails are meant to be just that, a little solder and shrink tubing and connect it to a longer cable with whatever connector you like on the other end.



On Sat, Dec 15, 2018 at 2:15 PM Robert Sears <kf7vop@...> wrote:

Complete assemblies

https://www.adafruit.com/product/261

https://www.sparkfun.com/products/9914

Robert/KF7VOP

On 12/15/2018 09:53 AM, Gayland Gump wrote:
Does anyone have a source for the power pigtails for the DRAWS?  I'll likely need a few as I learn how to put Anderson Power Pole connectors on the non-terminated end of the pigtail.  The one I got with the DRAWS is already getting too short as I fail my way through to having enough experience and technique to achieve success.

Gayland
KG7GCF


On Thu, Dec 6, 2018 at 10:57 AM Bryan Hoyer <bhhoyer@...> wrote:
Connector is JST XRH Series

> On Dec 6, 2018, at 10:38 AM, Steve Stroh <steve.stroh@...> wrote:
>
> Anyone have a lead on a longer power cable for a DRAWS?
>
> Yes, I know I can splice a longer cable onto the one that's supplied
> with the unit, but I'd rather not.
>
> I'm sure there's something on Amazon, but I don't even know what to
> call that particular connector.
>
> Thanks,
>
> Steve N8GNJ
>
> --
> Steve Stroh (personal / general): stevestroh@...
>
>
>






--


John D. Hays
Edmonds, WA
K7VE

   


Internet in the field for your DRAWS™ System #mifi #draws #internet

 

I gave a talk about using the amateur radio IP network and a VPN at DCC this year.  See:
https://www.youtube.com/watch?v=OxsmGaFZ2MM&t=5s

With or without the VPN, I like to operate sometimes away from the WiFi or a wired Internet connection.

I often use this little router https://www.gl-inet.com/products/gl-mifi/ with Google Fi service (US ATT model) -- I just saw they have a 25% off holiday special. (This model should also work with T-Mobile and ATT networks with the proper SIM and plan).

If you want to check out Google Fi (who will provide free SIMs to customers for this type of device, sharing the data plan with the account) -- use https://g.co/fi/r/C622J1 and get $20 credit after 30 days.   (I do get a referral credit, if you use the link or they are offering an equivalent 30 day free trial)                                                                                            
Neither I nor NW Digital Radio are affiliated with GL-INET or Google Fi.  I am just a satisfied customer of both of these products, and passing along the information.

--


John D. Hays
Edmonds, WA
K7VE

   


Brief Introduction and Some Generic Information #ft817 #din6 #audio

Annaliese McDermond
 

I figured I’d post this since we seem to have some new folks on this list that might benefit.

My name is Annaliese McDermond (you can call me Anna), and I’m one of the software folks that’s involved with NW Digital Radio. I’m the one who does a lot of the low level things like grubbing around the kernel to try to make the tlv320aic3204 driver work correctly, get the device tree correct for the draws hat so that the serial port works with the GPS and taking care of the udrc-dkms package and build process. I’ve been a ham for pretty much all of my adult life since getting my license when I was 14 in high school, and I’ve been doing computing even longer. I have interests in digital communications and SDR. I was involved with the OpenHPSDR project for a long time and wrote a bit of software to drive their hardware using a Mac. I also wrote Buster which is a D-STAR reflector client for the Mac.

Unlike many hams these days, I’m not retired so I have a day job that consumes much of my time. This makes my availability to answer questions and provide fixes sometimes limited. Many times I have to prioritize my free time so that I don’t go absolutely insane.

I also wanted to point out some resources that intrepid folks can use to find answers and play with the system.

The most important is that NW Digital Radio has a GitHub account where we keep all of our code. It is at https://github.com/nwdigitalradio. There is code for nearly everything we do there. This includes things like the Linux kernel source we use for the udrc driver, to the pi-gen setup that we use to create compass linux images. We are committed to open source and put pretty much everything we do in this repository. If you’re looking to “use the source Luke”, this is where to go. If there’s something you don’t see there for whatever reason, let us know and chances are we’ve just forgotten to push it into Github from our various development systems.

I’m generally happy to answer technical questions for people on how the system works. Please post them to one of our mailing lists so that others can get the benefit from my answers. If you e-mail me directly, you chances of a response go way down.

I’d like to thank all the early adopters. Seeing folks play with something that I and the whole NWDR team have worked so hard on for a number of years is greatly gratifying. Know that we really want to put out a product that we’re proud of, and when things don’t work as expected, we’re more disappointed than you are. Thanks for your patience while we work through documentation and software issues that have fallen out of the hardware release.

--
Anna McDermond, J.D.
NH6Z
nh6z@...


Re: (longer) DRAWS power cable? #draws #power

Gayland Gump
 

John,

Thanks for the input.  I am pretty much a rank amateur on the hardware side of things.  I've already managed loose an inch or more off the pigtails trying to put some Anderson Power Poles on them.  Hadn't occurred to me to simply solder longer wires to the pigtails.  I assume that I could go to a larger gauge of wire which would allow me to have a somewhat more robust termination to the connectors I want to try.  That 28 gauge wire in the pigtails is awfully fragile to a fumble thumbs like me.

If you have a part number for the pig tails and a source I'd appreciate hearing more from you.
 
Gayland
KG7GCF


On Sat, Dec 15, 2018 at 2:45 PM John D Hays - K7VE <john@...> wrote:
Be careful to get the right polarity, to match the pins on the DRAWS board.  We have seen some with the black and red wires switched from what DRAWS is expecting.

We are looking at some options, so don't overdo it on buying a bunch of pigtails.

BTW, pigtails are meant to be just that, a little solder and shrink tubing and connect it to a longer cable with whatever connector you like on the other end.



On Sat, Dec 15, 2018 at 2:15 PM Robert Sears <kf7vop@...> wrote:

Complete assemblies

https://www.adafruit.com/product/261

https://www.sparkfun.com/products/9914

Robert/KF7VOP

On 12/15/2018 09:53 AM, Gayland Gump wrote:
Does anyone have a source for the power pigtails for the DRAWS?  I'll likely need a few as I learn how to put Anderson Power Pole connectors on the non-terminated end of the pigtail.  The one I got with the DRAWS is already getting too short as I fail my way through to having enough experience and technique to achieve success.

Gayland
KG7GCF


On Thu, Dec 6, 2018 at 10:57 AM Bryan Hoyer <bhhoyer@...> wrote:
Connector is JST XRH Series

> On Dec 6, 2018, at 10:38 AM, Steve Stroh <steve.stroh@...> wrote:
>
> Anyone have a lead on a longer power cable for a DRAWS?
>
> Yes, I know I can splice a longer cable onto the one that's supplied
> with the unit, but I'd rather not.
>
> I'm sure there's something on Amazon, but I don't even know what to
> call that particular connector.
>
> Thanks,
>
> Steve N8GNJ
>
> --
> Steve Stroh (personal / general): stevestroh@...
>
>
>






--


John D. Hays
Edmonds, WA
K7VE

   


Re: amixer questions Re: Set Up Issues #setup #fldigi #draws

Annaliese McDermond
 

On Dec 13, 2018, at 9:00 PM, Brian Badger <brian@...> wrote:

I am only picking this up by side conversations:

Is this true -- I have been searching the archives and I can't find anything:
CM_L: Common (GND) for the left port
IN1_L: DISCRIMINATOR INPUT (9600) for the left port
IN2_L: AUDIO INPUT (1200) for the left port
CM_R: Common (GND) for the right port
IN1_R: DISCRIMINATOR INPUT (9600) for the right port
IN2_R: AUDIO INPUT (1200) for the right port

If that's not how it works, then how does it work?
That’s exactly how it works. The TLV320AIC3204 has three inputs that can be connected to the ADC. Each input also has an inline resistor that you can select from the mixer. We suggest that you use 10k, because that’s been shown to work in all the situations we’ve tried, but if you need to do some advanced configuration you can use the 20k and 40k values. Please also note that it is a valid configuration for the codec to hook both input 1 and 2 to the ADC at the same time. The signals will merely get mixed. So, if that’s not something you desire, remember to turn off 1 when 2 is in use and vice-versa.

Also read the entire mixer description. There are indeed switches for things like “IN1L to Right Mixer” where you can cross things up.

The “ADC Level” analog control determines the input gain for these. Left and right are separately controllable.

I’d love to be able to pare down these options to be more specific to udrc/draws, but the alsa code doesn’t really allow you to do that very easily.

On the output side, it’s quite a bit simpler. There’s one right and one left output off of the DAC. They are hooked to one of two amplifiers, LO and HP. LO is line out, and HP is headphones. UDRC/Draws only brings out the LO amplifier to pins. There’s an “LO DAC” control that should always be on unless you never intend on transmitting. This hooks the output of the DAC to the LO amplifier. There are then two output controls, one for each of the left and right pin. These are brought out to the output pin on the DIN6.

The trickiness here is that there are two level controls for the output. The first is the PCM control. This controls output from the DAC itself. The thing to note about this control is that it’s a digital control, which means it’s really just multiplying input values to the DAC by a scaling factor. That means that the lower you set it, the less effective bits of the DAC you’re using. This can cause more quantization noise in your output. The other control is the “LO Drive” control. This controls the gain of the LO amplifier. Because of the lack of quantization issues, you would prefer to use this one for the bulk of your setting if possible.

With regards to the “LO Drive” and “PCM” controls, my experience has shown that 0dB on both controls is pretty close to clipping the outputs, so use caution when adjusting them above 0dB.

If you need more output than the defaults can provide, there’s a secret device tree overlay called udrc-boost-output that’s in our repository that you can use to change the power source of the LO amplifier. How to use such is an exercise for the reader since it’s rarely needed.


And what is IN3? A
Unused.

--
Brian N0KZ

--
Annaliese McDermond (NH6Z)
Xenotropic Systems
mcdermj@...


Re: (longer) DRAWS power cable? #draws #power

 

Be careful to get the right polarity, to match the pins on the DRAWS board.  We have seen some with the black and red wires switched from what DRAWS is expecting.

We are looking at some options, so don't overdo it on buying a bunch of pigtails.

BTW, pigtails are meant to be just that, a little solder and shrink tubing and connect it to a longer cable with whatever connector you like on the other end.



On Sat, Dec 15, 2018 at 2:15 PM Robert Sears <kf7vop@...> wrote:

Complete assemblies

https://www.adafruit.com/product/261

https://www.sparkfun.com/products/9914

Robert/KF7VOP

On 12/15/2018 09:53 AM, Gayland Gump wrote:
Does anyone have a source for the power pigtails for the DRAWS?  I'll likely need a few as I learn how to put Anderson Power Pole connectors on the non-terminated end of the pigtail.  The one I got with the DRAWS is already getting too short as I fail my way through to having enough experience and technique to achieve success.

Gayland
KG7GCF


On Thu, Dec 6, 2018 at 10:57 AM Bryan Hoyer <bhhoyer@...> wrote:
Connector is JST XRH Series

> On Dec 6, 2018, at 10:38 AM, Steve Stroh <steve.stroh@...> wrote:
>
> Anyone have a lead on a longer power cable for a DRAWS?
>
> Yes, I know I can splice a longer cable onto the one that's supplied
> with the unit, but I'd rather not.
>
> I'm sure there's something on Amazon, but I don't even know what to
> call that particular connector.
>
> Thanks,
>
> Steve N8GNJ
>
> --
> Steve Stroh (personal / general): stevestroh@...
>
>
>






--


John D. Hays
Edmonds, WA
K7VE

   


Re: Beta Image Available #betaimage #draws

Basil Gunn
 

A new beta image has been posted.
http://nwdig.net/downloads/current_beta.zip

There are some config bring-up notes here:
https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md

There are some testing & verification notes here:
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md

/Basil

John D Hays - K7VE <@john_hays> writes:

A Beta image is available for download at
http://nwdig.net/downloads/draws_beta2.zip

(This location may change.)

Unzip the file which will create draws_beta2.img
Use an SD Card of at least 8 GB and copy the img file with an image burner
like Etcher <https://www.balena.io/etcher/> or dd under Linux.


 

There has been a rapid succession of betas the last couple of days.  We number each successive beta.


We are implementing a 'symbolic link' in the directory

For anyone that is building a pull script and doesn't want to have to go look for the current beta number, just use the  http://nwdig.net/downloads/current_beta.zip link to pull the latest.


--


John D. Hays
Director

  


Re: (longer) DRAWS power cable? #draws #power

Robert Sears
 

On 12/15/2018 09:53 AM, Gayland Gump wrote:
Does anyone have a source for the power pigtails for the DRAWS?  I'll likely need a few as I learn how to put Anderson Power Pole connectors on the non-terminated end of the pigtail.  The one I got with the DRAWS is already getting too short as I fail my way through to having enough experience and technique to achieve success.

Gayland
KG7GCF


On Thu, Dec 6, 2018 at 10:57 AM Bryan Hoyer <bhhoyer@...> wrote:
Connector is JST XRH Series

> On Dec 6, 2018, at 10:38 AM, Steve Stroh <steve.stroh@...> wrote:
>
> Anyone have a lead on a longer power cable for a DRAWS?
>
> Yes, I know I can splice a longer cable onto the one that's supplied
> with the unit, but I'd rather not.
>
> I'm sure there's something on Amazon, but I don't even know what to
> call that particular connector.
>
> Thanks,
>
> Steve N8GNJ
>
> --
> Steve Stroh (personal / general): stevestroh@...
>
>
>





Re: TODO list? Re: #draws #compass #dstar

Basil Gunn
 

@ Basil – which copy of direwolf.conf does your start up script
modify? I am missing the obvious as usual…
Linux configuration by convention lives in /etc or /usr/local/etc
direwolf config is here: /etc/direwolf.conf

With Beta2-

So wsjt and fldigi were a slam-dunk here, they just worked without
mods (I still need to adjust the screen parameters to get wsjt on the
7 inch touch screen)… I used the audio setup that was in audio setup
routine and did not try to use the original audio setup script.
Just my preference:
I found 7 inch screens, even the superior Sunfounder 1024x600 display
are too small to be usable for most of these applications.
I use the 10 inch Sunfounder 1280x800 display.

This was the first time I was able to reliably get a waterfall on any
program!

Basil’s solution for the activation of direwolf worked (and YACC, but
Xastir was still being goofy). When running direwolf as a system
process, there is not an active monitor terminal as is the case when
run directly from commandline or the GUI menu. In my attempt to get it
to work by playing with the .conf file, I messed up something and lost
the GPS. In process of trying to fix that I lost the PTT. Since Beta4
is available, I am just going to flash another image and start up slow
again.
Look here for my notes on bringing up a working Xastir
Note: The gps notes are NOT for the draws board.

https://github.com/nwdigitalradio/n7nix/tree/master/xastir

You can look at direwolf output this way:

tail -f /var/log/direwolf/direwolf.log

draws_beta5.zip is now available.


KD4IZ

Jack Spitznagel


Re: (longer) DRAWS power cable? #draws #power

Robert Sears
 

You can buy the connectors and wires with pre-crimped contacts from Digikey

https://www.digikey.com/en/product-highlight/j/jst/xh-series-connectors


Robert/KF7VOP


On 12/15/2018 09:53 AM, Gayland Gump wrote:
Does anyone have a source for the power pigtails for the DRAWS?  I'll likely need a few as I learn how to put Anderson Power Pole connectors on the non-terminated end of the pigtail.  The one I got with the DRAWS is already getting too short as I fail my way through to having enough experience and technique to achieve success.

Gayland
KG7GCF


On Thu, Dec 6, 2018 at 10:57 AM Bryan Hoyer <bhhoyer@...> wrote:
Connector is JST XRH Series

> On Dec 6, 2018, at 10:38 AM, Steve Stroh <steve.stroh@...> wrote:
>
> Anyone have a lead on a longer power cable for a DRAWS?
>
> Yes, I know I can splice a longer cable onto the one that's supplied
> with the unit, but I'd rather not.
>
> I'm sure there's something on Amazon, but I don't even know what to
> call that particular connector.
>
> Thanks,
>
> Steve N8GNJ
>
> --
> Steve Stroh (personal / general): stevestroh@...
>
>
>





Re: TODO list? Re: #draws #compass #dstar

Jack Spitznagel
 

Brian, Basil, All,

 

@ Basil – which copy of direwolf.conf does your start up script modify? I am missing the obvious as usual…

 

With Beta2-

So wsjt and fldigi were a slam-dunk here, they just worked without mods (I still need to adjust the screen parameters to get wsjt on the 7 inch touch screen)… I used the audio setup that was in audio setup routine and did not try to use the original audio setup script.

 

This was the first time I was able to reliably get a waterfall on any program!

 

Basil’s solution for the activation of direwolf worked (and YACC, but Xastir was still being goofy). When running direwolf as a system process, there is not an active monitor terminal as is the case when run directly from commandline or the GUI menu. In my attempt to get it to work by playing with the .conf file, I messed up something and lost the GPS. In process of trying to fix that I lost the PTT.  Since Beta4 is available, I am just going to flash another image and start up slow again.

 

KD4IZ

Jack Spitznagel

FM19oo

 

 

 

 

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Brian Badger
Sent: Saturday, December 15, 2018 14:40
To: udrc@nw-digital-radio.groups.io
Subject: [udrc] TODO list? Re: #draws #compass #dstar

 

I have no urgent needs for anything DRAWS related.  I know I'm an early adopter -- I get it.  But it would be really helpful if there was some kind of TODO list so I know what I should even be messing with. 

1) Direwolf, YAAC, XASTIR, gpsd, chronyd - working
2) fldigi - working, but amixer settings not documented?
3) virtual audio devices - not working?
4) dstarrepeater - not working?

Regarding #2, I didn't understand the comments about "AUDIOOUT" "DISCOUT" -- the comments don't appear to match the mixer settings.  From the schematics it looks like IN1 is the DISCOUT and IN2 is the AUDIOOUT.  I changed the amixer settings script thus to enable fldigi: 

# Set channel 0 

sset 'CM_L to Left Mixer Negative Resistor' '10 kOhm'

sset 'IN1_L to Left Mixer Positive Resistor' 'Off'

sset 'IN2_L to Left Mixer Positive Resistor' '10 kOhm'

# Set channel 1

sset 'CM_R to Right Mixer Negative Resistor' '10 kOhm'

sset 'IN1_R to Right Mixer Positive Resistor' 'Off'

sset 'IN2_R to Right Mixer Positive Resistor' '10 kOhm'

 


--
J Spitznagel
Science River LLC
KD4IZ


Re: TODO list? Re: #draws #compass #dstar

 



On Sat, Dec 15, 2018 at 11:39 AM Brian Badger <brian@...> wrote:
I have no urgent needs for anything DRAWS related.  I know I'm an early adopter -- I get it.  But it would be really helpful if there was some kind of TODO list so I know what I should even be messing with. 

1) Direwolf, YAAC, XASTIR, gpsd, chronyd - working
2) fldigi - working, but amixer settings not documented?
alsamixer settings are generally by radio, not application.  Once they are set for a radio, you can move from program to program.  [Not all radios are equal, and not all radios have been tested.]
 
3) virtual audio devices - not working?

Virtual audio devices work, as far as the OS is concerned.  Most applications don't enumerate them, and there is a small change in application code to make them work properly for non-streaming applications.

 
4) dstarrepeater - not working?
I haven't had a chance to test out yet, but it should be able to work -- just may take a different approach than the UDRC configuration as it was primarily focused on the UDRC/UDRC II and doesn't recognize the EPROM setting for the DRAWS yet.


John D. Hays
Edmonds, WA
K7VE

   


Re: Beta Image Available #betaimage #draws

 

Looks good, btw, if you do

chronyc sources -v 

It has a legend for the meaning of the various values.


On Sat, Dec 15, 2018 at 12:21 PM David [kg5eiu] via Groups.Io <dcappello=aol.com@groups.io> wrote:
Downloaded the beta 4 image today (dec 15, 2018) setup the pi and OS
location, enabled VNC and followed 
the beginning of this thread for setup/config working good - next to
get a radio hooked up.

--


John D. Hays
Edmonds, WA
K7VE

   


Re: Beta Image Available #betaimage #draws

David [kg5eiu]
 

Downloaded the beta 4 image today (dec 15, 2018) setup the pi and OS
location, enabled VNC and followed 
the beginning of this thread for setup/config working good - next to
get a radio hooked up.


TODO list? Re: #draws #compass #dstar

Brian Badger
 

I have no urgent needs for anything DRAWS related.  I know I'm an early adopter -- I get it.  But it would be really helpful if there was some kind of TODO list so I know what I should even be messing with. 

1) Direwolf, YAAC, XASTIR, gpsd, chronyd - working
2) fldigi - working, but amixer settings not documented?
3) virtual audio devices - not working?
4) dstarrepeater - not working?

Regarding #2, I didn't understand the comments about "AUDIOOUT" "DISCOUT" -- the comments don't appear to match the mixer settings.  From the schematics it looks like IN1 is the DISCOUT and IN2 is the AUDIOOUT.  I changed the amixer settings script thus to enable fldigi: 

# Set channel 0 
sset 'CM_L to Left Mixer Negative Resistor' '10 kOhm'
sset 'IN1_L to Left Mixer Positive Resistor' 'Off'
sset 'IN2_L to Left Mixer Positive Resistor' '10 kOhm'
# Set channel 1
sset 'CM_R to Right Mixer Negative Resistor' '10 kOhm'
sset 'IN1_R to Right Mixer Positive Resistor' 'Off'
sset 'IN2_R to Right Mixer Positive Resistor' '10 kOhm'
 


Re: #draws #compass #dstar #dstar #draws #compass

 

Hold off unless you have an urgent need Anna is working on something. 


On Sat, Dec 15, 2018, 11:13 Brian Badger <brian@... wrote:
Before I debug any further, is DRAWS supported as a dstarrepeater controller yet?

12:08:38: Opened hw:1,0 hw:1,0 Rate 48000
12:08:38: Error: UDRCController: Unknown product Detected
12:08:38: Error: Unknown NW Digital Radio Product
12:08:38: Error: Cannot open the hardware interface - UDRC
12:08:38: Starting ALSA writer thread
12:08:38: Starting ALSA reader thread
12:08:38: Starting Sound Card Controller thread

--
Brian N0KZ