Date   
Re: Serial not connected #bluedv #thumbdv

Steve Taylor
 

I had bad luck with the current version of BlueDV. It would not connect to the ThumbDV. 

I deleted the files from my computer and went the archive files and downloaded the 09548 version.

It installed and worked perfectly.


Steve N7BEF

Re: Serial not connected #bluedv #thumbdv

Andrew OBrien
 

Yes, I have tried unplugging and plugging in again.  I do get the Windows sound indicating it knows a USB device has been plugged in and Device Manager shows the USB port. .  I just ran the ThumbTest.exe utility though and after I enter the baud rate , the utility briefly displays a unhandled exception and the Thumbtest aborts.  I tried both baud rates common to the ThumbDV 
Andy K3UK

On Tue, Aug 13, 2019 at 9:16 AM Willie Williams <frewil16@...> wrote:
Have you tried to unplug thumb DV  and plug it in again?

KD4JBL

On Tue, Aug 13, 2019 at 12:06 AM Andrew OBrien <k3ukandy@...> wrote:
I have not used my ThumbDV in a while.  Today I plugged in in and installed the latest version of BlueDV.  I set the baud rate in the set-up area tp 46080 and entered my comm port number in the two usual areas where we specify the desired comm port.  The comm port I chose matches the number shown in my device manger. I have the top box ticked under AMBE for ThumbDV. Despite all this when I then click on SERIAL nothing happens , the firmware is not detected.  I have tried it on a Windows 10PC and a Windows 7 PC.

Andy K3UK 

Re: Serial not connected #bluedv #thumbdv

Willie Williams
 

Have you tried to unplug thumb DV  and plug it in again?

KD4JBL

On Tue, Aug 13, 2019 at 12:06 AM Andrew OBrien <k3ukandy@...> wrote:
I have not used my ThumbDV in a while.  Today I plugged in in and installed the latest version of BlueDV.  I set the baud rate in the set-up area tp 46080 and entered my comm port number in the two usual areas where we specify the desired comm port.  The comm port I chose matches the number shown in my device manger. I have the top box ticked under AMBE for ThumbDV. Despite all this when I then click on SERIAL nothing happens , the firmware is not detected.  I have tried it on a Windows 10PC and a Windows 7 PC.

Andy K3UK 

Re: Serial not connected #bluedv #thumbdv

Gwen Patton
 

I backed off from the most recent version to the previous version because there were some annoying bugs. I think the most recent version (9551) has some issues that David hasn't had time to fix. I'd try going to the archive folder and getting the 9550 version. I've been running that for months now and it works fine. I used it last night and it was fine, and my setup is a little more complex, running on a Raspberry Pi through a powered hub. I keep a PuTTY terminal open to it with Tmux, a telnet cluster on the top pane and the bottom pane running AMBEServer. It's a very lightweight setup, with a dynamic DNS punched through the firewall so I can access it from anywhere.


On Tue, Aug 13, 2019 at 12:06 AM Andrew OBrien <k3ukandy@...> wrote:
I have not used my ThumbDV in a while.  Today I plugged in in and installed the latest version of BlueDV.  I set the baud rate in the set-up area tp 46080 and entered my comm port number in the two usual areas where we specify the desired comm port.  The comm port I chose matches the number shown in my device manger. I have the top box ticked under AMBE for ThumbDV. Despite all this when I then click on SERIAL nothing happens , the firmware is not detected.  I have tried it on a Windows 10PC and a Windows 7 PC.

Andy K3UK 



--

-+-+-+-+-
Jenny Everywhere's Infinite: Quark Time
http://quarktime.net

Re: ThumbDV and WinDV Help

 

I'm not sure what you mean by "did not connect at all ..."?

Does your ThumbDV™ pass the ThumbTest in
https://nw-digital-radio.groups.io/g/ambe/files

https://www.youtube.com/watch?v=291k3VxJCv0

On Mon, Aug 12, 2019 at 5:20 PM Steve Taylor via Groups.Io
<sltay456=yahoo.com@groups.io> wrote:

I tried BlueDV and it did not connect at all to my PC.

Steve
N7BEF

On Aug 12, 2019, at 3:32 PM, John D Hays - K7VE <@john_hays> wrote:

Hi Steve,

WinDV is getting pretty long in the tooth and Fred hasn't released anything new in years. I would suggest trying BlueDV instead.

On Mon, Aug 12, 2019 at 3:26 PM Steve Taylor via Groups.Io <sltay456=yahoo.com@groups.io> wrote:

I have tried to setup my ThumbDV and WinDV to work on my WIN10 PC.

WinDV shows that it connects but I get no audio.

Under the RF Device part of the WinDV display there is the message "Sound card unable to open 1 as input". I confirmed that the mic and speakers were selected correctly for my PC.

Any help of ideas would be a big help.

THX
Steve
N7BEF


--
John D. Hays
Kingston, WA
K7VE





--
John D. Hays
Kingston, WA
K7VE

Serial not connected #bluedv #thumbdv

Andrew OBrien
 

I have not used my ThumbDV in a while.  Today I plugged in in and installed the latest version of BlueDV.  I set the baud rate in the set-up area tp 46080 and entered my comm port number in the two usual areas where we specify the desired comm port.  The comm port I chose matches the number shown in my device manger. I have the top box ticked under AMBE for ThumbDV. Despite all this when I then click on SERIAL nothing happens , the firmware is not detected.  I have tried it on a Windows 10PC and a Windows 7 PC.

Andy K3UK 

Re: ThumbDV and WinDV Help

VE3MIC
 

Hi Steve,

Can you verify that your ThumbDV is being recognized by Windows as a USB device?

Here is a video that N5ZNO from AmateurLogic.TV did some months ago about getting BlueDV installed & setup on Windows 10>
https://youtu.be/R48t3S9rNN8?t=938

73 de Mike

Re: ThumbDV and WinDV Help

Steve Taylor
 

I tried BlueDV and it did not connect at all to my PC.

Steve
N7BEF

On Aug 12, 2019, at 3:32 PM, John D Hays - K7VE <john@...> wrote:

Hi Steve,

WinDV is getting pretty long in the tooth and Fred hasn't released anything new in years.  I would suggest trying BlueDV instead.

On Mon, Aug 12, 2019 at 3:26 PM Steve Taylor via Groups.Io <sltay456=yahoo.com@groups.io> wrote:
I have tried to setup my ThumbDV and WinDV to work on my WIN10 PC.

WinDV shows that it connects but I get no audio. 

Under the RF Device part of the WinDV display there is the message "Sound card unable to open 1 as input". I confirmed that the mic and speakers were selected correctly for my PC. 

Any help of ideas would be a big help.

THX
Steve
N7BEF



--
John D. Hays
Kingston, WA
K7VE

 

Re: ThumbDV and WinDV Help

 

Hi Steve,

WinDV is getting pretty long in the tooth and Fred hasn't released anything new in years.  I would suggest trying BlueDV instead.

On Mon, Aug 12, 2019 at 3:26 PM Steve Taylor via Groups.Io <sltay456=yahoo.com@groups.io> wrote:
I have tried to setup my ThumbDV and WinDV to work on my WIN10 PC.

WinDV shows that it connects but I get no audio. 

Under the RF Device part of the WinDV display there is the message "Sound card unable to open 1 as input". I confirmed that the mic and speakers were selected correctly for my PC. 

Any help of ideas would be a big help.

THX
Steve
N7BEF



--
John D. Hays
Kingston, WA
K7VE

 

ThumbDV and WinDV Help

Steve Taylor
 

I have tried to setup my ThumbDV and WinDV to work on my WIN10 PC.

WinDV shows that it connects but I get no audio. 

Under the RF Device part of the WinDV display there is the message "Sound card unable to open 1 as input". I confirmed that the mic and speakers were selected correctly for my PC. 

Any help of ideas would be a big help.

THX
Steve
N7BEF

Re: AmateurLogic.tv segment

Kenneth R Fowler KD4IIW
 

Yes I was confused about that also.  I just got back into setting up my AMBE NWDR stick and it works great but was unable to turn on Fusion.  I was just confused. 

Kenneth 
KD4IIW

Re: [nw-digital-radio] 3D drawings?

 

Hello Han,


Are you on Windows, MacOS, or Linux?  

Has the ThumbDV been operational and then recently quit?

Does the LED flash when you test it?

On Wed, Jul 31, 2019 at 9:21 AM kwangsoo han <kshan315@...> wrote:
Hi, Dear;

I'm Han in Seoul, Korea.

I bought the Thumdv as DV3000 about one year ago.

Unfortunately, I failed the test with your recommanded test software.

I'd like to test mine is ok or not.

What can I do for that.

Pls inform to me in detail.

Rds, kshan
 
--------------- Original message -------------
From : "Bryan Hoyer"<bhhoyer@...>
To : <main@nw-digital-radio.groups.io>
CC :
Date : Thu, 1 Aug 2019 1:10:54 +0900 (KST), Wed, 31 Jul 2019 09:10:48 -0700
Subject : Re: [nw-digital-radio] 3D drawings?

Dale,

We’d be happy to give permission.

Contact me at sales@nwdigitalradio and we’ll work out the details.

Thanks,
Bryan K7UDR








--


John D. Hays
Director

  

a new program, qdv!

 

I have created a new digital voice application called qdv, for "Quadnet Digital Voice". If you are familiar with BlueDV, qdv is like that, but unlike BlueDV, qdv also does routing, and it's open-source! The source code for qdv is on my github at https://github.com/n7tae/DigitalVoice. It is for Linux and is a graphical program that uses a Nortwest Digital Radio ThumbDV(tm) to encode/decode between AMBE and voice data. qdv is (at least so far) a D-Star module that can route or link. Besides a Linux computer and a ThumbDV, you need a USB headset (preferably with a built-in microphone). qdv will automatically choose the default input and output audio device so you just need to plug in you headset and your ThumbDV and you're ready to go.

For all my contacts so far, I have gotten excellent audio reports with qdv and I am using a very inexpensive headset. As something like an "alpha" release (since I am the only one who has used it so far) qdv is very early in its development. There are several new features I am planning and haven't yet coded.

Please don't respond to this topic. If you want to talk about qdv, I have set up a new group at qdv@groups.io.

Re: Log for BlueDV for Windows? #bluedv

James Moen
 

Jack - Bingo.  REF045 is running a very old version of DPlus reflector software -- DREFD version 1.31.  The ham I an helping had registered his callsign on the G3 gateway that I administer.  My guess is that old version of reflector software is not able to authenticate callsigns registered on G3 gateways.  If we had BlueDV-Windows log, we would probably see that when it tries to link this callsign to this old reflector, their lookup fails and a return code of "OKRO" meaning Read Only - you can listen but not talk over that reflector.  What we want is a return code of OKRW.

The correct fix is to convince the REF045 Admins to update their reflector software to the latest version, but failing that, the user I'm helping can degregister at my gateway and register on a G2 gateway.  

There is nothing wrong with BlueDV for Windows nor with the user's setup and configuration.  The problem is entirely with the old version of reflector software.

Thanks very, very much for getting me headed in the right direction.

   Jim - K6JM

Re: Log for BlueDV for Windows? #bluedv

Jack Spitznagel
 

 

This sort of “lockout” was happening with several US Trust Reflectors that had not updated their gateway software about a month ago or so. Look to see what version they are running?

Jack – KD4IZ

 

From: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io> On Behalf Of James Moen
Sent: Tuesday, July 9, 2019 18:23
To: ambe@nw-digital-radio.groups.io
Subject: [ambe] Log for BlueDV for Windows? #bluedv

 

I am helping a ham who is using a ThumbDV with BlueDV for Windows.  It is generally working using DStar linking to both REF and XRF reflectors.  But one reflector -- REF045 -- does not allow his callsign to link and talk over the reflector.  Other callsigns, such as mine, work fine, but his callsign is only allowed to listen, not talk.

Normally this problem is caused by a registration problem, but I have checked and his callsign is registered properly with both a space and an A terminal.  His BlueDV Setup looks perfect and he can successfully use other REF reflectors, just not REF045.

I figure either the reflector admin is blocking his callsign, or more likely, that reflector is not getting the latest registration database updates.  When using other software, my next step would be to turn on logging and see what return code is given when he attempts to link to REF045C.  Does anyone know if BlueDV for Windows supports logging, how to turn it on and where the log file is written?


--
J Spitznagel
Science River LLC
KD4IZ

Re: Log for BlueDV for Windows? #bluedv

 

Yes. David is the right person for support.

On Tue, Jul 9, 2019 at 4:20 PM Alec-N1AJW <alec.wasserman@...> wrote:
just contact the Developer David Pa7LIM.  if you google his call.  you will see all his contact info.  He will be able to figure out what's wrong at least.   

Alec
N1AJW



--
John D. Hays
Kingston, WA
K7VE

 

Re: Log for BlueDV for Windows? #bluedv

Patrick Perdue
 

If there is a proper log for BlueDV, I can't find it.

I was trying to diagnose a similar situation with my own callsign the other day, which I suspect was never actually registered with DSTAR. I went through every option and directory I could find, but was never able to locate a log other than QSO.


On 7/9/2019 6:23 PM, James Moen wrote:

I am helping a ham who is using a ThumbDV with BlueDV for Windows.  It is generally working using DStar linking to both REF and XRF reflectors.  But one reflector -- REF045 -- does not allow his callsign to link and talk over the reflector.  Other callsigns, such as mine, work fine, but his callsign is only allowed to listen, not talk.

Normally this problem is caused by a registration problem, but I have checked and his callsign is registered properly with both a space and an A terminal.  His BlueDV Setup looks perfect and he can successfully use other REF reflectors, just not REF045.

I figure either the reflector admin is blocking his callsign, or more likely, that reflector is not getting the latest registration database updates.  When using other software, my next step would be to turn on logging and see what return code is given when he attempts to link to REF045C.  Does anyone know if BlueDV for Windows supports logging, how to turn it on and where the log file is written?

Re: Log for BlueDV for Windows? #bluedv

Alec-N1AJW
 

just contact the Developer David Pa7LIM.  if you google his call.  you will see all his contact info.  He will be able to figure out what's wrong at least.   

Alec
N1AJW

Log for BlueDV for Windows? #bluedv

James Moen
 

I am helping a ham who is using a ThumbDV with BlueDV for Windows.  It is generally working using DStar linking to both REF and XRF reflectors.  But one reflector -- REF045 -- does not allow his callsign to link and talk over the reflector.  Other callsigns, such as mine, work fine, but his callsign is only allowed to listen, not talk.

Normally this problem is caused by a registration problem, but I have checked and his callsign is registered properly with both a space and an A terminal.  His BlueDV Setup looks perfect and he can successfully use other REF reflectors, just not REF045.

I figure either the reflector admin is blocking his callsign, or more likely, that reflector is not getting the latest registration database updates.  When using other software, my next step would be to turn on logging and see what return code is given when he attempts to link to REF045C.  Does anyone know if BlueDV for Windows supports logging, how to turn it on and where the log file is written?

Re: Cannot communicate on 460800 baud thumbDV with FTDXX2 library #thumbdv

Annaliese McDermond
 

The observations he sees are the same I see when running the faster baud rate. I get a bunch of PKT_RDY packets with a few speech packets sprinkled in. The thread mentions something about the TI TPS380x-Q1 Voltage Detectors cause this hardware reset of the AMBE chip. Has anyone else run into this issue?
This indicates a hardware issue.  If there were a hardware issue, we'd have tons of folks complaining about bad hardware.  We have been selling the ThumbDV at 460800 for years now with no issues on Mac, Windows and Linux.