Date   

Re: Audio setup problem with Raspberry PI and DRAWS hat. #ft-817 #audio #drawsmanager #draws-manager #wsjt-x

jakob@...
 

Hi Basil,
Here is what I did so far:
1. I downloaded the file HamPi_v1.2a.img.xz on 1/21 
2. I extracted it and got a folder with the file HamPi_v1.2a.img
3. I formatted a brand new 64 GB Micro SD with SDCardFormatter5
4. I burned the image to the micro SD with balenaEtcher
5. I plugged the MicroSD into a 4GB RaspBerry P4 that has the DRAWS hat installed with a 6-pin cable to the FT-818. Pin 6 is open. There is also a CAT cable between the RaspBerry USB and the FT-818
6. I booted up the RaspBerry. A screen with the HamPi by W3DJS picture appeared and the pull-down menu shows  the item Hamradio with all the programs.
7. I opened the document Activating your DRAWS and followed the instructions.
8. I re-booted the RaspBerry 
9. I followed instructions from the web to run the DRAWS-Manager web app and set both channels to the recommended values for the pin 5 data and saved the settings.
10. I ran the FlRig program that comes with the image and set up the Rig as FT-857D and the proper serial interface settings and CAT-PTT. It connected correctly.
11. I ran the FlDigi program, set the mode to PSK31. I do not see any noise at all. I am very familiar with FlDigi and several modes, since I used it for years.
12. I checked the pin 5 of the cable and see audio signal from the receiver.
13. I click on Tune in FlDigi. The transmitter gets active on the FT-818, but with no output power. Pin 1 of the cable has no useful signal.

There is where I am now.
Questions:
1. Is it the proper NWDR image I use? Is there another one you suggest?
2. Should the steps I used above lead to a correct installation? Did I miss something?
3. If you want you can remote zoom into my Windows 10 computer that has a VNC client connected to the RaspBerry.

I was under the impression that I run the proper NWDR image so far, and I would really appreciate your help.
73 de Jakob


Re: Audio setup problem with Raspberry PI and DRAWS hat. #ft-817 #audio #drawsmanager #draws-manager #wsjt-x

Basil Gunn
 

Below is what you will get if you do NOT use the NWDR image and follow
the 'Getting Started' guide.

pi@hampi:~ $ udrcver.sh
bash: udrcver.sh: command not found
pi@hampi:~ $ showudrc.sh
bash: showudrc.sh: command not found

This is what I asked you to do:

USING THE NWDR IMAGE post the console output from the following
commands:
aplay -l
udrcver.sh
showudrc.sh

wsjt-x & fldigi are both installed on the NWDR image. Get that working
first.

If you have problems with DRAWS or are a Linux noob you must use the
NWDR image if you want my support.

jakob@scherer.com writes:

Basil, here is what I got:
pi@hampi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
pi@hampi:~ $ udrcver.sh
bash: udrcver.sh: command not found
pi@hampi:~ $ showudrc.sh
bash: showudrc.sh: command not found
pi@hampi:~ $
73 Jakob


Re: Audio setup problem with Raspberry PI and DRAWS hat. #ft-817 #audio #drawsmanager #draws-manager #wsjt-x

jakob@...
 

Basil, here is what I got:
pi@hampi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
pi@hampi:~ $ udrcver.sh
bash: udrcver.sh: command not found
pi@hampi:~ $ showudrc.sh
bash: showudrc.sh: command not found
pi@hampi:~ $ 
73 Jakob


Re: Audio setup problem with Raspberry PI and DRAWS hat. #ft-817 #audio #drawsmanager #draws-manager #wsjt-x

Basil Gunn
 

I installed the HamPi 1.2 on a Raspberry 4B 4GB and a DRAWS hat
installed.
Until you have a successful setup use the NWDR image and follow the
'Getting Started Guide' in the UDRC wiki.
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

I can't make it run with Wsjt-x or Fldigi with the FT-817 (FT-818).
Focus on one program, FLdigi, and get that working

Using the NWDR image post the console output from the following
commands:

aplay -l
udrcver.sh
showudrc.sh


Re: Audio setup problem with Raspberry PI and DRAWS hat. #ft-817 #audio #drawsmanager #draws-manager #wsjt-x

jakob@...
 

Thanks Corky and John for coming back on this issue. Yes, I have interrupted line 6 of the cable time ago. I saw these instructions somewhere.


Re: Audio setup problem with Raspberry PI and DRAWS hat. #ft-817 #audio #drawsmanager #draws-manager #wsjt-x

 

As Corky says, modify the 6 pin cable.  The FT-817 is one of the most tested units with DRAWS™ and works quite well.

On Fri, Jan 22, 2021 at 8:48 AM Corky Searls <af4pm@...> wrote:
Are you using a 6-pin cable that has pin 6 connected? If so you will likely need to follow the instructions for removing that pin as the Yaesu radios take pin 6 as an input in addition to using it as an output.

Thanks and 73,
-Corky, AF4PM


On Thu, Jan 21, 2021, at 10:25 PM, jakob@... wrote:
I installed the HamPi 1.2 on a Raspberry 4B 4GB and a DRAWS hat installed. I can't make it run with Wsjt-x or Fldigi with the FT-817 (FT-818). At this time I want to run it on 20 to 40 meter shortwave. Cat works fine, however I am not able to see any RF signals. Audio in signal on the pin 5 of the 6-pin cable is OK, a few hundred mV. Tune does not generate any output signal on pin 1. I ran the Draws-Manager several time und tried on both ports with saving the settings, using the recommended settings for the FT-817 AF.  For reference I hook up my trusted SignalLink between the FT-818 and the Raspberry Pi 4B USB, and all goes very smooth after setting the audio ports. I wanted to upgrade to the DRAWS solution, which looks so attractive for mobile use and it would free my SignalLink for the base station. I searched for hours and days now to try to make it work, but as a newbie in the Linux and Raspbian world I struggle with the steep learning curve. Instructions and blogs most of the time assume deep knowledge of the Raspberry operation and do not go into detail enough for me. I would have wished a comprehensive step-by-step instruction manual going from unpacking to running applications, in one document.
Can someone lead me through the troubleshooting process? As I said, I able to run the newest Draws-Manager, I have a break-out 6-pin cable and a scope and a dummy load with power meter or the antenna and I understand the FT-818 well.
73 de AA0JR, Jakob



--
John D. Hays
Kingston, WA
K7VE

 


Re: Audio setup problem with Raspberry PI and DRAWS hat. #ft-817 #audio #drawsmanager #draws-manager #wsjt-x

Corky
 

Are you using a 6-pin cable that has pin 6 connected? If so you will likely need to follow the instructions for removing that pin as the Yaesu radios take pin 6 as an input in addition to using it as an output.

Thanks and 73,
-Corky, AF4PM


On Thu, Jan 21, 2021, at 10:25 PM, jakob@... wrote:
I installed the HamPi 1.2 on a Raspberry 4B 4GB and a DRAWS hat installed. I can't make it run with Wsjt-x or Fldigi with the FT-817 (FT-818). At this time I want to run it on 20 to 40 meter shortwave. Cat works fine, however I am not able to see any RF signals. Audio in signal on the pin 5 of the 6-pin cable is OK, a few hundred mV. Tune does not generate any output signal on pin 1. I ran the Draws-Manager several time und tried on both ports with saving the settings, using the recommended settings for the FT-817 AF.  For reference I hook up my trusted SignalLink between the FT-818 and the Raspberry Pi 4B USB, and all goes very smooth after setting the audio ports. I wanted to upgrade to the DRAWS solution, which looks so attractive for mobile use and it would free my SignalLink for the base station. I searched for hours and days now to try to make it work, but as a newbie in the Linux and Raspbian world I struggle with the steep learning curve. Instructions and blogs most of the time assume deep knowledge of the Raspberry operation and do not go into detail enough for me. I would have wished a comprehensive step-by-step instruction manual going from unpacking to running applications, in one document.
Can someone lead me through the troubleshooting process? As I said, I able to run the newest Draws-Manager, I have a break-out 6-pin cable and a scope and a dummy load with power meter or the antenna and I understand the FT-818 well.
73 de AA0JR, Jakob


Audio setup problem with Raspberry PI and DRAWS hat. #ft-817 #audio #drawsmanager #draws-manager #wsjt-x

jakob@...
 

I installed the HamPi 1.2 on a Raspberry 4B 4GB and a DRAWS hat installed. I can't make it run with Wsjt-x or Fldigi with the FT-817 (FT-818). At this time I want to run it on 20 to 40 meter shortwave. Cat works fine, however I am not able to see any RF signals. Audio in signal on the pin 5 of the 6-pin cable is OK, a few hundred mV. Tune does not generate any output signal on pin 1. I ran the Draws-Manager several time und tried on both ports with saving the settings, using the recommended settings for the FT-817 AF.  For reference I hook up my trusted SignalLink between the FT-818 and the Raspberry Pi 4B USB, and all goes very smooth after setting the audio ports. I wanted to upgrade to the DRAWS solution, which looks so attractive for mobile use and it would free my SignalLink for the base station. I searched for hours and days now to try to make it work, but as a newbie in the Linux and Raspbian world I struggle with the steep learning curve. Instructions and blogs most of the time assume deep knowledge of the Raspberry operation and do not go into detail enough for me. I would have wished a comprehensive step-by-step instruction manual going from unpacking to running applications, in one document.
Can someone lead me through the troubleshooting process? As I said, I able to run the newest Draws-Manager, I have a break-out 6-pin cable and a scope and a dummy load with power meter or the antenna and I understand the FT-818 well.
73 de AA0JR, Jakob


Re: HDMI issue with Draws

Basil Gunn
 

Since you said that the HamPi image does what you expect why not copy
the /boot/config.txt file from that image to another machine and compare
with the NWDR image /boot/config.txt file.

If you post your HamPi image /boot/config.txt file that you say works I
will compare it to the NWDR image file if you want.

kc8fws <Michael_MSN@MSN.COM> writes:

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. T the 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


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>

361 - 380 of 5712