It was just that I missed the menu items:
Add-ons --> My add-ons -> PVR Clients
It was there and finally I was able to enable the TVHeadend HTSP Client.
It was already there because I have installed it using
sudo apt-get install kodi-pvr-tvheadend-hts
Consider other 5V and ground pins on the board, like pin 2 for 5V, pin 9 for ground.
If all the V+/ground pins are used up, you may try to extend the pins. There are multiple ways. One of the simplest way is to connect the pin to a breadboard, such that you will have a few extra holes to connect to the same pin.
Beware not to connect too many devices. You ...
There are many possibilities, from a heavy load that is running to a faulty SD card.
First thing is to examine the logs. Does the syslog give any hints? Errors/warnings? If so: this is probably the first thing you need to correct.
Next would be the filesystems. Any at 100%? What about swap?
Can you run a vmstat 10 > /tmp/vmstat until it crashes? that ...
It could be that there is a heavy memory workload, so there is a lot of swapping. I had similiar issues when I executed too many programs at once.
Try disabling swapfile, then the heavy memory application should be killed more likely and ssh should be still available.
Try this day via sudo swapoff -a This disables swap until the next reboot.
The signal (data) on USB cable between PC and RPi is relative to the GND on this cable. So cutting GND on this connection will result in no data transfer.
However cutting 5V only on this cable is OK.
From powerbank you need both: 5V and GND - again: 5V from powerbank is relative to its GND. So 2 wires between powerbank and RPi (it can be GPIO).
However I ...
Problem on using smBUS 2 block read/write functions.
1. Discussion on I2C reading/writing a block of data, smbus and smbus2, etc
Ah, your remind me one important thing. Some two years ago when I tried to use smBus block read/write (in my MCP23017 Micky Mouse toy project), I found the "bus stretch" thing is not implemented, so ...
[Error 121] is perhaps the most common I2C transceive error, usually caused by:
Bad hardware wiring, eg, too long (over 30 cm), therefore too capacitive, exceeding 400pF.
Bus overloaded with too many devices, also causing impedance over 400pF limit.
One simple and effective workaround is:
Remove all pullups (errata: pulldowns should read pullups) except ...
Basically a relay of the appropriate size.
You might need some transistors or etc to provide the relay with enough power to operate.
There's also SSR or solid state relays which would be fine if you could find one that can handle 50A.
The correct solution is probably to add your user to the group which is allowed to access /dev/gpiomem
$ ls -l /dev/gpiomem
crw-rw---- 1 root gpio 246, 0 Apr 28 13:17 /dev/gpiomem
On Raspbian it is gpio.
Hopefully it is similar on Ubuntu.
Then add your user to that group.
Assuming the Ubuntu equivalent to Raspbian's gpio is ubuntu-gpio do the following ...
It is standard programming practice to check if includes/initialisers have been used which can easily be done with #ifdef directives.
Frankly including wiringPiSetup() in a constructor is poor practice - if you want to use it include ONCE in your main code (as I think Gordon's comment indicates).
If you have multiple modules use #ifdef directives in each to ...
You really haven't provided enough information to make any reasonable deduction.
In particular you haven't said what the permissions of /dev/gpiomem are.
Changing permissions on a /dev/ doesn't change anything for future boots.
This needs to be set in kernel or Device Tree
I am not familiar with Ubuntu Server, while I have been a Ubuntu user for 20 years, ...
The first setup sets the wiringPiSetuped flag which is checked at each invocation.
From that it can be seen that it does not matter (any more) if setup is called multiple times.
The relevant part of the wiringPi code is as follows.
int wiringPiSetup (void)
int fd ;
int model, rev, mem, maker, overVolted ;
// It's actually a fatal error to call any ...
So I found the problem.
Short answer is yes it is possible to have two modes on one bus if the spidev devices are different or are released after each SPI transaction cycle.
these two are one bus but 2 devices so can have 2 modes
these three are one bus but 3 devices so can have 3 modes
The 2 resistors form a voltage divider to reduce the 5V output of the sensor to a value which is safe for the Pi GPIO which is a 3.3V device.
EACH sensor NEEDS its own voltage divider!
NOTE The values are not critical, in fact I would use equal value resistors to produce 2.5V output which is safely above the GPIO threshold.
You might find https://gpiozero....
I suggest that rather than trying to set a static IP Address you request the DHCP server to assign a predictable IP Address. See https://raspberrypi.stackexchange.com/a/121830/8697
The Pi WILL "work out of the box" - it is designed to use DHCP.
The values you are are attempting to assign seem to be inconsistent with your router, but you haven't ...
I have had a very similar problem (I/O errors) with SATA USB adapters that were also manufactured by JMicron. It seems to be a known problem especially for SATA (see here) that some manufacturers are buggy with Raspberry Pis. As you see, the list of NVMe adapters also seems to start growing...
As Dmitry says, you can try disabling UAS by adding "usb ...
I figured it out.
TLDR: (run everyhting as root, you won't get permission errors if you don't but it won't work)
After every reboot (yes the bytes in reverse)
hcitool cmd 0x3f 0x001 0xab 0x89 0x67 0x45 0x23 0x01
and every time you want to change it:
bdaddr -i hci0 01:23:45:67:89:ab
hciconfig hci0 reset
systemctl restart bluetooth.service
Your problem is not your power supply, but that you are powering all through Raspberry Pi USB.
First of all, your SSD draws more current than maximum total USB peripheral current draw accordingly to RASPBERRY PI FOUNDATION.
Secondly, Raspberry Pi 4 will power Geekworm Raspberry Pi 4 New X862 V2.0 via USB 3.0 and that exceeds maximum total USB peripheral ...
I will assume you are using the pigpio Python module.
You are correct to say that hardware_PWM can not be used at the same time as wave_chain.
I suggest you use the set_servo_pulsewidth method instead. This method can be used at the same time as wave_chain and is stable enough for servo operation.
Get an H-bridge motor driver board (e.g. L298N), connect your solenoid to "motor" terminal, and use a single input pin to control it. If you can live with 9V instead of 12, there are lots of smaller and cheaper motor drivers which work below 10V (like DRV8833).
There's also TA6586 chip which is suitable for hand soldering if you prefer DIY:
Note that all your RX errors are "frame" errors, which means incomplete or corrupted network frames were received by the network interface and discarded. Unlike "dropped" (which mean you receive frames you don't expect) or "overrun" (which means the system is overloaded), these errors cannot be fixed by configuration.
You can't drive a solenoid directly with a GPIO pin. You will need an interface between the GPIO and the solenoid. The technical details necessary to design this interface were provided on the product page the linked in the question.
Shown below is a representative schematic with the interface you'll need (components R1, Q1, and D1):
Q1 should be a ...
As per microsoft implementation you can take only one RDP session at a time. If you want to use more than one RDP session then you need to check the Terminal Service under Windows Server where it requires configuring an Windows Server with CAL license which will cost you too much.
There are other ways to achieve this using RDP Wrapper but by taking that ...
I had similar problem with my RPI4.
First: while using Argon M2 case, there is NO OTHER USB SDD that works on long run - even I tried with quirks - the same issue.
When I used RPI with microSD then there is no problem to attach the same USB SSD.
I suspect the USB power output - this is not a problem with my power supply as I have 5.3V/10A and when I measure ...
This is not your problem but I would be cautious with QIFEI branded ADS1115. I bought two from different UK eBay resellers in 2020 and both had the same bizarre fault, they are 12-bit but with upper 4 bits fixed at 0 and the i2c communication at 100kHz is unreliable. More detail in Adafruit Forums: Strange Case of Adafruit ADS1115 and QIFEI ADS1115.
Yes, you can, but you probably don't want to. I've crammed a Rpi4 into a Rpi3 case, but it wasn't pretty. Had to Dremel out plastic and the lid never fit right. Maybe wasteful of me, but I bought a new case.
I've also built my own cases. Ferinstance, A Peter Frampton cassette tape case can be Dremeled into shape for a Raspberry PI. It worked, but then it ...