Interesting! Didn't know that data was available on line. Is there a more detailed presentation of the data in, say, a spreadsheet for a greater period of time than what is presented? This would be very helpful in performing any detailed analysis. Is all of the telemetry presented on the web page? All data would be valuable in trying to make any correlations.
Where in the receive chain is the RSSI measured? Has an attempt been made yet to transmit a strong signal (modulated or unmodulated) during an overhead pass to try to 'nudge the needle' on the RSSI meter? Perhaps successively stronger transmissions could be made to see at what power level any change occurs in the RSSI without applying too much power. I recall someone mentioning approaching an EME operator to attempt transmitting at AO-95 with significantly more power than normal.
Why does the 'Battery I32C' indicate 'FAIL' (although I see that this is the same for the other FOX satellites)?
73,
Mac Cody / AE5PH
On 12/17/18 1:02 PM, H. Stephen Nipper wrote:
Mac, you can look at the data coming down from the satellite and maybe answer some of the questions that you asked. To my untrained eye it appears that the solar panels are all working. I am sure that the team understands that data and what it means more than me.
http://www.amsat.org/tlm/health.php?id=3&port=
So if you look at RSSI line you can see the receiver. Click on it. It's flat line. http://www.amsat.org/tlm/graph.php?sat=3&field=RSSI&raw=conv&res...
On Mon, Dec 17, 2018 at 10:30 AM Mac A. Cody <maccody@att.net mailto:maccody@att.net> wrote:
I'm sure that this is being considered, but I'll extend the thought anyway: If there has been a collision that may have damaged or sheared off the RX antenna, could other damage have occurred that might be identifiable via telemetry? What I'm thinking of is possible damage to one or more solar cells. Would damage, perhaps resulting is reduced current flow or voltage levels, be discernible through the telemetry? Are there other items of the surface of AO-95 that, if damaged, might reveal that damage through telemetry. Thanks to all the volunteers that have worked so hard to make the FOX series an outstanding success! 73, Mac Cody / AE5PH On 12/16/18 10:48 PM, Jerry Buxton wrote: > Hi Francis, > > That is one thing we are looking into, handily I am well acquainted with > the ExseedSat team lead and since we were in the deployer next to each > other and performing the integration together we have discussed the > possibility that we got to be too close friends somehow and are still > that way or perhaps remained too close even to the point of antenna > deploy and perhaps interfered with each other's deploy. TLE indicated > separation is perhaps the only way to guesstimate that though. If it > gives us something to maybe model or relate to past missions, we might > be able to infer that a possible cause was that we may have been close > for a while up to and including our antenna deploy times and something > may have happened as a result of that. It would at least provide one > possible path to follow in looking for causes and maybe (and I mean > MAYBE) a solution. > Keep on watching for clues, thanks! > > Jerry Buxton, NØJY > > On 12/16/2018 15:30, Francis Geraci wrote: >> First off, I do not want to "2nd guess" the Engineering team. >> >> JUst read the "post" that AO-95 was still very close to another "object". >> >> I just was wondering, if AO-95 is TOO close to another "object", maybe >> "object" is "blocking" the RX antenna, or did RX antenna get "knocked" off ? >> >> Opinions ? Everybody has them. HiHi >> >> Francis - W1FXX >> _______________________________________________ >> Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! >> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb >> >> > _______________________________________________ > Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! > Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb _______________________________________________ Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb-- Stephen Nipper Boise, Idaho N7DJX
Mac,
All of the telemetry can be downloaded and analyzed thoroughly through FoxTelem. There are a number of graphing and mapping features built in and all values can be exported to .csv files for analysis in other software.
73,
Paul, N8HM
On Mon, Dec 17, 2018 at 14:51 Mac A. Cody maccody@att.net wrote:
Interesting! Didn't know that data was available on line. Is there a more detailed presentation of the data in, say, a spreadsheet for a greater period of time than what is presented? This would be very helpful in performing any detailed analysis. Is all of the telemetry presented on the web page? All data would be valuable in trying to make any correlations.
Where in the receive chain is the RSSI measured? Has an attempt been made yet to transmit a strong signal (modulated or unmodulated) during an overhead pass to try to 'nudge the needle' on the RSSI meter? Perhaps successively stronger transmissions could be made to see at what power level any change occurs in the RSSI without applying too much power. I recall someone mentioning approaching an EME operator to attempt transmitting at AO-95 with significantly more power than normal.
Why does the 'Battery I32C' indicate 'FAIL' (although I see that this is the same for the other FOX satellites)?
73,
Mac Cody / AE5PH
On 12/17/18 1:02 PM, H. Stephen Nipper wrote:
Mac, you can look at the data coming down from the satellite and maybe answer some of the questions that you asked. To my untrained eye it appears that the solar panels are all working. I am sure that the team understands that data and what it means more than me.
http://www.amsat.org/tlm/health.php?id=3&port=
So if you look at RSSI line you can see the receiver. Click on it. It's flat line.
http://www.amsat.org/tlm/graph.php?sat=3&field=RSSI&raw=conv&res...
On Mon, Dec 17, 2018 at 10:30 AM Mac A. Cody <maccody@att.net mailto:maccody@att.net> wrote:
I'm sure that this is being considered, but I'll extend the thought anyway: If there has been a collision that may have damaged or sheared offthe
RX antenna, could other damage have occurred that might be identifiable via telemetry? What I'm thinking of is possible damage to one ormore
solar cells. Would damage, perhaps resulting is reduced current flow or voltage levels, be discernible through the telemetry? Are there other items of the surface of AO-95 that, if damaged, might reveal that damage through telemetry. Thanks to all the volunteers that have worked so hard to make the FOX series an outstanding success! 73, Mac Cody / AE5PH On 12/16/18 10:48 PM, Jerry Buxton wrote: > Hi Francis, > > That is one thing we are looking into, handily I am well acquainted with > the ExseedSat team lead and since we were in the deployer next to each > other and performing the integration together we have discussed the > possibility that we got to be too close friends somehow and are still > that way or perhaps remained too close even to the point of antenna > deploy and perhaps interfered with each other's deploy. TLE indicated > separation is perhaps the only way to guesstimate that though. If it > gives us something to maybe model or relate to past missions, we might > be able to infer that a possible cause was that we may have been close > for a while up to and including our antenna deploy times and something > may have happened as a result of that. It would at least provide one > possible path to follow in looking for causes and maybe (and I mean > MAYBE) a solution. > Keep on watching for clues, thanks! > > Jerry Buxton, NØJY > > On 12/16/2018 15:30, Francis Geraci wrote: >> First off, I do not want to "2nd guess" the Engineering team. >> >> JUst read the "post" that AO-95 was still very close to another "object". >> >> I just was wondering, if AO-95 is TOO close to another "object", maybe >> "object" is "blocking" the RX antenna, or did RX antenna get "knocked" off ? >> >> Opinions ? Everybody has them. HiHi >> >> Francis - W1FXX >> _______________________________________________ >> Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! >> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb >> >> > _______________________________________________ > Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! > Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb _______________________________________________ Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! Subscription settings:http://www.amsat.org/mailman/listinfo/amsat-bb
-- Stephen Nipper Boise, Idaho N7DJX
Sent via AMSAT-BB@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! Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
Thanks, Paul!
Latest version of FoxTelem downloaded and installed. I've downloaded the data from the server and I'm now exploring and analyzing.
73,
Mac Cody / AE5PH
On 12/17/18 2:02 PM, Paul Stoetzer wrote:
Mac,
All of the telemetry can be downloaded and analyzed thoroughly through FoxTelem. There are a number of graphing and mapping features built in and all values can be exported to .csv files for analysis in other software.
73,
Paul, N8HM
On Mon, Dec 17, 2018 at 14:51 Mac A. Cody <maccody@att.net mailto:maccody@att.net> wrote:
Interesting! Didn't know that data was available on line. Is there a more detailed presentation of the data in, say, a spreadsheet for a greater period of time than what is presented? This would be very helpful in performing any detailed analysis. Is all of the telemetry presented on the web page? All data would be valuable in trying to make any correlations. Where in the receive chain is the RSSI measured? Has an attempt been made yet to transmit a strong signal (modulated or unmodulated) during an overhead pass to try to 'nudge the needle' on the RSSI meter? Perhaps successively stronger transmissions could be made to see at what power level any change occurs in the RSSI without applying too much power. I recall someone mentioning approaching an EME operator to attempt transmitting at AO-95 with significantly more power than normal. Why does the 'Battery I32C' indicate 'FAIL' (although I see that this is the same for the other FOX satellites)? 73, Mac Cody / AE5PH On 12/17/18 1:02 PM, H. Stephen Nipper wrote: > Mac, you can look at the data coming down from the satellite and maybe > answer some of the questions that you asked. To my untrained eye it > appears that the solar panels are all working. I am sure that the > team understands that data and what it means more than me. > > http://www.amsat.org/tlm/health.php?id=3&port= > > So if you look at RSSI line you can see the receiver. Click on it. > It's flat line. > http://www.amsat.org/tlm/graph.php?sat=3&field=RSSI&raw=conv&reset=0&uptime=0&rows=100&port=8080 > > On Mon, Dec 17, 2018 at 10:30 AM Mac A. Cody <maccody@att.net <mailto:maccody@att.net> > <mailto:maccody@att.net <mailto:maccody@att.net>>> wrote: > > I'm sure that this is being considered, but I'll extend the > thought anyway: > If there has been a collision that may have damaged or sheared off the > RX antenna, could other damage have occurred that might be > identifiable > via telemetry? What I'm thinking of is possible damage to one or more > solar cells. Would damage, perhaps resulting is reduced current flow > or voltage levels, be discernible through the telemetry? Are > there other > items of the surface of AO-95 that, if damaged, might reveal that > damage > through telemetry. > > Thanks to all the volunteers that have worked so hard to make the FOX > series an outstanding success! > > 73, > > Mac Cody / AE5PH > > > On 12/16/18 10:48 PM, Jerry Buxton wrote: > > Hi Francis, > > > > That is one thing we are looking into, handily I am well > acquainted with > > the ExseedSat team lead and since we were in the deployer next > to each > > other and performing the integration together we have discussed the > > possibility that we got to be too close friends somehow and are > still > > that way or perhaps remained too close even to the point of antenna > > deploy and perhaps interfered with each other's deploy. TLE > indicated > > separation is perhaps the only way to guesstimate that though. > If it > > gives us something to maybe model or relate to past missions, we > might > > be able to infer that a possible cause was that we may have been > close > > for a while up to and including our antenna deploy times and > something > > may have happened as a result of that. It would at least > provide one > > possible path to follow in looking for causes and maybe (and I mean > > MAYBE) a solution. > > Keep on watching for clues, thanks! > > > > Jerry Buxton, NØJY > > > > On 12/16/2018 15:30, Francis Geraci wrote: > >> First off, I do not want to "2nd guess" the Engineering team. > >> > >> JUst read the "post" that AO-95 was still very close to another > "object". > >> > >> I just was wondering, if AO-95 is TOO close to another > "object", maybe > >> "object" is "blocking" the RX antenna, or did RX antenna get > "knocked" off ? > >> > >> Opinions ? Everybody has them. HiHi > >> > >> Francis - W1FXX > >> _______________________________________________ > >> Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@amsat.org> <mailto:AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! > >> Subscription settings: > http://www.amsat.org/mailman/listinfo/amsat-bb > >> > >> > > _______________________________________________ > > Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@amsat.org> <mailto:AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! > > Subscription settings: > http://www.amsat.org/mailman/listinfo/amsat-bb > > > _______________________________________________ > Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@amsat.org> <mailto:AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! > Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb > > > > -- > Stephen Nipper > Boise, Idaho > N7DJX > > _______________________________________________ Sent via AMSAT-BB@amsat.org <mailto:AMSAT-BB@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! Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
Battery I2C shows FAIL because on some of the early Fox-1s, there was an issue with the telemetry ADC on the battery board. So IHU sees no activity on the Battery I2C line and reports it as failed, it doesn't really have a way to tell that it's the chip at the other end and not the line. We did not have time to isolate and fix it between builds of Fox-1A, C, and D as they came in a string in 2014 and 2015. Fox-1B got manifested late(r) enough that we solved and applied the fix on her build. Fox-1E should be good as well.
Jerry Buxton, NØJY
On 12/17/2018 13:50, Mac A. Cody wrote:
Why does the 'Battery I32C' indicate 'FAIL' (although I see that this is the same for the other FOX satellites)?
participants (3)
-
Jerry Buxton -
Mac A. Cody -
Paul Stoetzer