Search result for:  id10=WA 0812 2782 5310 [[PANDAWA]] Layanan Wallcovering Support Full Kartasura Sukoharjo

MFAM-SuperMag (LCS100S) or MFAM-SX (LCS100X) can be configured to achieve dead-zone-free operation, in which the combined sensor is always active no matter where in the world and which direction the device is oriented. To set up the dead-zone-free configuration: Make sure the MFAM is in the "One Sensor (No Dead Zone) run mode. If not, please refer to "How to switch the operating mode for SuperMag MFAM" on our website found here: How to switch the operating mode for SuperMag (LCS100S) MFAM?. Orient two sensors orthogonally. The ideal relative orientation is shown below (also in the test report in the USB drive shipped with the unit). This configuration works for both the "Low Heading Error" and the "Low Noise" modes. Low Heading Error Only mode If you only wish to run the sensor in the "Low Heading Error" mode (note that SX MFAM does NOT have the "Low Noise" mode), a simpler configuration, as shown below, can also achieve the dead-zone-free operation.

Surveying using a randomized impulsive source (called "mini-Sosie), such as a Wacker, is Supported by the StrataVisor NZ and the Geode along with the Urban Seismic software and hardware package. Read our Random Source Seismic Surveying Manual In general, mini-Sosie surveying is useful in noisy, urban environments, particularly in close proximity to roads where near-field noise suppression can be used effectively.

The batteries used in the portable magnetometer instruments are lead-acid gelled electrolyte batteries. The choice of this type of battery was dictated by their non-magnetic internal construction. We “magnetically compensate” these batteries to further reduce their magnetic signature. We do this with bucking coils which are mounted against the battery surfaces and then an external wrap applied. The batteries should be charged using the charger furnished with the instrument. These chargers are Fully automatic and designed to do the best job of charging and maintaining the batteries for long life. All of the chargers are equipped with lights indicating when the battery is being charged and when the charging cycle is completed. The battery packs will provide the most operating cycles when they are Fully charged after each use. The number of operating cycles can vary from 250 cycles to above 1000 cycles depending on how deep the discharge was and how soon the battery is charged after use. A 30% discharge per cycle may result in a lifetime of 1000 cycles or more, whereas a 100% discharge per cycle can result in only 250 cycles. As a rule the magnetometer will shut down when the battery is discharged to about 20% of Full voltage. This is to ensure proper shutdown of the instrument. It is very important to recharge the battery as soon as possible after use so the maximum life can be expected from the pack. If the discharged pack is left to charge “when we get back from the field” the pack can suffer from “sulphation”. This is a high-resistance buildup in the battery which may render the battery unusable. If a battery of this type must be stored for an extended period, it must be stored in a Fully-charged condition. If such a battery is stored discharged and subject to below-freezing conditions, it is likely to freeze and be subsequently unusable. All Lead-Acid batteries must be maintained when in storage. This means that the user must recharge each pack at least once a month. Lead Acid batteries will self-discharge due to stray internal resistances, causing very small drain currents. Thus the maintenance requirement for monthly recharging is critical to long battery life. Do not leave the charger on all the time during storage. Also it is very important to use discharge the batteries on a regular basis otherwise the lifespan will be severely shortened. For more information contact our Support Department.

This is for customers of the ATOM 1C and ATOM 3C seismographs (“ATOMs”) and is intended to provide guidance on ways to improve the download behavior via Wi-Fi. The ATOMs should be removed from any enclosure and positioned with the metal base plate down and relatively close to the Access Point (AP), which will increase the signal strength available to both the Atom’s and the AP. The RF environment during data download can impact whether the ATOMs can connect and on how fast they download data. Other RF devices in the vicinity (i.e., Bluetooth, wireless cameras, other APs, etc.), can cause slower download time. If there is a microwave oven operating nearby, this can disrupt communication between the ATOMs and the AP. If you are having trouble getting the ATOMs to connect and download, try setting up the AP and laptop and then turning on the ATOMs one-by-one waiting for it to connect before turning on the next unit. Another thing that will improve download performance is connecting the laptop directly to the AP with an Ethernet cable. This eliminates all of the RF traffic between the laptop and AP. Summary: *Choose a location with the least amount of RF traffic. *Remove all ATOMs from any enclosure and place each ATOM on its aluminum bottom base plate. This is the best position for the internal antenna. *When possible, everything should at least be on the same level, off the ground, on a desk or table. The AP can even be placed higher than the ATOMs. *Each ATOM should have at least a foot of space around it and be within 10 to 12 ft. of the Access Point. Being too close to the AP is also not ideal. *The ATOMs and AP should be in the same space or room with the AP being centrally located. *Connect the Access Point directly to the Laptop with an Ethernet cable rather than using a WiFi connection between the laptop and AP. *The Access Point can connect up to 30 devices at once, but it is advisable to connect 24 or fewer. The time it takes to connect will vary from ATOM to ATOM. If after 1.5 minutes an ATOM is not found, restart the ATOM. If after another 1.5 minutes an ATOM is still not connected, it could be a hardware issue. Contact Support@geometrics.com Download time may also vary from ATOM to ATOM. If an ATOM disconnects or takes a much longer time than other ATOMs to download (>30 minutes) it could be a hardware issue. Contact Support@geometrics.com

Some of the Geometrics magnetometers include a feature, called the "File Cleanup Utility", that removes files that are no longer useful from storage on the instrument. The feature's accessible from the "Support" link in the Settings page in MagNav. You might be reading this post because that page directed you to read this post before using the utility. [This feature is not the same as the feature in MagNav to delete all of a survey's data. That feature removes information only from the database on the Android tablet, and doesn't remove any data in the instrument]. How do I use this feature? If this is the first time you've used this feature, please read the rest of this post before proceeding. Make sure that you're connected via WiFi to the instrument Go to the Settings page in MagNav Select the "Support" link. If your instrument Supports this feature, the Support page will include a link to "Delete project storage". Tap it. You should see a list of projects, with a name and a "Delete project" button for each project. This feature cleans up the data for all of the surveys in a project. Delete any projects for which you don't want to keep the in-instrument data. You can delete the data for all of the projects that you see, but there's no harm in leaving the files for projects that you're still using. Some projects will show a name similar to this: [c3bd]. These are early projects, in which the user-assigned name was not used in the instrument storage. It's OK to remove the data for these projects. Why do I need to do this? The magnetometers that use MagNav first store data on the instrument, and then sync (or download) the data to MagNav. Some instruments, for which this technical approach makes the instrument more reliable - MagEx, e.g. - do this automatically. Other instruments, such as those that allow disconnected acquisition (e.g. MagStation), store the data until the user re-connects to the instrument and manually starts the sync process. The data stored in the instrument is not of any use once it's been downloaded, but because deletion is slow and for other technical reasons, it's left on the file system in the instrument. As it accumulates, it could eventually interfere with the performance of the instrument and should therefore be deleted. Will this delete any data in the database in MagNav? No, this feature doesn't remove or change any data in the database in MagNav. When should I use this feature? Here are a few guidelines: Run this utility after deleting an entire project. Run this utility after completing a long field survey. Run this utility while doing other instrument maintenance. Run this utility after you've collected "a lot" of data. Run this utility when you have the impression that the instrument is unresponsive or is behaving sluggishly. Will anything bad happen if I forget to do this? Probably not any time soon; the storage systems on the instrument are large and quite efficient. Geometrics tests instruments with amounts of data consistent with several years of regular use, and which show no performance issues relating to file storage performance. But don't let it go forever; follow the guidelines above. Can I delete data for projects that I'm still using? Yes, you can, as long as the data has already been synced to the instrument (that happens manually with MagStation and automatically with the other instruments). Once the data has been synced and is visible in MagNav, its presence in the instrument storage is no longer needed.

You will need to test the magnetometer on the dry deck or in your shop. Connect the G882 directly to the junction box and use the black power supply Geometrics provided. Verify operation. If working go to step 4. If the magnetometer is not working, then there is a hardware failure. There is nothing that can be done in the field at this point. Arrange to send it in by requesting an RMA number from our RMA page. If the magnetometer is working then "dies" it would be useful to have the data from the "diagnostic survey". Review this document: Diagnostic Surveys for CM221 Counter Equipped Magnetometers r-2. Connect on board power supply (if different than the supply already checked) Verify operation. If it fails record Diagnostic Survey. If working proceed. Connect Deck cable (if applicable). Verify operation. If it fails record Diagnostic Survey. If working proceed. Connect Tow Cable. Verify operation. If it fails record Diagnostic Survey. If working proceed. Deploy magnetometer under normal configuration. Begin a Diagnostic Survey. If the mag doesn't work under tow then there is a problem with the tow cable/interconnections. Please take these steps and record the data when a failure occurs. (Best to record data all the time and then when it fails send the data to our Support Team, you can contact them through the Support contact form. Make sure you are specific as to the conditions/configuration if/when it failed.)

Hi All,   We are using the Teensy 4.1 as a logger (Adafruit GPS is linked with the Teensy) for the MFAM SX. Below is the code for the Arduino IDE (Teensy), for people who might find it useful, Roi   #include <NativeEthernet.h> #include <SD.h> // ---- NETWORK CONFIGURATION ---- byte mac[] = { 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED }; IPAddress ip(192, 168, 2, 10); IPAddress mfamIP(192, 168, 2, 2); uint16_t mfamPort = 1000; EthernetClient client; // ---- PACKET STRUCTURE ---- const int PACKET_SIZE = 1380; const int SAMPLE_SIZE = 32; const int HEADER_SIZE = 16; const int NUM_SAMPLES = 40; const int SD_CHIP_SELECT = BUILTIN_SDCARD; uint8_t buffer[PACKET_SIZE]; int bufferPos = 0; // ---- SD CARD ---- File logFile; bool sdReady = false; unsigned long sampleCount = 0; unsigned long fileStartTime = 0; char filename[32]; // ---- AUXILIARY CHANNEL STORAGE ---- double gyroX = 0, gyroY = 0, gyroZ = 0, gyroT = 0; double accelX = 0, accelY = 0, accelZ = 0, accelT = 0; double compassX = 0, compassY = 0, compassZ = 0, compassT = 0; // ---- GPS FROM ADAFRUIT MODULE ON SERIAL1 (Pin 0 = RX) ---- char gpsBuffer[256]; int gpsBufferPos = 0; char gpsString[128] = ""; char gpsDate[12] = "00/00/00"; char gpsTime[16] = "00:00:00.000"; bool gpsFix = false; uint8_t tsStatus = 0; // ---- OUTPUT CONTROL ---- // Set to 1 to log every sample, 10 for 100Hz, 20 for 50Hz, etc. const int DOWNSAMPLE_FACTOR = 1; // 50 Hz output int downsampleCounter = 0; // How many minutes per file. Set to 10, 20, 60, etc. const int FILE_MINUTES = 10; // ---- LED INDICATOR ---- // Off = starting up // Very slow blink (every 3 sec) = connected and logging // Fast blink (4/sec) = connected but no data arriving // Solid on = no SD card // 3 quick flashes then pause = cannot connect to MFAM const int LED_PIN = 13; unsigned long lastBlinkTime = 0; bool ledState = false; unsigned long lastDataTime = 0; // ---- FUNCTION PROTOTYPES ---- void createNewFile(); void parsePacket(uint8_t* pkt); void parseAuxChannels(uint8_t* sample, uint16_t frameID); void readGPS(); void parseGPRMC(char* sentence); void writeSample(unsigned long timestamp, uint16_t fiducial, double mag1, uint16_t mag1s, double mag2, uint16_t mag2s, uint16_t sysStatus); int16_t toSigned16(uint16_t val); void createNewFile() { static int fileNumber = 0; // On first call, find the next available file number if (fileNumber == 0) { char testName[32]; for (int i = 1; i <= 99999; i++) { snprintf(testName, sizeof(testName), "MFAM_%05d.txt", i); if (!SD.exists(testName)) { fileNumber = i - 1; // Will be incremented below break; } } } fileNumber++; snprintf(filename, sizeof(filename), "MFAM_%05d.txt", fileNumber); logFile = SD.open(filename, FILE_WRITE); if (logFile) { logFile.println("Mag 1,Mag 2,Fid,SysS,Mg1S,Mg2S,Gyro X,Gyro Y,Gyro Z,Gyro T,Accel X,Accel Y,Accel Z,Accel T,CompassX,CompassY,CompassZ,Comp T,Date,Time,TS Status,GPS"); logFile.flush(); fileStartTime = millis(); Serial.print("Logging to: "); Serial.println(filename); } else { Serial.print("ERROR: Could not create "); Serial.println(filename); } } void setup() { Serial.begin(115200); delay(2000); // Start GPS serial port (Adafruit Ultimate GPS defaults to 9600 baud) Serial1.begin(9600); pinMode(LED_PIN, OUTPUT); digitalWrite(LED_PIN, LOW); memset(gpsString, 0, sizeof(gpsString)); // Initialize SD card if (SD.begin(SD_CHIP_SELECT)) { sdReady = true; Serial.println("SD card ready."); } else { Serial.println("WARNING: No SD card found. Serial output only."); digitalWrite(LED_PIN, HIGH); } // Initialize Ethernet Ethernet.begin(mac, ip); if (Ethernet.hardwareStatus() == EthernetNoHardware) { Serial.println("ERROR: No Ethernet hardware found!"); while (true) {} } Serial.print("Teensy IP: "); Serial.println(Ethernet.localIP()); Serial.print("Connecting to MFAM at "); Serial.print(mfamIP); Serial.print(":"); Serial.println(mfamPort); if (client.connect(mfamIP, mfamPort)) { Serial.println("Connected to MFAM!"); } else { Serial.println("Connection failed!"); } Serial.println("Waiting for GPS fix..."); if (sdReady) { createNewFile(); } Serial.println("Mag 1,Mag 2,Fid,SysS,Mg1S,Mg2S,Gyro X,Gyro Y,Gyro Z,Gyro T,Accel X,Accel Y,Accel Z,Accel T,CompassX,CompassY,CompassZ,Comp T,Date,Time,TS Status,GPS"); } void loop() { // Always read GPS data from Serial1 readGPS(); if (!client.connected()) { Serial.println("Disconnected. Reconnecting..."); if (sdReady && logFile) { logFile.flush(); } for (int i = 0; i < 3; i++) { digitalWrite(LED_PIN, HIGH); delay(100); digitalWrite(LED_PIN, LOW); delay(100); } delay(1400); client.connect(mfamIP, mfamPort); if (client.connected()) { lastDataTime = millis(); } return; } while (client.available()) { buffer[bufferPos] = client.read(); bufferPos++; if (bufferPos >= PACKET_SIZE) { parsePacket(buffer); bufferPos = 0; lastDataTime = millis(); } } // LED patterns if (sdReady) { if (millis() - lastDataTime > 3000) { if (millis() - lastBlinkTime > 125) { ledState = !ledState; digitalWrite(LED_PIN, ledState ? HIGH : LOW); lastBlinkTime = millis(); } } else { if (millis() - lastBlinkTime > 1500) { ledState = !ledState; digitalWrite(LED_PIN, ledState ? HIGH : LOW); lastBlinkTime = millis(); } } } // New file every FILE_MINUTES minutes if (sdReady && logFile && (millis() - fileStartTime > (unsigned long)FILE_MINUTES * 60UL * 1000UL)) { logFile.close(); createNewFile(); } } // ---- GPS READING FROM ADAFRUIT MODULE ON SERIAL1 ---- void readGPS() { while (Serial1.available()) { char c = Serial1.read(); if (c == '$') { gpsBufferPos = 0; } if (gpsBufferPos < (int)sizeof(gpsBuffer) - 1) { gpsBuffer[gpsBufferPos] = c; gpsBufferPos++; } if (c == '\n' || c == '\r') { gpsBuffer[gpsBufferPos] = '\0'; if (strncmp(gpsBuffer, "$GPRMC", 6) == 0 || strncmp(gpsBuffer, "$GNRMC", 6) == 0) { // Save Full sentence for logging strncpy(gpsString, gpsBuffer, sizeof(gpsString) - 1); gpsString[sizeof(gpsString) - 1] = '\0'; // Remove trailing newline/carriage return int slen = strlen(gpsString); while (slen > 0 && (gpsString[slen - 1] == '\n' || gpsString[slen - 1] == '\r')) { gpsString[slen - 1] = '\0'; slen--; } parseGPRMC(gpsBuffer); } gpsBufferPos = 0; } } } void parseGPRMC(char* sentence) { // $GPRMC,HHMMSS.sss,A,lat,N,lon,W,speed,course,DDMMYY,... char copy[256]; strncpy(copy, sentence, sizeof(copy) - 1); copy[sizeof(copy) - 1] = '\0'; char* token = strtok(copy, ","); int field = 0; while (token != NULL && field < 10) { switch (field) { case 1: // Time if (strlen(token) >= 6) { snprintf(gpsTime, sizeof(gpsTime), "%c%c:%c%c:%s", token[0], token[1], token[2], token[3], token + 4); } break; case 2: // Fix status gpsFix = (token[0] == 'A'); break; case 9: // Date if (strlen(token) >= 6) { snprintf(gpsDate, sizeof(gpsDate), "%c%c/%c%c/%c%c", token[0], token[1], token[2], token[3], token[4], token[5]); } break; } token = strtok(NULL, ","); field++; } // Update GPS bits of tsStatus tsStatus = (tsStatus & 0x0C); // Keep MFAM PPS bits (3,2) tsStatus |= 0x01; // Bit 0: RMC sentence received if (gpsFix) { tsStatus |= 0x02; // Bit 1: GPS fix valid } } // ---- MFAM DATA PARSING ---- int16_t toSigned16(uint16_t val) { if (val > 32767) return (int16_t)(val - 65536); return (int16_t)val; } void parseAuxChannels(uint8_t* sample, uint16_t frameID) { uint8_t auxID = (frameID >> 11) & 0x07; uint16_t aux0 = sample[16] | (sample[17] << 8); uint16_t aux1 = sample[18] | (sample[19] << 8); uint16_t aux2 = sample[20] | (sample[21] << 8); uint16_t aux3 = sample[22] | (sample[23] << 8); switch (auxID) { case 1: compassX = toSigned16(aux0) / 0.01333333; compassY = toSigned16(aux1) / 0.01333333; compassZ = toSigned16(aux2) / 0.01333333; compassT = toSigned16(aux3) / 128.0 + 25.0; break; case 2: gyroX = toSigned16(aux0) / 16.384; gyroY = toSigned16(aux1) / 16.384; gyroZ = toSigned16(aux2) / 16.384; gyroT = toSigned16(aux3) / 512.0 + 23.0; break; case 4: accelX = toSigned16(aux0) / 16384.0; accelY = toSigned16(aux1) / 16384.0; accelZ = toSigned16(aux2) / 16384.0; accelT = toSigned16(aux3) / 512.0 + 23.0; break; default: break; } } void writeSample(unsigned long timestamp, uint16_t fiducial, double mag1, uint16_t mag1s, double mag2, uint16_t mag2s, uint16_t sysStatus) { char tsStr[12]; snprintf(tsStr, sizeof(tsStr), "%d%d%d%d%d%d%d%d", (tsStatus >> 7) & 1, (tsStatus >> 6) & 1, (tsStatus >> 5) & 1, (tsStatus >> 4) & 1, (tsStatus >> 3) & 1, (tsStatus >> 2) & 1, (tsStatus >> 1) & 1, tsStatus & 1); char sysHex[8], m1sHex[8], m2sHex[8]; snprintf(sysHex, sizeof(sysHex), "%04X", sysStatus); snprintf(m1sHex, sizeof(m1sHex), "%04X", mag1s); snprintf(m2sHex, sizeof(m2sHex), "%04X", mag2s); char line[512]; snprintf(line, sizeof(line), "%10.4f,%10.4f,%4d,%s,%s,%s,%10.2f,%10.2f,%10.2f,%5.1f,%8.5f,%8.5f,%8.5f,%5.1f,%8.1f,%8.1f,%8.1f,%5.1f,%s,%s,%s,%s", mag1, mag2, fiducial, sysHex, m1sHex, m2sHex, gyroX, gyroY, gyroZ, gyroT, accelX, accelY, accelZ, accelT, compassX, compassY, compassZ, compassT, gpsDate, gpsTime, tsStr, gpsString); if (sdReady && logFile) { logFile.println(line); if (sampleCount % 1000 == 0) { logFile.flush(); } } if (sampleCount % 500 == 0) { Serial.println(line); } } void parsePacket(uint8_t* pkt) { // Get PPS bits from MFAM system status uint16_t firstSysStatus = pkt[HEADER_SIZE + 2] | (pkt[HEADER_SIZE + 3] << 8); uint8_t mfamPPSbits = (firstSysStatus >> 12) & 0x0C; tsStatus = (tsStatus & 0x03) | mfamPPSbits; for (int i = 0; i < NUM_SAMPLES; i++) { int offset = HEADER_SIZE + (i * SAMPLE_SIZE); uint16_t frameID = pkt[offset] | (pkt[offset + 1] << 8); uint16_t fiducial = frameID & 0x07FF; uint16_t sysStatus = pkt[offset + 2] | (pkt[offset + 3] << 8); uint32_t mag1raw = pkt[offset + 4] | (pkt[offset + 5] << 8) | ((uint32_t)pkt[offset + 6] << 16) | ((uint32_t)pkt[offset + 7] << 24); double mag1 = mag1raw * 0.05 / 1000.0; uint16_t mag1status = pkt[offset + 8] | (pkt[offset + 9] << 8); uint32_t mag2raw = pkt[offset + 10] | (pkt[offset + 11] << 8) | ((uint32_t)pkt[offset + 12] << 16) | ((uint32_t)pkt[offset + 13] << 24); double mag2 = mag2raw * 0.05 / 1000.0; uint16_t mag2status = pkt[offset + 14] | (pkt[offset + 15] << 8); parseAuxChannels(pkt + offset, frameID); sampleCount++; downsampleCounter++; if (downsampleCounter >= DOWNSAMPLE_FACTOR) { downsampleCounter = 0; writeSample(millis(), fiducial, mag1, mag1status, mag2, mag2status, sysStatus); } } }

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 MagArrow product link under firmware/software download: 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

Hi Ahmed, Depending on the corner frequency of the LPF, some heading related noise may be removed already by the LPF. The heading correction (the Full maneuver compensation, not line-leveling) will then add the noise back to your data. In your flow chart, I would do heading correction before LPF. In addition, I would use raw data of 10Hz instead, because at certain parts of world, the AC power is at 50Hz. There will be 50Hz alias into 20Hz raw data.

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

Here are a few additional details relating to the measurement of elevation: GNSS AccuracyAccuracy depends on multiple aspects of the GNSS system: among them are clock accuracy, atmospheric effects, and satellite geometry. Satellite geometry"Satellite geometry" refers to how the currently visible satellites are distributed in the sky - close to each other or scattered around. The best satellite geometry includes satellites that are near the axes on which you hope to locate your receiver; for example, to locate your receiver on the East/West axis, it's helpful to have good reception from satellites low in the sky in the East and in the West. If you also have satellites that are low in the sky near the South and North horizons, you will have good accuracy on the horizontal (latitude/longitude) plane. It's best to have satellites scattered around the sky, overhead as well as near the horizon all around. HDOPMagArrow records HDOP, a standard measure of satellite geometry's effect on horizontal (or latitude/longitude) accuracy. A smaller number (less than 1.0 is very good) indicates that the visible satellites are in good positions to contribute to accuracy. Vertical AccuracyThe reason that GNSS systems aren't as accurate on the vertical axis as on the horizontal axes is that no satellites are visible in a Full half of that axis: the half that is below the horizon. Consequently, vertical accuracy is on average about half that of horizontal accuracy; calculated offset from true elevation is on average about twice that as on the horizontal axes. While on average HDOP can therefore be used to estimate VDOP (the similar measurement of the effect of satellite geometry on the vertical axis), that estimate is only a rule of thumb; it is possible to have an excellent HDOP, reflecting very good horizontal satellite geometry, while having poor vertical satellite geometry. In those cases, good HDOP does not indicate good VDOP. Keeping in mind that possibility, a combination of good HDOP and many satellites in view usually indicates good VDOP. Practical effects Some data processing techniques (upward continuation, for example) can include elevation as an input. Customers who are considering using GNSS elevation in those techniques should conduct a careful analysis of their data and develop test routines to verify that all their data meet the requirements of the technique and its application to a particular survey. Some customers who require very accurate elevation data incorporate LIDAR data and drone elevation data into their analyses.

The de facto "standard" for high-resolution reflection is 40-Hz geophones. The 40-Hz cutoff will filter out much of the ground roll, allowing you to use the maximum gain even at near offsets, and taking advantage of the Full dynamic range of the recording system.

You can 3D print a dead-zone-free sensor holder from the attached .step file. Attachment : Sensor Holder Perm Shell_Thin Wall_v10.zip

Geometrics recommends that customers purchase the G-882 and altimeter together from Geometrics to ensure Full factory testing and compatibility. For more details about this, please click here.