Notifications
Clear all
Search result for: id10=WA 0859 3970 0884 Jasa Interior Design Backdrop TV Dari HPL Di Nglipar Gunungkidul
Page 1 / 2
Next
| # | Post Title | Result Info | Date | User | Forum |
| RE: Half Rigid Suspension Design | 4 Relevance | 2 years ago | Rui Zhang | Hardware | |
| A CAD file of MagArrow can be downloaded here if you want to Design such a mounting structure. Attachment : MagArrow Shell.zip Please note that the external helical antenna is NOT in the CAD file. | |||||
| Half Rigid Suspension Design | 4 Relevance | 3 years ago | Rui Zhang | Hardware | |
| With the provided 10-feet suspension cables, the magnetic noise due to most commercial drones can be ignored. However, some MagArrow customers experience stability issue, especially in windy conditions. For a small number of drones, the MagArrow can be attached to the landing gear Directly with acceptable noises (line-levelling is still required in data processing). For most drones, however, this configuration causes too much noise. A half rigid mounting Design may solve this problem. It has 2 rigid bars with hinges on one side and 2 flexible cables on the other. On the ground, the rigid side folds to the side. While in the air, gravity will keep the MagArrow further away from the drone. Drone noise can be greatly suppressed since the noise follows 1/R^3. A factor of 2 increase in the separation can lead to a factor of 8 decrease in noise. Please make sure the hinges and the rigid bars are made of non-magnetic material. | |||||
| A simple mounting configuration to improve MagArrow stability during flights | 3 Relevance | 2 years ago | Rui Zhang | Hardware | |
| Many of our customers have found out that widening the attaching points of a MagArrow can greatly improve its stability (reducing swings) during flights. If you are interested in Designing a customized mounting fixture, a CAD file of a MagArrow baseplate can be found here: | |||||
| Magnetometer Exploration Depth | 3 Relevance | 3 years ago | Gretchen Schmauder | General Magnetometer Info | |
| In a general sense, the exploration depth of a magnetometer is unlimited. It is certainly sensitive to the Earth's field and this is generated in the Earth's Core, some 5000 km beneath our feet. But for practical purposes, the depth of exploration is determined from survey results by the spatial width of the magnetic field anomaly as observed at the Earth's surface. For Discrete objects, the depth of exploration is nominally 1/2 of the width of the magnetic anomaly. This topic is Discussed in our Portable Magnetometer Operation Manual. This Manual covers many topics related to survey Design and interpretation including exploration depth. As you will see, survey Design will have a large influence on the depth of investigation. | |||||
| RE: Half Rigid Suspension Design | 3 Relevance | 2 years ago | Rui Zhang | Hardware | |
| @ellipsis You are welcome! From the front of the front eyelets to the rear of the rear eyelets, it is a little more than 27 inches. So, your CAD reading is corret. | |||||
| RE: Half Rigid Suspension Design | 3 Relevance | 2 years ago | Kevin Wiebe | Hardware | |
| @rzhang thank you. I’m not sure if I’m reading the CAD file correctly. Is it 27.288 inches between the front and rear eyelets for cable attachments? | |||||
| RE: Half Rigid Suspension Design | 3 Relevance | 2 years ago | Rui Zhang | Hardware | |
| @ellipsis We would recommend the rigid part to be ~ 1m. So with the landing gear, the MagArrow is about 1.5m from the drone. | |||||
| RE: Half Rigid Suspension Design | 3 Relevance | 2 years ago | Kevin Wiebe | Hardware | |
| Great idea. What would be a recommended minimum Distance below the drone? | |||||
| Is it possible to extend the cables between the MFAM sensors and module? | 2 Relevance | 2 years ago | Gretchen Schmauder | Hardware | |
| The cables between the sensors and the MFAM module are flexible circuit boards, and the length is limited to 20 inches. It is possible to remove the MFAM module from the Development kit box and then reconnect it using a ribbon cable. That would allow you to extend the MFAM module and sensors away from the Dev Kit box. Our engineers have tested it to 4 meters. Below are some details about the ribbon cable. The connector on the MFAM unit is Samtec FSH-110-04-F-DH. Its mating connector is Samtec SFMH-110-02-L-D-WT. The easiest option for an extender cable between the MFAM and the Dev Kit is a pair of cable assemblies from Samtec www.samtec.com which has male/female mass terminate connectors put onto a ribbon cable. These connectors plug Directly into the MFAM I/O connector and also into the Development Kit. We are comfortable with lengths to 10 feet total. The samtec P/N for this cable is: FFMD-10-T-60.00-01-F-N The ‘60.00’ number specifies the cable length in inches (which equals 5 feet). We have found that there is generally a 2-4 week lead, time since they are made to order and not an off-the-shelf part. (There is another solution as well if you want to make adapter boards at each end (Dev Kit and MFAM). The exact Samtec mates for the MFAM / Dev Kit connectors are made in PCB mount connectors only, so if you make simple small adapter board to adapt the samtec connector to another connector of your choice. We've done this with ExpressPCB which is fast and inexpensive. A board set from ExpressPCB is about $70 including shipping. Our Engineering Team has a Design and parts list they can send you if you're interested in going this route.) | |||||
| Why does it take so long for my MagArrow GPS to lock? | 2 Relevance | 2 years ago | Rui Zhang | Hardware | |
| 1. Make sure the MagArrow top cover (the curved side) is facing up and under a clear sky. 2. It may take up to 20 minutes for the GPS to lock during the initial power up. Afterwards, the GPS stores the location information for a while (~40 minutes for MagArrow I and ~ 2 hours for MagArrow II) without the power so that it can lock much faster than 20 minutes (~2-3minutes) during subsequent powerups. 3. If the powerup locking time is significantly longer or intermittent GPS dropouts are observed during flight: MagArrow I will need to be sent back to Geometrics for repair. MagArrow II customers may choose to unscrew the external helical antenna (or attach the external helical antenna) and check whether the longer-than-normal locking time or the intermittent issue goes away. MagArrow II has an independent internal and external antenna Design. When the external helical antenna is attached (unattached), the system switches to the external (internal) antenna automatically. | |||||
| Magnetic Anomaly Model of a Point Source | 2 Relevance | 3 years ago | Gretchen Schmauder | General Magnetometer Info | |
| The Gammas2.exe is a Windows program that can be used to estimate the amplitude of the magnetic anomaly produced by a steel object that has not been magnetized. In other words, the program assumes that the magnetic anomaly is solely induced by the earth’s field according to the object’s susceptibility. The program uses a susceptibility of 10 cgs units to compute the anomaly amplitude. The estimate produced by Gammas2.exe can be used as a tool to help Design magnetic surveys and help interpret survey results. Geometrics no longer updates the Gammas2.exe software, and we offer no guarantee that it will work on your computer. | |||||
| Importing Raw Data From the MagArrow | 2 Relevance | 3 years ago | Gretchen Schmauder | Software | |
| Raw Data MagArrow data is imported into Survey Manager in the form of .MAGDATA files, downloaded from the MagArrow. The .MAGDATA file contains measurements from Different sensors inside the MagArrow: 1000Hz magnetometer readings; accelerometer, gyro, compass, temperature readings; and GPS info. MFAM assigns a fiducial number, or “FID” to each magnetometer reading, in a cycle from 1 to 1000 that repeats every second. In the instrument, the magnetometer readings and the GPS sentence data are synchronized so that the “FID-1” magnetometer record is matched with the GPS location and timing information. Exports to CSV and Geosoft file formats 1000Hz un-filtered export The 1000Hz export provides the original raw magnetometer data plus some simple interpolations: • Magnetometer reading: The raw magnetic field values are exported without application of a filter. [While these raw measurements are the output of a filter inside the MFAM sensor: a 9-pole Butterworth low pass filter with a -3dB point at 400Hz, that filter is considered part of the sensor for this description.] • Auxiliary sensors: Gyro, accelerometer, and temperature are acquired once per every 5 magnetometer readings, and are reported only when acquired. Compass readings are acquired one per every 10 magnetometer readings and are reported only when acquired. • GPS NMEA sentence: Reported with the associated FID-1 mag record. A few individual fields from the GPS are also broken out from the GPS sentence and reported separately, without interpolation. • Interpolated GPS fields: Time, date, latitude, longitude, and track (course over ground) are linearly interpolated between GPS readings. Decimated exports Each of the exports at frequencies from 10 Hz to 100 Hz is a decimation – data are filtered by a low-pass filter and then down-sampled to the target sample rate. Each low-pass filter (a Different one for each decimation) is a symmetric finite impulse response (or FIR) filter, with the following Design goals: • -3dB attenuation at 0.75 * Nyquist frequency (e.g., the -3dB point for the 10Hz decimation is 3.75Hz) • Significant attenuation of 50Hz and 60Hz signals. • Reasonably flat response in the pass band. Linear phase (or zero phase, or constant group delay) filters. These filters are not Kalman filters. The filters are applied to fields in the decimations as follows: • Magnetometer readings: Magnetometer readings are decimated: the FIR is applied, then the data are down-sampled to the target rate. • Aux sensors: Aux sensors are first up-sampled to 1000Hz by linear interpolation of values between individual readings (which occur once every 5 mag readings for gyro, accelerometer, and temperature, and once every 10 mag readings for compass). Then these 1000Hz values are decimated in the same process as the magnetometer readings. • Latitude and longitude are first up-sampled to 1000Hz by linear interpolation of values between successive GPS data (once per second), then these 1000 Hz values are decimated in the same process as the magnetometer readings. • Time, date, and track are linearly interpolated as in the raw, unfiltered 1000Hz export. Merging filtered and unfiltered data. Some of the values in an individual line of data are filtered: mag readings, aux sensors, etc. Other measurements are not filtered: time and date, GPS sentences, record counters, and the simple interpolated fields. These two sets of values – filtered and unfiltered, must be reported in individual lines that contain values of both types. The question “How should the two sets of values be matched?” is addressed as follows: A decimation filter has a center. For example, a single filter result that weighs 499 individual measurements running from record number 752 to record number 1250 (in DSP terms, it is the result of the convolution of 499 input values with 499 filter weights), is centered on record number 1001. The result is the “filtered value of record 1001”. In a single line along with this value should be the other filtered results centered on record number 1001 plus the unfiltered raw and interpolated values that were recorded as part of the original, raw record 1001. The down-sampling part of decimation involves keeping some results and Discarding others; down-sampling from 1000Hz to 100Hz includes Discarding 9 out of 10 results. During exports, Survey Manager keeps the “FID 1” record, because it includes the original GPS information, then Discards the next 9 records (if it’s a 100Hz decimation), and then repeats the pattern, each time starting with FID 1. If you have questions about the MagArrow decimations, please contact your Geometrics account manager. | |||||
Page 1 / 2
Next
