The build went well, without any major hick-ups, but yes there is always something, like forgetting to plug in something or whatever. But yes it is up and running.
The built details is as follow,
The power supply is Isolated via an DC-DC converter of MeanWell 9-18VDC with an output to 5VDC for the Pi and USB hub.
The power supply to the monitor, Waveshare 11.6 full HD monitor, is isolated via a DC-DC converter of Tracopower TEN 15W to enable a stable output from 9VDC-18VDC to 12VDC
I also have an DC-DC converter (not sure if it is isolated) from any input up to 36VDC to an stable output of 12VDC (adjustable)
In the box is build-in the three DC-DC converters, and USB2 HUB, PCB connected to the GPIO connector of the Pi 40pin with the following
5V DC output to the system fan, 5VDC output to the two chassis fans for inflow, I2C connector for peripherals e.g. OLED, DB9 for I2C SPI and UART connection via the DB9 male chassis connector, push button for safe shutdown as well as a LED with confidence pulse when the Pi is booted up, USB HUB, 120GB SSD with OS installed on it via the USB3 port.
The system fan and cooler is a low profile ICE cooler heat pipe cooling with an 40mm 5VDC fan
Cooling is provided by one 40mm sq X 10mm and 40mm sq X 20mm fan while two 40mm sq X 10mm exhaust fans is fitted on top for assisted box cooling.
The DB9 connector I have not tested yet
The hiccups began when I exchanged the DLink USB2 HUB with another? 7port USB2 Hub because with the mod I have blown an USB hub chip on the DLink so a few ports on the Dlink is not working anymore. The whole OS changed and the USB devices did not want to connect to the applications for HAM radio, even my custom made Prolific USB to RS232 connector for the Yaesu-FT897D, a panel mount Micro HDMI to HDMI connector as well as the USB audio COB dongle.
What a nightmare, It cost me to re-install the Pi OS as well as BAP.
With BAP I installed the FLrig and HAMLIB and checked if it was working before I installed anything else.
The I proceded with FLDigi and ARDOP asn finally the WSJT-X and JS8Call
At the moment the following devices is connected to my USB input,
An Homebrew Prolific adapter for the FT-897 CAT
An USB Sound COB dongle to the custom cables for the Audio I/O
A homebrew USB GPS from UBLOX NEO5
An external WiFi device with an external cable antenna to extend the WiFi signal and to keep it as far as possible from the other RF
An HDMI KVM switch with keyboard and mouse sharing
The USB touch input of my 11.6" monitor running from the Tracopower DC-DC converter fitted on the box
What a build! everything in an box approximately 7.5" X 6" X 3 " in size, smaller than my FT-897.
The device temperature in my shack is about 10C above the ambient temp in my shack.
Everything is running from a DC supply, even the FT-897 and ICOM 2m/70cm radio
It seems to be very stable and no USB or any other problems or conflicts ATM.
The only thing I have to sort out is the audio between the FT-897 and the Pi4, but that's another story. I want to build an external PiZero with an IQaudio Codec Zero connected via serial comms to the Pi4 via SPI or UART.
Hope thats my complete build. No external wires etc, all is done from chassis mount connectors

73 de Eugene / ZR4EM

I have been using this screen from Sunfounder. It is intended for use with a Raspberry Pi. It powers from 12vdc and supplies a USB 5vdc connection to the Pi solving the problem of how to power the Pi from your 12v battery. Comes with all the cables and a 12v wall wart.

It seems to be a good size, and works okay. You still will have trouble in bright sunlight, but a shade could be built pretty easily.

https://smile.amazon.com/gp/product/B07SZH1VB2?psc=1
--
Al AE2T

I ran the command you suggested and the response was: '/dev/serial/by-id/': No such file or directory.

that tells me that the pi isn't seeing the radio. you should get something like Fred posted. Try rebooting and run the command again before starting anything else. You might also try swapping to a different USB port.
--

well using ssh to get in; then using sudo raspi-config -> advanced options -> set screen resolution -> choose the last option -> "finish and reboot"? .... worked!

must have done this on the other pi without remembering it

thanks for the help!

Fred, thanks! That info will come in handy once I get connected. Those other settings would have been my next question :-)

73, Tom

开云体育

Thanks for the reply, Jason. I ran the command you suggested and the response was: '/dev/serial/by-id/': No such file or directory.

There is a dev directory off the root but it does not contain a serial directory. I should add that my flrig install was done as part of BAP 3.0.8.

Tom - K0TW?

I’ve been reluctant to try this and use dummy HDMI plugs that simulinstead. But with the Pi4 I’d like to get rid of those due to needed adapters to the mini-HDMI jacks. Despite asking numerous times on various forums, I’ve never been able to determine if it’s possible to do this for BOTH ports. Somehow I think not. It’s really great to have all the real estate of dual displays on the host even if the client is single display.?
--
Don
W6CZ
DM07bk

Hi,

I‘m using now BAP since 3 month, first a raspi 4B 2 without a case and 32GB ssd. Here I used mostly js8call, xastir with direwolf and wsjtx. The pi ran stable 24/7 and also the mentioned progs ran without any issue.
Meanwile I updated and put the pi into an argon m2 case with a 120G Kingston m2 ssd.
Here comes my 1st issue: the system isn‘t anymore as stable as before. It is freezing 2-3 times a day
2nd issue, as I do not like xastir so much, I switched to yaac and configured it for digipeating and use of an agape port on direwolf as I did also for xastir. Starting yaac standalone, digipeating functions well and the map is filled with stations. If I start direwolf and then yaac, I get the stations via rf but no stations by the in yaac configured digipeater.

Maybe one of the group has an idea to solve one of the issues

vy73 de Klaus, DC2JR

First, make sure nothing else like WSJTX is trying to control the rig by closing those applications. Now with the radio powered up and connected to the pi, open a terminal and run
ls -l /dev/serial/by-id/
which should give you something similar to what you see below.

lrwxrwxrwx 1 root root 13 Sep? 7 13:57 usb-Icom_Inc._IC-705_IC-705_12007996-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Sep? 7 13:57 usb-Icom_Inc._IC-705_IC-705_12007996-if02 -> ../../ttyACM1

The above information tells me that my Icom is connected to ttyACM0 & ttyACM1. In my case, I use the ttyACM0 in FLRIG.

--

I notice the same thing on my Pi 3 test box. Left to it's own devices, the swap will fill up over time. This is one reason I have upgraded almost all of them to Pi 4s. If you leave them running all the time, you might consider adding a nightly reboot to your crontab.
00 03 * * * sudo reboot
The line above will reboot the Pi daily at 0300.

--

On Tue, Sep 7, 2021 at 08:22 PM, K2PMD - Paul wrote:

Garmin flashes Input Password 1234.

Try using the GUI Bluetooth tool to connect to the Pi first before running the rfcomm connect tool. Click on the Bluetooth icon in the top right corner of the Pi desktop.
?
--

Which version of BAP are you running? This video may help

You can also try starting it manually and see what errors it produces. From the terminal run:
conky
--

Aha, I think I am almost there.

The hcitool scan finds my Garmin and gives me the MAC address. When I input?sudo rfcomm connect /dev/rfcomm0 (MAC ADDR HERE) the Garmin flashes Input Password 1234. And that's where it gets stuck. I have got to find a way to disable the automatic password and then I am going to try again.?

Thanks, Jason! I am going to keep trying, This damn going to work thing keeps getting in the way of my having fun with BAP and my Go Box.?

de K2PMD