Search result for:  id10=WA 0852 2611 9277 [[GLORION]] Order Kitchen Set Atas Pria Premium Bekasi

General information The most common symptoms of intermittent connection issues are shown below: D_CY shows a background decay signal is either much higher than normal, and/or C_CY is a flat line (doesn’t decay). Figure 1 Intermittent connection issue. Where is the failure occurring? The two most common places where intermittent issues occur are at the two ends of the Rx cable: the joint between the Rx cable and the Cart and the joint between the Rx cable and the EDA box (orange box). Now we need to identify which joint has the intermittent issue. Set up the MM2x2 in DAM mode. Collect DAM data while keeping the Cart stationary but tapping one joint. Collect another DAM data while tapping the other joint. Analyze the DAM data by plotting the “Monostatic_5” for all 12 Rx channels in Geosoft. The channels having intermittent issues will appear much noisier. If you have MatLab software, you can download the MatLab code to analyze the DAM data. Example plots are shown below. It is obvious that “ZA” channel has the intermittent issue in Figure 2 and “XB” channel is open in Figure 3 (very flat line, no noise at all). Click here to download the code: Attachment : Intermittent_noise_full.zip . If both DAM and IVS data have the same problematic channel(s), we are confident that the intermittent issues observed in IVS data are repeated in DAM data, and by tapping at that location, we are able to identify the intermittent joint. Figure 2 Intermittent "ZA" channel. Figure 3 Open "XB" channel. What to do next? Disconnect the problematic joint and clean the connectors on both sides thoroughly (using an acid brush and a can of compressed air). Reconnect and try the tapping method again. If the problem goes away (no more noisy channels), the intermittent issue is likely caused by dust. If cleaning doesn’t fix the problem, swap out the Rx cable and repeat the tapping method. If the problem goes away, it is likely caused by a bad Rx cable. If there is another Set of EDA and Cart available, swap out the EDA and the Cart to identify the problematic part. If not, use the tapping location to identify the problematic part. Fill out the RMA form at . If it is the Cart, send in the whole system for inspection/repair. You can contact Geometrics for MM2x2 rental if you need to continue your work during the down time. If it is the EDA, we recommend sending in the EDA only. It will save your repair time since it is much faster to unpack/pack/ship the EDA than the whole system. You can contact Geometrics for EDA rental if you need to continue your work during the down time. Warning Please note that this tapping method should ONLY be tried when intermittent issues have been observed in IVS tests. It is NOT recommended to use it as a daily QC test because it does put extra stress on connectors and likely leads to a shortened connector lifetime if applied too often.

Magnetic surveying as a means of estimating depth to basement requires the collection of a data Set that can be processed to yield the average radial power spectra as a function of survey position. The assumption here is that the basement rocks are much more magnetic that the overlying sediment and make a much greater contribution to the observed magnetic anomalies than do the sediments at the longer spatial wavelengths. This type of power spectral analysis relies on accurate data that are extensive in two dimensions relative to both the depth of the basement and the aerial extent of structural high that you seek. If the data are not extensive, the spatial truncation of the data Set will limit power spectra to short wave lengths and this is likely to bias the spectra power average yielding a poor estimate of depth to basement. If this discussion intrigues you, contact Magnetometer Sales for a more thorough discussion.

There are 3 main reasons: 1. Make sure your computer Ethernet port is Set up correctly. (For more details, please refer to Appendix A of the user guide on the USB drive shipped with the Dev Kit) 2. Make sure you are connecting to the correct IP. Sometimes the Dev Kit IP is NOT Set to the default 192.168.2.2, especially if you have more than one Dev Kit. 3. Make sure the Ethernet version of the firmware is loaded in the Dev Kit, instead of the WIFI version. To check to see if the Ethernet version of the firmware is loaded, plug an Ethernet cable into the Dev Kit Ethernet port and the PC Ethernet connector. Look to see if the two Ethernet Status LEDs on the Dev Kit light up. If the Ethernet Version of the firmware is loaded both LEDs will be lit. If not, the WiFi version of the firmware is probably installed. Note that even if the Ethernet firmware is loaded the WiFi adapter board in the Dev Kit will broadcast an SSID even though the Ethernet firmware doesn't look at the WiFi adapter at all. If the LEDs are NOT lit, reload the Ethernet firmware: remove the SD card, copy the Ethernet firmware to the SD card, and power cycle after plug the SD card back into the Dev Kit. For more details, please refer to the instructions provided on the USB drive shipped with the Dev Kit. The firmware can be downloaded from our website You may also try to restart your computer after all above fail.

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

- Make sure your computer Ethernet port is Set up correctly. (Please refer to the instructions provided on the USB drive shipped with the Dev Kit) - Make sure you are connecting to the correct IP. Sometimes the Dev Kit IP is NOT Set to the default 192.168.2.2 if you have more than one Dev Kit. - Make sure the Ethernet version of the firmware is loaded in the Dev Kit (Ethernet LED should be on), instead of the WIFI version. (To load different firmware, please refer to the instructions provided on the USB drive shipped with the Dev Kit). To check to see if the Ethernet version of the firmware is loaded (instead of the WiFi version), plug an Ethernet cable into the Dev Kit Ethernet Connector and into the PC Ethernet connector. Look to see if the two Ethernet Status LEDs on the Dev Kit light up. If the Ethernet Version of the firmware is loaded both will be lit. If not, the WiFi version of the firmware is probably installed. Note that even if the Ethernet firmware is loaded the WiFi adapter board in the Dev Kit will broadcast an SSID even though the Ethernet firmware doesn't look at the WiFi adapter at all. Seeing a broadcast SSID from the Dev Kit is not a verification that the WiFi firmware is installed. You must be able to connect to the WiFi adapter to verify the WiFi firmware is installed.

A customer reached out to support about inconsistent arrival times on stacks using his ES-3000. After stepping through the Set up, he sent the .dat files for us to look into. It was mentioned that the seismograph itself is not capable of randomly triggering early and that there was something external to the instrument causing this 100-200mS early trigger event to occur. Another puzzling factor was that it occurred randomly after a number of shots in auto-stack mode (10). It took some investigating and convincing, but what was finally concluded that the sledgehammer in use had some "flex" in the handle that would cause a "pre-trigger" on the downswing. Once the hammer was replaced the pre-triggers ceased.   Thanks again for the time on the phone today. I really appreciate the guidance and experience of your team.   After the discussion with your team, this led me to do a few more tests on the equipment. This evening, I got 40 stacks with no inconsistency in arrival times.   To close the loop on what I think was going on: I believe the hammer itself may have been the issue, husky hammers have a shock absorber and a sloped handle. Having the trigger strapped in a particular way on the hammer may have been the cause here. See image below:   Attachment : Husky Hammer.png   I used a new hammer (NOT HUSKY) and did not experience the inconsistent arrival times. I will continue to monitor the issue. I appreciate the support from your team! I've individually swapped out all other components (aside from the geode) - this is the only change that seems to have solved the issue.   In summary: My theory is either the shock absorber, or sloped handle caused the trigger to delay, resulting in early arrival times.

Customer had problem connecting Wi-Fi using domain magarrow.net. Solution: Verify the blinking LED patterns are ok: 1) One steady blink and a pause, about once per second - The MagArrow is ready for a WIFI connection from your device. 2) Two short blinks followed by a pause – A device is connected to the MagArrow’s WIFI. If your device or another nearby device is Set to connect automatically, this two-blink pattern might commence quite soon after power-on. If the MagArrow LED blinks normally, please try to connect to 192.168.1.1, instead of magarrow.net. If the LEDs don’t blink in these patterns, refer to the user manual’s troubleshooting section and/or contact support@geometrics.com

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

Thank you for detailed answer. I understood that common practice is separate grounding of each module. Also we will definitely try to shield each geophone with a separate ground, but this will require a large amount of preliminary work. Regarding 50 Hz filtering. We conducted a small experiment in the field to determine the frequencies of background electrical noise captured by geophones. Having Set the minimum possible sampling period for Geod, I recorded 9 consecutive intervals (128 seconds each) of passive observations. This resulted in a total of 19.2 minutes of continuous background noise recording at 125 Hz sampling rate. Then I calculated the signal spectrum from each geophone separately (19.2 minutes of recording), and then obtained the average spectrum for all sensors. For example, the figure in the appendix shows the average spectrum from 24 sensors (red curve) versus the spectrum of an individual geophone (blue curve). In general, I am interested in noise in the 30-50 Hz range. There are no clear peaks at 50 Hz on the frequency response graph. Peaks at 20, 25, 30 Hz are present constantly at any time of the day. In general, the frequency response of passive observation signals increases smoothly with a maximum around 48 Hz. I mean that filtering in some narrow frequency range in this case will not help much in my understanding. Thanks again for the advice. We’ll experiment. Attachment : 24 geophones 19.2 minutes 125 Hz sample rate.jpg

Hi Rui Zhang, Thanks for your prompt response.Loading the ethernet firmware did not work. I have the following observations:-1. Dev kit working well with wifi but not getting connected via Ethernet port.3. I have Set the correct IP address in my PC according to the manual and the other post you ask to refer. It was working well a few weeks before with the same Setting.2. Tried multiple attempt to install Tiva_Interface_EK_Public.bin, every time looks like its getting installed because I did not find the btb.bin in SD card after powering it up. If the Tiva_Interface_EK_Public.bin is installed, dev does not work with wifi as expected because Ethernet software is installed ?3. Also tried btb_192.168.2.3.bin and btb_192.168.2.4 provided inside TIVA_Ethernet_EK V1.1.1 Firmware folder. But no Ethernet led blinking on dev kit. I also tried ping using terminal.4. Also tried the Reset switch but the same status. Thanks a lot

To change the screen brightness on a MetalMapperII Panasonic Toughpad: 1) If you want to type easily, plug a keyboard into the USB socket in the side of the toughpad. Otherwise, use the screen keypad. 2) Open a terminal window (using the Applications menu). 3) Type the following command: sudo bash -c "echo 892 > /sys/class/backlight/intel_backlight/brightness" You will need to enter a password, which is the default password for the standard user. To Set different levels, replace the number 892 with other numbers. 892 is the maximum number allowed; lower numbers will result in a dimmer screen. The change should take place immediately. Then close the terminal window and return to normal use.

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.

GPS Clocks, used in Continuous Recording systems to provide 1 pps signal to trigger seismograph. Also provides GPZDA serial string to stamp records with UTC for Continuous Recording and Self-Triggering systems. Includes cable Set to connect clock to PC, seismograph, and 12V DC power. There are three GPS clock options for the Geode we sell. They are: GS-101B GPS clock from Orca, 1 pps accurate to within 100 ns of the precise time. Includes waterproof antenna with separate electronics module, with display of time and other indicators. Provides time base during loss of satellite lock. Options to provide 1 pps referenced to an IRIG-B generating source and to enclose electronics module in hardened aluminum case (P/N 25374-59). A101 Smart Antenna GPS clock from Hemisphere GPS, 1 pps accurate to within 20 ns of the precise time. Includes waterproof antenna with integrated electronics, with indicator of satellite lock, no display of time. Provides time base during loss of satellite lock. GC200 GPS clock from San Jose GPS, 1 pps accurate to within 1 μs of the precise time. Includes waterproof antenna with integrated electronics, no display of time or other indicators. No time base during loss of satellite lock. The level of precision needed determines which GPS clock is best suited for the job. Typically the GC200 fulfills the needs of 95% of our clients.

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.

Geometrics seismographs are designed to trigger on a contact closure, contact open, or signal input. The trigger circuit has protect from high voltages, but it is possible to damage the input circuit if voltages outside the specified range are connected directly to the input circuit. It is recommended that input signals, or voltages do not exceed + 10 volts. A typical voltage measurement using a hand held volt meter on pins A (+) and B (-) of the 3 pin trigger input connector will be 4.9 volts DC. Voltages less than 4.0 volts may indicate a problem with the trigger circuitry. Often times the unit will continue to operate and trigger, but should be serviced at the next opportunity. If the circuit has been damaged, typical problems will include false triggers, or failure to trigger. To verify the trigger function of the Seismograph, begin by removing the external connector from the trigger input, and short pins "A" and "B" together on the trigger input connector of the seismograph. The unit should trigger each time the pins touched as long as the interval between triggers is greater than the record time or the trigger hold off whichever is longer. It should not trigger unless these pins are touched. If consistent triggering is achieved using this method, then attach the hammer switch directly to the seismograph. Do not put the hammer switch on a hammer yet. Tap the hammer switch cylinder on the edge of a table or other hard object and verify consistent triggering. Watch the stack count on the screen to confirm each tap of the hammer switch results in a trigger of seismograph. Check the trigger hold off Setting and trigger sensitivity Settings. Set the trigger hold off to 0.5 sec. and the trigger sensitivity to 50. If the seismograph is triggering correctly, insert any trigger extension cables between the hammer switch and the seismograph. Repeat the test to confirm consistent triggering. Then attach the hammer switch to the hammer, or other device used for triggering. Make sure the cylinder of the hammer switch is firmly taped to the handle, and the direction of motion is across the diameter of the cylinder. You can also attach a geophone or other signal producing devise at this point and verify proper triggering. If the unit does not properly trigger, contact support with the results of the tests above for assistance.