HacDC Spaceblimp 7 - Revision history

207.172.92.193: /* Project Description & Status */ nnnn

2018-05-19T14:49:27Z

Project Description & Status: nnnn

← Older revision		Revision as of 14:49, 19 May 2018
Line 50:		Line 50:

	The project has Technical, logistical and Educational goals which are described below. Spaceblimp 7 looks to add new components that weren’t part of HacDC’s previous six Spaceblimp launches. By forming a partnership with several other area makerspaces, volunteers, hackers and educators we are expanding our team and pooling resources. By expanding the project we aim to increase its visibility and benefit all the organizations involved as well as an increase fund-raising opportunities to help sustain all the partners/organizations and the project Spaceblimp in the long-term. This will also expose high school students to educational and technical resources outside of the school environment as well as giving all the participants the opportunity to share skills and interests to work together and learn from one another to achieve shared goals. Local area hackers and space enthusiasts will also benefit by being able to actively participate and develop skills in the design and launch of the payloads.		The project has Technical, logistical and Educational goals which are described below. Spaceblimp 7 looks to add new components that weren’t part of HacDC’s previous six Spaceblimp launches. By forming a partnership with several other area makerspaces, volunteers, hackers and educators we are expanding our team and pooling resources. By expanding the project we aim to increase its visibility and benefit all the organizations involved as well as an increase fund-raising opportunities to help sustain all the partners/organizations and the project Spaceblimp in the long-term. This will also expose high school students to educational and technical resources outside of the school environment as well as giving all the participants the opportunity to share skills and interests to work together and learn from one another to achieve shared goals. Local area hackers and space enthusiasts will also benefit by being able to actively participate and develop skills in the design and launch of the payloads.

	Project logistics include those necessary to achieve the technical goals, but also networking of area makerspaces and volunteers, outreach to local governments, funding sources and potential sponsors, coordination of project documentation and public exhibition of the project.

	Local area hackers, space enthusiasts, and community members have come together to share and learn new skills in the design, construction, and launch of the project.The sixth launch, Spaceblimp 6, reached 104,000ft. Spaceblimp 7 is being done in collaboration with Rockville Makerspace [http://rockvillesciencecenter.org/programs/studio-i-makerspace/] and Unallocated Space [https://www.unallocatedspace.org/].		Local area hackers, space enthusiasts, and community members have come together to share and learn new skills in the design, construction, and launch of the project.The sixth launch, Spaceblimp 6, reached 104,000ft. Spaceblimp 7 is being done in collaboration with Rockville Makerspace [http://rockvillesciencecenter.org/programs/studio-i-makerspace/] and Unallocated Space [https://www.unallocatedspace.org/].

207.172.92.193: /* Project Description & Status */ nnn

2018-05-19T14:47:16Z

Project Description & Status: nnn

← Older revision		Revision as of 14:47, 19 May 2018
Line 50:		Line 50:

	The project has Technical, logistical and Educational goals which are described below. Spaceblimp 7 looks to add new components that weren’t part of HacDC’s previous six Spaceblimp launches. By forming a partnership with several other area makerspaces, volunteers, hackers and educators we are expanding our team and pooling resources. By expanding the project we aim to increase its visibility and benefit all the organizations involved as well as an increase fund-raising opportunities to help sustain all the partners/organizations and the project Spaceblimp in the long-term. This will also expose high school students to educational and technical resources outside of the school environment as well as giving all the participants the opportunity to share skills and interests to work together and learn from one another to achieve shared goals. Local area hackers and space enthusiasts will also benefit by being able to actively participate and develop skills in the design and launch of the payloads.		The project has Technical, logistical and Educational goals which are described below. Spaceblimp 7 looks to add new components that weren’t part of HacDC’s previous six Spaceblimp launches. By forming a partnership with several other area makerspaces, volunteers, hackers and educators we are expanding our team and pooling resources. By expanding the project we aim to increase its visibility and benefit all the organizations involved as well as an increase fund-raising opportunities to help sustain all the partners/organizations and the project Spaceblimp in the long-term. This will also expose high school students to educational and technical resources outside of the school environment as well as giving all the participants the opportunity to share skills and interests to work together and learn from one another to achieve shared goals. Local area hackers and space enthusiasts will also benefit by being able to actively participate and develop skills in the design and launch of the payloads.


	The baseline technical goals are the safe and successful launch, tracking and recovery of a stratospheric balloon and its multiple payloads launched simultaneously. These goals involve exploration of concepts of buoyancy, basic electronics and energy storage, triangulation and timekeeping, radio propagation, weather prediction, FAA regulations and stratospheric environment conditions. In addition to these baseline goals, the project will welcome additional technical goals from volunteers and students primarily in the form of payload experiments suggested, designed and built by them. Spaceblimp will encourage the use of CubeSat geometry payloads to give students experience with the CubeSat design constraints and to foster discussion with future other CubeSat missions.


	The educational objective is primarily to provide an engaging, multi-day hands-on educational experience for students and volunteers heavily focused on STEM. Students will be engaged in a hands-on lesson by disassembling, reassembling and testing the basic tracking module components (GPS, radios) and other payloads. The nature of the balloon flight will naturally lead to a discussion of scientific subjects like buoyancy, atmospheric composition and density, radio propagation, weather prediction and technical topics like power consumption and energy storage. Students will have first-hand exposure to a team working environment with a delegation of responsibilities and the necessary communication and coordination. Critically, students will be allowed to suggest, design and build their own balloon payloads to be launched into near-space. This kind of self-directed educational approach uses students own natural curiosity and motivation to increase engagement and their sense of ownership of the resulting project.


	Project logistics include those necessary to achieve the technical goals, but also networking of area makerspaces and volunteers, outreach to local governments, funding sources and potential sponsors, coordination of project documentation and public exhibition of the project.		Project logistics include those necessary to achieve the technical goals, but also networking of area makerspaces and volunteers, outreach to local governments, funding sources and potential sponsors, coordination of project documentation and public exhibition of the project.


	Local area hackers, space enthusiasts, and community members have come together to share and learn new skills in the design, construction, and launch of the project.The sixth launch, Spaceblimp 6, reached 104,000ft. Spaceblimp 7 is being done in collaboration with Rockville Makerspace [http://rockvillesciencecenter.org/programs/studio-i-makerspace/] and Unallocated Space [https://www.unallocatedspace.org/].		Local area hackers, space enthusiasts, and community members have come together to share and learn new skills in the design, construction, and launch of the project.The sixth launch, Spaceblimp 6, reached 104,000ft. Spaceblimp 7 is being done in collaboration with Rockville Makerspace [http://rockvillesciencecenter.org/programs/studio-i-makerspace/] and Unallocated Space [https://www.unallocatedspace.org/].

207.172.92.193: /* Project Description & Status */ nnn

2018-05-19T14:44:23Z

Project Description & Status: nnn

← Older revision		Revision as of 14:44, 19 May 2018
Line 47:		Line 47:
	=Project Description & Status=		=Project Description & Status=

			SpaceBlimp 7 was designed as a community project driven by independent specialists from DC (Nancy C. Wolfson-Project Manager), Maryland, and members from HacDC (Enrique Cobas-Technical Manager), Rockville Makerspace (Samarth C. & David R. DeLalio- Technical Manager), and Unallocated Hackerspace. Spaceblimp 7 is an educational and exploratory stratospheric balloon project that lofts various payloads to near-space (about 100,000ft). The team is dedicated to experimenting with new technologies that will make near space activities less expensive and more broadly accessible. From electronics to mechanical design to physics, the interconnectedness of disciplines teaches a lesson in engineering teamwork and collaboration.

	~~Spaceblimp is an educational and exploratory stratospheric balloon~~ project ~~that lofts various payloads to near-space (about 100~~,~~000ft)~~. ~~The sixth launch,~~ Spaceblimp 6, ~~reached 104~~,~~000ft~~. Spaceblimp ~~7 is being done~~ in ~~collaboration with Rockville Makerspace [http://rockvillesciencecenter~~.~~org/programs/studio-i-makerspace/]~~ and ~~Unallocated Space [https://www~~.~~unallocatedspace.org/]~~.		The project has Technical, logistical and Educational goals which are described below. Spaceblimp 7 looks to add new components that weren’t part of HacDC’s previous six Spaceblimp launches. By forming a partnership with several other area makerspaces, volunteers, hackers and educators we are expanding our team and pooling resources. By expanding the project we aim to increase its visibility and benefit all the organizations involved as well as an increase fund-raising opportunities to help sustain all the partners/organizations and the project Spaceblimp in the long-term. This will also expose high school students to educational and technical resources outside of the school environment as well as giving all the participants the opportunity to share skills and interests to work together and learn from one another to achieve shared goals. Local area hackers and space enthusiasts will also benefit by being able to actively participate and develop skills in the design and launch of the payloads.

	The ~~project has Technical~~, ~~logistical~~ and ~~Educational~~ goals ~~which are described below~~. ~~Spaceblimp 7 looks~~ to ~~add new components that weren’t part~~ of ~~HacDC’s previous six~~ Spaceblimp ~~launches. By forming a partnership~~ with ~~several~~ other ~~area makerspaces~~, volunteers, ~~hackers~~ and ~~educators we are expanding our team~~ and ~~pooling resources~~. ~~By expanding~~ the ~~project we aim~~ to ~~increase its visibility~~ and ~~benefit all the organizations involved as well as~~ and ~~increase fund~~-~~raising opportunities~~ to ~~help sustain all~~ the ~~partners/organizations~~ and ~~the project Spaceblimp in the long~~-~~term~~. This ~~will also expose high school~~ students to ~~educational~~ and ~~technical resources outside~~ of the ~~school environment as well as giving all~~ the ~~participants the opportunity~~ to ~~share skills~~ and ~~interests to work together~~ and ~~learn from one another to achieve shared goals~~. Local area hackers ~~and~~ space enthusiasts ~~will also benefit by being able~~ to ~~actively participate~~ and ~~develop~~ skills in the design and launch of the ~~payloads~~. ~~So come~~ and ~~join us!~~
			The baseline technical goals are the safe and successful launch, tracking and recovery of a stratospheric balloon and its multiple payloads launched simultaneously. These goals involve exploration of concepts of buoyancy, basic electronics and energy storage, triangulation and timekeeping, radio propagation, weather prediction, FAA regulations and stratospheric environment conditions. In addition to these baseline goals, the project will welcome additional technical goals from volunteers and students primarily in the form of payload experiments suggested, designed and built by them. Spaceblimp will encourage the use of CubeSat geometry payloads to give students experience with the CubeSat design constraints and to foster discussion with future other CubeSat missions.


			The educational objective is primarily to provide an engaging, multi-day hands-on educational experience for students and volunteers heavily focused on STEM. Students will be engaged in a hands-on lesson by disassembling, reassembling and testing the basic tracking module components (GPS, radios) and other payloads. The nature of the balloon flight will naturally lead to a discussion of scientific subjects like buoyancy, atmospheric composition and density, radio propagation, weather prediction and technical topics like power consumption and energy storage. Students will have first-hand exposure to a team working environment with a delegation of responsibilities and the necessary communication and coordination. Critically, students will be allowed to suggest, design and build their own balloon payloads to be launched into near-space. This kind of self-directed educational approach uses students own natural curiosity and motivation to increase engagement and their sense of ownership of the resulting project.


			Project logistics include those necessary to achieve the technical goals, but also networking of area makerspaces and volunteers, outreach to local governments, funding sources and potential sponsors, coordination of project documentation and public exhibition of the project.


			Local area hackers, space enthusiasts, and community members have come together to share and learn new skills in the design, construction, and launch of the project.The sixth launch, Spaceblimp 6, reached 104,000ft. Spaceblimp 7 is being done in collaboration with Rockville Makerspace [http://rockvillesciencecenter.org/programs/studio-i-makerspace/] and Unallocated Space [https://www.unallocatedspace.org/].

			COMING SOON:
			-Technical, Logistical, Educational and Outreach Results.
			-The Story Behind the Spaceblimp 7
			-Photo Galery

	=Project Goals=		=Project Goals=

Summakor: /* Environmental & Accelerometer Data */ no accel

2018-05-07T02:18:54Z

Environmental & Accelerometer Data: no accel

← Older revision		Revision as of 02:18, 7 May 2018
Line 71:		Line 71:
	Unallocated Space: Buddy, Technical and Logistics Manager		Unallocated Space: Buddy, Technical and Logistics Manager

	=Environmental ~~& Accelerometer~~ Data=		=Environmental Data=

	A nearly-complete record of sensor measurements was obtained from the Raspberry Pi Pimoroni Enviro PHAT sensor board. These divided into two data logs, one for pressure, temperature, illumination, illumination color and one for 3-axis acceleration and compass heading. The former acquired data several times per minute while the latter was acquired at about 40Hz. These were acquired and analyzed using Python scripts and plotted in gnuplot.		A nearly-complete record of sensor measurements was obtained from the Raspberry Pi Pimoroni Enviro PHAT sensor board. These divided into two data logs, one for pressure, temperature, illumination, illumination color and one for 3-axis acceleration and compass heading. The former acquired data several times per minute while the latter was acquired at about 40Hz. These were acquired and analyzed using Python scripts and plotted in gnuplot.

Summakor: logs

2018-05-07T02:18:24Z

logs

← Older revision		Revision as of 02:18, 7 May 2018
Line 118:		Line 118:
	[[File:Sb7Delay_ftime.png]]		[[File:Sb7Delay_ftime.png]]

	~~'''~~Accelerometer Data~~'''~~		=Accelerometer Data=
	The ascent phase was gentle with excursions of +/- 0.2g. There's no indication of an acceleration anomaly just prior to the glitch. The balloon pop occurs near 17:12:19* UTC where the total acceleration suddenly drops from 1.0g to below 0.1g for several seconds. Terminal velocity is approached very quickly as within 10 seconds the payload registers an average of about 1.0g again.		The ascent phase was gentle with excursions of +/- 0.2g. There's no indication of an acceleration anomaly just prior to the glitch. The balloon pop occurs near 17:12:19* UTC where the total acceleration suddenly drops from 1.0g to below 0.1g for several seconds. Terminal velocity is approached very quickly as within 10 seconds the payload registers an average of about 1.0g again.

Line 136:		Line 136:

	**Note the the sequence is 1.07, 1.75, 1.70, -0.06, 0.10g in a span of 0.6 seconds.		**Note the the sequence is 1.07, 1.75, 1.70, -0.06, 0.10g in a span of 0.6 seconds.

			=System Logs=


	'''Useful Links'''		'''Useful Links'''

108.48.49.78: /* Environmental & Accelerometer Data */ asterisks...

2018-04-28T13:56:55Z

Environmental & Accelerometer Data: asterisks...

← Older revision		Revision as of 13:56, 28 April 2018
Line 92:		Line 92:
	'''Temperature'''		'''Temperature'''

	Temperature readings fall steadily from ambient ground temperature about 29.7 C to -39.9C at 16:20:19 UTC when the pressure reading was 17,568 Pa or about 40,300 ft calculated altitude. It then rises again to 36.3 C at 17:12:10 UTC (the payload is in the sun and there’s less convective cooling with less air). That’s roughly the peak altitude. Then the temperature falls more steeply as the payload descends into cold (-40C) air, and then warms near ground altitude where the air is warmer.		Temperature readings fall steadily from ambient ground temperature about 29.7 C to -39.9C at 16:20:19 UTC when the pressure reading was 17,568 Pa or about 40,300 ft calculated altitude. It then rises again to 36.3 C at 17:12:10 UTC* (the payload is in the sun and there’s less convective cooling with less air). That’s roughly the peak altitude. Then the temperature falls more steeply as the payload descends into cold (-40C) air, and then warms near ground altitude where the air is warmer.

	[[File:Sb7T_ftime.png]]		[[File:Sb7T_ftime.png]]
Line 119:		Line 119:

	'''Accelerometer Data'''		'''Accelerometer Data'''
	The ascent phase was gentle with excursions of +/- 0.2g. There's no indication of an acceleration anomaly just prior to the glitch. The balloon pop occurs near 17:12:19 UTC where the total acceleration suddenly drops from 1.0g to below 0.1g for several seconds. Terminal velocity is approached very quickly as within 10 seconds the payload registers an average of about 1.0g again.		The ascent phase was gentle with excursions of +/- 0.2g. There's no indication of an acceleration anomaly just prior to the glitch. The balloon pop occurs near 17:12:19* UTC where the total acceleration suddenly drops from 1.0g to below 0.1g for several seconds. Terminal velocity is approached very quickly as within 10 seconds the payload registers an average of about 1.0g again.


Line 125:		Line 125:


	Minimum Pressure: 1685Pa at 17:11:56.1 UTC.		Minimum Pressure: 1685Pa at 17:11:56.1* UTC.

	Peak Temperature: 36.25C at 17:12:10.7 UTC.		Peak Temperature: 36.25C at 17:12:10.7* UTC.

	Last '~1G' Data: 1.07g at 17:12:18.5 UTC.		Last '~1G' Data: 1.07g at 17:12:18.5* UTC.

	First 'Zero-G' Data: 0.1g at 17:12:19.1 UTC.*		First 'Zero-G' Data: 0.1g at 17:12:19.1 UTC.**

	*Note the the sequence is 1.07, 1.75, 1.70, -0.06, 0.10g in a span of 0.6 seconds.		*Timestamps after 164737 are slow by 30 minutes due to a glitch (see glitch discussion above). 171200 corresponds to 17:42 UTC.

			**Note the the sequence is 1.07, 1.75, 1.70, -0.06, 0.10g in a span of 0.6 seconds.

	'''Useful Links'''		'''Useful Links'''

Summakor: /* Environmental & Accelerometer Data */ timestamp warning

2018-04-27T23:38:32Z

Environmental & Accelerometer Data: timestamp warning

← Older revision		Revision as of 23:38, 27 April 2018
Line 76:		Line 76:

	The pressure drops as expected from atmospheric (101kPa) to 1.68kPa. The minmium pressure recorded corresponds approximately to 94,000ft altitude according to some online calculators. Since we lack a GPS log of altitude at high altitudes, this is an important estimate. However, the sensor component on the Enviro PHAT is only rated down to 30kPa and readings far below this range may be untrustworthy. We may perform additional tests of the EnviroPHAT board in a vacuum chamber to establish a calibration. In addition the timestamp for the minimum pressure (171156 UTC) may be incorrect due to an unexplained glitch (see below).		The pressure drops as expected from atmospheric (101kPa) to 1.68kPa. The minmium pressure recorded corresponds approximately to 94,000ft altitude according to some online calculators. Since we lack a GPS log of altitude at high altitudes, this is an important estimate. However, the sensor component on the Enviro PHAT is only rated down to 30kPa and readings far below this range may be untrustworthy. We may perform additional tests of the EnviroPHAT board in a vacuum chamber to establish a calibration. In addition the timestamp for the minimum pressure (171156 UTC) may be incorrect due to an unexplained glitch (see below).

			'''For all plots below, Flight Time (sec) was obtained by dividing evenly among all timestamps between 15:00:00 and 18:00:00 UTC. However, 18:00 UTC should actually read 18:30 UTC (see glitch below). In addition, this method hides the uneven distribution of data collection especially in accelerometer data. In reality this was acquired in bursts at 40Hz.'''

	[[File:Sb7P_ftime.png]]		[[File:Sb7P_ftime.png]]


	'''Glitch at 164737 UTC.''' At 16:47:37.75 an unexplained glitch occurred: the timestamps in the environmental sensor log jump backwards almost 30 minutes to 161717. The pressure log drops suddenly from 8.388kPa to 7.042kPa, a drop of 1.346kPa. Note the Pi Zero doesn’t have an onboard clock so timestamps represent the running time of the script rather than the real absolute time. Extrapolating from the rate of pressure drop just before and after that point, the drop should have taken about 6 minutes. This is a reasonable delay for the Raspberry Pi to shutdown, reboot and complete a file system check and resume the measurement script. The glitch matches an unusually turbulent segment in the accelerometer data but the readings don't seem harmful (+/-0.1g at 1Hz). Far more turbulence occurred several minutes later during the ascent (+/-0.2g 1Hz), during the descent (+/-0.5g >2Hz) and during the landing (+/-2.0g) with no corresponding malfunctions.		'''Glitch at 164737 UTC.'''

			At 16:47:37.75 an unexplained glitch occurred: the timestamps in the environmental sensor log jump backwards almost 30 minutes to 161717. The pressure log drops suddenly from 8.388kPa to 7.042kPa, a drop of 1.346kPa. Note the Pi Zero doesn’t have an onboard clock so timestamps represent the running time of the script rather than the real absolute time. Extrapolating from the rate of pressure drop just before and after that point, the drop should have taken about 6 minutes. This is a reasonable delay for the Raspberry Pi to shutdown, reboot and complete a file system check and resume the measurement script. The glitch matches an unusually turbulent segment in the accelerometer data but the readings don't seem harmful (+/-0.1g at 1Hz). Far more turbulence occurred several minutes later during the ascent (+/-0.2g 1Hz), during the descent (+/-0.5g >2Hz) and during the landing (+/-2.0g) with no corresponding malfunctions.

	The most turbulent part of the ascent (+/-0.2g at 1 Hz) occurred several minutes later and during the decent		The most turbulent part of the ascent (+/-0.2g at 1 Hz) occurred several minutes later and during the decent

	[[File:Pglitch_ftime.png]]		[[File:Pglitch_ftime.png]]

			'''Temperature'''

	Temperature readings fall steadily from ambient ground temperature about 29.7 C to -39.9C at 16:20:19 UTC when the pressure reading was 17,568 Pa or about 40,300 ft calculated altitude. It then rises again to 36.3 C at 17:12:10 UTC (the payload is in the sun and there’s less convective cooling with less air). That’s roughly the peak altitude. Then the temperature falls more steeply as the payload descends into cold (-40C) air, and then warms near ground altitude where the air is warmer.		Temperature readings fall steadily from ambient ground temperature about 29.7 C to -39.9C at 16:20:19 UTC when the pressure reading was 17,568 Pa or about 40,300 ft calculated altitude. It then rises again to 36.3 C at 17:12:10 UTC (the payload is in the sun and there’s less convective cooling with less air). That’s roughly the peak altitude. Then the temperature falls more steeply as the payload descends into cold (-40C) air, and then warms near ground altitude where the air is warmer.
Line 90:		Line 96:
	[[File:Sb7T_ftime.png]]		[[File:Sb7T_ftime.png]]

	Illumination		'''Illumination'''

	Direct sunlight maxes out the illumination sensor (at 65,535 bits) and most of the data is thus this value. But some data points are lower, possibly measurements taken randomly in the shade of the nylon strap as the payload rotated. These would be measurements of the sky brightness not including direct sunlight, and they show a trend. They begin hear 60,000 and fall steadily to 15,000, i.e the sky transitions from bright to relatively dark. Illumination includes light scattered from the balloon and rigging. Large deviations from the max value (i.e. dark measurements) stop abruptly near the peak altitude. I’ll guess the payload was spinning too fast in descent to acquire a complete measurement in the shade.		Direct sunlight maxes out the illumination sensor (at 65,535 bits) and most of the data is thus this value. But some data points are lower, possibly measurements taken randomly in the shade of the nylon strap as the payload rotated. These would be measurements of the sky brightness not including direct sunlight, and they show a trend. They begin hear 60,000 and fall steadily to 15,000, i.e the sky transitions from bright to relatively dark. Illumination includes light scattered from the balloon and rigging. Large deviations from the max value (i.e. dark measurements) stop abruptly near the peak altitude. I’ll guess the payload was spinning too fast in descent to acquire a complete measurement in the shade.

	[[File:Sb7Lux_ftime.png]]		[[File:Sb7Lux_ftime.png]]

	Blueishness		'''Blueishness'''

	I calculated blue saturation by taking the Blue/RBG ratio in the RGB sensor data. Again, most of the time the sensor is maxed out by direct sunlight, setting the Blue/Red ratio to 1.0. However in the shade the measurement is meaningful. The sky illumination becomes more blue for about 2000 seconds (35-40 minutes) and then becomes less blue. At the highest altitudes the illumination is actually slightly reddish (the latex balloon color?).		I calculated blue saturation by taking the Blue/RBG ratio in the RGB sensor data. Again, most of the time the sensor is maxed out by direct sunlight, setting the Blue/Red ratio to 1.0. However in the shade the measurement is meaningful. The sky illumination becomes more blue for about 2000 seconds (35-40 minutes) and then becomes less blue. At the highest altitudes the illumination is actually slightly reddish (the latex balloon color?).

Line 101:		Line 109:

	'''Delay between measurements'''		'''Delay between measurements'''

	In principle all measurements should take the same amount of time, although some scatter is expected from the script swapping between fast accelerometer data (about 10 seconds worth) and environmental sensor data (measured every few seconds). The Raspberry Pi Zero was also tasked with photographing another payload every 60 seconds or so, an operation that could hog the CPU or the microSD card momentarily. These should be regular, consistent delays throughout the flight.		In principle all measurements should take the same amount of time, although some scatter is expected from the script swapping between fast accelerometer data (about 10 seconds worth) and environmental sensor data (measured every few seconds). The Raspberry Pi Zero was also tasked with photographing another payload every 60 seconds or so, an operation that could hog the CPU or the microSD card momentarily. These should be regular, consistent delays throughout the flight.

	The timestamp differential between measurements is largely binomial; the measurements are either 21 or 27ms apart although there's significant scatter even up to 55ms.		The timestamp differential between measurements is largely binomial; the measurements are either 21 or 27ms apart although there's significant scatter even up to 55ms.

	~~The PiZSensor was also tasked with photographing the Tesla payload, which it did every 1:05 until 16:47 UTC (7,474 sec).~~

	The '''glitch''' is visible in this data as well, as a statistical change in the measurement delay times: the fastest measurements (20.1-20.5ms) became more common than they were before. This changed lasted the remaining duration of the flight. The increased measurement delays exactly at the glitch time (6336 flight seconds or 16:48:30.5 UTC) are consistent with the script running while boot processes are still momentarily running after a reboot.		The '''glitch''' is visible in this data as well, as a statistical change in the measurement delay times: the fastest measurements (20.1-20.5ms) became more common than they were before. This changed lasted the remaining duration of the flight. The increased measurement delays exactly at the glitch time (6336 flight seconds or 16:48:30.5 UTC) are consistent with the script running while boot processes are still momentarily running after a reboot.

Summakor: /* Environmental & Accelerometer Data */ da

2018-04-27T23:31:11Z

Environmental & Accelerometer Data: da

← Older revision		Revision as of 23:31, 27 April 2018
Line 80:		Line 80:


	'''Glitch at 164737 UTC.''' At 16:47:37.75 an unexplained glitch occurred: the timestamps in the environmental sensor log jump backwards almost 30 minutes to 161717. The pressure log drops suddenly from 8.388kPa to 7.042kPa, a drop of 1.346kPa. Note the Pi Zero doesn’t have an onboard clock so timestamps represent the running time of the script rather than the real absolute time. Extrapolating from the rate of pressure drop just before and after that point, the drop should have taken about 6 minutes. This is a reasonable delay for the Raspberry Pi to shutdown, reboot and complete a file system check and resume the measurement script.		'''Glitch at 164737 UTC.''' At 16:47:37.75 an unexplained glitch occurred: the timestamps in the environmental sensor log jump backwards almost 30 minutes to 161717. The pressure log drops suddenly from 8.388kPa to 7.042kPa, a drop of 1.346kPa. Note the Pi Zero doesn’t have an onboard clock so timestamps represent the running time of the script rather than the real absolute time. Extrapolating from the rate of pressure drop just before and after that point, the drop should have taken about 6 minutes. This is a reasonable delay for the Raspberry Pi to shutdown, reboot and complete a file system check and resume the measurement script. The glitch matches an unusually turbulent segment in the accelerometer data but the readings don't seem harmful (+/-0.1g at 1Hz). Far more turbulence occurred several minutes later during the ascent (+/-0.2g 1Hz), during the descent (+/-0.5g >2Hz) and during the landing (+/-2.0g) with no corresponding malfunctions.

			The most turbulent part of the ascent (+/-0.2g at 1 Hz) occurred several minutes later and during the decent

	[[File:Pglitch_ftime.png]]		[[File:Pglitch_ftime.png]]

Summakor: /* Environmental & Accelerometer Data */ asdf

2018-04-27T23:18:39Z

Environmental & Accelerometer Data: asdf

← Older revision		Revision as of 23:18, 27 April 2018
Line 108:		Line 108:

	[[File:Sb7Delay_ftime.png]]		[[File:Sb7Delay_ftime.png]]

			'''Accelerometer Data'''
			The ascent phase was gentle with excursions of +/- 0.2g. There's no indication of an acceleration anomaly just prior to the glitch. The balloon pop occurs near 17:12:19 UTC where the total acceleration suddenly drops from 1.0g to below 0.1g for several seconds. Terminal velocity is approached very quickly as within 10 seconds the payload registers an average of about 1.0g again.


			[[File:Sb7Accelg_pop_ftime.png]]


	Minimum Pressure: 1685Pa at 17:11:56.1 UTC.		Minimum Pressure: 1685Pa at 17:11:56.1 UTC.

	Peak Temperature: 36.25C at 17:12:10.7 UTC.		Peak Temperature: 36.25C at 17:12:10.7 UTC.

	Last '~1G' Data: 1.07g at 17:12:18.5 UTC.		Last '~1G' Data: 1.07g at 17:12:18.5 UTC.

	First 'Zero-G' Data: 0.1g at 17:12:19.1 UTC.*		First 'Zero-G' Data: 0.1g at 17:12:19.1 UTC.*

	*Note the the sequence is 1.07, 1.75, 1.70, -0.06, 0.10g in a span of 0.6 seconds.		*Note the the sequence is 1.07, 1.75, 1.70, -0.06, 0.10g in a span of 0.6 seconds.

	~~[[File:Sb7Accelg_pop_ftime.png]]~~

	'''Useful Links'''		'''Useful Links'''

Summakor: /* Environmental & Accelerometer Data */ accel

2018-04-27T22:50:23Z

Environmental & Accelerometer Data: accel

← Older revision		Revision as of 22:50, 27 April 2018
Line 97:		Line 97:

	[[File:Sb7Blue_fltime.png]]		[[File:Sb7Blue_fltime.png]]












	'''Delay between measurements'''		'''Delay between measurements'''
Line 116:		Line 105:
	The PiZSensor was also tasked with photographing the Tesla payload, which it did every 1:05 until 16:47 UTC (7,474 sec).		The PiZSensor was also tasked with photographing the Tesla payload, which it did every 1:05 until 16:47 UTC (7,474 sec).

	The '''glitch''' is visible in this data as well, as a statistical change in the measurement delay times: the fastest measurements (20.1-20.5ms) became more common than they were before. This changed lasted the remaining duration of the flight. The increased measurement delays exactly at the glitch time (6336 flight seconds or 16:48:30 UTC) are consistent with the script running while boot processes are still momentarily running after a reboot.		The '''glitch''' is visible in this data as well, as a statistical change in the measurement delay times: the fastest measurements (20.1-20.5ms) became more common than they were before. This changed lasted the remaining duration of the flight. The increased measurement delays exactly at the glitch time (6336 flight seconds or 16:48:30.5 UTC) are consistent with the script running while boot processes are still momentarily running after a reboot.

	[[File:Sb7Delay_ftime.png]]		[[File:Sb7Delay_ftime.png]]

			Minimum Pressure: 1685Pa at 17:11:56.1 UTC.
			Peak Temperature: 36.25C at 17:12:10.7 UTC.
			Last '~1G' Data: 1.07g at 17:12:18.5 UTC.
			First 'Zero-G' Data: 0.1g at 17:12:19.1 UTC.*

			*Note the the sequence is 1.07, 1.75, 1.70, -0.06, 0.10g in a span of 0.6 seconds.

			[[File:Sb7Accelg_pop_ftime.png]]

	'''Useful Links'''		'''Useful Links'''