Date   

Re: Ambe Server Crash

Kenny Richards
 

Marco,

As a datapoint, I just checked my Pi / ThumbDV at home (running Compass), it has been running for 48 days now. The last time it was rebooted was due to me having to move it physically. AMBEServer hasn't been touched since launched and was working as of two days ago. (Last time I launched Buster)

73,
Kenny, KU7M


Re: Ambe Server Crash

Marco Della Cagna
 

Ok Thank you, at the present i take power from the USB of the router, but tomorrow i will change whit a regular power supply and i hope i will fix the problem.
My best 73
Marco / IK6IOQ


Re: Ambe Server Crash

 

Hi Marco,

A number of users have traced problems like this to an inadequate Power Supply. Make certain that you see 5V at the PI and that your connections are reliable.

Thanks,
Bryan K7UDR


Ambe Server Crash

Marco Della Cagna
 

Hallo,
I installed AMBE servers with Raspberry and Compass Linux, so my problem is that it works well for a few hours but then stops and I have to restart the Raspberry.
For your experience do you find the software AMBEServer stable ?
I use the Dvstick 30.
What I doing wrong ? How can I fix the problem? Does it happen to you too?
73 and Thank you
Marco / IK6IOQ


Re: I want to run BlueDV AMBE Server on Debian.

js3cop@...
 

Thank you for your advice.
So I installed AMBE Server, but it doesn't run.


root@debian:~# systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor pres
   Active: failed (Result: exit-code) since Wed 2018-09-26 19:42:37 JST; 36s ago
  Process: 7109 ExecStartPre=/bin/chgrp dialout /dev/ttyUSB0 (code=exited, statu

 9月 26 19:42:37 debian systemd[1]: Starting DV3000 Daemon...
 9月 26 19:42:37 debian systemd[7109]: ambeserver@...: Failed at step
 9月 26 19:42:37 debian systemd[1]: ambeserver@...: Control process e
 9月 26 19:42:37 debian systemd[1]: Failed to start DV3000 Daemon.
 9月 26 19:42:37 debian systemd[1]: ambeserver@...: Unit entered fail

Please tell me what to do.


Re: RPi server with DVMEGA AMBE3000

@mariosv
 

i use 230400 bps because with this rate running on windows. I have tried 460800 but i get buffer size error.


RPi server with DVMEGA AMBE3000

@mariosv
 

[Moderator: Questions about the DVMEGA product should addressed to it's manufacturer.  This port is included as a courtesy with respect to AMBEserver -- The first question is whether this device baud rate matches what is configured for the AMBEserver.]

-----------

Hello,
I have a DVMEGA AMBE3000 with Carier board together ( http://dvmega.auria.nl/AMBE3000_shield.html ). I have already tested on windows machine with BlueDV AMBE server and works perfect. I'm trying to use them with AMBE server on RPi 3 with compass image but i have this error

cat /var/log/syslog
Sep 25 23:08:45 compass systemd[1]: Started DV3000 Daemon.
Sep 25 23:08:45 compass AMBEserver[988]: AMBEserver: Starting...
Sep 25 23:08:45 compass AMBEserver[988]: AMBEserver: Opened serial port /dev/ttyUSB0 at 230400 bps.
Sep 25 23:08:45 compass AMBEserver[988]: AMBEserver: invalid response to reset
Sep 25 23:08:45 compass AMBEserver[988]: AMBEserver: Could not initialize the DV3K!
Sep 25 23:09:15 compass systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAILURE
Sep 25 23:09:15 compass systemd[1]: ambeserver@...: Unit entered failed state.
Sep 25 23:09:15 compass systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
Sep 25 23:09:15 compass systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 25 23:09:15 compass systemd[1]: Started Serial Getty on ttyUSB0.
Sep 25 23:09:18 compass systemd[1]: serial-getty@...: Service hold-off time over, scheduling restart.
Sep 25 23:09:18 compass systemd[1]: Stopped Serial Getty on ttyUSB0.
Sep 25 23:09:18 compass systemd[1]: Started Serial Getty on ttyUSB0.
Sep 25 23:09:19 compass systemd[1]: serial-getty@...: Service hold-off time over, scheduling restart.
Sep 25 23:09:19 compass systemd[1]: Stopped Serial Getty on ttyUSB0.
Sep 25 23:09:19 compass systemd[1]: Started Serial Getty on ttyUSB0.
Sep 25 23:09:20 compass systemd[1]: serial-getty@...: Service hold-off time over, scheduling restart.
Sep 25 23:09:20 compass systemd[1]: Stopped Serial Getty on ttyUSB0.
Sep 25 23:09:20 compass systemd[1]: Started Serial Getty on ttyUSB0.
Sep 25 23:09:22 compass systemd[1]: serial-getty@...: Service hold-off time over, scheduling restart.
Sep 25 23:09:22 compass systemd[1]: Stopped Serial Getty on ttyUSB0.
Sep 25 23:09:22 compass systemd[1]: Started Serial Getty on ttyUSB0.
Sep 25 23:09:23 compass systemd[1]: serial-getty@...: Service hold-off time over, scheduling restart.
Sep 25 23:09:23 compass systemd[1]: Stopped Serial Getty on ttyUSB0.
Sep 25 23:09:23 compass systemd[1]: serial-getty@...: Start request repeated too quickly.
Sep 25 23:09:23 compass systemd[1]: Failed to start Serial Getty on ttyUSB0.
Sep 25 23:09:23 compass systemd[1]: serial-getty@...: Unit entered failed state.
Sep 25 23:09:23 compass systemd[1]: serial-getty@...: Failed with result 'start-limit-hit'.

dmesg | grep tty
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=f2a280fb-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000423] console [tty1] enabled
[    0.640484] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    3.736739] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB0

Any help?
Thank you!


Re: "... this report of my death was an exaggeration." -- Mark Twain 1897

 

I'll place another order for the Thumb to put on the shelf as a backup and save a few $$
I have one on the shelf to be put to work at home - and the second in
the netbooks go-bag for use on the road. Now if I ever get my
portable Linux 'server' running I'll need yet another.

Bill


Re: "... this report of my death was an exaggeration." -- Mark Twain 1897

N9UMJ
 

Thanks John

Just ordered a Draws and GPS

I'll place another order for the Thumb to put on the shelf as a backup and save a few $$

Rick

On Mon, Sep 24, 2018, 7:06 PM John D Hays - K7VE <john@...> wrote:
Absolutely nothing.  It's a manufacturability change, mostly support parts on the PCB. The functionality and primary chips are the same as the current ThumbDV.


On Mon, Sep 24, 2018 at 3:57 PM N9UMJ <n9umj2@...> wrote:
Judging by the number you still have on hand. 
Don't you mean The Report of my death has been"grossly" exaggerated?

What are the differences between the sale Thumb and the new Thumb that would make.me want to wait and pay full price?

Rick n9umj

On Mon, Sep 24, 2018, 6:13 PM John D Hays - K7VE <john@...> wrote:

It was reported to me that someone on the International D-STAR net said that the ThumbDV was going out of production.  THIS IS NOT TRUE.

The ThumbDV is on sale for $99.95 on existing stock. NW Digital Radio is continuing the ThumbDV.  See http://nwdigitalradio.com/thumbdv-clearance-sale/ for details.  If you miss the sale, there is no functional difference, but the new batch will be back at full price.

It is best to go the source for information.

--


John D. Hays
Edmonds, WA
K7VE

   



--


John D. Hays
Edmonds, WA
K7VE

   


Re: "... this report of my death was an exaggeration." -- Mark Twain 1897

 

Absolutely nothing.  It's a manufacturability change, mostly support parts on the PCB. The functionality and primary chips are the same as the current ThumbDV.


On Mon, Sep 24, 2018 at 3:57 PM N9UMJ <n9umj2@...> wrote:
Judging by the number you still have on hand. 
Don't you mean The Report of my death has been"grossly" exaggerated?

What are the differences between the sale Thumb and the new Thumb that would make.me want to wait and pay full price?

Rick n9umj

On Mon, Sep 24, 2018, 6:13 PM John D Hays - K7VE <john@...> wrote:

It was reported to me that someone on the International D-STAR net said that the ThumbDV was going out of production.  THIS IS NOT TRUE.

The ThumbDV is on sale for $99.95 on existing stock. NW Digital Radio is continuing the ThumbDV.  See http://nwdigitalradio.com/thumbdv-clearance-sale/ for details.  If you miss the sale, there is no functional difference, but the new batch will be back at full price.

It is best to go the source for information.

--


John D. Hays
Edmonds, WA
K7VE

   



--


John D. Hays
Edmonds, WA
K7VE

   


Re: "... this report of my death was an exaggeration." -- Mark Twain 1897

N9UMJ
 

Judging by the number you still have on hand. 
Don't you mean The Report of my death has been"grossly" exaggerated?

What are the differences between the sale Thumb and the new Thumb that would make.me want to wait and pay full price?

Rick n9umj

On Mon, Sep 24, 2018, 6:13 PM John D Hays - K7VE <john@...> wrote:

It was reported to me that someone on the International D-STAR net said that the ThumbDV was going out of production.  THIS IS NOT TRUE.

The ThumbDV is on sale for $99.95 on existing stock. NW Digital Radio is continuing the ThumbDV.  See http://nwdigitalradio.com/thumbdv-clearance-sale/ for details.  If you miss the sale, there is no functional difference, but the new batch will be back at full price.

It is best to go the source for information.

--


John D. Hays
Edmonds, WA
K7VE

   


"... this report of my death was an exaggeration." -- Mark Twain 1897

 


It was reported to me that someone on the International D-STAR net said that the ThumbDV was going out of production.  THIS IS NOT TRUE.

The ThumbDV is on sale for $99.95 on existing stock. NW Digital Radio is continuing the ThumbDV.  See http://nwdigitalradio.com/thumbdv-clearance-sale/ for details.  If you miss the sale, there is no functional difference, but the new batch will be back at full price.

It is best to go the source for information.

--


John D. Hays
Edmonds, WA
K7VE

   


Re: Linking to XLX reflectors

Ian
 

Purely as an exercise I have XLX running on a BeagleBoneBlack and today I updated my Macbook with the resulting one-way audio.

A few minutes testing identified my problem and a workaround.

Regards,
Ian..

On 2018-09-20 20:17, Dick Herrick via Groups.Io wrote:
I suspect it’s an interim solution. Friends using Windows machines
can access 2-way audio by calling up the XLX reflectors. What you have
here is a work-around which is fine. However, I would not have known
the association between the DCS and XLX nomenclature. How did you
figure that one out?
I was able to open the plist data in 1.2.3 to compare the
“strings” in XLX and DCS plists. Sure enough they point to the
same … what appears to be … numeric DNS locations. For your
DCS600XLX600 example they both point to 13.16.14.204. So is one a
proxy for the other?
Thanks for writing back.
Dick Herrick, BEE, PE
rjherrickpe@aol.com
(Office) 704-509-2882
(Cell) 704-995-1522

On Sep 20, 2018, at 2:50 PM, Ian <gm4upx@gb7jd.co.uk> wrote:
I have Buster 1.2.3 and I experienced the same one-way effect. In
my case the cure I found is to issue a connect, for example, to
DCS600 A instead of XLX600 A.
A connection to XLX defaults to Dextra connection with one-way audio
whereas a connect to DCS defaults to DCS and audio is heard in both
directions.
Is this what you are looking for ?
Regards,
Ian..
Links:
------
[1] https://nw-digital-radio.groups.io/g/ambe/message/711
[2] https://groups.io/mt/25758194/162806
[3] https://nw-digital-radio.groups.io/g/ambe/post
[4] https://nw-digital-radio.groups.io/g/ambe/editsub/162806
[5] https://nw-digital-radio.groups.io/g/ambe/leave/defanged


Re: Linking to XLX reflectors

Annaliese McDermond
 

That’s what I figured. The dumb author of this software didn’t know who to ask about preferred protocols to the XLX reflectors and assumed that DExtra would work fine and was the easiest. I’m sure at some point in time soon that she’ll get around to shifting the protocol to connect to XLX reflectors to the DPlus or DCS link drivers instead. I heard she is getting married on Saturday, though, and has very limited time right now.

--
Annaliese McDermond (NH6Z)
Xenotropic Systems
mcdermj@xenotropic.com

On Sep 20, 2018, at 12:22 PM, Steven Blackford <kb7sqi@gmail.com> wrote:

There’s been an issue w/ use the XRF protocol w/ XLX reflectors known for a while. That’s why we recommend people use the DPLUS or DCS protocol on our XLX reflectors. I know for some, that can be an issue, but it solved all the problems we had w/ our users. 73 de K4SQI!

Steve, K4SQi

From: Dick Herrick via Groups.Io
Sent: Thursday, September 20, 2018 3:17 PM
To: ambe@nw-digital-radio.groups.io
Cc: Circuit Riders
Subject: Re: [ambe] Linking to XLX reflectors

I suspect it’s an interim solution. Friends using Windows machines can access 2-way audio by calling up the XLX reflectors. What you have here is a work-around which is fine. However, I would not have known the association between the DCS and XLX nomenclature. How did you figure that one out?

I was able to open the plist data in 1.2.3 to compare the “strings” in XLX and DCS plists. Sure enough they point to the same … what appears to be … numeric DNS locations. For your DCS600XLX600 example they both point to 13.16.14.204. So is one a proxy for the other?

Thanks for writing back.


Dick Herrick, BEE, PE
rjherrickpe@aol.com

(Office) 704-509-2882
(Cell) 704-995-1522


On Sep 20, 2018, at 2:50 PM, Ian <gm4upx@gb7jd.co.uk> wrote:

I have Buster 1.2.3 and I experienced the same one-way effect. In my case the cure I found is to issue a connect, for example, to DCS600 A instead of XLX600 A.

A connection to XLX defaults to Dextra connection with one-way audio whereas a connect to DCS defaults to DCS and audio is heard in both directions.

Is this what you are looking for ?

Regards,
Ian..



<1DC21149D24B413BA6960A02F001AE55.png>


Re: Linking to XLX reflectors

Steven Blackford
 

There’s been an issue w/ use the XRF protocol w/ XLX reflectors known for a while.  That’s why we recommend people use the DPLUS or DCS protocol on our XLX reflectors.  I know for some, that can be an issue,  but it solved all the problems we had w/ our users.  73 de K4SQI!

 

Steve, K4SQi

 

From: Dick Herrick via Groups.Io
Sent: Thursday, September 20, 2018 3:17 PM
To: ambe@nw-digital-radio.groups.io
Cc: Circuit Riders
Subject: Re: [ambe] Linking to XLX reflectors

 

I suspect it’s an interim solution.  Friends using Windows machines can access 2-way audio by calling up the XLX reflectors. What you have here is a work-around which is fine.  However, I would not have known the association between the DCS and XLX nomenclature.  How did you figure that one out?

 

I was able to open the plist data in 1.2.3 to compare the “strings” in XLX and DCS plists.  Sure enough they point to the same … what appears to be … numeric DNS locations.  For your DCS600XLX600 example they both point to 13.16.14.204.  So is one a proxy for the other?

 

Thanks for writing back.

 

 

Dick Herrick, BEE, PE
rjherrickpe@...

(Office) 704-509-2882
(Cell)    704-995-1522



On Sep 20, 2018, at 2:50 PM, Ian <gm4upx@...> wrote:

 

I have Buster 1.2.3 and I experienced the same one-way effect.  In my case the cure I found is to issue a connect, for example, to DCS600 A instead of XLX600 A.

A connection to XLX defaults to Dextra connection with one-way audio whereas a connect to DCS defaults to DCS and audio is heard in both directions.

Is this what you are looking for ?

Regards,
Ian..

 

 


Re: Linking to XLX reflectors

Dick Herrick
 

I suspect it’s an interim solution.  Friends using Windows machines can access 2-way audio by calling up the XLX reflectors. What you have here is a work-around which is fine.  However, I would not have known the association between the DCS and XLX nomenclature.  How did you figure that one out?

I was able to open the plist data in 1.2.3 to compare the “strings” in XLX and DCS plists.  Sure enough they point to the same … what appears to be … numeric DNS locations.  For your DCS600XLX600 example they both point to 13.16.14.204.  So is one a proxy for the other?

Thanks for writing back.


Dick Herrick, BEE, PE
rjherrickpe@...

(Office) 704-509-2882
(Cell)    704-995-1522

On Sep 20, 2018, at 2:50 PM, Ian <gm4upx@...> wrote:

I have Buster 1.2.3 and I experienced the same one-way effect.  In my case the cure I found is to issue a connect, for example, to DCS600 A instead of XLX600 A.

A connection to XLX defaults to Dextra connection with one-way audio whereas a connect to DCS defaults to DCS and audio is heard in both directions.

Is this what you are looking for ?

Regards,
Ian..


Re: Linking to XLX reflectors

Ian
 

I have Buster 1.2.3 and I experienced the same one-way effect.  In my case the cure I found is to issue a connect, for example, to DCS600 A instead of XLX600 A.

A connection to XLX defaults to Dextra connection with one-way audio whereas a connect to DCS defaults to DCS and audio is heard in both directions.

Is this what you are looking for ?

Regards,
Ian..


Re: Linking to XLX reflectors

Dick Herrick
 

Yes, same here.  I referred to Anna, Buster’s creator.  I’m sure she’ll take a look relatively soon.


Dick Herrick, BEE, PE
rjherrickpe@...

(Office) 704-509-2882
(Cell)    704-995-1522

On Sep 19, 2018, at 1:30 PM, Ted Huston <Jhuston1@...> wrote:

I’m using Buster on MacBook Pro and ThumbDV.  It works on REF reflectors, but not XLX reflectors.  Recent update allowed linking to XLX reflector and transmission confirmed on Dashboard.  Could not hear person I was trying to communicate with but, he could hear me (using BlueDV on a PC).  Any clues?
Ted W8JTH





Linking to XLX reflectors

Ted Huston
 

I’m using Buster on MacBook Pro and ThumbDV. It works on REF reflectors, but not XLX reflectors. Recent update allowed linking to XLX reflector and transmission confirmed on Dashboard. Could not hear person I was trying to communicate with but, he could hear me (using BlueDV on a PC). Any clues?
Ted W8JTH


Re: How To install AMBESERVER on Raspbian or Debian.

 

See updated note on the wiki


On Tue, Sep 18, 2018, 01:39 Node750Tt <node750tt@...> wrote:

[Edited Message Follows]


This will put AMBESERVER on your Raspberry Pi running Raspbian or Debian box running Stretch or Jesse. THIS IS NOT FOR COMPASS LINUX.

I am running this with ThumbDV in my Debian Box and also with my DVstick30 in my Raspberry Pi.

I am able to use my Android Phone running BlueDV Ambe from the Play store, or my Laptop with BlueDV and connect to my machines from any part of the planet.

My ThumbDV and DVstick30 are located over 10,000Km apart, and I can work D-Star or DMR stations. on my Android phone sitting at Starbucks, or an Airport, or on an Aircraft with WiFi.

Enough said let's start. I love Kali Linux, so will do all as root.

ssh into your machine, at the prompt run

sudo bash hit the enter key, you will now be root user.
nano /etc/ssh/sshd.config
scroll to the line that says
PORT 22 change 22 to any number you like.
{I WARN YOU TO REMEMBER THIS NUMBER YOU ENTERED}
Next scroll a little bit more to where you see.
# Authentication
# PermitRootLogin  blah blah. 
On that line remove the hash tag # and blah blah, then put the word yes
Ctrl + X and then Y on your keyboard.
at the prompt run:
passwd 
enter any password you want, you will see nothing as you typed in the password, hit enter, type the same password again enter
now you have full root access into your machine.
type reboot.

After the machine is rebooted ssh back in with your new ssh port number and
login as root with the root password you created.

Now run:
apt-get update
apt-get install git curl wget 
after these are installed, run:
git clone git://github.com/marrold/AMBEServer.git
cd AMBEServer
make
make install
At this point  Ambeserver is installed on your machine.

To be able to find your machine online, so before we start you will need to setup an account at one of these example: 
dyndns.org or noip.com, the list is endless, so your choice. After you make the account, create a hostname for your Raspberry Pi 
or Debian box on this website.

Next back to your machine run:
apt-get install ddclient
During the installation you will be asked to enter your login name and password to your dns host account, you setup above, and
choose what name you want to assign this machine from your account, once done, accept all the default prompts during the installation.
after you returned at the prompt run:
nano /etc/ddclient.conf
after the last line of text type in this:
Daemon=300
SSL=yes
Next on your keyboard hit Ctrl + X key together then Y key, you will be back at the prompt.

Home Router setup:
That your Pi or Debian box is connected too.
If your Machines are connected to the second or third router in your house,
it will be a bit tricky to get to your machine, not impossible, but very involved, so best put these machines on your first Router after 
your ISP Fibe optic or cable box or directly on your ISP router. Basically you want your machines getting an IP from the first router into your home.

Login into this router and set your Raspberry Pi or Debian box to get a fix IP, base on their Mac address. This is done in order for the router to always assigned the same IP whenever it reboots to your machine.
Now find the port forwarding section in your router and open 
the ssh port number you assigned above using TCP  to your machine IP address; also port 2460 use UDP. 
save and apply these changes into your router.

Now to get the AMBEserver to start automatically anytime your machine reboot do the following:
Save the script I attached somewhere on your desktop.
The easiest way:
Download and install WinSCP
Now with WinSCP login your Machine with the assign IP your set in the router and ssh port as root & root password. you assigned above.
on the right pane navigate to this directory.
lib/systemd/system 
from the left pane navigate where you save my script and dragged it in that system directory.
now close WinSCP. 

back at the machine run 
cd /etc/lib/systemd/system
chmod 644 ambeserver@...
systemctl daemon-reload
systemctl enable ambeserver@...
Now put your ThumbDV or DVstick30 into your Machine.
run 
reboot.

When your machine is back up, ssh back in and run 
systemctl status ambeserver@...
You want to see ACTIVE in GREEN. Means your server is running and you are set to use your ThumbDV or DVstick30 with BlueDV Ambe on android or BlueDV on you PC.

In the setup in BlueDV Ambe or BlueDV on PC or MAC if home use the Ip address of your machine baudrate 460800 and port 2460, when out of the home or on data on your phone use the hostname you assigned your machine at dyndns or noip.com.

I hope this helps all to get going please post your comments, and let me know if you get it going.

ps:
The ambeserver @ ttyUSB0.service is not showing properly in the post it is all one no space as I type here on this line; but look at the name of my script that is how it should be written.













921 - 940 of 1637