PSAT2 digipeating and aprs-to-voice ops are working using the special APRS-to-voice packet format.
But not both. A packet with a digipeating path will not be spoken and a properly formatted text-to-voice message will not be digipeated. This is a quirk of the TNC that for some reason does not pass a digipeated packet out its serial port to the Speech CPU.
Also the 6 day watchdog timer is about to reset and will probably reboot the spacecraft's comm system overnight. We are letting this fail-safe watchdog timer time out intentionally so we can verify it works. Turns out, the Speech CPU is sleeping longer than we expected and so it turned into a 9 day timer! We hope our command station in Brazil can restore it tomorrow.
You can see the alphabetic watchdog timer count (y) as the first character in the APRS-to-voice bulletin:
PSAT2>APDIGI,ARISS::BLNg-APRS:y|Q S T: This is the Aee PRS bullettin .
It turned to (y) sometime between 1400 and 1700z today and after (z) it will reset (it is 8 hours per count)...
If you wonder about the spelling of this bulletin, that is intentional, because it is intended that this bulletin be spoken. We have found that creative spelling can get the sound you want instead of what the text-to-speech processor might come up with. And remember, for text-to-speech, use lower case, or it will spell-out letters if they are uppercase. Hence "Aee PRS" is the correct pronunciation of APRS and not "Aprs" that some people use <wink> ;-)
Bob, WB4APR
A packet with a digipeating path will not be spoken
Your updates are very helpful as we learn about the capabilities of this new satellite - thanks Bob!
Regarding the text-to-voice, are you saying that we should not transmit messages in that format to the normal 'ARISS' path?
If not, then what path should be used for text-to-voice messages?
Thanks!
-Scott, K4KDR
==================
On Wed, Jul 3, 2019 at 4:03 PM Robert Bruninga via AMSAT-BB < [email protected]> wrote:
PSAT2 digipeating and aprs-to-voice ops are working using the special APRS-to-voice packet format.
But not both. A packet with a digipeating path will not be spoken and a properly formatted text-to-voice message will not be digipeated. This is a quirk of the TNC that for some reason does not pass a digipeated packet out its serial port to the Speech CPU.
Also the 6 day watchdog timer is about to reset and will probably reboot the spacecraft's comm system overnight. We are letting this fail-safe watchdog timer time out intentionally so we can verify it works. Turns out, the Speech CPU is sleeping longer than we expected and so it turned into a 9 day timer! We hope our command station in Brazil can restore it tomorrow.
You can see the alphabetic watchdog timer count (y) as the first character in the APRS-to-voice bulletin:
PSAT2>APDIGI,ARISS::BLNg-APRS:y|Q S T: This is the Aee PRS bullettin .
It turned to (y) sometime between 1400 and 1700z today and after (z) it will reset (it is 8 hours per count)...
If you wonder about the spelling of this bulletin, that is intentional, because it is intended that this bulletin be spoken. We have found that creative spelling can get the sound you want instead of what the text-to-speech processor might come up with. And remember, for text-to-speech, use lower case, or it will spell-out letters if they are uppercase. Hence "Aee PRS" is the correct pronunciation of APRS and not "Aprs" that some people use <wink> ;-)
Bob, WB4APR
If not ARISS, then what path should be used for text-to-voice messages?
No path that the satellite recognizes, (not ARISS and not APRSAT). Then if the rest of the special "say this" packet is correct it will get spoken if that mode is enabled. You can tell if text-to-voice mode is enabled by the X bit in the telemetry ....010001X1.
The latest firmware for the D72, D74 and D710 radios will now decode and display the telemetry packet so you can tell the modes.
Or, just download the PSAT2 Users Operating Manual from the web page: http://aprs.org/psat2.html
-----Original Message----- From: AMSAT-BB [email protected] On Behalf Of Scott via AMSAT-BB Sent: Wednesday, July 3, 2019 5:46 PM To: amsat bb [email protected] Subject: Re: [amsat-bb] PSAT2 Status and Voice Ops (and reset)
A packet with a digipeating path will not be spoken
Your updates are very helpful as we learn about the capabilities of this new satellite - thanks Bob!
Regarding the text-to-voice, are you saying that we should not transmit messages in that format to the normal 'ARISS' path?
If not, then what path should be used for text-to-voice messages?
Thanks!
-Scott, K4KDR
==================
On Wed, Jul 3, 2019 at 4:03 PM Robert Bruninga via AMSAT-BB < [email protected]> wrote:
PSAT2 digipeating and aprs-to-voice ops are working using the special APRS-to-voice packet format.
But not both. A packet with a digipeating path will not be spoken and a properly formatted text-to-voice message will not be digipeated. This is a quirk of the TNC that for some reason does not pass a digipeated packet out its serial port to the Speech CPU.
Also the 6 day watchdog timer is about to reset and will probably reboot the spacecraft's comm system overnight. We are letting this fail-safe watchdog timer time out intentionally so we can verify it works. Turns out, the Speech CPU is sleeping longer than we expected and so it turned into a 9 day timer! We hope our command station in Brazil can restore it tomorrow.
You can see the alphabetic watchdog timer count (y) as the first character in the APRS-to-voice bulletin:
PSAT2>APDIGI,ARISS::BLNg-APRS:y|Q S T: This is the Aee PRS bullettin .
It turned to (y) sometime between 1400 and 1700z today and after (z) it will reset (it is 8 hours per count)...
If you wonder about the spelling of this bulletin, that is intentional, because it is intended that this bulletin be spoken. We have found that creative spelling can get the sound you want instead of what the text-to-speech processor might come up with. And remember, for text-to-speech, use lower case, or it will spell-out letters if they are uppercase. Hence "Aee PRS" is the correct pronunciation of APRS and not "Aprs" that some people use <wink> ;-)
Bob, WB4APR
_______________________________________________ Sent via [email protected]. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
participants (2)
-
Robert Bruninga -
Scott