开云体育

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

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

See??regarding?Peripherals especially the power of the USB port, so it seems that the power drawn from the port more than allocated may make the whole device unstable:

Warning:

Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the Raspberry Pi. If the Raspberry Pi's supply voltage falls below a certain value (anecdotally stated as around 4.75?V), or it begins to fluctuate, your setup may become unstable.

and also?

Model B Hardware Revision 2.0 and Revision 1.0 with ECN0001 change?This had the polyfuses removed, removing the 100?mA current limitation for each USB port (but leaving the main fuse F3 intact). Users should still ensure their power supply can power the Raspberry Pi and the USB peripherals. Revision 2.0 was released in August 2012.??Warning: Because the polyfuses have been removed, back feeding of the PI, by applying power via its normal USB output, can damage D 17 if triggered by an over-voltage, and so lead to consequential over-heating. This can be discovered by melts, scorching, smoke or worse

So it seems that the power supplied to the USB ports is crytical, thus it may be advised to make use of powered USB Hubs?

--
73 de Eugene / ZR4EM

Everything is running smoothly now, except my SSD boot that I am still unable to get starting on the USB 3. It previously worked with the hack and with the SD still in place (even before the new updated and beta firmware). I can see the SDD when booted up in Raspbian (connected to the USB3 port) but cannot boot up in it. Will try and see whats wrong tonight.
Im using the above Wifi dongle and purchased a original D-Link DUB-H7 hub with external 5V power (Not the 12V as last time)
The USB2 hub is running very nicely,?
Its mind boggling. Will maybe use the Y cable on the external USB 2 HUB (the power side) but otherwise its up and running and I'm broke and fed-up with these Raspberry pi 4 problems.
Its not easy,?
--
BBT
73 de Eugene / ZR4EM

The SSD thingy is not working. I think I will go with the same direction as @KM4ACK by omitting the SSD completely and just use the microSD
--
73 de Eugene / ZR4EM

The problem with us and the RasPi, we are pushing the envelope.
It is not meant to be, but we want to force it in a direction we want It to be in.
Its and SBC and meant for SBC robotics with external pins programmable to do stuff
It is not meant to work with USB, USB is a very new concept in Linux and lets be fair, The SBC just cannot achieve what we want it to do on USB, there is just not enough power to drive all the USB devices and still, it is an SBC with not the initial intent to be a field PC for hammies. We just have to think and work outside the box.
So maybe we have to fall back to serial comms but even this have limitations.
If we want to make this work we have to think SBC and not Intel PC, It just won't work, no matter what.
You just cant reinvent the wheel, but you are able to built the body around the simple concept of the wheel.
Maybe the more technical should assist here to make this work, because USB seems not to be the solution, and I do not know what is.
Jason (KM4ACK) is falling back to use the Pi with a micro SD card, and that may be the perfect solution because the Pi is a SBC not intended to work from an external storage device, it is just the way it is, and what we have to work with. Lets have another look at serial comms because this USB thing is just not up to it.
--
73 de Eugene / ZR4EM