Date   

Re: tx dummyrepeater

Jim <g7icd.jim@...>
 

thanks Richard

will try that now i was using pin 5

cheers jim



Hard drive

Jim <g7icd.jim@...>
 

Now i have the dstar pi2 and thumbdv all working is there away i can transfer it all on to a harddrive (i have a 250g usb) so it uses the sd card for bootup but then reads all the other files from hard drive?

or is to much for a novide to do ?

cheers jim



Re: Hard drive

 

Here is a tutorial (I have not used this, but the concept is clear)

https://learn.adafruit.com/external-drive-as-raspberry-pi-root/overview

There is some work going on at Raspbian development to make network or external drive boot much easier.


On Wed, Aug 31, 2016 at 8:22 AM, Jim <g7icd.jim@...> wrote:

Now i have the dstar pi2 and thumbdv all working is there away i can transfer it all on to a harddrive (i have a 250g usb) so it uses the sd card for bootup but then reads all the other files from hard drive?

or is to much for a novide to do ?

cheers jim





--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: Hard drive

Richard - VE7CVS
 

Yes, you can use the SD card just to get the machine started. I do this and use a Solid State Drive (SSD) for a couple of my Pis - especially for servers that are 'always on', the SD card eventually gets fried with too many writes to the same locations for log files and such.

There's a set of instructions here:

https://learn.adafruit.com/external-drive-as-raspberry-pi-root/what-youll-need

You basically copy the SD filesystem to the hard drive, then alter the /boot/cmdline.txt file on the SD card to point to the hard drive.

Not trivial, but not really difficult either. You're welcome to contact me if you have problems doing it.

- Richard, VE7CVS

On 8/31/16 8:22 AM, Jim wrote:

Now i have the dstar pi2 and thumbdv all working is there away i can transfer it all on to a harddrive (i have a 250g usb) so it uses the sd card for bootup but then reads all the other files from hard drive?

or is to much for a novide to do ?

cheers jim


Re: Hard drive

Jim <g7icd.jim@...>
 

Thank you John & Richard now booting from hard drive (via sd card)

cheers jim g7icd



New file uploaded to ambe@nw-digital-radio.groups.io

ambe@nw-digital-radio.groups.io Notification <ambe+notification@...>
 

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the ambe@nw-digital-radio.groups.io group.

File: ambesocketest.py

Uploaded By: John Hays

Description:
With AMBEserver running on the localhost, run this file with python ambesocketest.py If the AMBEserver is running properly, you will see repeating output of Server reply : a 0AMBE3000R Use control-C to escape/kill the test.

You can access this file at the URL:
https://nw-digital-radio.groups.io/g/ambe/files/ambesocketest.py

Cheers,
The Groups.io Team


AMBEserver Addendum updated

 

https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum

Now includes testing AMBEserver and accessing the AMBEServer from Windows, Linux, and MacOS


RPi3, DummyRepeater, ircDDBGateway

ne3k@...
 

So moving this over here from the Yahoo! group, I am having a devil of a time getting a RPi3 up and running to use DummyRepeater and ircDDBGateway with a PiDV Board.


I've followed the AMBE Wiki directions that John sent, and have gotten AMBEServer running on the Pi3, as proven by the ambesocketest.py script giving me the expected returns.


ps ax | more gives the following:


  PID TTY      STAT   TIME COMMAND

    1 ?        Ss     0:04 /sbin/init

    2 ?        S      0:00 [kthreadd]

    3 ?        S      0:00 [ksoftirqd/0]

    4 ?        S      0:00 [kworker/0:0]

    5 ?        S<     0:00 [kworker/0:0H]

    6 ?        S      0:00 [kworker/u8:0]

    7 ?        S      0:00 [rcu_sched]

    8 ?        S      0:00 [rcu_bh]

    9 ?        S      0:00 [migration/0]

   10 ?        S      0:00 [migration/1]

   11 ?        S      0:00 [ksoftirqd/1]

   12 ?        S      0:00 [kworker/1:0]

   13 ?        S<     0:00 [kworker/1:0H]

   14 ?        S      0:00 [migration/2]

   15 ?        S      0:00 [ksoftirqd/2]

   16 ?        S      0:00 [kworker/2:0]

   17 ?        S<     0:00 [kworker/2:0H]

   18 ?        S      0:00 [migration/3]

   19 ?        S      0:00 [ksoftirqd/3]

   20 ?        S      0:00 [kworker/3:0]

   21 ?        S<     0:00 [kworker/3:0H]

   22 ?        S      0:00 [kdevtmpfs]

   23 ?        S<     0:00 [netns]

   24 ?        S<     0:00 [perf]

   25 ?        S      0:00 [khungtaskd]

   26 ?        S<     0:00 [writeback]

   27 ?        S<     0:00 [crypto]

   28 ?        S<     0:00 [bioset]

   29 ?        S<     0:00 [kblockd]

   30 ?        S      0:00 [kworker/0:1]

   31 ?        S<     0:00 [rpciod]

   32 ?        S      0:00 [kswapd0]

   33 ?        S<     0:00 [vmstat]

   34 ?        S      0:00 [fsnotify_mark]

   35 ?        S<     0:00 [nfsiod]

   44 ?        S<     0:00 [kthrotld]

   45 ?        S      0:00 [kworker/1:1]

   46 ?        S<     0:00 [bioset]

   47 ?        S<     0:00 [bioset]

   48 ?        S<     0:00 [bioset]

   49 ?        S<     0:00 [bioset]

   50 ?        S<     0:00 [bioset]

   51 ?        S<     0:00 [bioset]

   52 ?        S<     0:00 [bioset]

   53 ?        S<     0:00 [bioset]

   54 ?        S<     0:00 [bioset]

   55 ?        S<     0:00 [bioset]

   56 ?        S<     0:00 [bioset]

   57 ?        S<     0:00 [bioset]

   58 ?        S<     0:00 [bioset]

   59 ?        S<     0:00 [bioset]

   60 ?        S<     0:00 [bioset]

   61 ?        S<     0:00 [bioset]

   62 ?        S<     0:00 [bioset]

   63 ?        S<     0:00 [bioset]

   64 ?        S<     0:00 [bioset]

   65 ?        S<     0:00 [bioset]

   66 ?        S<     0:00 [bioset]

   67 ?        S<     0:00 [bioset]

   68 ?        S<     0:00 [bioset]

   69 ?        S<     0:00 [bioset]

   70 ?        S<     0:00 [VCHIQ-0]

   71 ?        S<     0:00 [VCHIQr-0]

   72 ?        S<     0:00 [VCHIQs-0]

   73 ?        S<     0:00 [iscsi_eh]

   74 ?        S<     0:00 [dwc_otg]

   75 ?        S<     0:00 [DWC Notificatio]

   76 ?        S      0:00 [kworker/u8:1]

   77 ?        S      0:00 [irq/92-mmc1]

   78 ?        S<     0:00 [bioset]

   79 ?        S      0:00 [mmcqd/0]

   80 ?        S      0:00 [kworker/3:1]

   81 ?        S      0:00 [VCHIQka-0]

   82 ?        S<     0:00 [SMIO]

   83 ?        S<     0:00 [deferwq]

   84 ?        S      0:00 [kworker/u8:2]

   85 ?        S      0:00 [kworker/2:1]

   86 ?        S      0:00 [kworker/1:2]

   87 ?        S      0:00 [jbd2/mmcblk0p2-]

   88 ?        S<     0:00 [ext4-rsv-conver]

   89 ?        S<     0:00 [ipv6_addrconf]

  110 ?        S      0:00 [kworker/0:2]

  127 ?        S      0:00 [kworker/2:2]

  135 ?        Ss     0:00 /lib/systemd/systemd-journald

  137 ?        Ss     0:00 /lib/systemd/systemd-udevd

  229 ?        S<     0:00 [cfg80211]

  235 ?        S<     0:00 [brcmf_wq/mmc1:0]

  237 ?        S      0:00 [brcmf_wdog/mmc1]

  401 ?        S      0:00 [kworker/1:3]

  420 ?        Ss     0:00 /usr/sbin/cron -f

  421 ?        Ss     0:00 /lib/systemd/systemd-logind

  426 ?        Ss     0:00 avahi-daemon: running [compass.local]

  428 ?        Ss     0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

  430 ?        Ss     0:00 /sbin/dhcpcd -q -b

  443 ?        Ss     0:00 /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan0.pid -i wlan0 -D nl80211,wext -c /etc/wpa_supplicant/wpa_supplicant.conf

  455 ?        Ss     0:00 /usr/sbin/thd --daemon --triggers /etc/triggerhappy/triggers.d/ --socket /var/run/thd.socket --pidfile /var/run/thd.pid --user nobody /dev/input/event0 /dev/input/event1

  470 ?        S      0:00 avahi-daemon: chroot helper

  502 ?        S<     0:00 [kworker/1:1H]

  518 ?        Ssl    0:00 /usr/sbin/rsyslogd -n

  570 ?        Ss     0:00 /usr/sbin/sshd -D

  577 ?        Ssl    0:00 /usr/sbin/lightdm

  584 ?        Ss     0:00 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyS0 -r

  599 ?        S      0:00 [kworker/3:2]

  602 ?        Ss     0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:111

  643 tty1     Ss     0:00 /bin/login -f

  648 tty7     Ssl+   0:02 /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

  659 ?        Sl     0:00 lightdm --session-child 13 16

  667 ?        Ss     0:00 /lib/systemd/systemd --user

  670 ?        S      0:00 (sd-pam)

  673 ?        Ssl    0:00 /usr/bin/lxsession -s LXDE-pi -e LXDE

  697 ?        Ss     0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager

  700 ?        S      0:00 /usr/bin/dbus-launch --exit-with-session x-session-manager

  701 ?        Ss     0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

  709 ?        Sl     0:00 /usr/lib/gvfs/gvfsd

  713 ?        Sl     0:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes

  719 ?        S<     0:00 [kworker/0:1H]

  723 ?        S<     0:00 [kworker/u9:0]

  724 ?        S<     0:00 [hci0]

  725 ?        S<     0:00 [hci0]

  726 ?        S<     0:00 [kworker/u9:1]

  727 ?        S      0:00 /usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -

  728 ?        S<     0:00 [kworker/u9:2]

  732 ?        S<     0:00 [kworker/3:1H]

  734 ?        Ss     0:00 /usr/lib/bluetooth/bluetoothd

  756 ?        S      0:00 openbox --config-file /home/pi/.config/openbox/lxde-pi-rc.xml

  759 ?        Sl     0:00 lxpolkit

  761 ?        Sl     0:01 lxpanel --profile LXDE-pi

  764 ?        S      0:00 [kworker/0:3]

  766 ?        Sl     0:00 pcmanfm --desktop --profile LXDE-pi

  770 tty1     S+     0:00 -bash

  775 ?        Ssl    0:00 /usr/lib/policykit-1/polkitd --no-debug

  776 ?        Ss     0:00 /usr/bin/ssh-agent -s

  847 ?        Sl     0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor

  875 ?        Ssl    0:00 /usr/lib/udisks2/udisksd --no-debug

  909 ?        Sl     0:00 /usr/lib/gvfs/gvfs-goa-volume-monitor

  913 ?        Sl     0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor

  917 ?        Sl     0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor

  921 ?        Sl     0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor

  932 ?        Sl     0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.1 /org/gtk/gvfs/exec_spaw/0

  942 ?        Ssl    0:00 /usr/lib/menu-cache/menu-cached /tmp/.menu-cached-:0-pi

 1052 ?        Sl     0:01 lxterminal

 1053 ?        S      0:00 gnome-pty-helper

 1054 pts/0    Ss+    0:00 /bin/bash

 1088 ?        Ss     0:00 sshd: pi [priv]

 1095 ?        S      0:00 sshd: pi@pts/1

 1097 pts/1    Ss     0:00 -bash

 1107 pts/1    R+     0:00 ps ax

 1108 pts/1    S+     0:00 more

I can get DummyRepeater and ircDDBGateway to work, but when I tell DR that I want to use AMA0 (the only option via DV3000 Serial) it freezes when I restart it. 


Any ideas, cause I've done just about everything I can think of, and know how to do.


Thanks,

Geoff, NE3K


Re: RPi3, DummyRepeater, ircDDBGateway

 

When AMBEserver is running, you do not select a serial port, you select DV3000 network -- https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#DummyRepeater-for-Windows-or-Linux


On Sun, Sep 4, 2016 at 5:38 PM, <ne3k@...> wrote:

So moving this over here from the Yahoo! group, I am having a devil of a time getting a RPi3 up and running to use DummyRepeater and ircDDBGateway with a PiDV Board.


I've followed the AMBE Wiki directions that John sent, and have gotten AMBEServer running on the Pi3, as proven by the ambesocketest.py script giving me the expected returns.



I can get DummyRepeater and ircDDBGateway to work, but when I tell DR that I want to use AMA0 (the only option via DV3000 Serial) it freezes when I restart it. 


Any ideas, cause I've done just about everything I can think of, and know how to do.


Thanks,

Geoff, NE3K
_._,_.

--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: RPi3, DummyRepeater, ircDDBGateway

ne3k@...
 

Ok, I thought that was only when I was running them from a different computer on the network.


I'll give it a try again.


PiDV - Pinout / jumpers for UART

Tom Cichowicz <tcichowicz@...>
 

Looking for the information on the Jumpers to be used to utilize the UART on the PiDV

   if anyone has this information or a link to it it would be appreciated.


The PiDV™ is designed to use the GPIO UART pins on a Raspberry Pi, Raspberry Pi 2, Raspberry Pi 3, and compatible devices such as the Odroid C1, to provide access to AMBE encoding and decoding.  It can be adapted to other similar devices using jumper wires to connect the UART.


Re: PiDV - Pinout / jumpers for UART

 

Northwest digital radio site look under products.

Don
WB5EKU



On September 7, 2016, at 7:02 AM, Tom Cichowicz <tcichowicz@...> wrote:


Looking for the information on the Jumpers to be used to utilize the UART on the PiDV

   if anyone has this information or a link to it it would be appreciated.


The PiDV™ is designed to use the GPIO UART pins on a Raspberry Pi, Raspberry Pi 2, Raspberry Pi 3, and compatible devices such as the Odroid C1, to provide access to AMBE encoding and decoding.  It can be adapted to other similar devices using jumper wires to connect the UART.


Re: PiDV - Pinout / jumpers for UART

Tom Cichowicz <tcichowicz@...>
 

Thanks - got it.

On Wed, Sep 7, 2016 at 10:54 AM, Donald Jacob <wb5eku@...> wrote:

Northwest digital radio site look under products.

Don
WB5EKU



On September 7, 2016, at 7:02 AM, Tom Cichowicz <tcichowicz@...> wrote:


Looking for the information on the Jumpers to be used to utilize the UART on the PiDV

   if anyone has this information or a link to it it would be appreciated.


The PiDV™ is designed to use the GPIO UART pins on a Raspberry Pi, Raspberry Pi 2, Raspberry Pi 3, and compatible devices such as the Odroid C1, to provide access to AMBE encoding and decoding.  It can be adapted to other similar devices using jumper wires to connect the UART.




--
Mobile: (941) 888-4519
Ham   : KM4VIG

~TomC.


PI3 and DV3000U

Ian
 

Hello,

While I try and figure out were I have gone wrong I thought I'd post this just in case someone else has experienced it.

As you can see the ambeserver starts but falls over a few seconds later.

Regards,

Ian.. 


pi@compass02:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled)

   Active: active (running) since Wed 2016-09-14 14:56:17 BST; 3s ago

  Process: 999 ExecStartPre=/bin/chmod 0660 /dev/%i (code=exited, status=0/SUCCESS)

  Process: 995 ExecStartPre=/bin/chgrp dialout /dev/%i (code=exited, status=0/SUCCESS)

 Main PID: 1003 (AMBEserver)

   CGroup: /system.slice/system-ambeserver.slice/ambeserver@...

           └─1003 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyUSB0


Sep 14 14:56:17 compass02 systemd[1]: Started DV3000 Daemon.

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Starting...

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Opened serial port /dev/ttyUSB0 at 230400 bps.

pi@compass02:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled)

   Active: failed (Result: exit-code) since Wed 2016-09-14 14:56:50 BST; 1s ago

  Process: 1003 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/%i $AMBESERVER_FLAGS (code=exited, status=1/FAILURE)

  Process: 999 ExecStartPre=/bin/chmod 0660 /dev/%i (code=exited, status=0/SUCCESS)

  Process: 995 ExecStartPre=/bin/chgrp dialout /dev/%i (code=exited, status=0/SUCCESS)

 Main PID: 1003 (code=exited, status=1/FAILURE)


Sep 14 14:56:17 compass02 systemd[1]: Started DV3000 Daemon.

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Starting...

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Opened serial port /dev/ttyUSB0 at 230400 bps.

Sep 14 14:56:50 compass02 AMBEserver[1003]: AMBEserver: Couldn't find start byte in serial data

Sep 14 14:56:50 compass02 AMBEserver[1003]: AMBEserver: error receiving response to reset

Sep 14 14:56:50 compass02 AMBEserver[1003]: AMBEserver: Could not initialize the DV3K!

Sep 14 14:56:50 compass02 systemd[1]: ambeserver@...: main process exited, code=exited, status=1/FAILURE

Sep 14 14:56:50 compass02 systemd[1]: Unit ambeserver@... entered failed state.

Sep 14 14:56:50 compass02 systemd[1]: Triggering OnFailure= dependencies of ambeserver@....



Re: PI3 and DV3000U

ne3k@...
 

Ian-

I had quite the time with a Pi3 and DV3000 board. This set of directions worked for me, and also worked for my friend I sent them to, KI7SI.

Best of luck, let me know how it goes.

73,

Geoff, NE3K



Ok, first thing:


You have to use the 'Compass' distro I have found.

Once you get that done:


then:

sudo apt-get install ircddbgateway ircddbgatewayd dummrepeater

sudo ircddbgatewayconfig

Under the Gateway tab, Type - Dongle; Callsign - KI7SI; Local HB Address - 127.0.0.1, then whatever you want to enter for your QTH.

Under the Repeater 1 Tab, Band - B (apparently on a dongle it doesn't matter); Type - Homebrew; Address - 127.0.0.1; Port 20011; Reflector - IF you want it to connect to a particular reflector at startup. I set mine to REF062C since that is what the local D-Star machine is on.

Under the ircddbgateway network 1 tab, set it for 'Enabled', 'rr.openquad.net', 'KI7SI'.

Under the ircddbgateway network 2 tab, set it for 'Enabled', 'ircddb.dstar.su', 'KI7SI'

Under the D-PRS Tab, D-PRS - Enabled; Hostname - rotate-aprs2.net; Port 14580

DExtra - Enabled; Max Dongles - 5

D-Plus - Enabled; Max Dongles - 5; Login - KI7SI

DCS and CCS - Both Enabled; Server - CCS704 worked for me

Don't do anything in the StarNet tabs

Remote - if you want to control it via an app on your phone, you need to set this up, otherwise you can leave it alone

Misc - English (US), enable all other settings


'Save' the settings under the 'File' menu.


 
 
When setting up dummyrepeater, you have to select 'DV3000 Network' and the set the loopback address under the 'Dongle' tab.
 
 
Callsign Tab - fill in your call. I put '3000' after the slash since I'm using the DV3000
 
Sound Card - select the headset for both
 
Dongle - Type - DV3000 Network; Device - none; Address 127.0.0.1; Port - 2460
 
Network - Gateway address - 127.0.0.1; Gateway Port - 20010; Local Address - 127.0.0.1; Local Port 20011
 
Controller and Timeout you can leave as is
 
Message - Whatever message you want to come up when you transmit.
 
 
 
 
To make the wlan0 and wireless work on the Pi3 with Compass, make sure your /etc/network/interfaces file looks like this:
 

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

iface eth0 inet manual

allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

 
 
 
To set a static IP with this setup, make sure /etc/dhcpcd.conf has this language with your settings at the end of the file:

Interface wlan0
static ip_address=xxx.xxx.xxx.xxx/24
static routers=xxx.xxx.xxx.xxx
static domain_name_servers=xxx.xxx.xxx.xxx




To get it to associate with your wireless, your /etc/wpa_supplicant/wpa_supplicant.conf file looks like this:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US

network={
ssid="[Your SSID]"
psk="[Your Password]"
key_mgmt=[Your Encryption Level]
}

 
sudo reboot
 
under 'Menu' go to 'Run' then 'sudo dummyrepeater' and 'sudo ircddbgateway'.
 
It will take a minute for it to get up and running. To connect to whatever reflector you want, in the 'UR' block type REFXXX[ABCD]CL, then switch back to 'CQCQCQ'. You should hear a connect message then a beep. 
 
After that, hit transmit and you should be cooking.
 
 
I have not been able to get ircddbgatewayd to run at startup automatically, but it works fine if I do it in a terminal window. Still waiting on an answer for that problem. Otherwise this should take care of getting it to work for you.
 
There is also a script/procedure for updating the DExtra hosts file, I have to dig that out for you.
 
 
Let me know if it works ok.
 
 
Geoff
 



From: "Ian" <gm4upx@...>
To: ambe@nw-digital-radio.groups.io
Sent: Wednesday, September 14, 2016 10:14:24 AM
Subject: [ambe] PI3 and DV3000U

Hello,

While I try and figure out were I have gone wrong I thought I'd post this just in case someone else has experienced it.

As you can see the ambeserver starts but falls over a few seconds later.

Regards,

Ian.. 


pi@compass02:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled)

   Active: active (running) since Wed 2016-09-14 14:56:17 BST; 3s ago

  Process: 999 ExecStartPre=/bin/chmod 0660 /dev/%i (code=exited, status=0/SUCCESS)

  Process: 995 ExecStartPre=/bin/chgrp dialout /dev/%i (code=exited, status=0/SUCCESS)

 Main PID: 1003 (AMBEserver)

   CGroup: /system.slice/system-ambeserver.slice/ambeserver@...

           └─1003 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyUSB0


Sep 14 14:56:17 compass02 systemd[1]: Started DV3000 Daemon.

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Starting...

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Opened serial port /dev/ttyUSB0 at 230400 bps.

pi@compass02:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled)

   Active: failed (Result: exit-code) since Wed 2016-09-14 14:56:50 BST; 1s ago

  Process: 1003 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/%i $AMBESERVER_FLAGS (code=exited, status=1/FAILURE)

  Process: 999 ExecStartPre=/bin/chmod 0660 /dev/%i (code=exited, status=0/SUCCESS)

  Process: 995 ExecStartPre=/bin/chgrp dialout /dev/%i (code=exited, status=0/SUCCESS)

 Main PID: 1003 (code=exited, status=1/FAILURE)


Sep 14 14:56:17 compass02 systemd[1]: Started DV3000 Daemon.

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Starting...

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Opened serial port /dev/ttyUSB0 at 230400 bps.

Sep 14 14:56:50 compass02 AMBEserver[1003]: AMBEserver: Couldn't find start byte in serial data

Sep 14 14:56:50 compass02 AMBEserver[1003]: AMBEserver: error receiving response to reset

Sep 14 14:56:50 compass02 AMBEserver[1003]: AMBEserver: Could not initialize the DV3K!

Sep 14 14:56:50 compass02 systemd[1]: ambeserver@...: main process exited, code=exited, status=1/FAILURE

Sep 14 14:56:50 compass02 systemd[1]: Unit ambeserver@... entered failed state.

Sep 14 14:56:50 compass02 systemd[1]: Triggering OnFailure= dependencies of ambeserver@....




Re: PI3 and DV3000U

 

From your error log, you are running at 230400 baud. If your ThumbDV is new, it runs at 460800.

Make sure it is at /dev/ttyUSB0 and modify the configuration as per https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum


On Sep 14, 2016 07:20, "Ian" <gm4upx@...> wrote:

Hello,

While I try and figure out were I have gone wrong I thought I'd post this just in case someone else has experienced it.

As you can see the ambeserver starts but falls over a few seconds later.

Regards,

Ian.. 


pi@compass02:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled)

   Active: active (running) since Wed 2016-09-14 14:56:17 BST; 3s ago

  Process: 999 ExecStartPre=/bin/chmod 0660 /dev/%i (code=exited, status=0/SUCCESS)

  Process: 995 ExecStartPre=/bin/chgrp dialout /dev/%i (code=exited, status=0/SUCCESS)

 Main PID: 1003 (AMBEserver)

   CGroup: /system.slice/system-ambeserver.slice/ambeserver@ttyUSB0.service

           └─1003 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyUSB0


Sep 14 14:56:17 compass02 systemd[1]: Started DV3000 Daemon.

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Starting...

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Opened serial port /dev/ttyUSB0 at 230400 bps.

pi@compass02:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled)

   Active: failed (Result: exit-code) since Wed 2016-09-14 14:56:50 BST; 1s ago

  Process: 1003 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/%i $AMBESERVER_FLAGS (code=exited, status=1/FAILURE)

  Process: 999 ExecStartPre=/bin/chmod 0660 /dev/%i (code=exited, status=0/SUCCESS)

  Process: 995 ExecStartPre=/bin/chgrp dialout /dev/%i (code=exited, status=0/SUCCESS)

 Main PID: 1003 (code=exited, status=1/FAILURE)


Sep 14 14:56:17 compass02 systemd[1]: Started DV3000 Daemon.

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Starting...

Sep 14 14:56:17 compass02 AMBEserver[1003]: AMBEserver: Opened serial port /dev/ttyUSB0 at 230400 bps.

Sep 14 14:56:50 compass02 AMBEserver[1003]: AMBEserver: Couldn't find start byte in serial data

Sep 14 14:56:50 compass02 AMBEserver[1003]: AMBEserver: error receiving response to reset

Sep 14 14:56:50 compass02 AMBEserver[1003]: AMBEserver: Could not initialize the DV3K!

Sep 14 14:56:50 compass02 systemd[1]: ambeserver@...: main process exited, code=exited, status=1/FAILURE

Sep 14 14:56:50 compass02 systemd[1]: Unit ambeserver@... entered failed state.

Sep 14 14:56:50 compass02 systemd[1]: Triggering OnFailure= dependencies of ambeserver@....



Re: PI3 and DV3000U

Ian
 

Hello Geoff,

Thanks for the pointers, I have gone through the download/setup etc with a fresh card and I am still experiencing a problem. It'll be something simple I imagine, perhaps because I am only running dummyrepeater, as an example. Incidentally my Pi3 card did not run on a Pi2B ; I'll keep looking.


Hello John,

I double checked the baud rate and I get an error ( wrong baud rate ) when I enter 460800 so my ThumbDV is an " old " one and it is at /dev/ttyUSB0

My first install was with Compass lite on which I had  Direwolf running; I followed the install instructions to use dl5di github and ambetest3.py ( maybe not the correct name as typing from memory <smile> ) responded correctly although dummyrepeater needed a GUI installed so I downloaded the Compass GUI.  I'm assuming the ambeserver runs on its own and doesn't need dummyrepeater, unfortunately I get no response when running python ambesocketest.py.

Regards,

Ian..


Re: PI3 and DV3000U

 

Please use the instructions at https://nw-digital-radio.groups.io/g/ambe/wiki/Installing-AMBEserver-on-a-Raspberry-Pi-and-ThumbDV%E2%84%A2 -- the Github instructions are out of date, though you could use the Python scripts for testing.  ambesockettest.py tests the server when it is up and running, the scripts on Github are for testing the port 'raw'.

On Wed, Sep 14, 2016 at 1:45 PM, Ian <gm4upx@...> wrote:

Hello Geoff,

Thanks for the pointers, I have gone through the download/setup etc with a fresh card and I am still experiencing a problem. It'll be something simple I imagine, perhaps because I am only running dummyrepeater, as an example. Incidentally my Pi3 card did not run on a Pi2B ; I'll keep looking.


Hello John,

I double checked the baud rate and I get an error ( wrong baud rate ) when I enter 460800 so my ThumbDV is an " old " one and it is at /dev/ttyUSB0

My first install was with Compass lite on which I had  Direwolf running; I followed the install instructions to use dl5di github and ambetest3.py ( maybe not the correct name as typing from memory <smile> ) responded correctly although dummyrepeater needed a GUI installed so I downloaded the Compass GUI.  I'm assuming the ambeserver runs on its own and doesn't need dummyrepeater, unfortunately I get no response when running python ambesocketest.py.

Regards,

Ian..




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Newbie needs some pointers

Thomas Edmonson
 

I'm in the process of setting up the following and I needs some gaps in my understanding filled.


Here's the high level view:


1.    I have a Raspberry PI 3 with a DV3000.

2.    I loaded the following software:

        A. Compass

        B. IRCDDBGATEWAY

        C. Dummyrepeater

   What I want to do is to be able to VNC into my Raspberry with another PC or MAC and then using the remote device

enter the Dstar network. The Gateway seems to be functioning at some level. I see:

IRCDB = connected

D-PRS= active

Repeater 1 = AG5GY  B Not Linked

Everything seems to be ok until I try to configure Dummy Repeater. When I try to configure it I only get "NONE" as a choice

under the sound-card field.  It then won't let me save the config items I did change because the sound-card is not set

Any suggestions?


Re: Newbie needs some pointers

 

Tom,

It took a minute to figure out what you were trying to do.  There is no 2-way soundcard on the Raspberry Pi, unless you add one, e.g. a USB headset or sound FOB.

If you are coming in from another computer, your better choice is to install DummyRepeater on your Windows box or Buster on your Mac, and access the AMBEserver over the network. (No VNC necessary -- if you are going to connect for a disply, you might want to use xrdp with Remote Desktop).

Buster doesn't require ircddb on the Mac, just point it at your Raspberry Pi with AMBEserver running (DV3000 network) https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#Buster-for-MacOS

On Windows, put it at the AMBEserver (DV3000 Network) and point it the Raspberry Pi for ircddbgateway. https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#DummyRepeater-for-Windows-or-Linux  


BTW, I will at DCC the next few days, so availability for support will be at a minimum.

On Wed, Sep 14, 2016 at 6:23 PM, <tom@...> wrote:

I'm in the process of setting up the following and I needs some gaps in my understanding filled.


Here's the high level view:


1.    I have a Raspberry PI 3 with a DV3000.

2.    I loaded the following software:

        A. Compass

        B. IRCDDBGATEWAY

        C. Dummyrepeater

   What I want to do is to be able to VNC into my Raspberry with another PC or MAC and then using the remote device

enter the Dstar network. The Gateway seems to be functioning at some level. I see:

IRCDB = connected

D-PRS= active

Repeater 1 = AG5GY  B Not Linked

Everything seems to be ok until I try to configure Dummy Repeater. When I try to configure it I only get "NONE" as a choice

under the sound-card field.  It then won't let me save the config items I did change because the sound-card is not set

Any suggestions?




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223