Date   

Re: HDMI issue with Draws

W8GMC
 

Thank you Basil, 

You are correct this is not a DRAWS issue and appears to an NDDR image problem which i can not find resolution for. I have created a fresh boot image utilizing the original config.txt and confirmed   'hdmi_force_hotplug=1' & 'hdmi_drive=2' are commented out. Tthe problem still remains, one monitor or the other, not both. Perhaps i have posted this to the wrong group and if so I apologize. 

Thank you,
Mike


DRAWS™ Cases are Shipping to Customers!

 


All materials are in house now, and the first DRAWS Aluminum Cases will ship tomorrow.

Shipments will start with our Early Adopters. If you ordered an Early Adopter Case, make sure that is correct for your DRAWS HAT:

http://nwdigitalradio.com/draws-cases-have-shipped/

We anticipate having all of the case orders resolved by the end of the month, at which time we will focus on our TurnKey backorders.

It's been a long and arduous task, and we appreciate your patience. We will be publishing an assembly video this week.

--


John D. Hays
Director

  


Re: HDMI issue with Draws

Basil Gunn
 

To be clear this thread has nothing to do with DRAWS but is a problem
with a customized /boot/config.txt file from an NWDR image.

I am guessing that if you booted a fresh NWDR image your problem would
be fixed.

In the config.txt file you supplied you have 'hdmi_drive=2' uncommented in
3 places which forces HDMI. This is probably causing the symptom you are
seeing.

In your previous post you say that the HamPi image works. Note that a
stock Buster image, the HamPi image and the current NWDR image all have
the HDMI options 'hdmi_force_hotplug=1' & 'hdmi_dirve=2' commented out.

You should edit /boot/config.txt so that you only have one instance of
each of those parameter lines and make sure that they are commented out.


kc8fws <Michael_MSN@MSN.COM> writes:

Hi Basil,

Yes, you summarized the issue correctly. Here is the output as requested.

Config.txt...
# For more options and information see


Re: HDMI issue with Draws

Kevin K. - N7KJK
 

Hi,
I was searching on the DSI port and came across this.  It may require additional software to do what you are attempting.


Hope this helps.
Kevin


Re: HDMI issue with Draws

W8GMC
 

Hi Basil, 

Yes, you summarized the issue correctly. Here is the output as requested. 

Config.txt...
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details
# Always force HDMI output and enable HDMI sound
hdmi_force_hotplug=1
hdmi_drive=2
 
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=2
 
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1
 
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
 
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
 
# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1
 
# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1
 
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2
 
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
config_hdmi_boost=4
 
# uncomment for composite PAL
#sdtv_mode=2
 
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
 
# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
 
# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18
 
# Additional overlays and parameters are documented /boot/overlays/README
 
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
 
[all]
#dtoverlay=vc4-fkms-v3d
 
# Flush all overlays, ie. deprecated overlays loaded from eeprom
dtoverlay=
# enable udrc/draws if no eeprom
dtoverlay=draws,alsaname=udrc
force_turbo=1
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
#hdmi_group=2
#hdmi_mode=85
#hdmi_safe=1
#Always force HDMI output and enable HDMI sound
hdmi_force_hotplug=1
hdmi_drive=2


Here is the output from head -n1 /var/log/udr_install.log....
2020 12 04 13:45:55 PST: SD image version: nwdr18
 
and udr_install.log....

2019 09 19 14:30:00 PDT: install.sh: draws-manager install script FINISHED
2019 09 19 15:00:47 PDT: xs_install.sh: Xastir install script FINISHED
2020 01 06 12:54:56 PST: gp_install.sh: gps install script FINISHED
2020 01 06 12:54:57 PST: gp_verchk.sh: gpsd program update script FINISHED
2020 01 06 13:16:35 PST: hf_install.sh: HF program (js8call) install script FINISHED
2020 01 06 13:16:53 PST: hf_install.sh: HF program (wsjtx) install script FINISHED
2020 01 06 13:18:19 PST: hf_install.sh: HF program (fllog) install script FINISHED
2020 01 06 13:18:20 PST: hf_verchk.sh: hf program update script FINISHED
2020 01 06 13:34:28 PST: xs_install.sh: Xastir install script FINISHED
2020 01 08 13:08:49 PST: install.sh: YAAC install script FINISHED
2020 01 19 08:40:32 PST: hf_install.sh: HF program (fldigi) install script FINISHED
2020 01 19 08:49:52 PST: hf_install.sh: HF program (flrig) install script FINISHED
2020 01 19 08:49:54 PST: hf_verchk.sh: hf program update script FINISHED
2020 01 19 11:32:37 PST: install.sh: fbb BBS install script FINISHED
2020 05 11 09:31:46 PDT: xs_install.sh: Xastir install script FINISHED
2020 05 11 09:31:46 PDT: xs_verchk.sh: Xastir program update script FINISHED
2020 05 11 09:45:03 PDT: hf_install.sh: HF program (fldigi) install script FINISHED
2020 05 11 09:49:23 PDT: hf_install.sh: HF program (flrig) install script FINISHED
2020 05 11 09:49:23 PDT: hf_verchk.sh: hf program update script FINISHED
2020 05 11 10:07:24 PDT: dw_update.sh: direwolf update script FINISHED
2020 06 08 10:18:55 PDT: hf_install.sh: HF program (wsjtx) install script FINISHED
2020 06 08 10:28:58 PDT: hf_install.sh: HF program (fldigi) install script FINISHED
2020 06 08 10:31:41 PDT: hf_install.sh: HF program (flmsg) install script FINISHED
2020 06 08 10:31:42 PDT: hf_verchk.sh: hf program update script FINISHED
2020 07 17 13:59:05 PDT: hf_install.sh: HF program (js8call) install script FINISHED
2020 07 17 13:59:16 PDT: hf_install.sh: HF program (wsjtx) install script FINISHED
2020 07 17 14:09:09 PDT: hf_install.sh: HF program (fldigi) install script FINISHED
2020 07 17 14:13:43 PDT: hf_install.sh: HF program (flrig) install script FINISHED
2020 07 17 14:16:38 PDT: hf_install.sh: HF program (flmsg) install script FINISHED
2020 07 17 14:16:49 PDT: hf_verchk.sh: hf program update script FINISHED
2020 07 17 21:50:22 PDT: dw_update.sh: direwolf update script FINISHED
2020 08 21 09:20:21 PDT: gp_install.sh: gps install script FINISHED
2020 08 21 09:20:22 PDT: gp_verchk.sh: gpsd program update script FINISHED
2020 09 18 09:48:43 PDT: hf_install.sh: HF program (flmsg) install script FINISHED
2020 09 18 09:48:43 PDT: hf_verchk.sh: hf program update script FINISHED
2020 11 04 12:21:02 PST: bbs_install.sh: fbb BBS install script FINISHED
2020 11 04 12:33:46 PST: hf_install.sh: HF program (fldigi) install script FINISHED
2020 11 04 12:38:37 PST: hf_install.sh: HF program (flrig) install script FINISHED
2020 11 04 12:38:37 PST: hf_verchk.sh: hf program update script FINISHED
2020 11 04 12:43:39 PST: dw_update.sh: direwolf update script FINISHED
2020 11 10 08:46:46 PST: install.sh: RMS Gateway updated
2020 11 27 10:11:24 PST: hf_install.sh: HF program (fldigi) install script FINISHED
2020 11 27 10:11:26 PST: hf_verchk.sh: hf program update script FINISHED
2020 12 04 13:32:10 PST: hf_install.sh: HF program (fldigi) install script FINISHED
2020 12 04 13:36:36 PST: hf_install.sh: HF program (flrig) install script FINISHED
2020 12 04 13:36:37 PST: hf_verchk.sh: hf program update script FINISHED
2021 01 16 13:08:45 EST: app_config.sh: core config script FINISHED
2021 01 16 13:08:56 EST: app_config.sh: AX.25 config script FINISHED
2021 01 16 13:08:56 EST: app_config.sh: direwolf config script FINISHED
2021 01 16 13:08:57 EST: install.sh: systemd install script FINISHED
2021 01 16 13:08:58 EST: config.sh: systemd config script FINISHED
2021 01 16 13:08:59 EST: iptable_install.sh: iptables installed but NOT configured, no AX.25 devices available
2021 01 16 13:11:04 EST: app_config.sh: app config (core) script FINISHED
2021 01 16 13:18:43 EST: app_config.sh: RMS Gateway config script FINISHED
2021 01 16 13:18:43 EST: app_config.sh: app config (rmsgw) script FINISHED
2021 01 16 13:19:16 EST: app_config.sh: paclink-unix basic config FINISHED
2021 01 16 13:19:20 EST: app_config.sh: postfix config script FINISHED
2021 01 16 13:19:29 EST: app_config.sh: mutt config script FINISHED
2021 01 16 13:21:08 EST: pluweb_install.sh: script FINISHED
2021 01 16 13:23:08 EST: app_config.sh: dovecot config FINISHED
2021 01 16 13:25:46 EST: app_config.sh: rainloop install script FINISHED
2021 01 16 13:26:29 EST: app_config.sh: app config (plu) script FINISHED

Thank you,
Mike


Re: HDMI issue with Draws

W8GMC
 

Yes that summarizes it perfectly. 

Mike


Re: HDMI issue with Draws

Basil Gunn
 

Trying to understand your question.

You have a 7" screen attached to RPi DSI port and another monitor
attached to the HDMI port & they do not work together. If you remove
power to the device on the DSI port then the HDMI device works.
Both screens work with the HamPi image.

Is this a correct statement of the problem?

Send me the /boot/config.txt file from your HamPi image and your NWDR
image.
Which NWDR image are you using?
Show me the console output of:
head -n1 /var/log/udr_install.log


kc8fws <Michael_MSN@MSN.COM> writes:

Hi All,

I have a bit of an issue a cant seem to solve. Im running the DRAWS on
a Pi 4 8gig. Everything seems to be working as expected so far. (Have
YACC up and running, maps imported and receiving as expected from an
FT-817nd). I have the unit mounted in a SmartiPI case with the 7”
touch screen. My issue is that if I provide power to the touch screen
I get no output to either HDMI port. Port 1 does briefly show boot
text upon startup for less than a second then goes to the rainbow
screen. Then the 7” is loaded as the only monitor. If I pull power
from the 7” touchscreen the HDMI ports work fine. Just not in
conjunction. I have made all the recommended HDMI modifications to
config.txt to no avail. I have verified the set up works with my HamPi
build perfectly. I even booted without the draws hat installed and the
issue remains. Any ideas would be greatly appreciated. I don’t believe
it to be a power supply issue as I have a 5 amp PS and also tried with
powering the 7in from a separate PS than the one powering the PI. I
have not tried powering through the Draws onboard 12V but as I said
the same issue remains even without the DRAWS installed. This is using
the NW Digital Draws build….


HDMI issue with Draws

W8GMC
 

Hi All,

 

I have a bit of an issue a cant seem to solve. Im running the DRAWS on a Pi 4 8gig. Everything seems to be working as expected so far. (Have YACC up and running, maps imported and receiving as expected from an FT-817nd). I have the unit mounted in a SmartiPI case with the 7” touch screen. My issue is that if I provide power to the touch screen I get no output to either HDMI port. Port 1 does briefly show boot text upon startup for less than a second then goes to the rainbow screen. Then the 7” is loaded as the only monitor. If I pull power from the 7” touchscreen the HDMI ports work fine. Just not in conjunction.  I have made all the recommended HDMI modifications to config.txt to no avail. I have verified the set up works with my HamPi build perfectly. I even booted without the draws hat installed and the issue remains. Any ideas would be greatly appreciated. I don’t believe it to be a power supply issue as I have a  5 amp PS and also tried with powering the 7in from a separate PS than the one powering the PI. I have not tried powering through the Draws onboard 12V but as I said the same issue remains even without the DRAWS installed. This is using the NW Digital Draws build….

 

Thank you in advance,

Mike

W8GMC (Previously KC8FWS)

 

Sent from Mail for Windows 10

 


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

 

 

 

341 - 360 of 5683