ambeserver-install -Has anyone run the Simple Install lately?


ve3mic@...
 

I'm getting the following errors when I 'sudo apt-get install git' on a fresh install of > 2021-03-04-raspios-buster-armhf-lite

E: Invalid archive signature
E: Internal error, could not locate member control.tar.{zstlz4gzxzbz2lzma}
E: Prior errors apply to /var/cache/apt/archives/libcurl3-gnutls_7.64.0-4+deb10u2_armhf.deb
E: Invalid archive signature
E: Internal error, could not locate member control.tar.{zstlz4gzxzbz2lzma}
E: Prior errors apply to /var/cache/apt/archives/liberror-perl_0.17027-2_all.deb
E: Invalid archive signature
E: Internal error, could not locate member control.tar.{zstlz4gzxzbz2lzma}
E: Prior errors apply to /var/cache/apt/archives/git-man_1%3a2.20.1-2+deb10u3_all.deb
E: Invalid archive signature
E: Internal error, could not locate member control.tar.{zstlz4gzxzbz2lzma}
E: Prior errors apply to /var/cache/apt/archives/git_1%3a2.20.1-2+deb10u3_armhf.deb
debconf: apt-extracttemplates failed: No such file or directory
dpkg-deb: error: '/var/cache/apt/archives/libcurl3-gnutls_7.64.0-4+deb10u2_armhf.deb' is not a Debian format archive
dpkg: error processing archive /var/cache/apt/archives/libcurl3-gnutls_7.64.0-4+deb10u2_armhf.deb (--unpack):
 dpkg-deb --control subprocess returned error exit status 2
dpkg-deb: error: '/var/cache/apt/archives/liberror-perl_0.17027-2_all.deb' is not a Debian format archive
dpkg: error processing archive /var/cache/apt/archives/liberror-perl_0.17027-2_all.deb (--unpack):
 dpkg-deb --control subprocess returned error exit status 2
dpkg-deb: error: '/var/cache/apt/archives/git-man_1%3a2.20.1-2+deb10u3_all.deb' is not a Debian format archive
dpkg: error processing archive /var/cache/apt/archives/git-man_1%3a2.20.1-2+deb10u3_all.deb (--unpack):
 dpkg-deb --control subprocess returned error exit status 2
dpkg-deb: error: '/var/cache/apt/archives/git_1%3a2.20.1-2+deb10u3_armhf.deb' is not a Debian format archive
dpkg: error processing archive /var/cache/apt/archives/git_1%3a2.20.1-2+deb10u3_armhf.deb (--unpack):
 dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libcurl3-gnutls_7.64.0-4+deb10u2_armhf.deb
 /var/cache/apt/archives/liberror-perl_0.17027-2_all.deb
 /var/cache/apt/archives/git-man_1%3a2.20.1-2+deb10u3_all.deb
 /var/cache/apt/archives/git_1%3a2.20.1-2+deb10u3_armhf.deb

73 & thanks.
de Mike  VE3MIC


 

Hi Mike,

Just went through the install steps on my Pi 400 to verify.  

It looks like you may be having problems with apt ... did you try a sudo apt update before the install attempt? If that doesn't do it, try sudo apt purge git && sudo apt install git


On Wed, May 5, 2021 at 2:45 PM <ve3mic@...> wrote:
I'm getting the following errors when I 'sudo apt-get install git' on a fresh install of > 2021-03-04-raspios-buster-armhf-lite

E: Invalid archive signature
E: Internal error, could not locate member control.tar.{zstlz4gzxzbz2lzma}
E: Prior errors apply to /var/cache/apt/archives/libcurl3-gnutls_7.64.0-4+deb10u2_armhf.deb
E: Invalid archive signature
E: Internal error, could not locate member control.tar.{zstlz4gzxzbz2lzma}
E: Prior errors apply to /var/cache/apt/archives/liberror-perl_0.17027-2_all.deb
E: Invalid archive signature
E: Internal error, could not locate member control.tar.{zstlz4gzxzbz2lzma}
E: Prior errors apply to /var/cache/apt/archives/git-man_1%3a2.20.1-2+deb10u3_all.deb
E: Invalid archive signature
E: Internal error, could not locate member control.tar.{zstlz4gzxzbz2lzma}
E: Prior errors apply to /var/cache/apt/archives/git_1%3a2.20.1-2+deb10u3_armhf.deb
debconf: apt-extracttemplates failed: No such file or directory
dpkg-deb: error: '/var/cache/apt/archives/libcurl3-gnutls_7.64.0-4+deb10u2_armhf.deb' is not a Debian format archive
dpkg: error processing archive /var/cache/apt/archives/libcurl3-gnutls_7.64.0-4+deb10u2_armhf.deb (--unpack):
 dpkg-deb --control subprocess returned error exit status 2
dpkg-deb: error: '/var/cache/apt/archives/liberror-perl_0.17027-2_all.deb' is not a Debian format archive
dpkg: error processing archive /var/cache/apt/archives/liberror-perl_0.17027-2_all.deb (--unpack):
 dpkg-deb --control subprocess returned error exit status 2
dpkg-deb: error: '/var/cache/apt/archives/git-man_1%3a2.20.1-2+deb10u3_all.deb' is not a Debian format archive
dpkg: error processing archive /var/cache/apt/archives/git-man_1%3a2.20.1-2+deb10u3_all.deb (--unpack):
 dpkg-deb --control subprocess returned error exit status 2
dpkg-deb: error: '/var/cache/apt/archives/git_1%3a2.20.1-2+deb10u3_armhf.deb' is not a Debian format archive
dpkg: error processing archive /var/cache/apt/archives/git_1%3a2.20.1-2+deb10u3_armhf.deb (--unpack):
 dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libcurl3-gnutls_7.64.0-4+deb10u2_armhf.deb
 /var/cache/apt/archives/liberror-perl_0.17027-2_all.deb
 /var/cache/apt/archives/git-man_1%3a2.20.1-2+deb10u3_all.deb
 /var/cache/apt/archives/git_1%3a2.20.1-2+deb10u3_armhf.deb

73 & thanks.
de Mike  VE3MIC



--
John D. Hays
Kingston, WA
K7VE / WRJT-215

 


ve3mic@...
 

Thanks John.
I may have a bad SD card... I'm trying (another) new one (It won't even format anymore).
I suspect that the Raspberry Pi Foundation's memory cards aren't 100% QC'd.


VE3MIC
 

Almost there...(it was a bad SD card) however, I'm running into an error when I run 'sudo systemctl status ambeserver@ttyAMA0'

ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2021-05-05 22:00:11 EDT; 41s ago
  Process: 507 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=0/SUCCESS)
  Process: 508 ExecStartPre=/bin/chmod 0660 /dev/ttyAMA0 (code=exited, status=0/SUCCESS)
  Process: 509 ExecStart=/usr/local/sbin/AMBEserver -p ${UDP_PORT} -i /dev/ttyAMA0 $AMBESERVER_FLAGS (code=exited, status=1/FAILURE)
 Main PID: 509 (code=exited, status=1/FAILURE)
 
May 05 22:00:11 AMBEServer systemd[1]: Starting AMBEserver Daemon...
May 05 22:00:11 AMBEServer systemd[1]: Started AMBEserver Daemon.
May 05 22:00:11 AMBEServer AMBEserver[509]: AMBEserver: Starting...
May 05 22:00:11 AMBEServer AMBEserver[509]: AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.
May 05 22:00:11 AMBEServer AMBEserver[509]: AMBEserver: Unable to open GPIO export interface: Permission denied
May 05 22:00:11 AMBEServer AMBEserver[509]: AMBEserver: Could not initialize the DV3K!
May 05 22:00:11 AMBEServer systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAILURE
May 05 22:00:11 AMBEServer systemd[1]: ambeserver@...: Failed with result 'exit-code'.
May 05 22:00:11 AMBEServer systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.


 

So what device are you trying to access?


On Wed, May 5, 2021, 19:29 VE3MIC via groups.io <ve3mic=yahoo.com@groups.io> wrote:
Almost there...(it was a bad SD card) however, I'm running into an error when I run 'sudo systemctl status ambeserver@ttyAMA0'

ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2021-05-05 22:00:11 EDT; 41s ago
  Process: 507 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=0/SUCCESS)
  Process: 508 ExecStartPre=/bin/chmod 0660 /dev/ttyAMA0 (code=exited, status=0/SUCCESS)
  Process: 509 ExecStart=/usr/local/sbin/AMBEserver -p ${UDP_PORT} -i /dev/ttyAMA0 $AMBESERVER_FLAGS (code=exited, status=1/FAILURE)
 Main PID: 509 (code=exited, status=1/FAILURE)
 
May 05 22:00:11 AMBEServer systemd[1]: Starting AMBEserver Daemon...
May 05 22:00:11 AMBEServer systemd[1]: Started AMBEserver Daemon.
May 05 22:00:11 AMBEServer AMBEserver[509]: AMBEserver: Starting...
May 05 22:00:11 AMBEServer AMBEserver[509]: AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.
May 05 22:00:11 AMBEServer AMBEserver[509]: AMBEserver: Unable to open GPIO export interface: Permission denied
May 05 22:00:11 AMBEServer AMBEserver[509]: AMBEserver: Could not initialize the DV3K!
May 05 22:00:11 AMBEServer systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAILURE
May 05 22:00:11 AMBEServer systemd[1]: ambeserver@...: Failed with result 'exit-code'.
May 05 22:00:11 AMBEServer systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.


VE3MIC
 

The DV3000/PiDV. I was planning on doing a short segment about AMBE Server on the RPi, since it's been a while since I've done anything with AMBE on Linux.
I'm going to demonstrate with the ThumbDV after I get the PiDV running


Mike Moore
 

I am migrating my ambe server from compass to 2021-03-04-raspios-buster-armhf-lite.  I verified that my ThumbDV is working on windows.  When I run the installation script it ends as follows:

 
etc/udev/rules.d:
99-thumbdv.rules
ls: cannot access '/dev/ThumbDV': No such file or directory
Endabling ThumbDV™ ...
Job for ambeserver@... failed because the control process exited with error code.
See "systemctl status ambeserver@..." and "journalctl -xe" for details.
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2021-06-18 15:09:22 EDT; 1s ago

Next I ran

pi@ambeserver:~/ambeserver-install/etc/udev/rules.d $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2021-06-18 15:09:22 EDT; 15min ago
 
Jun 18 15:09:22 ambeserver systemd[1]: Starting AMBEserver Daemon...
Jun 18 15:09:22 ambeserver chgrp[3280]: /bin/chgrp: cannot access '/dev/ThumbDV': No such file or dir
Jun 18 15:09:22 ambeserver systemd[1]: ambeserver@...: Control process exited, code=exite
Jun 18 15:09:22 ambeserver systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Jun 18 15:09:22 ambeserver systemd[1]: Failed to start AMBEserver Daemon.
Jun 18 15:09:22 ambeserver systemd[1]: ambeserver@...: Triggering OnFailure= dependencies

Next I Ran 

pi@ambeserver:~/ambeserver-install/etc/udev/rules.d $ sudo journalctl -xe
--
-- A start job for unit dev-ThumbDV.device has finished with a failure.
--
-- The job identifier is 1836 and the job result is timeout.
Jun 18 15:10:52 ambeserver systemd[1]: Dependency failed for Serial Getty on ThumbDV.
-- Subject: A start job for unit serial-getty@... has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit serial-getty@... has finished with a failure.
--
-- The job identifier is 1778 and the job result is dependency.
Jun 18 15:10:52 ambeserver systemd[1]: serial-getty@...: Job serial-getty@...
Jun 18 15:10:52 ambeserver systemd[1]: dev-ThumbDV.device: Job dev-ThumbDV.device/start failed with r
Jun 18 15:17:01 ambeserver CRON[3301]: pam_unix(cron:session): session opened for user root by (uid=0
Jun 18 15:17:01 ambeserver CRON[3302]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 18 15:17:01 ambeserver CRON[3301]: pam_unix(cron:session): session closed for user root
Jun 18 15:21:15 ambeserver sudo[3237]: pam_unix(sudo:session): session closed for user root
Jun 18 15:24:55 ambeserver sudo[3329]:       pi : TTY=pts/0 ; PWD=/home/pi/ambeserver-install/etc/ude
Jun 18 15:24:55 ambeserver sudo[3329]: pam_unix(sudo:session): session opened for user root by pi(uid
Jun 18 15:25:25 ambeserver sudo[3329]: pam_unix(sudo:session): session closed for user root
Jun 18 15:27:33 ambeserver sudo[3332]:       pi : TTY=pts/0 ; PWD=/home/pi/ambeserver-install/etc/ude
Jun 18 15:27:33 ambeserver sudo[3332]: pam_unix(sudo:session): session opened for user root by pi(uid

I also tried  sudo apt update before the install attempt? And sudo apt purge git && sudo apt install git

Recommendations anyone?
 73, KC2NM
 
 
 


 

Make sure the rule is in place
 ls /etc/udev/rules.d/99-thumbdv.rules
/etc/udev/rules.d/99-thumbdv.rules
Make sure udev is running
 systemctl status udev.service

Unplug the ThumbDV™ and plug it back in,  see if /dev/ThumbDV shows (ls -l /dev/ThumbDV)
If not find out what terminal is created when plugging in the ThumbDV™
Unplug
ls /dev/ttyUSB*
Plug-in
ls /dev/ttyUSB*

Take the /dev/ttyUSBx  (eg. /dev/ttyUSB0) and run
udevadm info /dev/ttyUSB0
And look to see that it lists ThumbDV for a model
Use the test script as described at the end of https://github.com/nwdigitalradio/ambeserver-install

Sometimes you need to restart udev and/or remove and reinsert the ThumbDV™ on a new install.



On Fri, Jun 18, 2021 at 12:31 PM Mike Moore <mikemoore@...> wrote:
I am migrating my ambe server from compass to 2021-03-04-raspios-buster-armhf-lite.  I verified that my ThumbDV is working on windows.  When I run the installation script it ends as follows:

 
etc/udev/rules.d:
99-thumbdv.rules
ls: cannot access '/dev/ThumbDV': No such file or directory
Endabling ThumbDV™ ...
Job for ambeserver@... failed because the control process exited with error code.
See "systemctl status ambeserver@..." and "journalctl -xe" for details.
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2021-06-18 15:09:22 EDT; 1s ago

Next I ran

pi@ambeserver:~/ambeserver-install/etc/udev/rules.d $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2021-06-18 15:09:22 EDT; 15min ago
 
Jun 18 15:09:22 ambeserver systemd[1]: Starting AMBEserver Daemon...
Jun 18 15:09:22 ambeserver chgrp[3280]: /bin/chgrp: cannot access '/dev/ThumbDV': No such file or dir
Jun 18 15:09:22 ambeserver systemd[1]: ambeserver@...: Control process exited, code=exite
Jun 18 15:09:22 ambeserver systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Jun 18 15:09:22 ambeserver systemd[1]: Failed to start AMBEserver Daemon.
Jun 18 15:09:22 ambeserver systemd[1]: ambeserver@...: Triggering OnFailure= dependencies

Next I Ran 

pi@ambeserver:~/ambeserver-install/etc/udev/rules.d $ sudo journalctl -xe
--
-- A start job for unit dev-ThumbDV.device has finished with a failure.
--
-- The job identifier is 1836 and the job result is timeout.
Jun 18 15:10:52 ambeserver systemd[1]: Dependency failed for Serial Getty on ThumbDV.
-- Subject: A start job for unit serial-getty@... has failed
-- Defined-By: systemd
--
-- A start job for unit serial-getty@... has finished with a failure.
--
-- The job identifier is 1778 and the job result is dependency.
Jun 18 15:10:52 ambeserver systemd[1]: serial-getty@...: Job serial-getty@...
Jun 18 15:10:52 ambeserver systemd[1]: dev-ThumbDV.device: Job dev-ThumbDV.device/start failed with r
Jun 18 15:17:01 ambeserver CRON[3301]: pam_unix(cron:session): session opened for user root by (uid=0
Jun 18 15:17:01 ambeserver CRON[3302]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 18 15:17:01 ambeserver CRON[3301]: pam_unix(cron:session): session closed for user root
Jun 18 15:21:15 ambeserver sudo[3237]: pam_unix(sudo:session): session closed for user root
Jun 18 15:24:55 ambeserver sudo[3329]:       pi : TTY=pts/0 ; PWD=/home/pi/ambeserver-install/etc/ude
Jun 18 15:24:55 ambeserver sudo[3329]: pam_unix(sudo:session): session opened for user root by pi(uid
Jun 18 15:25:25 ambeserver sudo[3329]: pam_unix(sudo:session): session closed for user root
Jun 18 15:27:33 ambeserver sudo[3332]:       pi : TTY=pts/0 ; PWD=/home/pi/ambeserver-install/etc/ude
Jun 18 15:27:33 ambeserver sudo[3332]: pam_unix(sudo:session): session opened for user root by pi(uid

I also tried  sudo apt update before the install attempt? And sudo apt purge git && sudo apt install git

Recommendations anyone?
 73, KC2NM
 
 
 



--
John D. Hays
Kingston, WA
K7VE / WRJT-215

 


Mike Moore
 

On Fri, Jun 18, 2021 at 03:42 PM, John D Hays - K7VE wrote:
udevadm info /dev/ttyUSB0


Mike Moore
 

John, thank you for the speedy reply.  I did not see the name ThumbDV listed as the model shown below.
73, KC2NM

pi@ambeserver:~ $ udevadm info /dev/ttyUSB0
P: /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/ttyUSB0/tty/ttyUSB0
N: ttyUSB0
L: 0
S: serial/by-path/platform-3f980000.usb-usb-0:1.4:1.0-port0
S: serial/by-id/usb-FTDI_FT230X_Basic_UART_DN00WOUP-if00-port0
E: DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/ttyUSB0/tty/ttyUSB0
E: DEVNAME=/dev/ttyUSB0
E: MAJOR=188
E: MINOR=0
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=269956600767
E: ID_VENDOR=FTDI
E: ID_VENDOR_ENC=FTDI
E: ID_VENDOR_ID=0403
E: ID_MODEL=FT230X_Basic_UART
E: ID_MODEL_ENC=FT230X\x20Basic\x20UART
E: ID_MODEL_ID=6015
E: ID_REVISION=1000
E: ID_SERIAL=FTDI_FT230X_Basic_UART_DN00WOUP
E: ID_SERIAL_SHORT=DN00WOUP
E: ID_TYPE=generic
E: ID_BUS=usb
E: ID_USB_INTERFACES=:ffffff:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=ftdi_sio
E: ID_VENDOR_FROM_DATABASE=Future Technology Devices International, Ltd
E: ID_MODEL_FROM_DATABASE=Bridge(I2C/SPI/UART/FIFO)
E: ID_PATH=platform-3f980000.usb-usb-0:1.4:1.0
E: ID_PATH_TAG=platform-3f980000_usb-usb-0_1_4_1_0
E: DEVLINKS=/dev/serial/by-path/platform-3f980000.usb-usb-0:1.4:1.0-port0 /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DN00WOUP-if00-port0
E: TAGS=:systemd:
 


Mike Moore
 

I ran the following

 sudo systemctl restart udev

then I unplugged and plugged in the thumbdv with the same results

I also have a windows machine and a mac.  BlueDV works and Buster works with the ThumbDV



 


 

Ok, so if that is indeed your ThumbDV™ then it is either very old or somehow got its identity information changed.

You can use it as is by

sudo systemctl disable ambeserver@ThumbDV
sudo systemctl stop ambeserver@ThumbDV
sudo systemctl enable ambeserver@ttyUSB0
sudo systemctl start ambeserver@ttyUSB0
sudo systemctl status ambeserver@ttyUSB0
This will run an ambeserver with it looking for /dev/ttyUSB0 instead of /dev/ThumbDV  -- It is functionally equivalent.

If you want to fix the identity information, contact sales@... for instructions.

Be sure to review the "Assumptions and Defaults" and "Theory of Operation" in  https://github.com/nwdigitalradio/ambeserver-install/blob/master/README.md


On Sat, Jun 19, 2021 at 10:56 AM Mike Moore <mikemoore@...> wrote:
John, thank you for the speedy reply.  I did not see the name ThumbDV listed as the model shown below.
73, KC2NM

pi@ambeserver:~ $ udevadm info /dev/ttyUSB0
P: /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/ttyUSB0/tty/ttyUSB0
N: ttyUSB0
L: 0
S: serial/by-path/platform-3f980000.usb-usb-0:1.4:1.0-port0
S: serial/by-id/usb-FTDI_FT230X_Basic_UART_DN00WOUP-if00-port0
E: DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/ttyUSB0/tty/ttyUSB0
E: DEVNAME=/dev/ttyUSB0
E: MAJOR=188
E: MINOR=0
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=269956600767
E: ID_VENDOR=FTDI
E: ID_VENDOR_ENC=FTDI
E: ID_VENDOR_ID=0403
E: ID_MODEL=FT230X_Basic_UART
E: ID_MODEL_ENC=FT230X\x20Basic\x20UART
E: ID_MODEL_ID=6015
E: ID_REVISION=1000
E: ID_SERIAL=FTDI_FT230X_Basic_UART_DN00WOUP
E: ID_SERIAL_SHORT=DN00WOUP
E: ID_TYPE=generic
E: ID_BUS=usb
E: ID_USB_INTERFACES=:ffffff:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=ftdi_sio
E: ID_VENDOR_FROM_DATABASE=Future Technology Devices International, Ltd
E: ID_MODEL_FROM_DATABASE=Bridge(I2C/SPI/UART/FIFO)
E: ID_PATH=platform-3f980000.usb-usb-0:1.4:1.0
E: ID_PATH_TAG=platform-3f980000_usb-usb-0_1_4_1_0
E: DEVLINKS=/dev/serial/by-path/platform-3f980000.usb-usb-0:1.4:1.0-port0 /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DN00WOUP-if00-port0
E: TAGS=:systemd:
 



--
John D. Hays
Kingston, WA
K7VE / WRJT-215

 


Mike Moore
 

Yes, I was a relatively early adopter.  Also, this unit is one that you repaired when I bent the connector.  It looks like it came up at 230400 bps.  I will look for that in the configuration.  AMBEserver: Opened serial port /dev/ttyUSB0 at 230400 bps.
Mike Moore
mikemoore@...
Cell, Text (585) 721-0011




Mike Moore
 

I shelved this project for the summer and picked it back up this week.  I have my thumbDV working now in my Raspberry Pi 2 model B.  This unit builds with the device name ttyUSB0 and I start the server just as you recommended John, with the commands:

sudo systemctl enable ambeserver@ttyUSB0
sudo systemctl start ambeserver@ttyUSB0
sudo systemctl status ambeserver@ttyUSB0

It took me a while to figure out why the python test scripts were not working.  The reason was a permissions thing and when preceded the python command with sudo, I verified that my device was working in the pi but not reliably or for very long.  I suspected that I had a problem with my pi.  In searching "Will ambe server run on a pi 2 model B"  I found the thread about ensuring that the power supply is adequate.  I changed from a charger block to a real pi power supply and voila!  Reliable operation.

So thanks for your help last summer John.  I retraced the steps this week and found the problem was the supply.


Jiri Culak
 

hi Mike

where do you run the actual dstar/dmr app. ? Also on Pi? 
Jiri

On Thu, 11 Nov 2021 at 18:29, Mike Moore via groups.io <mikemoore=ieee.org@groups.io> wrote:
I shelved this project for the summer and picked it back up this week.  I have my thumbDV working now in my Raspberry Pi 2 model B.  This unit builds with the device name ttyUSB0 and I start the server just as you recommended John, with the commands:

sudo systemctl enable ambeserver@ttyUSB0
sudo systemctl start ambeserver@ttyUSB0
sudo systemctl status ambeserver@ttyUSB0

It took me a while to figure out why the python test scripts were not working.  The reason was a permissions thing and when preceded the python command with sudo, I verified that my device was working in the pi but not reliably or for very long.  I suspected that I had a problem with my pi.  In searching "Will ambe server run on a pi 2 model B"  I found the thread about ensuring that the power supply is adequate.  I changed from a charger block to a real pi power supply and voila!  Reliable operation.

So thanks for your help last summer John.  I retraced the steps this week and found the problem was the supply.


Mike Moore
 

I run the blueDV app on a windows computer configured to use ambeserver at the IP address of the raspberry pi.

Mike Moore
mikemoore@...
Cell, Text (585) 721-0011