1. DVSwitch | Main
  2. Topics

Request for information

Steve N4IRS
 

We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 
David KE6UPI
 

Hello Steve, I'm running an old Dell Optiplex 960 i3 (3rd Gen) 4Gb ram. 

Should the latency_timer be set to 16 or 1?

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 6:14 AM, Steve N4IRS <szingman@...> wrote:
We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 


David
 

timer is 1
Pi 3 NWdigital dongle raspbian

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:
We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 


Steve N4IRS
 

Was it set that way or did you change it after we emailed yesterday? Please check it after a fresh boot.

Thanks, Steve

On 1/17/2018 9:24 AM, David wrote:

timer is 1
Pi 3 NWdigital dongle raspbian

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:
We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 


Steven Blackford
 

Steve,

   I have a few setups here.  First is an ODroid-C1 which runs Ubuntu and is a full time DMR<->D-Star bridge the settings were default to 16.  The second system is a PI3 running Arch Linux.  It’s defaults were 1.

 

X64 Thinkpad running Debian Stretch, default is 16.

 

While assisting setting up an ASL<->DMR<->D-Star system last night on 2 PI3’s.  I checked those as well.  Those were both running Arch Linux and they were both set to a default of 1.

 

Hope that helps. 

 

Steve, K4SQI

 

 

From: Steve N4IRS
Sent: Wednesday, January 17, 2018 9:14 AM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] Request for information

 

We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 

 

6007AAB721E8401FA8CD908F040B91D1.png

David KE6UPI
 

After your email yesterday. I changed it to 1 from 16. It stays at 1 after reboots.

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 6:33 AM, Steve N4IRS <szingman@...> wrote:
Was it set that way or did you change it after we emailed yesterday? Please check it after a fresh boot.

Thanks, Steve

On 1/17/2018 9:24 AM, David wrote:
timer is 1
Pi 3 NWdigital dongle raspbian

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:
We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 



Steve N4IRS
 

Both interesting bits of info.
Did changing to 1 improve the audio quality?

Thanks

On 1/17/2018 9:50 AM, David KE6UPI wrote:

After your email yesterday. I changed it to 1 from 16. It stays at 1 after reboots.

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 6:33 AM, Steve N4IRS <szingman@...> wrote:
Was it set that way or did you change it after we emailed yesterday? Please check it after a fresh boot.

Thanks, Steve

On 1/17/2018 9:24 AM, David wrote:
timer is 1
Pi 3 NWdigital dongle raspbian

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:
We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 




David KE6UPI
 

No it didn't. Could I (we) have received a bad batch of DV3000u? ASL to DMR sounds great. DMR to ASL is choppy. 

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 7:09 AM, Steve N4IRS <szingman@...> wrote:
Both interesting bits of info.
Did changing to 1 improve the audio quality?

Thanks

On 1/17/2018 9:50 AM, David KE6UPI wrote:
After your email yesterday. I changed it to 1 from 16. It stays at 1 after reboots.

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 6:33 AM, Steve N4IRS <szingman@...> wrote:
Was it set that way or did you change it after we emailed yesterday? Please check it after a fresh boot.

Thanks, Steve

On 1/17/2018 9:24 AM, David wrote:
timer is 1
Pi 3 NWdigital dongle raspbian

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:
We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 





G7RPG - Peter Kendall
 

Steve,

My asl box running Analog_Bridge is Debain 8.9 VM on ESX 6.5 (i5 3570K) the value of latency_timer is 1


[    5.343999] usbcore: registered new interface driver ftdi_sio
[    5.344007] usbserial: USB Serial support registered for FTDI USB Serial Device
[    5.344032] ftdi_sio 1-2.2:1.0: FTDI USB Serial Device converter detected
[    5.344049] usb 1-2.2: Detected FT-X
[    5.344050] usb 1-2.2: Number of endpoints 2
[    5.344052] usb 1-2.2: Endpoint 1 MaxPacketSize 64
[    5.344053] usb 1-2.2: Endpoint 2 MaxPacketSize 64
[    5.344054] usb 1-2.2: Setting MaxPacketSize 64



Peter


On 17/01/18 14:14, Steve N4IRS wrote:

We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 

Steven Blackford
 

David,

   Have you tried swapping the ThumbDV’s around?  That’s a quck easy test to see how they work.

 

Steve

 

From: David KE6UPI
Sent: Wednesday, January 17, 2018 10:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Request for information

 

No it didn't. Could I (we) have received a bad batch of DV3000u? ASL to DMR sounds great. DMR to ASL is choppy. 

 

David


 

 

--

Thanks, David

 

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."

Thomas Jefferson

 

On Wed, Jan 17, 2018 at 7:09 AM, Steve N4IRS <szingman@...> wrote:

Both interesting bits of info.
Did changing to 1 improve the audio quality?

Thanks

On 1/17/2018 9:50 AM, David KE6UPI wrote:

After your email yesterday. I changed it to 1 from 16. It stays at 1 after reboots.

 

David


 

 

--

Thanks, David

 

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."

Thomas Jefferson

 

On Wed, Jan 17, 2018 at 6:33 AM, Steve N4IRS <szingman@...> wrote:

Was it set that way or did you change it after we emailed yesterday? Please check it after a fresh boot.

Thanks, Steve

On 1/17/2018 9:24 AM, David wrote:

timer is 1

Pi 3 NWdigital dongle raspbian

 

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:

We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 

 

 

 

 

 

 

CF403CAE817549F1AF89813E65C6BB30.png

Steve N4IRS
 

It's ASL to DMR. Only 1 DV3000

On 1/17/2018 10:14 AM, Steven Blackford wrote:

David,

   Have you tried swapping the ThumbDV’s around?  That’s a quck easy test to see how they work.

 

Steve

 

From: David KE6UPI
Sent: Wednesday, January 17, 2018 10:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Request for information

 

No it didn't. Could I (we) have received a bad batch of DV3000u? ASL to DMR sounds great. DMR to ASL is choppy. 

 

David


 

 

--

Thanks, David

 

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."

Thomas Jefferson

 

On Wed, Jan 17, 2018 at 7:09 AM, Steve N4IRS <szingman@...> wrote:

Both interesting bits of info.
Did changing to 1 improve the audio quality?

Thanks

On 1/17/2018 9:50 AM, David KE6UPI wrote:

After your email yesterday. I changed it to 1 from 16. It stays at 1 after reboots.

 

David


 

 

--

Thanks, David

 

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."

Thomas Jefferson

 

On Wed, Jan 17, 2018 at 6:33 AM, Steve N4IRS <szingman@...> wrote:

Was it set that way or did you change it after we emailed yesterday? Please check it after a fresh boot.

Thanks, Steve

On 1/17/2018 9:24 AM, David wrote:

timer is 1

Pi 3 NWdigital dongle raspbian

 

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:

We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 

 

 

 

 

 

 
Steven Blackford
 

Yeah…. I thought of that when I hit send.  Disregard.  I’m used to having an extra to experiment with. 😊

 

Steve

 

From: Steve N4IRS
Sent: Wednesday, January 17, 2018 10:15 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Request for information

 

It's ASL to DMR. Only 1 DV3000

On 1/17/2018 10:14 AM, Steven Blackford wrote:

David,

   Have you tried swapping the ThumbDV’s around?  That’s a quck easy test to see how they work.

 

Steve

 

From: David KE6UPI
Sent: Wednesday, January 17, 2018 10:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Request for information

 

No it didn't. Could I (we) have received a bad batch of DV3000u? ASL to DMR sounds great. DMR to ASL is choppy. 

 

David


 

 

--

Thanks, David

 

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."

Thomas Jefferson

 

On Wed, Jan 17, 2018 at 7:09 AM, Steve N4IRS <szingman@...> wrote:

Both interesting bits of info.
Did changing to 1 improve the audio quality?

Thanks

On 1/17/2018 9:50 AM, David KE6UPI wrote:

After your email yesterday. I changed it to 1 from 16. It stays at 1 after reboots.

 

David


 

 

--

Thanks, David

 

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."

Thomas Jefferson

 

On Wed, Jan 17, 2018 at 6:33 AM, Steve N4IRS <szingman@...> wrote:

Was it set that way or did you change it after we emailed yesterday? Please check it after a fresh boot.

Thanks, Steve

On 1/17/2018 9:24 AM, David wrote:

timer is 1

Pi 3 NWdigital dongle raspbian

 

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:

We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 

 

 

 

 

 

 

 

 

DAF3E09EDC554E52A11C1707610BF8DE.png

Steve N4IRS
 

I have 3 ThumbDVs. Two are in a semi-permanent DMR <---> D-Star bridge I put up for the local group. The other is in a machine Mike and I are testing on. That just leaves a PiDV.

On 1/17/2018 10:18 AM, Steven Blackford wrote:

Yeah…. I thought of that when I hit send.  Disregard.  I’m used to having an extra to experiment with. 😊

 

Steve

 

From: Steve N4IRS
Sent: Wednesday, January 17, 2018 10:15 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Request for information

 

It's ASL to DMR. Only 1 DV3000

On 1/17/2018 10:14 AM, Steven Blackford wrote:

David,

   Have you tried swapping the ThumbDV’s around?  That’s a quck easy test to see how they work.

 

Steve

 

From: David KE6UPI
Sent: Wednesday, January 17, 2018 10:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Request for information

 

No it didn't. Could I (we) have received a bad batch of DV3000u? ASL to DMR sounds great. DMR to ASL is choppy. 

 

David


 

 

--

Thanks, David

 

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."

Thomas Jefferson

 

On Wed, Jan 17, 2018 at 7:09 AM, Steve N4IRS <szingman@...> wrote:

Both interesting bits of info.
Did changing to 1 improve the audio quality?

Thanks

On 1/17/2018 9:50 AM, David KE6UPI wrote:

After your email yesterday. I changed it to 1 from 16. It stays at 1 after reboots.

 

David


 

 

--

Thanks, David

 

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."

Thomas Jefferson

 

On Wed, Jan 17, 2018 at 6:33 AM, Steve N4IRS <szingman@...> wrote:

Was it set that way or did you change it after we emailed yesterday? Please check it after a fresh boot.

Thanks, Steve

On 1/17/2018 9:24 AM, David wrote:

timer is 1

Pi 3 NWdigital dongle raspbian

 

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:

We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 

 

 

 

 

 

 

 

 
Steve N4IRS
 

No, I do not think so. Did you run the confidence test (AMBEtest4.py) with Analog_bridge stopped?

On 1/17/2018 10:11 AM, David KE6UPI wrote:

No it didn't. Could I (we) have received a bad batch of DV3000u? ASL to DMR sounds great. DMR to ASL is choppy. 

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 7:09 AM, Steve N4IRS <szingman@...> wrote:
Both interesting bits of info.
Did changing to 1 improve the audio quality?

Thanks

On 1/17/2018 9:50 AM, David KE6UPI wrote:
After your email yesterday. I changed it to 1 from 16. It stays at 1 after reboots.

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 6:33 AM, Steve N4IRS <szingman@...> wrote:
Was it set that way or did you change it after we emailed yesterday? Please check it after a fresh boot.

Thanks, Steve

On 1/17/2018 9:24 AM, David wrote:
timer is 1
Pi 3 NWdigital dongle raspbian

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:
We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 






Richard (Joseph) VE2DJE
 

Hardware  is  Dell OptiPlex 380 - SFF - Core 2 Duo E7500 2.93 GHz

Running  Debian 8

 cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer     result  =   1

DV3000U running a DMR to AllStarLink gateway


Richard VE2DJE




Le 17/01/2018 à 09:24, David a écrit :

timer is 1
Pi 3 NWdigital dongle raspbian

On Wed, Jan 17, 2018 at 8:14 AM, Steve N4IRS <szingman@...> wrote:
We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 


Virus-free. www.avg.com

Veijo Arponen OH4VA
 

Linux dmr 4.13.0-19-generic #22-Ubuntu SMP Mon Dec 4 11:57:38 UTC 2017 i686 i686 i686 GNU/Linux

Distributor ID: Ubuntu
Description: Ubuntu 17.10
Release: 17.10
Codename: artful


Currently I'm not running any DMR-application. I have plans to run
SharkRF SPK-server which serves openSPOTs for the announcements.

/sys/bus/usb-serial/devices/ttyUSB0/latency_timer
16

73 de Veijo OH3NFC
Dylan KI7SBI
 

On Wed, Jan 17, 2018 at 6:14 AM, Steve N4IRS <szingman@...> wrote:
but for now, All I want to know is what hardware / software you are running and the value.


Dell PowerEdge 400SC with DV3000usb
$ cat /etc/issue
Ubuntu 14.04.5 LTS \n \l
$ uname -a
Linux ast3 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:56:31 UTC 2017 i686 i686 i686 GNU/Linux
$ cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
1

KI7SBI
David KE6UPI
 

Here is my AMBEtest4 results.

root@asl2060:/opt/Analog_Bridge/DV3000# python AMBEtest4.py -n -s /dev/ttyUSB0
Setting serial port
Serial port parameters:
Port name:      /dev/ttyUSB0
Baudrate:       460800
Byte size:      8
Parity:         N
Stop bits:      1
Xon Xoff:       False
RTS/CTS:        False
DST/DTR:        False
*********************
Silent testing mode.....
Error count =  0


David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 12:35 PM, Dylan KI7SBI <dylan@...> wrote:
On Wed, Jan 17, 2018 at 6:14 AM, Steve N4IRS <szingman@...> wrote:
but for now, All I want to know is what hardware / software you are running and the value.


Dell PowerEdge 400SC with DV3000usb
$ cat /etc/issue
Ubuntu 14.04.5 LTS \n \l
$ uname -a
Linux ast3 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:56:31 UTC 2017 i686 i686 i686 GNU/Linux
$ cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
1

KI7SBI
David KE6UPI
 

So I moved the DV3000u to the front usb port. Now its sounds much better. 

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 3:15 PM, David KE6UPI <shawpbx@...> wrote:
Here is my AMBEtest4 results.

root@asl2060:/opt/Analog_Bridge/DV3000# python AMBEtest4.py -n -s /dev/ttyUSB0
Setting serial port
Serial port parameters:
Port name:      /dev/ttyUSB0
Baudrate:       460800
Byte size:      8
Parity:         N
Stop bits:      1
Xon Xoff:       False
RTS/CTS:        False
DST/DTR:        False
*********************
Silent testing mode.....
Error count =  0


David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Wed, Jan 17, 2018 at 12:35 PM, Dylan KI7SBI <dylan@...> wrote:
On Wed, Jan 17, 2018 at 6:14 AM, Steve N4IRS <szingman@...> wrote:
but for now, All I want to know is what hardware / software you are running and the value.


Dell PowerEdge 400SC with DV3000usb
$ cat /etc/issue
Ubuntu 14.04.5 LTS \n \l
$ uname -a
Linux ast3 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:56:31 UTC 2017 i686 i686 i686 GNU/Linux
$ cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
1

KI7SBI
Ian Tulley
 

Hi Steve, I’m running an i3 mini ITX Board Debian 9, result=16 for me

Regards
Ian (VK2HK)

Typo's, autocorrect or spelling mistakes courtesy of both myself and my iPhone

On 18 Jan 2018, at 01:14, Steve N4IRS <szingman@...> wrote:

We have been working on the next revision of Analog_Bridge. Along with adding features and refining settings, we are trying to squash bugs. While testing the NWDigital DV300u (ThumbDV) we encountered a problem with data transfer . Some of the packets were not being processed in the required window. The NWD DV3000u uses a FTDI chip to communicate with the host computer. Under Linux, or at least Debian the driver is the FTDI serial. On the machine under test, a older Dell 2950 with more then enough horsepower and no history of issues with USB, we were not getting data in a timely manner. There is a value that can be adjusted to resolve this. /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. The default looks to be 16. The 2950 was set at 16. So far so good. Well, I have a machine running a full time DMR <---> D-Star bridge using two of the DV3000u. When I checked the latency_timer, it was set to 1. Huh? I know I did not change it.

I am asking everybody that is using a DV3000 and a FTDI chip to test with the device plugged in. As root: cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer. Please report the result here. We have multiple ways to set this to what we want, but for now, All I want to know is what hardware / software you are running and the value.

Thanks, Steve

 

1 - 20 of 24