Date   

Test

Ed W8VT
 

Test. 
Please ignore.


Oddly

Ken KE2N
 


the non-functional transmit data in the log shows a "src=" number that I do not recognize

 DMR, Begin TX: src=13157013 rpt=315146902 dst=315148 slot=2 cc=6 metadata=315146901

In your how-to example, the src= is the same number as metadata=   in mine it's not.

I searched through my ini files and I cannot find 13157013 anywhere.    Perhaps because this is not a valid number (not in the CSV files) it is not letting it transmit? 


Re: : [DVSwitch] stanzas

Steve N4IRS
 

I don't see anything that jumps out. One thing to try is:
gatewayDmrId = 3151469

On 07/24/2018 10:11 PM, Ken KE2N via Groups.Io wrote:

No problem

 

Here is one (mmdvm)

 

[DMR]

Enable=1

ColorCode=6

EmbeddedLCOnly=1

DumpTAData=0

 

And perhaps you meant this one (dvswitch)

 

[DMR]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 31100                  ; Port to send AMBE TLV frames to (export)

RXPort = 31103                  ; Port to listen on (import)

Slot = 2                        ; Export slot

 

==============

 

 

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Tuesday, July 24, 2018 8:39 PM
To: main@DVSwitch.groups.io
Subject: Re: : [DVSwitch] stanzas

 

Sorry,
I should have also asked for the [DMR] stanza.

On 07/24/2018 08:36 PM, Ken KE2N via Groups.Io wrote:

Yessir  (some white space squeezed out here):

 

 

[AMBE_AUDIO]

address = 127.0.0.1    ; IP address of xx_Bridge

txPort = 31103         ; Transmit TLV frames to partner on this port

rxPort = 31100         ; Listen for TLV frames from partner on this port

ambeMode = DMR         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)

minTxTimeMS = 3000     ; Minimum time in MS for hang delay (0-10000)

 

; The metadata below is used when ASL is the source since it does not have any concept of digital modes

gatewayDmrId = 315146901      ; ID to use when transmitting from Analog_Bridge

repeaterID = 315146902        ; ID of source repeater

txTg = 315148                 ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge

txTs = 2                      ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge

colorCode = 6                 ; Color Code to assign DMR frames

 

= = = = = =

 

[General]

Callsign=KE2N

Id=315145701

Timeout=180

Duplex=0

 

[DMR Network]

Enable=1

Address=74.91.114.19

Port=62031

Jitter=360

Local=62032

Password=passw0rd

Slot1=1

Slot2=1

Debug=0

 

= = = = = =

 



Re: : [DVSwitch] stanzas

Ken KE2N
 

No problem

 

Here is one (mmdvm)

 

[DMR]

Enable=1

ColorCode=6

EmbeddedLCOnly=1

DumpTAData=0

 

And perhaps you meant this one (dvswitch)

 

[DMR]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 31100                  ; Port to send AMBE TLV frames to (export)

RXPort = 31103                  ; Port to listen on (import)

Slot = 2                        ; Export slot

 

==============

 

 

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Tuesday, July 24, 2018 8:39 PM
To: main@DVSwitch.groups.io
Subject: Re: : [DVSwitch] stanzas

 

Sorry,
I should have also asked for the [DMR] stanza.

On 07/24/2018 08:36 PM, Ken KE2N via Groups.Io wrote:

Yessir  (some white space squeezed out here):

 

 

[AMBE_AUDIO]

address = 127.0.0.1    ; IP address of xx_Bridge

txPort = 31103         ; Transmit TLV frames to partner on this port

rxPort = 31100         ; Listen for TLV frames from partner on this port

ambeMode = DMR         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)

minTxTimeMS = 3000     ; Minimum time in MS for hang delay (0-10000)

 

; The metadata below is used when ASL is the source since it does not have any concept of digital modes

gatewayDmrId = 315146901      ; ID to use when transmitting from Analog_Bridge

repeaterID = 315146902        ; ID of source repeater

txTg = 315148                 ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge

txTs = 2                      ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge

colorCode = 6                 ; Color Code to assign DMR frames

 

= = = = = =

 

[General]

Callsign=KE2N

Id=315145701

Timeout=180

Duplex=0

 

[DMR Network]

Enable=1

Address=74.91.114.19

Port=62031

Jitter=360

Local=62032

Password=passw0rd

Slot1=1

Slot2=1

Debug=0

 

= = = = = =

 


Re: : [DVSwitch] stanzas

Steve N4IRS
 

Sorry,
I should have also asked for the [DMR] stanza.

On 07/24/2018 08:36 PM, Ken KE2N via Groups.Io wrote:

Yessir  (some white space squeezed out here):

 

 

[AMBE_AUDIO]

address = 127.0.0.1    ; IP address of xx_Bridge

txPort = 31103         ; Transmit TLV frames to partner on this port

rxPort = 31100         ; Listen for TLV frames from partner on this port

ambeMode = DMR         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)

minTxTimeMS = 3000     ; Minimum time in MS for hang delay (0-10000)

 

; The metadata below is used when ASL is the source since it does not have any concept of digital modes

gatewayDmrId = 315146901      ; ID to use when transmitting from Analog_Bridge

repeaterID = 315146902        ; ID of source repeater

txTg = 315148                 ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge

txTs = 2                      ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge

colorCode = 6                 ; Color Code to assign DMR frames

 

= = = = = =

 

[General]

Callsign=KE2N

Id=315145701

Timeout=180

Duplex=0

 

[DMR Network]

Enable=1

Address=74.91.114.19

Port=62031

Jitter=360

Local=62032

Password=passw0rd

Slot1=1

Slot2=1

Debug=0

 

= = = = = =



: [DVSwitch] stanzas

Ken KE2N
 

Yessir  (some white space squeezed out here):

 

 

[AMBE_AUDIO]

address = 127.0.0.1    ; IP address of xx_Bridge

txPort = 31103         ; Transmit TLV frames to partner on this port

rxPort = 31100         ; Listen for TLV frames from partner on this port

ambeMode = DMR         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)

minTxTimeMS = 3000     ; Minimum time in MS for hang delay (0-10000)

 

; The metadata below is used when ASL is the source since it does not have any concept of digital modes

gatewayDmrId = 315146901      ; ID to use when transmitting from Analog_Bridge

repeaterID = 315146902        ; ID of source repeater

txTg = 315148                 ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge

txTs = 2                      ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge

colorCode = 6                 ; Color Code to assign DMR frames

 

= = = = = =

 

[General]

Callsign=KE2N

Id=315145701

Timeout=180

Duplex=0

 

[DMR Network]

Enable=1

Address=74.91.114.19

Port=62031

Jitter=360

Local=62032

Password=passw0rd

Slot1=1

Slot2=1

Debug=0

 

= = = = = =


Re: sorry

Steve N4IRS
 

Please show your complete [AMBE_AUDIO] stanza in Analog_Bridge.ini
Also show the [General] and [DMR Network] stanzas in MMDVM_Bridge.ini

Steve

On 07/24/2018 07:28 PM, Ken KE2N via Groups.Io wrote:
Following this thread back, I think you were telling me that I need two fob's to do DMR to DSTAR.  I understand the AB's would be  cascaded to do that.  Right now I am just doing DMR to analog,  but I am only getting it to work in one direction - from DMR to analog.  In the direction from analog to DMR, MMDVM_Bridge says it is TX'ing, but the repeater does not key up.  I am using the repeater's own address as a talkgroup and have configured that address as a static TG on TS2 in the repeater's configuration.  That approach worked with Open Spot.

in the mmdvm output, the repeater's address appears in the "dst=" field, the slot and color code are correct. 
I am not sure any of the other data is important.

Begin TX: src=13157013 rpt=315146902 dst=315148 slot=2 cc=6 metadata=315146901
 


Re: AMBED

Ken KE2N
 

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


sorry

Ken KE2N
 

Following this thread back, I think you were telling me that I need two fob's to do DMR to DSTAR.  I understand the AB's would be  cascaded to do that.  Right now I am just doing DMR to analog,  but I am only getting it to work in one direction - from DMR to analog.  In the direction from analog to DMR, MMDVM_Bridge says it is TX'ing, but the repeater does not key up.  I am using the repeater's own address as a talkgroup and have configured that address as a static TG on TS2 in the repeater's configuration.  That approach worked with Open Spot.

in the mmdvm output, the repeater's address appears in the "dst=" field, the slot and color code are correct. 
I am not sure any of the other data is important.

Begin TX: src=13157013 rpt=315146902 dst=315148 slot=2 cc=6 metadata=315146901
 


Re: AMBED

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


Re: AMBED

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


Re: AMBED

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




Re: AMBED

Ken KE2N
 


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

latency is still at 16



Re: AMBED

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




Re: AMBED

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



Re: AMBED

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 
 


Re: AMBED

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?


Re: AMBED

 

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

   


Re: AMBED

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?


Re: AMBED

 


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

7941 - 7960 of 9882