Date   
ThumbDV with GnuRadio

 

Tom AC2IE has built a GNU radio block for D-STAR using the ThumbDV.

DStar using GNU Radio with a ThumbDV

 

I have built GNU Radio blocks to encode and decode DStar. These blocks use NWDigitalRadio's ThumbDV for the vocoding. My OOT (out-of-tree) module is at https://github.com/ac2ie/gr-ambe3000.

The DStar Decoding block is mostly complete. The decoder prints any incoming header as well as any "slow data" in the voice frames. (Of course the main output of the decode block is the audio stream!) A GNU Radio flow-graph for a DStar receiver is included. (See the picture below.)

Encoding is still a "work-in-progress". Output of my current DStar Encoder block does not have the prepended 660-bit frame header and frame sync. The output is also not properly terminated with a terminating sync flag. In spite of these shortcomings, a flow graph is included that will transmit a valid voice stream that can be successfully received with a DStar receiver, it just won't have a header or a terminating flag. I'm still working on the details of how to implement that in GNU Radio.

Of course to transmit RF with GNU Radio you need a suitable, supported RF sink, like a HackRF or Ettus Research UHD.

73

Tom AC2IE


New file uploaded to ambe@nw-digital-radio.groups.io

ambe@nw-digital-radio.groups.io Notification <ambe+notification@...>
 

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the ambe@nw-digital-radio.groups.io group.

File: windv-1.5.8p3-win32-setup.exe

Uploaded By: John Hays

Description:
WinDV 1.5.8p3 setup package. While Dutch-Star.eu gets their DNS sorted out, we have permission to make this available to the community. It will be removed when service is restored.

You can access this file at the URL:
https://nw-digital-radio.groups.io/g/ambe/files/windv-1.5.8p3-win32-setup.exe

Cheers,
The Groups.io Team

dutch-star.eu

 

The dutch-star.eu services are back online for WinDV users/

--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: dutch-star.eu

Peter Robbins <robbins1@...>
 

Thanks John

 

Regards and 73

Peter R

VK5NAQ

Please remove my email address before forwarding this email Thanks

 

From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of John Hays
Sent: Tuesday, 19 July 2016 4:02 AM
To: ambe@nw-digital-radio.groups.io
Subject: [ambe] dutch-star.eu

 

The dutch-star.eu services are back online for WinDV users/

 

--

 


John D. Hays
K7VE

 

PO Box 1223, Edmonds, WA 98020-1223

   

 




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


HELP --- Getting ThumbDV 'really' working ...

Tom Cichowicz
 

I'm hoping to get some information that will hopefully anwser why I've only got my Thumb DV partially working.

    I just got a Thumb DV - with a few hicups and some help from John Hays -- I was able to get it configured to a point where I think it's working.


  However I can't get anyone to respond to me.

 my setup is as follows:


   Windows 7 Pro - PC

   Thumb DV DV3000U

   DV Node for Windows 1.5.8 P3

   Plantronics Headset   

Installed everything, and configured as instructions say ...

I get the VU meter to respond when I transmit and my results show I'm transmitting, but no one responds.

I've submitted my callsign for registration on my closest D-Star repeater W1SCC 

however it still shows that I'm NOT approved and yet it's been a week. I was expecting it to be quicker than that.

I REALLY hoping that my troubles are all routed in me NOT yet completing the registration process, and it's preventing me from my XMIT from working.


  I've tried contacting the the administrator of the repeater, without success. My emails have not bounced but have gone un-answered. I'm kinda stuck because I'm told that you can't register on more than one repeater at a time and don't know how to get anyone to help.

  I guess I'll just have to wait .... I started the registration before I ordered my ICOM ID51A Plus; and my Thumb DV in hopes this would be all behind me.


   Any advice or insight would be appreciated.





 I even see myself in the Reflector's website log ... ( but just as "LISTENING" )



    I can listen to gateways & reflectors -  XMIT - but no response if I was closer to the repeater I would use my HT to try as well, but it 46 miles away. That's why I wanted to go with a Tumb DV or DVAP.

Re: HELP --- Getting ThumbDV 'really' working ...

 

Dplus reflectors block unregistered users. Try xrf Or dcs reflectors.


On Jul 31, 2016 20:56, <tcichowicz@...> wrote:

I'm hoping to get some information that will hopefully anwser why I've only got my Thumb DV partially working.

    I just got a Thumb DV - with a few hicups and some help from John Hays -- I was able to get it configured to a point where I think it's working.


  However I can't get anyone to respond to me.

 my setup is as follows:


   Windows 7 Pro - PC

   Thumb DV DV3000U

   DV Node for Windows 1.5.8 P3

   Plantronics Headset   

Installed everything, and configured as instructions say ...

I get the VU meter to respond when I transmit and my results show I'm transmitting, but no one responds.

I've submitted my callsign for registration on my closest D-Star repeater W1SCC 

however it still shows that I'm NOT approved and yet it's been a week. I was expecting it to be quicker than that.

I REALLY hoping that my troubles are all routed in me NOT yet completing the registration process, and it's preventing me from my XMIT from working.


  I've tried contacting the the administrator of the repeater, without success. My emails have not bounced but have gone un-answered. I'm kinda stuck because I'm told that you can't register on more than one repeater at a time and don't know how to get anyone to help.

  I guess I'll just have to wait .... I started the registration before I ordered my ICOM ID51A Plus; and my Thumb DV in hopes this would be all behind me.


   Any advice or insight would be appreciated.





 I even see myself in the Reflector's website log ... ( but just as "LISTENING" )



    I can listen to gateways & reflectors -  XMIT - but no response if I was closer to the repeater I would use my HT to try as well, but it 46 miles away. That's why I wanted to go with a Tumb DV or DVAP.

Re: HELP --- Getting ThumbDV 'really' working ...

Tom Cichowicz
 

Thanks again John, I'll give that a try for sure. 

~TomC.

Mobile: (941) 888-4519
Ham:     KM4VIG

Sent by pressing a send button. 

On Jul 31, 2016, at 11:59 PM, John Hays <john@...> wrote:

Dplus reflectors block unregistered users. Try xrf Or dcs reflectors.


On Jul 31, 2016 20:56, <tcichowicz@...> wrote:

I'm hoping to get some information that will hopefully anwser why I've only got my Thumb DV partially working.

    I just got a Thumb DV - with a few hicups and some help from John Hays -- I was able to get it configured to a point where I think it's working.


  However I can't get anyone to respond to me.

 my setup is as follows:


   Windows 7 Pro - PC

   Thumb DV DV3000U

   DV Node for Windows 1.5.8 P3

   Plantronics Headset   

Installed everything, and configured as instructions say ...

I get the VU meter to respond when I transmit and my results show I'm transmitting, but no one responds.

I've submitted my callsign for registration on my closest D-Star repeater W1SCC 

however it still shows that I'm NOT approved and yet it's been a week. I was expecting it to be quicker than that.

I REALLY hoping that my troubles are all routed in me NOT yet completing the registration process, and it's preventing me from my XMIT from working.


  I've tried contacting the the administrator of the repeater, without success. My emails have not bounced but have gone un-answered. I'm kinda stuck because I'm told that you can't register on more than one repeater at a time and don't know how to get anyone to help.

  I guess I'll just have to wait .... I started the registration before I ordered my ICOM ID51A Plus; and my Thumb DV in hopes this would be all behind me.


   Any advice or insight would be appreciated.




<blob>


 I even see myself in the Reflector's website log ... ( but just as "LISTENING" )

<blob>


    I can listen to gateways & reflectors -  XMIT - but no response if I was closer to the repeater I would use my HT to try as well, but it 46 miles away. That's why I wanted to go with a Tumb DV or DVAP.

Call Sign & Gateway config --- questions

Tom Cichowicz
 

I know this forum is really for the hardware aspect of the device, or at least I'm assuming it is. But I'm hoping I can get some help trying to understand the operational side of the device and technology as well.

My two questions for this post are as follows.


1,)  when configuring the Call Sign suffix what do each of the letter choices represent? (I'm currently using A) I see many users with A,B,C,D

      I'm guessing that it's A=23cm  , B=70cm  , C=2m ,   D=Dongle. Should I be using 'D' as I'm connecting with a Thumb DV. ?   

2,)  when configuring a DCS gateway, the letter designation seems to select a 'group' that you are labeled with while on the reflector.

       ie. I currently use a gateway of DCS006 N  which labels me as : USA Florida Group(N)

       while listening do I hear ALL group traffic? or only those in my 'N' Group?

Need HELP getting configured on DSTAR

Tom Cichowicz
 

I'm hoping someone can help me or point me to a site that shows how to configure a Thumb DV hotspot dongle for DStar ?

   I finally got my callsign approved on W1SCC DStar repeater - I now need to configure the Terminal ID(s)  --

    I followed the video instructions from ICOM to set it up for my radio ID-51a, however I'm not sure what if anything I need to do for my Thumb DV setup running DV Node for Windows.

     All of the terminology is just alphabet soup to me right now. Until I understand abit more how this stuff works I'm kinda lost. 

     I created a second terminal on my account placing a "C" for initial, and adding a PCNAME of callsign-dongle saved it and hoped for the best. I used a "C" for initial because that's what is setup in the DV Node Client software.


     However I still can't get anyone to respond to me on the REF030 C reflector - I can connect and hear everyone fine. I XMIT and my VU moves but no one seems to hear me.

     Just looking for some resources to learn how this software and technology works. If I was closer to my W1SCC reflector I would test my connection with my HT - but that's not possible from where I am.


Re: Need HELP getting configured on DSTAR

Tom Cichowicz
 

Just an UPDATE -- I'm up and running ..... disregard my previous post.

  The only thing I changed was the callsign server - I was using Free*Star; because the Dutch*Star kept giving me errors or wouldn't connect when I first configured the DV Node. Im HAPPY to report just switching to to Dutch*Star DPNS -- made everything HAPPY! including me.

New Pages in the AMBE Wiki

 

New documentation pages have been created in the Wiki

PI-DV3000 error message and ideas about its source

 

I administer a dstar system, W7VOI. It has worked well for a couple of years and continues to work adequately with a single anomaly.


I can access and use the W7VOI system perfectly when accessing it from a radio. However, if I try to link to the system from my pi-DV3000 computer, I get a message “Connected to . Attempting to establish link.” Despite this message, I am able to hear the audio from W7VOI but I cannot transmit to W7VOI from the computer.

The port forwarding tests at W7VOI are passed but when the gateway is up, I see with nettalk  that port 4000 is not ‘listening.’ I have no trouble linking to sites other than W7VOI so I think the issue is in my dstar setup. 

My question is has anyone seen this message and found it associated with any specific dstar issue? I would love to have help conceptualizing the problem so I might know where in the dstar system to look for a solution. Can it be hardware in the computer? a modem issue? a software error or some other problem source that I should be attending to?

Thank you in advance for any ideas.

Gary W7JZU

Re: PI-DV3000 error message and ideas about its source

 

Hi Gary,

I have just connected to W7VOI B with Buster and the connection seems to be working, though nobody is transmitting right now. (BTW, you can get a security certificate from AA4RC so you don't get the warning when connecting to your dashboard.)

It is unusual that this would happen with one system.  W7VOI does not appear to be at a fixed address?  It is currently at 159.118.95.176 -- You might want to check your /dstar/tmp/gateways.txt file and see if it has this address for W7VOI.

You also seem to be reporting into ircDDB with the add-on, but have incomplete data as it doesn't have lat/lon.  http://status.ircddb.net/qam.php?call=W7VOI

The main issue may be that W7JZU does not have a registered terminal on the US Trust (also it would be the DPLUS login in DummyRepeater).  http://query.ke5bms.com/index.php

https://nw-digital-radio.groups.io/g/ambe/wiki

On Thu, Aug 18, 2016 at 4:15 PM, Gary Payne via Groups.io <garyw7jzu@...> wrote:

I administer a dstar system, W7VOI. It has worked well for a couple of years and continues to work adequately with a single anomaly.


I can access and use the W7VOI system perfectly when accessing it from a radio. However, if I try to link to the system from my pi-DV3000 computer, I get a message “Connected to . Attempting to establish link.” Despite this message, I am able to hear the audio from W7VOI but I cannot transmit to W7VOI from the computer.

The port forwarding tests at W7VOI are passed but when the gateway is up, I see with nettalk  that port 4000 is not ‘listening.’ I have no trouble linking to sites other than W7VOI so I think the issue is in my dstar setup. 

My question is has anyone seen this message and found it associated with any specific dstar issue? I would love to have help conceptualizing the problem so I might know where in the dstar system to look for a solution. Can it be hardware in the computer? a modem issue? a software error or some other problem source that I should be attending to?

Thank you in advance for any ideas.

Gary W7JZU


--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: PI-DV3000 error message and ideas about its source

 

Thank you John, that was helpful to know that it was probably my status within the larger network and not a software glitch in the gateway. The fact that it worked for you was important information.

I did establish the terminals and we will wait until they propagate thru the system. I suspect this was indeed the problem. I had registered at another gateway but that was deleted and I had not reregistered terminals in the new gateway where I registered.

I am waiting to hear how to revise my IrcDDB entry and will make the changes when I get the link.

73, Gary




From: John Hays <john@...>
To: ambe@nw-digital-radio.groups.io
Sent: Thursday, August 18, 2016 5:43 PM
Subject: Re: [ambe] PI-DV3000 error message and ideas about its source

Hi Gary,

I have just connected to W7VOI B with Buster and the connection seems to be working, though nobody is transmitting right now. (BTW, you can get a security certificate from AA4RC so you don't get the warning when connecting to your dashboard.)

It is unusual that this would happen with one system.  W7VOI does not appear to be at a fixed address?  It is currently at 159.118.95.176 -- You might want to check your /dstar/tmp/gateways.txt file and see if it has this address for W7VOI.

You also seem to be reporting into ircDDB with the add-on, but have incomplete data as it doesn't have lat/lon.  http://status.ircddb.net/qam.php?call=W7VOI

The main issue may be that W7JZU does not have a registered terminal on the US Trust (also it would be the DPLUS login in DummyRepeater).  http://query.ke5bms.com/index.php

https://nw-digital-radio.groups.io/g/ambe/wiki

On Thu, Aug 18, 2016 at 4:15 PM, Gary Payne via Groups.io <garyw7jzu@...> wrote:
I administer a dstar system, W7VOI. It has worked well for a couple of years and continues to work adequately with a single anomaly.

I can access and use the W7VOI system perfectly when accessing it from a radio. However, if I try to link to the system from my pi-DV3000 computer, I get a message “Connected to . Attempting to establish link.” Despite this message, I am able to hear the audio from W7VOI but I cannot transmit to W7VOI from the computer.

The port forwarding tests at W7VOI are passed but when the gateway is up, I see with nettalk  that port 4000 is not ‘listening.’ I have no trouble linking to sites other than W7VOI so I think the issue is in my dstar setup. 

My question is has anyone seen this message and found it associated with any specific dstar issue? I would love to have help conceptualizing the problem so I might know where in the dstar system to look for a solution. Can it be hardware in the computer? a modem issue? a software error or some other problem source that I should be attending to?

Thank you in advance for any ideas.

Gary W7JZU


--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   



Re: PI-DV3000 error message and ideas about its source

 

Thank you John, that was helpful to know that it was probably my status within the larger network and not a software glitch in the gateway. The fact that it worked for you was important information.

I did establish the terminals and we will wait until they propagate thru the system. I suspect this was indeed the problem. I had registered at another gateway but that was deleted and I had not reregistered terminals in the new gateway where I registered.

I am waiting to hear how to revise my IrcDDB entry and will make the changes when I get the link.

73, Gary


From: Gary Payne via Groups.io <garyw7jzu@...>
To: ambe@nw-digital-radio.groups.io
Sent: Friday, August 19, 2016 2:06 PM
Subject: Re: [ambe] PI-DV3000 error message and ideas about its source

Thank you John, that was helpful to know that it was probably my status within the larger network and not a software glitch in the gateway. The fact that it worked for you was important information.

I did establish the terminals and we will wait until they propagate thru the system. I suspect this was indeed the problem. I had registered at another gateway but that was deleted and I had not reregistered terminals in the new gateway where I registered.

I am waiting to hear how to revise my IrcDDB entry and will make the changes when I get the link.

73, Gary




From: John Hays <john@...>
To: ambe@nw-digital-radio.groups.io
Sent: Thursday, August 18, 2016 5:43 PM
Subject: Re: [ambe] PI-DV3000 error message and ideas about its source

Hi Gary,

I have just connected to W7VOI B with Buster and the connection seems to be working, though nobody is transmitting right now. (BTW, you can get a security certificate from AA4RC so you don't get the warning when connecting to your dashboard.)

It is unusual that this would happen with one system.  W7VOI does not appear to be at a fixed address?  It is currently at 159.118.95.176 -- You might want to check your /dstar/tmp/gateways.txt file and see if it has this address for W7VOI.

You also seem to be reporting into ircDDB with the add-on, but have incomplete data as it doesn't have lat/lon.  http://status.ircddb.net/qam.php?call=W7VOI

The main issue may be that W7JZU does not have a registered terminal on the US Trust (also it would be the DPLUS login in DummyRepeater).  http://query.ke5bms.com/index.php

https://nw-digital-radio.groups.io/g/ambe/wiki

On Thu, Aug 18, 2016 at 4:15 PM, Gary Payne via Groups.io <garyw7jzu@...> wrote:
I administer a dstar system, W7VOI. It has worked well for a couple of years and continues to work adequately with a single anomaly.

I can access and use the W7VOI system perfectly when accessing it from a radio. However, if I try to link to the system from my pi-DV3000 computer, I get a message “Connected to . Attempting to establish link.” Despite this message, I am able to hear the audio from W7VOI but I cannot transmit to W7VOI from the computer.

The port forwarding tests at W7VOI are passed but when the gateway is up, I see with nettalk  that port 4000 is not ‘listening.’ I have no trouble linking to sites other than W7VOI so I think the issue is in my dstar setup. 

My question is has anyone seen this message and found it associated with any specific dstar issue? I would love to have help conceptualizing the problem so I might know where in the dstar system to look for a solution. Can it be hardware in the computer? a modem issue? a software error or some other problem source that I should be attending to?

Thank you in advance for any ideas.

Gary W7JZU


--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   





Re: PI-DV3000 error message and ideas about its source

 

The addition of 2 terminals for W7JZU fixed the problem

Thanks again John

Gary W7JZU



From: Gary Payne via Groups.io <garyw7jzu@...>
To: ambe@nw-digital-radio.groups.io
Sent: Friday, August 19, 2016 2:09 PM
Subject: Re: [ambe] PI-DV3000 error message and ideas about its source

Thank you John, that was helpful to know that it was probably my status within the larger network and not a software glitch in the gateway. The fact that it worked for you was important information.

I did establish the terminals and we will wait until they propagate thru the system. I suspect this was indeed the problem. I had registered at another gateway but that was deleted and I had not reregistered terminals in the new gateway where I registered.

I am waiting to hear how to revise my IrcDDB entry and will make the changes when I get the link.

73, Gary


From: Gary Payne via Groups.io <garyw7jzu@...>
To: ambe@nw-digital-radio.groups.io
Sent: Friday, August 19, 2016 2:06 PM
Subject: Re: [ambe] PI-DV3000 error message and ideas about its source

Thank you John, that was helpful to know that it was probably my status within the larger network and not a software glitch in the gateway. The fact that it worked for you was important information.

I did establish the terminals and we will wait until they propagate thru the system. I suspect this was indeed the problem. I had registered at another gateway but that was deleted and I had not reregistered terminals in the new gateway where I registered.

I am waiting to hear how to revise my IrcDDB entry and will make the changes when I get the link.

73, Gary




From: John Hays <john@...>
To: ambe@nw-digital-radio.groups.io
Sent: Thursday, August 18, 2016 5:43 PM
Subject: Re: [ambe] PI-DV3000 error message and ideas about its source

Hi Gary,

I have just connected to W7VOI B with Buster and the connection seems to be working, though nobody is transmitting right now. (BTW, you can get a security certificate from AA4RC so you don't get the warning when connecting to your dashboard.)

It is unusual that this would happen with one system.  W7VOI does not appear to be at a fixed address?  It is currently at 159.118.95.176 -- You might want to check your /dstar/tmp/gateways.txt file and see if it has this address for W7VOI.

You also seem to be reporting into ircDDB with the add-on, but have incomplete data as it doesn't have lat/lon.  http://status.ircddb.net/qam.php?call=W7VOI

The main issue may be that W7JZU does not have a registered terminal on the US Trust (also it would be the DPLUS login in DummyRepeater).  http://query.ke5bms.com/index.php

https://nw-digital-radio.groups.io/g/ambe/wiki

On Thu, Aug 18, 2016 at 4:15 PM, Gary Payne via Groups.io <garyw7jzu@...> wrote:
I administer a dstar system, W7VOI. It has worked well for a couple of years and continues to work adequately with a single anomaly.

I can access and use the W7VOI system perfectly when accessing it from a radio. However, if I try to link to the system from my pi-DV3000 computer, I get a message “Connected to . Attempting to establish link.” Despite this message, I am able to hear the audio from W7VOI but I cannot transmit to W7VOI from the computer.

The port forwarding tests at W7VOI are passed but when the gateway is up, I see with nettalk  that port 4000 is not ‘listening.’ I have no trouble linking to sites other than W7VOI so I think the issue is in my dstar setup. 

My question is has anyone seen this message and found it associated with any specific dstar issue? I would love to have help conceptualizing the problem so I might know where in the dstar system to look for a solution. Can it be hardware in the computer? a modem issue? a software error or some other problem source that I should be attending to?

Thank you in advance for any ideas.

Gary W7JZU


--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   







Re: PI-DV3000 error message and ideas about its source

 

Glad you were able to fix it.

On Fri, Aug 19, 2016 at 2:03 PM, Gary Payne via Groups.io <garyw7jzu@...> wrote:
The addition of 2 terminals for W7JZU fixed the problem

Thanks again John

Gary W7JZU


--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

thumbdv and rasberry pi 2

Jim <g7icd.jim@...>
 
Edited

Thanks To John D. Haysi have nearly got the thumbdv pi 2 working i must have just one thing wrong will put what i have done with John D. Hays 

tomorrow and see if anyone can see were i have gone wrong (I do have it working on win7 ) so must be a config error some were even done the ehco test with -------E and that came back fine

its just this cannot find user G7ICD and the connect to what ever repeater/reflector it says ignoring shows on the log will post more tomorrow as it wa past my bed time

thanks jim

Re: thumbdv and rasberry pi 2

Jim <g7icd.jim@...>
 

could you please have a look at these snap shots and see were i am going wrong i have puy them on my own site so not to fill up yours

http://g7icd.ddns.net/info/

cheers jim