Date   

Re: PiDV, AMBEserver and Buster

KB5ZUR
 

Hi John,

Still no Joy!  tried your suggestion and the server failed. I stopped the server and ran the AMBEtest3.py and it hangs about half way through the test.
i@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyAMA0
Setting ...
/dev/ttyAMA0
d
8
N
1
False
False
False

Reset
6100010033

grep dialout shows the following:
pi@DV3000SVR:~/ambeserver-install $ grep dialout /etc/group
dialout:x:20:pi,opendv
 AMBEtest3,py with ttyS0 seems to complete

pi@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
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

What now coach?

-David
KB5ZUR


On Wed, Sep 30, 2020 at 11:25 AM John D Hays - K7VE <john@...> wrote:
OK, normally the PiDV™ would be on /dev/ttyAMA0 and not /dev/ttyS0 (Pi4 may re-map).

Give a try with:
sudo systemctl stop ambeserver@...  
sudo systemctl disable ambeserver@...  
sudo systemctl start ambeserver@...  
sudo systemctl status ambeserver@... 

If all is good, then

sudo systemctl enable ambeserver@...    

You can verify that opendv is in the dialout group with
 grep dialout /etc/group

Which should return something like:
dialout:x:20:opendv     

On Wed, Sep 30, 2020 at 6:58 AM KB5ZUR <kb5zur@...> wrote:
John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*

crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0


Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.




--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 

OK, normally the PiDV™ would be on /dev/ttyAMA0 and not /dev/ttyS0 (Pi4 may re-map).

Give a try with:
sudo systemctl stop ambeserver@...  
sudo systemctl disable ambeserver@...  
sudo systemctl start ambeserver@...  
sudo systemctl status ambeserver@... 

If all is good, then

sudo systemctl enable ambeserver@...    

You can verify that opendv is in the dialout group with
 grep dialout /etc/group

Which should return something like:
dialout:x:20:opendv     


On Wed, Sep 30, 2020 at 6:58 AM KB5ZUR <kb5zur@...> wrote:
John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*

crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0


Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.




--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

KB5ZUR
 

John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*
crw-rw-rw- 1 root tty       5,  0 Sep 29 15:13 /dev/tty
crw--w---- 1 root tty       4,  0 Sep 29 15:13 /dev/tty0
crw------- 1 pi   tty       4,  1 Sep 29 15:13 /dev/tty1
crw--w---- 1 root tty       4, 10 Sep 29 15:13 /dev/tty10
crw--w---- 1 root tty       4, 11 Sep 29 15:13 /dev/tty11
crw--w---- 1 root tty       4, 12 Sep 29 15:13 /dev/tty12
crw--w---- 1 root tty       4, 13 Sep 29 15:13 /dev/tty13
crw--w---- 1 root tty       4, 14 Sep 29 15:13 /dev/tty14
crw--w---- 1 root tty       4, 15 Sep 29 15:13 /dev/tty15
crw--w---- 1 root tty       4, 16 Sep 29 15:13 /dev/tty16
crw--w---- 1 root tty       4, 17 Sep 29 15:13 /dev/tty17
crw--w---- 1 root tty       4, 18 Sep 29 15:13 /dev/tty18
crw--w---- 1 root tty       4, 19 Sep 29 15:13 /dev/tty19
crw--w---- 1 root tty       4,  2 Sep 29 15:13 /dev/tty2
crw--w---- 1 root tty       4, 20 Sep 29 15:13 /dev/tty20
crw--w---- 1 root tty       4, 21 Sep 29 15:13 /dev/tty21
crw--w---- 1 root tty       4, 22 Sep 29 15:13 /dev/tty22
crw--w---- 1 root tty       4, 23 Sep 29 15:13 /dev/tty23
crw--w---- 1 root tty       4, 24 Sep 29 15:13 /dev/tty24
crw--w---- 1 root tty       4, 25 Sep 29 15:13 /dev/tty25
crw--w---- 1 root tty       4, 26 Sep 29 15:13 /dev/tty26
crw--w---- 1 root tty       4, 27 Sep 29 15:13 /dev/tty27
crw--w---- 1 root tty       4, 28 Sep 29 15:13 /dev/tty28
crw--w---- 1 root tty       4, 29 Sep 29 15:13 /dev/tty29
crw--w---- 1 root tty       4,  3 Sep 29 15:13 /dev/tty3
crw--w---- 1 root tty       4, 30 Sep 29 15:13 /dev/tty30
crw--w---- 1 root tty       4, 31 Sep 29 15:13 /dev/tty31
crw--w---- 1 root tty       4, 32 Sep 29 15:13 /dev/tty32
crw--w---- 1 root tty       4, 33 Sep 29 15:13 /dev/tty33
crw--w---- 1 root tty       4, 34 Sep 29 15:13 /dev/tty34
crw--w---- 1 root tty       4, 35 Sep 29 15:13 /dev/tty35
crw--w---- 1 root tty       4, 36 Sep 29 15:13 /dev/tty36
crw--w---- 1 root tty       4, 37 Sep 29 15:13 /dev/tty37
crw--w---- 1 root tty       4, 38 Sep 29 15:13 /dev/tty38
crw--w---- 1 root tty       4, 39 Sep 29 15:13 /dev/tty39
crw--w---- 1 root tty       4,  4 Sep 29 15:13 /dev/tty4
crw--w---- 1 root tty       4, 40 Sep 29 15:13 /dev/tty40
crw--w---- 1 root tty       4, 41 Sep 29 15:13 /dev/tty41
crw--w---- 1 root tty       4, 42 Sep 29 15:13 /dev/tty42
crw--w---- 1 root tty       4, 43 Sep 29 15:13 /dev/tty43
crw--w---- 1 root tty       4, 44 Sep 29 15:13 /dev/tty44
crw--w---- 1 root tty       4, 45 Sep 29 15:13 /dev/tty45
crw--w---- 1 root tty       4, 46 Sep 29 15:13 /dev/tty46
crw--w---- 1 root tty       4, 47 Sep 29 15:13 /dev/tty47
crw--w---- 1 root tty       4, 48 Sep 29 15:13 /dev/tty48
crw--w---- 1 root tty       4, 49 Sep 29 15:13 /dev/tty49
crw--w---- 1 root tty       4,  5 Sep 29 15:13 /dev/tty5
crw--w---- 1 root tty       4, 50 Sep 29 15:13 /dev/tty50
crw--w---- 1 root tty       4, 51 Sep 29 15:13 /dev/tty51
crw--w---- 1 root tty       4, 52 Sep 29 15:13 /dev/tty52
crw--w---- 1 root tty       4, 53 Sep 29 15:13 /dev/tty53
crw--w---- 1 root tty       4, 54 Sep 29 15:13 /dev/tty54
crw--w---- 1 root tty       4, 55 Sep 29 15:13 /dev/tty55
crw--w---- 1 root tty       4, 56 Sep 29 15:13 /dev/tty56
crw--w---- 1 root tty       4, 57 Sep 29 15:13 /dev/tty57
crw--w---- 1 root tty       4, 58 Sep 29 15:13 /dev/tty58
crw--w---- 1 root tty       4, 59 Sep 29 15:13 /dev/tty59
crw--w---- 1 root tty       4,  6 Sep 29 15:13 /dev/tty6
crw--w---- 1 root tty       4, 60 Sep 29 15:13 /dev/tty60
crw--w---- 1 root tty       4, 61 Sep 29 15:13 /dev/tty61
crw--w---- 1 root tty       4, 62 Sep 29 15:13 /dev/tty62
crw--w---- 1 root tty       4, 63 Sep 29 15:13 /dev/tty63
crw--w---- 1 root tty       4,  7 Sep 29 15:13 /dev/tty7
crw--w---- 1 root tty       4,  8 Sep 29 15:13 /dev/tty8
crw--w---- 1 root tty       4,  9 Sep 29 15:13 /dev/tty9
crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw------- 1 root root      5,  3 Sep 29 15:13 /dev/ttyprintk
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0

On Tue, Sep 29, 2020 at 6:38 PM John D Hays - K7VE <john@...> wrote:
Provide a listing of the command

ls -l /dev/tty*

On Tue, Sep 29, 2020 at 2:12 PM KB5ZUR <kb5zur@...> wrote:
On Fri, Apr 24, 2020 at 06:42 PM, John D Hays - K7VE wrote:
sudo usermod -G dialout opendv
Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 

Provide a listing of the command

ls -l /dev/tty*

On Tue, Sep 29, 2020 at 2:12 PM KB5ZUR <kb5zur@...> wrote:
On Fri, Apr 24, 2020 at 06:42 PM, John D Hays - K7VE wrote:
sudo usermod -G dialout opendv
Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

KB5ZUR
 

On Fri, Apr 24, 2020 at 06:42 PM, John D Hays - K7VE wrote:
sudo usermod -G dialout opendv
Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.


HamPi 1.1 (September 2020) Released!

 



---------- Forwarded message ---------
From: Dave Slotter, W3DJS <slotter+W3DJS@...>
Date: Sun, Sep 20, 2020 at 10:22 AM
Subject: HamPi 1.1 (September 2020) Released!
To: <Ham-Pi@groups.io>, <RaspberryPi-4-HamRadio@groups.io>
Cc: Atlanta-Hams@groups.io Group Moderators <Atlanta-Hams@groups.io>, <main@athensradioclub.groups.io>, <Cherokee-Hams@groups.io>, GARS@groups.io Group Moderators <GARS@groups.io>, <main@alfordmemorialradioclub.groups.io>, main@NFARL.groups.io <main@nfarl.groups.io>, <BarrowARC@groups.io>, <main@wc4rg.groups.io>, <main@nw-digital-radio.groups.io>


Attention All Hams Using Raspberry Pi For Ham Radio:

I am pleased to announce that HamPi 1.1 is now available for public download!

Please use the attached BitTorrent file to make it easier for everyone to get the image. And after you have completed downloading, please continue to seed for at least a week so other hams can benefit.

If you cannot or will not use BitTorrent, you may download HamPi from SourceForge:


If you run into issues, please post to the forum on https://groups.io/g/Ham-Pi/ first. If you see a bug (defect), please report it on the GitHub issues page at: https://github.com/dslotter/HamPi/issues

UPGRADING: In order to transition smoothly from HamPi 1.0 to HamPi 1.1 and preserve your configuration settings, please follow the instructions in the attached file, "UPGRADING_FROM_PRIOR_VERSION.TXT"

CHANGELOG:

Version 1.1 (September 2020) Release
====================================

Updated WSJT-X
Updated JTDX
Updated GridTracker
Added HamClock by WB0OEW
Added adifmerg command line utility
Added Lopora (QRSS viewer)
Minor fixes with SDRAngel installation
Fixed BlueDV not launching from menu as expected
Fixed FreeDV not launching from menu as expected
Updated DireWolf installation as DW and GPSd are both "moving targets"
Enhanced error message display for D-Rats software update failures
Added exclusion for EMComm / Field users in license
Partially added AMBEserver
Many other applications updated from Internet


Good luck and 73!

HamPi Logo Transparent.png


--


John D. Hays
Director

  


Re: what does this error message mean?

Gwen Patton
 

If it's the error I think it is, check your setup. You can't leave the server and default room blank for Fusion. Unlike DMR and D-Star, it doesn't have default settings.

73,
Gwen, NG3P

On Wed, Sep 16, 2020, 3:39 PM S. Wilk <nk9a@...> wrote:
 How do I fix it ?   Blue DV for windows .. " Unhandled exception has occurred in your application".  I get  the message when I try to change  talk groups  in the settings  screen for the PA7LIM blue dv program . 


what does this error message mean?

S. Wilk
 

 How do I fix it ?   Blue DV for windows .. " Unhandled exception has occurred in your application".  I get  the message when I try to change  talk groups  in the settings  screen for the PA7LIM blue dv program . 


Re: AMBE server multiple connections

 

You can run multiple instances of AMBEserver on a computer each with it's own ThumbDV™ and UDP port.



On Tue, Sep 8, 2020, 18:38 alpha foxtrotsix <alphafoxtrotsix@...> wrote:
I believe you can add a second ambe device (ThumbDV, etc.) and use a different port and support 2 connections. One on each port.

Jeff

On Tue, Sep 8, 2020, 10:30 John D Hays - K7VE <john@...> wrote:
Hi Derek,

AMBEserver only supports one client at a time.  It is simply a mechanism to make the serial (USB) connection to an AMBE3000 device available on a UDP port.

The server can be shared by ending one client and starting another.  It doesn't do any multiplexing and the DVSI AMBE 3000 Chip only has one pipeline.

On Tue, Sep 8, 2020 at 1:55 AM Derek William Haden <facebook@...> wrote:
I have the AMBE server running, thanks for the instructions John, very comprehensive.

I am making an assumption here.

The whole point of using AMBE server rather than connecting directly via USB to the stick is so that more than one connection can use the AMBE server?

However when I try to connect connect BlueDVambe and DVswitch the results are "Interesting" to say the least.

I am making another assumption here, would setting up a second service to the dongle on a different port allow this to work.



--
John D. Hays
Kingston, WA
K7VE

 


Re: AMBE server multiple connections

alpha foxtrotsix
 

I believe you can add a second ambe device (ThumbDV, etc.) and use a different port and support 2 connections. One on each port.

Jeff


On Tue, Sep 8, 2020, 10:30 John D Hays - K7VE <john@...> wrote:
Hi Derek,

AMBEserver only supports one client at a time.  It is simply a mechanism to make the serial (USB) connection to an AMBE3000 device available on a UDP port.

The server can be shared by ending one client and starting another.  It doesn't do any multiplexing and the DVSI AMBE 3000 Chip only has one pipeline.

On Tue, Sep 8, 2020 at 1:55 AM Derek William Haden <facebook@...> wrote:
I have the AMBE server running, thanks for the instructions John, very comprehensive.

I am making an assumption here.

The whole point of using AMBE server rather than connecting directly via USB to the stick is so that more than one connection can use the AMBE server?

However when I try to connect connect BlueDVambe and DVswitch the results are "Interesting" to say the least.

I am making another assumption here, would setting up a second service to the dongle on a different port allow this to work.



--
John D. Hays
Kingston, WA
K7VE

 


Re: AMBE server multiple connections

Kenny Richards
 

On Tue, Sep 8, 2020 at 01:55 AM, Derek William Haden wrote:
The whole point of using AMBE server rather than connecting directly via USB to the stick is so that more than one connection can use the AMBE server?
Derek - there is another reasons, which covers my personal case. I personally have more than one computer that I work on, so using AMBE server I am able to launch Buster where ever I happen to be working. I've also exposed AMBEsever to the outside world, so I can even launch it when using my laptop somewhere remote.

73,
Kenny 


Re: AMBE server multiple connections

 

Yes, that would work.

On Tue, Sep 8, 2020 at 11:42 AM Derek William Haden <facebook@...> wrote:

Thanks John for the clarification.

But I could have 2 dongles running as servers on the same Pi but offering up it's service on different port?



--
John D. Hays
Kingston, WA
K7VE

 


Re: AMBE server multiple connections

Derek William Haden
 

Thanks John for the clarification.

But I could have 2 dongles running as servers on the same Pi but offering up it's service on different port?


Re: AMBE server multiple connections

 

Hi Derek,

AMBEserver only supports one client at a time.  It is simply a mechanism to make the serial (USB) connection to an AMBE3000 device available on a UDP port.

The server can be shared by ending one client and starting another.  It doesn't do any multiplexing and the DVSI AMBE 3000 Chip only has one pipeline.

On Tue, Sep 8, 2020 at 1:55 AM Derek William Haden <facebook@...> wrote:
I have the AMBE server running, thanks for the instructions John, very comprehensive.

I am making an assumption here.

The whole point of using AMBE server rather than connecting directly via USB to the stick is so that more than one connection can use the AMBE server?

However when I try to connect connect BlueDVambe and DVswitch the results are "Interesting" to say the least.

I am making another assumption here, would setting up a second service to the dongle on a different port allow this to work.



--
John D. Hays
Kingston, WA
K7VE

 


AMBE server multiple connections

Derek William Haden
 

I have the AMBE server running, thanks for the instructions John, very comprehensive.

I am making an assumption here.

The whole point of using AMBE server rather than connecting directly via USB to the stick is so that more than one connection can use the AMBE server?

However when I try to connect connect BlueDVambe and DVswitch the results are "Interesting" to say the least.

I am making another assumption here, would setting up a second service to the dongle on a different port allow this to work.


Re: PiDV, AMBEserver and Buster

Balasubramanian Iyer
 

I am running ThumDV on usb exteder without power, it is working on windows 10 
i am also using ThumbDV on Buster on Mac it is working fine


Re: #DVMegaStick 30 #dvmegastick

 

The ThumbDV and PiDV (discontinued) are manufactured by NW Digital Radio (This list is to support NW Digital Radio products).   DVStick and other 3rd party products have their own support mechanisms.

On Mon, Sep 7, 2020 at 9:36 AM Balasubramanian Iyer <vu3tbr@...> wrote:
Yes same Dongle
if it works it is great
as the App Store is silent about the DVMEGA  stock 30 in their list it only confirms ThumbDV and PiDV over the network
need to update  by the author

Tks and regards
Bala



--
John D. Hays
Kingston, WA
K7VE

 


Re: #DVMegaStick 30 #dvmegastick

Balasubramanian Iyer
 

Yes same Dongle
if it works it is great
as the App Store is silent about the DVMEGA  stock 30 in their list it only confirms ThumbDV and PiDV over the network
need to update  by the author

Tks and regards
Bala


On Mon, 7 Sep 2020 at 21:54, Derek William Haden <facebook@...> wrote:

Is that the DV3000 ambe dongle?

If so the answer is yes.

 


Re: #DVMegaStick 30 #dvmegastick

Derek William Haden
 

Is that the DV3000 ambe dongle?

If so the answer is yes.

 

81 - 100 of 1504