Search result for:  id10=WA 0852 2611 9277 [[Glorion KitchenSet]] Kontraktor Kitchen Set Bagus di Pesona Square Depok

Verify BAUD Rate selected on dip switches 6,7,8 Note: according to a customer this is how the switches are Set as they are attempting a file transfer at 115200 BAUD. Connect the G-857 to the computer using the download cable and a properly installed USB/RS-232 adaptor. (Must have FTDI): Open the MagMap Software. Select Import>G-857/ASCII 1. Enter known Serial Port (My computer is COM4) 2. BAUD 115200 (Switches 6, 7 and 8 off) 3. Set a good location for the file to written to. 4. Leave Download only, open later unchecked. 5. Leave download time out 2. Select OK. On the G-857 press OUTPUT, ENTER when this window opens. BYTES DOWNLOADED will begin to increment. Select OK in the window below: The downloaded Mag file should be displayed: If the download sequence does not happen this way, it is usually a problem with: 1. USB/RS-232 Adaptor not FTDI, or driver not installed. 2. COM PORT assignment incorrect, and/or file destination not valid. 3. BAUD RATE mismatch. 4. Faulty I/O Cable PN 16492-01. 5. Faulty Computer. 6. Faulty G-857 console. Check to make sure that the G-857 is not in Legacy Mode: To check if Legacy Mode is enabled press: AUTO-OUTPUT To turn it off press: AUTO-OUTPUT-CLEAR To Turn on: AUTO-OUTPUT-ENTER If Legacy Mode was on then the recorded data recorded needs to be downloaded as a G-856:

What Affects Geode Trigger Cycle Times? If you're trying to optimize your Geode system for faster trigger cycles—especially in high-repeat environments—there are a few key factors to consider. The goal is to ensure that the system completes its entire cycle (trigger → recording → data transfer → re-arming) before the next expected trigger. Here’s what influences that cycle: 🧠 Core Factors That Affect Cycle Times 1. File Size (Sampling Parameters) Your sample interval and record length directly affect the size of each data file.You can view the resulting file size in the Acquisition Parameters menu.Larger files take longer to transfer, which delays the re-arm process. 2. Data Transfer Rate The Geode typically transfers data at around 450–465 kb/sec.Reducing file size is the best way to reduce transfer time and speed up the cycle. 3. Calibration Frequency By default, the system may attempt to calibrate every N shots, which takes additional time.Go to Options > Calibration and Set "calibrate every N shots" to a large number (e.g., 100000) to prevent unnecessary delays. 4. Recording Delay and Record Length If you're operating in a region with a consistently deep seafloor, you can add a recording delay and reduce record length accordingly.Example: If the water column is always >0.3s, you can apply a delay of 0.2s and reduce record length by the same amount.This trims your file size and speeds up the transfer/re-arm process. ⚙️ Best Practices Use the Auto-Trigger function or Set trigger sensitivity to the maximum value for testing.Monitor the cycle timing and adjust acquisition parameters to stay within your trigger window.It's often an iterative process to find the ideal configuration for your environment.

I have Set up a G-882 system here at Geometrics and am receiving data and sending commands using TeraTerm (any terminal emulation program should work). When in normal use mode the digital add on board sits in front of the G-882 and parses and acts on all commands coming in. There are two versions of the digital Add On board, which are the GP120 and the GP140. The GP140 is a newer version of the digital Add ON board. It is the GP140 digital board that outputs all S/N (and other) information. I first Set up with the GP140 board (the newer version). I find that the ""RESET" command does work - i.e. it goes into BYPASS mode for a couple seconds, then output the S/N and configuration information, and reverts to normal operation with the digital depth and altimeter information. But it only works every other time I send it. The first time nothing happens. Then I send it again and it works. This appears to be a bug in the GP140. For some commands the first command after power up or reset are ignored. The second time (and subsequent commands) are executed. The work around seems to be sending the RESET command twice. I also tried an older G-882 with the GP120 digital board. The Reset (and other commands worked first time and every time. BTW, the digital Board version is in the second line with the S/N information that is sent on power up or Reset. Some questions: 1) My configuration is one G-882 connected to a PC through the white junction box. Is this your configuration, or do you have concatenated G-882's? 2) Can you get the G-882 to accept any commands (like going into Bypass Mode)? I'm wondering if there is a open link in the command line from the PC to the digital board.

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.

The MFAM Development Kit is usually Set to a fixed address of 192.168.2.2 (port 1000). The Ethernet port on the Windows PC must also be switched from DHCP to a fixed IP Address mode in order to connect to the Dev Kit. The procedure for doing this is described in the Dev Kit User Guide. If there are more than one Dev Kits connecting through an Ethernet switch they cannot have the same address. Therefore it is possible to Set the Dev Kit IP address to something other than the default. 192.168.2.3 and 192.168.2.4 firmware are included in the USB drive shipped with Dev Kit and can be downloaded here: For other IPs, please contact Geometrics or reply to this post. You may need to install the Uniflash program from Texas Instruments.

Stacking is a complicated topic, and warrants its own technical note. Which stacking features are available and how they work depends which modes you are in. There are three main mode “groups”: SAVE, CORRELATION, AND STACK. Within those are sub modes whose names indicate their function. Save Autosave Manual Save Correlation No correlation Standard correlation Stack before Correlation Stack after Correlation Random Source Correlation Stack Autostack Replace There is a complicated interplay between the above modes and between these modes and the stack options: Stack polarity display Intermediate Stacks Unstack Delay We will examine each possible combination in rough order of popularity Modes: Manual save , No correlation, Autostack This is the most common configuration used in refraction and downhole surveys. Each shot is automatically stacked Each stacked record is displayed as the stack count increments The stack count continues to increment with each shot until you clear the data, even if you save the data sometime in the process. Stack Polarity can be changed at any time. This is most often used in shear wave surveys where reverse-polarity stacking is required. Unstack Delay gives you the option to unstack the most recent stack; for example, Setting the stack count from 4 back to 3. The data will be held in a temporary buffer for n seconds, during which time you can choose whether to stack or not. If you do nothing, the data will be automatically stacked after n seconds, and unstacking will be no longer be an option for that stack. If Unstack Delay is Set to zero, this feature is disabled. Modes: Auto Save, No correlation, Autostack This is the most common configuration used in impulsive reflection surveys. Each shot is automatically stacked until the Stack ulmit is reached. When the Stack ulmit is reached, the data are saved automatically. Data are automatically cleared and the stack count is reset to one the next time the seismograph triggers after saving the data. Stack Polarity is generally left Set to Positive. displaying intermediate stacks is optional. disabulng this option results in faster production, since the data do not need to be sent over the network with every stack. Modes: Auto Save, Standard Correlation, Stack Before Correlation This is the most common configuration used in swept-source reflection surveys. Each shot is automatically stacked until the Stack ulmit is reached. When the Stack ulmit is reached, the data are saved automatically. Data are automatically cleared and the stack count is reset to one the next time the seismograph triggers after saving the data. Data are stacked in raw, uncorrelated form in the Geodes, and are not sent to the PC until the Stack ulmit is reached. When the Stack ulmit is reached, the stacked raw record is correlated in the Geode (with the most recent pilot), sent to the PC, and saved. Modes: Auto Save, Standard Correlation, Stack After Correlation This is the most common configuration used in Random Source (mini-Sosie) reflection surveys. Each shot is automatically stacked until the Stack ulmit is reached. When the Stack ulmit is reached, the data are saved automatically. Data are automatically cleared and the stack count is reset to one the next time the seismograph triggers after saving the data. Each individual record is correlated with its own pilot and stacked in correlated form in the Geodes. displaying intermediate, correlated stacks is optional. When the Stack ulmit is reached, the stacked, correlated record is sent to the PC and saved. Modes: Auto Save, Replace This is the most common configuration used in Continuous Recording surveys. Each stack is replaced by the previous. If Auto Save is not enabled, the previous stack is lost. If Auto Save is on the Stack ulmit is hard-coded to 1. Each shot is displayed.

1. Hook up Geode in normal configuration to computer Ethernet box. 2. Select Start New Survey. 3. Uncheck Line Tap. 4. Uncheck Aux. 5. Select YES to all pop up menus. 6. Locate lower left corner menu: Seismodule List Window. 7. Note what current loader version under LDVER column of table in Seismodule List Window. (Ex. 2.729) 8. In order to change the LDVER, you must first Set up the table in column F from N/A to X by doing the following: 9. Select System pull down menu from the upper task bar. 10. Select Test. 11. Select Update System Board Bios. 12. Select I Agree. 13. Select Browse. 14. To Set up table to enable loader version update (LDVER) select the file: GEODEFOR3D-1.0.exe. 15. Select Open. 16. Select Start Burning. 17. Select Yes. 18. Cycle power or shut down controller by using the software. 19. Restart the Geode. 20. Repeat necessary steps to get to Seismodule List Window. 21. Verify value in column is now X. 22. Select System pull down menu from the upper task bar. 23. Select Test. 24. Select Update System Board Bios. 25. Select I Agree. 26. Select Browse. 27. Select from Flash Update File Flash3_703&2_42.exe. 28. Select Start Burning. 29. Select Yes. 30. Verify Power LED light on Geode now blinks 3 seconds on 1 second off. 31. Select OK. 32. Cycle power or shut down controller by using the software.

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

Very often I am asked what the difference is between the Lite, Std and Pro versions of the 2D Refraction software licenses. SeisImager/2D Software Packages • Standard version: for use on seismograph with mouse or PC with mouse; allows up to 16K samples per trace, 128 traces per shot, 360 traces per interpretation, and 65 shots per interpretation.• Professional version: for use on seismograph with mouse or PC with mouse; allows virtually unlimited input up to 2M samples per trace, 48K traces per shot, 48K traces per interpretation, and 48K shots per interpretation.• Lite version: included with purchase of Geometrics Windows-based seismographs. For use on seismograph with mouse or PC with mouse; allows up to 16K samples per trace, 64 traces per shot, 51 traces per interpretation, and 12 shots per interpretation.• Demonstration version: for use on PC with mouse, may be launched 15 times; same allowances as Lite version; no printing capability.Note: The number of shots per spread and spreads per interpretation are dependent on the actual trace number used. The Standard and Professional versions are also available for rent. SeisImager Software Suite* Refraction & Surface Wave Data Analysis Software 40 hr - $200 75 hr - $300 250 hr- $500. See Rentals - Geometrics : Geometrics and email rentals@geometrics.com to Set up an order.

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