Notifications
Clear all
Search result for: id10=WA 0812 2782 5310 Kontraktor Pasang Interior Kamar Estetik Simple Kretek Bantul
| # | Post Title | Result Info | Date | User | Forum |
| A simple mounting configuration to improve MagArrow stability during flights | 6 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: | |||||
| Importing Raw Data From the MagArrow | 3 Relevance | 2 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. | |||||
| How to bulk process MagArrow magdata files? | 2 Relevance | 12 months ago | Rui Zhang | Software | |
| If you have many .magdata files to convert, it is more convenient to use the command-based MagArrowConverter, instead of the Windows-based Survey Manager. The MagArrowConverter installation file can be downloaded from this link: Attachment : MagArrowConverterInstaller-2.2.129.0.zip To use the MagArrowConverter: Run “MagArrowConverterInstaller.exe” to install the converter. It is recommended NOT to install the converter on the default C:\Program Files\ directory since some computer may not allow users to create files in this directory. Open Windows Command (“cmd”) and enter the directory where the converter is installed. Type MagArrowConverter and press Enter key. A short instruction of how to use the converter will be printed out. If you run it from a different directory, type the full path, e.g. "C:\ Geometrics\MagArrowConverter\MagArrowConverter" (assuming the program is installed in C:\ Geometrics\MagArrowConverter\ directory). Note that to change the installation directory, you will have to un-installed the program first and then re-install and set up the directory. A typical example command: …\MagArrowConverter type=MA1 format=csv1 input=”C:\test\test.magdata” output=”C:\test\test.csv” decimation=10 A new csv file with sample rate of 10Hz will be created in C:\test directory from test.magdata file. After you become familiar with MagArrowConverter command, you can write a Simple Batch Script to bulk process MagArrow .magdata files. An example batch code which searches for .magdata files in "C:\MagArrowData" folder and converts all files to .csv files at 10Hz is attached below. Attachment : batch example.zip | |||||
| RE: Geometrics preliminary MagArrow and MagEx data processing program download | 2 Relevance | 1 year ago | Rui Zhang | Software | |
| @ahmed_ramadan_geo Regarding your questions: 1. It removes the maneuver effect due to the swing of the sensor as well. 2. There are really NO best way to do the compensation flight. There are two main requirements for a compensation flight: 1. Include as much roll/pitch/yaw motions as possible. 2. Avoid magnetic gradient. If you can fly the drone very high (>100m) over a low gradient area, a cloverleaf pattern is probably the best (as in traditional airborne surveys in which you can fly high to avoid the local gradient.). But this pattern is hard to fly, especially over a small area. 360-degree turn is Simple and almost guaranteed to have no magnetic gradient in the compensation data since it is over the same location. If the MagArrow doesn't have much pitch and roll motion, 360-deg turn is sufficient. But it doesn't compensate well for pitch and roll maneuver noise (no much pitch/roll calibration). A survey pattern is between the two patterns described above. You may be able to use it, instead of doing a calibration flight. You can use the calibration file generation module to process the cloverleaf pattern. 3. Since the calibration flight is typically short, a base-station may not be necessary. Diurnal field change is usually not significant in a minute. 4. As I mentioned in 1., maneuver correction is also applied here. You can also use LP filter but make sure NOT to apply the heading compensation after the LP filter. | |||||
| Why does data transfer through WiFi become slow? | 2 Relevance | 1 year ago | Rui Zhang | Hardware | |
| If the system has a large amount of survey data, it may affect the data transfer rate. Sometimes a very slow SD card makes the system unresponsive; to the user this can look like a slow/bad network connection. Therefore, it might be useful to clean up the SD card and USB drive. Delete the Geometrics.log file on the USB drive. Clean up the survey data on the SD card: First, make sure that you have all the data that you need off of the SD card. Either download all survey data that you want to keep, or copy all of the contents of the SD card to another drive (perhaps to a PC). Delete all of the data on the SD card, doing one of the following: Use the UI to delete all of the surveys, then use the "Clean old files" button on the Admin page to empty the recycle bin on the SD card. This can be VERY slow, and because the MagArrow has a very Simple web interface, the user will get no useful feedback. On a very full SD card, this process might take 30 minutes or so. Or.... Remove the SD card from the MagArrow and after copying any data that the user still hasn't saved to a PC, format it or delete everything on it, then re-insert it. Be careful not to lose the SD card or to let it drop into the inaccessible spaces in the instrument. If you format the SD card, the ExFAT format is preferable. If the customer can't get the data downloaded from the instrument (takes too long or stops), the data can be imported into a survey in Survey Manager, directly from the SD card (or from the PC hard drive to which the SD card data has been copied). Then the SD card can be cleaned up or formatted. With the new version of Survey Manager (you need to update that also, not just the instrument software), the user can import a large survey, including all of the files in subdirectories, by selecting the "acquinfo.txt" file in the root directory of the survey, from the SD card. More details about how to import/export SD card files using Survey Manager can be found in the post below: SD card files conversion | |||||
| Why does my MagNav app receive no data from the instrument? | 2 Relevance | 1 year ago | Rui Zhang | Software | |
| 1. Make sure the tablet is connected to the instrument via WiFi. 2. The correct connecting sequence is as following: If you start MagNav, and then connect WiFi to the instrument, or if you connect WiFi to the instrument and then start MagNav, then you should receive data in MagNav. If you do anything to disconnect the WiFi, for example by rebooting the instrument, or by walking out of WiFi range, or by using the tablet settings to disconnect WiFi from the instrument, then you will not be able to see data in that original open MagNav session, even if you reconnect to WiFi. The app will not communicate to the instrument through this second WiFi connection. The solution is Simple: close MagNav and then re-open it. MagNav will now communicate with the instrument (as long as the WiFi is connected). 3. This is a common feature in MagNav, which applies to all other MagNav products, such as G-864. | |||||
| Installing Magnetometer Software | 2 Relevance | 2 years ago | Magnetics SW | General Magnetometer Info | |
| Software releases for Geometrics magnetometers usually include multiple softwares to be installed. Check the installation package that you've received and follow the instructions below that apply to your instrument's release: Installing MagNav - For instruments that use the MagNav Android app to acquire data, copy the dot-APK file in the installation package to a USB drive, then follow the instructions in this video from the Geometrics YouTube library: MagNav Installation instructions. Installing the instrument software - To install new software in the instrument (the backpack, or wand, or other physical instrument), remove the USB drive from the instrument and insert it into the USB socket on your Windows laptop or desktop. Run the program setup file; when it asks for a directory to place the file, choose the USB's main or root directory (d:\, or e:\, for example). Select a Simple password (the main purpose of the password is to prevent logins from devices that are looking for open networks), a default channel (4 is a good choice), and let the install complete. Use the "Eject" functionality in Windows file explorer (to make sure that the install files are correctly written to the USB drive), then remove it from the Windows machine, place it into the USB socket in the instrument, and then reboot the instrument. During boot-up, the instrument will install the new software that it discovers on the USB drive. Installing SurveyManager - Execute the setup file from the release, on the Windows computer on which you plan to run the software. Installing MagArrowConverter - If you plan to use the command-line export function for MagArrow data, run the MagArrowConverter setup file. Because this program is executed from a command line, don't use the default installation path suggested by the install; instead, choose a location that will easy to type, and that doesn't include spaces, for example c:\mag, or something similar. | |||||
| 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.) | |||||
| Is there a low cut filter applied, even with all filters set off (to OUT) in the SCS software? | 2 Relevance | 2 years ago | Gretchen Schmauder | Software | |
| Further Elaboration: You might ask this question to try and understand the low frequency response to determine if the Geode amplifiers effectively have a flat response from DC up. Does the Geode go down to DC for example? Answer: We apply anti-alias filters to the data to prevent out of band noise from being introduced into the data. The filters are set with a corner frequency at ¾ of the Nyquist frequency (1/2 the sampling frequency) for almost all of the sampling frequencies. When we sample at 1.5625 uS, the Nyquist frequency is 32kHz and the filters are set at 20 kHz, because of limitations of our electronics. There are two single-pole filters: one analog and one digital. The analog filter is a Simple RC filter with 1uF +/-5% and 100kOhm +/- 1%. We short out the capacitor in the conversion process. The digital filter is software controlled when the option is registered, so it can be switched in or out in the field. It is an IIR Butterworth with a -3dB corner at 0.9Hz for 48ksps sampling, and 0.6Hz at all the lower sample rates. Also, we offer software and hardware options to modify the low end frequency response of the Geode. Low-end bandwidth modification: 1.5 Hz, P/N 28311-37 0.6 Hz, P/N 28147-01 DC, P/Ns 28147-02, 28311-37per system plus | |||||
| Understanding the SGOS Geometry Window GUI | 2 Relevance | 2 years ago | Gretchen Schmauder | Software | |
| The Geometry GUI provides a graphical representation of your survey, along with a wide range of control capability. It is particularly useful when conducting reflection surveys, but can be useful in a wide range of applications. It summarizes, in one Simple view, the physical positions and other attributes of the hardware on the ground, and allows graphical control of these. Below is a typical display of a 96-channel, four-Geode layout. We will first describe the display itself, and follow with a description of its control capabilities. Example Geometry GUI | |||||
| Is MagArrow's "Altitude" with respect to ellipsoid or geoid? | 2 Relevance | 2 years ago | Rui Zhang | Hardware | |
| Altitude refers to Meters Above Mean Sea Level. For both MagArrow I and II, the altitude is ellipsoidal and the earth model is WGS84. For additional information: Overview Reported elevations from MagArrow (and G-864 and MagEx) are the unedited values from the elevation field in the GNSS's GGA NMEA string. That value is the GNSS's calculated height above geoid; height above geoid is the standard meaning of the elevation field in the GGA NMEA string. But what does calculated height above geoid mean? Definitions GNSS - Global Navigation Satellite System GPS - The GNSS operated by the United States. Other systems include GLONASS(Russia), Galileo (Europe), BeiDou (China), QZSS (Japan), IRNSS (India). Ellipsoid - A comparatively Simple or abstract geometric model of Earth's surface. Geoid - A more complex model of Earth's surface that takes the place of what was previously called Mean Sea Level. At any particular latitude or longitude, the geoid's surface may be above or below the ellipsoid's by as much as a few hundred meters, depending on regional and local geography and geology. Reference datum - A specific model of Earth's shape (such as WGS84, EGM96...), including references to specific landmarks. Calculations A particular GNSS, for example the GPS system run by the United States, provides timing data to a receiver to calculate the receiver's position above or below a particular latitude and longitude on the surface of the ellipsoid. The GNSS receiver first uses that timing data to calculate its height over the ellipsoid, and then subtracts from it the local height of the geoid over the ellipsoid (or HAE), to arrive at the local height of the receiver over the geoid (or in old-fashioned terms, elevation over mean sea level): h - calculated height above geoid. This is the value reported in the GGA elevation field. H - height of the receiver over the ellipsoid (calculated from GNSS timing signals) N - local height of geoid over the ellipsoid, or HAE, per a lookup table or other local reference. h = H - N Because the local height of the geoid over the ellipsoid is not provided by the GNSS, it must be provided locally, i.e. by the GNSS receiver, which may contain an internal database from which the local geoid height over ellipsoid (or HAE) can be found, based on the receiver's latitude and longitude. Small GNSS receivers contain small HAE databases, so the HAE value will not be exact. Some small receivers contain no HAE table at all; in this case HAE is deemed to be zero, so that the reported elevation is the uncorrected height over ellipsoid. A user of elevation data from Geometrics' MagArrow, G-864, and MagEx magnetometers may evaluate or adjust the reported values of the GGA elevation field and the GGA HAE field, by comparing the GGA HAE values to another source of local HAE data; this may particularly be useful for GNSSes that report a HAE equal to zero. Geometrics magnetometers do not currently record the values of a VDOP calculation, which offers an additional statistical estimate of the accuracy of the GNSS elevation measurement. | |||||
| How can I connect a GPS to my G-858 Magnetometer? | 2 Relevance | 2 years ago | Gretchen Schmauder | Hardware | |
| It is a fairly Simple task to connect a GPS to a G-858 magnetometer. You can use the External I/O cable assembly and a null modem to connect the G-858 to most GPS receivers. Null modems are available from Geometrics or from local Radio Shack or computer stores. The Null modem pin configuration for GPS receivers that have a data cable compatible with 9 pin IBM PC COM ports has male pins on both sides. The GPS should be set to output NMEA data that contains the $GPGGA sentence. Be sure to set the RS232 protocol to 9600 Baud, 8 Databits, 1 Stop Bit and No Parity. The G-858 must have its serial port set to the same baud rate as the GPS. You can use System Setup -> Com & Field Note String Setup -> Chat Mode to determine whether correct communications have been established. | |||||
| Working with GPX Route Files for the G-864 and other Geometrics Magnetometers | 2 Relevance | 2 years ago | Gretchen Schmauder | Application | |
| Recent Geometrics magnetometers use route files in GPX, KML, and other formats to describe mapped or marked surveys. Various tools – the Survey Manager route designer, online designers, desktop software, etc., can generate different flavors of these files. This document describes the flavor of GPX file used by G-864 and provides a Simple recipe for transforming files generated in one on-line tool, into the flavor used by G-864. These other tools are helpful when creating routes that are not in the rectangular format that is the output of Route Designer. Click on Working with GPX route files for G864 to access the code for the tool. | |||||
| What are the differences between LCS050G (Low-Noise) vs. LCS100S (SuperMag) modules | 2 Relevance | 2 years ago | Gretchen Schmauder | Hardware | |
| Differences between LCS050G (Low-Noise) vs. LCS100S (SuperMag) modules Q. What is the difference between LCS050G (Low Noise) and LCS100S (SuperMag)? Is different firmware the only thing that separates the Low-Noise version from SuperMag version? Or are there mechanical differences in how the sensors are constructed? A.The firmware is different, but that is not the only difference. We also build our sensors in two different groups - A and B - to satisfy the different requirements for each version. Group A satisfies SuperMag specs, while group B meets the Low-Noise specs (please refer to the datasheet). Each SuperMag must have 2 Group A sensors. Q. The sensors in the SuperMag are physically mounted in a configuration to eliminate the dead zones. Could a customer mount their Low-Noise version of the sensors into the same 'no Dead Zone' configuration, then run a Simple script to accept only good data so that if one sensor goes into a dead zone, the firmware will automatically switch to record the data from the second sensor? Obviously Geometrics performs some magic when combining the data in the firmware, but that doesn't necessarily preclude a customer from trying to make a "SuperMag" type system with their Low-Noise sensors, right? A. In principle, yes. Customers can write their own script to combine the readings from each sensor to achieve the dead-zone-free operation. However, smoothing out the combined reading when one sensor’s reading drops out is pretty tricky. In addition, the heading effect will be much worse (determined by the heading effect of individual sensors) if customers choose to combine individual magnetometer readings instead of using the SuperMag dead-zone-free mode. Q. Can I upgrade my Low-Noise sensors to the SuperMag version? Would I have to send my unit to Geometrics' Customer Support or could you simply provide the new firmware so that the instrument behaves like a SuperMag? A. Yes, it is possible to upgrade your firmware, but this process requires you to return the instrument to us. However, Geometrics will NOT guarantee the SuperMag specs in this case since LCS050G still has Group B sensors. The only way to guarantee SuperMag specs is to purchase the SuperMag sensors. Please contact us us for more information. | |||||
| Magnetometer Survey Planning Considerations | 2 Relevance | 2 years ago | Gretchen Schmauder | General Magnetometer Info | |
| A common question many have with magnetic surveys is "How wide of a survey swath does a single magnetometer sensor cover on a single pass?" The answer is it depends on what is being searched for. Magnetometers are passive instruments, meaning they don’t actively send out signals or have a limited swath or depth of exploration. When planning a magnetic survey the grid (line spacing and waypoint spacing) should be designed using the best possible model of the target. There are some general rules of thumb that can be used to determine typical detection ranges for common iron objects. For example, a 10lb sledgehammer has been lost and needs to be found, and assuming this is 10lbs of pure iron, it would be expected to see a 1nT anomaly when the magnetometer sensor passes 6 meters over the top of the tool. Knowing this, survey line spacings should not be any narrower than 6 meters. With a line spacing of 3 meters, the chances of getting a clear anomaly goes up 8 fold as the 10lb iron sledgehammer would be at a minimum a 8nT anomaly vs a 1nT anomaly. In a geological sense, let's say we have a mafic dike intrusion that we believe is running E-W and it extends at least 25 meters in the near-surface in a somewhat linear fashion. It's difficult to model the amount of iron in a geological structure like this, so the survey should be designed to cross the dike perpendicularly every 5 meters or so, making sure to cross over the dike several times. Each pass over the dike may exhibit an anomaly of similar amplitude, and the feature will show up as a clear linear feature in the final processed map. For general mapping of geology, you have a lot of options. Most commonly mineral exploration surveys are done over very large areas, so the line spacing is wider to save time as the lower resolution model that results still accomplishes the task of finding large mineral deposits. If more detail is required, then a more fine-grained survey can be done later. 20m-50m line spacing is typical for mineral exploration surveys. Design a survey grid to completely encompass the area of interest (i.e. make sure you get some data outside of the areas of interest, in case an interesting anomaly lies right along the edge). The founder of Geometrics the late Sheldon Breiner called this the Law of Search, as he often found his targets of interest along the edges of his archaeological magnetic surveys. It is important to make sure the operator of the magnetometer is magnetically clean before surveying with the magnetometer. This means no steel toe boots, glasses or hats with metal fittings, cellphone, belt buckle, etc. Magnetometer data acquisition is fairly Simple, but data interpretation can be complex. You may need a base-station too. Please refer to the Base-Station information. | |||||
