Date   

Re: Portable ambe server

Frank
 

HI
I've been using the same system for a few years. I can tell you that I have made some soft and hardware changes to the master which improves the latency a little when you are on the go (auto) as a slave.

This does less unpack, so in mine I did this:

1. I modified the various ports to be independent and avoid default access using its internal config in the sd

2. you must have a configuration without automatic dhcp but fixed ip for and in your ambe

3. in any case inform your router with the NAT port you use towards the IP of the ambe (for external access)

4. there is a recent change to be made on the ambe server hardware to improve the latency which then brings it from 230400bd to 460800bd (a simple hardware soldering) and then also mod speed in the soft AMBEs you use

5. Change the SD and port to the new speed and the new soft to download iso for the SD

6. have a fixed IP or use any system dyndns or no-ip or other to reach it even from outside the home on the internet

7. I have activated the SSH app to be able to reboot and turn off and turn on the master again if it crashes

With the DVSWITCH app you don't need an AMBE, as everything is contained via soft.
A single raspberry on the network as a server and the DvSwitch app with its iso on the configured sd, obviously with the NAT configured and fixed ip or dyndns / no-ip for access from outside your home network.

73


Re: Portable ambe server

Gwen Patton
 

I run my AMBEServer on a Raspberry Pi, with the ThumbDV on a powered hub. I have a port forwarded to Dyndns so I can access it from anywhere using my phone or any other internet-connected machine. It's not portable, but it doesn't have to be. I activate it by SSH'ing to the RasPi and bringing up the AMBEServer. Then I leave the session open but minimized. I can use the same computer to run BlueDV, or my Android phone to run BlueDV AMBE. Works great. I use ExtraPuTTY (a fork of PuTTY that has file transfer protocols, and other features) for the access.

If I used it more, I might pop for a static IP for mine as well, but the DynDNS works ok so long as I have a daemon on the RasPi that updates it if my home network's IP changes.

Note that I ONLY run AMBEServer. I don't run Buster or any other programs except the dynamic DNS daemon, which runs in the background and starts on boot. What else might you want to know?

-=-=-=-=-=-=-=-=-
73,
Gwen, NG3P


On Thu, Jan 21, 2021 at 11:31 PM Glenn Taylor VK1NUT <vk1nut@...> wrote:
hi,
I have a portable ambe server
https://reflectorloversclub.jimdofree.com/shop/
and am trying to accertain if moving the default port (2465) to match local ambeservers (2462) would effect the reliability of the connection.
I can connect externally from bluedv ambe for android and bluedv for windows to a static ip address as I don't need dyn dns etc.
Unfortunately the connection seems to be unrealiable at best to others.
The server can be accessed by me anywhere even ssh everytime.
Has anyone had experience with these as I would appreciate your help.
thanks

Glenn vk1nut


Portable ambe server

Nutters (vk1nut)
 

hi,
I have a portable ambe server
https://reflectorloversclub.jimdofree.com/shop/
and am trying to accertain if moving the default port (2465) to match local ambeservers (2462) would effect the reliability of the connection.
I can connect externally from bluedv ambe for android and bluedv for windows to a static ip address as I don't need dyn dns etc.
Unfortunately the connection seems to be unrealiable at best to others.
The server can be accessed by me anywhere even ssh everytime.
Has anyone had experience with these as I would appreciate your help.
thanks

Glenn vk1nut


Re: AMBE not detected by Thumb DV

 

Have you run the ThumbTest.exe from https://nw-digital-radio.groups.io/g/ambe/files  ???

The ThumbDV™ appears to the operating system and applications as a simple serial device.  There is no user firmware to be loaded to the ThumbDV™  -- that warning is a 'red herring' that applies to other devices that BlueDV interacts with. 

The driver is simply the FTDI USB drivers (which on Windows should just automatically load and on Linux they are built in).  The serial (COM) port either is there or it isn't. 

If you can talk to the right COM port at the right data rate, using the test program for Windows (or the python scripts for Linux), then the ThumbDV™ is good --  it is then a configuration issue or an application/operating system issue to be debugged.

On Tue, Jan 19, 2021 at 1:06 PM Tim Lawrence <kj4hpg@...> wrote:
Hello all,

I am using Thumb DV with Blue dV version 9572 download.  I have installed everything correctly and am using the correct COM port.  However upon startup Blue DV does not recognize the AMBE software.  I get a firmware not detected error or if I uncheck the thumb DV box in the AMBE section of Blue DV I says connected to zumspot however I have no control over the AMBE setting mic gain, output etc and can hear no audio.  I have updated software and looked for a firmware upgrade for teh thumb DV however have came up empty.  Has anyone else experience this issue?

KJ4HPG
Tim



--
John D. Hays
Kingston, WA
K7VE

 


Re: AMBE not detected by Thumb DV

Dave Slotter, W3DJS
 

Tim,

These are my (redacted) settings for BlueDV for Windows.

Where I have filled in "YOURCALL", you should put in your callsign. Where I have filled in "DMR_ID" in three places, you should put in your assigned DMR ID number. I have both a ThumbDV and another (competitor) AMBE USB Dongle. I have the AMBE USB dongle plugged into COM4 -- you should confirm you have the right COM port. Notice I select COM4 under "Serial Port Radio" and also under "AMBE Serial Port" (two places). Depending on how new or old your ThumbDV is, you should either select 230400 baud or 460800 baud.

Are you able to share what your settings look like?



On Wed, Jan 20, 2021 at 11:01 AM, Tim Lawrence wrote:
I have tried the different baud rates and it does not seem to have an effect.  The COM ports are correct it usually defaults to COM 6.  Looks like the software is just not communicating with the AMBE chip.  All settings are there just grayed out and can't adjust anything or use PTT function.  When I check the box to use the dongle the COM ports will not connect. When I uncheck it everything connects but just no audio.  It is receiving data.  I was going to install this on my PC and then if I want to connect to PC remotely via desktop would be able to pull up Dstar or DMR.
 
KJ4HPG
TIM

 
--
- Dave
  W3DJS


Re: AMBE not detected by Thumb DV

Mike, AA9VI
 

Tim,
Have a look at these 2 links.  I'm wondering if the driver install isn't quite right.  I know these instructions are for the XLX utility, but the driver install is probably identical.  I also used the 1.3.6 driver since the newer 1.4.8 did not work.

I'd try and get the 1.3.6 drivers first.  I got them from the XLXbbs:

make sure you have the build-essential and g++ packages installed

Then follow this to install:

Be sure to also add your username to the device group.  (i.e dialout for debian in the device group)



Mike, AA9VI



Re: AMBE not detected by Thumb DV

Brad N8PC
 

baud rate of the Thumbdv is not a common baud rate it is 460800. try that in the software for the ambe server

On 1/20/2021 11:00 AM, Tim Lawrence wrote:
I have tried the different baud rates and it does not seem to have an effect.  The COM ports are correct it usually defaults to COM 6.  Looks like the software is just not communicating with the AMBE chip.  All settings are there just grayed out and can't adjust anything or use PTT function.  When I check the box to use the dongle the COM ports will not connect. When I uncheck it everything connects but just no audio.  It is receiving data.  I was going to install this on my PC and then if I want to connect to PC remotely via desktop would be able to pull up Dstar or DMR.

KJ4HPG
TIM

On Tue, Jan 19, 2021 at 7:37 PM AB4WS - Jack <Ab4wsnews@...> wrote:
Check your communication speed for the port the ThumbDV is plugged into, early versions of the ThumbDV required slower communication speed while the newer device requires a faster speed.


On Jan 19, 2021, at 16:06, Tim Lawrence <kj4hpg@...> wrote:

Hello all,

I am using Thumb DV with Blue dV version 9572 download.  I have installed everything correctly and am using the correct COM port.  However upon startup Blue DV does not recognize the AMBE software.  I get a firmware not detected error or if I uncheck the thumb DV box in the AMBE section of Blue DV I says connected to zumspot however I have no control over the AMBE setting mic gain, output etc and can hear no audio.  I have updated software and looked for a firmware upgrade for teh thumb DV however have came up empty.  Has anyone else experience this issue?

KJ4HPG
Tim


Re: AMBE not detected by Thumb DV

Tim Lawrence
 

I have tried the different baud rates and it does not seem to have an effect.  The COM ports are correct it usually defaults to COM 6.  Looks like the software is just not communicating with the AMBE chip.  All settings are there just grayed out and can't adjust anything or use PTT function.  When I check the box to use the dongle the COM ports will not connect. When I uncheck it everything connects but just no audio.  It is receiving data.  I was going to install this on my PC and then if I want to connect to PC remotely via desktop would be able to pull up Dstar or DMR.

KJ4HPG
TIM

On Tue, Jan 19, 2021 at 7:37 PM AB4WS - Jack <Ab4wsnews@...> wrote:
Check your communication speed for the port the ThumbDV is plugged into, early versions of the ThumbDV required slower communication speed while the newer device requires a faster speed.


On Jan 19, 2021, at 16:06, Tim Lawrence <kj4hpg@...> wrote:

Hello all,

I am using Thumb DV with Blue dV version 9572 download.  I have installed everything correctly and am using the correct COM port.  However upon startup Blue DV does not recognize the AMBE software.  I get a firmware not detected error or if I uncheck the thumb DV box in the AMBE section of Blue DV I says connected to zumspot however I have no control over the AMBE setting mic gain, output etc and can hear no audio.  I have updated software and looked for a firmware upgrade for teh thumb DV however have came up empty.  Has anyone else experience this issue?

KJ4HPG
Tim


Re: AMBE not detected by Thumb DV

AB4WS - Jack
 

Check your communication speed for the port the ThumbDV is plugged into, early versions of the ThumbDV required slower communication speed while the newer device requires a faster speed.


On Jan 19, 2021, at 16:06, Tim Lawrence <kj4hpg@...> wrote:

Hello all,

I am using Thumb DV with Blue dV version 9572 download.  I have installed everything correctly and am using the correct COM port.  However upon startup Blue DV does not recognize the AMBE software.  I get a firmware not detected error or if I uncheck the thumb DV box in the AMBE section of Blue DV I says connected to zumspot however I have no control over the AMBE setting mic gain, output etc and can hear no audio.  I have updated software and looked for a firmware upgrade for teh thumb DV however have came up empty.  Has anyone else experience this issue?

KJ4HPG
Tim


AMBE not detected by Thumb DV

Tim Lawrence
 

Hello all,

I am using Thumb DV with Blue dV version 9572 download.  I have installed everything correctly and am using the correct COM port.  However upon startup Blue DV does not recognize the AMBE software.  I get a firmware not detected error or if I uncheck the thumb DV box in the AMBE section of Blue DV I says connected to zumspot however I have no control over the AMBE setting mic gain, output etc and can hear no audio.  I have updated software and looked for a firmware upgrade for teh thumb DV however have came up empty.  Has anyone else experience this issue?

KJ4HPG
Tim


BlueDV for Windows #bluedv

Johan Lehmann
 

I have a DELL Notebook with Windows 10 Build 1909 and DELL Desktop with Windows 10 Build 20H2. I installed BlueDV on both machines. On the notebook it starts up and works perfectly, on the desktop it is refusing to start. I even tried version 9572 and 9594 it is the same on the desktop. I have looked at all the obvious rights issues, registry settings etc and can not find any thing out of order.

Anybody else had a similar issue in getting BlueDV to start up?

Johan ZS6JPL


Re: DMR XLX Fusion Linking #thumbdv

Charles Wiant
 

On github check out n5amd ambed  that is what i use open ports point to reflector,point reflector to ambed


On Jan 7, 2021, at 7:14 PM, CHARLES WIANT <kd8itc@...> wrote:

In your xlx install there is ambed in there just have to set it up


On Jan 7, 2021, at 5:57 PM, John Ferrari via groups.io <jsfpamac@...> wrote:

Thank you so much. I think I'm on the right track now. 
I'm reviewing this pdf now.    http://hamradio.dip.jp/ja3gqj/ambed_server_myexp.pdf

John

On Thu, Jan 7, 2021 at 04:46 PM, Ryan Matthew Headley wrote:
This can certainly be done.  The program is called ambed.  It is part of the xlxd repository, but it can be built and installed completely separately from xlxd.  Good instructions are found in the README within the ambed folder.

Make sure that the internet connection for the ambed server has the lowest latency possible.  You cannot control your ISP, but do everything you can locally.

Used remotely, ambed--like xlxd--will need a static public IP address.  One thing not specifically mentioned in the README is that for a local (to xlxd) install, ambed should listen on the local-link address (127.0.0.1); for a remote (to xlxd) install, ambed should listen on the LAN address of the device running ambed.

All in all, the network considerations for running ambed remotely are a little greater than running both ambed and xlxd locally.  In the end, running both xlxd and ambed on a local server may still give you fewer headaches and better overall performance. 


Re: DMR XLX Fusion Linking #thumbdv

Charles Wiant
 

In your xlx install there is ambed in there just have to set it up


On Jan 7, 2021, at 5:57 PM, John Ferrari via groups.io <jsfpamac@...> wrote:

Thank you so much. I think I'm on the right track now. 
I'm reviewing this pdf now.    http://hamradio.dip.jp/ja3gqj/ambed_server_myexp.pdf

John

On Thu, Jan 7, 2021 at 04:46 PM, Ryan Matthew Headley wrote:
This can certainly be done.  The program is called ambed.  It is part of the xlxd repository, but it can be built and installed completely separately from xlxd.  Good instructions are found in the README within the ambed folder.

Make sure that the internet connection for the ambed server has the lowest latency possible.  You cannot control your ISP, but do everything you can locally.

Used remotely, ambed--like xlxd--will need a static public IP address.  One thing not specifically mentioned in the README is that for a local (to xlxd) install, ambed should listen on the local-link address (127.0.0.1); for a remote (to xlxd) install, ambed should listen on the LAN address of the device running ambed.

All in all, the network considerations for running ambed remotely are a little greater than running both ambed and xlxd locally.  In the end, running both xlxd and ambed on a local server may still give you fewer headaches and better overall performance. 


Re: DMR XLX Fusion Linking #thumbdv

John
 

Thank you so much. I think I'm on the right track now. 
I'm reviewing this pdf now.    http://hamradio.dip.jp/ja3gqj/ambed_server_myexp.pdf

John


On Thu, Jan 7, 2021 at 04:46 PM, Ryan Matthew Headley wrote:
This can certainly be done.  The program is called ambed.  It is part of the xlxd repository, but it can be built and installed completely separately from xlxd.  Good instructions are found in the README within the ambed folder.

Make sure that the internet connection for the ambed server has the lowest latency possible.  You cannot control your ISP, but do everything you can locally.

Used remotely, ambed--like xlxd--will need a static public IP address.  One thing not specifically mentioned in the README is that for a local (to xlxd) install, ambed should listen on the local-link address (127.0.0.1); for a remote (to xlxd) install, ambed should listen on the LAN address of the device running ambed.

All in all, the network considerations for running ambed remotely are a little greater than running both ambed and xlxd locally.  In the end, running both xlxd and ambed on a local server may still give you fewer headaches and better overall performance. 


Re: DMR XLX Fusion Linking #thumbdv

Ryan Matthew Headley
 

For that matter, you could run your vpn server on your cloud machine, and run both xlxd and ambed on a local machine.

Either way, the lowest overhead protocol (by a wide margin) for the VPN would be WireGuard.


Re: DMR XLX Fusion Linking #thumbdv

 

You could also run a VPN between your XLXD host and AMBED host. (Isolating the AMBED from the public Internet and then it could also be at a dynamic public IP).

On Thu, Jan 7, 2021 at 1:46 PM Ryan Matthew Headley <headley.ryan@...> wrote:
This can certainly be done.  The program is called ambed.  It is part of the xlxd repository, but it can be built and installed completely separately from xlxd.  Good instructions are found in the README within the ambed folder.

Make sure that the internet connection for the ambed server has the lowest latency possible.  You cannot control your ISP, but do everything you can locally.

Used remotely, ambed--like xlxd--will need a static public IP address.  One thing not specifically mentioned in the README is that for a local (to xlxd) install, ambed should listen on the local-link address (127.0.0.1); for a remote (to xlxd) install, ambed should listen on the LAN address of the device running ambed.

All in all, the network considerations for running ambed remotely are a little greater than running both ambed and xlxd locally.  In the end, running both xlxd and ambed on a local server may still give you fewer headaches and better overall performance. 



--
John D. Hays
Kingston, WA
K7VE

 


Re: DMR XLX Fusion Linking #thumbdv

Ryan Matthew Headley
 

This can certainly be done.  The program is called ambed.  It is part of the xlxd repository, but it can be built and installed completely separately from xlxd.  Good instructions are found in the README within the ambed folder.

Make sure that the internet connection for the ambed server has the lowest latency possible.  You cannot control your ISP, but do everything you can locally.

Used remotely, ambed--like xlxd--will need a static public IP address.  One thing not specifically mentioned in the README is that for a local (to xlxd) install, ambed should listen on the local-link address (127.0.0.1); for a remote (to xlxd) install, ambed should listen on the LAN address of the device running ambed.

All in all, the network considerations for running ambed remotely are a little greater than running both ambed and xlxd locally.  In the end, running both xlxd and ambed on a local server may still give you fewer headaches and better overall performance. 


Re: DMR XLX Fusion Linking #thumbdv

John
 

Thanks for the reply. Our gaol is to have Dstar, YSF and DMR on the same XLX module. I believe this link is for setting up a new reflector and transcoder on a local machine. We have an existing XLX reflector on a remote server with DMR and YSF  to be added soon. What I am looking for is information on setting up the local transcoder to receive transcode  and send back to the remote server. I've been told this has been done on a raspberry pi with 2 digital vocoders but can't find and information on the setup.  


On Thu, Jan 7, 2021 at 02:25 PM, Ryan Matthew Headley wrote:
The absolute quickest and easiest way to get a a transcoding XLX reflector up an running is the N7TAE's new-xlx:  https://github.com/n7tae/new-xlxd

If your goal is to use YSF and DMR, then you need no transcoder.  That is only required for D-Star to either of those modes.

A few cautions when using a Raspberry Pi for the XLX reflector:

1) use a Pi 4.  It will work on the Pi 3B+, but will struggle with too many connections--and the transcoder will have more 'hickups.'
2) In most cases, use an ethernet cable, not. WiFi for the internet connection. (Such a case would be if you do not know the which WiFi standard your router uses, or in any case where your router is provided by your ISP).


Re: DMR XLX Fusion Linking #thumbdv

 

N7TAE has done some great work. 


On Thu, Jan 7, 2021, 11:51 Ryan Matthew Headley <headley.ryan@...> wrote:
That should work out fine.  I just mentioned the Pi's because there is are quite few different guides online directing the use of a Pi.

I run two:  one is on a circa 2012 Dell Optiplex connected to Verizon business service in Brooklyn, NY.  The other is running in a Debian virtual machine on my Threadripper-powered desktop/server.  Both run without a hitch.

N7TAE's build is not only easier to build and install, but also has few extra features like DExtra linking.  He has also done a good bit of work cleaning up the code.  It is more stable than the main build, and can run for weeks or months without issue.

One other thing included in Tom's build is the ability to set it up for ipv6 connectivity.  The ability for every device to have its own global address solves a lot of problems with reflectors and hotspots.  I have my reflectors setup for ipv6 connectivity for D-Star, Fusion, and DMR.  The newest builds of DMRGateway and YSFClients have the ability to use ipv6 connections, and well as QnetGateway does for D-Star.


Re: DMR XLX Fusion Linking #thumbdv

Ryan Matthew Headley
 

That should work out fine.  I just mentioned the Pi's because there is are quite few different guides online directing the use of a Pi.

I run two:  one is on a circa 2012 Dell Optiplex connected to Verizon business service in Brooklyn, NY.  The other is running in a Debian virtual machine on my Threadripper-powered desktop/server.  Both run without a hitch.

N7TAE's build is not only easier to build and install, but also has few extra features like DExtra linking.  He has also done a good bit of work cleaning up the code.  It is more stable than the main build, and can run for weeks or months without issue.

One other thing included in Tom's build is the ability to set it up for ipv6 connectivity.  The ability for every device to have its own global address solves a lot of problems with reflectors and hotspots.  I have my reflectors setup for ipv6 connectivity for D-Star, Fusion, and DMR.  The newest builds of DMRGateway and YSFClients have the ability to use ipv6 connections, and well as QnetGateway does for D-Star.

181 - 200 of 1680