Date   

Re: Emulator timed out on encode!

G4WXN@...
 

I assumed you meant ps and not pa

ps ax | grep md380-emu

974 pts/0    S+     0:00 grep --color=auto md380-emu
 
--
Derek

G4WXN


Re: Emulator timed out on encode!

Steve N4IRS
 

Stop the emulator:
systemctl stop md380-emu

Check for another instance running:
pa ax | grep md380-emu



On 3/12/21 6:58 AM, G4WXN@... wrote:
All looks good in the AB log until I press PTT and then the error 

Emulator timed out on encode!

I have another install of DVS on a netbook which I normally use for DMR+ and FreeDMR, I switched that over to Brandmeister and all worked fine.

Anything else I can do to test, before I wipe the card and start again?

--
Derek

G4WXN


Re: Emulator timed out on encode!

G4WXN@...
 

All looks good in the AB log until I press PTT and then the error 

Emulator timed out on encode!

I have another install of DVS on a netbook which I normally use for DMR+ and FreeDMR, I switched that over to Brandmeister and all worked fine.

Anything else I can do to test, before I wipe the card and start again?

--
Derek

G4WXN


Re: Emulator timed out on encode!

Steve N4IRS
 

Yes it is.

On 3/12/21 6:44 AM, G4WXN@... wrote:
Here's the output from that.
Looks like the emulator is running.
---------------------
● md380-emu.service - MD-380 Emulator Service
   Loaded: loaded (/lib/systemd/system/md380-emu.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-03-12 11:07:12 GMT; 36min ago
 Main PID: 875 (md380-emu)
    Tasks: 1 (limit: 2062)
   CGroup: /system.slice/md380-emu.service
           └─875 /opt/md380-emu/md380-emu -S 2470
 
Mar 12 11:07:12 DVSwitch4 systemd[1]: Started MD-380 Emulator Service.
 
--
Derek

G4WXN


Re: Emulator timed out on encode!

G4WXN@...
 

Here's the output from that.
Looks like the emulator is running.
---------------------
● md380-emu.service - MD-380 Emulator Service
   Loaded: loaded (/lib/systemd/system/md380-emu.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-03-12 11:07:12 GMT; 36min ago
 Main PID: 875 (md380-emu)
    Tasks: 1 (limit: 2062)
   CGroup: /system.slice/md380-emu.service
           └─875 /opt/md380-emu/md380-emu -S 2470
 
Mar 12 11:07:12 DVSwitch4 systemd[1]: Started MD-380 Emulator Service.
 
--
Derek

G4WXN


Re: Emulator timed out on encode!

Steve N4IRS
 

OK, that's clean.
to verify emulator is running:
systemctl status md380-emu

On 3/12/21 6:35 AM, G4WXN@... wrote:

Sorry, posted the AB.ini from the Rpi I use for DStar

The correct one is now attached.

All was working fine early yesterday, the only problem I had at the time was that i was only seeing DMR ids on the client.

I ran DVSM_update after that this issue started.

--
Derek

G4WXN



Re: Emulator timed out on encode!

G4WXN@...
 

Sorry, posted the AB.ini from the Rpi I use for DStar

The correct one is now attached.

All was working fine early yesterday, the only problem I had at the time was that i was only seeing DMR ids on the client.

I ran DVSM_update after that this issue started.

--
Derek

G4WXN


Re: Emulator timed out on encode!

Steve N4IRS
 

These are the settings for you to look at:

[GENERAL]

; General vocoder setup information
decoderFallBack = false            ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false                ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470   ; IP address and port of the md380 server

[DV3000]
;address = 127.0.0.1               ; IP address of AMBEServer
;rxPort = 2471                     ; Port of AMBEServer
address = /dev/ttyUSB0             ; Device of DV3000U on this machine
baud = 460800                      ; Baud rate of the dongle (230400 or 460800)
serial = true                      ; Use serial=true for direct connect or serial=false for AMBEServer


You are not set to use the emulator or fall back to the vocoder built into Analog_Bridge
You are setup to use a hardware vocoder plugged into the USB port

If this is not what you want, fix the settings above.

Steve N4IRS

On 3/12/21 4:55 AM, G4WXN@... wrote:
I was seeing activity on the android device, but no audio.

How can I test to see if the emulator is running?

AB.ini file attached.

Thanks for your time.
--
Derek

G4WXN


Re: Emulator timed out on encode!

G4WXN@...
 

I was seeing activity on the android device, but no audio.

How can I test to see if the emulator is running?

AB.ini file attached.

Thanks for your time.
--
Derek

G4WXN


Re: M17 to ASL

 

Yep, that sounds reasonable.  The Codec2 server already exists, might as well make use of what's already out there.

On 12/3/21 6:14 pm, SP2ONG Waldek wrote:
The Codec2 server is used in DMRStation project:

https://github.com/ea3ihi/DMRStation/blob/master/DMRStation.ini

# md380-emu
[ambe]
ambeServerHost=127.0.0.1
ambeServerPort=2460
 

#Codec2 server

[codec2]
codec2ServerHost=127.0.0.1
codec2ServerPort=2470
enabled=0
 

So it looks like similar in Analog_Bridge


-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: M17 to ASL

 

This sounds like a really good way to do it.

On 12/3/21 6:10 pm, SP2ONG Waldek wrote:
Perhaps this would require adding Codec2 support and an M17 mode to Analog_Bridge similar to use md380-emu.
The Codec2 server version is available

https://github.com/ea3ihi/codec2

and it can be used in a similar way as md380-emu via UDP port


-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: M17 to ASL

SP2ONG Waldek
 

The Codec2 server is used in DMRStation project:

https://github.com/ea3ihi/DMRStation/blob/master/DMRStation.ini

# md380-emu
[ambe]
ambeServerHost=127.0.0.1
ambeServerPort=2460
 

#Codec2 server

[codec2]
codec2ServerHost=127.0.0.1
codec2ServerPort=2470
enabled=0
 

So it looks like similar in Analog_Bridge


Re: M17 to ASL

SP2ONG Waldek
 

Perhaps this would require adding Codec2 support and an M17 mode to Analog_Bridge similar to use md380-emu.
The Codec2 server version is available

https://github.com/ea3ihi/codec2

and it can be used in a similar way as md380-emu via UDP port


Re: Error when using AMBEserver

 

I think you have the same usb stick that I have. Played for hours had no joy . Will only work with ambeserver. When running its got a green Led.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Tony Langdon <vk3jed@...>
Sent: Friday, March 12, 2021 6:28:35 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Error when using AMBEserver
 
I'm now xperimnting with AB talking to the AMBE dongle over USB, but still no joy, even when using the actual /dev/ttyUSBn device name.

On 12/3/21 5:22 pm, Ernie Gm7kbk wrote:
I get the same problem. If I restart the ambeserver with AB running all will work fine for days.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Tony Langdon <vk3jed@...>
Sent: Friday, March 12, 2021 6:04:30 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Error when using AMBEserver
 
While I had a bit of spare time this morning, I decided to do a bit of
troubleshooting to find out why AB was apparently not using my ThumbDV
dongle for D-STAR (distorted audio being an obvious symptom!).

In test mode, I am using AMBEserver on localhost.  Eventually, I plan to
dedicate the AMBEserver to a remote instance of AB running on a VM, so
switching to local USB connection isn't an option.  Also, the AMBEserver
has previously been successfully used with BlueDV running in a local
Windows host.

I restarted AMBEserver, then restarted AB, and when AB attemoted to
connect, I got the following error repeated dozens of times by AMBEserver:

AMBEserver: invalid start byte when reading from the socket, 0x00

The system appears to recognise the AMBE dongle, and I am using a static
symlink (managed by udev rules), because there are multiple USB serial
devices, and using the ttyUSB device name would mean frequent manual
intervention.

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com







-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: Error when using AMBEserver

 

I'm now xperimnting with AB talking to the AMBE dongle over USB, but still no joy, even when using the actual /dev/ttyUSBn device name.

On 12/3/21 5:22 pm, Ernie Gm7kbk wrote:
I get the same problem. If I restart the ambeserver with AB running all will work fine for days.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Tony Langdon <vk3jed@...>
Sent: Friday, March 12, 2021 6:04:30 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Error when using AMBEserver
 
While I had a bit of spare time this morning, I decided to do a bit of
troubleshooting to find out why AB was apparently not using my ThumbDV
dongle for D-STAR (distorted audio being an obvious symptom!).

In test mode, I am using AMBEserver on localhost.  Eventually, I plan to
dedicate the AMBEserver to a remote instance of AB running on a VM, so
switching to local USB connection isn't an option.  Also, the AMBEserver
has previously been successfully used with BlueDV running in a local
Windows host.

I restarted AMBEserver, then restarted AB, and when AB attemoted to
connect, I got the following error repeated dozens of times by AMBEserver:

AMBEserver: invalid start byte when reading from the socket, 0x00

The system appears to recognise the AMBE dongle, and I am using a static
symlink (managed by udev rules), because there are multiple USB serial
devices, and using the ttyUSB device name would mean frequent manual
intervention.

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com







-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: Error when using AMBEserver

 

I get the same problem. If I restart the ambeserver with AB running all will work fine for days.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Tony Langdon <vk3jed@...>
Sent: Friday, March 12, 2021 6:04:30 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Error when using AMBEserver
 
While I had a bit of spare time this morning, I decided to do a bit of
troubleshooting to find out why AB was apparently not using my ThumbDV
dongle for D-STAR (distorted audio being an obvious symptom!).

In test mode, I am using AMBEserver on localhost.  Eventually, I plan to
dedicate the AMBEserver to a remote instance of AB running on a VM, so
switching to local USB connection isn't an option.  Also, the AMBEserver
has previously been successfully used with BlueDV running in a local
Windows host.

I restarted AMBEserver, then restarted AB, and when AB attemoted to
connect, I got the following error repeated dozens of times by AMBEserver:

AMBEserver: invalid start byte when reading from the socket, 0x00

The system appears to recognise the AMBE dongle, and I am using a static
symlink (managed by udev rules), because there are multiple USB serial
devices, and using the ttyUSB device name would mean frequent manual
intervention.

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com







Error when using AMBEserver

 

While I had a bit of spare time this morning, I decided to do a bit of
troubleshooting to find out why AB was apparently not using my ThumbDV
dongle for D-STAR (distorted audio being an obvious symptom!).

In test mode, I am using AMBEserver on localhost.  Eventually, I plan to
dedicate the AMBEserver to a remote instance of AB running on a VM, so
switching to local USB connection isn't an option.  Also, the AMBEserver
has previously been successfully used with BlueDV running in a local
Windows host.

I restarted AMBEserver, then restarted AB, and when AB attemoted to
connect, I got the following error repeated dozens of times by AMBEserver:

AMBEserver: invalid start byte when reading from the socket, 0x00

The system appears to recognise the AMBE dongle, and I am using a static
symlink (managed by udev rules), because there are multiple USB serial
devices, and using the ttyUSB device name would mean frequent manual
intervention.

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: M17 to ASL

 

Hmm, I'd have thought it better to have Analog_Bridge or an equivalent program to transcode between M17 (Codec2) and PCM.  Doing it via DMR means there's an unnecessary transcoding step, when going from M17 to ASL (i.e. going via AMBE+2), degrading audio quality unnecessarily.  I've built my multimode gateway on the principle of transcoding as few times as possible.  From any digital mode to PCM is only one transcoding operation, between any 2 modes, there is never more than 2 transcoding operations (one source to PCM, then one from PCM to the target codec).  And the release of Analog_Reflector has allowed me to (mostly) preserve metadata across modes.
`

On 12/3/21 8:46 am, Steve KC1AWV wrote:
As of now, there is only one known path to get M17 to ASL, and that is to use M172DMR.

nostar MMDVM_CM fork: https://github.com/nostar/MMDVM_CM

Using M172DMR, you can cross-mode M17 to a DMR talkgroup. Then it's a simple matter of getting that DMR TG to ASL.

If anyone's interested in creating an ASL to M17 bridge, feel free to reach out to me.

Steve KC1AWV


-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: M17 to ASL

Steve KC1AWV
 

As of now, there is only one known path to get M17 to ASL, and that is to use M172DMR.

nostar MMDVM_CM fork: https://github.com/nostar/MMDVM_CM

Using M172DMR, you can cross-mode M17 to a DMR talkgroup. Then it's a simple matter of getting that DMR TG to ASL.

If anyone's interested in creating an ASL to M17 bridge, feel free to reach out to me.

Steve KC1AWV


Re: Emulator timed out on encode!

Steve N4IRS
 

Can you receive DMR?
Is the emulator running?
Please show your AB.ini



On 3/11/21 1:56 PM, G4WXN@... wrote:
DVSwitch server connected to BM.

MMDVM_bridge log says that it's logging in correctly.

I have a selfcare account with BM and password set.

When I try to transmit from the client I get this error in the analogue bridge log.

"Emulator timed out on encode!"

After that happens the whole system appears to lock up.

appreciate any help.



--
Derek

G4WXN

821 - 840 of 9595