Search the Community

Showing results for tags 'probe'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • The Daily Kerbal
  • General KSP
    • KSP Discussion
    • Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Gameplay and Technical Support
    • Gameplay Questions and Tutorials
    • Technical Support (PC, unmodded installs)
    • Technical Support (PC, modded installs)
    • Technical Support (PlayStation 4, XBox One)
  • Add-ons
    • Add-on Discussions
    • Add-on Releases
    • Add-on Development
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website
  • KSP Pre-release
    • 1.2.9 Pre-release Branch
    • 1.2.9 Pre-release Modding Discussions
    • 1.2.9 Pre-release Bug Tracker

Categories

  • Developer Articles

Found 20 results

  1. So i'm fairly new to this game and i decide i wanted to build a probe, so i did and i built a rocket with mk3 cargo doors to put it into space. My goal was to try and get into orbit then open the cargo doors and have the probe released. Once i got into orbit and opened the doors, activated the radial decouplers nothing happened. The probe was just sitting in the doors and it wasn't even attached to anything. i tried wiggling the ship around but nothing happened still. If Anyone has any idea on how to fix this it would be appreciated. Thank you. Screenshots~ http://prntscr.com/fl68xe http://prntscr.com/fl691w http://prntscr.com/fl697k http://prntscr.com/fl69eq
  2. I have a problem building a new unmanned satellite for a mission. I tried once launching the saved ship design i used for another mission and when the orbit was identical i noticed that the new unmanned satellite wasn't ticked. Then i even tried with testing new ships, built from scratch and different names, even flags but no result. I've found nothing that help in any similar case...any ideas? screenshot:http://prnt.sc/f5nqjm Thanks in advance
  3. Ok, this is a really complicated question, but I'll do my best to make it clear. I've built myself a plane with a downward facing cargo bay (called henceforth carrier). It's purpose is to carry a few probe cores, outfitted with parachutes, a small battery, and some science gear, and drop them into different biomes for data collection (called henceforth pods). The idea being I can record data and collect science from many biomes with fewer missions launched, and also very quickly, since the carrier pushes right up to the edge of mach 1, fully loaded. So far so good. I fly off with one pod in the carriers belly, and an action group to detach the pod, deploy its chute, and turn off its hibernation all at once. I let it go at about 3,000m, everything looks peachy. I can't switch to the probe, since I'm flying in atmosphere, so I watch its altitude and speed from map view. It holds at about 175m/s all the way into the ground. After much tinkering with drogue chutes, differing altitudes and states of probe hibernation, I decide that what needs to happen is I need my control to follow the pod when it detaches instead of the plane. That way I can see what's really happening with the parachutes, and once its landed I can switch back to the plane and keep flying. I had toyed a little with the Stratolauncher (stock), so I figured this would work well. I converted all my action groups into a staging setup, since that's how the Stratolauncher (stock), is set up, and I thought it would work. Same deal as before. How do I get this to work? How can I designate to the editor that I'd like the staging to follow the probe pod out the belly, instead of the plane all the way? Or is there another solution I'm not seeing? I'd include the .craft file of the carrier as it stands right now, but I'm not sure how to attach a .craft. I'd appreciate a concise explanation of that as well if you feel the need to see the plane. Thank you!
  4. So I updated to 1.2 KSP. Now I had a save in 1.1, and had started a Duna probe with lander. The problem is, I only have a Commutron-16 on the probe, so I don't have link back to Kerbin. DSN is level 3, and I just launched a Relay into 16 000 000 m Orbit with HG-5s. My question is, how could I establish a connection with the probe, if my best relay is the HG-5? Thanks
  5. I'm designing a return probe for Laythe and doing trials on Kerbin. My problem is, shortly after launch, at roughly 50-60k altitude, it loses contact with KSC, going instantly from maximum signal to zero. I have a surface-mounted Mk 16 antenna on it, which has not been destroyed by aero forces. I have a direct line of sight to KSC (level 2 tracking station). Contact isn't re-established once it's out of the atmosphere so it can't be plasma-induced comms blackout either (and I'm not going that fast anyway). So... what gives? Why am I losing contact?
  6. Hi Guys, Having real issues with my (fairly large) Duna probe in an RT install... my signal delay is up to about 2s and I'm trying to do a course correct ion burn... however I'm having major issues aligning with the manouver marker. Neither the ASAS nor the flight computer can actually align to the node - they just circle around it always over-correcting and wasting precious monoprop. I've checked in both RCS buildaid and as the manouvers are conducted and there's no errant 'spin' imparted by unbalanced RCS. Nor is the probe itself unbalanced... it just burns like cray in one direction, overshoots, and burns like crazy back again, like a beagle puppy on a polished timber floor... My only thought is that the computers can't cope with the sheer mass (and thus inertia) of the probe - it does weigh in at some 47,000kg... Though I packed SpaceYRCS5x7 thrusters in an effort to compensate... Help?
  7. All of my unmanned probes have vanished from the tracking station. I can't see them, I can't control them. When I launch a new one, it doesn't have an icon in it's own map screen and as soon as I return to the space center it vanishes. I've managed to find the vessels in the save game file, so it appears they're still out there, but I have no idea how to make them trackable again. I've been playing KSP vanilla for some time but I recently installed mechjeb and mechjeb integrated, because I was tired of docking and performing holtzman transfers on my own. It worked fine for several days so I'm not convinced that the mods have anything to do with my issue. I haven't tried removing the mods yet, I suppose I'll try that next.
  8. This thread is a collection of screenshots taken from my Surveyor 17 probe that orbits Jool. I launched it to Jool to learn more about the moons and orbital mechanics. The first set of flybys (Laythe, Vall, and Laythe again) http://imgur.com/a/GJi8u Can someone tell me how to upload albums without having to leave a link?
  9. Afternoon! I am currently running 1.1.3 of KSP on my machine with several mods. Full list is after the issue. I have found that when I tried to build by first satellite for the comms network required by RemoteTech, my probe cores don't do anything on the launch pad. I can't activate SAS, using the Probodobodyne OKTO core. Also, while it let's me adjust the throttle, pitch, yaw and roll, I cannot activate anything using the staging mechanism (space bar) nor can I manually active engines through the right click menu. Let me know if anyone else has experienced this issue and, if so, what is the fix? Mods installed: CommonResources, DockingPortAlignment, USI Freight, Karbonite, USI Karibou, Kerbal Attachment System, Kerbal Inventory System, KSP Interstellar Extended (Includes KSPI, Firespitter, InterstellarFuelSwitch,RcsSounds and TweakScale in addition to KSPI), SCANsat, StationScience, USIKolonization, USILifeSupport, All mods are up to date and using the correct installation to my knowledge. Also! I have the necessary antennae on the craft and it is reading as connected in the upper left hand corner per RemoteTech requirements. Thanks and looking forward to getting this resolved! Bill
  10. Have an real irritating problem then assemble complex payloads from probe dispensers up to interplanetary missions with bases and landets its nice to test each component and add control from here on bottom docking port, load and merge or use it as an subcomponent and add to launcher. and the rest of the payload. This worked nice in earlier version of KSP, however in 1.12 it reset back to the original control from here node on load of craft, this creates a lot of problems for me especially small probes with high twr. is this an known issue or caused by mods? Is it any fix?
  11. How do I unlink the RCS/gear/etc. of my docked mini-ship subassembly from the main ship? I have a large ship with a docked scouting ship. When I turn on RCS, or press 'G' for gear, the mini ship works along the big ship. I want to unlink these ships. The mini ship is in a bay and does not need to fire its RCS or deploy its gear when the main ship is landing or maneuvering.
  12. Ok, this my first post here, i hope i've done it right and i don't absolutely know what tags should i use, so, let's begin: Master Aerospace Technologies is proud to announce the new, fantastic, versatile probe design, the Wheeled Autonomous Surface Probe or W.A.S.P. : The W.A.S.P. can carry al sort of scientific experiments, it has solar panels for daylight and a small fuel cell with 2 Oscar-B fuel tanks and a light for night time. The ultimate 3 wheeled design is stable and reliable and allow the W.A.S.P. to travel up to 11 m/s without flipping*! The model here illustrated is equipped with a Remotetech antenna and some scientific stuff from DMagic, but the core is full stock and can be easily reproduced. *That's not true, but nobody reads the notes: http://i.imgur.com/2uqmVcm.png
  13. Is There A way to add a Science Lab to the probe - rover -base thingy? Like with a "0" crew requirement? I made a curiosty rover replica and i would like to have a science lab onboard like the real thing.
  14. RELEASED! A new thread will soon be up in the released forum, but you can allready download the mod at SpaceDock: DOWNLOAD :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: First in line to be introduced we have the very first step in the K-Sat series: Pzl-BB 888. It's intended to be more of a DIY probe, with more flexibility but less integrated parts. As far as antennas go, it only features an always-on launch omni (500km) but it still provides a small battery bank and a trickle of power using a miniscule nuclear generator. The most interesting part of the design is without a doubt the fact that it is hollowed out, making it possible to place the fuel tank inside the probe, keeping the spherical shape of the probe intact. It is also the only probe core in the series that allows surface attachment, and it has it's own dedicated support pylon available, giving it lots of options for bringing scientific equipment along for the ride. To further help with that last part, I've also made an inline part containing all four basic enviromental experiments: Temp, Pressure, Grav and Acc. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: This probe is called PzL-LO 242 and it's the first of the LO models. It lacks a dedicated dish, but more than makes up for that with a powerful omni (5Mn). I carries 500 units of electrical charge in it's integrated battery bank, and a small nuclear generator provides 0.3e/s, slightly more than the BB 888. During this test flight we also attached our latest stand-alone battery bank, the EC-500, capable of storing 500 units of charge. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: The next step up from the 242 is the PzL-LO 1138. It comes with a 2.5Mn omni and a 50Mn dish with a standard 45 degree cone. It carries 600 units of electrical charge and provides 0.4e/s using a slightly beefed up version of the K-Sat integrated nuclear generator. Provided that at least one solar panel is included, the power will last through Kerbins darkness time at altitudes of up to 1,500,000 meters. Also presented below is the K-Sat Fuel Tank A. It's half a meter tall (10 centimeters taller than the Oscar) and carries 27/33 units of fuel. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: The last step in the LO series is the PzL-LO 1142. It comes pre-packaged with a medium ranged omni (3Mn) and a dish capable of reaching Kerbin from the edge of the planets SOI (80Mn). It is also by far the most capable model in the series as far as power production goes, with 0.5e/s produced and 700 units of charge stored in the internal battery banks, making it possible to operate trhoughout the darkness time at a keosynchronous orbit. We also get a look at the all-purpose structural girder, K-Sat Structural Support A, with cross-feed for fuel and... not much else. It's there to glue stuff to. Lastly, we have the first stand-alone dish, the K-Sat COM-D1, an interesting dish with a very specific purpose. It's limited range (15Mn) and an unusually narrow cone of angle (12.5 degrees) makes it more or less useless for all other tasks other than communication with The Mün, but the upside is that it requires much less electricity to run than most other dishes, and on top of that it has it's own small battery bank. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: K-Sat LFE-808 "Bolt" is PanzarLabs in-house engine. It's designed specifically with satellites in mind, and as such it is almost useless in atmospheric flight, but has a very good Isp in vacuum. The trust is slightly lower than that of the "Spark" engine, but the Isp makes up for it and then some. It comes with custom made engine FXs and heat emission. The actual values are subject to change as I'm still balance testing it, but right now it has an atmospheric Isp of 110 and a vacuum Isp of 340, with a maximum thrust of 14.
  15. I have just launched a probe to Saturn. It will arrive in 12 years, so I think I could do some more things. Probe leaving home. A picture taken by the telescope camera. Another photo for the probe. The delta-v remained is about 2500, which is enough for the Saturn capture and further exploration. And I am using Aerozine50 and NTO for fuel, inside the B9 Procedural Wings (Sound like a atmosphere work).
  16. I want a Mission Control room for launching spacecrafts like as in Houston Control Room. People are waiting for this for a long time. Hope Squad starts working in this thing. We want the Control room to be something like this. If anybody can help please do so.
  17. Is there an altimeter on stock probes? Or, is there a clever way to get distance to terrain when using only a stock probe? Why do I feel like I'm opening a can of worms?
  18. In 2017, the competition for New Frontiers missions for launch in 2021 begins. New Frontiers missions have a cost cap of $1 Billion, and are used for medium class missions larger than discovery, but smaller than Flagship. Keep in mind that we know little about the design of these probes themselves, so this thread is more about where you would launch a mission. Missions may use an RTG or Ion Drive. https://en.m.wikipedia.org/wiki/New_Frontiers_program There are 6 Mission proposals being considered currently: Titan/Enceledus Mission: NASA recently sent out a call for New Frontiers proposals to study Titan and/or Enceladus. Currently, little is known about what such a mission would look like. It could do multiple flybys of Titan and Enceladus (like Europa Clipper, though radiation is not an issue at Saturn), orbit either Titan or Enceladus, or land on Titan. Pros: - Both moons could harbour life, and are considered excellent scientific destinations. - Would be great for NASA publicity- almost as much as New Horizons. - A multi-flyby probe could help replace the lost science capability once Cassini ends its mission. - A RTG-powered probe would likely be able to launch on a smaller Falcon Heavy via a Jupiter flyby, but would have a more expensive probe, while a solar-powered probe (like Juno, but at Saturn) would require a Jupiter Flyby, and a SLS- but the probe would likely be cheaper. Both assume we use a direct trajectory to the outer planets, and not something like VEEGA, which would increase the transit time A LOT. Cons: - Probably better to reserve for a Flagship mission, as it has a higher of going over-budget and being cancelled than the other missions, due to the distance to Saturn (something none of us would want). - Would either need giant Solar panels or RTGs, due to the distance to Saturn. - An SLS, though it would not be included in the project costs (launch costs are not included in Discovery, Explorer, and New Frontiers missions), but would still cost an arm and a leg. So would an RTG. And a VEEGA-like trajectory would give us less science data due to the lower lifetime from having to linger around the inner solar system. - We know nothing about this mission proposal (so DON'T blindly choose this one!) Saturn Atmospheric Entry Probe: A Galileo-style entry probe carrying a carrier/relay spacecraft, which would carry the entry probe, and send data back to Earth. It would give scientists critical data about Saturn's atmosphere, including isotopic ratios, and noble gas abundances, which they apparently really want. The entry probe would survive to at least five bar, but would continue to operate until it is crushed by the atmosphere. Pros: - Highly important science data will be collected. Cons: - Mission will likely not generate any publicity. - Mission would last for very little time despite the approx. 7 year transit time to Saturn. (4 years transit for SLS) - Faces the same power problems as the Enceladus/Titan Mission, but with the added twist of needing a high-G entry probe- something that might be too much for the limited New Frontiers budget. Venus In-Situ Explorer: Similar to a comet probe-less VEGA, or a extended VERITAS also designed to land on Venus, Venus In-Situ Explorer would send a lander, and possibly an aero-bot or another kind of probe, to study Venus's entire atmosphere, especially of trace and noble gases. It would also study the crust and lower atmosphere in detail, something impossible from orbit. It would also obtain surface samples for study. Pros: - Would retrieve very high-importance science data. - Would have less of a chance of breaking the budget due to Venus being closer. - Venus In-Situ Explorer would make a great follow-up to VEGA. - We need to study Venus more. Cons: - It would likely be a relatively short mission-perhaps 2 days in length. - Power is likely limited to how much you can carry in your batteries. Trojan Tour and Rendezvous: The Trojan Tour and Rendezvous mission would likely be similar to an extended version of the proposed LUCY, and would study a completely new kind of object- a Jupiter Trojan. It would flyby two or more Trojan asteroids, then settle in orbit around one of them. Pros: - It would provide good scientific data on a completely unknown category of asteroids- Trojan Asteroids are thought to be very different than the ones closer into the solar system. - It might provide a SLS mission for the empty SLS launch manifest. - It would study multiple objects in the Trojans, getting more science data on a variety of objects there. Cons: - If Juno https://en.m.wikipedia.org/wiki/Juno_(spacecraft) is any indication, such a asteroid mission would need an SLS Block I or an RTG to reach the Jupiter Trojans, both which cost an arm and a leg. - Transit time is surprisingly 10 years, no matter if you launch on SLS or Atlas V + VEEGA. SLS would provide 6x the payload capacity, though. Comet Surface Sample Return: A Comet Surface Sample Return Mission would acquire and return to Earth a small amount of cometary material from the nucleus (by landing) of a comet in a way that preserves organic compounds in the sample. It may also get a sample from multiple locations on the comet, though obviously this increases cost. It would get important data on the condition and constituents of the early Solar System, especially water and organics. It has also been suggested such a mission land near an active cometary jet. This mission would also study the comet's structure, composition, age, texture, structure, regolith, and evolution as it passes close to the Sun. Pros: - Good Science data can be obtained from this mission. - Depending on the comet, and intercept location, can have less or greater risk of breaking the budget. - Can be a good follow-up to the Rosetta/Philae mission. - Gets cometary material not able to be obtained by the Stardust mission. Cons: - It might be better to wait until the next New Frontiers mission, where a Lunar space station, or Orion can retrieve the capsule- this will increase the sample size enormously, as it can ride on a much larger capsule, and reduce the mass of the spacecraft for moar! boosters!. A Lunar Space station would be especially advantageous, as it could be incorporated into the crew's mission without having to send a dedicated, expensive mission to retrieve it. Lunar South Pole - Aitken Basin Sample Return: A Lunar South Pole Sample Return Mission would return samples of the early Moon's deep crust(the Aitken Basin is an enormous, deep impact crater) - something the region targeted is thought to contain. It would also obtain previously unobtainable surface samples not biased by Near-side Impact basin formation at the South Pole of the Moon. Most of the science objectives, however, such as trying to understand Lunar thermal evolution, would be accomplished via the returned samples. Pros: - Good science data can be obtained from this mission. - The first lunar dust samples from the poles (and partially far side) of the Moon can finally be obtained- giving scientists an idea of what a human mission to the Moon might get at the poles/far side. - Probably less likely to break the budget. - Would test a NASA heavy lander (like Morpheus) that would help in building a manned lunar lander- it would launch on an Atlas 431. Cons: - Possibly better to wait until a Lunar Space Station (which is likely, due to the new deep space HAB work going on in NASA)+Orion can pick up the samples for Earth Return, which would increase the payload/ regolith the mission would return to Earth. An Io Orbiter and Lunar Geophysical Network are proposed for a later New Frontiers mission, and are not in this New Frontiers mission contest. Information on these can be found here:https://en.wikipedia.org/wiki/New_Frontiers_program#Io_Volcano_Observer So, which New Frontiers Mission would you choose for launch in 2021?
  19. here is a neat idea for a part, a xenon scoop that you could unlock shortly after the dawn engine that would deploy like a solar panel and collect very small amounts of xenon, enough to keep it running almost indefinitely. if the game ever went interstellar this would be a low-tech - relatively speaking of course in comparison to warp or near ftl - solution to rudimentary exploration of worlds beyond. another feature that would complement interstellar nicely would be a fog of exploration, like in sid meier's civ, where you could only see within a certain range of where you've been.
  20. Hi everybody. I am not familiar with modding but I've got an idea to improve the gameplay in career mode and I would like to share it with you. If some of you find it relevant and think it can be modded, I would be glad to help as much as I can. My idea is to remove the mechjeb part and include the mechjeb functions in both pilots aptitudes and probe caracteristics. To make it fun, the number of functionalities available should raise with: the Xp-level of the pilot / the tech-level of the probe. I started to think at the balance adjustments with 6 steps : # Pilot lvl PROBE FUNCTIONALITIES unlocked 1 0 Stayputnik Mk1 SAS / Delta-V stats 2 1 Probodobodyne OKTO Smart A.S.S. / RCS balancer / Smart RCS 3 2 Probodobodyne HECS Maneuver planner / Node editor 4 3 Probodobodyne QBE CH-J3 fly-by-wire Translatron / Rover Autopilot 5 4 Probodobodyne OKTO 2 Ascent / landing & spaceplane guidance 6 5 RC-001S / Mk2 Drone / RC-L01 Rendez-vous & docking guidance The idea is to include the following function by default in all modules & probes: Vessel info Utilities Warp helper Surface info Orbit info In addition, the tech tree position of the probe could be modified to have earlier access to it, for example: Probe Tech prereq Stayputnik Mk1 Stability Probodobodyne OKTO Flight control Probodobodyne HECS Advanced flight control Probodobodyne QBE Precision engineering I let you comment my idea, let me know if you like it, if you think it's realisable, how to do it ... etc Sorry if someone already posted a similar idea somewhere else on the forum, i just didn't find a similar thread.