Re: Non NW Ambe Support

You wanna borrow one.. I got 2

On Mon, Jul 22, 2019, 8:09 PM Robert Alford via Groups.Io <Mw1coe=[email protected]> wrote:

[email protected]

They were only like $65

On Mon, Jul 22, 2019, 7:33 AM Robert Alford via Groups.Io <Mw1coe=[email protected]> wrote:
No I got them from another

On Mon, Jul 22, 2019, 6:30 AM Tom Early <n7tae@...> wrote:
Where did you get them? Is this the DVMEGA DVstick30?

Re: Non NW Ambe Support

#15

[email protected]

They were only like $65

Show quoted text

On Mon, Jul 22, 2019, 7:33 AM Robert Alford via Groups.Io <Mw1coe=[email protected]> wrote:

No I got them from another

On Mon, Jul 22, 2019, 6:30 AM Tom Early <n7tae@...> wrote:
Where did you get them? Is this the DVMEGA DVstick30?

Re: Not in Cache error message

#14

I tried XRF757 A, XRF002 A and DCS299 F.? Everytime I get these errors:

n9ko@n9ko-Latitude-D830:~$ bin/qdv

read 62 indicies from /home/n9ko/.config/qdv/announce/index.dat

Host map contains:

568 XLX_Hosts.txt

499 DExtraHosts.txt

422 DCS_Hosts.txt

441 DPlus_Hosts.txt

0 MyHosts.txt

Initialized AMBE3000R version V120.E100.XXXX.C106.G514.R009.B0

Failed to connect to socket am2link : Connection refused

Re: Not in Cache error message

#13

qdv now will preload all routes in your list when it starts up.

DExtra and DCS linking work, but something has happened to DPlus linking. I'll look at it when I get back later this week.

Re: Non NW Ambe Support

#12

No I got them from another

Show quoted text

On Mon, Jul 22, 2019, 6:30 AM Tom Early <n7tae@...> wrote:

Where did you get them? Is this the DVMEGA DVstick30?

Re: Not in Cache error message

#11

OK.? I just had? a QSO on Dstar1, so it is working.? I loaded this mainly to be able to use my ThumbDV on my Linux laptop for REF and XRF reflectors, including those not in Quadnet.? I have tried linking to? REF030, XRF757 and nothing happens.? Will this type of linking be available?

Tnx

Re: Non NW Ambe Support

#10

Where did you get them? Is this the DVMEGA DVstick30?

Re: Not in Cache error message

#9

This is normal, at least for now.

When a gateway first starts up, it has an empty cache, where callsign->repeater->gateway->IP_address are kept. This cache is is populated as each node on the IRC network keys up. Then everyone else gets the info about which user used which repeater and gateway. Routing groups "key up" once an hour to let everyone know they are still there.

So if you key up and right away, you cache is empty and you get the "please try again" messsage. In this case, your gateway will ask the Quadnet server where to find your target. Within a few milliseconds the server will respond with the info you need, the next time you key up, you will connect. When you do, the routing server will callsign-route back to you and you will hear a telephone ring as your confirmation that you have logged in to the routing group (or logged out).

I will add code that will do a "find" for every callsign in your routing list when you first start. The you will see them listed right after the "Finding Routes for..." message. Look for this in a later release. I will let you know on this thread when I have pushed this up to my github.

Not in Cache error message

#8

I keep gettng a "Not in Cache" message.? I tried Dstar1 and Dstar2.? ?The install looks like it went OK.? Using Ubuntu 18.04 LTS on a 64bit Dell D830 with 4 GB RAM.

22:00:37: findRoutes = [22:00:37: ]

22:00:37: Repeater callsign: [N9KO-A]

22:00:37: connecting to rr.openquad.net at 9007

22:00:37: Waiting for rr.openquad.net connection status of 2

22:00:37: rr.openquad.net status=0

22:00:42: rr.openquad.net status=0

22:00:47: rr.openquad.net status=0

22:00:52: IRC server is using IPV4

22:00:52: QnetGateway...entering processing loop

22:00:52: get_irc_data thread[0] started

22:00:59: Finding Routes for...

WELCOME_TO_QUADNET

22:01:07: id=84e1 start RPTR flag0=00 ur=DSTAR2? ?r1=N9KO? ?A r2=N9KO? ?G my=N9KO? ? /QDV?

22:01:07: could not find a repeater for user DSTAR2??

22:01:07: User [DSTAR2? ] not in local cache, try again

22:01:13: id=84e1 END RPTR

NOT_IN_CACHE

?

Re: Non NW Ambe Support

#7

I got 2 maybe I can loan ya one..

Show quoted text

On Sun, Jul 21, 2019, 3:15 PM Robert Alford via Groups.Io <Mw1coe=[email protected]> wrote:

I use it on bluedv. Works on dmr and dstar, also receives c4fm as bluedv doesn't fully support c4fm yet for tx
On Sun, Jul 21, 2019, 12:49 PM Tom Early <n7tae@...> wrote:
It doesn't look like it's fully compatible with the AMBE-3000. According to Google Translate, there is no D-Star en/de-coding, only DMR. Apparently, this chip is used in Chinese DMR radios.

It looks like this is a no-go for qdv, unless you can find evidence that it can be used for D-Star.

On 7/21/19 8:07 AM, Robert Alford wrote:

So after a Little Investigation it's a Clone..

It's a WT3080 Ambe 3000 Compatible Device

It Does use the 460800

I included a Schematic with some documentation but not sure if its gonna help..

Rob.
-- 
___________________________
73
n7tae (at) tearly (dot) net

Re: Non NW Ambe Support

#6

I use it on bluedv. Works on dmr and dstar, also receives c4fm as bluedv doesn't fully support c4fm yet for tx

Show quoted text

On Sun, Jul 21, 2019, 12:49 PM Tom Early <n7tae@...> wrote:

It doesn't look like it's fully compatible with the AMBE-3000. According to Google Translate, there is no D-Star en/de-coding, only DMR. Apparently, this chip is used in Chinese DMR radios.

It looks like this is a no-go for qdv, unless you can find evidence that it can be used for D-Star.

On 7/21/19 8:07 AM, Robert Alford wrote:

So after a Little Investigation it's a Clone..

It's a WT3080 Ambe 3000 Compatible Device

It Does use the 460800

I included a Schematic with some documentation but not sure if its gonna help..

Rob.
-- 
___________________________
73
n7tae (at) tearly (dot) net

Re: Non NW Ambe Support

#5

开云体育

It doesn't look like it's fully compatible with the AMBE-3000. According to Google Translate, there is no D-Star en/de-coding, only DMR. Apparently, this chip is used in Chinese DMR radios.

It looks like this is a no-go for qdv, unless you can find evidence that it can be used for D-Star.

On 7/21/19 8:07 AM, Robert Alford wrote:

So after a Little Investigation it's a Clone..

It's a WT3080 Ambe 3000 Compatible Device

It Does use the 460800

I included a Schematic with some documentation but not sure if its gonna help..

Rob.

-- 
___________________________
73
n7tae (at) tearly (dot) net

Re: Non NW Ambe Support

#4

the Device was /dev/tty/USB0

Show quoted text

On Sun, Jul 21, 2019 at 10:07 AM Robert Alford via Groups.Io <Mw1coe=[email protected]> wrote:

So after a Little Investigation it's a Clone..

It's a WT3080 Ambe 3000 Compatible Device

It Does use the 460800

I included a Schematic with some documentation but not sure if its gonna help..

Rob.

--

No trees were killed in the sending of this message. However, a large number of electrons were terribly inconvenienced !

Re: Non NW Ambe Support

#3

So after a Little Investigation it's a Clone..

It's a WT3080 Ambe 3000 Compatible Device

It Does use the 460800

I included a Schematic with some documentation but not sure if its gonna help..

Rob.

BAO3000.pdf

Re: Non NW Ambe Support

#2

It depends on how easy it would be to add it...

If you can give me the details of the device, I will see what I can do. Where does the device show up under /dev? What baudrate does it need? Are there any serial parameters that it needs that would be considered non-standard? Most importantly, is it using the same AMBE-3000 chip as the ThumbDV? If not, I will probably need to get my hands on a device and the manufacturers documentation. In that case, it would also be nice to start with an already published, working driver. My CDV3000U C++ class driver is based on open-source work by K7VE, NH6Z and G4KLX, so my driver design was the easy part of the qdv development.

Non NW Ambe Support

#1

Hi..

Are there any future plans to support non NW Ambe Boards as I have 2 that come up as Serial but the Program wont detect them.

Thanks

Rob.

mw1coe