Hello All,
I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status.
So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration.
Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems.
As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting).
1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS.
2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out.
Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions.
Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well.
Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :)
73
Sincerely, Rizwan Merchant KF5BNL
Hello Riz,
My APRS gateway is running and I am waiting to receive another *EMAIL packet. Unfortunately, this was not the case in the last 2 days.
Enclosed new beacons ... Is kiss ok or do you need the hex format?
73 Mike
DK3WN
Von: Rizwan Merchant kommandantdrake@gmail.com Gesendet: Mittwoch, 3. Februar 2021 05:25 An: Amsat - BBs amsat-bb@amsat.org; mail@mike-rupprecht.de Cc: nicktstephan (nicktstephan@gmail.com) nickTstephan@gmail.com; Nolan Edwards nje@nolanjohnedwards.com; jake sonnier jcrsonnier@gmail.com; Nicholas J Drozda nicholas.drozda1@louisiana.edu Betreff: [AMSAT-BB] CAPE-3 Updates and iGate Request
Hello All,
I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status.
So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration.
Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems.
As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting).
1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS.
2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out.
Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions.
Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well.
Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :)
73
Sincerely,
Rizwan Merchant
KF5BNL
Hello Riz,
are we talking about a standard APRS 70cm frequency of 432.500 MHz? If yes I can also set one up.
73 Fabian DB7FS
Am 03.02.2021 um 07:39 schrieb mail@mike-rupprecht.de:
Hello Riz,
My APRS gateway is running and I am waiting to receive another *EMAIL packet. Unfortunately, this was not the case in the last 2 days.
Enclosed new beacons ... Is kiss ok or do you need the hex format?
73 Mike DK3WN
Von: Rizwan Merchant kommandantdrake@gmail.com Gesendet: Mittwoch, 3. Februar 2021 05:25 An: Amsat - BBs amsat-bb@amsat.org; mail@mike-rupprecht.de Cc: nicktstephan (nicktstephan@gmail.com) nickTstephan@gmail.com; Nolan Edwards nje@nolanjohnedwards.com; jake sonnier jcrsonnier@gmail.com; Nicholas J Drozda nicholas.drozda1@louisiana.edu Betreff: [AMSAT-BB] CAPE-3 Updates and iGate Request
Hello All,
I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status.
So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration.
Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems.
As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting).
1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS.
2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out.
Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions.
Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well.
Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :)
73
Sincerely, Rizwan Merchant KF5BNL <2021-02-03_dk3wn_cape-3.kss> <2021-02-02_dk3wn_cape-3.kss>
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 2/2/2021 11:25 PM, Rizwan Merchant wrote:
Hello All,
I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status.
So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration.
Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems.
As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ https://www.satblog.info/new-cape-3-beacons/ we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting).
1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS.
2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out.
Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions.
Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well.
Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :)
73
Sincerely, Rizwan Merchant KF5BNL
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
No, it is not a 'standard' 70cm APRS frequency - that's going to vary from country to country, and would be outside of the satellite segment anyway.
CAPE-3 transmits on 437.325 MHz.
The SatNOGS network is getting packets fairly regularly: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&a...
73 Mark VK5QI
On Thu, Feb 4, 2021 at 12:14 AM Lynn W Deffenbaugh (Mr) KJ4ERJ@arrl.net wrote:
For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 2/2/2021 11:25 PM, Rizwan Merchant wrote:
Hello All,
I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status.
So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration.
Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems.
As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting).
1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS.
2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out.
Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions.
Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well.
Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :)
73
Sincerely, Rizwan Merchant KF5BNL
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Hi Every one,
Does anyone have GNU radio flow chart all ready setup for igating CAPE-3 uhf aprs?
I have a b100 that I'm happy to use to get the packets of CAPE-3.
Located in SE Australia.
Pete
VK2PET.
On 4/02/2021 8:17 am, Mark Jessop wrote:
No, it is not a 'standard' 70cm APRS frequency - that's going to vary from country to country, and would be outside of the satellite segment anyway.
CAPE-3 transmits on 437.325 MHz.
The SatNOGS network is getting packets fairly regularly: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&a... https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&failed=0&norad=47309&observer=&station=&start=&end=
73 Mark VK5QI
On Thu, Feb 4, 2021 at 12:14 AM Lynn W Deffenbaugh (Mr) <KJ4ERJ@arrl.net mailto:KJ4ERJ@arrl.net> wrote:
For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 2/2/2021 11:25 PM, Rizwan Merchant wrote:Hello All, I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status. So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration. Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems. As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ <https://www.satblog.info/new-cape-3-beacons/> we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting). 1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS. 2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out. Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions. Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work. So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well. Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :) 73 Sincerely, Rizwan Merchant KF5BNL ----------------------------------------------------------- Sent via AMSAT-BB(a)amsat.org <http://amsat.org>. 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! View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org <https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org> To unsubscribe send an email to amsat-bb-leave(a)amsat.org <http://amsat.org> Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org <https://mailman.amsat.org>----------------------------------------------------------- Sent via AMSAT-BB(a)amsat.org <http://amsat.org>. 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! View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org <https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org> To unsubscribe send an email to amsat-bb-leave(a)amsat.org <http://amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org <https://mailman.amsat.org>
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Hello all,
Sorry I fell off the face of the Earth with emails. It's been a hectic time with moving into a new house and making regular trips between Louisiana and Texas to support the CAPE-3 Mission. Anyway let me provide a few quick answers:
1.) We are expecting UHF APRS on 437.325, the same as what our FSK and AX.25 packets are coming across on.
2.) From what I can tell, our NORAD ID is 47309.
3.) Currently we are having some issues commanding CAPE-3 from our University lab, so once we are able to transmit commands, we'll be able to set the APRS emails to come across more often, and begin experimenting the tweeting function to see if it works as we intended.
I'd like to thank everyone who's helped so far! We got our first email packet from W7KKE-13 earlier this evening.
Sincerely, Rizwan Merchant KF5BNL
On Wed, Feb 3, 2021 at 5:43 PM Pete vk2pet vk2pet@internode.on.net wrote:
Hi Every one,
Does anyone have GNU radio flow chart all ready setup for igating CAPE-3 uhf aprs?
I have a b100 that I'm happy to use to get the packets of CAPE-3.
Located in SE Australia.
Pete
VK2PET. On 4/02/2021 8:17 am, Mark Jessop wrote:
No, it is not a 'standard' 70cm APRS frequency - that's going to vary from country to country, and would be outside of the satellite segment anyway.
CAPE-3 transmits on 437.325 MHz.
The SatNOGS network is getting packets fairly regularly: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&a...
73 Mark VK5QI
On Thu, Feb 4, 2021 at 12:14 AM Lynn W Deffenbaugh (Mr) KJ4ERJ@arrl.net wrote:
For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 2/2/2021 11:25 PM, Rizwan Merchant wrote:
Hello All,
I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status.
So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration.
Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems.
As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting).
1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS.
2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out.
Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions.
Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well.
Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :)
73
Sincerely, Rizwan Merchant KF5BNL
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Copy of the iGated packet we got an hour ago-ish:
W5UL-11>KF5BNL-7,WIDE2-2,qAO,W7KKE-13:*EMAIL cape.cubesats@gmail.com 3844, 3844, 3848, -110, 0, 0, 14, 13, 14, 3820, 108, 18, 17, 1, 1, 11, 40
Sincerely, Rizwan Merchant KF5BNL
On Fri, Feb 5, 2021 at 11:45 PM Rizwan Merchant kommandantdrake@gmail.com wrote:
Hello all,
Sorry I fell off the face of the Earth with emails. It's been a hectic time with moving into a new house and making regular trips between Louisiana and Texas to support the CAPE-3 Mission. Anyway let me provide a few quick answers:
1.) We are expecting UHF APRS on 437.325, the same as what our FSK and AX.25 packets are coming across on.
2.) From what I can tell, our NORAD ID is 47309.
3.) Currently we are having some issues commanding CAPE-3 from our University lab, so once we are able to transmit commands, we'll be able to set the APRS emails to come across more often, and begin experimenting the tweeting function to see if it works as we intended.
I'd like to thank everyone who's helped so far! We got our first email packet from W7KKE-13 earlier this evening.
Sincerely, Rizwan Merchant KF5BNL
On Wed, Feb 3, 2021 at 5:43 PM Pete vk2pet vk2pet@internode.on.net wrote:
Hi Every one,
Does anyone have GNU radio flow chart all ready setup for igating CAPE-3 uhf aprs?
I have a b100 that I'm happy to use to get the packets of CAPE-3.
Located in SE Australia.
Pete
VK2PET. On 4/02/2021 8:17 am, Mark Jessop wrote:
No, it is not a 'standard' 70cm APRS frequency - that's going to vary from country to country, and would be outside of the satellite segment anyway.
CAPE-3 transmits on 437.325 MHz.
The SatNOGS network is getting packets fairly regularly: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&a...
73 Mark VK5QI
On Thu, Feb 4, 2021 at 12:14 AM Lynn W Deffenbaugh (Mr) KJ4ERJ@arrl.net wrote:
For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 2/2/2021 11:25 PM, Rizwan Merchant wrote:
Hello All,
I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status.
So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration.
Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems.
As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting).
1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS.
2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out.
Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions.
Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well.
Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :)
73
Sincerely, Rizwan Merchant KF5BNL
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Hi Rizwan,
I note that the last few packets received in the SatNOGS network do not match this format. e.g. this observation: https://network.satnogs.org/observations/3600190/ (go to the data tab)
Note that the data packet shown there is the contents of the AX.25 frame, minus the frame check. The first few bytes are clearly an AX.25 address, and decode to DST: W5UL-1 SRC: W5UL-11 However apart from a little bit of ASCII text ("CAPE-3 W5UL-11") the rest of the data appears to be some binary format? DK3WN appears to have a decoder here ( https://www.dk3wn.info/files/cape3.zip ) but I'm not sure where he got his telemetry information from.
Could you perhaps provide some details on this binary format, since we are regularly receiving packets on the SatNOGS network, and it would be possible to put together a telemetry dashboard (e.g. like Bobcat-1's dashboard here: https://dashboard.satnogs.org/d/BFU00FHMz/bobcat-1?orgId=1 )
A link to observations which have seen signals from CAPE-3 are here: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&a...
The ones with valid data packets are marked as such in the 'results' column.
73 Mark VK5QI
On Sat, Feb 6, 2021 at 4:17 PM Rizwan Merchant kommandantdrake@gmail.com wrote:
Copy of the iGated packet we got an hour ago-ish:
W5UL-11>KF5BNL-7,WIDE2-2,qAO,W7KKE-13:*EMAIL cape.cubesats@gmail.com 3844, 3844, 3848, -110, 0, 0, 14, 13, 14, 3820, 108, 18, 17, 1, 1, 11, 40
Sincerely, Rizwan Merchant KF5BNL
On Fri, Feb 5, 2021 at 11:45 PM Rizwan Merchant kommandantdrake@gmail.com wrote:
Hello all,
Sorry I fell off the face of the Earth with emails. It's been a hectic time with moving into a new house and making regular trips between Louisiana and Texas to support the CAPE-3 Mission. Anyway let me provide a few quick answers:
1.) We are expecting UHF APRS on 437.325, the same as what our FSK and AX.25 packets are coming across on.
2.) From what I can tell, our NORAD ID is 47309.
3.) Currently we are having some issues commanding CAPE-3 from our University lab, so once we are able to transmit commands, we'll be able to set the APRS emails to come across more often, and begin experimenting the tweeting function to see if it works as we intended.
I'd like to thank everyone who's helped so far! We got our first email packet from W7KKE-13 earlier this evening.
Sincerely, Rizwan Merchant KF5BNL
On Wed, Feb 3, 2021 at 5:43 PM Pete vk2pet vk2pet@internode.on.net wrote:
Hi Every one,
Does anyone have GNU radio flow chart all ready setup for igating CAPE-3 uhf aprs?
I have a b100 that I'm happy to use to get the packets of CAPE-3.
Located in SE Australia.
Pete
VK2PET. On 4/02/2021 8:17 am, Mark Jessop wrote:
No, it is not a 'standard' 70cm APRS frequency - that's going to vary from country to country, and would be outside of the satellite segment anyway.
CAPE-3 transmits on 437.325 MHz.
The SatNOGS network is getting packets fairly regularly: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&a...
73 Mark VK5QI
On Thu, Feb 4, 2021 at 12:14 AM Lynn W Deffenbaugh (Mr) KJ4ERJ@arrl.net wrote:
For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 2/2/2021 11:25 PM, Rizwan Merchant wrote:
Hello All,
I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status.
So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration.
Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems.
As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting).
1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS.
2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out.
Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions.
Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well.
Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :)
73
Sincerely, Rizwan Merchant KF5BNL
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Here is a copy of the packet decoded during the pass over my station a few minutes ago: 1:Fm W5UL-11 To W5UL-1 <UI R Pid=F0 Len=200> [20:24:05R] [+++]CAPE-3 W5UL-1100010001B0000000Œ:˜ðkÄÿ“ÈЀ¬Øx¸àÀxÀ¼UüÁ÷¢3A1–y A©?A¡öB/¤BŸ®Â£4éBŸœ(Bƒ $§#™B¦ózQh€ Unfortunately, it was an obstructed pass so the signal wasn't strong enough to decode any others. This is the first time I've received a satellite packet, so pretty excited about that. Are the contents of the above at all useful? 73,RayKN2K -----Original Message----- From: Rizwan Merchant kommandantdrake@gmail.com To: Pete vk2pet vk2pet@internode.on.net Cc: Amsat - BBs amsat-bb@amsat.org; mail@mike-rupprecht.de Sent: Sat, Feb 6, 2021 12:47 am Subject: [AMSAT-BB] Re: CAPE-3 Updates and iGate Request
Copy of the iGated packet we got an hour ago-ish: W5UL-11>KF5BNL-7,WIDE2-2,qAO,W7KKE-13:*EMAIL cape.cubesats@gmail.com 3844, 3844, 3848, -110, 0, 0, 14, 13, 14, 3820, 108, 18, 17, 1, 1, 11, 40
Sincerely,Rizwan Merchant KF5BNL
On Fri, Feb 5, 2021 at 11:45 PM Rizwan Merchant kommandantdrake@gmail.com wrote:
Hello all, Sorry I fell off the face of the Earth with emails. It's been a hectic time with moving into a new house and making regular trips between Louisiana and Texas to support the CAPE-3 Mission. Anyway let me provide a few quick answers: 1.) We are expecting UHF APRS on 437.325, the same as what our FSK and AX.25 packets are coming across on. 2.) From what I can tell, our NORAD ID is 47309. 3.) Currently we are having some issues commanding CAPE-3 from our University lab, so once we are able to transmit commands, we'll be able to set the APRS emails to come across more often, and begin experimenting the tweeting function to see if it works as we intended. I'd like to thank everyone who's helped so far! We got our first email packet from W7KKE-13 earlier this evening. Sincerely,Rizwan Merchant KF5BNL
On Wed, Feb 3, 2021 at 5:43 PM Pete vk2pet vk2pet@internode.on.net wrote:
Hi Every one, Does anyone have GNU radio flow chart all ready setup for igating CAPE-3 uhf aprs? I have a b100 that I'm happy to use to get the packets of CAPE-3. Located in SE Australia. Pete VK2PET. On 4/02/2021 8:17 am, Mark Jessop wrote:
No, it is not a 'standard' 70cm APRS frequency - that's going to vary from country to country, and would be outside of the satellite segment anyway. CAPE-3 transmits on 437.325 MHz. The SatNOGS network is getting packets fairly regularly: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&a... 73 Mark VK5QI On Thu, Feb 4, 2021 at 12:14 AM Lynn W Deffenbaugh (Mr) KJ4ERJ@arrl.net wrote:
For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 2/2/2021 11:25 PM, Rizwan Merchant wrote:
Hello All, I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status. So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration. Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems. As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/%C2%A0we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting). 1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS. 2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out. Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions. Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well. Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :) 73 Sincerely, Rizwan Merchant KF5BNL -----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
This is the binary packet format I mentioned in a previous e-mail. When printed as ASCII text a lot of content will be lost, so probably not useful unfortunately.
I'm sure the CAPE-3 team will release the packet format for this soon so those who are interested will be able to do something with the data.
From the IARU Satellite Coordination Info Paper: "With the exception of control signals exchanged between earth command stations and space stations in the amateur-satellite service all amateur signals shall not be encoded for the purpose of obscuring their meaning. To meet this requirement, operators of satellites in the amateur-satellite service must publish full details of their modulation, encoding and telemetry formats and equations before launch."
Unfortunately the 'before launch' part rarely happens...
73 Mark VK5QI
On Sun, Feb 7, 2021 at 12:08 PM crohtun--- via AMSAT-BB amsat-bb@amsat.org wrote:
Here is a copy of the packet decoded during the pass over my station a few minutes ago:
1:Fm W5UL-11 To W5UL-1 <UI R Pid=F0 Len=200> [20:24:05R] [+++] CAPE-3 W5UL-1100010001B0000000Œ :˜ðkÄÿ“ÈЀ¬Øx¸àÀxÀ¼UüÁ÷¢3A1–y A©?A¡öB/¤BŸ®Â£4éBŸœ(Bƒ $§#™B¦ózQh€
Unfortunately, it was an obstructed pass so the signal wasn't strong enough to decode any others.
This is the first time I've received a satellite packet, so pretty excited about that. Are the contents of the above at all useful?
73, Ray KN2K
-----Original Message----- From: Rizwan Merchant kommandantdrake@gmail.com To: Pete vk2pet vk2pet@internode.on.net Cc: Amsat - BBs amsat-bb@amsat.org; mail@mike-rupprecht.de Sent: Sat, Feb 6, 2021 12:47 am Subject: [AMSAT-BB] Re: CAPE-3 Updates and iGate Request
Copy of the iGated packet we got an hour ago-ish:
W5UL-11>KF5BNL-7,WIDE2-2,qAO,W7KKE-13:*EMAIL cape.cubesats@gmail.com 3844, 3844, 3848, -110, 0, 0, 14, 13, 14, 3820, 108, 18, 17, 1, 1, 11, 40
Sincerely, Rizwan Merchant KF5BNL
On Fri, Feb 5, 2021 at 11:45 PM Rizwan Merchant kommandantdrake@gmail.com wrote:
Hello all,
Sorry I fell off the face of the Earth with emails. It's been a hectic time with moving into a new house and making regular trips between Louisiana and Texas to support the CAPE-3 Mission. Anyway let me provide a few quick answers:
1.) We are expecting UHF APRS on 437.325, the same as what our FSK and AX.25 packets are coming across on.
2.) From what I can tell, our NORAD ID is 47309.
3.) Currently we are having some issues commanding CAPE-3 from our University lab, so once we are able to transmit commands, we'll be able to set the APRS emails to come across more often, and begin experimenting the tweeting function to see if it works as we intended.
I'd like to thank everyone who's helped so far! We got our first email packet from W7KKE-13 earlier this evening.
Sincerely, Rizwan Merchant KF5BNL
On Wed, Feb 3, 2021 at 5:43 PM Pete vk2pet vk2pet@internode.on.net wrote:
Hi Every one, Does anyone have GNU radio flow chart all ready setup for igating CAPE-3 uhf aprs? I have a b100 that I'm happy to use to get the packets of CAPE-3. Located in SE Australia. Pete VK2PET. On 4/02/2021 8:17 am, Mark Jessop wrote:
No, it is not a 'standard' 70cm APRS frequency - that's going to vary from country to country, and would be outside of the satellite segment anyway.
CAPE-3 transmits on 437.325 MHz.
The SatNOGS network is getting packets fairly regularly: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&a...
73 Mark VK5QI
On Thu, Feb 4, 2021 at 12:14 AM Lynn W Deffenbaugh (Mr) KJ4ERJ@arrl.net wrote:
For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 2/2/2021 11:25 PM, Rizwan Merchant wrote:
Hello All,
I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status.
So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration.
Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems.
As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting).
1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS.
2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out.
Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions.
Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well.
Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :)
73
Sincerely, Rizwan Merchant KF5BNL
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Hi Ray,
That packet is in "KISS" format. So the text copy is not much use. If you like to let me know how you are receiving it, I can give you instructions on how to record it and show some useful data on Mike's decoder program.
73, Terry Osborne ZL2BAC
On 7/02/2021 2:38 pm, crohtun--- via AMSAT-BB wrote:
Here is a copy of the packet decoded during the pass over my station a few minutes ago:
1:Fm W5UL-11 To W5UL-1 <UI R Pid=F0 Len=200> [20:24:05R] [+++] CAPE-3 W5UL-1100010001B0000000Œ :˜ðkÄÿ“ÈЀ¬Øx¸àÀxÀ¼UüÁ÷¢3A1–y A©?A¡öB/¤BŸ®Â£4éBŸœ(Bƒ$§#™B¦ózQh€
Unfortunately, it was an obstructed pass so the signal wasn't strong enough to decode any others.
This is the first time I've received a satellite packet, so pretty excited about that. Are the contents of the above at all useful?
73, Ray KN2K
-----Original Message----- From: Rizwan Merchant kommandantdrake@gmail.com To: Pete vk2pet vk2pet@internode.on.net Cc: Amsat - BBs amsat-bb@amsat.org; mail@mike-rupprecht.de Sent: Sat, Feb 6, 2021 12:47 am Subject: [AMSAT-BB] Re: CAPE-3 Updates and iGate Request
Copy of the iGated packet we got an hour ago-ish:
W5UL-11>KF5BNL-7,WIDE2-2,qAO,W7KKE-13:*EMAIL cape.cubesats@gmail.com mailto:cape.cubesats@gmail.com 3844, 3844, 3848, -110, 0, 0, 14, 13, 14, 3820, 108, 18, 17, 1, 1, 11, 40
Sincerely, Rizwan Merchant KF5BNL
On Fri, Feb 5, 2021 at 11:45 PM Rizwan Merchant <kommandantdrake@gmail.com mailto:kommandantdrake@gmail.com> wrote:
Hello all, Sorry I fell off the face of the Earth with emails. It's been a hectic time with moving into a new house and making regular trips between Louisiana and Texas to support the CAPE-3 Mission. Anyway let me provide a few quick answers: 1.) We are expecting UHF APRS on 437.325, the same as what our FSK and AX.25 packets are coming across on. 2.) From what I can tell, our NORAD ID is 47309. 3.) Currently we are having some issues commanding CAPE-3 from our University lab, so once we are able to transmit commands, we'll be able to set the APRS emails to come across more often, and begin experimenting the tweeting function to see if it works as we intended. I'd like to thank everyone who's helped so far! We got our first email packet from W7KKE-13 earlier this evening. Sincerely, Rizwan Merchant KF5BNL On Wed, Feb 3, 2021 at 5:43 PM Pete vk2pet <vk2pet@internode.on.net <mailto:vk2pet@internode.on.net>> wrote: Hi Every one, Does anyone have GNU radio flow chart all ready setup for igating CAPE-3 uhf aprs? I have a b100 that I'm happy to use to get the packets of CAPE-3. Located in SE Australia. Pete VK2PET. On 4/02/2021 8:17 am, Mark Jessop wrote:No, it is not a 'standard' 70cm APRS frequency - that's going to vary from country to country, and would be outside of the satellite segment anyway. CAPE-3 transmits on 437.325 MHz. The SatNOGS network is getting packets fairly regularly: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&failed=0&norad=47309&observer=&station=&start=&end= <https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&failed=0&norad=47309&observer=&station=&start=&end=> 73 Mark VK5QI On Thu, Feb 4, 2021 at 12:14 AM Lynn W Deffenbaugh (Mr) <KJ4ERJ@arrl.net <mailto:KJ4ERJ@arrl.net>> wrote: For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 2/2/2021 11:25 PM, Rizwan Merchant wrote:Hello All, I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status. So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration. Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems. As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/ <https://www.satblog.info/new-cape-3-beacons/> we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting). 1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS. 2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out. Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions. Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work. So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well. Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :) 73 Sincerely, Rizwan Merchant KF5BNL ----------------------------------------------------------- Sent via AMSAT-BB(a)amsat.org <http://amsat.org/>. 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! View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org <https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org> To unsubscribe send an email to amsat-bb-leave(a)amsat.org <http://amsat.org/> Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org <https://mailman.amsat.org/>----------------------------------------------------------- Sent via AMSAT-BB(a)amsat.org <http://amsat.org/>. 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! View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org <https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org> To unsubscribe send an email to amsat-bb-leave(a)amsat.org <http://amsat.org/> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org <https://mailman.amsat.org/> ----------------------------------------------------------- Sent via AMSAT-BB(a)amsat.org <http://amsat.org/>. 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! View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org <https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org> To unsubscribe send an email to amsat-bb-leave(a)amsat.org <http://amsat.org/> Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org <https://mailman.amsat.org/>----------------------------------------------------------- Sent via AMSAT-BB(a)amsat.org <http://amsat.org/>. 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! View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org <https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org> To unsubscribe send an email to amsat-bb-leave(a)amsat.org <http://amsat.org/> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org <https://mailman.amsat.org/>
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org https://mailman.amsat.org/
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Terry,This was displayed on the UZ7HO soundcard monitor. I have the Easyterm and APRSIS32 clients that I use with the soundcard, but no other packet software. And neither client was running during the pass, just the soundcard. My transceiver is an IC 9700 set with the same parameters used for APRS and Doppler controlled by SatPC32.Ray
Sent from the all new Aol app for iOS
On Saturday, February 6, 2021, 10:24 PM, Wendy and Terry Osborne wandtosborne@gmail.com wrote:
Hi Ray,
That packet is in "KISS" format. So the text copy is not much use. If you like to let me know how you are receiving it, I can give you instructions on how to record it and show some useful data on Mike's decoder program.
73, Terry Osborne ZL2BAC
On 7/02/2021 2:38 pm, crohtun--- via AMSAT-BB wrote:
Here is a copy of the packet decoded during the pass over my station a few minutes ago: 1:Fm W5UL-11 To W5UL-1 <UI R Pid=F0 Len=200> [20:24:05R] [+++] CAPE-3 W5UL-1100010001B0000000Œ :˜ðkÄÿ“ÈЀ¬Øx¸àÀxÀ¼UüÁ÷¢3A1–y A©?A¡öB/¤BŸ®Â£4éBŸœ(Bƒ $§#™B¦ózQh€ Unfortunately, it was an obstructed pass so the signal wasn't strong enough to decode any others. This is the first time I've received a satellite packet, so pretty excited about that. Are the contents of the above at all useful? 73, Ray KN2K -----Original Message----- From: Rizwan Merchant kommandantdrake@gmail.com To: Pete vk2pet vk2pet@internode.on.net Cc: Amsat - BBs amsat-bb@amsat.org; mail@mike-rupprecht.de Sent: Sat, Feb 6, 2021 12:47 am Subject: [AMSAT-BB] Re: CAPE-3 Updates and iGate Request
Copy of the iGated packet we got an hour ago-ish: W5UL-11>KF5BNL-7,WIDE2-2,qAO,W7KKE-13:*EMAIL cape.cubesats@gmail.com 3844, 3844, 3848, -110, 0, 0, 14, 13, 14, 3820, 108, 18, 17, 1, 1, 11, 40
Sincerely, Rizwan Merchant KF5BNL
On Fri, Feb 5, 2021 at 11:45 PM Rizwan Merchant kommandantdrake@gmail.com wrote:
Hello all, Sorry I fell off the face of the Earth with emails. It's been a hectic time with moving into a new house and making regular trips between Louisiana and Texas to support the CAPE-3 Mission. Anyway let me provide a few quick answers: 1.) We are expecting UHF APRS on 437.325, the same as what our FSK and AX.25 packets are coming across on. 2.) From what I can tell, our NORAD ID is 47309. 3.) Currently we are having some issues commanding CAPE-3 from our University lab, so once we are able to transmit commands, we'll be able to set the APRS emails to come across more often, and begin experimenting the tweeting function to see if it works as we intended. I'd like to thank everyone who's helped so far! We got our first email packet from W7KKE-13 earlier this evening. Sincerely, Rizwan Merchant KF5BNL
On Wed, Feb 3, 2021 at 5:43 PM Pete vk2pet vk2pet@internode.on.net wrote:
Hi Every one, Does anyone have GNU radio flow chart all ready setup for igating CAPE-3 uhf aprs? I have a b100 that I'm happy to use to get the packets of CAPE-3. Located in SE Australia. Pete VK2PET. On 4/02/2021 8:17 am, Mark Jessop wrote:
No, it is not a 'standard' 70cm APRS frequency - that's going to vary from country to country, and would be outside of the satellite segment anyway. CAPE-3 transmits on 437.325 MHz. The SatNOGS network is getting packets fairly regularly: https://network.satnogs.org/observations/?future=0&bad=0&unknown=0&a... 73 Mark VK5QI On Thu, Feb 4, 2021 at 12:14 AM Lynn W Deffenbaugh (Mr) KJ4ERJ@arrl.net wrote:
For those of us not tracking the full details of the CAPE-3 satellite, what is the specific UHF frequency on which you'd like IGates to listen for packets? And also if you can include the satellite catalog number, it would assist in making sure I'm listening at the right pass times for my QTH. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 2/2/2021 11:25 PM, Rizwan Merchant wrote:
Hello All, I wanted to give a quick update on CAPE-3, and where we are in mission goals. However, first I'd like to thank everyone who has taken part in helping track CAPE-3 and gather data for us to analyze the state of the satellite in orbit. Without the wonderful support of the community, we might be still trying to capture enough information to determine our status. So from all reports, it seems CAPE-3 is indeed healthy in orbit. Our power system seems to be working as intended and UHF transmitters seem healthy. However, we're suspecting the VHF radio is dead on arrival. We've not seen any indication of it functioning in orbit, which aligns with a fear we had prior to integration. Using this information, our team is now devising plans to begin testing individual subsystems on the satellite to gauge the health of those. This might take a few more weeks to validate and provide an update on what capabilities we can still carry out, as we update our ground systems. As reported in DK3WN's blog: https://www.satblog.info/new-cape-3-beacons/%C2%A0we have seen reports of CAPE-3 attempting to email home with health data. However we have come across two issues with the APRS services our satellite performs (email and tweeting). 1.) Our satellite from what we can tell only has a functional UHF radio, and is able to transmit the packet correctly. However, we don't believe CAPE-3 will find many iGates listening on UHF frequencies to gate packets for it. If there are any operators out there with iGates I'd like to humbly request help in setting up a few UHF iGate stations in different areas to help gate our packets back into the APRS. 2.) We are not able to validate the email packets will reliably come out once every hour and half as we initially believed. Due to the way we designed the satellite, the APRS functions will be transmitted on whichever radio our satellite thinks is active. At current, CAPE-3 thinks it has a functional UHF and VHF, so there will most likely be many failed attempts made on VHF. We're hoping to gather enough data from email packet timestamps to figure out a new frequency of when email UHF packets will be sent out. Once we're further in our testing and verification phase, we'll make attempts to shut down the VHF radio on the satellite to improve reliability of these functions. Note these two functions are supported by custom software we're using to check APRS-IS feeds for our packets to email and tweet out. I'm planning to make a release of information to allow the community to test out this server, and am hoping to make that information public by this weekend. I'm running a few tests to make sure things still work as intended on the ground end in my free time in the evenings after work.
So if anyone is able to switch their iGates, or make a UHF iGate to help track CAPE-3 email packets, we'd be really grateful for the help! We've turned on one at our University as well. Thanks all, I apologize if this email was wordy, but I felt it necessary to be fully transparent on what we're planning to do to help you help us with our mission goals. :) 73 Sincerely, Rizwan Merchant KF5BNL -----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org -----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-----------------------------------------------------------
Sent via AMSAT-BB(a)amsat.org. 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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
participants (9)
-
crohtun -
crohtun＠aol.com
-
Fabian Schneider -
Lynn W Deffenbaugh (Mr) -
mail＠mike-rupprecht.de -
Mark Jessop -
Pete vk2pet -
Rizwan Merchant -
Wendy and Terry Osborne