what generates log file messages

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

what generates log file messages

Joe Erlewein N8CN
Rx1/Tx1 are a repeater pair
Rx2/Tx2 is a simplex channel

Here’s a snippet of my /var/log/svxlink file during normal operation:

(signal comes in on Rx1)

Tue Dec 29 15:44:09 2015: Rx1: The squelch is OPEN (0.758677)
Tue Dec 29 15:44:09 2015: Tx1: Turning the transmitter ON
Tue Dec 29 15:44:09 2015: The squelch is 1 on RX 0
Tue Dec 29 15:44:10 2015: Tx2: Turning the transmitter ON
Tue Dec 29 15:44:12 2015: Rx1: The squelch is CLOSED (6.36083)
Tue Dec 29 15:44:12 2015: The squelch is 0 on RX 0
Tue Dec 29 15:44:12 2015: Tx2: Turning the transmitter OFF
Tue Dec 29 15:44:16 2015: Tx1: Turning the transmitter OFF



(signal comes in on Rx2)

Tue Dec 29 15:44:26 2015: Rx2: The squelch is OPEN (6.85944)
Tue Dec 29 15:44:26 2015: The squelch is 1 on RX 0
Tue Dec 29 15:44:26 2015: Tx1: Turning the transmitter ON
Tue Dec 29 15:44:33 2015: Rx2: The squelch is CLOSED (6.05768)
Tue Dec 29 15:44:33 2015: The squelch is 0 on RX 0
Tue Dec 29 15:44:37 2015: Tx1: Turning the transmitter OFF


Regarding the red text above: Where is this generated? Does anyone know? I’ve looked recursively in /etc/svxlink and /usr/share/svxlink and can’t find mention of it
(using “grep squelch * | grep puts” then “grep squelch */* | grep puts” then “grep squelch */*/* | grep puts” and so on..)

I want to find it to see if I can fix it, because it says RX 0 all of the time, which is not correct.

regarding the blue text above: What does the number at the end of the CLOSED statements mean? Does anyone know where this is located? I want to make changes, but the only mention of “CLOSED” I could found was in /usr/share/svxlink/modules.d/ModuleTcl.tcl.example 

I changed it to “CLOS3D” and restarted the service to see if I had found the correct occurrence, and I indeed have not. the text remained “CLOSED”..


hints? (wish i was a better programmer..)


Thanks!  :)
Joe






------------------------------------------------------------------------------

_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what generates log file messages

Rob Janssen
Joe Erlewein wrote:

I want to find it to see if I can fix it, because it says RX 0 all of the time, which is not correct.

The RX number is a sequential number of the receiver within that logic (which can have multiple receivers when you have a Voter).
In your case it is confusing because the numbering is separate for the two logics and both of your receivers are number 0.

The message is output in proc squelch_open in /usr/share/svxlink/events.d/Logic.tcl or in your local copy, but only after you
have removed the # mark.


regarding the blue text above: What does the number at the end of the CLOSED statements mean?

It is the signal quality of the signal at the receiver (on a 0..100 scale) at the moment de software decides the squelch is closed.
What this exactly means depends on your configuration and whether you calibrated the scale (siglevdetcal).

Rob

------------------------------------------------------------------------------

_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what generates log file messages

Joe Erlewein N8CN

> On Dec 29, 2015, at 16:27, Rob Janssen <[hidden email]> wrote:
>
> Joe Erlewein wrote:
>>
>> I want to find it to see if I can fix it, because it says RX 0 all of the time, which is not correct.
>
> The RX number is a sequential number of the receiver within that logic (which can have multiple receivers when you have a Voter).
> In your case it is confusing because the numbering is separate for the two logics and both of your receivers are number 0.
>
> The message is output in proc squelch_open in /usr/share/svxlink/events.d/Logic.tcl or in your local copy, but only after you
> have removed the # mark.
>

Aaahh.. I see. So if since there are two logics, with one receiver (0) each, it’s always… zero! :)

Thanks!



>>
>> regarding the blue text above: What does the number at the end of the CLOSED statements mean?
>
> It is the signal quality of the signal at the receiver (on a 0..100 scale) at the moment de software decides the squelch is closed.
> What this exactly means depends on your configuration and whether you calibrated the scale (siglevdetcal).
>
> Rob

Hmm. I don’t think I have that connected.. if it is an additional GPIO input for instance, which I haven’t.
If it’s something I can do with just GND, COS, and RXA, it looks like I’ve got a new adventure to learn about!
If not and I need another GPIO for a voltage-level on my receiver that changes with signal strength, then I have some soldering to do. :)

Thanks Rob!
73,
Joe


------------------------------------------------------------------------------
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what generates log file messages

Rob Janssen
Joe Erlewein wrote:

>
> regarding the blue text above: What does the number at the end of the CLOSED statements mean?
>> It is the signal quality of the signal at the receiver (on a 0..100 scale) at the moment de software decides the squelch is closed.
>> What this exactly means depends on your configuration and whether you calibrated the scale (siglevdetcal).
>>
>> Rob
> Hmm. I don’t think I have that connected.. if it is an additional GPIO input for instance, which I haven’t.
> If it’s something I can do with just GND, COS, and RXA, it looks like I’ve got a new adventure to learn about!
> If not and I need another GPIO for a voltage-level on my receiver that changes with signal strength, then I have some soldering to do. :)
>

When your receive audio is not filtered (i.e. directly from the detector; 9600 baud connect for example) the signal quality
can be calculated from the level of noise above the normal audio passband.
No other signal lines are required, but it is important that you have unsquelched and unfiltered audio.

Using siglevdetcal you have to calibrate the 0 and 100 levels by changing the SIGLEV_SLOPE and SIGLEV_OFFSET
parameters in the configuration.

The result can then be used to get a software squelch (SQL_DET=SIGLEV and SIGLEV_OPEN_THRESH/SIGLEV_CLOSE_THRESH)
and to use the quality in a voter to decide which receiver has the best signal.

When you have a voter (even with just one receiver!) you can also feed this value to a webpage where you can monitor the
signal level present on the receivers, see for example http://pe1chl.nl.eu.org/repeaters/
The code to do that is included in the svxlink/src/svxlink/scripts/eventsource directory.

Rob


------------------------------------------------------------------------------
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what generates log file messages

Joe Erlewein N8CN

> On Dec 29, 2015, at 16:53, Rob Janssen <[hidden email]> wrote:
>
> Joe Erlewein wrote:
>>
>> regarding the blue text above: What does the number at the end of the CLOSED statements mean?
>>> It is the signal quality of the signal at the receiver (on a 0..100 scale) at the moment de software decides the squelch is closed.
>>> What this exactly means depends on your configuration and whether you calibrated the scale (siglevdetcal).
>>>
>>> Rob
>> Hmm. I don’t think I have that connected.. if it is an additional GPIO input for instance, which I haven’t.
>> If it’s something I can do with just GND, COS, and RXA, it looks like I’ve got a new adventure to learn about!
>> If not and I need another GPIO for a voltage-level on my receiver that changes with signal strength, then I have some soldering to do. :)
>>
>
> When your receive audio is not filtered (i.e. directly from the detector; 9600 baud connect for example) the signal quality
> can be calculated from the level of noise above the normal audio passband.
> No other signal lines are required, but it is important that you have unsquelched and unfiltered audio.

Holy cow, that is awesome!
I think I am in luck; when I modified my Maxtrac radios for COS, I plucked a pin from discriminator audio and am using that. Sounds like I’m set :)

> Using siglevdetcal you have to calibrate the 0 and 100 levels by changing the SIGLEV_SLOPE and SIGLEV_OFFSET
> parameters in the configuration.

Neat! Sounds like it’s some bench-time and tweaking, and restarting of the svxlink service when I change values, but the result will definitely be worth it.
Just in time for the upcoming three-day weekend: a new project :)

> The result can then be used to get a software squelch (SQL_DET=SIGLEV and SIGLEV_OPEN_THRESH/SIGLEV_CLOSE_THRESH)
> and to use the quality in a voter to decide which receiver has the best signal.
>
> When you have a voter (even with just one receiver!) you can also feed this value to a webpage where you can monitor the
> signal level present on the receivers, see for example http://pe1chl.nl.eu.org/repeaters/
> The code to do that is included in the svxlink/src/svxlink/scripts/eventsource directory.


I think I just drooled on my keyboard. This is on the very top of my list of cool things I’ve seen in 2015. :)
it sets the bar pretty high going into next year, for sure.

Thanks Rob!

Joe




------------------------------------------------------------------------------
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what generates log file messages

Rob Janssen
Joe Erlewein wrote:
> I think I just drooled on my keyboard. This is on the very top of my list of cool things I’ve seen in 2015. :)
> it sets the bar pretty high going into next year, for sure.

Ok...  well then I did not even give you the URL of another page that PC7X made with the same eventsource information:
https://pc7x.net/repeaters/#/map/google/pi2nos

This form is of course mainly useful for repeaters with a lot of receivers like our PI2NOS and another group's PI2NON.
It can even compute an approximation of the location of the transmitting station when it is received on many receivers.

I should mention that support for more than one logic on the same machine is not really available in the eventsource
server so you will have to tinker a bit with that (run 2 copies or combine the two logics in a single display).

Rob


------------------------------------------------------------------------------
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Loading...