Date   

Re: ThumbDV / ambed / AMBEServer reliability on Raspberry Pi 2 ?

Kenny Richards
 

Santu,

As another data point, I've had AMBEServer running on a Raspberry Pi 2 for months at a time without any issues. I typically only have a single instance of Buster (Mac client) connected and it is running all the time since I use it to monitor my DSTAR repeater.

73,
Kenny, KU7M


ThumbDV / ambed / AMBEServer reliability on Raspberry Pi 2 ?

Santu OTTAVI (TK1BI)
 

Hi all,

I'm running twi different setups :
- ambed with two ThumbDVs on a Raspberry Pi 2 (for XLX)
- AMBEserver with one ThumbDV on another Raspberry Pi 2 (for DVSwitch Analog_Bridge)
Both seem to malfunction after a while : scrambled audio, no audio at all, timeout errors in the logs, etc... Rebooting the RPi solves the problem, but the problem may appear again  later.

All the machines (XLX server, Analog_bridge, and the two RPIs) are in the same data center, and on the same VLAN. So, this is not a network latency problem, nor a port opening issue. Also, power supplies are "official" Raspberry Pi ones.

Did someone already encounter such issues with RPi 2 ? As USB problems are frequent topics in the RPi world, I'm thinking about connecting ThumbDVs through powered USB hubs. Any other ideas ?

Thank you in advance. 73 de TK1BI



Re: Audio receive problem with AMBE 3000 Stick on WIN10 Laptop

Bill - KI7BZ
 

dont forget to pull up windows device manager, find the thumbdrive under ports, then right click and update driver. this was a "gotcha" that happened to me. the win10 box recognized the thumbDV but it wouldn't work right until i updated the driver.


Re: Monitoring AMBESERVER traffic

Tom Corcoran
 

Tnx John. I appreciate the speedy response. 

Tom VE3NY 


Re: AmateurLogic.tv segment

Brent LeFevre
 

Blue DV does not support tx on FUSION, is that suggested sw that will support all of the modes?

73 Dr W4CHF

On Mon, Jan 14, 2019, 12:40 PM John D Hays - K7VE <john@... wrote:


AmateurLogic.tv segment

 


Re: Monitoring AMBESERVER traffic

 

Not really.  If you wanted to monitor debug output for activity you can use the -x flag to the ambeserver.

AMBEserver is really a stateless daemon, it doesn't track who/what is sending it traffic and there is no session information to know that a user is accessing it.

On Mon, Jan 14, 2019 at 8:29 AM Michael KD5DFB <mhebert1975@...> wrote:
Good Question! I would like to know too. 

On top of Tom's question, does it create a log file ? If so, where? 


On Mon, Jan 14, 2019, 10:26 <tcorcoran@... wrote:
Is there a terminal command to monitor traffic on the RPi/COMPASS AMBEserver? My server is accessible by a few friends and I’d like to know when the server is being used. 

Tnx .... Tom VE3NY 



--


John D. Hays
Edmonds, WA
K7VE

   


Re: Monitoring AMBESERVER traffic

Michael KD5DFB
 

Good Question! I would like to know too. 

On top of Tom's question, does it create a log file ? If so, where? 


On Mon, Jan 14, 2019, 10:26 <tcorcoran@... wrote:
Is there a terminal command to monitor traffic on the RPi/COMPASS AMBEserver? My server is accessible by a few friends and I’d like to know when the server is being used. 

Tnx .... Tom VE3NY 


Monitoring AMBESERVER traffic

Tom Corcoran
 

Is there a terminal command to monitor traffic on the RPi/COMPASS AMBEserver? My server is accessible by a few friends and I’d like to know when the server is being used. 

Tnx .... Tom VE3NY 


Re: Audio receive problem with AMBE 3000 Stick on WIN10 Laptop

Karl-Aug. Eichhorn <dr.eichhorn@...>
 

Hi John,
thanks for your quick reply.
With your first question you are hitting the spot: it's a 3rd party AMBE. And last night in our 80m daily qso party somebody told me about  the difference between 3000R and 3000F :-)
And after more hours of frustration I found out that my AMBE 3000F is now working fine with an older version of BlueDV ;-)

Thanks for the help and it's your fault that I ordered just now this nice Eversame-Multimeter-Chargers-Capacity-Banks for a few Euros :-)

vy 73 Charly (DK3ZL / AD8AS)

 


Re: Audio receive problem with AMBE 3000 Stick on WIN10 Laptop

 

Hi Charly,

Is this a ThumbDV™ or a 3rd party AMBE 3000 device?  They all function similarly, but NW Digital Radio manufactures and supports the ThumbDV™ exclusively.

It sounds like your AMBE is fine.  The USB ThumbDV™ appears simply as a FTDI USB serial port.  The interchange is encoded PCM digital audio and AMBE encoded data between the ThumbDV™ and the computer.  Programs such as BlueDV or Buster access the ThumbDV™ serially and exchange data packets with the AMBE 3000 chip.

All audio processing and routing, as well as radio protocols (D-STAR, DMR, ...) and network connections are handled in the program you use to access the ThumbDV™.  Assistance with PC specific and program configuration will require someone familiar with your particular setup.

USB 3 should be compatible.  One thing to be aware of is both the voltage and current supplied by the laptop USB interfaces -- sometimes testing with a powered USB hub can pinpoint if that is the issue.  For testing, I keep something similar to this in my shack -- https://www.amazon.com/Eversame-Multimeter-Chargers-Capacity-Banks-Black/dp/B01D9Y6ZFW

Perhaps if you provide the ACER model number someone else on the list has direct experience.



Audio receive problem with AMBE 3000 Stick on WIN10 Laptop

Karl-Aug. Eichhorn <dr.eichhorn@...>
 

Hello, I'm new on DStar and I try to get an AMBE 3000 stick working on my new Win10 ACER Laptop. My problem is: on the ACER I can't hear any thing in the speaker or my Sennheiser headset. The headset itself works fine with music and I have a good modulation while transmitting. But no RX audio? The AMBE 3000 works excellent at my WIN10 pc for amateur radio. No audio issues at all there. The only difference I found out is: the PC uses "Realtek High Definition Audio" drivers AND the Laptop "Realtek High Definition Audio (SST)" drivers mentioned in the device manager. A second difference is: with the normal PC I use USB 2 slot and with the ACER laptop I got only USB 3 slots.
Anybody any clue to solve this mystery for me which gives me hours of frustration :-) at the latop.

vy 73 Charly (DK3ZL / AD8AS)


Re: RPi 3 and PIDV will not work

Michael KD5DFB
 

So, after reboot. I tried to run ambeserver with systemctl. I enabled and then started

 

Here is the output.

 

sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

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

   Active: failed (Result: exit-code) since Sat 2019-01-12 20:03:15 GMT; 7s ago

  Process: 562 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=217/USER)

 

Jan 12 20:03:15 raspberrypi systemd[1]: Starting DV3000 Daemon...

Jan 12 20:03:15 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited status=217

Jan 12 20:03:15 raspberrypi systemd[1]: Failed to start DV3000 Daemon.

Jan 12 20:03:15 raspberrypi systemd[1]: ambeserver@...: Unit entered failed state.

Jan 12 20:03:15 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.

Jan 12 20:03:15 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.

 

Michael KD5DFB

 

From: Michael KD5DFB via Groups.Io
Sent: Saturday, January 12, 2019 13:58
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] RPi 3 and PIDV will not work

 

John,

 

That article helped and lot! I think that should be in the wiki.

 

I did sudo systemctl disable hciuart and added pi3-disable-bt to the config.txt and rebooted.

 

Here is the ambetest2 after reboot

 

sudo python AMBEtest2.py

d

8

N

1

False

False

False

0

a9

Reset

6100010033

Wrote: 5 bytes

a9

Product ID

6100010030

Wrote: 5 bytes

a

0AMBE3000R

Version

6100010031

Wrote: 5 bytes

a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208

Set DSTAR Mode

61000c000a013007634000000000000048

Wrote: 17 bytes

A

 

Here is just trying to run the program

 

sudo ./AMBEserver

AMBEserver: Starting...

AMBEserver: error when opening /dev/ttyUSB0: No such file or directory

 

Define port and tty

 

sudo ./AMBEserver -d -r -p 2460 -i /dev/ttyAMA0

AMBEserver: Starting...

AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

pi@raspberrypi:~ $ AMBEserver: Initialized AMBE3000R version V120.E100.XXXX.C106                                     .G514.R009.B0010411.C0020208.

AMBEserver: Listening for connections on UDP port 2460.

 

I guess I need to fix the systemctl for the ambeserver

 

Michael KD5DFB

 

From: John D Hays - K7VE
Sent: Saturday, January 12, 2019 12:59
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] RPi 3 and PIDV will not work

 

The RPi 3 can muck with device names. See https://www.raspberrypi.org/documentation/configuration/uart.md

 

Try /dev/ttyS0

 

On Sat, Jan 12, 2019, 09:08 Michael KD5DFB <mhebert1975@... wrote:

Good Morning! 

I have a RPi3 and PIDV and cannot get it to work with AMBEtest , AMBEsocket or AMBEserver. 

I have tried the guide on the ambe groups.io wiki and installed compass. I could never get ambetest2 or 3 to work

I am currently trying a fresh install of raspbian and have tried several different things.

When looking at the systemctl status I get the following:

ambeserver@... - DV3000 Daemon

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

   Active: failed (Result: exit-code) since Sat 2019-01-12 16:26:33 GMT; 2s ago

  Process: 1040 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=217/USER)

 

Jan 12 16:26:33 raspberrypi systemd[1]: Starting DV3000 Daemon...

Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited

Jan 12 16:26:33 raspberrypi systemd[1]: Failed to start DV3000 Daemon.

Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Unit entered failed state.

Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.

Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.


When I try to start it manually using ./AMBEServer I get the following: 

./AMBEserver

AMBEserver: Starting...

AMBEserver: error when opening /dev/ttyUSB0: No such file or directory

When I try to define everything during run, I get the following:

sudo ./AMBEserver -d -r -p 2460 -i /dev/ttyAMA0 -x

AMBEserver: Starting...

Baud 230400

opened /dev/ttyAMA0 230400

AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

 

Here is the AMBEtest2.py

 sudo python AMBEtest2.py

d

8

N

1

False

False

False

0

 

Reset

6100010033

Wrote: 5 bytes

 

Product ID

6100010030

Wrote: 5 bytes

 

Version

6100010031

Wrote: 5 bytes

 

Set DSTAR Mode

61000c000a013007634000000000000048

Wrote: 17 bytes

Hers is the AMBEtest3.py

sudo python AMBEtest3.py

Setting ...

/dev/ttyAMA0

d

8

N

1

False

False

False

 

Reset

6100010033

Wrote: 5 bytes

 

Product ID

6100010030

Wrote: 5 bytes

 

Version

6100010031

Wrote: 5 bytes

 

Set DSTAR Mode

61000c000a013007634000000000000048

Wrote: 17 bytes

 

Any help would be greatly appreciated! 

Michael KD5DFB

 

 

 


Re: RPi 3 and PIDV will not work

Michael KD5DFB
 

John,

 

That article helped and lot! I think that should be in the wiki.

 

I did sudo systemctl disable hciuart and added pi3-disable-bt to the config.txt and rebooted.

 

Here is the ambetest2 after reboot

 

sudo python AMBEtest2.py

d

8

N

1

False

False

False

0

a9

Reset

6100010033

Wrote: 5 bytes

a9

Product ID

6100010030

Wrote: 5 bytes

a

0AMBE3000R

Version

6100010031

Wrote: 5 bytes

a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208

Set DSTAR Mode

61000c000a013007634000000000000048

Wrote: 17 bytes

A

 

Here is just trying to run the program

 

sudo ./AMBEserver

AMBEserver: Starting...

AMBEserver: error when opening /dev/ttyUSB0: No such file or directory

 

Define port and tty

 

sudo ./AMBEserver -d -r -p 2460 -i /dev/ttyAMA0

AMBEserver: Starting...

AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

pi@raspberrypi:~ $ AMBEserver: Initialized AMBE3000R version V120.E100.XXXX.C106                                     .G514.R009.B0010411.C0020208.

AMBEserver: Listening for connections on UDP port 2460.

 

I guess I need to fix the systemctl for the ambeserver

 

Michael KD5DFB

 

From: John D Hays - K7VE
Sent: Saturday, January 12, 2019 12:59
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] RPi 3 and PIDV will not work

 

The RPi 3 can muck with device names. See https://www.raspberrypi.org/documentation/configuration/uart.md

 

Try /dev/ttyS0

 

On Sat, Jan 12, 2019, 09:08 Michael KD5DFB <mhebert1975@... wrote:

Good Morning! 

I have a RPi3 and PIDV and cannot get it to work with AMBEtest , AMBEsocket or AMBEserver. 

I have tried the guide on the ambe groups.io wiki and installed compass. I could never get ambetest2 or 3 to work

I am currently trying a fresh install of raspbian and have tried several different things.

When looking at the systemctl status I get the following:

ambeserver@... - DV3000 Daemon

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

   Active: failed (Result: exit-code) since Sat 2019-01-12 16:26:33 GMT; 2s ago

  Process: 1040 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=217/USER)

 

Jan 12 16:26:33 raspberrypi systemd[1]: Starting DV3000 Daemon...

Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited

Jan 12 16:26:33 raspberrypi systemd[1]: Failed to start DV3000 Daemon.

Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Unit entered failed state.

Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.

Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.


When I try to start it manually using ./AMBEServer I get the following: 

./AMBEserver

AMBEserver: Starting...

AMBEserver: error when opening /dev/ttyUSB0: No such file or directory

When I try to define everything during run, I get the following:

sudo ./AMBEserver -d -r -p 2460 -i /dev/ttyAMA0 -x

AMBEserver: Starting...

Baud 230400

opened /dev/ttyAMA0 230400

AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

 

Here is the AMBEtest2.py

 sudo python AMBEtest2.py

d

8

N

1

False

False

False

0

 

Reset

6100010033

Wrote: 5 bytes

 

Product ID

6100010030

Wrote: 5 bytes

 

Version

6100010031

Wrote: 5 bytes

 

Set DSTAR Mode

61000c000a013007634000000000000048

Wrote: 17 bytes

Hers is the AMBEtest3.py

sudo python AMBEtest3.py

Setting ...

/dev/ttyAMA0

d

8

N

1

False

False

False

 

Reset

6100010033

Wrote: 5 bytes

 

Product ID

6100010030

Wrote: 5 bytes

 

Version

6100010031

Wrote: 5 bytes

 

Set DSTAR Mode

61000c000a013007634000000000000048

Wrote: 17 bytes

 

Any help would be greatly appreciated! 

Michael KD5DFB

 

 


Re: RPi 3 and PIDV will not work

 

The RPi 3 can muck with device names. See https://www.raspberrypi.org/documentation/configuration/uart.md

Try /dev/ttyS0


On Sat, Jan 12, 2019, 09:08 Michael KD5DFB <mhebert1975@... wrote:
Good Morning! 

I have a RPi3 and PIDV and cannot get it to work with AMBEtest , AMBEsocket or AMBEserver. 

I have tried the guide on the ambe groups.io wiki and installed compass. I could never get ambetest2 or 3 to work

I am currently trying a fresh install of raspbian and have tried several different things.

When looking at the systemctl status I get the following:

ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-01-12 16:26:33 GMT; 2s ago
  Process: 1040 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=217/USER)
 
Jan 12 16:26:33 raspberrypi systemd[1]: Starting DV3000 Daemon...
Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited
Jan 12 16:26:33 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Unit entered failed state.
Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.

When I try to start it manually using ./AMBEServer I get the following: 

./AMBEserver
AMBEserver: Starting...
AMBEserver: error when opening /dev/ttyUSB0: No such file or directory

When I try to define everything during run, I get the following:

sudo ./AMBEserver -d -r -p 2460 -i /dev/ttyAMA0 -x
AMBEserver: Starting...
Baud 230400
opened /dev/ttyAMA0 230400
AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.
 
Here is the AMBEtest2.py

 sudo python AMBEtest2.py
d
8
N
1
False
False
False
0
 
Reset
6100010033
Wrote: 5 bytes
 
Product ID
6100010030
Wrote: 5 bytes
 
Version
6100010031
Wrote: 5 bytes
 
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

Hers is the AMBEtest3.py

sudo python AMBEtest3.py
Setting ...
/dev/ttyAMA0
d
8
N
1
False
False
False
 
Reset
6100010033
Wrote: 5 bytes
 
Product ID
6100010030
Wrote: 5 bytes
 
Version
6100010031
Wrote: 5 bytes
 
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes
 
Any help would be greatly appreciated! 

Michael KD5DFB



RPi 3 and PIDV will not work

Michael KD5DFB
 

Good Morning! 

I have a RPi3 and PIDV and cannot get it to work with AMBEtest , AMBEsocket or AMBEserver. 

I have tried the guide on the ambe groups.io wiki and installed compass. I could never get ambetest2 or 3 to work

I am currently trying a fresh install of raspbian and have tried several different things.

When looking at the systemctl status I get the following:

ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-01-12 16:26:33 GMT; 2s ago
  Process: 1040 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=217/USER)
 
Jan 12 16:26:33 raspberrypi systemd[1]: Starting DV3000 Daemon...
Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited
Jan 12 16:26:33 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Unit entered failed state.
Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
Jan 12 16:26:33 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.

When I try to start it manually using ./AMBEServer I get the following: 

./AMBEserver
AMBEserver: Starting...
AMBEserver: error when opening /dev/ttyUSB0: No such file or directory

When I try to define everything during run, I get the following:

sudo ./AMBEserver -d -r -p 2460 -i /dev/ttyAMA0 -x
AMBEserver: Starting...
Baud 230400
opened /dev/ttyAMA0 230400
AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.
 
Here is the AMBEtest2.py

 sudo python AMBEtest2.py
d
8
N
1
False
False
False
0
 
Reset
6100010033
Wrote: 5 bytes
 
Product ID
6100010030
Wrote: 5 bytes
 
Version
6100010031
Wrote: 5 bytes
 
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

Hers is the AMBEtest3.py

sudo python AMBEtest3.py
Setting ...
/dev/ttyAMA0
d
8
N
1
False
False
False
 
Reset
6100010033
Wrote: 5 bytes
 
Product ID
6100010030
Wrote: 5 bytes
 
Version
6100010031
Wrote: 5 bytes
 
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes
 
Any help would be greatly appreciated! 

Michael KD5DFB


locked Using the discussion topics #support

 


Hi Everyone.

First of all thank you for your testing, observations, suggestions, and requests for help via the established groups on groups.io


This allows the folks at NW Digital Radio and others to answer once and everyone can benefit.

A few important requests:
  1. Use the right sub-group for you topic (e.g. draws and udrc to https://nw-digital-radio.groups.io/g/udrc and so forth)
  2. Use subject line hashtags, e.g. #fldigi for topics about fldigi. If you use the web interface you can click on hashtags in the subject and see all postings related to that topic, including previous conversations.  Also you can search them in your email.  This helps with organizing information and doing your research on a topic.
  3. Place one and only only one issue per topic, with  a matching hashtag, and create separate topics for each issue so that a thread can be established for a topic/issue.  E.g. don't place an AX.25 and D-STAR issue in the same topic, unless it is specific to an interaction of the two (rare), create a topic for each.
  4. Be thorough in your description, e.g. radio, which port, which application, configuration, etc. Others can't figure out what is going on without sufficient information.
Again, thank you for using NW Digital Radio products and services and your valuable insights.

--


John D. Hays
Director

  


Re: Pb running AMBE server on RPI3b+

Pierre-Paul Raoult
 

Hi all,

I wish to thank you for your responses. It helped! And now server is working fine. It was indeed a pb of ports….

Best regards, 73

F1JMN

Le 11 déc. 2018 à 22:24, Annaliese McDermond <nh6z@...> a écrit :

If you’re using a ThumbDV you are using the wrong serial port. You need to do something like:

systemctl stop ambeserver@ttyS0
systemctl disable ambeserver@ttyS0
systemctl enable ambeserver@ttyUSB0
systemctl start ambeserver@ttyUSB0

—Anna

On Dec 11, 2018, at 3:37 AM, Pierre-Paul Raoult via Groups.Io <f1jmn@...> wrote:

After installing AMBE server on a RPI3B+ i cannot run it.... I have this message :

Can anyone help me please?

Best 73 F1JMN

 ambeserver@... - DV3000 Daemon

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

   Active: failed (Result: exit-code) since Tue 2018-12-11 12:33:53 CET; 49s ago

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

  Process: 425 ExecStartPre=/bin/chmod 0660 /dev/ttyS0 (code=exited, status=0/SUCCESS)

  Process: 417 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=0/SUCCESS)

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

 

déc. 11 12:33:10 AMBE-server systemd[1]: Starting DV3000 Daemon...

déc. 11 12:33:11 AMBE-server systemd[1]: Started DV3000 Daemon.

déc. 11 12:33:11 AMBE-server AMBEserver[428]: AMBEserver: Starting...

déc. 11 12:33:11 AMBE-server AMBEserver[428]: AMBEserver: Opened serial port /dev/ttyS0 at 460800 bps.

déc. 11 12:33:53 AMBE-server systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAILURE

déc. 11 12:33:53 AMBE-server systemd[1]: ambeserver@...: Unit entered failed state.

déc. 11 12:33:53 AMBE-server systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.

déc. 11 12:33:53 AMBE-server systemd[1]: ambeserver@...: Failed with result 'exit-code'.

 


Re: Pb running AMBE server on RPI3b+

Annaliese McDermond
 

If you’re using a ThumbDV you are using the wrong serial port. You need to do something like:

systemctl stop ambeserver@ttyS0
systemctl disable ambeserver@ttyS0
systemctl enable ambeserver@ttyUSB0
systemctl start ambeserver@ttyUSB0

—Anna

On Dec 11, 2018, at 3:37 AM, Pierre-Paul Raoult via Groups.Io <f1jmn@...> wrote:

After installing AMBE server on a RPI3B+ i cannot run it.... I have this message :

Can anyone help me please?

Best 73 F1JMN

ambeserver@... - DV3000 Daemon

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

   Active: failed (Result: exit-code) since Tue 2018-12-11 12:33:53 CET; 49s ago

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

  Process: 425 ExecStartPre=/bin/chmod 0660 /dev/ttyS0 (code=exited, status=0/SUCCESS)

  Process: 417 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=0/SUCCESS)

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

 

déc. 11 12:33:10 AMBE-server systemd[1]: Starting DV3000 Daemon...

déc. 11 12:33:11 AMBE-server systemd[1]: Started DV3000 Daemon.

déc. 11 12:33:11 AMBE-server AMBEserver[428]: AMBEserver: Starting...

déc. 11 12:33:11 AMBE-server AMBEserver[428]: AMBEserver: Opened serial port /dev/ttyS0 at 460800 bps.

déc. 11 12:33:53 AMBE-server systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAILURE

déc. 11 12:33:53 AMBE-server systemd[1]: ambeserver@...: Unit entered failed state.

déc. 11 12:33:53 AMBE-server systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.

déc. 11 12:33:53 AMBE-server systemd[1]: ambeserver@...: Failed with result 'exit-code'.

 


Re: Pb Installing ThumDV AMBE server on RPI3b+

 

Often these issues boil down to the power supply for the Pi, make sure your supply is at or above the recommended 2.5A at 5.1 VDC as recommended for the Pi.
--


John D. Hays
Edmonds, WA
K7VE