Date   

Re: dstar repeater config

 


You need to make sure dstarrepeater or dstarrepeaterd is completely stopped before running dstarrepeater 1

Then you will see the correct values -- which should be hw:0.0 (udrc)

Also you probably want to do this, so the built-in sound chip doesn't show up:

Optionally disable the internal sound chip by editing /boot/config.txt and commenting out this line (recommended unless you need it for something else):
#dtparam=audio=on
https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-For-Simplex-Hotspots-and-Converted-Analog-Repeaters

On Tue, Jan 3, 2017 at 6:21 PM, Ted McArthur <kb7pab@...> wrote:

I am wondering if this is correct setting in the Modem Tab I thought it used to be something else.




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


dstar repeater config

Ted McArthur
 

I am wondering if this is correct setting in the Modem Tab I thought it used to be something else.


Re: Hotspot with Kenwood D700

 

On Dec 28, 2016 08:00, "Ted Leonard" <w3vgted@...> wrote:
I would like to use my UDRC ll with a Kenwood D700 is it as simple as just using the 6 pin Din plug on the front of the radio? Are there any special settings to make on the radio?

Thanks, Ted W3VG





Hotspot with Kenwood D700

 

I would like to use my UDRC ll with a Kenwood D700 is it as simple as just using the 6 pin Din plug on the front of the radio? Are there any special settings to make on the radio?

Thanks, Ted W3VG


Re: ThumbDV and AMBEserver : Couldn't find start byte in serial data -> SOLVED

 

Great that you solved it. If you are using Raspbian Jesse or Compass Linux using systemd is recommended over init.d

On Dec 28, 2016 07:25, "Santu OTTAVI" <t.ottavi@...> wrote:
Hi,

Le 27/12/2016 à 23:00, John D Hays - K7VE a écrit :
Are you sure the ThumbDV is at /dev/ttyUSB0 ? (ls /dev/ttyUSB?)

Yes, it's on /dev/ttyUSB0. Here's what "dmesg" says :
  FTDI USB Serial Device converter now attached to ttyUSB0

Have you tried the python test scripts?

Yes. Using it on /dev/ttyUSB0, speed 460800, of course with ThumbDV connected :
-------------------------------------
...
Version
6100010031
Wrote: 5 bytes
a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes
a -------------------------------------


If you have a Windows box handy, you can also test using ThumbTest.exe from https://nw-digital-radio.groups.io/g/ambe/files

Done :
-------------------------------------
Enter COM port value (Default: COM1): COM20
Baud Rate(default:9600): 460800
a ☺ 9
a ♂ 0AMBE3000R
a 1 1V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
-------------------------------------

If it is a newly purchased ThumbDV the baud rate is 460800
Brand new, ordered last month.

--
After re-checking all, reinstalling init.d script, and rebooting, it works !!!

--
I think the reason of the failure was I had an init.d startup script with the default speed (230400). This may have sent scrambled data to the serial port during boot, causing odd behavior later (even with the right speed settings).

For people who may encounter the same problem later, my init.d startup script contains the following line :
  /usr/bin/AMBEserver -d -i /dev/ttyUSB0 -s 460800


73 de TK1BI






Re: ThumbDV and AMBEserver : Couldn't find start byte in serial data -> SOLVED

Santu OTTAVI (TK1BI)
 

Hi,

Le 27/12/2016 à 23:00, John D Hays - K7VE a écrit :
Are you sure the ThumbDV is at /dev/ttyUSB0 ? (ls /dev/ttyUSB?)
Yes, it's on /dev/ttyUSB0. Here's what "dmesg" says :
FTDI USB Serial Device converter now attached to ttyUSB0

Have you tried the python test scripts?
Yes. Using it on /dev/ttyUSB0, speed 460800, of course with ThumbDV connected :
-------------------------------------
...
Version
6100010031
Wrote: 5 bytes
a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes
a
-------------------------------------


If you have a Windows box handy, you can also test using ThumbTest.exe from https://nw-digital-radio.groups.io/g/ambe/files
Done :
-------------------------------------
Enter COM port value (Default: COM1): COM20
Baud Rate(default:9600): 460800
a ☺ 9
a ♂ 0AMBE3000R
a 1 1V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
-------------------------------------

If it is a newly purchased ThumbDV the baud rate is 460800
Brand new, ordered last month.

--
After re-checking all, reinstalling init.d script, and rebooting, it works !!!

--
I think the reason of the failure was I had an init.d startup script with the default speed (230400). This may have sent scrambled data to the serial port during boot, causing odd behavior later (even with the right speed settings).

For people who may encounter the same problem later, my init.d startup script contains the following line :
/usr/bin/AMBEserver -d -i /dev/ttyUSB0 -s 460800


73 de TK1BI


Re: ThumbDV and AMBEserver : Couldn't find start byte in serial data

 

Are you sure the ThumbDV is at /dev/ttyUSB0 ? (ls /dev/ttyUSB?)

Have you tried the python test scripts?

If you have a Windows box handy, you can also test using ThumbTest.exe from https://nw-digital-radio.groups.io/g/ambe/files

If it is a newly purchased ThumbDV the baud rate is 460800

On Tue, Dec 27, 2016 at 12:14 PM, Santu OTTAVI <t.ottavi@...> wrote:
Hi,

I'm trying to run AMBEserver with a ThumbDV on a Raspberry Pi 2 running Raspbian (with kernel 4.4.38).

I compiled AMBEserver from DL5DI OpenDV GitHub.

I try to run it with the following command :
  /usr/bin/AMBEserver -d -i /dev/ttyUSB0 -s 460800

It seems to start :
  AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 bps.

Then, after a few seconds, I get the following errors :
  AMBEserver: Couldn't find start byte in serial data
  AMBEserver: error receiving response to reset
  AMBEserver: Could not initialize the DV3K!

ThumbDV is brand new, out-of-the-box. I tried both speeds of 230400 and 460800, with same results.

Please note I didn't follow the installation procedure described here :
https://nw-digital-radio.groups.io/g/ambe/wiki/Installing-AMBEserver-on-a-Raspberry-Pi-and-ThumbDV%E2%84%A2
(I do not want to use an 'exotic' Linux distribution, I'd like to run it on standard Raspbian).

Thank you in advance. 73 de TK1BI










--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: ThumbDV and AMBEserver : Couldn't find start byte in serial data

Ian
 

Santu,

I too had a similar problem with my ThumbDV until I changed over to compasslinux; I found it easier to use Compass as it is Raspbian Jessie with the UDRC driver and a few other minor updates and is available as lite or with GUI.

My version is:-
Linux compass03 4.4.22-v7+ #1 SMP Thu Sep 29 05:45:46 EDT 2016 armv7l GNU/Linux

and is running on a PI2 and PI3.

Just my thoughts.

Regards,
Ian..



Linux compass03 4.4.22-v7+ #1 SMP Thu Sep 29 05:45:46 EDT 2016 armv7l GNU/Linux

On 27-12-2016 20:14, Santu OTTAVI wrote:
Hi,
I'm trying to run AMBEserver with a ThumbDV on a Raspberry Pi 2
running Raspbian (with kernel 4.4.38).
I compiled AMBEserver from DL5DI OpenDV GitHub.
I try to run it with the following command :
/usr/bin/AMBEserver -d -i /dev/ttyUSB0 -s 460800
It seems to start :
AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 bps.
Then, after a few seconds, I get the following errors :
AMBEserver: Couldn't find start byte in serial data
AMBEserver: error receiving response to reset
AMBEserver: Could not initialize the DV3K!
ThumbDV is brand new, out-of-the-box. I tried both speeds of 230400
and 460800, with same results.
Please note I didn't follow the installation procedure described here :
https://nw-digital-radio.groups.io/g/ambe/wiki/Installing-AMBEserver-on-a-Raspberry-Pi-and-ThumbDV%E2%84%A2
(I do not want to use an 'exotic' Linux distribution, I'd like to run
it on standard Raspbian).
Thank you in advance. 73 de TK1BI


ThumbDV and AMBEserver : Couldn't find start byte in serial data

Santu OTTAVI (TK1BI)
 

Hi,

I'm trying to run AMBEserver with a ThumbDV on a Raspberry Pi 2 running Raspbian (with kernel 4.4.38).

I compiled AMBEserver from DL5DI OpenDV GitHub.

I try to run it with the following command :
/usr/bin/AMBEserver -d -i /dev/ttyUSB0 -s 460800

It seems to start :
AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 bps.

Then, after a few seconds, I get the following errors :
AMBEserver: Couldn't find start byte in serial data
AMBEserver: error receiving response to reset
AMBEserver: Could not initialize the DV3K!

ThumbDV is brand new, out-of-the-box. I tried both speeds of 230400 and 460800, with same results.

Please note I didn't follow the installation procedure described here :
https://nw-digital-radio.groups.io/g/ambe/wiki/Installing-AMBEserver-on-a-Raspberry-Pi-and-ThumbDV%E2%84%A2
(I do not want to use an 'exotic' Linux distribution, I'd like to run it on standard Raspbian).

Thank you in advance. 73 de TK1BI


Re: error: unable to retrieve device version

j.lineback
 

Follow your instincts  and browse for DStar.  The first hit you should see is dstarinfo.  Front page says "Am I registered?"

Sent from my iPhone

On Dec 23, 2016, at 10:03 PM, Jp Colville <colville500@...> wrote:



On Fri, Dec 23, 2016 at 3:52 PM John D Hays - K7VE <john@...> wrote:
REF030 C  and REF001 C  are two of the busiest - connect to them and listen for awhile.  Try putting out a call.

I don't use WinDV on a day to day basis (I tend to use RF or Buster with AMBEserver), so perhaps someone who does can provide additional input.


On Mon, Dec 19, 2016 at 9:47 PM, Jp Colville <colville500@...> wrote:
ok John....getting close....I can connect now, was messing with the gateway settings. I don't hear anyone...but  I am connected now. What should my gateway settings be?











-- aparently no one tells a guy he needs to register with the dstar network. Even the you tube vid i saw doesnt tell you that. Whynare they so secrative about getting this going, no directions from mw digital. i dont get it



John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   












Re: error: unable to retrieve device version

Jp Colville <colville500@...>
 



On Fri, Dec 23, 2016 at 3:52 PM John D Hays - K7VE <john@...> wrote:
REF030 C  and REF001 C  are two of the busiest - connect to them and listen for awhile.  Try putting out a call.

I don't use WinDV on a day to day basis (I tend to use RF or Buster with AMBEserver), so perhaps someone who does can provide additional input.


On Mon, Dec 19, 2016 at 9:47 PM, Jp Colville <colville500@...> wrote:
ok John....getting close....I can connect now, was messing with the gateway settings. I don't hear anyone...but  I am connected now. What should my gateway settings be?











-- aparently no one tells a guy he needs to register with the dstar network. Even the you tube vid i saw doesnt tell you that. Whynare they so secrative about getting this going, no directions from mw digital. i dont get it



John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   












Re: error: unable to retrieve device version

 

REF030 C  and REF001 C  are two of the busiest - connect to them and listen for awhile.  Try putting out a call.

I don't use WinDV on a day to day basis (I tend to use RF or Buster with AMBEserver), so perhaps someone who does can provide additional input.


On Mon, Dec 19, 2016 at 9:47 PM, Jp Colville <colville500@...> wrote:
ok John....getting close....I can connect now, was messing with the gateway settings. I don't hear anyone...but  I am connected now. What should my gateway settings be?




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: error: unable to retrieve device version

Jp Colville <colville500@...>
 

ok John....getting close....I can connect now, was messing with the gateway settings. I don't hear anyone...but  I am connected now. What should my gateway settings be?


Re: error: unable to retrieve device version

 

On Mon, Dec 19, 2016 at 9:24 PM, Jp Colville <colville500@...> wrote:
It was the baud rate setting.just figured that part out...but....  i am using the 1.5.8 software version. Now it seems that I am not connected, and the connect button is grayed out. i am making a little headway, that baud issue really had me going there. Thanks for your help John.




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: error: unable to retrieve device version

Jp Colville <colville500@...>
 

It was the baud rate setting.just figured that part out...but....  i am using the 1.5.8 software version. Now it seems that I am not connected, and the connect button is grayed out. i am making a little headway, that baud issue really had me going there. Thanks for your help John.


Re: error: unable to retrieve device version

 

What program? Do you have the correct com port and baud rate?

On Dec 19, 2016 21:03, "Jp Colville" <colville500@...> wrote:

got this error on both a pc and a tablet. windows 10. any ideas?


error: unable to retrieve device version

Jp Colville <colville500@...>
 

got this error on both a pc and a tablet. windows 10. any ideas?


Re: Holiday Sale on the ThumbDV for $99.95

Jose Manuel Martinez Barbera
 

What program can I use the dv3000u Thumbdv in dmr?

El El mar, 29 nov 2016 a las 22:10, Barry Bettman <k6st@...> escribió:
Is there any software to access DMR with the NW Thumbdv ?



On Tue, Nov 29, 2016 at 2:04 PM, John D Hays - K7VE <john@...> wrote:

Visit: http://nwdigitalradio.com/product/thumbdv/


















--
Enviado desde EA8EE red movil


Re: WinDV

Brendan O'Neill
 

I understand the support situation, thank you for your reply. I have attempted to get this going ion a Win 7 Enterprise laptop and I am having the exact same issues with being troubled with display issues. I have sent 5 communications to DutchStar and have zero replies, so now I have 2 different Windows versions experiencing the exact same issue with display issues keeping me from using the WinDV software.


I will look into the AmbeServer that someone else was suggesting but Buster is working and I do believe in the Keep it Simple S_____ method, so if it works why break it, right ?


73,

Brendan

KM4HRR


Re: WinDV

Scott Currie
 

I suspect an incompatibility between WinDV and Win10 and/or your computer. I have run WinDV on a Win7 system with a ThumbDV for weeks on end without any problems. WinDV is still considered beta, and has not seen any updates from Dutch*Star in some time (nearly 2 years ago). I'm not sure it was even tested on Win10.

-Scott, NS7C

On Thu, Dec 8, 2016 at 10:33 PM, Brendan O'Neill <brendan.oneill@...> wrote:

I've gone roughly 1hour w/o the app crashing or having display issues but the "stop" button to end a transmission is failing to engage once a transmission has begun. Thet's just bad amateur radio practice and if it's the app failing then that's no good. It's a pretty app but I'm not sure it's a very reliable app at this time. Well, I hope it's been noticed and addressed. I have no idea if they are reading my submissions, I get no replies.


I do not want just complain or point out faults. I do appreciate the application and the effort that's been put into it. So, thank you for the app and I hope my donation goes toward making it a better app.


73,

Brendan

KM4HRR




--
-Scott

1161 - 1180 of 2576