Date   

Re: Timercontrol

Jeremy McDermond <mcdermj@...>
 


On Oct 13, 2016, at 3:16 AM, John M Wysocki ZL2TWS <zl2tws@...> wrote:

Jeremy

I located the timercontrol file in /etc/logrotate.d and copied it to /etc/opendv.

That’s not the timercontrol configuration file.  That’s the log rotation file that tells logrotate how often to rotate the log files for timercontrol so that your /var partition doesn’t fill up.  You will have to create a configuration file to make it run correctly.

The same error message is sent.

pi@compass:~ $ sudo timercontrol -confdir /etc/opendv

Fatal Error: Assertion failed on line 38 in file TimerControl/TimerControlRemoteControlHandler.cpp and function CTimerControlRemoteControlHandler: !address.IsEmpty() 

pi@compass:~ $ 

I will wait until there is a fix.

Thank you, 73, John ZL2TWS


Jeremy McDermond


Re: Loosing Last 1/2 second of transmission

John Blaisdell
 

Rich,

Thanks for the help. I haven't really looked into audio levels settings since we only have the one complaint. But, now I will. Again thanks.

73,

John W4CJB 



Sent from my Verizon 4G LTE smartphone


-------- Original message --------
From: Rich KR4PI <rich.schnieders@...>
Date: 10/13/16 8:59 AM (GMT-06:00)
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Loosing Last 1/2 second of transmission

John, the ID-5100 is the pickiest on audio levels coming out of the repeater. I have found that with my ID-5100 I have to go into alsamixer and adjust the levels while listening on the ID-5100. I have to set PCM at 2db gain, ADC at -2 db gain and LO Driver at 0 db gain. I have an IC-7100 which is very tolerant of just about any setting, my ID51a+ is pretty tolerant but the ID-5100 requires these settings. I suggest setting them while monitoring on the 5100. BTW this is well documented on many different kinds of hotspots with the ID-5100, it is not a problem with the UDRC.

As far as our losing the last portion of every transmission I replaced the raspberry pi, loaded brand new image on the pi along with increasing the TX Delay and TX tail and have successfully eliminated the loss at the end of a transmission. We also did a factory reset of the DR-1X. We have discovered a couple of times the DR-1X would not respond properly to the UDRC and the only solution was a factory reset of the DR-1X which is pretty quick. The repeater is working great now.

Thanks for all the help.

Rich, KR4PI


Re: SD Surprise

VE3MIC
 

If your running Linux, DD is the way to go
de Mike


On Thursday, October 13, 2016 7:31 AM, John McDonough <wb8rcr@...> wrote:


On Wed, 2016-10-12 at 17:45 -0700, Richard - VE7CVS wrote:
> If you shrink the filesystem before you save it, you can restore it
> and 
> expand it to the size of the destination card.
>
> I use tools like dd, resize2fs and fdisk to manipulate filesystems.

I use dd to make the backups, and certainly I can muck with the
filesystem sizes, but it is just so convenient to just tell dd to copy
this file to this device with no messing around.  I suppose if I think
about it, a little bash pixie dust could automate the process tho.

> These commands are worth learning if you want to understand how 
> filesystems and storage work.
>
> But then, I rarely do things the easy way, and I have a compulsion
> to 
> know how things work. :-)

hmmm ... sounds familiar ;)
>
> - Richard, VE7CVS
>
>




Re: Pi3 PSU Voltage Critical

 

The UDRC has a 12vdc input which will power both the UDRC and Pi with good voltage and current.


On Oct 13, 2016 02:54, "John M Wysocki ZL2TWS" <zl2tws@...> wrote:

Hello NW Digital team.

Today I found what might be the reason for the UDRC cutout on RX.

I am still testing but have found a real issue with voltages lower than 5.1VDC when measured on the GPIO pins 4 & 6.

On the UDRC compass image I have installed DummyRepeater using the DV3000.

This was done when the UDRC board was removed.

Two PSU's are available.

1) 5.0VDC @ 2.0Amps.

2) 5.1VDC @2.5Amps.

DummyRepeater fails to operate correctly if the PSU at 1) is used.

DummyRepeater works perfectly when the PSU at 2) is used.

Operating voltage of 5.15VDC between GPIO 4 & 6 is the best or possibly higher.

Please carry out testing on the UDRC and Pi3 to determine if the wrong voltage PSU is used can cause the RX drop outs I was experiencing.

If 4.9V is used for testing it might show the problem.

I will continue to test the UDRC over the next couple of days to prove this theory with my own variable PSU.

Amazed that 0.15V could cause the Pi3 to be problematic. I have been told that some of the Plug Pack PSU's can drop to a lower voltage or have poor regulation.

I will investigate a 13.8VDC drop down regulated 5.2VDC supply as an option.

The difference in 2.0A and 2.5A I cannot see to be a problem since the Pi3 running current is lower than 2A. On-board SMPS problem like the Pi2?

Looks like Pi3 VDC is critical and must be higher than 5.1V definitely for DummyRepeater and possibly UDRC.

Those wanting to use the Compass image with DV3000, USB headset and DummyRepeater must use >5.1VDC.

I tried three different 5.0V 2.0A PSU's and DummyRepeater failed to work correctly with all three but 100% as soon as the >5.1V 2.5A was used.

73, John ZL2TWS


Re: Loosing Last 1/2 second of transmission

 

John, the ID-5100 is the pickiest on audio levels coming out of the repeater. I have found that with my ID-5100 I have to go into alsamixer and adjust the levels while listening on the ID-5100. I have to set PCM at 2db gain, ADC at -2 db gain and LO Driver at 0 db gain. I have an IC-7100 which is very tolerant of just about any setting, my ID51a+ is pretty tolerant but the ID-5100 requires these settings. I suggest setting them while monitoring on the 5100. BTW this is well documented on many different kinds of hotspots with the ID-5100, it is not a problem with the UDRC.

As far as our losing the last portion of every transmission I replaced the raspberry pi, loaded brand new image on the pi along with increasing the TX Delay and TX tail and have successfully eliminated the loss at the end of a transmission. We also did a factory reset of the DR-1X. We have discovered a couple of times the DR-1X would not respond properly to the UDRC and the only solution was a factory reset of the DR-1X which is pretty quick. The repeater is working great now.

Thanks for all the help.

Rich, KR4PI


Re: Pi3 PSU Voltage Critical

Robert Sears
 

Be wary of cheap micro USB cables, when the Pi2 came out power supplies cables I had that powered the Pi-B just fine would give the "rainbow square" in the upper right hand corner. That is a n indication of low power supply voltage. It turned out to be the voltage drop in the usb cables. Even a cheap 3 foot cable had .4 volt drop when powering the Pi2. Now I buy cables from Monoprice that are 20 gauge wire.

But the real answer is, the UDRC has a voltage regulator on it that can can take a 12 volt input and power the UDRC/Pi from that.

If you order a case from Budd Churchwood WB7FHC it has a "standard" DC power jack to use this feature.

Robert/KF7VOP

On 10/13/2016 2:54 AM, John M Wysocki ZL2TWS wrote:

Hello NW Digital team.

Today I found what might be the reason for the UDRC cutout on RX.

I am still testing but have found a real issue with voltages lower than 5.1VDC when measured on the GPIO pins 4 & 6.

On the UDRC compass image I have installed DummyRepeater using the DV3000.

This was done when the UDRC board was removed.

Two PSU's are available.

1) 5.0VDC @ 2.0Amps.

2) 5.1VDC @2.5Amps.

DummyRepeater fails to operate correctly if the PSU at 1) is used.

DummyRepeater works perfectly when the PSU at 2) is used.

Operating voltage of 5.15VDC between GPIO 4 & 6 is the best or possibly higher.

Please carry out testing on the UDRC and Pi3 to determine if the wrong voltage PSU is used can cause the RX drop outs I was experiencing.

If 4.9V is used for testing it might show the problem.

I will continue to test the UDRC over the next couple of days to prove this theory with my own variable PSU.

Amazed that 0.15V could cause the Pi3 to be problematic. I have been told that some of the Plug Pack PSU's can drop to a lower voltage or have poor regulation.

I will investigate a 13.8VDC drop down regulated 5.2VDC supply as an option.

The difference in 2.0A and 2.5A I cannot see to be a problem since the Pi3 running current is lower than 2A. On-board SMPS problem like the Pi2?

Looks like Pi3 VDC is critical and must be higher than 5.1V definitely for DummyRepeater and possibly UDRC.

Those wanting to use the Compass image with DV3000, USB headset and DummyRepeater must use >5.1VDC.

I tried three different 5.0V 2.0A PSU's and DummyRepeater failed to work correctly with all three but 100% as soon as the >5.1V 2.5A was used.

73, John ZL2TWS



Re: SD Surprise

John McDonough
 

On Wed, 2016-10-12 at 17:45 -0700, Richard - VE7CVS wrote:
If you shrink the filesystem before you save it, you can restore it
and 
expand it to the size of the destination card.

I use tools like dd, resize2fs and fdisk to manipulate filesystems.
I use dd to make the backups, and certainly I can muck with the
filesystem sizes, but it is just so convenient to just tell dd to copy
this file to this device with no messing around.  I suppose if I think
about it, a little bash pixie dust could automate the process tho.

These commands are worth learning if you want to understand how 
filesystems and storage work.

But then, I rarely do things the easy way, and I have a compulsion
to 
know how things work. :-)
hmmm ... sounds familiar ;)

- Richard, VE7CVS

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links:


Re: Timercontrol

John M Wysocki ZL2TWS <zl2tws@...>
 

Jeremy

I located the timercontrol file in /etc/logrotate.d and copied it to /etc/opendv.

The same error message is sent.

pi@compass:~ $ sudo timercontrol -confdir /etc/opendv

Fatal Error: Assertion failed on line 38 in file TimerControl/TimerControlRemoteControlHandler.cpp and function CTimerControlRemoteControlHandler: !address.IsEmpty() 

pi@compass:~ $ 

I will wait until there is a fix.

Thank you, 73, John ZL2TWS


Pi3 PSU Voltage Critical

John M Wysocki ZL2TWS <zl2tws@...>
 

Hello NW Digital team.

Today I found what might be the reason for the UDRC cutout on RX.

I am still testing but have found a real issue with voltages lower than 5.1VDC when measured on the GPIO pins 4 & 6.

On the UDRC compass image I have installed DummyRepeater using the DV3000.

This was done when the UDRC board was removed.

Two PSU's are available.

1) 5.0VDC @ 2.0Amps.

2) 5.1VDC @2.5Amps.

DummyRepeater fails to operate correctly if the PSU at 1) is used.

DummyRepeater works perfectly when the PSU at 2) is used.

Operating voltage of 5.15VDC between GPIO 4 & 6 is the best or possibly higher.

Please carry out testing on the UDRC and Pi3 to determine if the wrong voltage PSU is used can cause the RX drop outs I was experiencing.

If 4.9V is used for testing it might show the problem.

I will continue to test the UDRC over the next couple of days to prove this theory with my own variable PSU.

Amazed that 0.15V could cause the Pi3 to be problematic. I have been told that some of the Plug Pack PSU's can drop to a lower voltage or have poor regulation.

I will investigate a 13.8VDC drop down regulated 5.2VDC supply as an option.

The difference in 2.0A and 2.5A I cannot see to be a problem since the Pi3 running current is lower than 2A. On-board SMPS problem like the Pi2?

Looks like Pi3 VDC is critical and must be higher than 5.1V definitely for DummyRepeater and possibly UDRC.

Those wanting to use the Compass image with DV3000, USB headset and DummyRepeater must use >5.1VDC.

I tried three different 5.0V 2.0A PSU's and DummyRepeater failed to work correctly with all three but 100% as soon as the >5.1V 2.5A was used.

73, John ZL2TWS


Re: SD Surprise

Richard - VE7CVS
 

If you shrink the filesystem before you save it, you can restore it and expand it to the size of the destination card.

I use tools like dd, resize2fs and fdisk to manipulate filesystems.

These commands are worth learning if you want to understand how filesystems and storage work.

But then, I rarely do things the easy way, and I have a compulsion to know how things work. :-)

- Richard, VE7CVS


Re: Timercontrol

Jeremy McDermond <mcdermj@...>
 


On Oct 12, 2016, at 1:11 PM, John M Wysocki ZL2TWS <zl2tws@...> wrote:

Jeremy

Yes I can confirm there is no timercontrol config file in /etc/opendv.


I used this and the same.

pi@compass:~ $ sudo timercontrol -confdir /etc/opendv

Fatal Error: Assertion failed on line 38 in file TimerControl/TimerControlRemoteControlHandler.cpp and function CTimerControlRemoteControlHandler: !address.IsEmpty() 



Right, because there’s no configuration file in there.  There’s no configuration file, and it won’t complain about that fact.  That just means that it can’t get your gateway’s IP address to control it, so it throws this assertion.

pi@compass:~ $ 

The Config files I have in /etc/opendv are:
dstarrepeater_1, ircddbgateway, starnetserver and timeserver

Should remotecontrol also be there because I cannot get the remotecontrol dashboard to function as it does on all other images I have DG9VH installed on?
Remote control is working using smart phone app by David PA7LIM but not via www-data.

I want to make Compass the same as other images for Pi2 and Pi3 that we now expect to be fully functional with G4KLX.

/etc/opendv is where the configuration should go for *everything*.  I don’t think that timer control is doing the correct thing right now.  I need an opportunity to make the code match the way it should work.  In the mean time, place your configuration file for timercontrol in /etc/opendv and use the -confdir flag.  I’ll push a new package out when I can to fix this more permanently.

Regards, John ZL2TWS

Jeremy McDermond


Re: Timercontrol

John M Wysocki ZL2TWS <zl2tws@...>
 

Jeremy

Yes I can confirm there is no timercontrol config file in /etc/opendv.

I used this and the same.

pi@compass:~ $ sudo timercontrol -confdir /etc/opendv

Fatal Error: Assertion failed on line 38 in file TimerControl/TimerControlRemoteControlHandler.cpp and function CTimerControlRemoteControlHandler: !address.IsEmpty() 

pi@compass:~ $ 

The Config files I have in /etc/opendv are:
dstarrepeater_1, ircddbgateway, starnetserver and timeserver

Should remotecontrol also be there because I cannot get the remotecontrol dashboard to function as it does on all other images I have DG9VH installed on?
Remote control is working using smart phone app by David PA7LIM but not via www-data.

I want to make Compass the same as other images for Pi2 and Pi3 that we now expect to be fully functional with G4KLX.

Regards, John ZL2TWS


Re: Loosing Last 1/2 second of transmission

John Blaisdell
 

 I'm also running DR-1 repeater with v1.10j  and the DStar repeater is on a RPi 3. I have not fiddled with the settings either. It's just local a repeater at this point, no internet/gateway. We now have several users in a 40+ mile radius. I've only had a complaint from one user with a new ID-5100. He reports that the 1st part of any received signal has no audio. The s-meter shows a signal but no audio at first. He even sent the 5100 back to HRO and had it replaced. He still has the same problem. No one else does. Several of us have successfully tested simultaneous voice and data (with drats) with success. In a couple weeks I'll start looking into adjusting settings and into setting up the internet/gateway.

73,
 
John Blaisdell - W4CJB
Walton Co., FL ARES EC 
850-307-7458


On Wednesday, October 12, 2016 12:35 PM, Michael Champion Sr <mikec@...> wrote:


I don’t have the issue at all on mine running 1.10J firmware so I have not fiddled with the setting.  It’s not going to hurt anything to experiment to see if it helps. It’s strange that with the same hardware that you are getting more delay on the audio.
 
-Michael
 
From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of Rich KR4PI
Sent: Wednesday, October 12, 2016 8:38 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Loosing Last 1/2 second of transmission
 
Thank you Michael for your help.  Still trying to get this figured out. I have read that the TX Tail setting "pads the audio out until the transmitter drop at the end of a transmission".  Am I to interpret that to mean it puts 100 ms on the end of the transmission before the transmitter shuts down? It seems like 100ms may not be enough time but that is the max it can go to. I am still trying to understand the interaction of both the TX Delay and the TX Tail. ON my hotspot I do not lose any audio but on the DR-1X i lose the last couple letters of a call sign or the last words. 
Thanks for the help.
Rich, KR4PI
 



Re: Loosing Last 1/2 second of transmission

Michael Champion Sr
 

I don’t have the issue at all on mine running 1.10J firmware so I have not fiddled with the setting.  It’s not going to hurt anything to experiment to see if it helps. It’s strange that with the same hardware that you are getting more delay on the audio.

 

-Michael

 

From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of Rich KR4PI
Sent: Wednesday, October 12, 2016 8:38 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Loosing Last 1/2 second of transmission

 

Thank you Michael for your help.  Still trying to get this figured out. I have read that the TX Tail setting "pads the audio out until the transmitter drop at the end of a transmission".  Am I to interpret that to mean it puts 100 ms on the end of the transmission before the transmitter shuts down? It seems like 100ms may not be enough time but that is the max it can go to. I am still trying to understand the interaction of both the TX Delay and the TX Tail. ON my hotspot I do not lose any audio but on the DR-1X i lose the last couple letters of a call sign or the last words. 

Thanks for the help.

Rich, KR4PI

 


Re: SD Surprise

VE3MIC
 

Due to the problems with different image sizes, and the variance in usable free  (advertized) space for the same size SD cards, I've abandoned Win32DiskImager.
I now use an image backup utility by Acronis. It can be "told" not to backup unused, free space unlike Win32DiskImager which requires 2 identical SD cards regardless of how much space is being occupied on the source image.
There are other "Free" programs out there that will ignore the unused partition space, but I have not tried any of them.
73 de Mike

On Wednesday, October 12, 2016 12:49 PM, Jeremy McDermond <mcdermj@...> wrote:


You may want to take a look at this script:

https://github.com/nwdigitalradio/pi-gen/blob/compass/export-image/prerun.sh

It’s a part of the “pi-gen” software that’s used to create Raspbian images.  It will create an image file that is the smallest possible for the amount of data.  This allows you to expand it when it’s put on a new card.  You may be able to adapt it to your backup procedure to get a backup image that you can restore on more different sized cards.

> On Oct 12, 2016, at 9:35 AM, John McDonough <wb8rcr@...> wrote:
>
> Of course I recognized that an 8GB SD card isn't really 8GB, but I sort
> of expected that all the manufacturers would use the same sleazy math
> to inflate their size.  Not so.
>
> The reason this is important is that the safest, easiest way to back up
> a Raspberry Pi is to make an image copy of the SD card from time to
> time.  Something happens, just restore the image onto a fresh card and
> you are good to go.
>
> *BUT*, it turns out that Kingston 8GB SD cards are more than 20MB
> larger than SanDisk cards.  So if you made the original image on a
> Kingston card, you can't restore it to a SanDisk card.
>
> So perhaps I need to pick one or the other and stock up on them.
>
> Bummer.
>
> —McD


Jeremy McDermond
nh6z@...




Re: SD Surprise

Jeremy McDermond <mcdermj@...>
 

You may want to take a look at this script:

https://github.com/nwdigitalradio/pi-gen/blob/compass/export-image/prerun.sh

It’s a part of the “pi-gen” software that’s used to create Raspbian images. It will create an image file that is the smallest possible for the amount of data. This allows you to expand it when it’s put on a new card. You may be able to adapt it to your backup procedure to get a backup image that you can restore on more different sized cards.

On Oct 12, 2016, at 9:35 AM, John McDonough <wb8rcr@arrl.net> wrote:

Of course I recognized that an 8GB SD card isn't really 8GB, but I sort
of expected that all the manufacturers would use the same sleazy math
to inflate their size. Not so.

The reason this is important is that the safest, easiest way to back up
a Raspberry Pi is to make an image copy of the SD card from time to
time. Something happens, just restore the image onto a fresh card and
you are good to go.

*BUT*, it turns out that Kingston 8GB SD cards are more than 20MB
larger than SanDisk cards. So if you made the original image on a
Kingston card, you can't restore it to a SanDisk card.

So perhaps I need to pick one or the other and stock up on them.

Bummer.

—McD

Jeremy McDermond
nh6z@nh6z.net


Re: SD Surprise

 

Yes, unfortunately, the best path is to have the same make and model of SD card for replication or restoration.


--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


SD Surprise

John McDonough
 

Of course I recognized that an 8GB SD card isn't really 8GB, but I sort
of expected that all the manufacturers would use the same sleazy math
to inflate their size.  Not so.

The reason this is important is that the safest, easiest way to back up
a Raspberry Pi is to make an image copy of the SD card from time to
time.  Something happens, just restore the image onto a fresh card and
you are good to go.

*BUT*, it turns out that Kingston 8GB SD cards are more than 20MB
larger than SanDisk cards.  So if you made the original image on a
Kingston card, you can't restore it to a SanDisk card.

So perhaps I need to pick one or the other and stock up on them.

Bummer.

--McD


Re: Loosing Last 1/2 second of transmission

 

Thank you Michael for your help.  Still trying to get this figured out. I have read that the TX Tail setting "pads the audio out until the transmitter drop at the end of a transmission".  Am I to interpret that to mean it puts 100 ms on the end of the transmission before the transmitter shuts down? It seems like 100ms may not be enough time but that is the max it can go to. I am still trying to understand the interaction of both the TX Delay and the TX Tail. ON my hotspot I do not lose any audio but on the DR-1X i lose the last couple letters of a call sign or the last words. 

Thanks for the help.

Rich, KR4PI



Re: Timercontrol

Jeremy McDermond <mcdermj@...>
 


On Oct 12, 2016, at 3:32 AM, John M Wysocki ZL2TWS <zl2tws@...> wrote:

Hello NW Team.

I would like to use Timercontrol on the ircDDBGateway package with compass and UDRC.

Timeserver 1, Timeserverd 1, Timercontrol 1, Timercontrold 1, Remotecontrol 1 and Remotecontrold 1 all install without errors but when I run

Timercontrol 1 the following message is displayed:

pi@compass:~ $ sudo timercontrol 1

Fatal Error: Assertion failed on line 38 in file TimerControl/TimerControlRemoteControlHandler.cpp and function CTimerControlRemoteControlHandler: !address.IsEmpty() 

pi@compass:~ $ 

What can be wrong to cause this?
Remotecontrol 1 and Timeserver 1 are working correctly.

It appears as though the daemon is not getting the address of the gateway correctly from the configuration file.  I looked briefly through the code, and it appears as though it possibly didn’t get updated to use /etc/opendv as it’s configuration directory, so it might not be finding the configuration file at all.  I’ll have to look into it and see if I can get a patch generated.  In the mean time, you can try to use the -confdir flag to make sure the configuration directory is set correctly.

Thank you, 73, John ZL2TWS

Jeremy McDermond

5281 - 5300 of 6024