Notifications
Clear all
Search result for: id10=WA 0812 2782 5310 Layanan Pembuatan Plafon GRC Board Terpercaya Banguntapan Bantul
| # | Post Title | Result Info | Date | User | Forum |
| RE: Rs232 Comms to maggy | 14 Relevance | 1 year ago | Lynn Edwards | G-882 | |
| 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. | |||||
| Is it possible to extend the cables between the MFAM sensors and module? | 4 Relevance | 2 years ago | Gretchen Schmauder | Hardware | |
| The cables between the sensors and the MFAM module are flexible circuit Boards, and the length is limited to 20 inches. It is possible to remove the MFAM module from the Development kit box and then reconnect it using a ribbon cable. That would allow you to extend the MFAM module and sensors away from the Dev Kit box. Our engineers have tested it to 4 meters. Below are some details about the ribbon cable. The connector on the MFAM unit is Samtec FSH-110-04-F-DH. Its mating connector is Samtec SFMH-110-02-L-D-WT. The easiest option for an extender cable between the MFAM and the Dev Kit is a pair of cable assemblies from Samtec www.samtec.com which has male/female mass terminate connectors put onto a ribbon cable. These connectors plug directly into the MFAM I/O connector and also into the Development Kit. We are comfortable with lengths to 10 feet total. The samtec P/N for this cable is: FFMD-10-T-60.00-01-F-N The ‘60.00’ number specifies the cable length in inches (which equals 5 feet). We have found that there is generally a 2-4 week lead, time since they are made to order and not an off-the-shelf part. (There is another solution as well if you want to make adapter Boards at each end (Dev Kit and MFAM). The exact Samtec mates for the MFAM / Dev Kit connectors are made in PCB mount connectors only, so if you make simple small adapter Board to adapt the samtec connector to another connector of your choice. We've done this with ExpressPCB which is fast and inexpensive. A Board set from ExpressPCB is about $70 including shipping. Our Engineering Team has a design and parts list they can send you if you're interested in going this route.) | |||||
| Geode SGOS Timing | 4 Relevance | 2 years ago | Gretchen Schmauder | Software | |
| The time associated with each data point in a SEG-2 data file generated by a Geode is related to the time of the “trigger” event which was instrumental in the production of the file and its content. The Trigger Master and Trigger Distribution The trigger event occurs at the Geode designated within the Controller software as the Trigger Master. Although all Geodes are capable of being Trigger Masters, there must be one and only one Trigger Master in any properly functioning Geode system. The Controller automatically takes care of this requirement when the designation is made by a user, and when the system is established at the time of Controller start-up based on a previous designation (or a default setting in the case of a “new survey”). All other Geodes in the system will have their Trigger Master circuit disabled. A trigger event can be initiated by an external electrical pulse provided to the trigger input connector of the Trigger Master Geode, or by a command sent via Ethernet from the Controller to the Trigger Master (usually for test purposes), but only when all conditions are satisfied to allow data recording. There is also a special trigger initiation situation, called “self-triggering” which will not be discussed further here. Upon acceptance of a trigger event, the Trigger Master will distribute the trigger signal to all Geodes in the system, itself included, via an RS-485 network that resides within the digital interconnect cabling. (Proper termination of this RS-485 network is automatically taken care of by the Controller.) The trigger signal is propagated through the cabling and Geodes at the nominal speed of 70% of the speed of light, or approximately 2.1x10^8 m/sec. The maximum distance of successful propagation depends on a number of factors such as the number of Geodes involved, the noise environment, the quality of the cables, and the acceptable amount of timing uncertainty for the particular application. Distances approaching or exceeding 1km should be given careful attention in this regard. In a 3-D Geode system involving LTUs, each LTU, unlike a Geode, will reconstruct the trigger signal before sending it on, effectively confining the maximum distance issue to each sub-network separated by LTUs. The penalty is an additional delay of about 100nS for each LTU in the route. The External Trigger Circuit The external trigger input is capacitively coupled, with a 2mS time constant, to the midpoint of a resistive voltage divider. The voltage difference between the two ends of the divider constitute a voltage "window", which size is set by the trigger sensitivity parameter and can range from essentially zero at the highest sensitivity, to about +/- 2.5V at the lowest sensitivity. The Geode will trigger (if enabled) if and when the coupled signal exceeds the window, in either direction (i.e., positive or negative going). The signal, after the capacitor, is clamped by diodes to the range between the trigger signal ground and +5VDC. The trigger detector output is disabled when the system is disarmed, during a parameter change, and during a shot, up to the trigger hold-off time after the end of the shot. The trigger hold-off time is a parameter set by the user. Preceding the coupling capacitor (i.e., essentially the node accessible at pin A of the external connector), there is a 3.3K-Ohm pull-up resistor to +5VDC (relative to pin B). Also a fast transient suppressor clamps the input at about +/-14VDC. It is advised that the DC + AC level of any voltage applied to pin A relative to pin B be kept within the range of +/-7V, giving some margin of safety. If a DC voltage somewhat less than +5VDC is applied when the connector is first mated, the instrument may trigger at that moment. But, subsequently, because of the capacitive coupling, it will trigger on the next positive or negative going pulse that exceeds the window level. If the duration of the applied voltage pulse is less than the record length + delay time + hold-off time, then the Geode will effectively be ready to trigger on the same edge of another similar pulse. Sub-sample Synchronization The Geode supports a sub-sample timing synchronization feature used for synchronizing the data acquisition after a trigger event to the distributed trigger signal, so that subsequent time points will be known to within 1/32 (~1/20 at the fastest two sampling rates) sample interval. It does this by increasing the sample interval at the trigger time by 0 to 31/32 of a sample interval in increments of 1/32, so that the first sample after the trigger would represent a time of one sample interval after the trigger event, with a tolerance within 1/32 of a sample interval. The following samples continue from there at the expected intervals. For example, with a selected sampling interval of ¼ mS and a recording delay of 0mS, the first sample in the recorded file for each channel would represent data at 250 to 258uS after the trigger event. This of course potentially introduces a small discontinuity at the time of the trigger, observable depending on the nature of the channel waveform(s). (The zero-phase anti-alias filter will smear the discontinuity into the nearby samples both before and after, consistent with the bandwidth of the filter.) Sub-sample synchronization can be disabled if it is deemed to be detrimental for the particular application, at the expense of losing the 1/32 interval timing accuracy. Timing Errors The principal errors in Geode timing are of two types: those associated with the trigger mechanism and which are static over the duration of the record, and those associated with the time base and which change over the duration of the record. Excluding the trigger propagation delay mentioned above, the trigger timing uncertainty is about 1uS. The known fixed errors have been lumped together and are reported in the SEG-2 file trace headers as channel SKEW. (The actual channel skew is zero, since all channels are effectively sampled simultaneously, but the SKEW value in the header is used as the only place permitting small timing corrections. Note that the SKEW value for every channel is identical.) If the size of this correction is important to the application, the SKEW value should be added to the calculated time points when the data is being processed. The Geode time base has a +/-15ppm stability over temperature (-20C to +70C) and component variations. Thus time drift relative to absolute time and relative to other Geodes is possible. (However, all channels within any Geode enclosure use the same time base, so there is no relative drift between channels in the same enclosure.) Therefore timing uncertainty increases from that existing at the time of the trigger until the time of the next trigger (or end of record). Special Timing Issues Involved with “Continuous” Recording “Continuous” recording is a method that allows unending 100% time coverage with recorded Geode data. It produces a series of time-overlapped records created by the use of a negative time delay set equal to the record length such that each record consists of completed history at the time of the trigger event. This technique circumvents the problem of data transmission overrunning data acquisition. The principle constraint is that the cycle time from trigger to trigger must always be less than the chosen record length. Otherwise, gaps rather than overlap would result. Commonly it is used with GPSderived triggering in order to provide time-stamping of each trigger event. Upon consideration of the above, it will become clear that the time-stamp associated with a particular trigger event will pertain to the data in the following record, not to the data in the record in which the time-stamp is written. This comes about because the trigger event ends the record. Because there is data overlap between records, the precise trigger point in the following record at which the time-stamp applies can be found by comparison of the data values at the end of the former record with those near the beginning of the subsequent record. The overlapping data will be exactly identical in both records (since they are read from the same memory location, twice). The earliest data in the subsequent record that goes beyond the data of the previous record is the data that is one sample interval (assuming sub-sample synchronization is enabled) past the time-stamp. Note well that this comparison must be made independently for at least one channel of each 8-channel Geode Board set, because the discrete time at which data values are written to the memory buffer, relative to the trigger event, is a function of each individual Board set in the Geode system. Correct GPS Time-Stamping There are differences between various GPS models that can affect accurate time stamping. The 1PPS signal from a GPS has a “timing edge” and return edge, of which only the former is the true whole-second edge. Some models use a rising edge as the timing edge, some the falling edge, and some have it selectable. Consult the GPS manual to determine the definition of its timing edge. As indicated earlier, the Geode can be triggered on either a rising or falling edge. It is important to insure that the Geode is being triggered on the proper edge in order to avoid timing that may be a fraction of a second off. This is expanded upon below. Some GPS units provide a very narrow timing pulse, others one that has a nearly 50/50 duty cycle. For the narrow pulse units, almost certainly it is the leading edge (rising or falling) that is the “timing edge”. This case can be easily handled by using the Geode Trigger Hold-off feature. If a 10-second cycle time is desired, set the Trigger Hold-off time to about 9.5 seconds. In this case, there is a very small chance that the very first trigger could occur on the wrong (trailing) edge, but from then on the leading edge will be used as the triggering edge. If the GPS provides a 50/50 duty cycle edge, and it is not alterable, then the Geode by itself could as easily start on the wrong edge as on the correct timing edge, and continue thusly until restarted. For this case, Geometrics can provide a Trigger Timing Interface Box (TTIB) that will correct the situation. The TTIB can be programmed to respond only to the correct edge (rising or falling), change the polarity if needed, and gate through only one of every N 1PPS pulses, where N is programmable. (The TTIB also incorporates an alarm system that can provide a remote alert if a record is missed.) Another potential issue comes from the variations between GPS models of the time that the serial time string (containing the time value of the associated 1PPS) is issued relative to the 1PPS itself. The Geode Controller attempts to pick the correct serial string based on a calculation involving the known record length, the PC times, and the trigger notification message from the Geodes. But if the GPS issues the serial string at an unusual time (and the time has been seen to vary somewhat with a given GPS unit) then it could pick up the incorrect time, off by 1 second. If rare, it can be subsequently detected and corrected during data processing, but if consistent it may not be easily detected. Again, the TTIB can accommodate the situation by only gating through to the Controller PC the string belonging to the gated-through 1PPS pulse. The Controller Serial Input Time Window can then safely be widened to 2 seconds (assuming the cycle time is more than 2 seconds) if need be, to expand the Controller’s search for the string around the calculated trigger time. | |||||
| How do you convert a Geode from 2D to 3D use? | 4 Relevance | 2 years ago | Gretchen Schmauder | Hardware | |
| 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. | |||||
| Why is the vector sum of 3 compass readings so different from the MFAM reading? | 2 Relevance | 2 years ago | Rui Zhang | Application | |
| If the compass readings are accurate and its 3 axes are perfectly orthogonal to each other, the vector sum of 3 compass readings (x,y,z) should be very close to the MFAM reading, assuming the local gradient is small. However, due to two main reasons, very often customers find a big difference between the vector sum and the MFAM reading. 1. The compass inside the MFAM driver box is NOT a top-rated vector magnetometer, in terms of reading accuracy and axis orthogonality. A top-rated vector magnetometer, capable of producing good vector sum readings, costs thousands of dollars and is much bigger in size. 2. The compass is integrated on the MFAM driver Board, which has many magnetic components. The magnetic field at the compass location is altered by these magnetic components. Although the compass doesn't generate good absolute readings, its relative angle measurement (related to the reading repeatability) is good enough to be used for maneuver noise (heading effect) compensation. | |||||
| RE: Sensor box SD card | 2 Relevance | 2 years ago | Andre Santos | G-864 | |
| Thank you. No, I am asking about the micro SD card on the box Board. | |||||
| Internal QA/QC Performance Testing for the Geode Seismograph | 2 Relevance | 2 years ago | Gretchen Schmauder | Hardware | |
| Geodes do have an option to have a factory installed oscillator Board at extra cost that is used to test the electronics in the Geode. These are not normally installed for most of our users. Users do have the option to run geophone tests using the standard equipped Geode Seismograph that can run line continuity and geophone tests. This can be accessed from the system->tests->Run Geophone/Line tests. Oscillator Boards are typically installed during purchase. Fewer than 5% of the customers purchase that option, that level of QC is typically not necessary. For more information please read the test box manual. We no longer supply the Test Box to external customers. A description of how to run the tests if you use the test box or if you use the internal oscillators is described in Section 2.11.3.1 RUN INSTRUMENT TESTS (OPTIONAL ADD-ON FEATURE) of the manual. The latest standard Geode Operations Manual has more information. You can run the tests outlined in the Geode Operations Manual to detect the bad geophones and spread cables. If you require a calibration certificate for your Geode please consult our Support Note. All Geophysical surveys require interpretation given limited understanding of the site, data from equipment, and ground truthing. Any interpretation provided is the best that can be provided according to the geophysical expertise and experience of the geophysicist. | |||||
| Why can't my computer connect to the MFAM Development Kit through Ethernet? | 2 Relevance | 3 years ago | Rui Zhang | Hardware | |
| 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. | |||||
| G-882 Magnetometer will no longer communicate with a computer | 2 Relevance | 3 years ago | Gretchen Schmauder | Hardware | |
| 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.) | |||||
| Cannot Connect to the MFAM Dev Kit through the Ethernet | 2 Relevance | 3 years ago | Gretchen Schmauder | Hardware | |
| - 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. | |||||
