Date   

DVmega stick (new to DMR user)

Brian Helm <helmet.head22@...>
 

I'm a new-to-DMR user and have BlueDV installed and working with a DVmega stick.  I am connected to Brandmeister DMR talkgroups and can make contacts just fine now.  I notice that when others speak, I mostly see their name and callsign appear in the software window.  However, when I transmit, I just see my DMR ID.  Is this normal and is there any way to get my call/name to appear?  I've looked at blueDV settings...I've logged into the brandmeister network and looked for settings I have also tried the Update-->Update call database... in blueDV as someone suggested.  I have had my DMR ID for several months.  Any other suggestions?
Brian K5CIS

[Note: DVMega and BlueDV are not products of NW Digital Radio.

BlueDV is a popular application for ThumbDV™ and there are knowledgeable users on this list.  

DVMega questions should go to the manufacturer]


Re: How To install AMBESERVER on Raspbian or Debian.

 


On Sat, Aug 8, 2020, 08:55 John Anderson via groups.io <mi0aaz=yahoo.co.uk@groups.io> wrote:
AMBEserver[366]: AMBEserver: Couldn't find start byte in serial data

Is what i get happening when i use the instructions above and checking the status of my Combitronics DV30 stick on a VM running Debian with the dongle plugged in at the server itself, how can i sort this ?

73 Mi0AAZ.


Re: How To install AMBESERVER on Raspbian or Debian.

 

Derek,

This should work with compatible AMBE devices from other manufacturers.  We do not provide technical support for other manufacturers, if you run into difficulties, contact the manufacturer.

You will need to stop and disable  ambeserver@ThumbDV (using systemctl)
You will need to see what 'serial' port your device enumerates to, such as /dev/ttyUSB0
You will need to look at the conf files in /etc/opendv and see if one matches your device, e.g. port and speed, with a name matching your device's /dev filename.
You can then start/stop/status/enable/disable using the systemctl command.
The selection of the port number is flexible in the conf file for a variety of reasons, just use what your client is using.




On Tue, Jul 28, 2020 at 2:20 AM Derek William Haden <facebook@...> wrote:

Looking at the instructions, it reads that it is for ThumbDV.

I am using the DVmega version, I assume it will also work?

I also have another question, not sure if this is the place for it but here goes anyway.

The Ambeserver uses port 2460, however when running DVswitch and the Ambeserver together DVswitch uses 2471?
Just curious as to why?



--
John D. Hays
Kingston, WA
K7VE

 


Re: How To install AMBESERVER on Raspbian or Debian.

Derek William Haden
 

Looking at the instructions, it reads that it is for ThumbDV.

I am using the DVmega version, I assume it will also work?

I also have another question, not sure if this is the place for it but here goes anyway.

The Ambeserver uses port 2460, however when running DVswitch and the Ambeserver together DVswitch uses 2471?
Just curious as to why?


Re: How To install AMBESERVER on Raspbian or Debian.

Ken Kayser
 

Absolutely brilliant.  Couldn't be easier.


 

The Wiki is updated.


 

A new AMBEserver install process is available at https://github.com/nwdigitalradio/ambeserver-install


Re: How To install AMBESERVER on Raspbian or Debian.

 

https://github.com/nwdigitalradio/ambeserver-install/blob/master/README.md (this is a new install procedure, it has been tested - send feedback if you try it.)


On Sun, Jul 26, 2020, 01:04 Derek William Haden <facebook@...> wrote:
Thank you John

That was my best guess, but just wanted to be sure.


Re: How To install AMBESERVER on Raspbian or Debian.

Derek William Haden
 

Thank you John

That was my best guess, but just wanted to be sure.


Re: How To install AMBESERVER on Raspbian or Debian.

 

/etc/systemd/system 

Is the correct location for user created/installed service files. 


On Sat, Jul 25, 2020, 10:07 Derek William Haden <facebook@...> wrote:

Thanks for a great tutorial.

However I do have a question.

In the section about using WinSCP it says to copy the ambeserver@... file to

lib/systemd/system 

However in the following section regarding setting the permissions for the file it points to

/etc/lib/systemd/system

My Rpi 3 with Buster does not have /etc/lib/systemd/system

So where Should the file go?


Re: How To install AMBESERVER on Raspbian or Debian.

Derek William Haden
 

Thanks for a great tutorial.

However I do have a question.

In the section about using WinSCP it says to copy the ambeserver@... file to

lib/systemd/system 

However in the following section regarding setting the permissions for the file it points to

/etc/lib/systemd/system

My Rpi 3 with Buster does not have /etc/lib/systemd/system

So where Should the file go?


Re: bringing some transcoding to my xlx reflector?

w8mw
 

A pair of dongles can be used on the channel that needs the transcoding, so you need a pair for however many channels you have that do transcoding. 

 

There are some cards out there (not sure about active production) that have 8 AMBE chips on them for example, so single USB will do 4 channels of transcoding.  That is what I do on xLX004, we have about 6 channels, but only 2-3 active at a time.

 

Mike

Kb8zgl

 

 

From: "ambe@nw-digital-radio.groups.io" <ambe@nw-digital-radio.groups.io> on behalf of "Justin Mann via groups.io" <w9fyi@...>
Reply-To: "ambe@nw-digital-radio.groups.io" <ambe@nw-digital-radio.groups.io>
Date: Tuesday, July 21, 2020 at 12:26 PM
To: "ambe@nw-digital-radio.groups.io" <ambe@nw-digital-radio.groups.io>
Subject: Re: [ambe] bringing some transcoding to my xlx reflector?

 

So the reflectors have a total of 25 modules.  That means I’d need 52 of them?  assuming each module a, b, c, is a channel?



On Jul 21, 2020, at 11:08 AM, Ernie Gm7kbk <erniepratt@...> wrote:

 

You need 2 dongles per channel. Ambe software is in the xlx download.


From: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io> on behalf of Justin Mann via groups.io <w9fyi@...>
Sent: Tuesday, July 21, 2020 4:33:34 PM
To: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io>
Subject: [ambe] bringing some transcoding to my xlx reflector?

 

Hi all,

 

I’m totally new with this, so I hope you will forgive my lack of knowledge, and/or what is needed with regards to my goals, and objectives in this post.

I’ve just recently setup an xlx reflector:

with the goal of bringing, d-star, DMR, and fusion to the local Texas Ih-35 system. Currently the Texas i35 system is on FCS, reflector 3, room 30, and I believe that it has a wires-x room 40096.  I’ve gone ahead, and created an x-reflector which is now showing up as reflector 94, and it’s ip address is:

96.126.124.4.

As I understand things, I can't cross-mode out of the box with an xlx reflector, thus I need some kind of Ambe chip to do this?  I currently use D-star, and I have a number of pi-star enabled hotspots, as well as an openspot 3.  What kind of transcoding will an xlx reflector do natively, and where to the Ambecoder chips come in to play?  Also, I have the reflector sitting on a box at linode.com in Dallas, is all of this still doable, even though the reflector is in a remote location?  I know D-star, Dmr, and fusion, but I’ve not been familiar with how to bring everything together, and admittedly I’ having to teach myself Linux.  To setup the xlx reflector, I followed the tutorial at

Anything y’all can do to help I’d appreciate,

Thanks

Justin-ai5os.

 

 


Re: bringing some transcoding to my xlx reflector?

Ryan Matthew Headley
 

You would only need 52 chips if you anticipated all 26 modules being used simultaneously.  That would likely never happen.  

Three is four pairs is typically quite sufficient.  If you only want to transcode one module, you can set xlxd that way.

On Tue, 21 Jul 2020, 12:26 Justin Mann via groups.io, <w9fyi=me.com@groups.io> wrote:
So the reflectors have a total of 25 modules.  That means I’d need 52 of them?  assuming each module a, b, c, is a channel?

On Jul 21, 2020, at 11:08 AM, Ernie Gm7kbk <erniepratt@...> wrote:

You need 2 dongles per channel. Ambe software is in the xlx download.


From: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io> on behalf of Justin Mann via groups.io <w9fyi@...>
Sent: Tuesday, July 21, 2020 4:33:34 PM
To: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io>
Subject: [ambe] bringing some transcoding to my xlx reflector?
 
Hi all,

I’m totally new with this, so I hope you will forgive my lack of knowledge, and/or what is needed with regards to my goals, and objectives in this post.
I’ve just recently setup an xlx reflector:
with the goal of bringing, d-star, DMR, and fusion to the local Texas Ih-35 system. Currently the Texas i35 system is on FCS, reflector 3, room 30, and I believe that it has a wires-x room 40096.  I’ve gone ahead, and created an x-reflector which is now showing up as reflector 94, and it’s ip address is:
96.126.124.4.
As I understand things, I can't cross-mode out of the box with an xlx reflector, thus I need some kind of Ambe chip to do this?  I currently use D-star, and I have a number of pi-star enabled hotspots, as well as an openspot 3.  What kind of transcoding will an xlx reflector do natively, and where to the Ambecoder chips come in to play?  Also, I have the reflector sitting on a box at linode.com in Dallas, is all of this still doable, even though the reflector is in a remote location?  I know D-star, Dmr, and fusion, but I’ve not been familiar with how to bring everything together, and admittedly I’ having to teach myself Linux.  To setup the xlx reflector, I followed the tutorial at
Anything y’all can do to help I’d appreciate,
Thanks
Justin-ai5os.



Re: bringing some transcoding to my xlx reflector?

Justin Mann
 

So the reflectors have a total of 25 modules.  That means I’d need 52 of them?  assuming each module a, b, c, is a channel?

On Jul 21, 2020, at 11:08 AM, Ernie Gm7kbk <erniepratt@...> wrote:

You need 2 dongles per channel. Ambe software is in the xlx download.


From: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io> on behalf of Justin Mann via groups.io <w9fyi@...>
Sent: Tuesday, July 21, 2020 4:33:34 PM
To: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io>
Subject: [ambe] bringing some transcoding to my xlx reflector?
 
Hi all,

I’m totally new with this, so I hope you will forgive my lack of knowledge, and/or what is needed with regards to my goals, and objectives in this post.
I’ve just recently setup an xlx reflector:
with the goal of bringing, d-star, DMR, and fusion to the local Texas Ih-35 system. Currently the Texas i35 system is on FCS, reflector 3, room 30, and I believe that it has a wires-x room 40096.  I’ve gone ahead, and created an x-reflector which is now showing up as reflector 94, and it’s ip address is:
96.126.124.4.
As I understand things, I can't cross-mode out of the box with an xlx reflector, thus I need some kind of Ambe chip to do this?  I currently use D-star, and I have a number of pi-star enabled hotspots, as well as an openspot 3.  What kind of transcoding will an xlx reflector do natively, and where to the Ambecoder chips come in to play?  Also, I have the reflector sitting on a box at linode.com in Dallas, is all of this still doable, even though the reflector is in a remote location?  I know D-star, Dmr, and fusion, but I’ve not been familiar with how to bring everything together, and admittedly I’ having to teach myself Linux.  To setup the xlx reflector, I followed the tutorial at
Anything y’all can do to help I’d appreciate,
Thanks
Justin-ai5os.



Re: bringing some transcoding to my xlx reflector?

 

You need 2 dongles per channel. Ambe software is in the xlx download.


From: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io> on behalf of Justin Mann via groups.io <w9fyi@...>
Sent: Tuesday, July 21, 2020 4:33:34 PM
To: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io>
Subject: [ambe] bringing some transcoding to my xlx reflector?
 
Hi all,

I’m totally new with this, so I hope you will forgive my lack of knowledge, and/or what is needed with regards to my goals, and objectives in this post.
I’ve just recently setup an xlx reflector:
with the goal of bringing, d-star, DMR, and fusion to the local Texas Ih-35 system. Currently the Texas i35 system is on FCS, reflector 3, room 30, and I believe that it has a wires-x room 40096.  I’ve gone ahead, and created an x-reflector which is now showing up as reflector 94, and it’s ip address is:
96.126.124.4.
As I understand things, I can't cross-mode out of the box with an xlx reflector, thus I need some kind of Ambe chip to do this?  I currently use D-star, and I have a number of pi-star enabled hotspots, as well as an openspot 3.  What kind of transcoding will an xlx reflector do natively, and where to the Ambecoder chips come in to play?  Also, I have the reflector sitting on a box at linode.com in Dallas, is all of this still doable, even though the reflector is in a remote location?  I know D-star, Dmr, and fusion, but I’ve not been familiar with how to bring everything together, and admittedly I’ having to teach myself Linux.  To setup the xlx reflector, I followed the tutorial at
Anything y’all can do to help I’d appreciate,
Thanks
Justin-ai5os.


bringing some transcoding to my xlx reflector?

Justin Mann
 

Hi all,

I’m totally new with this, so I hope you will forgive my lack of knowledge, and/or what is needed with regards to my goals, and objectives in this post.
I’ve just recently setup an xlx reflector:
with the goal of bringing, d-star, DMR, and fusion to the local Texas Ih-35 system. Currently the Texas i35 system is on FCS, reflector 3, room 30, and I believe that it has a wires-x room 40096.  I’ve gone ahead, and created an x-reflector which is now showing up as reflector 94, and it’s ip address is:
96.126.124.4.
As I understand things, I can't cross-mode out of the box with an xlx reflector, thus I need some kind of Ambe chip to do this?  I currently use D-star, and I have a number of pi-star enabled hotspots, as well as an openspot 3.  What kind of transcoding will an xlx reflector do natively, and where to the Ambecoder chips come in to play?  Also, I have the reflector sitting on a box at linode.com in Dallas, is all of this still doable, even though the reflector is in a remote location?  I know D-star, Dmr, and fusion, but I’ve not been familiar with how to bring everything together, and admittedly I’ having to teach myself Linux.  To setup the xlx reflector, I followed the tutorial at
Anything y’all can do to help I’d appreciate,
Thanks
Justin-ai5os.


Re: Linking Peanut Server to Fusion Room

Alain | VA2WE
 

Good morning Patrick: I am using an OpenSpot 1 and it serves as a bridge between my Fusion repeater (conencted to room 28104 on my HRI-200) and my YSF CHARC reflector on whick Peanut is connected. This is an indirect way to connect Wires-X to Peanut! It works perfectly. OpenSpot 1 is a great device. Too bad they don't manaufacture it anaymore.Am I answering your question?


Re: Linking Peanut Server to Fusion Room

mfle2001
 

Hi Patrick,
I'd be interested in more detail about how your setup "WIRES x is happening between a Yaesu HRI-200 and an Allstar node in analog mode" is happening.

In regard to Alain's query I host an AMBE server for XLX301. The YSF server at another QTH is hosted on XLX and registered at: https://register.ysfreflector.de/register Then we provided the details to David and a week or so later it was all working. If there is any problem check on the peanut dashboard that your AMBE server is online - mine has required an occasional restart.

Mike
VK2AMF

At 07:14 AM 21/07/2020, Patrick Perdue wrote:

Are you talking about WIRES x or YSF? I'm new to any C4FM stuff, but as I understand it, you generally can't connect to YSF reflectors from WIRES x repeaters. No problem if you have a hotspot.

You can host a YSF reflector on XLX, and have Peanut connected to that as DMR, thus no codec translation is required other than the AMBE dongle you already have. This is how I'm doing it, in fact, as part of a system involving DMR, DStar, echo link, Allstar, Peanut, YSF, and WIRES x. In my case, WIRES x is happening between a Yaesu HRI-200 and an Allstar node in analog mode, since I don't have a Yaesu radio to make a digital link. But, if you want to digitall involve WIRES x, it gets a lot more complicated. You'll need a hotspot, a Yaesu radio, such as the FT-M100 or FT-400DR, and an HRI-200 connected to the radio in order to host the WIRES x room, plus a Windows PC to run the WIRES x software. So, you don't need a repeater as such, but if you want to truly connect to WIRES x, you need all this extra gear just to get on the network.

If all you want is YSF support, that's much easier. There are instructions for auto-linking a particular XLX module to the YSF reflector hosted by XLXD, involves changing a couple of lines in part of the XLXD source and compiling with those changes. Then, you can have Peanut connected to your XLX reflector and module using the DMR master server rather than the DStar way, which seems to be the default way to connect XLXD to Peanut. If you want to connect to module A, use TG 4001. For module B, use 4002... and so on. If you connect as DStar, you'll need two more AMBE dongles for your XLX reflector in order to translate DMR/YSF to DStar and back, plus another AMBE dongle to translate to and from Peanut itself, which is why I suggest having it connected as if it is a DMR master server instead... unless David does support YSF connections now, in which case you could just go directly to that.


On 5/30/2020 10:25 AM, Alain Reid wrote:

Folks, I am trying to achieve what PA7LIM describes below: My goal that is to allow an amateur with Peanuts Client on his Android / Windows to have a QSO with an amateur who uses his Yeasu FT3D on my Fusion repeater. So I followed PA7LIM procedure described below:
[]Â

I set up an AMBEserver on a Raspberry PI 4 using a ThumbDV. That works well. It did not work with DVStick30 unfortunately. In reference to the red dots above, my questions are the following:
Q1: Do I really have to build a YSF repeater or I can just provide PA7LIM with my Room number  so he can connects is Peanut server to my Fusion Room number?  Q2: Do I need to set up a YSF Server and than link it to my Fusion Room number and  forward that to PA7LIM with  the Hostname and port of the YSF server? Thank you folks if you can bright some light! 73!

Mike Fleetwood
Canberra Australia and Sidcup UK.

Worldwide email address is:      mfleetwood@...


Re: blocked ip address

mfle2001
 

They may not know who their "customers" are as they likely just know an IP address is consuming bandwidth and want to avoid their system grinding to a halt. I suspect with connected hotspots all traffic on the reflector is relayed to them and no way to know if it is actually being listened to.

Mike
VK2AMF


At 05:25 AM 19/07/2020, you wrote:

Typical mentality of people who are closed and don't communicate with their customers.   Totally within their right to run their reflector system as they would like.  It  would be better if the software were improved so that it would disconnect those long connecting folks after some time of inactivity that is clearly published instead of blocking.    Repeaters have had timeouts since at least the 1970s so not a new concept.     Guess the DPlus roadmap is full up with features in progress.    If someone knows where to add feature suggestions I'll be glad to put this one in.Â
73,
Robert, WB4DHC

On Sat, Jul 18, 2020 at 2:52 PM Lou Fisher <bhu1954@...> wrote:
Reflector one has been doing that for a while now  lot of people with same problem.   Have heard 30 might start doing it too


On Jul 18, 2020, at 12:37 PM, John D Hays - K7VE <john@...> wrote:


Be aware, this has nothing to do with your ThumbDV™.

The ThumbDVâ„¢ simply converts audio (PCM) to AMBE and AMBE to audio (PCM) via a USB based serial port, all connectivity to reflectors, repeaters, etc. is a function of the program that is using the ThumbDV™ and/or the reflector, repeater, etc. to which that program is communicating.

Please address concerns with the reflector operator or software developer for the reflector.  (Most REF reflectors run DPLUS by AA4RC).

On Sat, Jul 18, 2020 at 10:28 AM kk4lzx <Kk4lzx@...> wrote:
I’m having the same problem from my ThumbDV. 

JohnA


On Jul 18, 2020, at 08:02, William Shepherd via groups.io <washephe=yahoo.com@groups.io > wrote:

Just recently I haven't been able to link to ref001c nor its dashboard from my shack computer.  All other links, dashborads and modes work just fine.  In researching this problem and speaking with a few dstar users, I believe my ip address has been blocked.  It seems they will block you if you link with more than one device or something.  Maybe I did that.  I don't know.  But it has been suggested to contact the administrator of ref001c to clear the block.  Does anyone one know how to contact the administrator?Â

Thanks,
William KJ4ZEO



--
John D. Hays
Kingston, WA
K7VE

Â

Mike Fleetwood
Canberra Australia and Sidcup UK.

Worldwide email address is:      mfleetwood@...


Re: Linking Peanut Server to Fusion Room

Patrick Perdue
 

Are you talking about WIRES x or YSF? I'm new to any C4FM stuff, but as I understand it, you generally can't connect to YSF reflectors from WIRES x repeaters. No problem if you have a hotspot.

You can host a YSF reflector on XLX, and have Peanut connected to that as DMR, thus no codec translation is required other than the AMBE dongle you already have. This is how I'm doing it, in fact, as part of a system involving DMR, DStar, echo link, Allstar, Peanut, YSF, and WIRES x. In my case, WIRES x is happening between a Yaesu HRI-200 and an Allstar node in analog mode, since I don't have a Yaesu radio to make a digital link. But, if you want to digitall involve WIRES x, it gets a lot more complicated. You'll need a hotspot, a Yaesu radio, such as the FT-M100 or FT-400DR, and an HRI-200 connected to the radio in order to host the WIRES x room, plus a Windows PC to run the WIRES x software. So, you don't need a repeater as such, but if you want to truly connect to WIRES x, you need all this extra gear just to get on the network.

If all you want is YSF support, that's much easier. There are instructions for auto-linking a particular XLX module to the YSF reflector hosted by XLXD, involves changing a couple of lines in part of the XLXD source and compiling with those changes. Then, you can have Peanut connected to your XLX reflector and module using the DMR master server rather than the DStar way, which seems to be the default way to connect XLXD to Peanut. If you want to connect to module A, use TG 4001. For module B, use 4002... and so on. If you connect as DStar, you'll need two more AMBE dongles for your XLX reflector in order to translate DMR/YSF to DStar and back, plus another AMBE dongle to translate to and from Peanut itself, which is why I suggest having it connected as if it is a DMR master server instead... unless David does support YSF connections now, in which case you could just go directly to that.


On 5/30/2020 10:25 AM, Alain Reid wrote:

Folks, I am trying to achieve what PA7LIM describes below: My goal that is to allow an amateur with Peanuts Client on his Android / Windows to have a QSO with an amateur who uses his Yeasu FT3D on my Fusion repeater. So I followed PA7LIM procedure described below:
 


I set up an AMBEserver on a Raspberry PI 4 using a ThumbDV. That works well. It did not work with DVStick30 unfortunately. In reference to the red dots above, my questions are the following:
Q1: Do I really have to build a YSF repeater or I can just provide PA7LIM with my Room number  so he can connects is Peanut server to my Fusion Room number?  Q2: Do I need to set up a YSF Server and than link it to my Fusion Room number and  forward that to PA7LIM with  the Hostname and port of the YSF server? Thank you folks if you can bright some light! 73!

461 - 480 of 1840