Vittorio at 14:17, 15 March 2021

2021-03-15T14:17:22Z

Vittorio: Created page with "Sometimes it is necessary / useful to be able to switch between different antennas. In this way the observations can take place on different bands, or it is useful to have onl..."

2021-03-15T13:55:12Z

Created page with "Sometimes it is necessary / useful to be able to switch between different antennas. In this way the observations can take place on different bands, or it is useful to have onl..."

New page

Sometimes it is necessary / useful to be able to switch between different antennas. In this way the observations can take place on different bands, or it is useful to have only one feeder, with excellent performance in terms of attenuation, from the antennas to the receiver.

Read carefully the full thread in [ https://community.libre.space/t/antenna-switching-project/2311 ], where it's possible to find different solutions, ranging from "parallel" control exploited via GPIO pins, to "serial" solution via USB connection or via RS485 (under tests) for longer physical connections.

Several parts (software & hardware) are necessary to activate this kind of control. Once the type of control has been established there are some software setting to be done, mainly to write scripts which will be performed before and after the observations.

Firstly, run 'sudo satnogs-setup' , then into "Advanced" section edit the parameter SATNOGS''PRE''OBSERVATION''SCRIPT to <path_''to_script>preob.sh -f <nowiki>{{ FREQ }}</nowiki>.

In the same manner in satnogs-setup set the parameter SATNOGS''POST''OBSERVATION''SCRIPT to <path''_to_script>postob.sh

This, for example, is the content of preob.sh and postob.sh, invoked by the client to switch the correct antenna using an USB serial connection. Pay attention to the exact syntax and to the following described permissions on scripts and users:

 

*'''preob.sh''' : called just before observation starts, set the right antenna and write to the local satnogs log.

 <pre class="">#!/bin/bash
#set the ports up to known state and disable close between calls
stty -F /dev/ttyUSB0 9600 -hupcl

date=`date +"%d/%m/%y %H:%M:%S %Z"`
freq=0

while getopts f: option
do
case "${option}"
in
f) freq=${OPTARG};;
esac

if ([ $freq -ge 399900000 ] && [ $freq -lt 470000000 ]) ;
then
echo "$date --> 399.9 to 470 frequency, ANT0 selected" >> /home/pi/tests/satnogs_log.txt
echo -e "ANT0\n" > /dev/ttyUSB0
fi

if ([ $freq -ge 136000000 ] && [ $freq -lt 150100000 ]) ;
then
echo "$date --> 136 to 150.1 frequency, ANT1 selected" >> /home/pi/tests/satnogs_log.txt
echo -e "ANT1\n" > /dev/ttyUSB0
fi

if ([ $freq -ge 24000000 ] && [ $freq -lt 30000000 ]) ;
then
echo "$date --> 24 to 30 frequency, ANT2 selected" >> /home/pi/tests/satnogs_log.txt
echo -e "ANT2\n" > /dev/ttyUSB0
fi

done</pre>

*'''postob.sh''' : called at observation end, puts RF relays in ‘deactivated’ position and to setup a know switch position.

 <pre class="">#!/bin/bash
# disable all relays... no power waste!

date=`date +"%d/%m/%y %H:%M:%S %Z"`
echo -e "ANT0\n" > /dev/ttyUSB0
echo "$date antenna switch reset " >> /home/pi/tests/satnogs_log.txt</pre>

Please take note about the following mandatory permissions, because the scripts are executed as “satnogs” user:

*<code>sudo usermod -a -G dialout satnogs</code>, to access serial device by satnogs user
*<code>sudo usermod -a -G pi satnogs</code>, to permit execution to satnogs as member of pi group
*<code>touch satnogs_log.txt</code>, to create the log file
*<code>chmod 666 satnogs_log.txt</code>, to permit everybody writing on this file
*<code>chmod +x preob.sh</code>, set script to be executable
*<code>chmod +x postob.sh</code>, set script to be executable

To test the whole stuff try to execute:<pre class="">./preob.sh -f 435000000

./postob.sh

tail ./satnogs_log.txt</pre>and satnogs_log.txt should contain something like:<pre class="">18/02/21 12:15:25 GMT --> 399.9 to 470 frequency, ANT0 selected
18/02/21 12:30:23 GMT antenna switch reset </pre>

@@ Line 5: / Line 5: @@
 Several parts (software &amp; hardware) are necessary to activate this kind of control. Once the type of control has been established there are some software setting to be done, mainly to write scripts which will be performed before and after the observations.
-Firstly, run 'sudo satnogs-setup' , then into &quot;Advanced&quot; section edit the parameter SATNOGS''PRE''OBSERVATION''SCRIPT to &lt;path_''to_script&gt;preob.sh -f <nowiki>{{ FREQ }}</nowiki>.
+Firstly, run 'sudo satnogs-setup' , then into &quot;Advanced&quot; section edit the parameter SATNOGS_''PRE_''OBSERVATION_''SCRIPT to &lt;path_''to_script&gt;preob.sh -f <nowiki>{{ FREQ }}</nowiki>.
-In the same manner in satnogs-setup set the parameter SATNOGS''POST''OBSERVATION''SCRIPT to &lt;path''_to_script&gt;postob.sh
+In the same manner in satnogs-setup set the parameter SATNOGS_''POST_''OBSERVATION_''SCRIPT to &lt;path''_to_script&gt;postob.sh
 This, for example, is the content of preob.sh and postob.sh, invoked by the client to switch the correct antenna using an USB serial connection. Pay attention to the exact syntax and to the following described permissions on scripts and users:
@@ Line 67: / Line 67: @@
 *<code>chmod +x preob.sh</code>, set script to be executable
 *<code>chmod +x postob.sh</code>, set script to be executable

Antenna switching - Revision history

Vittorio at 14:17, 15 March 2021

Vittorio: Created page with "Sometimes it is necessary / useful to be able to switch between different antennas. In this way the observations can take place on different bands, or it is useful to have onl..."