Difference between revisions of "M700 Survey Scanner"
CDR Xavier (talk | contribs) (Removed extraneous detail of electric consumption) |
|||
Line 19: | Line 19: | ||
There are options to change the data presentation. You can modify the display cutoff value (the higher the value, the richer the deposit) and the results' color and style. You cannot change these parameters from map mode. Retracting the scanner will hide the results until the scanner is re-deployed and the overlay is toggled again. | There are options to change the data presentation. You can modify the display cutoff value (the higher the value, the richer the deposit) and the results' color and style. You cannot change these parameters from map mode. Retracting the scanner will hide the results until the scanner is re-deployed and the overlay is toggled again. | ||
+ | |||
+ | [[File:Orbitalsurvey.png|right|thumb|The [[Mun]] in false color after completing an orbital survey]] | ||
After using this scanner, it is possible to start resource extraction based on its results alone, but the best results will be achieved by using the scan results as the basis for performing detailed, targeted scans with the high resolution scanners: | After using this scanner, it is possible to start resource extraction based on its results alone, but the best results will be achieved by using the scan results as the basis for performing detailed, targeted scans with the high resolution scanners: |
Revision as of 22:46, 2 April 2023
M700 Survey Scanner | ||
Scanner by Experimental Engineering Group | ||
Radial size | Small, Radial mounted | |
Cost | (total) | 1 500.00 |
Mass | (total) | 0.200 t |
Drag | 0.2 | |
Max. Temp. | 2000 K | |
Impact Tolerance | 7 m/s | |
Research | Scanning Tech | |
Unlock cost | 4 500 | |
Since version | 1.0 | |
Part configuration | SurveyScanner.cfg | |
Mode | Orbital | |
Resource | All | |
Scanning time | 5 s | |
Science bonus | 10 | |
Min. Altitude | 25 000 m [1] | |
Max. Altitude | 1 500 000 m [2] | |
Packed volume | None | |
|
The M700 Survey Scanner is an orbital low resolution resource scanner. It is used to map broad areas of resource concentration on a celestial body. It is the first step in finding locations which are rich in resources, for subsequent extraction. It provides a low detail overview of the entire celestial body, which can then be used to target specific areas for further detailed scanning with high resolution scanners (which can only scan a small area, not an entire celestial body).
Contents
Product description
“ | This orbital survey scanner uses a combination of advanced sensor technology and witchcraft to provide information on a planet or moons natural resources. These images can be viewed either in flight, or in relative safety and comfort back at the KSC. Be sure to bring an antenna capable of transmitting the information back, and sufficient power. — Experimental Engineering Group |
” |
Usage
The scanner works well on a small 1.25m satellite, but generate a large amount of data when activated, so a Z-1k battery, or equivalent, is recommended to store enough electricity for transmission, but is not required if the antenna have "require complete" toggled. It is not particularly heavy, so a FL-T200 fuel tank and LV-909 engine are quite adequate for the final stage, providing the necessary power to establish and adjust the orbit, either from LKO to Mun and Minmus, or entry from solar orbit to another system. An antenna is required to upload the data back to KSC, and any antenna will suffice. Transmitting a resource scan back to Kerbin counts as a science broadcast in terms of "world's firsts" (that is, if you perform a resource scan before transmitting any other science data, you will receive a "We have transmitted our first science from _" accomplishment.)
Launching should probably make use of a payload fairing or cargo bay, as the scanner is large and not a good aerodynamic shape, so is likely to cause atmospheric control issues when placed on top of a rocket. The scanner requires a stable polar orbit at an appropriate altitude (see below). Once established in orbit, it must first be opened (Deploy Scanner), then the scan can be performed (Perform orbital survey). The scan is a once per body operation, and only takes a few seconds, but the amount (of data) is fairly substantial. The scan result can be viewed in map mode (default M key) while controlling the scanner satellite, or from the KSC Tracking Station. To view the results in map mode, right-click on the scanner while it is deployed and select Toggle Overlay. To view the results from the Tracking Station, select the orbital body and then click on the Resources icon on the right hand side of the window. The deployed scanner can be retracted by clicking on the Retract Scanner option.
There are options to change the data presentation. You can modify the display cutoff value (the higher the value, the richer the deposit) and the results' color and style. You cannot change these parameters from map mode. Retracting the scanner will hide the results until the scanner is re-deployed and the overlay is toggled again.
After using this scanner, it is possible to start resource extraction based on its results alone, but the best results will be achieved by using the scan results as the basis for performing detailed, targeted scans with the high resolution scanners:
You don't need to orbit the body with a M700 scanner anymore after an orbital scan. You can either destroy it or send it to another body if you have enough fuel left. The ore information will stil be available in the map view (sliced planet icon).
Scanning requirements
The scanner can only perform an orbital survey if it is in a stable polar orbit at medium altitude. It means the inclination must be between 80° and 100°.
Celestial body | Radius | Altitude | |
---|---|---|---|
Min. | Max. | ||
Kerbol | 261.6 Mm | N/A | N/A |
Moho | 250 km | 25 km | 1.25 Mm |
Eve | 700 km | 70 km | 1.5 Mm |
Gilly | 13 km | 25 km | 65 km |
Kerbin | 600 km | 60 km | 1.5 Mm |
Mun | 200 km | 25 km | 1000 km |
Minmus | 60 km | 25 km | 300 km |
Duna | 320 km | 32 km | 1.5 Mm |
Ike | 130 km | 25 km | 650 km |
Dres | 138 km | 25 km | 690 km |
Jool | 6 Mm | 600 km | 1.5 Mm |
Laythe | 500 km | 50 km | 1.5 Mm |
Vall | 300 km | 30 km | 1.5 Mm |
Tylo | 600 km | 60 km | 1.5 Mm |
Bop | 65 km | 25 km | 325 km |
Pol | 44 km | 25 km | 220 km |
Eeloo | 210 km | 25 km | 1.05 Mm |
As for the altitude, the minimum and maximum scanning altitudes are based on the radius of the body it is scanning:
- The minimum altitude is one-tenth of the body radius or 25 km, whichever is higher.
- The maximum altitude is five times the body radius or 1.5 Mm, whichever is lower.
Delta v required for 90° plane change
For the M700 Survey Scanner to function it must be placed in a polar orbit, that is, an orbit with an inclination of 90° passing over both north and south poles. On Kerbin it is possible to launch your rocket into the 90° plane. For other bodies, you can use a mid-course correction to move your closest approach to one of the poles, then perform insertion burn there.
If you are starting in an equatorial orbit, you will need to adjust your inclination to 90° after you have arrived. It takes more energy to perform plane change maneuvers at low altitudes due to the increased orbital velocity. Additionally, eccentric orbits have a much lower orbital velocity at apoapsis than circular orbits of the same altitude. The following table shows the maximum potential delta v requirements to make the 90° turn at the minimum and maximum operational altitudes for the M700. The last column shows the maximum potential delta v requirements if the turn is made at apoapsis while in an eccentric orbit bounded by the minimum and maximum required altitudes.
Planet | Min. altitude | Delta v | Max. altitude | Delta v | Eccentric Delta v |
---|---|---|---|---|---|
Moho | 25km | 1107.4m/s | 1250km | 474.1m/s | 263.9m/s |
Eve | 70km | 4607.2m/s | 1500km | 2725.6m/s | 1962.3m/s |
Gilly | 25km | 20.9m/s | 65km | 14.6m/s | 11.8m/s |
Kerbin | 60km | 3721.6m/s | 1500km | 1834.1m/s | 1268.3m/s |
Mun | 25km | 760.9m/s | 1000km | 329.5m/s | 185.2m/s |
Minmus | 25km | 203.8m/s | 300km | 99.1m/s | 61.2m/s |
Duna | 32km | 1308.6m/s | 1500km | 575.5m/s | 327.6m/s |
Ike | 25km | 489.5m/s | 650km | 218.2m/s | 125.6m/s |
Dres | 25km | 513.4m/s | 690km | 227.8m/s | 130.7m/s |
Jool | 600km | 9252.4m/s | 1500km | 8679.5m/s | 8398.1m/s |
Laythe | 50km | 2671.1m/s | 1500km | 1400.7m/s | 920.0m/s |
Vall | 30km | 1121.4m/s | 1500km | 480.2m/s | 267.3m/s |
Tylo | 60km | 2925.9m/s | 1500km | 1640.3m/s | 1134.4m/s |
Bop | 25km | 235.1m/s | 325km | 112.9m/s | 69.2m/s |
Pol | 25km | 144.6m/s | 220km | 73.9m/s | 47.6m/s |
Eeloo | 25km | 795.8m/s | 1050km | 343.7m/s | 192.7m/s |
Electricity and time required
Each body generates a certain amount of data when scanned, measured in Mits. The data size correlates with the size of the body; Jool produces the most—1200 Mits—and Gilly the least—just 3 Mits. Roughly, the amount of data required for a survey is .205 mits per radial kilometer.
As with transmitting science, more data requires more time and electricity to transmit, and different antennas have different speeds and efficiencies. Also like transmitting science, only one antenna is used at a time, so there is no stacking bonus possible.
The following tables list the size of the scan data for each body, and the time and electricity required to transmit that data with a given antenna.[1]
Body | Kerbol | Kerbin | Mun | Minmus | Moho | Eve | Duna | Ike | Jool | Laythe | Vall | Bop | Tylo | Gilly | Pol | Dres | Eeloo |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Mits | – | 123 | 42 | 15 | 51 | 141 | 66 | 27 | 1200 | 102 | 63 | 15 | 123 | 3 | 9 | 30 | 45 |
Communotron 16 | – | 738 | 252 | 90 | 306 | 846 | 396 | 162 | 7200 | 612 | 378 | 90 | 738 | 18 | 54 | 180 | 270 |
Communotron 16-S | – | 738 | 252 | 90 | 306 | 846 | 396 | 162 | 7200 | 612 | 378 | 90 | 738 | 18 | 54 | 180 | 270 |
Communotron DTS-M1 | – | 738 | 252 | 90 | 306 | 846 | 396 | 162 | 7200 | 612 | 378 | 90 | 738 | 18 | 54 | 180 | 270 |
Communotron HG-55 | – | 820 | 280 | 100 | 340 | 940 | 440 | 180 | 8004 | 680 | 420 | 100 | 820 | 20 | 60 | 200 | 300 |
Communotron 88-88 | – | 1230 | 420 | 150 | 510 | 1410 | 660 | 270 | 12000 | 1020 | 630 | 150 | 1230 | 30 | 90 | 300 | 450 |
HG-5 High Gain Antenna | – | 1107 | 378 | 135 | 459 | 1269 | 594 | 243 | 10800 | 918 | 567 | 135 | 1107 | 27 | 81 | 270 | 405 |
RA-2 Relay Antenna | – | 2952 | 1008 | 360 | 1224 | 3384 | 1584 | 648 | 28800 | 2448 | 1512 | 360 | 2952 | 72 | 216 | 720 | 1080 |
RA-15 Relay Antenna | – | 1476 | 504 | 180 | 612 | 1692 | 792 | 324 | 14400 | 1224 | 756 | 180 | 1476 | 36 | 108 | 360 | 540 |
RA-100 Relay Antenna | – | 738 | 252 | 90 | 306 | 846 | 396 | 162 | 7200 | 612 | 378 | 90 | 738 | 18 | 54 | 180 | 270 |
Body | Kerbol | Kerbin | Mun | Minmus | Moho | Eve | Duna | Ike | Jool | Laythe | Vall | Bop | Tylo | Gilly | Pol | Dres | Eeloo |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Mits | – | 123 | 42 | 15 | 51 | 141 | 66 | 27 | 1200 | 102 | 63 | 15 | 123 | 3 | 9 | 30 | 45 |
Communotron 16 | – | 37 | 13 | 5 | 15 | 42 | 20 | 8 | 360 | 31 | 19 | 5 | 37 | 1 | 3 | 9 | 14 |
Communotron 16-S | – | 37 | 13 | 5 | 15 | 42 | 20 | 8 | 360 | 31 | 19 | 5 | 37 | 1 | 3 | 9 | 14 |
Communotron DTS-M1 | – | 22 | 7 | 3 | 9 | 25 | 12 | 5 | 210 | 18 | 11 | 3 | 22 | 1 | 2 | 5 | 8 |
Communotron HG-55 | – | 6 | 2 | 1 | 3 | 7 | 3 | 1 | 60 | 5 | 3 | 1 | 6 | 0 | 0 | 2 | 2 |
Communotron 88-88 | – | 6 | 2 | 1 | 3 | 7 | 3 | 1 | 60 | 5 | 3 | 1 | 6 | 0 | 0 | 2 | 2 |
HG-5 High Gain Antenna | – | 22 | 7 | 3 | 9 | 25 | 12 | 5 | 210 | 18 | 11 | 3 | 22 | 1 | 2 | 5 | 8 |
RA-2 Relay Antenna | – | 43 | 15 | 5 | 18 | 49 | 23 | 9 | 420 | 36 | 22 | 5 | 43 | 1 | 3 | 10 | 16 |
RA-15 Relay Antenna | – | 22 | 7 | 3 | 9 | 25 | 12 | 5 | 210 | 18 | 11 | 3 | 22 | 1 | 2 | 5 | 8 |
RA-100 Relay Antenna | – | 11 | 4 | 1 | 4 | 12 | 6 | 2 | 105 | 9 | 6 | 1 | 11 | 0 | 1 | 3 | 4 |
Changes
- Initial release
References
- ↑ Some values were found by experiment (in 1.2.2) and the rest were extrapolated from those and antenna stats.Details in this Google Sheet.