Search result for:  id10=WA 0821 1305 0400 Perusahaan Hidroseeding Green Project Tanjung Jabung Timur Jambi

Customers can pre-define a survey area using Google Earth Pro and load the KML file into MagNav app. Open Google Earth Pro. Navigate to your survey area and click “Add Path”. Move your cursor and left click to define the outline of your survey area. You can rename your path name and click OK. Select the new path created and right click it. In the pop-up menu, click “Save Place As” to save it as a kml file. Open the Survey Manager. Load an existing Project or create a new Project. Inside the Project, create a new survey. Set up other preferred parameters. Click “Select Route File” and load the saved kml file. Make sure to click “Save” before exiting Plug in a USB drive and copy the Project (.dbt file) to the USB. Eject the USB from your computer to make sure it can be safely removed. Turn on the instrument and the Getac tablet. Make sure the wifi is connected. Plug the USB drive into the Getac tablet. Open the MagNav app. Click “Import Project” to load the Project (.dbt file) from the USB. Enter the Project and enter the survey. On the Navigation page, the path created in Google Earth will be displayed, which can be served as guidelines or outlines for GPS surveys. Marker points can be created similarly for marked surveys.

When you've exported a Project file from MagNav onto a USB drive, be sure to choose the "Eject" function in Android before physically removing the USB drive from the MagNav tablet. If you don't, the Project database may not be correctly saved to the USB drive, and when you open it in Survey Manager you might not find any data. A corollary to this practice is to check the data in Survey Manager before deleting a Project from MagNav; there is no mechanism to un-delete a Project in MagNav. The "Eject" feature varies a little from version to version of Android, but is normally found by swiping for the main Android options menus, then finding the USB drive and tapping on a link to "Eject".

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.

1. Establish WIFI connection between your PC and the MagStation. 2. Open a web browser and type in . Attachment : image.png 3. Click "Delete Project storage" or "Download survey data" to delete or down raw data from micro-SD card. We recommend deleting raw data files after 700 hours data collection. 4. The downloaded survey data is in .magdata format. To convert it to CSV, open Survey Manager and create a new MagStation Project. Inside the Project, create a new survey. Select the survey name, click "Import Data" and then choose the .magdata file. After successful import, click "Export CSV".

If you're exporting data from G-864, MagArrow, or MagEx, using any of the export tools - Quick Conversion, Command-line conversion, or export from a Project and survey in Survey Manager - and you don't get any data, or you think the export is missing some data, follow these steps: Verify that you have records to export: In survey manager, verify that the survey has data in it: there's a "Measurements" field in the survey details. For MagArrow, if you're using Quick Conversion or the command line program, you will need to create a Project and survey in Survey Manager and import the .magdata file into it. If you don't have any data records, then verify that you've opened the correct file. If you have records, but they just don't seem to be exporting, then choose to export invalid records and records without locations The export functions in Survey Manager allow you to choose this option with the "Filter" choices: Look in the exported file for records without locations (no GPS) and with invalid records; they are not included in the default exports. For MagArrow, export with 1000 samples/second. If you are troubleshooting an export at a decimated rate (e.g. 20 samples/second) then note that a single invalid record in the 1000 samples/second original data may invalidate about 1/2 second of data; in a 20 samples/second MagArrow decimation, a single 1000 samples/second invalid record will invalidate about 10 decimated results.

The crossover distance is the distance from the source at which the critically-refracted energy from the next deepest layer overtakes the critically-refracted energy from the previous layer (in the two-layer case, the energy traveling through layer 1 is direct, not refracted energy, but the idea is the same). This is illustrated by the following animation: The direct energy (red) is the first-arrival energy at the first six geophones. However, by the seventh geophone, the direct energy is overtaken by the critically-refracted energy (green). The reciprocal of the slope of each segment is equal to the apparent velocity of the material. If there were a third, even faster layer, a third slope and second crossover distance would eventually appear on the travel time graph. The crossover distance, along with the velocities indicated by the slopes of the segments, are used to determine the refractor depth.

1. When the transmitter is turned on, the red power light (or Green light in later versions) comes on and stays on. The blue light will go into a rapid flashing pattern then settles into a three-flash sequence, for example short-long-short or short-long-long, or something like that. Is that what the transmitter is doing? If not, there are three possible causes of the problem and this will require require swapping parts: Defective dipole cable or shorting plugs are two potential problems. The best test is to plug the shorting plugs directly into both ends of the Transmitter and turn on. If this works, then add one dipole cable and turn on again. Then add the second cable and power up. If failure occurs with just the shorting plugs then the most likely problem is a battery with a shorted internal cell. This will look like it is fully charged when you measure it with a volt meter, but will not be able to supply the current required to drive the transmitter. Swap out batteries to test. If swapping the batteries does not resolve the issue and you never get the blue light to start flashing you may have a bad Tx and it would need to be returned to Geometrics. 2. When the receiver is turned on the red power light will come on, then the blue light will flash rapidly, then the blue light will turn off waiting for the receiver to phase lock onto the Tx. Once it locks onto the transmitter the blue light will start flashing at once per measurement. Depending on how conductive the ground is and how far apart the Tx/Rx separation is you may have to wait up to a minute to get the lock. Try it with about a 5 meter separation between the end of the dipoles, i.e. the equivalent to having a 5-meter rope between them. The Rx should lock and start flashing within about 20 seconds. If it never locks on even though the Tx's blue light is flashing then there may be something wrong with the receiver and it would need to be sent back. Remember that the transmitter blue light has to be flashing first. If the Tx is not working the Rx will never detect it and start flashing. 3. With the Rx turned on, even if the blue light is not flashing, when you look at the OhmMapper Test screen on the console do you see the message: Setting Gain, Phase A, Phase B or something similar being updated on the screen every second (or twice per second with the old systems)? If so your console is communicating with the receiver. If not, you have no communication between the Rx and the console so you could have a bad dipole cable, bad optical wand, bad console cable, or a bad receiver. If you have spares of any of these items you can troubleshoot the problem. If you have no spares then you will need to send the system back here for evaluation by submitting an RMA request.

Overview The MagEx instrument and the MagNav app both display information about the state of the instrument's battery. Battery state and reporting exist in bands according to percentage of remaining battery capacity: 30% or higher:The instrument has good remaining capacity.The LED on the instrument's power switch glows a solid Green.MagNav displays the battery percentage or voltage in black text on a white background. Between 20% and 30%:The instrument has capacity to survey for additional time, but if you will be surveying a significant amount more, start thinking about changing the battery.The LED on the power switch is blue.MagNav displays the battery percentage with a blue background. Between 5% and 20%:You can continue to survey, but the battery is running low and you should consider changing the battery soon.The LED on the power switch is red.MagNav displays the battery percentage with a red background, and periodically notifies you that the battery is running low. Below 5%:The battery is running low, and the instrument may turn off at any time in order to preserve battery health. You should change the battery as soon as possible. Temperature-related effects:Battery performance also changes as the temperature of the battery changes; as the temperature of a battery falls, the voltage it supplies also decreases, and the total energysupplied by the battery decreases. This means that in cold weather a battery will not last as long as in hot weather. The battery percentages reported in the instrument are adjusted for the effect of temperature; at a given battery voltage a cold battery will display a higher percentage than a warm battery will report. The effects of colder temperatures are not normally permanent; as a battery warms up, its output voltage and energy return to higher levels. Notes about the calculation:The MagEx instrument includes 2 batteries, and each battery includes 3 separate cells. Battery percentages are calculated from only one battery in the instrument - either the single battery if only one is connected, or from the better battery if two batteries are connected. Reported battery percentage is an estimate, based on measurements of the behavior of healthy batteries in instruments in the field and in the lab. Battery performance may change as a battery ages and as the temperature changes. The best practice for batteries is to use 2 healthy, fully charged batteries, and replace them both when the percentage falls below 20%.

In general, avoid stainless steel parts. If you have to use stainless steel parts, make sure it is made of SS316. To make sure that the parts are magnetically clean, you can set up the MFAM Dev Kit in the gradiometer mode. 1. Have the two sensors separated by 20cm or more. 2. Turn on the gradient reading (green curve) in MagViewMFAM. 3. Place the part 10cm to one sensor and 30cm to the other. 4. Rotate the part while monitoring the gradient curve. Make sure you don't have any magnetic parts (such as keys, cell phone, watch) with you while doing this. 5. The peak-to-peak difference in the gradient curve (you may have to adjust the gradient scale if the curve wraps on screen) is the magnetic signature of the part at 10cm. 6. For the magnetic signature at different distances, scale the reading as 1/R^3. For example, if the part will be 20cm away, its magnetic signature should be 1/8 of of the reading at 10cm.

Color representationRed: data collected by a survey magnetometer, such as a MagArrowGreen: survey data we are interested inBlue: base-station data Magnetic field is a function of location (r) and time (t): B(r,t)In general, we are only interested in magnetic field as a function of location: B(r). Ideally, we set up one magnetometer at each location of interest and measure the magnetic field at different locations at the same time. This method removes the time dependence.However, the method requires many magnetometers. The common practice is to move one magnetometer around. In this case, B(r,t) is collected since it takes time to move the magnetometer. To remove the time dependence, a base-station is required. Assume the base-station reading at a fixed location R1 is B1(R1,t) = c1 + B1(t), where c1 is a constant, depending on R1. We hope to achieve the base-station correction B(r,t) - B1(R1,t) = B(r) – c1.For a single base-station location, c1 can be ignored since it is a constant offset applied to the whole survey area. In another word, B(r) and B(r) – c1 generate the same survey color map. For large scale surveys, it is impossible to have a single base-station location, since it is not economical and magnetic field time dependence is also regional.Now we obtain base-station data sets at different locations: B1(R1,t), B2(R2,t), B3(R3,t)… When the base-station correction is applied, Bi(r,t) - Bi(Ri,t) = Bi(r) – ci. In general, ci are different. Therefore, Bi(r,t) - Bi(Ri,t) can NOT be combined directly into a single data base unless constant offsets are applied to achieve Bi(r). A typical combined 5-day survey without applying offsets is shown below. These constant offsets are hard to measure, unless multi base-stations are set up. However, they can be calculated based on the overlapping areas between two data sets since the readings in the overlapping areas must be the same, assuming the same AGL (above ground level). With this method, the new combined data is shown below. Geometrics offers an auto survey combination program for MagArrow and MagEx customers. Attachment : Survey_Data_Stitch_Auto_V3.zip

Hello all, I'm currently working on a software Project to integrate some Maggy's more effectively into our system. I see that when the magnetometer starts up it outputs it's serial number as well as some other useful information. I'd like to know if there is a serial command I can send that will initiate that information? A reset command for instance. I've read the manual and it suggests that I can simply send 'Reset' via a serial console but have tried it multiple times and have not been able to receive that initial startup string when I try it. Am I missing something? Or is there a terminator that I'm missing? I know it's possible as the digital console software can live reset the Maggy while it's sending data (same as what I want to achieve) so any help you could offer would be very gratefully accepted. For your information I've used multiple serial console softwares none of which have worked

Hi guys, I need MFAM live data streaming from ethernet or serial UART5 for my Project. Initially, I am planning to write a piece of code using C++ that reads the data from one of the ports and prints it on the terminal. To be sure that data is present on UART5, I connected this port to the USB port of my laptop using a suitable cable and tried to monitor data using Putty with different baud rates but found nothing. Is data streaming available on UART5 by default? or do I need to enable it? I can see data on the ethernet port using MagView. Ethernet port uses TCP protocol. Is there any way to enable UDP on the ethernet port? In case I write code to read the ethernet port using TCP then please suggest a suitable reference to start. Thanks a lot

A sample MagEx data can be downloaded from the link below: Attachment : MagEx_Sample_Data.zip The csv data file is directly exported from a MagEx Project file (.DBT file, which is the raw binary MagEx data) using Survey Manager software. No additional data processing is applied. The data can be displayed in any plotting software, as shown below.