Date   
Re: AMBEServer Install for PiDV

Mike Besemer - WM4B
 

John,

You seriously underestimate my ability to confuse myself!

I did:

wget https://raw.githubusercontent.com/dl5di/OpenDV/master/DummyRepeater/DV3000/AMBEserver.c
gcc -o AMBEserver AMBEserver.c

sudo cp AMBEserver /usr/sbin

So I now have AMBEServer in /usr/sbin. 

Looking over the rest of the page: 

I did not have the directory "/etc/opendv", so I created it.  At that point, the XYL revoked my kitchen pass.

Looks like tonight I need to create ambeserver-ttyAMA0.conf as follows:

#
# Configuration file for the AMBEserver program started by systemd.
# Adding flags to AMBESERVER_FLAGS will pass this to the daemon.
# For example, to change the speed to 460800, use the following line:
# AMBESERVER_FLAGS="-s 460800"
#

UDP_PORT=2460
AMBESERVER_FLAGS=""

Am I getting warm?

73,

Mike
WM4B



On Mon, Mar 11, 2019 at 8:10 PM, John D Hays - K7VE wrote:

 Mike,


It appears the makefile is now missing, but no worries -- try this approach



(Read the whole page.





On Mon, Mar 11, 2019 at 4:51 PM Mike Besemer < mwbesemer@...> wrote:
John,
 
Typing ‘make’ yields the following:
 
pi@raspberrypi:~/DV3000 $ make
make: *** No targets specified and no makefile found.  Stop.
pi@raspberrypi:~/DV3000 $
 
Mike
WM4B
 
 
 
From: ambe@nw-digital-radio.groups.io[mailto: ambe@nw-digital-radio.groups.io] On Behalf Of John D Hays - K7VE
Sent: Monday, March 11, 2019 7:41 PM
Subject: Re: [ambe] AMBEServer Install for PiDV
 
Hi Mike
 
On Mon, Mar 11, 2019 at 4:38 PM Mike Besemer < mwbesemer@...> wrote:
 
I get as far as the ls command (below) before things go wrong.  When I run ls, the Makefile is not there.
 
ls
AMBEserver.c  AMBEtest2.py  AMBEtest3.py  dv3000d-AMBEserver.pdf  dv3000d.c  init.d   Makefile  README-dv3000d.txt  README.txt
 
Now type --
make
 
--
 
___________________________________

John D. Hays
Edmonds, WA
K7VE
 
     
 


--

___________________________________

John D. Hays
Edmonds, WA
K7VE



     

Re: AMBEServer Install for PiDV

Mike Besemer - WM4B
 

Simple - except when it's not.

It appears that those directions are for the DVThumb, not my PiDV (DV3000).  I guess this will work if I do the following:

$ sudo nano /boot/config.txt
   init_uart_clock=3686400

$ sudo nano /etc/inittab
  Replace: T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
  With: #T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100

$ sudo nano /boot/cmdline.txtd
   Replace: wc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
   With: dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait

If I can get it to work, perhaps I'll write it up.

Unfortunatly, time to work on this is limited; I'll see what happens.

Thanks and 73,

Mike
WM4B


On Mon, Mar 11, 2019 at 7:45 PM, Clint Heffner wrote:

 This is the only one I have gotten to work recently...




Its so simple.

Clint -- KF8MZ

Re: AMBEServer Install for PiDV

Mike Besemer - WM4B
 

I'll give it a try, but I'm NOT running a DVThumb. I have the DV3000 (PiDV) attached to the GPIO headers.

I appreciate the help. It's frustrating for a newbie to have to chase problems with out-of-date documentation. I just suffered through all that getting AllStar up and running.

73,

Mike
WM4B

On Mon, Mar 11, 2019 at 8:22 PM, (null) (null) via Groups.Io wrote:

Mike 
Try this document it worked well for me, Under step 1. use this link instead of whats in the document. 

Index of /images/


| | | | Index of /images/


|

|

|



On Monday, March 11, 2019, 5:12:24 PM PDT, Clint Heffner <clintheffner@...> wrote:
This is the only one I have gotten to work recently...
https://nw-digital-radio.groups.io/g/ambe/message/703
Its so simple.
Clint -- KF8MZ


Re: AMBEServer Install for PiDV

(null) (null)
 

Mike 

Try this document it worked well for me, Under step 1. use this link instead of whats in the document. 





On Monday, March 11, 2019, 5:12:24 PM PDT, Clint Heffner <clintheffner@...> wrote:


This is the only one I have gotten to work recently...


Its so simple.

Clint -- KF8MZ

Re: AMBEServer Install for PiDV

Clint Heffner
 

This is the only one I have gotten to work recently...


Its so simple.

Clint -- KF8MZ

Re: AMBEServer Install for PiDV

 

Mike,

It appears the makefile is now missing, but no worries -- try this approach




On Mon, Mar 11, 2019 at 4:51 PM Mike Besemer <mwbesemer@...> wrote:

John,

 

Typing ‘make’ yields the following:

 

pi@raspberrypi:~/DV3000 $ make

make: *** No targets specified and no makefile found.  Stop.

pi@raspberrypi:~/DV3000 $

 

Mike

WM4B

 

 

 

From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of John D Hays - K7VE
Sent: Monday, March 11, 2019 7:41 PM
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] AMBEServer Install for PiDV

 

Hi Mike

 

On Mon, Mar 11, 2019 at 4:38 PM Mike Besemer <mwbesemer@...> wrote:

 

I get as far as the ls command (below) before things go wrong.  When I run ls, the Makefile is not there.

 

ls

AMBEserver.c  AMBEtest2.py  AMBEtest3.py  dv3000d-AMBEserver.pdf  dv3000d.c  init.d  Makefile  README-dv3000d.txt  README.txt

 

Now type --

make

 

--

 


John D. Hays
Edmonds, WA

K7VE

 

   

 



--


John D. Hays
Edmonds, WA
K7VE

   

Re: AMBEServer Install for PiDV

Mike Besemer - WM4B
 

John,

 

Typing ‘make’ yields the following:

 

pi@raspberrypi:~/DV3000 $ make

make: *** No targets specified and no makefile found.  Stop.

pi@raspberrypi:~/DV3000 $

 

Mike

WM4B

 

 

 

From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of John D Hays - K7VE
Sent: Monday, March 11, 2019 7:41 PM
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] AMBEServer Install for PiDV

 

Hi Mike

 

On Mon, Mar 11, 2019 at 4:38 PM Mike Besemer <mwbesemer@...> wrote:

 

I get as far as the ls command (below) before things go wrong.  When I run ls, the Makefile is not there.

 

ls

AMBEserver.c  AMBEtest2.py  AMBEtest3.py  dv3000d-AMBEserver.pdf  dv3000d.c  init.d  Makefile  README-dv3000d.txt  README.txt

 

Now type --

make

 

--

 


John D. Hays
Edmonds, WA

K7VE

 

   

 

Re: AMBEServer Install for PiDV

 

Hi Mike

On Mon, Mar 11, 2019 at 4:38 PM Mike Besemer <mwbesemer@...> wrote:


I get as far as the ls command (below) before things go wrong.  When I run ls, the Makefile is not there.


ls

AMBEserver.c  AMBEtest2.py  AMBEtest3.py  dv3000d-AMBEserver.pdf  dv3000d.c  init.d  Makefile  README-dv3000d.txt  README.txt


Now type --
make

--


John D. Hays
Edmonds, WA
K7VE

   

AMBEServer Install for PiDV

Mike Besemer - WM4B
 

Greetings,

New guy here.

Trying to get AMBEServer installed on my Pi using Method 2 here: http://nwdigitalradio.com/dv3000-ambeserver/

I get as far as the ls command (below) before things go wrong.  When I run ls, the Makefile is not there.

I am not a Linux geek, but can generally follow directions.  What am I doing wrong?

73,

Mike

WM4B

apt-get install git

 

cd

git clone https://github.com/dl5di/OpenDV.git

Cloning into ‘OpenDV’…

remote: Counting objects: 2196, done.

remote: Total 2196 (delta 0), reused 0 (delta 0)

Receiving objects: 100% (2196/2196), 29.65 MiB | 2.05 MiB/s, done.

Resolving deltas: 100% (1444/1444), done.

Checking connectivity… done.

mv OpenDV/DummyRepeater/DV3000 DV3000

rm -rf OpenDV

cd DV3000

ls

AMBEserver.c  AMBEtest2.py  AMBEtest3.py  dv3000d-AMBEserver.pdf  dv3000d.c  init.d  Makefile  README-dv3000d.txt  README.txt

Re: No light. Dongle fails test

va7vw@...
 

I am referring to a ThumbDV from NW Digital Radio.

It is showing as a USB com port on my PC.

Re: No light. Dongle fails test

va7vw@...
 

Thanks for the link. I have confirmed that it is on the correct com port.

Re: Can 6 Digit DMR IDs work with BlueDV & AMBE Servers?? #dmrid, #ambe, # amberserver

Dev 9Y4DG
 

Hi Jason,
Unfortunately..that did not work.

Thanks again for your help....73 Dev


On Fri, 22 Feb 2019 at 11:18, Jason Kingsbury <jkingsbury13@...> wrote:
Not sure if this will work, but have you tried to put a 0 (zero) in front of the six digit ID when configuring it on BlueDV? 


On Feb 8, 2019, at 1:56 PM, Dev Gosine <dgosine@...> wrote:

Good day,
                  Thank you for taking the time to read this message and also for your kind contribution to the thread.

Here are the facts.

1. I have 5 AMBE Servers.
2. I have 2 DMR IDs
3. BlueDV (Android) does not support adding an additional 2 digits to the end of the DMR ID as the DMR ID input field allows only 7 digits.
4. I have applied for additional DMR IDs, but was given five 6 digit repeater IDs.
5. This initially sounded like the perfect solution since I have 5 AMBE Servers and got 5 DMR IDs.
6. The problem is that the 6 digit DMR ID is not seen on Brandmeister's Hoseline when I transmit. This means I have absolutely no transmission being monitored on hoseline if I were to transmit.

Can anyone tell me what I'm doing wrong and possibly lead me in the correct direction.

I thank you again for all your contributions.....73 Dev, 9Y4DG
 

 



--


“Your chances of success in any undertaking can
always be measured by your belief in yourself"
       ~Robert Collier~.

The pessimist complains about the wind.
The optimist expects it to change.
The leader adjusts the sails.

                 ~John Maxwell~

Teamwork is the ability to work together toward a common vision.
The ability to direct individual accomplishment toward organizational objectives.
It is the fuel that allows common people to attain uncommon results.
      ~ Anonymous~

We believe that:

"We make a living by what we get,
We make a life by what we give!"
          ~Winston Churchill~

Re: Can 6 Digit DMR IDs work with BlueDV & AMBE Servers?? #dmrid, #ambe, # amberserver

Dev 9Y4DG
 

Thanks Jason... certainly worth a try
73 Dev

On Fri, Feb 22, 2019, 11:18 AM Jason Kingsbury <jkingsbury13@...> wrote:
Not sure if this will work, but have you tried to put a 0 (zero) in front of the six digit ID when configuring it on BlueDV? 


On Feb 8, 2019, at 1:56 PM, Dev Gosine <dgosine@...> wrote:

Good day,
                  Thank you for taking the time to read this message and also for your kind contribution to the thread.

Here are the facts.

1. I have 5 AMBE Servers.
2. I have 2 DMR IDs
3. BlueDV (Android) does not support adding an additional 2 digits to the end of the DMR ID as the DMR ID input field allows only 7 digits.
4. I have applied for additional DMR IDs, but was given five 6 digit repeater IDs.
5. This initially sounded like the perfect solution since I have 5 AMBE Servers and got 5 DMR IDs.
6. The problem is that the 6 digit DMR ID is not seen on Brandmeister's Hoseline when I transmit. This means I have absolutely no transmission being monitored on hoseline if I were to transmit.

Can anyone tell me what I'm doing wrong and possibly lead me in the correct direction.

I thank you again for all your contributions.....73 Dev, 9Y4DG
 

 

Re: No light. Dongle fails test

 

Are you referring to a ThumbDV from NW Digital Radio?

Is it showing as a com port on your computer?


On Fri, Mar 1, 2019 at 10:34 PM <va7vw@...> wrote:
If there is no light and it fails the test, is it finished or can it be repaired?



--


John D. Hays
Edmonds, WA
K7VE

   

Re: No light. Dongle fails test

 
Edited

It only lights when it tx or rx
Are you sure you have the correct com port selected in your software?
Link to a wealth of info:

https://1drv.ms/b/s!Atybf7djk0kciiYxu30hjrbQV7ba

No light. Dongle fails test

va7vw@...
 

If there is no light and it fails the test, is it finished or can it be repaired?

Re: AMBEServer DVStick 30 Compass Raspberry Pi #ambeserver

Stefsan
 

Hi Mesa,

at first ive running AMBEServer also with DV30 Stick in perfect value. I am using a normal actual raspian image on a raspi zero W and a 2b+ also.

Normally its to know that the physical port ist /dev/ttyUSB0 ( its the first USB device) and second the portspeed its 460800 Baud somewhere in the AMBEserver start script the information must transfered by starting trhe AMBEServer.

The needed Port for Application communication is 2460 UDP.


What to do: check in terminal on pi or via ssh if you can attach following folder when DV30 is connected to usb port of raspberry with command   ls /dev/ttyUSB*      it must come back with /dev/ttyUSB0 if that is right usb connection is ok

Other Problem could be that your user ( most its pi) is not in the group dailout) check with   sudo nano /etc/group   and find the line with  it must look like this ( pi is important, if not add it) dailout:x:20:pi

best is use a actual raspian and compile ( make , make install) the "github resource AMBE Server Marrold" in only 2 steps and crate a desktop start script in .config/autostart .

If you need assistance contact me its very easy.

BR Stefan DL1ESZ



Am 28.02.19 um 18:04 schrieb Al Mesa:

Hello,
I am having the following issue:
CONDITIONS: Raspberry Pi 3B+ Compass Linux, DVStick 30.
ISSUE After install without problems the AMBEserver per instructions and after start the AMBEServer service, a few seconds after the AMBEServer services stop and failed.
Please see the terminal detail:
 

^Xroot@compass:~# systemctl start ambeserver@...

root@compass:~# systemctl status ambeserver@...

ambeserver@... - DV3000 Daemon

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

   Active: active (running) since Thu 2019-02-28 11:14:00 EST; 31s ago

  Process: 20143 ExecStartPre=/bin/chmod 0660 /dev/ttyUSB0 (code=exited, status=

  Process: 20142 ExecStartPre=/bin/chgrp dialout /dev/ttyUSB0 (code=exited, stat

 Main PID: 20148 (AMBEserver)

   CGroup: /system.slice/system-ambeserver.slice/ambeserver@...

           └─20148 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyUSB0

 

Feb 28 11:14:00 compass systemd[1]: Starting DV3000 Daemon...

Feb 28 11:14:00 compass systemd[1]: Started DV3000 Daemon.

Feb 28 11:14:00 compass AMBEserver[20148]: AMBEserver: Starting...

Feb 28 11:14:00 compass AMBEserver[20148]: AMBEserver: Opened serial port /dev/t

 

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

 

pi@compass:~ $ sudo systemctl status ambeserver@...

ambeserver@... - DV3000 Daemon

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

   Active: failed (Result: exit-code) since Thu 2019-02-28 11:14:36 EST; 1min 27

  Process: 20148 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/ttyUSB0 $

  Process: 20143 ExecStartPre=/bin/chmod 0660 /dev/ttyUSB0 (code=exited, status=

  Process: 20142 ExecStartPre=/bin/chgrp dialout /dev/ttyUSB0 (code=exited, stat

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

 

Feb 28 11:14:00 compass systemd[1]: Starting DV3000 Daemon...

Feb 28 11:14:00 compass systemd[1]: Started DV3000 Daemon.

Feb 28 11:14:00 compass AMBEserver[20148]: AMBEserver: Starting...

Feb 28 11:14:00 compass AMBEserver[20148]: AMBEserver: Opened serial port /dev/t

Feb 28 11:14:36 compass systemd[1]: ambeserver@...: Main process exi

Feb 28 11:14:36 compass systemd[1]: ambeserver@...: Unit entered fai

Feb 28 11:14:36 compass systemd[1]: ambeserver@...: Triggering OnFai

Feb 28 11:14:36 compass systemd[1]: ambeserver@...: Failed with resu


I am looking for any advice or information about what I need to do to fix this problem.
 
Thank you.
 
Al
W4RAM
 
[Note: DVStick 30 is not a product of NW Digital Radio - Moderator]

AMBEServer DVStick 30 Compass Raspberry Pi #ambeserver

Al Mesa
 

Hello,
I am having the following issue:
CONDITIONS: Raspberry Pi 3B+ Compass Linux, DVStick 30.
ISSUE After install without problems the AMBEserver per instructions and after start the AMBEServer service, a few seconds after the AMBEServer services stop and failed.
Please see the terminal detail:
 

^Xroot@compass:~# systemctl start ambeserver@...

root@compass:~# systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

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

   Active: active (running) since Thu 2019-02-28 11:14:00 EST; 31s ago

  Process: 20143 ExecStartPre=/bin/chmod 0660 /dev/ttyUSB0 (code=exited, status=

  Process: 20142 ExecStartPre=/bin/chgrp dialout /dev/ttyUSB0 (code=exited, stat

 Main PID: 20148 (AMBEserver)

   CGroup: /system.slice/system-ambeserver.slice/ambeserver@...

           └─20148 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyUSB0

 

Feb 28 11:14:00 compass systemd[1]: Starting DV3000 Daemon...

Feb 28 11:14:00 compass systemd[1]: Started DV3000 Daemon.

Feb 28 11:14:00 compass AMBEserver[20148]: AMBEserver: Starting...

Feb 28 11:14:00 compass AMBEserver[20148]: AMBEserver: Opened serial port /dev/t

 

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

 

pi@compass:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

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

   Active: failed (Result: exit-code) since Thu 2019-02-28 11:14:36 EST; 1min 27

  Process: 20148 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/ttyUSB0 $

  Process: 20143 ExecStartPre=/bin/chmod 0660 /dev/ttyUSB0 (code=exited, status=

  Process: 20142 ExecStartPre=/bin/chgrp dialout /dev/ttyUSB0 (code=exited, stat

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

 

Feb 28 11:14:00 compass systemd[1]: Starting DV3000 Daemon...

Feb 28 11:14:00 compass systemd[1]: Started DV3000 Daemon.

Feb 28 11:14:00 compass AMBEserver[20148]: AMBEserver: Starting...

Feb 28 11:14:00 compass AMBEserver[20148]: AMBEserver: Opened serial port /dev/t

Feb 28 11:14:36 compass systemd[1]: ambeserver@...: Main process exi

Feb 28 11:14:36 compass systemd[1]: ambeserver@...: Unit entered fai

Feb 28 11:14:36 compass systemd[1]: ambeserver@...: Triggering OnFai

Feb 28 11:14:36 compass systemd[1]: ambeserver@...: Failed with resu


I am looking for any advice or information about what I need to do to fix this problem.
 
Thank you.
 
Al
W4RAM
 
[Note: DVStick 30 is not a product of NW Digital Radio - Moderator]

Re: Can 6 Digit DMR IDs work with BlueDV & AMBE Servers?? #dmrid, #ambe, # amberserver

Dave Amos <damos54@...>
 

Thanks WA6PX,

I will give that a try next Wednesday evening Brandmeister talk group 31771.

73,

Dave, WB7DFV

On 2/22/2019 8:45 AM, J G Shaw wrote:

In the past, I have found that Wed Not a Net Gathering on BM TG 31771. 

But, have not listened in recently – hope it hasn’t changed.

 

From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of Dave Amos
Sent: Friday, February 22, 2019 7:42 AM
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] Can 6 Digit DMR IDs work with BlueDV & AMBE Servers?? #dmrid, #ambe, # amberserver

 

Hi

I, too, have experienced connection problems running BlueDV/ThumbDV.  Make sure your thumb drive comm port is selected under "General" and "AMBE" boxes in the setup window under the "FILE" menu selection.  My ThumbDV drive is on COM36 on my computer (I do a lot of work with USB connected devices so I have some that are clear up in the high 60's).

I do not have a zero in front of my ID number and have had no issues with that.

by the way, I have not received an answer to my question regarding the Wednesday evening Not a Net Gathering.  Is it possible to connect to that net using BlueDV and if so, what is the talk group number I need to use.  Can I access via BM or do I have to select a DMR+ server connection?

73,

Dave, WB7DFV

 

On 2/8/2019 1:19 PM, Jason Kingsbury wrote:

Not sure if this will work, but have you tried to put a 0 (zero) in front of the six digit ID when configuring it on BlueDV? 


On Feb 8, 2019, at 1:56 PM, Dev Gosine <dgosine@...> wrote:

Good day,
                  Thank you for taking the time to read this message and also for your kind contribution to the thread.

Here are the facts.

1. I have 5 AMBE Servers.
2. I have 2 DMR IDs
3. BlueDV (Android) does not support adding an additional 2 digits to the end of the DMR ID as the DMR ID input field allows only 7 digits.
4. I have applied for additional DMR IDs, but was given five 6 digit repeater IDs.
5. This initially sounded like the perfect solution since I have 5 AMBE Servers and got 5 DMR IDs.
6. The problem is that the 6 digit DMR ID is not seen on Brandmeister's Hoseline when I transmit. This means I have absolutely no transmission being monitored on hoseline if I were to transmit.

Can anyone tell me what I'm doing wrong and possibly lead me in the correct direction.

I thank you again for all your contributions.....73 Dev, 9Y4DG
 

 

Re: Can 6 Digit DMR IDs work with BlueDV & AMBE Servers?? #dmrid, #ambe, # amberserver

J G Shaw
 

In the past, I have found that Wed Not a Net Gathering on BM TG 31771. 

But, have not listened in recently – hope it hasn’t changed.

 

From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of Dave Amos
Sent: Friday, February 22, 2019 7:42 AM
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] Can 6 Digit DMR IDs work with BlueDV & AMBE Servers?? #dmrid, #ambe, # amberserver

 

Hi

I, too, have experienced connection problems running BlueDV/ThumbDV.  Make sure your thumb drive comm port is selected under "General" and "AMBE" boxes in the setup window under the "FILE" menu selection.  My ThumbDV drive is on COM36 on my computer (I do a lot of work with USB connected devices so I have some that are clear up in the high 60's).

I do not have a zero in front of my ID number and have had no issues with that.

by the way, I have not received an answer to my question regarding the Wednesday evening Not a Net Gathering.  Is it possible to connect to that net using BlueDV and if so, what is the talk group number I need to use.  Can I access via BM or do I have to select a DMR+ server connection?

73,

Dave, WB7DFV

 

On 2/8/2019 1:19 PM, Jason Kingsbury wrote:

Not sure if this will work, but have you tried to put a 0 (zero) in front of the six digit ID when configuring it on BlueDV? 


On Feb 8, 2019, at 1:56 PM, Dev Gosine <dgosine@...> wrote:

Good day,
                  Thank you for taking the time to read this message and also for your kind contribution to the thread.

Here are the facts.

1. I have 5 AMBE Servers.
2. I have 2 DMR IDs
3. BlueDV (Android) does not support adding an additional 2 digits to the end of the DMR ID as the DMR ID input field allows only 7 digits.
4. I have applied for additional DMR IDs, but was given five 6 digit repeater IDs.
5. This initially sounded like the perfect solution since I have 5 AMBE Servers and got 5 DMR IDs.
6. The problem is that the 6 digit DMR ID is not seen on Brandmeister's Hoseline when I transmit. This means I have absolutely no transmission being monitored on hoseline if I were to transmit.

Can anyone tell me what I'm doing wrong and possibly lead me in the correct direction.

I thank you again for all your contributions.....73 Dev, 9Y4DG