AMBED


Ken KE2N
 

can someone help  me with instructions to use the NW Digital 6-channel device with Analog Bridge?  I have AMBED on the same machine as my DVSwitch install and have used it with XLXD so I know that it works.  Will analog bridge talk to the 6-channel USB device directly, or do I run AMBED and set some port numbers accordingly?   If the 6 channel device is out of the question, I do have a pair of ThumbDV's that could be pressed into service.

Thanks
Ken


Steve N4IRS
 

Ken,
You are in uncharted waters. We have no experience with the 6 channel device. If AMBED emulates AMBEServer that might work. 

On 07/23/2018 09:52 PM, Ken KE2N via Groups.Io wrote:
can someone help  me with instructions to use the NW Digital 6-channel device with Analog Bridge?  I have AMBED on the same machine as my DVSwitch install and have used it with XLXD so I know that it works.  Will analog bridge talk to the 6-channel USB device directly, or do I run AMBED and set some port numbers accordingly?   If the 6 channel device is out of the question, I do have a pair of ThumbDV's that could be pressed into service.

Thanks
Ken


Ken KE2N
 

ok... - while waiting for somebody who knows the answer to that, what is the approved method?  Do I plug in the ThumbDV's and install AMBEServer? and where do I find that program (for a conventional machine not a raspberry pi).

Thanks again


Steve N4IRS
 

You don't have to use AMBEServer. Analog_Bridge will use a thumbdv directly


 


On Mon, Jul 23, 2018, 19:59 Ken KE2N via Groups.Io <ke2n=cs.com@groups.io> wrote:
ok... - while waiting for somebody who knows the answer to that, what is the approved method?  Do I plug in the ThumbDV's and install AMBEServer? and where do I find that program (for a conventional machine not a raspberry pi).

Thanks again


Ken KE2N
 

OK - thanks for that. But apparently I do not need AMBEserver if the device is a ThumbDV.

Can AMBEserver talk to the 6-channel device? if so, what does the config file look like?


 

No AMBEserver does not support the 3006 -- ambed is the current solution and is only used by the xlx reflector system.

On Tue, Jul 24, 2018 at 8:51 AM, Ken KE2N via Groups.Io <ke2n@...> wrote:
OK - thanks for that. But apparently I do not need AMBEserver if the device is a ThumbDV.

Can AMBEserver talk to the 6-channel device? if so, what does the config file look like?



--


John D. Hays
Edmonds, WA
K7VE

   


Steve N4IRS
 

Ken,
This begs the questions:
How many bridges that you are planning will need a Vocoder (Remember you will need 2 for transcoding)
How many bridges that you are planning will involve D-Star

The only mode that will benefit from a HW Vocoder is D-Star. All other modes can be done in SW.

Hope this helps.

Steve N4IRS

On 7/24/2018 11:51 AM, Ken KE2N via Groups.Io wrote:
OK - thanks for that. But apparently I do not need AMBEserver if the device is a ThumbDV.

Can AMBEserver talk to the 6-channel device? if so, what does the config file look like?


Matthew 2E0SIP
 

My fork of AMBEServer will *possibly* get a 3003 working with Analog_bridge, but only a single channel, which is a bit of a waste - https://github.com/marrold/AMBEServer
 
If it doesn't work, I'd be interested in getting it working by exposing each transcoder as a separate socket, but I have a project due in a month and not enough hours in the day, and Id have to check its possible 
 


Ken KE2N
 

I am building DV switch on the same box where I was experimenting with XLX - so the device was already there.  Initially I got some audio to pass from DMR to analog and it sounded kind of "muddy" so I thought I would give the hardware a try.  I may want DSTAR in this too so I would have some hardware transcoding in any case.

I unplugged the 6 channel device and plugged in two ThumDV's. They appear as /dev/ttyUSB0 and /dev/ttyUSB1.
I modified the ini file and have this startup (below) -
>> are the error messages anything to worry about?
>> do I need to add a line for USB1 ?


M: 2018-07-24 18:24:22.584 Setting [DV3000] address -> /dev/ttyUSB0
M: 2018-07-24 18:24:22.584 Setting [DV3000] baud -> 460800
M: 2018-07-24 18:24:22.584 Setting [DV3000] serial -> true
W: 2018-07-24 18:24:22.584 ioctl reset error
W: 2018-07-24 18:24:22.584 ioctl speed error
W: 2018-07-24 18:24:22.584 ioctl stereo error
W: 2018-07-24 18:24:22.584 ioctl setfmt error
M: 2018-07-24 18:24:22.584 Audio In/Out Device: /dev/null
I: 2018-07-24 18:24:22.584 Open UDP listener on 127.0.0.1:31100
I: 2018-07-24 18:24:22.584 Open USRP on 127.0.0.1:32001
M: 2018-07-24 18:24:22.584 Connecting to DV3000 hardware......
M: 2018-07-24 18:24:22.631 Begin DV3000 decode
M: 2018-07-24 18:24:22.631 DV3000 latency is currently set to 16



Steve N4IRS
 

Each copy of Analog_Bridge can only use one Vocoder. So, for USB1 you will have a second copy of Analog_Bridge.
These lines are meaningless and should be gone.
W: 2018-07-24 18:24:22.584 ioctl reset error
W: 2018-07-24 18:24:22.584 ioctl speed error
W: 2018-07-24 18:24:22.584 ioctl stereo error
W: 2018-07-24 18:24:22.584 ioctl setfmt error

I thought they were removed in the current version of AB. I suggest a apt-get update and a apt-get upgrade.

The line I'm most concerned about is:
M: 2018-07-24 18:24:22.631 DV3000 latency is currently set to 16

You want this at 1.
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer

Verify it is now at 1:
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer

Steve N4IRS

On 7/24/2018 2:42 PM, Ken KE2N via Groups.Io wrote:
I am building DV switch on the same box where I was experimenting with XLX - so the device was already there.  Initially I got some audio to pass from DMR to analog and it sounded kind of "muddy" so I thought I would give the hardware a try.  I may want DSTAR in this too so I would have some hardware transcoding in any case.

I unplugged the 6 channel device and plugged in two ThumDV's. They appear as /dev/ttyUSB0 and /dev/ttyUSB1.
I modified the ini file and have this startup (below) -
>> are the error messages anything to worry about?
>> do I need to add a line for USB1 ?


M: 2018-07-24 18:24:22.584 Setting [DV3000] address -> /dev/ttyUSB0
M: 2018-07-24 18:24:22.584 Setting [DV3000] baud -> 460800
M: 2018-07-24 18:24:22.584 Setting [DV3000] serial -> true
W: 2018-07-24 18:24:22.584 ioctl reset error
W: 2018-07-24 18:24:22.584 ioctl speed error
W: 2018-07-24 18:24:22.584 ioctl stereo error
W: 2018-07-24 18:24:22.584 ioctl setfmt error
M: 2018-07-24 18:24:22.584 Audio In/Out Device: /dev/null
I: 2018-07-24 18:24:22.584 Open UDP listener on 127.0.0.1:31100
I: 2018-07-24 18:24:22.584 Open USRP on 127.0.0.1:32001
M: 2018-07-24 18:24:22.584 Connecting to DV3000 hardware......
M: 2018-07-24 18:24:22.631 Begin DV3000 decode
M: 2018-07-24 18:24:22.631 DV3000 latency is currently set to 16




Ken KE2N
 


Analog Bridge Version 1.1 Wed May 30 15:46:26 EDT 2018

latency is still at 16



Steve N4IRS
 

AB does not change thelatency, use the echo I included.
Do you still see?
W: 2018-07-24 18:24:22.584 ioctl reset error
W: 2018-07-24 18:24:22.584 ioctl speed error
W: 2018-07-24 18:24:22.584 ioctl stereo error
W: 2018-07-24 18:24:22.584 ioctl setfmt error


On 7/24/2018 3:04 PM, Ken KE2N via Groups.Io wrote:

Analog Bridge Version 1.1 Wed May 30 15:46:26 EDT 2018

latency is still at 16




Ken KE2N
 

Sorry - yes, now that I wrote a "1" in there, it is staying at that value, even with a restart. 
But the ioctl error is still there

M: 2018-07-24 22:00:20.681 Setting [DV3000] address -> /dev/ttyUSB0
M: 2018-07-24 22:00:20.681 Setting [DV3000] baud -> 460800
M: 2018-07-24 22:00:20.681 Setting [DV3000] serial -> true
W: 2018-07-24 22:00:20.681 ioctl reset error 
W: 2018-07-24 22:00:20.681 ioctl speed error 
W: 2018-07-24 22:00:20.681 ioctl stereo error 
W: 2018-07-24 22:00:20.681 ioctl setfmt error 
M: 2018-07-24 22:00:20.681 Audio In/Out Device: /dev/null
I: 2018-07-24 22:00:20.681 Open UDP listener on 127.0.0.1:31100
I: 2018-07-24 22:00:20.681 Open USRP on 127.0.0.1:32001
M: 2018-07-24 22:00:20.681 Connecting to DV3000 hardware......
M: 2018-07-24 22:00:20.691 Begin DV3000 decode
M: 2018-07-24 22:00:20.691 DV3000 latency is currently set to 1

============================================================
How is the second instance of AB configured?
Does one instance have the TxPorts and the other the RxPorts?
I am using the port numbering scheme shown in the "ASL to DMR Bridge how to"

Thanks
Ken


Steve N4IRS
 

As I said you can ignore those lines.
Did you do a apt-get update and a apt-get upgrade?
What was the result?

Sent via smoke signal (AT&T)




On Tue, Jul 24, 2018 at 6:10 PM -0400, "Ken KE2N via Groups.Io" <ke2n@...> wrote:

Sorry - yes, now that I wrote a "1" in there, it is staying at that value, even with a restart. 
But the ioctl error is still there

M: 2018-07-24 22:00:20.681 Setting [DV3000] address -> /dev/ttyUSB0
M: 2018-07-24 22:00:20.681 Setting [DV3000] baud -> 460800
M: 2018-07-24 22:00:20.681 Setting [DV3000] serial -> true
W: 2018-07-24 22:00:20.681 ioctl reset error 
W: 2018-07-24 22:00:20.681 ioctl speed error 
W: 2018-07-24 22:00:20.681 ioctl stereo error 
W: 2018-07-24 22:00:20.681 ioctl setfmt error 
M: 2018-07-24 22:00:20.681 Audio In/Out Device: /dev/null
I: 2018-07-24 22:00:20.681 Open UDP listener on 127.0.0.1:31100
I: 2018-07-24 22:00:20.681 Open USRP on 127.0.0.1:32001
M: 2018-07-24 22:00:20.681 Connecting to DV3000 hardware......
M: 2018-07-24 22:00:20.691 Begin DV3000 decode
M: 2018-07-24 22:00:20.691 DV3000 latency is currently set to 1

============================================================
How is the second instance of AB configured?
Does one instance have the TxPorts and the other the RxPorts?
I am using the port numbering scheme shown in the "ASL to DMR Bridge how to"

Thanks
Ken


Ken KE2N
 

to clarify - these results are after having done the update/upgrade as you recommended.