Re: [beagleboard] BeagleBone Black GPS PPS and Chrony for time sync
Hello, I am trying to run NTP server on my PocketBeagle with GPS and PPS time source. To establish that I am following your notes. However when I try to run gpsd it is giving me output like this: :$ gpsd -D 5 -n -N /dev/ttyO4 /dev/pps0 gpsd:INFO: launching (Version 3.17) gpsd:IO: opening IPv4 socket gpsd:ERROR: can't bind to IPv4 port gpsd, Address already in use gpsd:ERROR: maybe gpsd is already running! gpsd:IO: opening IPv6 socket gpsd:ERROR: can't bind to IPv6 port gpsd, Address already in use gpsd:ERROR: maybe gpsd is already running! gpsd:INFO: command sockets creation failed, netlib errors -1, -1 Deep-dive into systemctl shows: systemctl status gpsd.service ● gpsd.service - GPS (Global Positioning System) Daemon Loaded: loaded (/lib/systemd/system/gpsd.service; disabled; vendor preset: enabled) Active: failed (Result: timeout) since Tue 2021-03-09 18:48:39 UTC; 28min ago Mar 09 18:47:09 beaglebone systemd[1]: Starting GPS (Global Positioning System) Daemon... Mar 09 18:47:31 beaglebone systemd[1]: gpsd.service: Current command vanished from the unit file, execution of the command list won't be resumed. Mar 09 18:48:39 beaglebone systemd[1]: gpsd.service: Start operation timed out. Terminating. Mar 09 18:48:39 beaglebone systemd[1]: gpsd.service: Failed with result 'timeout'. Mar 09 18:48:39 beaglebone systemd[1]: Failed to start GPS (Global Positioning System) Daemon. Running cgps is giving normal output but when I start chrony it is updating only PPS. Could you please help me with that? środa, 17 października 2018 o 13:50:47 UTC+2 engrmas...@gmail.com napisał(a): > Hi, > I have gps with pps and signal level is measured in scope and is ok. The > problem is that when ppstest command is run the pps output is displayed as > ok but after arround 180 to 230 seconds i get error connection timed out > error. I have gpsd amd chrony installed. > Strangely when i restart gpsd then ppstest gives correct output but then > it shows connection timed out error again. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/2038e452-7f07-4fa4-afb9-15a3af4bf981n%40googlegroups.com.
Re: [beagleboard] Re: battery power for PocketBeagle?
I connected a 6v 5amp battery and it broke my bricked my pocket beagle. On Thursday, November 22, 2018 at 6:23:51 PM UTC+2 fek...@gmail.com wrote: > Hello, I had to put the charging project on hold but will pick it up again > soon. I probably blocked excessively on finding an acceptable 10K NTC > thermistor with the right B= value. > > On Tue, Nov 20, 2018 at 9:25 AM Jason Kridner wrote: > >> On Thursday, September 6, 2018 at 10:22:38 AM UTC-4, Fred Kerr wrote: >>> >>> I am concerned about the battery temperature for safety in my office, >>> house, and around my 4-year-old son. :) And I'm curious about logging stuff >>> infinitum. >>> >>> I have it working with a fixed resistor (without attempting charging >>> yet). >>> >> >> Did you ever get your thermistor working and enable charging? >> >> > On Thu, Sep 6, 2018 at 7:18 AM Graham Haddock wrote: >>> >> Fred: The temperature coefficient is only important if you are going to use them as temperature monitors, and you are going to thermally/mechanically attach them to the battery. If you are just trying to get the battery power supply to run, and are not concerned about battery temperatures, a fixed resistor will work fine. --- Graham == On Thu, Sep 6, 2018 at 3:34 AM Fred Kerr wrote: >>> I am looking for 10K NTC Thermistors with B=3480. How critical is the B > value, or what range can I accept? Currently I am looking on Mouser. > > Is there a specific or recommended battery pack? I'm just using an > 18650 from a local surplus store. > > Regarding the log file, I still need to do this: > > sudo /opt/scripts/tools/developers/update_bootloader.sh > > I'll also look for 100K thermistor with B=3960 > > On Thursday, August 30, 2018 at 5:35:43 PM UTC-7, Fred Kerr wrote: > It runs well with the soldered implementation. My breadboards are a >> little cheap. >> >> The attached minicom_20180830b.cap shows a boot with microUSB power >> from a wall wart (from my rpi3), then a boot with the battery circuit. I >> left both RX and TX attached; I'll play with disconnecting them another >> time. >> >> I'll look into getting some "telemetry" info from the pocket beagle. >> I'm open to suggestions about things to add/log, etc. Also, I think this >> pocket beagle doesn't have a fix that I got before - after the shutdown, >> things panic. >> >> If anything else jumps out from the log file, please let me know! >> > >> On Wednesday, August 29, 2018 at 10:59:03 AM UTC-7, Fred Kerr wrote: >> > I'll try again soon with my more stable circuit (*soldered), also with >>> RX disconnected so I just get output from the Pocket Beagle and the >>> only >>> power input is from the battery circuit. >>> >>> (*Soldered, so no loose breadboard connections, better current >>> carrying capacity, etc.) >>> >>> What is a good way to share log files? Mine can get verbose! I could >>> store it somewhere and post a link - suggestions welcomed! I have a lot >>> of >>> possibilities, but just let me know what works best for you. >>> >>> On Tuesday, August 28, 2018 at 12:51:23 PM UTC-7, Fred Kerr wrote: >>> >> Yes, it ran quite a lot longer on the 1F, but still hung. I wired this up (see pic) to be more stable than the breadboard mess I had. The led on 1.8k resistor is gonna run a lot longer than I'll take at lunch!!! Can I isolate RX and TX or...oh I just need TX from the beagle for visibility! 1F 5.5v supercap (that battery was discharged to 3.96v). This one has more charge. Also put a 1000uf electrolytic on the soldered version, "because". Fred Kerr (mobile) On Tue, Aug 28, 2018, 12:13 PM Jason Kridner wrote: >>> > > On Monday, August 27, 2018 at 11:15:36 PM UTC-4, Fred Kerr wrote: >> >> Hello all, >> >> I'm being just a little bit careful here: >> >> I'm about to try this, but I will connect up the serial terminal >> first, so I can see output and interact with the board. (Graceful >> shutdown!) >> > > Don't connect the power or RX (ie., serial cable to PocketBeagle) > signals to avoid them interfering. Great thing to monitor. > > >> >> I will test the serial connection first with just a micro USB >> charging cable rather than USB to a computer. (Simplify!) >> > > Not sure what you are testing here. Are you just saying you'll > power via the microUSB connection and not connect to a computer, just > to > see the behavior? You are monitoring with a
[beagleboard] BBB sudo apt upgrade errors
While performing an sudo apt upgrade the following occurred.. Past upgrades had no issues. debian@beaglebone:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: c9-core-installer 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up nginx-full (1.14.2-2+deb10u3) ... Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details. invoke-rc.d: initscript nginx, action "start" failed. ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: en abled) Active: failed (Result: exit-code) since Thu 2021-03-11 12:01:25 EST; 104ms a go Docs: man:nginx(8) Process: 316 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process o n; (code=exited, status=0/SUCCESS) Process: 317 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code= exited, status=1/FAILURE) Mar 11 12:01:24 beaglebone nginx[317]: nginx: [emerg] bind() to 0.0.0.0:80 faile d (98: Address already in use) Mar 11 12:01:24 beaglebone nginx[317]: nginx: [emerg] bind() to [::]:80 failed ( 98: Address already in use) Mar 11 12:01:24 beaglebone nginx[317]: nginx: [emerg] bind() to 0.0.0.0:80 faile d (98: Address already in use) Mar 11 12:01:24 beaglebone nginx[317]: nginx: [emerg] bind() to [::]:80 failed ( 98: Address already in use) Mar 11 12:01:25 beaglebone nginx[317]: nginx: [emerg] bind() to 0.0.0.0:80 faile d (98: Address already in use) Mar 11 12:01:25 beaglebone nginx[317]: nginx: [emerg] bind() to [::]:80 failed ( 98: Address already in use) Mar 11 12:01:25 beaglebone nginx[317]: nginx: [emerg] still could not bind() Mar 11 12:01:25 beaglebone systemd[1]: nginx.service: Control process exited, co de=exited, status=1/FAILURE Mar 11 12:01:25 beaglebone systemd[1]: nginx.service: Failed with result 'exit-c ode'. Mar 11 12:01:25 beaglebone systemd[1]: Failed to start A high performance web se rver and a reverse proxy server. dpkg: error processing package nginx-full (--configure): installed nginx-full package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: nginx-full E: Sub-process /usr/bin/dpkg returned an error code (1) debian@beaglebone:~$ debian@beaglebone:~$ cat /etc/dogtag BeagleBoard.org Debian Buster IoT Image 2020-04-06 debian@beaglebone:~$ uname -a Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux debian@beaglebone:~$ lsb_release -a No LSB modules are available. Distributor ID:Debian Description:Debian GNU/Linux 10 (buster) Release:10 Codename:buster Any ideas appreciated. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/6e89ef02-738b-49b1-9f7b-5fed1689592dn%40googlegroups.com.
