You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running an APRX Igate in my community for a long time using an RPi. I love it! because it's really very stable and until now works flawlessly.
Today I'm was needed to avoid TX any packet and my first thougth was to edit my config and in my section edit the "tx-ok true" option to false..
Then I restarted the service, but the service don't started...
On the syslog these lines point to me the problem:
May 28 12:13:47 raspberrypi3 systemd[1]: Starting LSB: start and stop aprx...
May 28 12:13:47 raspberrypi3 aprx[10002]: /etc/aprx.conf:93 ERROR: This transmit interface has no TX-OK TRUE setting: 'CX8FS-2'
May 28 12:13:47 raspberrypi3 aprx[10002]: ERROR: Failures on defining block parameters
May 28 12:13:47 raspberrypi3 aprx[10002]: APRS RF-Telemetry will not be activated.
May 28 12:13:47 raspberrypi3 aprx[10002]: /etc/aprx.conf:99 ERROR: This transmit interface has no TX-OK TRUE setting: 'CX8FS-2'
May 28 12:13:47 raspberrypi3 aprx[10002]: ERROR: Config fault observed on definitions!
May 28 12:13:47 raspberrypi3 aprx[10002]: Seen configuration errors. Aborting!
May 28 12:13:48 raspberrypi3 systemd[1]: Started LSB: start and stop aprx.
The problem seems to be a conflict between the tx-ok=false and the sections on the config who expected a TX enabled and exited the execution with an error.
I think maybe it's a harsh behavior, because the parser only need to ignore these parts of the config who are useless for a RX-Only.
My actual interface and telemetry sections are this.
<interface> serial-device /dev/ttyAMA0 19200 8n1 KISS callsign $mycall tx-ok true # transmitter enable defaults to false #telem-to-is false # set to 'false' to disable </interface>
...... <telemetry> transmitter $mycall via TRACE1-1 source $mycall </telemetry>
Needless to say, the configuration is correct and the behavior of APRX when the transmission is enabled works without problems.
Thanks in advance..
Claudio CX8FS
The text was updated successfully, but these errors were encountered:
Hello everybody,
I'm running an APRX Igate in my community for a long time using an RPi. I love it! because it's really very stable and until now works flawlessly.
Today I'm was needed to avoid TX any packet and my first thougth was to edit my config and in my section edit the "tx-ok true" option to false..
Then I restarted the service, but the service don't started...
On the syslog these lines point to me the problem:
May 28 12:13:47 raspberrypi3 systemd[1]: Starting LSB: start and stop aprx...
May 28 12:13:47 raspberrypi3 aprx[10002]: /etc/aprx.conf:93 ERROR: This transmit interface has no TX-OK TRUE setting: 'CX8FS-2'
May 28 12:13:47 raspberrypi3 aprx[10002]: ERROR: Failures on defining block parameters
May 28 12:13:47 raspberrypi3 aprx[10002]: APRS RF-Telemetry will not be activated.
May 28 12:13:47 raspberrypi3 aprx[10002]: /etc/aprx.conf:99 ERROR: This transmit interface has no TX-OK TRUE setting: 'CX8FS-2'
May 28 12:13:47 raspberrypi3 aprx[10002]: ERROR: Config fault observed on definitions!
May 28 12:13:47 raspberrypi3 aprx[10002]: Seen configuration errors. Aborting!
May 28 12:13:48 raspberrypi3 systemd[1]: Started LSB: start and stop aprx.
The problem seems to be a conflict between the tx-ok=false and the sections on the config who expected a TX enabled and exited the execution with an error.
I think maybe it's a harsh behavior, because the parser only need to ignore these parts of the config who are useless for a RX-Only.
My actual interface and telemetry sections are this.
<interface>
serial-device /dev/ttyAMA0 19200 8n1 KISS
callsign $mycall
tx-ok true # transmitter enable defaults to false
#telem-to-is false # set to 'false' to disable
</interface>
......
<telemetry>
transmitter $mycall
via TRACE1-1
source $mycall
</telemetry>
Needless to say, the configuration is correct and the behavior of APRX when the transmission is enabled works without problems.
Thanks in advance..
Claudio CX8FS
The text was updated successfully, but these errors were encountered: