So my Yeasu FT-890 is connected using a CAT to USB-FTDI cord my Baund is set at 4800 when I click Init I get this error:

Transceiver not responding!?
Check serial (COM) port connection?
Open menu Config/Setup/Transceiver
Press 'Ser Port' button, reselect port
Press 'Init' button

I though it was a cord issue that I bought on Amazon, so I purchased a new cord from the UK that was supposed to be the fix, but I'm still getting this issue. Any help would be appreciated.?

The problem, seems to me, may also be supply related as well as the Linux core. I'm not sure what anymore, Its just demoralizing to battle so much with a piece of hardware.
My order of business after failing again to boot from SSD, will be:

1. Carefully evaluate the power outputs of the USB ports, during boot-up and continuously when operating (is the USB port supplying adequate power to all the connected peripherals.
2. Have a look what the influence of the built-in WiFi is on the whole system. Compare it with different monitors e.g. DC or AC supply monitors as users expressed difficulty here. Test it with external WiFi devices and note the difference.
3. I have to rebuilt my GPS module as the previous one's is a paper weight ATM. Take careful note of the power requirements of it.
4. Check power requirements during startup of peripheral and see if some devices do not require more power with the initializing process.
5. Falling back to other externally powered USB hubs may not be an bad Idea, powering it from a stable DC-DC converter that is able to deliver enough power during peak requirements.

Something is wrong somewhere causing the USB devices to fail, and I'm determined to find out what the problem may be.

Stay safe everybody. Got also news that a school mate of me is seriously ill with COVID-19. Does not matter what the conspiracy theorist tells you or what everybody experience or where or how it originated, the point is its real.?
--
73 de Eugene / ZR4EM

Hi Craig
I also got that problem early on especially because I'm running from a UBEC supply directly coupled to the GPIO port but it seems that that is sorted. I will certainly have a close watch on that because I do not know what is happening during the running of the Pi after boot-up. Problems experienced with the pi may be that the PSU and supply to the USB become unstable especially with the fact that the Pi is not like a windows PC that will alert you if the USB devices is drawing too much power or that the Pi's USB ports do not have that much power compared to a PC. Maybe that is the problem, coupled with the fact that the Linux Core works different with the USB devices that the actual Debian Distro. I am just fed-up with the Pi4 atm. It gives me lot of grief that I may be too old to handle (the same as with digital modes). Sometimes the Pi's errors is just demoralizing and it drives me nuts. I battled till 2am local time this morning with the bloody Pi, to the frustration of the wife (and me).
--
73 de Eugene / ZR4EM

Hi Jason,

Did you check dmesg (diagnostic message)?log? That may give you some idea what is happening. From terminal just run dmesg (I prefer to add -T option to give the timestamp). There will be entries there anytime anything is connected or disconnected, and if there are power issues, you'll see that too. For example, here's what mine shows when running on an extremely under powered supply:

On Thu, Jun 25, 2020 at 09:57 PM, Michael Lloyd?
?I, too, am very interested in how to make this work. I built the kit, and never used it yet because of trying to get it to work. Will be watching. Thank you for having this here.

KY3M

Jim

A good point Ben,

I am running a 3.5 amp wall wart and pretty sure Jason was still running one of the?

hooked up to a Dakota 12v LifePo battery.? I believe power shouldn't have been the problem.

73 dave/W6TUX

Using the Pi4 for a field PC running on DC has its ups and downs.
Sometimes more downs and frustrations as ups.
Most of my problems is related to the USB connectivity of peripherals and equipment.
I build and customise almost all of my stuff as its a bit expensive due to a crappy exchange rate, but this is not without any headaches.
It seems that most of the problems of the Pi4 is related to the on board WiFi. As soon as you disable it in the /boot/config.txt with the command line?dtoverlay=disable-wifi?the problems seems to disappear or be less.
Most of the other RPi4 users is complaining regarding the HDMI/WiFi interference. My only experience with this was that the YouTube audio was really bad and choppy but this seems to be resolved. I really do not like the Micro HDMI connector just as the Micro USB connector as this is an unreliable bad connector. It seems even worse if you try an Micro HDMI to HDMI adaptor and I resolved this issue by using a Micro HDMI to HDMI cable and not the adaptor.
I used an OEM type Ublox Lea6 module for a GPS but destroyed it together with my external TP-Link WiFi adaptor and 7 port hub by injecting 12VDC in stead of 5VDC into the hub (Stupid mistake but I have to many wires and stuff that have to run from a DC supply so I'm confusing myself).
Most of the stuff I use is custom made or Homebrew. I am currently studying how to setup a Pi0 as a MQTT Borker with Mosquito and Node Red to get notifications of intrusions of my area with Proximity sensors etc via a ESP32 network of devices, that will be running on its own solar powered supplies. I also modded an old 7' trailer with solar panels etc (work in progress) for an custom DC supply with AGM batteries for my radios and other DC equipment like the Pi4 field PC, HDMI monitor etc and radios (primarily my FT-897D)
Back to the Pi4 built, it is not easy. The Software and hardware work to a point and then, suddenly without warning, everything starts to fail. I do not know why, but I am trying everything related to the Pi4 hardware. It also seems to be compatibility issues with the Debian 32bit software (have not yet tried the 64bit upgrade), hardware and USB related. There is even issues with incompatible USB adaptors and Thumb drives for alternative boot drive that I'm trying to overcome (my SSD and SATA to USB adaptor seems not to be a compatible boot device, not sure why but working on it).
I guess the road is a bit bumpy to make custom stuff work.
Any thoughts or comments/experience with Raspberry Pi 4 related hardware/software
--
73 de Eugene / ZR4EM

Hi fellow hammies,
The problems with the Pi4 is really weird. Some people reported leakage/problems between their HDMI and Wifi, other just described the WiFi module just as crap. I also have some weird experiences with my Pi4 but mostly related to USB connectivity. Most of the problems (I think) is related to RF. We all just love RF with the radios and all, but the Pi4 do not like it (It seems). My Pi4's WiFi module is just pathetic so I opted for an external WiFi device. Lots of problems solved (until I blew up my WiFi USB module that is).
Taking the WiFi transceiver away from the Pi4 with a USB unit and disabling the? on board WiFi and Bluetooth did it for me. I unfortunately cannot use my Bluetooth keyboard anymore but the results was mind-shattering to say the least. Even my YouTube video's audio was without hick up on the HDMI monitor.
I'm not exactly sure what the problem seems to be, but it is likely to do with leaking RF or not enough shielding or something similar.
Here is a few articles and info regarding the Pi4 WiFi

Dozens of Raspberry Pi 4 users have reported similar display output Wi-Fi problems?. However, the reports are inconsistent and there are lots?... The exact cause remains a mystery, but a Raspberry Pi Foundation engineer speculated that a possible cause is radio frequency leaking from HDMI cables and causing interference with Wi-Fi signals. Some users have noticed a different impact on Wi-Fi, depending on which of the two HDMI ports are being used.?

RPI on board WiFi is rubbish...

Again the experience with RPi3 is totally different for all users. I also did not experience any problems with USB or WiFi with my Pi3.
The Raspberry Pi Foundation is working on the problem but it does not resolve our stability issues with the Pi4, it may be anything but for me querying the Pi Foundation while everything is modified is a big No-No
I am awaiting delivery of my official tried and tested?ith an Ralink RT3070 chipset and will give feedback on the results. Since using an external Orico USB2 Hub and an Unitek USB3 hub witha wired mouse and keyboard the problems seems to be quite less with USB connectivity.
PS I had a real headache to get JS8CALL up and running on the Pi4 with an external USB to audio hub but since using an official tried and tested??it seems much better although nobody seems to have any problems with any USB sound dongle.

73 de Eugene

I would recommend checking the total power usage of the Raspberry Pi while running with the Drive and without the Drive. I've seen low power issues cause things like this.

Ben

I have "re-built" my RPi hardware. The SSD is on a USB3 corded adapter. I have the u-lox 8 (2m USB cord) attached to USB2. When I plugged in the USB it did not sync. I checked gpsmon, nothing. I changed "the" window (looking outside), nothing. I re-booted, the GPS synced up within ~30 seconds...

I have seen before that re-boot made a difference.

Not that it should matter, I am overclocking at 2G.

The PI case has a metal bottom and a "shield" 12V DC supply/fan on the top. Copper heatsinks on CPU and Memory, and "other". Esentualy an open case... The wifi is pi hotspot 10.10.10.10 with NO connection. Hardwired LAN.

Now to see what I can do with the SiRF Star IV GPS Chipset working... The GlobalSat BU-353-S4 GPS. I have info. I need to sit down and see what I can do. Now that FD is over. I operated 1D in AC. I did not need the GPS, anyway. I find as I get older, the heat (it was 90F+ here in DE) takes "it" out of me... I may operate inside next year or find a cooler section. I guess I could operate at night, as it is cooler then.

I have also tried to get ububtu to boot from the SSD - no. I need to go back and run on the microSD. I want to see how the 64bit OS works and how it does with wsjt-x...

73, steve WB3LGC

Nope, tried but it seems I'm a bit too far and the propagation of 40m pathetic. Tried to contact North America and Europe but to no avail.

开云体育

cgps is usually frozen when I first run it after Conky freezes.? I removed the gps, Conky showed current info including grid square until the next time it refreshed.? When the gps was reinserted, cgps was working normally when the window was open.? After 4-5 cycles of this, Conky was running ok, with the occasional lag.? I went through the steps in the video you included.? I did notice multiple process IDs for Conky.? Should there be only one?? I am also going to run a fresh BAP3 script on a different SD card to see if I screwed something up.

Good morning Jason,

Had GPS working before.? Just after the release of Build a Pi v. 3.0, I moved my Raspberry Pi projects out of the house into our Travel trailer parked on our property, from there I did the tweaks to move the operating system onto a Ravpower USB 3.0 SSD, then ran the script and enjoyed a far faster installation? - had a problem with GPS not working out there and was blaming it on the metal shell of the trailer.? It now turns out that I may have some kind of problem between my USB GPS receiver and the USB SSD trying to operate at the same time.? Will be looking into that further this week.? Love the increased speed of the SSD but need that GPS.? Certainly glad you noticed the same during Field Day - now on a proper path of discovery for what the problem really is, in the mean time will revert to booting from the Micro SD card this morning.

73, dave/W6TUX

Jason
It may also be with one thumb drive that is better isolated than the other against RF. Again maybe you should try the external WiFi module but find one that is compatible with the Raspberry Pi.
See??and?. Maybe something there also that is blocking the Pi
Sometimes switching between USB ports also cause some havoc so make sure U use the same port for the same USB device when you have to unplug the Pi.
Also remember that the power output of the RPi ports is limited, so that may also be an issue.
73 de ZR4EM

Hi Jason
I have so many issues with USB and Pi 4 that I don't know where to begin.
It seems that the Raspbian buster distro is quite finicky about the USB devices. I cant even start my SSD with an Orinco USB to SATA adapter, but the Pi4 see the SSD. I am not sure why. I have read so many articles and tried so many things that I am buggering up my installation. It also seems that if you connect some things to USB3 and other things to USB2 everything goes haywire. It also seems that the internal WiFi and Bluetooth is causing all sorts of problems. Most of my problems were sorted out when I switched to an external USB WiFi device and switched the internals off, but this also not with quite a few headaches.
The GPS unit I'm currently using is a modified UBLox Lea6 but unfortunately I fried both the GPS and the WiFi module with the USB hub (accidentally plugged a 12VDC supply into it in stead of a 5VDC supply). So I'm back to square 1, but it seems that the internal WiFi have quite a lot to do with the troubles. There also seems no way to mod the pi to add an UFl connector for and external antenna like the Pi3, which is a shame because I have limited range with my aluminum cooling housing for the Pi4.

I ran into an odd issue with the GPS during field day that has me stumped.

I plugged in the GPS, CAT cable, and sound card. Then booted the pi and everything was working as it should including the GPS. A few minutes later, I plugged in my USB thumb drive (data) and the GPS stopped working. Noticing the GPS had stopped, I removed the thumb drive and rebooted the pi. The GPS started working again. Plug the thumb drive back in and the GPS stopped working.

This is the thumb drive that creates the problem and I am able to reproduce the problem.

Back in the shack on Monday, I swapped the thumb drive for the one that comes with many of the pi kits and inserted the same micro SD card into the thumb drive. Plugged it into the pi and had NO issue with the GPS. Left it running overnight just to verify. As of this morning, the GPS is still working with the other thumb drive plugged in.

I have no clue why one adapter works and the other doesn't. The main difference is that one is a USB 3.0 and the other is USB 2.0

If anyone has a guess as to why the one doesn't seem compatible with the GPS, I would love to hear it. No settings were changed on the pi at any time. Only the USB device was swapped.

--

On Mon, Jun 29, 2020 at 03:57 PM, Nick AF2M wrote:

Yes. Exactly.?

After Conky freezes, are you able to view your GPS by running
cgps

I am curious if it is a Conky issue or a GPS issue. I have seen the GPS create odd problems with Conky before
?
--

Mitch:

Thanks for the information. I had read that blog post over the weekend, but although the autor provides crucial information, I was unable to tie his ideas together enough to make the project work.

On the other hand, today I put some time into this and after consulting several sources, including a couple of videos from Mr. Oleham (KM4ACK), I successfully put the pieces together (i.e. connected a Pi 3B+ via Bluetooth to a TH-D74 and reliably and consistently sent and received emails through Pat). Tomorrow I will go through the process again from the ground-up. If I can validate the procedure, I'll come back to this forum and share the steps (if it is OK with all).

Hi, Jason. Best regards.

Victor
WP4QZH

This feature is in alpha test at the moment.? I have been testing it and standard forms work great.? The developers are working to get it available for a beta test soon.
--
--Bill AA6BD