GPS Daemon (gpsd) On RaspberryPi Claims NO FIX - gps

I've connected an adafruit ultimate gps v3 to a raspberry pi using a USB adaptor. The gps unit seems to have a fix because the led (on the gps unit) blinks at a slow rate (may be every 10 s). If I do sudo cat /dev/ttyUSB0 I get NMEA data with location.
But when I install the gpsd, meaning:
sudo apt-get install gpsd gpsd-clients python-gps
sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
and run the daemon (cgps -s), it says no fix found and GPS times out. I tried to kill gpsd and run it again:
sudo killall gpsd
sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
but that didn't help. Do you have any idea why is that?

sudo nano /etc/default/gpsd
change it to look like this
START_DAEMON="true"
GPSD_OPTIONS="/dev/ttyUSB0"
DEVICES=""
USBAUTO="true"
GPSD_SOCKET="/var/run/gpsd.sock"
then reboot. CGPS should work then.

Related

Is it possible to generate CAN message in one device and dump CAN message in another device using SocketCAN?

I am using SocketCAN and CANtact toolkit to send and receive CAN message. I am using two CANtact toolkits one to send CAN message and other to receive the CAN message both the CANtact toolkits are connected by DB9 female to DB9 female and the other ends are connected to the USB port of the laptop.
I used the following SocketCAN commands to first configure them
sudo modprobe can
sudo modprobe can_raw
sudo modprobe slcan
sudo slcand -o -s6 -t hw -S 3000000 /dev/ttyACM0 slcan0
sudo ip link set slcan0 up
The above commands are for the first CANtact toolkit then I connected the second CANtact toolkit and configured it with the following commands
sudo modprobe can
sudo modprobe can_raw
sudo modprobe slcan
sudo slcand -o -s6 -t hw -S 3000000 /dev/ttyACM1 slcan1
sudo ip link set slcan1 up
I performed these steps in two different terminals
In the first terminal, I gave
cangen -v slcan0
In the second terminal,I gave
candump slcan1
I don't receive any CAN messages in terminal 2 but if i give
cangen -v slcan0
in the first terminal and
candump slcan0
in second terminal I am able to view the CAN messages sent
This means the CAN message is not communicated between the two CANtact toolkits How can this be resolved? Or am I committing any mistake?
]5

terminal freezing when interfacing gps module with raspberry pi

I am using raspberry pi 3 B+ with latest raspbian stretch. I am trying to interface GPS module Neo 6m V2 with raspberry pi.Connected my raspberry pi with gps module using female to female jumper wires.
VCC to Pin 1, which is 3.3v
TX to Pin 10, which is RX (GPIO15)
RX to Pin 8, Which is TX (GPIO14)
Gnd to Pin 6, which is Gnd
I followed below steps to configure : ---
edit sudo nano /boot/config.txt , at the bottom of above files added two lines
enable_uart=1
dtoverlay=pi3-miniuart-bt
sudo rebbot
stop serial ttyS0 using command
sudo systemctl stop serial-getty#ttyS0.service
disable serial ttyS0 using command
sudo systemctl disable serial-getty#ttyS0.service
sudo reboot
enable ttyAMA0 using command
sudo systemctl enable serial-getty#ttyAMA0.service
verify it using ls -l /dev ,it gives
lrwxrwxrwx 1 root root 7 Sep 6 15:18 serial0 -> ttyAMA0
lrwxrwxrwx 1 root root 5 Sep 6 15:18 serial1 -> ttyS0
install minicom package using sudo apt-get install minicom
but when I am checking it using
sudo minicom -D/dev/ttyAMA0 -b4800
it freezes , nothing showing me on terminal.as shown below
enter image description here
Even sudo cat /etc/ttyAMA0 ,also not showing anything.
Please help to solve this .as I am trying this project first time,I dont know much about this.
So what's wrong with freeze terminal problem??
how can I find out ,that my gps module is working or not?when I power on raspberry pi , gps module's red light gets on.
Maybe read page 11 of the datasheet https://www.u-blox.com/sites/default/files/products/documents/NEO-6_DataSheet_%28GPS.G6-HW-09005%29.pdf on the configuration of the UART with pins CFG_COM0 and CFG_COM1 ( you change the baud rate by this and i do not know how you configured the module ... )
In https://www.raspberrypi.org/forums/viewtopic.php?t=84610 is more information especially NMEA commands and also a similar problem ...

FATAL_ERROR: "continuous.c", line 246: Failed to open audio device

I am looking for a solution for pocketsphinx for a long time. I tried everything
apt-get remove pulseaudio -y
aptitude purge pulseaudio -y
apt-get install bison -y
cd /usr/install
tar -xvf sphinxbase-0.8.tar.gz
cd sphinxbase-0.8
./configure
make
make install
tar -xvf pocketsphinx-0.8.tar.gz
cd pocketsphinx-0.8
./configure
make
make install
There is no file /etc/modprob.d/alsa-base.config so I updated /usr/shared/alsa/alsa.config uncommenting load card-specific configuration files (on request) and also /lib/modprob.d/aliases.conf commenting options snd-usb-audio index=-2
Every try from various resources I have done. I can record arecord -f cd -D plughw:1,0 -d 20 test.wav and play the same file using aplay test.wav
my soundcards are
0 [ALSA ]: bcm2835 - bcm2835 ALSA
bcm2835 ALSA
1 [CAMERA ]: USB-Audio - USB2.0 PC CAMERA
ARKMICRO USB2.0 PC CAMERA at usb-3f980000.usb-1.2,high speed
Every supported libraries are downloaded(Dont'know how many) but still It is not working.
I am using raspbian jessie image.
It is not recommended to use pocketsphinx-0.8, pocketsphinx-5prealpha is much more accurate.
Audio device for recording is specified with -adcdev option:
pocketsphinx_continuous -inmic yes -adcdev plughw:1,0
You can also configure alsa to use plughw:1,0 as default recording device, in that case you would not need -adcdev

Synaptics Touch Pad disables after login

I'm on KDE using plasma5 on NixOS, and for some reason my touch pad is disabling after logging in with KDM. Here is the output of synclient -l right after booting. What would cause this issue? Any guidance would be very much appreciated.
Having the same problem with KDE on debian with my t440p and opened an issue for the synaptics package. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770923
But I found a workaround in the ubuntu forum to use "imps". It has the disadvantage that you can't disable the touchpad an the virtual buttons separately. Better than nothing. Maybe it might help you too.
https://askubuntu.com/questions/262287/synaptic-touchpad-on-laptop-not-working/262364#262364?newreg=acf9a725adb249169b5dad26ac731c17
Try:
sudo modprobe -r psmouse
sudo modprobe psmouse proto=imps
make some changes in your grub file:
1.sudo nano /etc/default/grub
2.Add “i8042.notimeout i8042.nomux” to the line which says 3.GRUB_CMDLINE_LINUX=”…”.
4.sudo update-grub
5.sudo apt-get install kde-config-touchpad && synaptiks
edit touchpad file:
6.sudo nano /etc/pm/sleep.d/restart_touchpad.sh
7. Enter the following code:
#!/bin/sh
case “$1” in
resume)
modprobe -r psmouse
modprobe psmouse
esac
exit 0
7.sudo chmod +x /etc/pm/sleep.d/restart_touchpad.sh
8.sudo reboot.
follow all step correctly.

Programmatically remounting usb hubs after boot ubuntu 10.04

I'm running ubuntu 10.04 and kernal 2.6.32-28-server.
There are 4 usb hubs connected to the server with 4 usb ports each. On boot only two or three of them get mounted. If I plug them in after boot then all are mounted just fine. On a different server with a more powerful power supply the usb hubs mount just fine on boot so this makes me think that there isn't enough power getting to the hubs on boot. I don't have the luxury of being able to replug them in every time so I have to figure out a way to get the usb hubs remounted programmatically sometime after boot.
So far I have tried other suggestions like.
Removing and reloading usb_storage:
sudo modprobe -w -r usb_storage; sudo modprobe usb_storage
I've also tried:
sudo modprobe -vr ehci_hcd
sudo modprobe -v ehci_hcd
But this just results in:
FATAL: Module ehci_hcd is builtin
Getting really desperate I copied some of the files in /sys/devices after successfully mounting by plugging the hubs in after boot into a separate folder. After rebooting the system I tried to copy those files back into /sys/devices but even as root I couldn't copy them.