Date   

Re: [New post] DRAWS™ Cases Have Shipped!

 

The Barrel Connector was incorporated into the latest Boards. There is a PowerPole to 2.1mm DC Coax Cable available from Powerwerx

If you have an earlier board you can terminate the supplied JST XH Pigtail to anything you like, wether it’s coax, PowerPole, or whatever works for your application. Of course most of you have already done this.

These pigtails are available from Pololu and others if you need another one.

MAKE SURE TO CHECK POLARITY! as they are not all the same. RED on RIGHT

Best Practice is to Fuse the power link at the source 1-2.5A

Bryan K7UDR


Re: [New post] DRAWS™ Cases Have Shipped!

okiejim
 

May I ask about the power connections. On the original case you said you were including a barrel connector for power. I still the case with the newer cases?


Re: [New post] DRAWS™ Cases Have Shipped!

 

Yes, the cases work with Pi3 or 4, here’s pics:



On Jan 11, 2021, at 4:41 PM, Kevin JJ1PJI <kajiki@...> wrote:

Great News. Will the the "early adopter" case work with the PI 4? The website photos are not displaying with an image of the case.  Looking forward to receiving it. Ordered it back when I running it on Pi 3.  Thank you.   JJ1PJI Kevin
<5C32A980-3336-4861-834E-DF61C62542DF.png>


Re: [New post] DRAWS™ Cases Have Shipped!

Kevin JJ1PJI
 

Great News. Will the the "early adopter" case work with the PI 4? The website photos are not displaying with an image of the case.  Looking forward to receiving it. Ordered it back when I running it on Pi 3.  Thank you.   JJ1PJI Kevin


[New post] DRAWS™ Cases Have Shipped!

 
Edited

 
k7udr posted: "DRAWS™ cases have shipped from the manufacturer and we will start shipping once they arrive! 
 

New post on NW Digital Radio

 

DRAWS™ Cases Have Shipped!

by k7udr

DRAWS™ cases have shipped from the manufacturer and we will start shipping once they arrive!

Important: Make sure you have ordered the correct case for your DRAWS™ HAT!

Please review your case order.
If your DRAWS™ HAT looks like this (SMA to left of DIN-6 connectors), Order the "early adopter" case

If it looks like one of these (SMA on the narrow side of board), you need the "production" case. If you ordered an "early adopter" case, please enter an upgrade order to get the correct case.

 

Trouble clicking? Copy and paste this URL into your browser:
http://nwdigitalradio.com/draws-cases-have-shipped/

 
 



Re: Interested in buying the DRAWS kit from NW digital -- when will it be back in stock?

 

Interested in buying the DRAWS kit from NW digital --
Sounds like a good application for some of the economic impact stimulus funds...

Bill


Interested in buying the DRAWS kit from NW digital -- when will it be back in stock?

NIcholas Caruso
 

Interested in buying the DRAWS kit from NW digital -- when will it be
back in stock?


new membership and NW DRAWS with Codan NGT and/or 9360

Tino HB9DUW
 

Hello from Switzerland (HB9DUW, op. Tino) and happy new year!

Thank you for letting me in.

I became aware of DRAWS HAT only recently and find it a good option
for my project :

Setting up remote HF ARDOP station on a Raspberry and Codan NGT SR(x) and/or 9360.

Does someone know the NW DRAWS pinout for these particular TXs?

I'd like also please to get some of your experiences in choosing the
best "clothing" for Pi3/4, considering this remote setup with 12v
solar pannels, regulator (about 19v to 12v battery) and a fan to
extract heat and/or humidity from a "sealed box".---> Waiting for the new NW aluminium case 

HF destroyed one of my first solar regulator but a 30ish USD Amazon
unit seems to be less sensible. Where shall I place ferrites (or other
protections) ?


Any hints welcome.



73 frm HB9DUW


Re: #support Low transmit audio #support

@K5LVL
 

Thanks John!  I'll shoot an email over.


Kyle


Re: #support Low transmit audio #support

 

Contact sales@... for defective hat support. (Closed until next week.)

On Thu, Dec 31, 2020 at 11:44 AM <kylemcdonald87@...> wrote:

What would be the process if I do have a defective DRAWS hat?  It's had this issue from the start and I did get frustrated with it and gave up.  Just decided to pick it back up and give it another shot.

Kylw

_._,_._,_



--
John D. Hays
Kingston, WA
K7VE

 


Re: #support Low transmit audio #support

@K5LVL
 
Edited

Hey Basil,

Thanks for replying.  That is the 6-pin MiniDIN adapter that I have.. I even tried my spare with no success.  It's had this issue from the start and I did get frustrated with it and gave up.  Just decided to pick it back up and give it another shot.
I've only ever had it out in the open without a fan.  It does have the heat sinks on it as well.  Luckily I've been on the list for a case which as a built in fan so hopefully that will work after the fact.

What would be the process if I do have a defective DRAWS hat?  It's had this issue from the start and I did get frustrated with it and gave up.  Just decided to pick it back up and give it another shot.

Kyle


Re: NWDR18 image release announcement

Jack Spitznagel
 

Thank you John! This is a very helpful hint. – Jack KD4IZ

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of John D Hays - K7VE
Sent: Thursday, December 31, 2020 12:40
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] NWDR18 image release announcement

 

With a little digging you can find the unique identifier for the plugged in CT-62 cable and create a udev description to give it a name that remains consistent between plug-in instances.

An example for the ThumbDV™ is found at 
https://github.com/nwdigitalradio/ambeserver-install/blob/master/etc/udev/rules.d/99-thumbdv.rules

It makes link at /dev/ThumbDV regardless of which ttyUSB# the device is plugged into.

Also doing a ls /dev/serial/by-id will provide a direct path to the plugged in USB serial device.

 

On Thu, Dec 31, 2020 at 9:20 AM Basil Gunn <basil@...> wrote:


Re-stating your problem to see if I have it right:

CAT control is not working between an RPi 4 and and a Yaesu FT-100D
which is a multiband HF/VHF/UHF radio.
Connection is through a Yaesu CT-62 cable which is an 8 pin mDin to
USB serial device connection.

This has nothing to do with the DRAWS hat!

The most common problem is finding the correct Linux serial device name
for FLdigi/FLrig.

# With the CT-62 disconnected from the RPi find all current USB serial
device names:

  ls /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory

# In my case their are NO USB serial devices plugged into the RPi.
# Now plug your CT-62 cable into your RPi and execute 'ls' to find the
# name of the serial device.

  ls /dev/ttyU*
/dev/ttyUSB0

# In this case the USB serial device name is /dev/ttyUSB0
# This is the device name to use in your FLdigi/FLrig configuration for
# CAT control.

Note if you unplug/plug your CT-62 cable in your RPi while it is running the
device name will change.

Eric Williams <kf4yep@...> writes:

> Thanks Basil for the rapid response,
>
> That's good to know. So, how do I get the frequencies to show up in
> the display and/or flrig? The cat cable is CT-62 with USB end. No
> serial-to-usb converters in the middle.





 

--

John D. Hays
Kingston, WA

K7VE

 

 

 


Re: NWDR18 image release announcement

 

With a little digging you can find the unique identifier for the plugged in CT-62 cable and create a udev description to give it a name that remains consistent between plug-in instances.

An example for the ThumbDV™ is found at 
https://github.com/nwdigitalradio/ambeserver-install/blob/master/etc/udev/rules.d/99-thumbdv.rules
It makes link at /dev/ThumbDV regardless of which ttyUSB# the device is plugged into.

Also doing a ls /dev/serial/by-id will provide a direct path to the plugged in USB serial device.

On Thu, Dec 31, 2020 at 9:20 AM Basil Gunn <basil@...> wrote:

Re-stating your problem to see if I have it right:

CAT control is not working between an RPi 4 and and a Yaesu FT-100D
which is a multiband HF/VHF/UHF radio.
Connection is through a Yaesu CT-62 cable which is an 8 pin mDin to
USB serial device connection.

This has nothing to do with the DRAWS hat!

The most common problem is finding the correct Linux serial device name
for FLdigi/FLrig.

# With the CT-62 disconnected from the RPi find all current USB serial
device names:

  ls /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory

# In my case their are NO USB serial devices plugged into the RPi.
# Now plug your CT-62 cable into your RPi and execute 'ls' to find the
# name of the serial device.

  ls /dev/ttyU*
/dev/ttyUSB0

# In this case the USB serial device name is /dev/ttyUSB0
# This is the device name to use in your FLdigi/FLrig configuration for
# CAT control.

Note if you unplug/plug your CT-62 cable in your RPi while it is running the
device name will change.

Eric Williams <kf4yep@...> writes:

> Thanks Basil for the rapid response,
>
> That's good to know. So, how do I get the frequencies to show up in
> the display and/or flrig? The cat cable is CT-62 with USB end. No
> serial-to-usb converters in the middle.







--
John D. Hays
Kingston, WA
K7VE

 


Re: NWDR18 image release announcement

Basil Gunn
 

Re-stating your problem to see if I have it right:

CAT control is not working between an RPi 4 and and a Yaesu FT-100D
which is a multiband HF/VHF/UHF radio.
Connection is through a Yaesu CT-62 cable which is an 8 pin mDin to
USB serial device connection.

This has nothing to do with the DRAWS hat!

The most common problem is finding the correct Linux serial device name
for FLdigi/FLrig.

# With the CT-62 disconnected from the RPi find all current USB serial
device names:

ls /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory

# In my case their are NO USB serial devices plugged into the RPi.
# Now plug your CT-62 cable into your RPi and execute 'ls' to find the
# name of the serial device.

ls /dev/ttyU*
/dev/ttyUSB0

# In this case the USB serial device name is /dev/ttyUSB0
# This is the device name to use in your FLdigi/FLrig configuration for
# CAT control.

Note if you unplug/plug your CT-62 cable in your RPi while it is running the
device name will change.

Eric Williams <kf4yep@gmail.com> writes:

Thanks Basil for the rapid response,

That's good to know. So, how do I get the frequencies to show up in
the display and/or flrig? The cat cable is CT-62 with USB end. No
serial-to-usb converters in the middle.


Re: NWDR18 image release announcement

Eric Williams
 

Thanks Basil for the rapid response,

That's good to know.  So, how do I get the frequencies to show up in the display and/or flrig?  The cat cable is CT-62 with USB end.  No serial-to-usb converters in the middle.


Re: NWDR18 image release announcement

Basil Gunn
 

Eric,

Placing A Hold On Kernel Upgrade
* FOR REFERENCE ONLY, the current Linux kernel is safe to use with
DRAWS
You do NOT need to place a hold on kernel upgrade. That procedure was to
fix a problem that affected the DRAWS overlay last summer.

I will take this reference out of the 'Getting Started Guide' later on
today because that section was "For reference only, the current Linux
kernel is safe to use with DRAWS"

The drivers in the current kernel, 5.4.79-v7l+ #1373, works fine with DRAWS.

kf4yep@gmail.com writes:

Hi team,
I've been having issues with the Draws hat and it is installed on a Pi4. I first tried getting it to work on KM4ACKs Build-a-Pi (Ham experimentation right?). Then I formatted my sd card and followed the getting started guide https://nw-digital-radio.groups.io/g/udrc/wiki/8921 for image nwdr18.img.xz ( http://nwdig.net/downloads/nwdr18.img.xz ) 2020-Dec-05 08:36:33 1.8G and got as far as the fldigi configuration. ax.25/direwolf appeared to work and sent/received appropriately. fldigi keys the radio (yaesu FT-100d attached currently to 1 watt to dummy load) but it appears my cat cable is not reading or setting the radio frequency so I also tried fiddling with flrig to no avail. I stopped here. Reading further:
--------------------------------

* For reference only, the current Linux kernel is safe to use with DRAWS
*

To verify your current kernel version

uname - r
*

You should see: 4.19.118-v7l+

*

If you see : 5.4.51-v7l+ then your DRAWS hat will have problems

* The driver for the TI ads1015 chip is missing in this kernel.
*

To revert your kernel back to 4.19.118 run the following (courtesy of Thomas KF7RSF):

sudo rpi - upgrade e1050e94821a70b2e4c72b318d6c6c968552e9a2

*

Do NOT use the following commands:

* apt-get dist-upgrade
* apt full-upgrade

What I saw was not kernel 4.19....
and n7nix's verify_config guide 'sensors' fails to show
ads1015-i2c-1-48
so I try

*

* sudo rpi - upgrade e1050e94821a70b2e4c72b318d6c6c968552e9a2

and get sudo: rpi-upgrade: command not found

I formatted (again) and haven't connected to network or configured anything.
First check of uname -r gives me 5.4.79-v7l+

Help, please and thank you!
Eric Williams de KF4YEP



Re: NWDR18 image release announcement

Eric Williams
 

Hi team,
I've been having issues with the Draws hat and it is installed on a Pi4.  I first tried getting it to work on KM4ACKs Build-a-Pi (Ham experimentation right?). Then I formatted my sd card and followed the getting started guide https://nw-digital-radio.groups.io/g/udrc/wiki/8921 for image nwdr18.img.xz 2020-Dec-05 08:36:33 1.8G and got as far as the fldigi configuration.  ax.25/direwolf appeared to work and sent/received appropriately.  fldigi keys the radio (yaesu FT-100d attached currently to 1 watt to dummy load) but it appears my cat cable is not reading or setting the radio frequency so I also tried fiddling with flrig to no avail.  I stopped here.  Reading further: 

Placing A Hold On Kernel Upgrade

  • For reference only, the current Linux kernel is safe to use with DRAWS
  • To verify your current kernel version

    uname -r
  • You should see: 4.19.118-v7l+

  • If you see : 5.4.51-v7l+ then your DRAWS hat will have problems

    • The driver for the TI ads1015 chip is missing in this kernel.
    • To revert your kernel back to 4.19.118 run the following (courtesy of Thomas KF7RSF):

      sudo rpi-upgrade e1050e94821a70b2e4c72b318d6c6c968552e9a2
  • Do NOT use the following commands:

    • apt-get dist-upgrade
    • apt full-upgrade
What I saw was not kernel 4.19.... 
and n7nix's verify_config guide 'sensors' fails to show
 ads1015-i2c-1-48
so I try
    • sudo rpi-upgrade e1050e94821a70b2e4c72b318d6c6c968552e9a2
and get sudo: rpi-upgrade: command not found

I formatted (again) and haven't connected to network or configured anything.
First check of uname -r gives me 5.4.79-v7l+

Help, please and thank you!
Eric Williams de KF4YEP


Re: #support Low transmit audio #support

Basil Gunn
 

Use deviation guide here:
https://github.com/nwdigitalradio/n7nix/tree/master/deviation

Running measure_deviate.sh will allow you to output a tone so that you
can use alsamixer to change the 'Lo Drive' & 'PCM' alsa controls.

I used the Argent Data 6-pin MiniDIN adapter for the Moto CDM 1250
https://www.argentdata.com/catalog/product_info.php?products_id=169
You have to be careful how you plug that into CDM 1250

It looks like you are using the right hand mDin 6 connector. Channel 0
is the left hand mDin6 connector which is the default connector for
using scripts to set up packet.

If you can't get enough volume using the measure_deviate.sh script you
may have a defective DRAWS hat.

The soft temperature limit bit is set in the get_throttled register.
The current temperature, 59C, is fine but at some time your RPi over
heated.

kylemcdonald87@gmail.com writes:

First off thanks for creating such a versatile board!

I've ran through the setup a few times and I'm still having the same
low transmit audio problem. I've tried it with 2 radios (FTM-400 &
Motorola CDM1250). I have to have my HT turned up all the way and I
can still barely hear the data bursts. I've tried adjusting through
Manager as well as alsa from ssh and I'm not able to get much change.

Here is the output from my showudrc.sh: https://pastebin.com/raw/krbtCAm8



#support Low transmit audio #support

@K5LVL
 

First off thanks for creating such a versatile board!

I've ran through the setup a few times and I'm still having the same low transmit audio problem.  I've tried it with 2 radios (FTM-400 & Motorola CDM1250).  I have to have my HT turned up all the way and I can still barely hear the data bursts.  I've tried adjusting through Manager as well as alsa from ssh and I'm not able to get much change.

Here is the output from my showudrc.sh:  https://pastebin.com/raw/krbtCAm8


Re: DRAWS™ Cases have moved to production!

 

We will announce ship dates on the blog and the groups.io site

1 - 20 of 5335