<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Geometrics Forum - Recent Posts				            </title>
            <link>https://www.geometrics.com/community/</link>
            <description>Geometrics Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Tue, 04 Aug 2026 18:30:17 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Inconsistent arrival times</title>
                        <link>https://www.geometrics.com/community/general-seismograph/inconsistent-arrival-times/#post-1286</link>
                        <pubDate>Fri, 17 Jul 2026 14:41:47 +0000</pubDate>
                        <description><![CDATA[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 mentione...]]></description>
                        <content:encoded><![CDATA[<p>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).</p>
<p>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. </p>
<p>&nbsp;</p>
<p>Thanks again for the time on the phone today. I really appreciate the guidance and experience of your team. </p>
<p>&nbsp;</p>
<p>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. </p>
<p>&nbsp;</p>
<p>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: </p>
<p>&nbsp;</p>
156
<p>&nbsp;</p>
<p>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.</p>
<p>&nbsp;</p>
<p>In summary: My theory is either the shock absorber, or sloped handle caused the trigger to delay, resulting in early arrival times.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Randl Rivera</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/general-seismograph/inconsistent-arrival-times/#post-1286</guid>
                    </item>
				                    <item>
                        <title>RE: Geometrics preliminary MagArrow and MagEx data processing program download</title>
                        <link>https://www.geometrics.com/community/magarrow-software/geometrics-preliminary-magarrow-and-magex-data-processing-program-download/paged/2/#post-1285</link>
                        <pubDate>Sat, 11 Jul 2026 01:23:21 +0000</pubDate>
                        <description><![CDATA[@rzhang Thank very much for the immediate response. Legend!.
All workign again.]]></description>
                        <content:encoded><![CDATA[<p>@rzhang Thank very much for the immediate response. Legend!.</p>
<p>All workign again.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Benjamin Johnson</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/magarrow-software/geometrics-preliminary-magarrow-and-magex-data-processing-program-download/paged/2/#post-1285</guid>
                    </item>
				                    <item>
                        <title>RE: Geometrics preliminary MagArrow and MagEx data processing program download</title>
                        <link>https://www.geometrics.com/community/magarrow-software/geometrics-preliminary-magarrow-and-magex-data-processing-program-download/paged/2/#post-1284</link>
                        <pubDate>Sat, 11 Jul 2026 01:18:23 +0000</pubDate>
                        <description><![CDATA[@benjamin-johnson I uploaded a new config file. Please try it again.]]></description>
                        <content:encoded><![CDATA[@benjamin-johnson I uploaded a new config file. Please try it again.]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Rui Zhang</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/magarrow-software/geometrics-preliminary-magarrow-and-magex-data-processing-program-download/paged/2/#post-1284</guid>
                    </item>
				                    <item>
                        <title>RE: Geometrics preliminary MagArrow and MagEx data processing program download</title>
                        <link>https://www.geometrics.com/community/magarrow-software/geometrics-preliminary-magarrow-and-magex-data-processing-program-download/paged/2/#post-1283</link>
                        <pubDate>Sat, 11 Jul 2026 01:06:19 +0000</pubDate>
                        <description><![CDATA[Hey there, Ive been using this tool with no issues for a few weeks, but not get the &quot;trial period expired&quot; error. Ive redownloaded the config file and placed it in the directory as suggested...]]></description>
                        <content:encoded><![CDATA[<p>Hey there, Ive been using this tool with no issues for a few weeks, but not get the "trial period expired" error. Ive redownloaded the config file and placed it in the directory as suggested here but have had no success. Is there a new licence for this?</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Benjamin Johnson</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/magarrow-software/geometrics-preliminary-magarrow-and-magex-data-processing-program-download/paged/2/#post-1283</guid>
                    </item>
				                    <item>
                        <title>How to use SeisImager 2D seismic profiles to be used in real world models</title>
                        <link>https://www.geometrics.com/community/seisimager-software/how-to-use-seisimager-2d-seismic-profiles-to-be-used-in-real-world-models/#post-1282</link>
                        <pubDate>Tue, 07 Jul 2026 21:32:24 +0000</pubDate>
                        <description><![CDATA[Q. We are now often being asked to provide our 2D seismic profiles to be used in real world models. When the inversion is done it has distance along line and depth/elevation as the output. I...]]></description>
                        <content:encoded><![CDATA[<p>Q. We are now often being asked to provide our 2D seismic profiles to be used in real world models. When the inversion is done it has distance along line and depth/elevation as the output. Is there a way to add real world Northing/Easting coordinates into the data file so it can be more simply reference to the real world location the data was collected?<br /><br />A. Thank you very much for using SeisImager.<br />So you want to add coordinate to 2D Vp or Vs cross sections.<br />You can use GeoPlot to add the coordinates either lat-lon or UTM.<br />GeoPlot can import cross sections from PlotRefa (.vs) and WaveEq (.pvs).<br />Use "Edit", "XY coordinates (latitude-longitude)" to add the coordinates.<br />See GeoPlot manual for more details.<br /><br />https://seisimager.com/download/Geoplot_Manual_v2.0_ENGLISH.pdf <br /><br />If you have several cross-sections, you may use GeoPlot3D to interpolate 2D cross sections to a 3D volume.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Randl Rivera</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/seisimager-software/how-to-use-seisimager-2d-seismic-profiles-to-be-used-in-real-world-models/#post-1282</guid>
                    </item>
				                    <item>
                        <title>RE: Using UART4 to stream data to a Rpi4</title>
                        <link>https://www.geometrics.com/community/mfam-software/using-uart4-to-stream-data-to-a-rpi4/#post-1281</link>
                        <pubDate>Fri, 03 Jul 2026 14:33:52 +0000</pubDate>
                        <description><![CDATA[@easswar Hello,Thank you for you answer, I think it will really help me sort out the communication. When you mention the softwares available for this sync, do you recommend any one in partic...]]></description>
                        <content:encoded><![CDATA[@easswar Hello,<br /><br />Thank you for you answer, I think it will really help me sort out the communication. When you mention the softwares available for this sync, do you recommend any one in particular?<br /><br />Also, I have been trying another option which is to use the ethernet port to transfer the data to the Raspberry Pi 4 (to its ethernet port as well), but I don't seem to receive any signal of any kind. Do you know if that's also already been tested?<br /><br />Again, Thank you.<br />Best&lt;]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Ana Teresa Falcão</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/mfam-software/using-uart4-to-stream-data-to-a-rpi4/#post-1281</guid>
                    </item>
				                    <item>
                        <title>RE: Using UART4 to stream data to a Rpi4</title>
                        <link>https://www.geometrics.com/community/mfam-software/using-uart4-to-stream-data-to-a-rpi4/#post-1280</link>
                        <pubDate>Thu, 02 Jul 2026 22:57:24 +0000</pubDate>
                        <description><![CDATA[HeyThere is no hardware limitation to use UART4 or UART5 for your application. The previous post you read was talking about UART not being implemented in the example code and not specificall...]]></description>
                        <content:encoded><![CDATA[<p>Hey<br /><br />There is no hardware limitation to use UART4 or UART5 for your application. The previous post you read was talking about UART not being implemented in the example code and not specifically about UART5.<br /><br />The existing pipeline does assume a single consumer and you will run into race conditions if you only implement a mailbox_pend for your UART transmission. I would recommend that you either remove the TCP mailbox or create a new mailbox for UART.<br /><br />We have tried UART streaming before without issue. <br /><br />Transmitting the raw binary data will cause issues with some receiver implementations as the values 0x00(NULL char in ASCII), 0x0A or 0x0D which usually denote the end of a serial transmission occur regularly in the MFAM data.<br /><br />Two options to avoid this issue:<br />1. Convert the fields you are interested in to ASCII before sending them over UART.<br />2. Send a fixed number of bytes and implement binary mode on your receiver and request the same number of bytes.<br /><br />One other issue to watch out for in binary mode is if the receiver starts receiving data in the middle of a transmission the transmitter and receiver will be out of sync. There are two handshake signal lines available on the UART4 port on the DevKit called RTS and CTS(Request to Send and Clear to Send). You can use these lines to synchronize the transmitter and receiver. There are software options available as well to implement this synchronization.<br /><br />Hope this helps.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Easswar Balasubramaniam</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/mfam-software/using-uart4-to-stream-data-to-a-rpi4/#post-1280</guid>
                    </item>
				                    <item>
                        <title>Using UART4 to stream data to a Rpi4</title>
                        <link>https://www.geometrics.com/community/mfam-software/using-uart4-to-stream-data-to-a-rpi4/#post-1279</link>
                        <pubDate>Thu, 02 Jul 2026 04:25:11 +0000</pubDate>
                        <description><![CDATA[Hello,
I saw in a previous post that the current firmware only supports MFAM streaming via Ethernet, and that UART5 isn&#039;t supported. I&#039;m modifying the Dev Kit firmware to add TX output on U...]]></description>
                        <content:encoded><![CDATA[<p>Hello,</p>
<p class="font-claude-response-body break-words whitespace-normal">I saw in a previous post that the current firmware only supports MFAM streaming via Ethernet, and that UART5 isn't supported. I'm modifying the Dev Kit firmware to add TX output on UART4 instead, by adding a parallel <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded- px-1 py-px text-">Mailbox_post</code> in <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded- px-1 py-px text-">spiTaskFxns.c</code> to a new UART4 TX task/mailbox, at 460800 bps.</p>
<p class="font-claude-response-body break-words whitespace-normal">Before going further, I wanted to ask:</p>
<ol class=":mb-0 :mt-1 :gap-1 :pb-1 :pb-1 list-decimal flex flex-col gap-1 pl-8 mb-3">
<li class="font-claude-response-body whitespace-normal break-words pl-2">Is there any hardware-level reason UART4 wouldn't work here, beyond it just not being implemented in the stock firmware?</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Does the existing SPI→Ethernet pipeline assume a single consumer, in a way that could cause timing issues if I add a second parallel mailbox post for UART4?</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Has anyone tried UART-based streaming from the Dev Kit before, and if so, any known pitfalls?</li>
</ol>
<p class="font-claude-response-body break-words whitespace-normal">Thanks in advance!</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Ana Teresa Falcão</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/mfam-software/using-uart4-to-stream-data-to-a-rpi4/#post-1279</guid>
                    </item>
				                    <item>
                        <title>MFAM Dev Kit TIVA example code</title>
                        <link>https://www.geometrics.com/community/mfam-software/mfam-dev-kit-tiva-example-code/#post-1278</link>
                        <pubDate>Thu, 28 May 2026 21:47:28 +0000</pubDate>
                        <description><![CDATA[We will provide the example source code for MFAM Dev Kit &#039;as-is&#039; for your reference and review. Please note that we do not provide any technical support, maintenance, debugging, or updates f...]]></description>
                        <content:encoded><![CDATA[<p>We will provide the example source code for MFAM Dev Kit 'as-is' for your reference and review. Please note that we do not provide any technical support, maintenance, debugging, or updates for this code.</p>
<p>Click below to download:</p>
154]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Rui Zhang</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/mfam-software/mfam-dev-kit-tiva-example-code/#post-1278</guid>
                    </item>
				                    <item>
                        <title>Methods for obtaining underwater positioning data during towing MagElement</title>
                        <link>https://www.geometrics.com/community/magarrow-magarrow-hardware/methods-for-obtaining-underwater-positioning-data-during-towing-magelement/#post-1277</link>
                        <pubDate>Mon, 25 May 2026 05:04:52 +0000</pubDate>
                        <description><![CDATA[If there are any practical examples of methods for acquiring underwater position information when towing a MagElement, please let me know.
For example, if acoustic positioning using transpo...]]></description>
                        <content:encoded><![CDATA[<p>If there are any practical examples of methods for acquiring underwater position information when towing a MagElement, please let me know.</p>
<p>For example, if acoustic positioning using transponders is employed, could you explain how it is implemented?</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/"></category>                        <dc:creator>Shinji Matsuda</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/magarrow-magarrow-hardware/methods-for-obtaining-underwater-positioning-data-during-towing-magelement/#post-1277</guid>
                    </item>
							        </channel>
        </rss>
		