Saturday, May 15. 2010More Throttle Control progress
Under software control, Luke has demonstrated opening and closing the throttle +/- 10 degrees. This 'dithering' action is made using a simple algorithm and can be customised so as to prevent the super-cold liquid oxygen ball valve from sticking, prior to launch.
Luke's work is advancing nicely with a PCB layout for throttle control hardware. We'll attempt to make the make the board dimensions and positions of the mounting holes identical between the Rutex R2020 and the throttle control board, so they can be stacked together making them more space efficient. ![]() After analysing design proposals, Roy suggested providing two sensing potentiometers for valve positioning. This would provide redundancy in case one is damaged and increase valve position accuracy when the results of both are combined. Roy's proposal is to have the two cams, which are connected to the throttle position sensing potentiometers, offset by 45 degrees. Nice throttle control work being done Numbatters! Saturday, April 3. 2010Throttle Control work, progresses
Fortunately the variable throttle control technology we're developing for ASRI's Ausroc 2.5 is also transferable to the descent stage motor of the White Label Space lunar lander, so it's a win all round for our GLXP partner WLS, the Australian Space Research Institute, and us.
With parts for development provided by ASRI, Luke Weston has built a 60 V power supply for testing the motor which will drive the gearhead that will control the RP1 valve, and thus throttle propellent to the rocket engine. After some simple testing, Luke has also tuned the Rutex R2020 servo drive board so as to give it full control of the motor / gearhead assembly, as seen below: Along with this great work, Luke has also prepared some preliminary code for an AVR (Arduino) to control the throttle motor via the Rutex servo board, and done a marvellous job of updating the relevant documentation on the Wiki. Ultimately, through Luke's and the rest of the build team's efforts, we'll prepare avionics to take instructions on a CAN bus and translate these to valve positions which will control propellant flow into the Ausroc A2.5 rocket engine, and thus thrust. All a bit exciting really Saturday, June 20. 2009Building up capability and practical expertise
Andy Gelme of the Lunar Numbat build team has prepared this post of his recent endeavours:
Continuing on from the initial launches of a Class C rocket, the Lunar Numbat build team has been making steady progress towards launching more sophisticated avionics, along with an audio/video feed, as part of a Class G rocket. A crucial part of the journey has been, not just creating the hardware and software, but bringing more capability and experience to the effort, in the form of organization, equipment and most importantly ... people with specialist skills. For a long time, we've been contemplating the need for a shared space or workshop, expensive electronics equipment and mechanical manufacturing capabilities beyond that which individuals can typically justify or afford. These sorts of facilities are available in universities and specific types of government or commercial organizations, but they are much less accessible to smaller communities of individual developers. At the end of March 2009, a Wired magazine article propelled the concept of HackerSpaces into the popular zeitgeist. So, it was an natural step to create the first HackerSpace in Melbourne, Australia, aka the "Connected Community". The Connected Community HackerSpace was formed and operates independently of Lunar Numbat. A HackerSpace is much broader in scope than even a space technology project, to the point of hacking any object in any domain in any conceivable fashion is fair game. Fortunately, there is significant overlap in the types of people involved in both groups, the skills and equipment required and the artifacts created. An advantage of the HackerSpace is that it attracts a larger community of hobbyists and professionals. These people may not be as focused or as passionate about the research and development of space technology as the Lunar Numbat team. Although, sometimes they are even more passionate. However, their skills can directly or indirectly contribute to the Lunar Numbat effort, due to the deeply embedded culture of sharing. This collaboration is enhanced by both groups utilizing commodity, open-source hardware and software. The power of open-source hardware and software communities is evident in the growing number of developers using the Arduino platform or BeagleBoard for increasingly sophisticated projects. Since it's inception, the HackerSpace has been meeting regularly and working on a variety of projects. Many of the projects have been founded by HackerSpace members, often initiated prior to the HackerSpace and operating independently. In addition, the HackerSpace is introducing new members to those projects and bringing them up-to-speed with fundamental skills, such as PCB design and manufacture. New members also bring additional skills such as amateur radio experience, CNC milling machine design, construction using composite materials or hard-core hardware and software engineering ... and, even rocketry Lunar Numbat will benefit from this infusion of new blood into HackerSpace and the Class G rocket development has been one of the projects around which HackerSpace members can gravitate and apply their skills. Project progress and technical discussions have been captured on the Connected Community HackerSpace web-site and project artifacts placed in social coding repositories, such as the popular GitHub, as follows ... A key outcome will be to deliver re-usable hardware and software components. In part, this is driving us to create general purpose frameworks, like Aiko, which provide a modular, event-driven abstraction on top of specific hardware / software platforms, like the Arduino. This is so that we can produce high-quality embedded applications and software components that encapsulate a given set of hardware devices. In the longer term, this collaboration between the Connected Community HackerSpace and Lunar Numbat, along with the resulting re-usable hardware and software artifacts, provides a strong foundation for undertaking the next phases of Lunar Numbat beyond the current Class G rocket launch milestone. Sunday, April 26. 2009A glance at Software Defined RadioI will explain what that means shortly, but first a quick background in the components I will be mentioning. When a radio signal is received by an antenna, it is amplified by a pre-amp, then converted from it original frequency to an intermediate frequency. The selection (tuning) of what frequency is received is part of the conversion process. The main reason to use intermediate frequency is that intermediate frequency is much easier to create electronics for and requires cheaper components. The intermediate frequency signal is then processed (demodulated) to create the output signal, be it audio signals, analog TV or digital data. The reverse process it used to send the signal out. The most common component to replace is the function that turns intermediate frequency analog signal into the output signal and vis-versa. In SDR, the output of the original to intermediate frequency conversion is fed into a high speed (bandwidth of the signal, typically less than 20MHz) analog to digital converter (ADC). This gives digital representation of the signal, which is then processed by computer. The reverse is accomplished with a digital to analog converter (DAC). The computer then turns the digital signal into something useful. This conversion is requires a lot of processing power, so specialised hardware such as Digital Signal Processing (DSP) components are often used. GNU Radio (an implementation of SDR with some open hardware and software) has been used to decode AM and FM radio stations, digital TV and others. GNU Radio hardware uses cable modem components to tune into and convert the original signal to intermediate frequency. The main advantage of SDR is it's flexibility. A single hardware unit can be used to tune into and decode a large number of different types transmissions. An example of this flexibility is being able to adapt from using 802.11b to 802.11g by tweaking some code, whereas with hardware new chips, components and circuits would be required. There are two significant disadvantages for using SDR in space applications. They are the computer power required, and failure scenarios. The significant (1GHz+) processing power required for SDR has three flow on effect: more mass, more power required, and more heat to deal with. More mass comes from the extra computer, which requires extra shielding as faster computers are more prone to solar radiation. Obviously a computer requires power so more electricity is needed. And computers produce heat which must be removed or it will fail, and removing heat in space is more difficult than in an atmosphere. SDR creates new risks of failure. Because of it's software defined nature, any software problem will prevent the system from working. This is a key risk, as without the communication link, most space craft can't do anything. A second risk is introduced by it's flexible reprogrammable nature. Any upgrade or reconfiguration could prevent the system from working again. Both can be mitigated to a certain extent. Software defined radio could have a place in space missions where there is a need for flexibility or adaptability in radio modulation and risks are dealt with. Published under CC-by-sa Wednesday, February 18. 2009The other 'Marsupial' Rover An ingenious 'tethered marsupial rover' that would spend most of its time attached to a larger vehicle until it is needed is being investigated by NASA.From Space.com: The Axel rover prototype is built like a yo-yo; its tether is wrapped around its central axle. The other end of the tether would be attached to a larger, conventional rover robot, like the Spirit and Opportunity rovers on Mars. The Axel rover solves a problem that bedevils these conventional robots. When Spirit, for example, encounters a crater, it cannot descend and explore. Small, nippy and smart is all the rage. Go Lunar Numbat! Friday, February 13. 2009Mars rovers driven by Australian DC micromotors Spirit and Opportunity, the wildly successful Martian rovers have an Australian contribution.Both are driven by 39 DC micromotors supplied by Maxon Motor Australia. Each rover is equipped with 39 DC motors from Swiss drive specialists, Maxon motor Australia. The precision drives are used for driving the robotic arms, rock drilling, operating the cameras, the steering mechanism, and for the 6 wheels that drive the heavy vehicles (each weighing nearly 180kg) over the planet’s surface. Worthy of investigation.
(Page 1 of 1, totaling 6 entries)
|
Lunar NumbatBlogrollLN Mail List feedRe: Copenhagen Suborbitals
Tuesday, September 7. 2010 Apertus, The Open Source HD Cinema Camera Tuesday, September 7. 2010 Re: Copenhagen Suborbitals Tuesday, September 7. 2010 Re: ASRI Generic Telemetry Module Tuesday, September 7. 2010 Re: Lunar Numbat meeting in Melbourne tonight. Tuesday, September 7. 2010 White Label SpaceLeo de Bolster
Sunday, September 5. 2010 Paper for IAC 2010 Sunday, September 5. 2010 Rover Prototype Design Friday, September 3. 2010 Space Rover: Move Me With Your Touch Monday, August 30. 2010 NASA Surveyor Programme – 1966-68 – Laying the Foundations for Apollo Friday, August 20. 2010 Blog ArchivesSyndicate This Blog |