Date   

Re: DVMega AMBE3000

Steve N4IRS
 

On the NWDigital PiDV DTXEN is pulled low. I don't know if I have the schematic on the DV3000u. I ASSUME it's the same state.

Steve

On 8/28/2017 11:46 AM, Matthew 2E0SIP wrote:

Cheers Steve, that's very helpful. 

It looks like the DVMEGA AMBE3000 can generate AMBE comfort noise packets if it's not receiving any audio, I wonder if that's what's going on here-

The Voice Activity Detection (VAD) algorithm along with the Comfort Noise Insertion (CNI) feature of the AMBE-3000™ Vocoder Chip performs useful functions in systems trying to convert periods of silence, that exist in normal conversation, to savings in system bandwidth or power. VAD and CNI can be enabled by either hardware configuration pin (DTX_ENABLE TQFP pin5 BGA pin C1) or as part of a control packet. 

I will drop Guus a message and see if he has any thoughts.

Thanks again
Matthew
2E0SIP


Re: DVMega AMBE3000

Matthew 2E0SIP
 

Cheers Steve, that's very helpful. 

It looks like the DVMEGA AMBE3000 can generate AMBE comfort noise packets if it's not receiving any audio, I wonder if that's what's going on here-

The Voice Activity Detection (VAD) algorithm along with the Comfort Noise Insertion (CNI) feature of the AMBE-3000™ Vocoder Chip performs useful functions in systems trying to convert periods of silence, that exist in normal conversation, to savings in system bandwidth or power. VAD and CNI can be enabled by either hardware configuration pin (DTX_ENABLE TQFP pin5 BGA pin C1) or as part of a control packet. 

I will drop Guus a message and see if he has any thoughts.

Thanks again
Matthew
2E0SIP


Re: DVMega AMBE3000

Steve N4IRS
 



On 8/28/2017 8:38 AM, Matthew 2E0SIP wrote:

Hi Steve,

Do you have any idea why its a "no go" ? Does the carrier board not expose direct access to the AMBE 3000 chip?

Cheers

Matthew

Mike pointed this out to me.

If you look at the logs you see a constant stream of:

61000801xxxxxxxxxxxxxxxx

Where xx is an AMBE byte. 

61 = Header

00 08 = 8 bytes of payload

01 = Channel data (AMBE)

xxxxxxxxxxxxxxxx = The AMBE data


This occurs no matter what the chip is being commanded to do.
We expect to send a command followed by a response. Do not understand why we are getting more.

Steve
,_._,_

Setting serial port
Serial port parameters:
Port name:      /dev/ttyUSB1
Baudrate:       115200
Byte size:      8
Parity:         N
Stop bits:      1
Xon Xoff:       False
RTS/CTS:        False
DST/DTR:        False
a
Testing Reset DV3000
Errror, DV3000 send back invalid start byte.  Expected 0x61 and got 19 Reset DV3000
137461000801013068662d2264786100080101303e024f04432e61000801013028460967647c6100080101301c240e74066c6100080101303e024e37430e6100080101301c246b41176c61000801013078420d26217a6100080101307c062d0544526100080101303e062b21737e6100080101302e242
f61220a6100080101303c204b4242786100080101301e060c07767c6100080101303c260f07206861000801013038642d0646486100080101302a440f23472e6100080101301e202f07636e6100080101302e4628134194610008010130d4a4c56645666100080101306a626812145e6100080101303c
060f35510a6100080101303c242f02576e6100080101307c042d4776606100080101306e042e12742c6100080101302c220d2323686100080101303c206f04316e610008010130e404674776756100080101301e606b71762c61000801013068460c15274a6100080101303e206c12477a61000801013
05e24287555466100080101303e060852132e6100080101304a424d65774c6100080101306c224856477a6100080101307c206f2140726100080101304a460d42156c6100080101305e62285360246100080101304e060f22314e6100080101303e020f2652686100080101300c060b40673e61000801
01300e024f2431d66100080101308e068704646c6100080101307c024e3045786100080101307e060c1753726100080101303c262d3016c061000801013018424f25646c6100080101306c662945714261000801013068402c71556a610008010130b6260874656f6100080101300e006f02733861000
80101307c026b44757c6100080101
Testing Get Product ID
Errror, DV3000 send back invalid start byte.  Expected 0x61 and got 48 Get Product ID
306c026874256c6100080101306c062d6132426100080101301e262d14602e6100080101308e022635257d6100080101306c042c10544e6100080101303e242a77137861000801013008642d46346e6100080101303c060f20745e61000801013068424f06526a6100080101304c024c30750e6100080
101305e246b0375746100080101307e006d45662c6100080101307c260f01307461000801013068460a76637a610008010130a6260417516f6100080101305c026f04340c610008010130c2406675466f6100080101306c064d0323626100080101302e260d07710e6100080101302e024e12564e6100
080101306e242947663a6100080101304c206f03526461000801013068462f25055a61000801013084204d34566d610008010130b6240520647f6100080101303e242f05700e6100080101302e040f00356a61000801013038642d6604846100080101305c420b6567666100080101304e242941614e6
1000801013048606d20210e6100080101306c26685165766100080101303c042963135e6100080101306e026c07033a6100080101306c042b60775661000801013078626d0603686100080101302c060a76137a610008010130f2460651565f6100080101306c266d2521726100080101303a462a5347
3e6100080101301c602d27004c6100080101306a606d04646a6100080101302c040872727e61000801013068260b41463c6100080101307e024d6534246100080101301c226c10666c6100080101306e242960015a6100080101302c042967654a6100080101307a602f47323e6100080101303c424a7
0575e6100080101306c024f214172
Testing Get Version
In test Get Version
Error, did not get expected value from DV3000.  Got: 0j`l4CJ expected 1V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
01306a606c34434a
Testing Set DSTAR Mode
In test Set DSTAR Mode
Error, did not get expected value from DV3000.  Got: 0WFt expected

01304c0608574674
Testing Reset DV3000
In test Reset DV3000
Error, did not get expected value from DV3000.  Got: 0|O1. expected 9
01307c024f03312e
Testing Set DMR Mode
In test Set DMR Mode
Error, did not get expected value from DV3000.  Got: 0Hb
                                                        dG^ expected

013048620b64475e
Testing Decode AMBE
Test result: Success (6100080101302c060a74717e)
Error, did not get the right number of PCM bytes back from an encode 8


Re: DVMega AMBE3000

Matthew 2E0SIP
 

Hi Steve,

Do you have any idea why its a "no go" ? Does the carrier board not expose direct access to the AMBE 3000 chip?

Cheers

Matthew


Re: DVMega AMBE3000

Steve N4IRS
 

Nope,
I'm going to have to call this a "no go"

Steve

On 8/25/2017 9:46 AM, Matthew 2E0SIP wrote:

Hi Guys,

If it doesn't work out the box it's probably not worth spending more time on it, I was just curious as the DVMEGA AMBE 3000 is about the same cost as the ThumbDV.

I will grab a ThumbDV instead.

Thanks for investigating.



Re: DVMega AMBE3000

Steve N4IRS
 

I just had a idea I want to check before we call it a no go.

On 8/25/2017 9:46 AM, Matthew 2E0SIP wrote:

Hi Guys,

If it doesn't work out the box it's probably not worth spending more time on it, I was just curious as the DVMEGA AMBE 3000 is about the same cost as the ThumbDV.

I will grab a ThumbDV instead.

Thanks for investigating.



Re: DVMega AMBE3000

Matthew 2E0SIP
 

Hi Guys,

If it doesn't work out the box it's probably not worth spending more time on it, I was just curious as the DVMEGA AMBE 3000 is about the same cost as the ThumbDV.

I will grab a ThumbDV instead.

Thanks for investigating.


Re: Bug fix and other changes.

Will - N7DUD
 

Thanks for your work on this project and the bug fix!

I just wanted to let you know that your work is helping a (very active) search & rescue group communicate when outside of the range of RF sites.
It also helps one of our dispatchers (me) stay active even after moving out of the state.

Openspot (AK) -> DCI PNW C-Bridge (Thanks Mike! NO7RF) -> N-Oregon DMR Repeater System 

Thanks again!
Will - N7DUD - www.MWave.org


Re: DVMega AMBE3000

G7RPG - Peter Kendall
 

Hi Steve,

Did it turn out to be a case of "Computers Says No" ?


Peter


On 24/08/2017 18:09, Steve N4IRS wrote:
Well,
At least I'm getting data back from the AMBE3000 but it's not right. looking at the log.

Steve

On 8/24/2017 12:20 PM, G7RPG - Peter Kendall wrote:

Steve,

Just plugged it in now.


Peter


On 24/08/2017 17:14, Steve N4IRS wrote:
Peter,
I am at my desk today. If you want to put the AMBE3000 on a carrier board, I'll give it another try.

Steve




Re: DVMega AMBE3000

Steve N4IRS
 

Well,
At least I'm getting data back from the AMBE3000 but it's not right. looking at the log.

Steve

On 8/24/2017 12:20 PM, G7RPG - Peter Kendall wrote:

Steve,

Just plugged it in now.


Peter


On 24/08/2017 17:14, Steve N4IRS wrote:
Peter,
I am at my desk today. If you want to put the AMBE3000 on a carrier board, I'll give it another try.

Steve



Re: DVMega AMBE3000

G7RPG - Peter Kendall
 

Steve,

Just plugged it in now.


Peter


On 24/08/2017 17:14, Steve N4IRS wrote:
Peter,
I am at my desk today. If you want to put the AMBE3000 on a carrier board, I'll give it another try.

Steve


Re: DVMega AMBE3000

Steve N4IRS
 

Peter,
I am at my desk today. If you want to put the AMBE3000 on a carrier board, I'll give it another try.

Steve


Bug fix and other changes.

Steve N4IRS
 
Edited

Over the last few days, Cort identified a bug when OpenSpot was communicating with HBlink / HB_Bridge. Mike created a fix that has been tested and looks like it solves the issue. I have uploaded the change to the dmr_utils repository.
I suggest people do a git pull on the dmr_utils repository and then run the install.sh script. Please report here any issues you encounter. We would rather not have to chase down people experiencing a problem without reporting it to us.

Cort has decided a simplification of the repositories are in order. We will be moving some of the older, unused or superseded applications into a separate directories. This should alleviate some of the confusion new users are experiencing.
We will be making some changes in HBlink to better align it with the structure of DMRlink. In simple terms, reducing the number of small sub applications (my term) required to bring up a HBlink application. As we move forward there will be a effort to create a more unified environment.

Mike and I spoke about the issue that require people to use DMRGateway as a "shim" between HB_Bridge and XLX. We think this can be resolved with a pull request to the XLX repository. Stay tuned.

73, Steve N4IRS 
.


Re: DVMega AMBE3000

G7RPG - Peter Kendall
 

Matthew, this is the carrier board if you've not seen one, its a USB to serial converter.

http://www.combitronics.nl/index.php?route=product/product&path=61&product_id=90


On 23/08/2017 15:02, Matthew 2E0SIP wrote:

Steve - The DVMega AMBE3000 initially came out as a 'shield' that would sit on an Arduino, with an additional audio board so you could plug in a mic / speaker and hold a QSO over a D-Star(?) network via a PC without any local RF.

The next evolution was the 'carrier board' which  removed the requirement for the Arduino , and meant you could plug it directly into a PC and use the PC sound card rather than the additional audio board + Arduino.


Peter - does it look like the carrier board is doing anything other than converting USB to serial?  If not, then hopefully Analog_Bridge can interface with it directly. If there is an additional microcontroller it might be best going straight into the AMBE3000 with a serial adapter

Cheers all for taking an interest in this, much appreciated.



Re: DVMega AMBE3000

Matthew 2E0SIP
 

Steve - The DVMega AMBE3000 initially came out as a 'shield' that would sit on an Arduino, with an additional audio board so you could plug in a mic / speaker and hold a QSO over a D-Star(?) network via a PC without any local RF.

The next evolution was the 'carrier board' which  removed the requirement for the Arduino , and meant you could plug it directly into a PC and use the PC sound card rather than the additional audio board + Arduino.


Peter - does it look like the carrier board is doing anything other than converting USB to serial?  If not, then hopefully Analog_Bridge can interface with it directly. If there is an additional microcontroller it might be best going straight into the AMBE3000 with a serial adapter

Cheers all for taking an interest in this, much appreciated.


Re: DVMega AMBE3000

G7RPG - Peter Kendall
 

Steve, do you want to try with it on the carrier board ?

On 23/08/2017 13:41, Steve N4IRS wrote:
Can anyone point me to the information on the differences between on a
DVMega vs a carrier board?

Steve


Re: DVMega AMBE3000

Steve N4IRS
 

Can anyone point me to the information on the differences between on a DVMega vs a carrier board?

Steve

--
"What are HB_bridge, IPSC_bridge and Analog_bridge?"


Re: DVMega AMBE3000

Mike Zingman - N4IRR
 

What is the port name for the serial device?  /dev/ttyUSBx, /dev/ttyAMA0, something else?


Re: DVMega AMBE3000

G7RPG - Peter Kendall
 

It was sitting on an Arduino MEGA, I also have the carrier board.


On 22/08/2017 15:03, Matthew 2E0SIP wrote:
Hi All,
Guss got back to me and confirmed-
The ambe board is designed to communicate accordingly to the DVSI spec.
So hopefully it can be made to work. 

Out of curiosity Peter, were you interfacing with the AMBE directly via serial, or via the carrier board? 

Cheers
Matthew 


Re: DVMega AMBE3000

Steve N4IRS
 

I did try yesterday to communicate with Peter's install at both 115200 and 230400. I was unable to communicate. I "assume" since it was on USB1 it was the carrier board.
We need to do more looking at DummyRepeater since it supports both the ThumDV and Guus board.

Steve

On 8/22/2017 10:03 AM, Matthew 2E0SIP wrote:
Hi All,
Guss got back to me and confirmed-
The ambe board is designed to communicate accordingly to the DVSI spec.
So hopefully it can be made to work. 

Out of curiosity Peter, were you interfacing with the AMBE directly via serial, or via the carrier board? 

Cheers
Matthew 

9761 - 9780 of 10163