Ultima tripulacion del Endeavour , foto NASA despues de aterrizar

>
>
> Todo un hito.....hay videos de la vuelta a tierra y el aterrizaje?
>
> El 1 de junio de 2011 19:54, Edgar J. De Cleene <[hidden email]>escribió:
>
>>
>>
>>
>
>
> --
> =================================================
> Germán S. Arduino  <gsa @ arsol.net>   Twitter: garduino
> Arduino Software & Web Hosting   http://www.arduinosoftware.com
> PasswordsPro  http://www.passwordspro.com
> =================================================
>
>  
>

>
>
> Que facil que se destruyen las cosas por arrogancia, no?  Mientras tanto,
> aca vi unas noticias lindas...
>
> 1.  Nueva sonda a Jupiter, y con paneles solares porque la van a poner en
> una orbita polar asi que nunca va a estar a la sombra.
>
> http://en.wikipedia.org/wiki/Juno_%28spacecraft%29
>
> 2.  Tambien en 2016 llega New Horizons a Pluton.
>
> http://en.wikipedia.org/wiki/New_Horizons
>
> 3.  Lo que vale hacer las cosas bien... miren los Voyagers con sus ~1700
> bytes de RAM...
>
> http://voyager.jpl.nasa.gov/
>
> 4.  O que tal Opportunity (Spirit palmo durante el invierno marciano),
> llevan 5 años andando y tenian una garantia de 90 dias...
>
> http://marsrover.nasa.gov/home/
>
> 5.  Y el que sigue...
>
> http://www.nasa.gov/mission_pages/msl/index.html
>
> 6.  Ah, y de paso, que es esta aparente particula nueva?  Estan ahi de
> decir que hay un descubrimiento nuevo... saldra?
>
> http://resonaances.blogspot.com/2011/05/cdf-wjj-bump-is-almost-5-sigma.html
>
>
> http://blogs.discovermagazine.com/cosmicvariance/2011/05/30/anomaly-at-the-tevatron-might-be-something-real/
>
>
> http://www.newscientist.com/blogs/shortsharpscience/2011/06/tevatrons-mystery-signal-grows.html
>
> Estaria bueno que no cerraran el Tevatron ahora en unos meses...
>
>
> 2011/6/1 Germán Arduino <[hidden email]>
>
>>
>>
>> Todo un hito.....hay videos de la vuelta a tierra y el aterrizaje?
>>
>> El 1 de junio de 2011 19:54, Edgar J. De Cleene <[hidden email]>escribió:
>>
>>>
>>>
>>>
>>
>>
>> --
>> =================================================
>> Germán S. Arduino  <gsa @ arsol.net>   Twitter: garduino
>> Arduino Software & Web Hosting   http://www.arduinosoftware.com
>> PasswordsPro  http://www.passwordspro.com
>> =================================================
>>
>>
>  
>

>
>
> El 1 de junio de 2011 21:08, Andres Valloud <[hidden email]>
> escribió:
>>
>>
>>
>> 3.  Lo que vale hacer las cosas bien... miren los Voyagers con sus ~1700
>> bytes de RAM...
>>
>> http://voyager.jpl.nasa.gov/
>
> Empecé por este, por lo de los 1.7MB (o casi) de RAM, pero aún no encontré
> la referencia,
> Me encantaría saber más sobre el hard/soft que las controlaba, tenés algún
> link, dato, etc (con una búsqueda rápida en la página aún no encontré nada)?
>

> Que facil que se destruyen las cosas por arrogancia, no?  Mientras tanto, aca
> vi unas noticias lindas...
>
> 1.  Nueva sonda a Jupiter, y con paneles solares porque la van a poner en una
> orbita polar asi que nunca va a estar a la sombra.
>
> http://en.wikipedia.org/wiki/Juno_%28spacecraft%29
>
> 2.  Tambien en 2016 llega New Horizons a Pluton.
>
> http://en.wikipedia.org/wiki/New_Horizons
>
> 3.  Lo que vale hacer las cosas bien... miren los Voyagers con sus ~1700 bytes
> de RAM...
>
> http://voyager.jpl.nasa.gov/
>
> 4.  O que tal Opportunity (Spirit palmo durante el invierno marciano), llevan
> 5 años andando y tenian una garantia de 90 dias...
>
> http://marsrover.nasa.gov/home/
>
> 5.  Y el que sigue...
>
> http://www.nasa.gov/mission_pages/msl/index.html
>
> 6.  Ah, y de paso, que es esta aparente particula nueva?  Estan ahi de decir
> que hay un descubrimiento nuevo... saldra?
>
> http://resonaances.blogspot.com/2011/05/cdf-wjj-bump-is-almost-5-sigma.html
>
> http://blogs.discovermagazine.com/cosmicvariance/2011/05/30/anomaly-at-the-tev
> atron-might-be-something-real/
>
> http://www.newscientist.com/blogs/shortsharpscience/2011/06/tevatrons-mystery-
> signal-grows.html
>
> Estaria bueno que no cerraran el Tevatron ahora en unos meses...
>
> Gracias Andres, algunos de estos no los conocia.
> Edgar

> El 1 de junio de 2011 21:08, Andres Valloud <[hidden email]>
> escribió:
>  
>
> 3.  Lo que vale hacer las cosas bien... miren los Voyagers con sus ~1700 bytes
> de RAM...
>
> http://voyager.jpl.nasa.gov/
>
>
>
> Empecé por este, por lo de los 1.7MB (o casi) de RAM, pero aún no encontré la
> referencia,
>
> Me encantaría saber más sobre el hard/soft que las controlaba, tenés algún
> link, dato, etc (con una búsqueda rápida en la página aún no encontré nada)?
>
> No se si eran estos los que tenina programación en USCD Pascal ?
> Que solo podia tener 77 archivos ?
>
> Edgar
>
>

>
>
> El 1 de junio de 2011 21:08, Andres Valloud <*[hidden email]*>
> escribió:
>
>
> 3.  Lo que vale hacer las cosas bien... miren los Voyagers con sus ~1700
> bytes de RAM...
>
> *http://voyager.jpl.nasa.gov/
> *
>
>
>
> Empecé por este, por lo de los 1.7MB (o casi) de RAM, pero aún no encontré
> la referencia,
>
> Me encantaría saber más sobre el hard/soft que las controlaba, tenés algún
> link, dato, etc (con una búsqueda rápida en la página aún no encontré nada)?
>
> No se si eran estos los que tenina programación en USCD Pascal ?
> Que solo podia tener 77 archivos ?
>
> Edgar
>
>
>
>  
>

> Ahhh, mentira, me acordaba mal de los 1.7kb.  En realidad dice que son como
> 68kb (32K words).  Igual... que joda...
>
> http://voyager.jpl.nasa.gov/faq.html
>
>
> Question: What kind of computers are used on the Voyager spacecraft?
>
>  
>
> Answer: There are three different computer types on the Voyager spacecraft and
> there are two of each kind. Total number of words among the six computers is
> about 32K.
>
> Computer Command System (CCS) - 18-bit word, interrupt type processors (2)
> with 4096 words each of plated wire, non-volatile memory.
>
> Flight Data System (FDS) - 16-bit word machine (2) with modular memories and
> 8198 words each
>
> Attitude and Articulation Control System (AACS) - 18-bit word machines (2)
> with 4096 words each.
>
> According to my calculations, that's a total of about 68KB, or small potatoes
> compared to today's microprocessors. We probably could perform all functions
> with one of today's boards and still have room for solid state data storage
> and much more fault detection software. We would still need a second unit for
> redundancy. Today's microprocessors are also much faster than the chips used
> on Voyager and a comparative system would use less electrical power. On the
> other hand, software might be more complicated as opposed to that used in an
> interrupt type system, but it would be much more capable and more flexible.
>
> Let's look closer at the CCS. The CCS has two main functions: to carry out
> instructions from the ground to operate the spacecraft, and to be alert for a
> problem or malfunction and respond to it. Two identical 4096- word memories
> contain both fixed routines (about 2800 words) and a variable section (about
> 1290 words) for changing science sequences. The CCS issues commands to the
> AACS for movement of the scan platform or spacecraft maneuvers; to the FDS for
> changes in instrument configurations or telemetry rates and to numerous other
> subsystems within the spacecraft for specific actions. Fault-protection
> algorithms are also stored in the CCS, occupying roughly 10 percent of the CCS
> memory.
>
> The main functions of the FDS are to collect data from, and controls the
> operations of, the scientific instruments; and to format engineering and
> science data for on-board storage and/or real-time transmission. The FDS also
> keeps the spacecraft "time" and provides frequency references to the
> instruments and other spacecraft subsystems.
>
> The Voyager spacecraft computers are interrupt driven computer, similar to
> processors used in general purpose computers with a few special instructions
> for increased efficiency. The programming is a form of assembly language.
>
> There is no clock chip, as such, in the spacecraft. The "clock" is really a
> counter, based on one of several electronically generated frequencies. These
> frequencies, based on a reference, generated by a very stable oscillator, are
> converted and fed to different locations in the spacecraft as synchronization
> signals, timers, counters, etc. The "clock" signal is part of the information
> telemetered to the ground and it is with ground software that we convert to
> day of year, time of day Greenwich Mean Time.
>
> Voyager was built in-house at JPL; the computers were manufactured by General
> Electric to JPL specifications.
>
>
>
>
> Gracias Andres, referencias invaluables .
> Edgar

>
>
> Ahhh, mentira, me acordaba mal de los 1.7kb.  En realidad dice que son como
> 68kb (32K words).  Igual... que joda...
>
> *http://voyager.jpl.nasa.gov/faq.html
> *
>
> Question: What kind of computers are used on the Voyager spacecraft?
>
>
>
> Answer: There are three different computer types on the Voyager spacecraft
> and there are two of each kind. Total number of words among the six
> computers is about 32K.
>
> Computer Command System (CCS) - 18-bit word, interrupt type processors (2)
> with 4096 words each of plated wire, non-volatile memory.
>
> Flight Data System (FDS) - 16-bit word machine (2) with modular memories
> and 8198 words each
>
> Attitude and Articulation Control System (AACS) - 18-bit word machines (2)
> with 4096 words each.
>
> According to my calculations, that's a total of about 68KB, or small
> potatoes compared to today's microprocessors. We probably could perform all
> functions with one of today's boards and still have room for solid state
> data storage and much more fault detection software. We would still need a
> second unit for redundancy. Today's microprocessors are also much faster
> than the chips used on Voyager and a comparative system would use less
> electrical power. On the other hand, software might be more complicated as
> opposed to that used in an interrupt type system, but it would be much more
> capable and more flexible.
>
> Let's look closer at the CCS. The CCS has two main functions: to carry out
> instructions from the ground to operate the spacecraft, and to be alert for
> a problem or malfunction and respond to it. Two identical 4096- word
> memories contain both fixed routines (about 2800 words) and a variable
> section (about 1290 words) for changing science sequences. The CCS issues
> commands to the AACS for movement of the scan platform or spacecraft
> maneuvers; to the FDS for changes in instrument configurations or telemetry
> rates and to numerous other subsystems within the spacecraft for specific
> actions. Fault-protection algorithms are also stored in the CCS, occupying
> roughly 10 percent of the CCS memory.
>
> The main functions of the FDS are to collect data from, and controls the
> operations of, the scientific instruments; and to format engineering and
> science data for on-board storage and/or real-time transmission. The FDS
> also keeps the spacecraft "time" and provides frequency references to the
> instruments and other spacecraft subsystems.
>
> The Voyager spacecraft computers are interrupt driven computer, similar to
> processors used in general purpose computers with a few special instructions
> for increased efficiency. The programming is a form of assembly language.
>
> There is no clock chip, as such, in the spacecraft. The "clock" is really a
> counter, based on one of several electronically generated frequencies. These
> frequencies, based on a reference, generated by a very stable oscillator,
> are converted and fed to different locations in the spacecraft as
> synchronization signals, timers, counters, etc. The "clock" signal is part
> of the information telemetered to the ground and it is with ground software
> that we convert to day of year, time of day Greenwich Mean Time.
>
> Voyager was built in-house at JPL; the computers were manufactured by
> General Electric to JPL specifications.
>
>
>
>
> Gracias Andres, referencias invaluables .
> Edgar
>
>  
>