开云体育

Check out freedompop on sprint, aka cdma. Free 500 megs each month and easy to root and hotspot most devices.

David, thanks. My bad; I had not in fact read the 1.3 docs as you can guess. :) Figures that I am looking at the guts of source code instead of the obvious. All better now, though. -Mike K0FSJ

Hello Shimniok (no call given), I assume you've configured a Tracker beacon (tbeacon) in your direwolf.conf and also configured the use of your GPS using either the GPSNEMA or GPSD keywords. Looking

I'm running into a TBEACON error on RPi / direwolf 1.3. I searched github issues, googled, and searched yahoo groups -- to no avail. I figured I'd ask if anyone's seen this... On RPi 2, newly

Hello John, If things are working for an hour or so and then things start to break down, I would begin to suspect: - RFI from your radio getting back into the soundcard and/or Rpi and

David, sorry for the delay. Just to be sure I checked the patch level of Jessie: apt-get update apt-get upgrade apt-get dist-upgrade rpi-update reboot. still see the same error after an hour or so of

Just pulled and rebuilt from dev branch. That works for me (user is a gpio group member). Thanks!

This has been fixed. 67b11d4922ce538e55ab7853c1a449ad4de6ec83 in the 'dev' branch. Don't digipeat packets when the source is my call.

Nick B. wrote: Commit 58c2707f7d65b5b074b5e67e00c06a50fb968349, on the 'dev' branch, should fix this. Raspbian Jessie has a new 'gpio' group which was not in Wheezy. The logic for getting access to

Hello John, Ok.. and it's fully patched: apt-get update apt-get upgrade apt-get dist-upgrade rpi-update reboot Ok.. and how is your Syba sound device connected to your Raspberry Pi? Directly connected

Dave, Please see responses below. 73, John, NX2I

Hello John, I've been running Direwolf v1.4 on both a Raspberry Pi v2 and v3 with Syba USB devices with good luck for months. A few questions if I may: - Are you running on a Rpi v1, v2, or v3? - What

Thanks Tim. I have been testing this solution for the last couple days. Bottom line..... I still see the same error. Thanks and 73, John NX2I direwolf_packet@...> wrote:

Hi, It may also be worth reducing checking the CPU load by running top or htop in another terminal. Then reduce the sampling rate by running with e.g. "direwolf -r 11025" . This made a difference for

I'm seeing an odd problem, but it might be difficult to describe. I have a Raspberry Pi Zero running the latest software and DireWolf 1.4.E. But it has also done this with version 1.3. I am running

As far as it concerns permissions, everything seems to be fine. Something else is grabbing your serial port as soon as direwolf exits. After stopping direwolf, try: $ lsof | grep PTT and $ lsof | grep

Hi David, thanks for your reply. I've been exploring the sudo issue for a few days now and here's what I've found. - Works perfectly on the default pi user on Rpi. This is because pi is set up for

Hello all, I've been using DireWolf for quite some time now and I'm really happy with it. The decoding performance is amazing and the program is pretty stable. Uptime without restart at all before the

As for GPIO access, the running user needs to be apart of the "gpio" group. Quick example is: -- b. Add this new user into the following unix groups: - "audio" (allow users to access the soundcard) -

Thanks for the reply, here is the results: kd9dcs@bluetracker:/dev $ ls -al /dev/ttyUSB0 crw-rw---- 1 root dialout 188, 0 Feb 27 15:26 /dev/ttyUSB0 as an added bonus here is the udev rule I wrote to