T3RRA Troubleshooting guide

• Tablet issues
• Tablet screen freezes (Panasonic)
• Surface Pro tablet not updating or freezing
• Mouse Pointer flickers across the screen randomly
• Windows are opening and closing on the tablet randomly.
• T3RRA software does not automatically start when the tablet boots.
• Can’t find an onscreen keyboard.
• T3RRA software will not install
• T3RRA software is not updating
• In-cab tablet is too small to design on effectively
• Tablet is in ‘Tablet Mode’ and you can’t find the desktop icon for your T3RRA Software
• Access to the port ‘COM X’ is denied.
• iGrade dropping out during work
• Software Issues
• T3RRA Xxxxx is not happy :-( error.
• Out of memory errors
• T3RRA software crashes without an error message
• Unauthorized Access Exception on program exit
• ‘Out of memory’ error when saving
• Setup & Installation issues
• Unable to install T3RRA software.
• Unable to import RCD or ADAPT files directly from flash drive.
• Version manager not working correctly
• Software licence details disappearing after updating
• InCab Installer will not open
• John Deere related issues
• Notes for Dual or Triple Receiver systems.
• Diagnosing guidance line location issues
• Error “Incorrect MD5 Hash” occurs when loading project
• Dual GPS scraper is not level.
• Height control jumping in and out of Auto
• Settings
• Changing language has no effect.
• Unable to change language.
• Error reading settings.
• GPS issues
• No GPS signal is being received from iGrade.
• No GPS signal is being received when connected directly to a GPS receiver.
• Baud rate is set correctly but messages from iGrade are still garbled.
• Vertical Performance Issues (GPS drift).
• No GPS in T3RRA Cutta v1 when using dual scrapers in iGrade v1.
• You are getting GPS data but the quality is not RTK.
• GPS data stops and COM port number has changed.
• You have bench mark locations but they are not in Latitude and Longitude.
• GPS issues with Windows 11
• Sudden Vertical Shifts/Jumps
• Surveying issues
• Collected survey data is blue and red only.
• Elevation Offset during surveying.
• Drain Survey mode performed in error.
• Elevation points not appearing correctly or with voids.
• Surveying at heights close to sea level results in an incorrect field surface.
• Designing issues
• Levees are jumbled and crossing over.
• Imported SWP+ ditch track names are too long.
• Drain Design freezing and/or producing jagged profile view OR Small Field design has jagged edge and difficult to see changes in elevation.
• Attempting to save a PDF report throws an error.
• Markers not visible.
• My cut/fill map is totally a single color representing no cut and no fill.
• There is an ‘offset’ cut area beside my drain.
• Drain Design error message ‘not downhill all the way’
• Drain Design error message ‘drains were affected by this operation’
• Cross Slope issues
• Cross slope control is not working.
• Cross Slope not working and Front and Rear Error displays are visible.
• Paddle pots are backwards for manual control of cross slope.
• Scraper cross slope appears to be the opposite of what it should be.
• Implementing issues - iGrade alone
• Troubleshooting performance.
• Implementing issues with iGrade (will occur without T3RRA connected)
• Bi-Directional error in iGrade.
• Blade continuously loads on one side.
• Poor “on grade” performance.
• Engaging auto causes the scraper to raise into the air.
• Scraper is “washboarding”.
• Implement blade moves to an extreme position when placed in Auto.
• Blade not staying on grade & acting inconsistently.
• The implement blade does not seem to follow the design surface.
• Implement blade is intermittently jumping up or attempting to deep dive.
• Erratic performance during drain implementation.
• iGrade is indicating that Remote Commands are not being received from T3RRA software or indicating ‘No Surface Defined’.
• Error from grade values do not match on iGrade and T3RRA software.
• User cannot turn “Grade On” with iGrade 2.
• Poor as-applied coverage.
• Implementing issues - T3RRA
• Bi-Directional error in T3RRA.
• Tractor position icon is far above or below the surface.
• Tractor position icon does not adjust when you zero against a benchmark.
• Map icon on the T3RRA software screen lags behind the actual field position.
• ‘As-Applied’ not updating correctly
• Project has moved N/S or E/W.
• My drain design is no longer present in the ‘Apply’ wizard step.
• My drains have ‘bumps’ in them that weren’t present when I designed them.
• Implement is offset a large amount after 'zeroing'

Tablet issues

Tablet screen freezes (Panasonic)

Symptoms: 

The screen of the tablet PC has frozen and is not responding to inputs such as pressing on the screen or the mouse (if one is attached).

Your tablet becomes slow and sluggish.

Cause:

The Tablet may not have enough available memory.

Windows or the T3RRA software needs updating.

If you have connected your tablet to the Wi-Fi hotspot previously, the tablet will retain internet access credentials and connect to the internet. Automatic updates of the operating system, or software can start without your knowledge.These can slow operations.

If you have surveyed the field in ‘drain mode’ rather than ‘field survey mode’ the tablet can become sluggish when implementing (due to continual calculations positioning the displayed position relative to the large drain line created).

Solutions:

1. Confirm tablet running T3RRA meets minimum requirements:

• Windows 10

• CPU: Intel i5

• RAM: 8GB, HDD

• HDD 128GB (minimum)

2. Perform updates for T3RRA and Windows:

T3RRA needs to be updated regularly in order to perform at its best. When connected to a good internet connection, click on 'Check online for updates' in T3RRA Settings Application tab and the newest version will install. (T3RRA alerts when a new version is available if connected to the internet). Windows & .NET need to be regularly updated. Windows 10 is best updated using the Windows 10 Update Assistant downloadable from the Microsoft website. Perform a hard restart after updates are completed.

3. Create manageable projects:

Break large projects into smaller projects that are less taxing on the computer.

4. Check for applications running in the background:

Make sure there is nothing else running on the computer and bogging it down (you can go into Task Manager and look at the performance charts).

5. Report detailed information to T3RRA if the problem persists.

• Does the tablet freeze? 

• Does the software freeze? 

• Does the freeze 'unfreeze' at some time?

• Can the software be killed manually or does the machine have to be re-started?

Please provide this information when reporting an issue.

Surface Pro tablet not updating or freezing

Symptoms:

Surface Pro tablet does not update T3RRA software completely and/or freezes.

Cause:

Windows updates require hard restart to take effect.

High speed internet connection required.

Solution:

Microsoft suggests executing the “Two Button Shutdown” after restart and before signing in. This is only to be used on Surface Pros. Do not use this process on Surface RT, Surface 2, or Surface 3. Using this two-button shutdown process ensures that your Surface is turned off completely. Here’s how:

Step 1:    Press and hold the power button on your Surface for 45 seconds and then release it.

Step 2:    Press and hold the volume-up button and the power button at the same time for at least 20 seconds and then release both. (the screen may flash the Surface logo or something else, but continue holding the buttons down)

Step 3:    After you release the buttons, wait 10 seconds.

Step 4:    Press and release the power button to turn your Surface back on.

Things we have also found useful:

Connect to the hotspot on your cell phone for a possible higher speed internet connection.

Make sure there is nothing else running on the computer and bogging it down (you can go into the task manager and look at the performance charts).

Break large projects into smaller projects that are less taxing on the computer.

Mouse Pointer flickers across the screen randomly

Symptoms:

When the tablet starts the on-screen mouse jumps randomly about the screen. Windows may open and close as the mouse clicks on desktop or program icons. Input is difficult due to competition from the ‘crazed and possessed’ mouse arrow. You will likely receive a pop-up error about your desired com port being taken already when you try to open your T3RRA software.

Cause:

When booting, some tablets check the serial port for the presence of a serial mouse (a common type of mouse prior to PS1 and bluetooth mice). If a stream of GPS data is present the operating system can mistake it for mouse data and direct the data to the onscreen pointing device. As the data is not mouse data it simply results in random movement and clicking. This also monopolizes the serial port, which then cannot be used by T3RRA software. Note: Even after implementing the registry fix below a ‘Windows Update’ can sometimes cause this fix to be reverted and the problem will re-appear.

Solutions:

1. Go to ‘Settings > Advanced’ and disable the serial mouse (Version 2 software).
   

2. Always start the tablet before the tractor is turned on. If the tablet starts prior to any incoming GPS data the problem will not occur.

3. Search for the serial mouse with the Windows ‘Device Manager’ and disable it.

4. Permanently disable serial mice using the Windows Registry. Instructions for doing this can be found online on pages like: http://www.taltech.com/support/entry/windows_2000_nt_serial_mice_and_missing_com_port

NOTE: Do not alter the Windows Registry unless you are competent to do so and understand the possible issues of doing so. If in doubt contact your dealer or T3RRA.

5. Request that your dealer uses their T3RRA Installer software to correct the issue. This software will perform the Registry fix action. The relevant tab in the software is the “Tablet Setup” tab. 

Windows are opening and closing on the tablet randomly.

Symptoms:

Windows are opening and closing randomly as if someone was tapping on desktop or program icons. 

Cause:

It is possible that the touch screen is malfunctioning. A crack in the screen may be a good indicator. This happens whether or not GPS data is streaming into the tablet COM port (see Mouse pointer flickers across the screen randomly.)

Solutions:

Tablet repair may be required. Alternatively, disable touch input (via the Human Interface Devices section of the Windows Device Manager) and use a computer mouse for input. 

T3RRA software does not automatically start when the tablet boots.

Symptoms:

When the tablet starts it is normal for T3RRA software to automatically load. However if you wait a reasonable period (sometimes up to several minutes, if updates or other activities are occurring) the T3RRA software still may not load,

Cause:

The tablet has not been properly configured to load the T3RRA software on startup, or the load routine has been disabled.

Solutions:

Configure your system to start T3RRA software on startup. There are several ways to do this. Google will provide many answers.  See below for answers from Microsoft at https://support.microsoft.com/en-au/help/4026268/windows-10-change-startup-apps

Note: If you are asked to copy the T3RRA software program file to a startup location DO NOT copy an actual executable file from any of the T3RRA software program directories. Copy the shortcut that is on the Windows desktop instead. Alternatively, create a shortcut pointing to the executable file and copy it. Note that the executable file that the shortcut must point to will normally be in a folder with two subfolders named ‘d’ and ‘v’ (see below for T3RRA Cutta’s program file, other software will be named similarly, according to the application name).

 

Important: you should be familiar with working with files in Windows in order to apply this fix. Mistakes while performing these types of activities can cause serious system problems. If you are not confident of your abilities please contact T3RRA or your dealer.

Can’t find an onscreen keyboard.

Symptoms:

You need to enter text (like a filename) while running T3RRA software but you can’t figure out how to.

Cause:

Microsoft Windows has at least one onscreen keyboard available to use for text input on tablets. However it can sometimes be challenging to find it.

Windows may be set to desktop mode and the Keyboard won't automatically open when a text box is selected,

Solutions:

There are 2 current solutions to this problem.

1. Plug a physical keyboard into your tablet
   
   
2. Swipe in from the “right” side of the screen and check if tablet mode is on/off, the icon should be highlighted blue if tablet mode is on.
   If tablet mode is on press the small image of a keyboard on the task bar in the lower right corner of the screen (in case you have moved the taskbar the keyboard icon should be next to the clock).
   
   
3. The onscreen keyboard may not be enabled. Go into Settings>Devices>Typing and scroll down to find a toggle option labelled "Show the touch keyboard when not in tablet mode and there's no keyboard attached".

T3RRA software will not install

Symptoms:

Installation proceeds smoothly. However, when attempting to run the software it will not start. The program shortcut icon may disappear. Subsequent attempts to re-install may throw errors indicating the user does not have sufficient permissions to perform file writing or folder accessing tasks.

Cause:

It is likely that you are running some type of anti-virus or malware protection software. This software may be seeing T3RRA software as a potential threat and refusing to run it. Alternatively, your administrative settings may be such that software cannot be installed without help from your system administrator.

Solutions:

1. Read the documentation provided with your malware protection software. Follow directions to allow the T3RRA software to run as a whitelisted application. The path to add as an exclusion is:
       C:\Users\YourUserName\AppData\Local\T3RRA\
2. Alternatively, uninstall your malware product and install the T3RRA software while it is uninstalled. Then re-install your malware software.
3. Seek advice from your system administrator.

T3RRA software is not updating

Symptoms:

When attempting to update T3RRA software using the normal method in the Settings area an error message like the following appears. You appear to have a good internet connection.

Cause:

If you are on a corporate network it might be configured not to allow access to certain websites. Our download server may not be on an approved whitelist.

Solution:

Request help from the company network administrators. Alternatively switch to another network (such as by tethering the tablet to your phone’s internet signal).

In-cab tablet is too small to design on effectively

Symptoms:

You are having difficulty performing designs on a tablet screen that is 10 or 12 inches in size.

Cause:

Small screens can be difficult to work with, particularly for anyone with impaired vision.

Solution:

Take the tablet back to your office. Plug the tablet into a large PC monitor or TV. Most tablets will have an HDMI connector for this purpose. Consult your local IT retail firm regarding cables or adapters required. Duplicate your tablet screen on the external monitor.

Tablet is in ‘Tablet Mode’ and you can’t find the desktop icon for your T3RRA Software

Symptoms:

The screen on your tablet when T3RRA Cutta is not running appears different from what you expect. It does not display the regular Windows desktop. You are unable to find the T3RRA software icon to activate your T3RRA software.

Cause:

Your tablet has been somehow placed in ‘Tablet’ mode.

Solution:

Turn off tablet mode.

 

Access to the port ‘COM X’ is denied.

See also: “Mouse Pointer flickers across screen randomly”.

Symptoms:

The following message appears.

Cause:

This message generally occurs when an attempt is made to open a serial connection to iGrade or directly to a GPS, but the serial port in question is already being used by another piece of software. 

Solutions:

1. Check that no other software is running on the tablet and already using the port.
2. Check the connection of the cable to the tablet. 
3. Power down the tablet running T3RRA and the tractor. Next, remove the serial cable or USB-Serial cable from the tablet. Turn on the tablet and start T3RRA. Once you are looking at the GPS screen, plug in the cable. Now, start up the tractor.

Plug all cables for iGrade in before starting the tractor. In other words, the tractor needs to be OFF until iGrade is plugged in and the T3RRA tablet is powered on.

The tablets that do not have true dedicated serial ports require USB-to-serial cables which create 'virtual' COM ports.  Best practice is to update the USB-to-serial cable driver before initial use of T3RRA in-field.

Steps:

1. Turn on the tablet that has T3RRA installed.
2. Connect to the internet.
3. Insert your USB to Serial cable.
4. Select Settings, then GPS Port settings, click on 'Device Manager'.
5. When the Device Manager window opens, locate 'Ports (COM & LPT)'.*
6. Click on 'Ports (COM & LPT)' to show which COM port has been assigned.
7. Right click on 'COM Port'.
8. Select 'Update Driver'. You will be notified once the software has been updated or if it has the current driver.
9. Set the COM port in T3RRA GPS Port Settings to correct port from the drop down.

*NOTE: If ‘Port” is not in the list, you may need to download the driver from the product website and install manually. We ONLY recommend FTDI USB to Serial Port adapters. This is the URL to download the FTDI Setup executable file: https://ftdichip.com/wp-content/uploads/2021/08/CDM212364_Setup.zip

iGrade dropping out during work

Symptoms:

iGrade is dropping its connection during work.

Possible cause:

To much data is being processed. 

In-Cab software automatically orientates to the north, and is recorded as a square. If the surveyed field is at an angle to north it will be save additional data as invisible points to fill empty space, shown in the red hatched section of the below image.

Solutions:

Separate the field into smaller sections using the Regions tool, and "turn off" the sections that are not currently being applied.

Software Issues

T3RRA Xxxxx is not happy :-( error.

Symptoms:

The following error (or similar) appears.

Cause:

There is a problem with T3RRAs program file structure. The program cannot find the correct path to the latest program files when it is started up. 

Solution:

Contact T3RRA or your dealer. Please provide context about when this error started happening and whether or not any changes were recently made to the tablet.

Out of memory errors

Symptoms:

T3RRA software crashes with an “Out of Memory” error.

Cause:

If the software is running on a 32bit version of Windows 10 and is working with large data sets it is possible to get this error.

Solution:

Upgrade your Windows 10 operating system to the 64bit version.

T3RRA software crashes without an error message

Symptoms:

The T3RRA software will suddenly close with no warning or error message. It is not clear what has caused the program to do this. Alternatively, the program will freeze with the splash screen showing or not start at all.

Cause:

Some unhandled error is causing the program to suddenly halt.  

Solution:

If the issue occurs on startup, or you are on an old version, updating can help. Sometimes an older version will run well enough to access the update function. To 'downgrade', right-click on the desktop shortcut and choose "Open file location". In that folder there should be two or more folders starting with "app-" (e.g. "app-2024.9.2"). In older products, there will be a "v" folder containing two or more folders with numbers for names (e.g. "0" and "2.233"). The larger the folder number, the more recent the release. Move the most recent release folder to a temporary location (e.g. Desktop) and restart the program. If it starts normally, open "Settings" and click "Download updates". Don't forget to delete the folder from the temporary location (or restore it if it doesn't help). If the issue persists, try rerunning the installer.

If a certain action by you causes the crash, try to avoid that action. Normally this type of error requires our software developers to develop a fix and release an updated version of the software. However, this type of error is difficult to reproduce and hence difficult to fix. Follow the following steps to send the information the developers will need.

1. Open the Windows ‘Event Viewer’ program 
2. In the left pane navigate to “Windows Logs > Application”
3. Find the most recent errors in the right pane that are related to the crash
   1. Normally these errors will occur in pairs with the first one having the source “Application Error” and the second having the source “.NET Runtime”. It is the second one that is of interest normally.
   2. Copy the contents to the “.NET Runtime” error into an email and send it to support@t3rra.com

         (image above: finding the errors in windows logs.)

         (Image above: highlighted contents that should be sent to T3RRA.)

Unauthorized Access Exception on program exit

Symptoms:

Bozo Error message occurs upon Exit prohibiting close of T3RRA software.

Cause:

Current “User” of the tablet does not have access to T3RRA Program Data in folder.

Solution:

1. Maneuver to the location -  C:\ProgramData\T3RRA\T3RRA Cutta\Settings\T3RRA Cutta Saved Settings.xml
2. Right click on T3RRA Cutta saved settings file.
3. Choose Properties
4. Choose Security tab
5. Choose Advanced
6. In Permissions tab Click Add
7. Choose select a principle
8. Type in name of User to add
9. Select Ok
10. Check Full control permissions
11. Select Ok
12. Select Apply

‘Out of memory’ error when saving

Symptoms:

Attempting to save a project causes an ‘Out of Memory’ error and no file is saved. This error will also occur periodically when auto-saves occur. This error will completely disrupt your ability to use the T3RRA software. Prior to the error occurring you may have noticed the project getting progressively slower and slower to load. If you run Task Manager you will see that the project is using excessive amounts of memory while loading.

Cause:

There is a bug in earlier software versions that causes replication of unnecessary data within the project each time a save occurs. Eventually this will bloat the project file to the extent that internal variables can no longer process the data objects that exceed memory limits.

Solutions:

Upgrade your software to at least v2.137. Load the offending project (it may take a long time to load) and then save it again. The project will have offending data sections removed and now should go back to normal load time on subsequent loads.

Setup & Installation issues

Unable to install T3RRA software.

Symptoms:

“Access denied” type errors occur when attempting to install T3RRA software. The installation fails, or the software disappears from the computer shortly after installation.

Causes:

1. Antivirus software on the tablet prevents installation, or quarantines the installed files shortly after installation.
2. Company IT staff have locked down the tablet such that software cannot be installed.

Solutions:

1. Disable your antivirus software or ‘whitelist’ T3RRA files with an exclusion. Consult your antivirus software documentation for information on how to do this. In some situations you may have to uninstall the antivirus software. It can normally be reinstalled afterwards.
2. Consult your company IT staff.

Unable to import RCD or ADAPT files directly from flash drive.

Symptoms:

Choosing to Import Survey Data then picking RCD or ADAPT files on flash drive plugged in tablet and the files are not loading or ‘grayed out’ so you cannot choose them in the import list.

Causes:

Flash drive is not transferring files correctly.

Solutions:

Copy files from the flash drive to the tablet’s hard drive then import from that location.

Use a new flash drive or reformat the old one

Version manager not working correctly

Symptoms: The version manager is displaying no available version to roll back to.

Cause:

Solution:

1. Access the T3RRA installation files.

2. In the v folder rename the installation files.

3. When restarting your T3RRA Software make sure you do not use the 

Software licence details disappearing after updating

Problem: After updating software to the latest version the licence becomes deactivated.

Cause:

Solution:

InCab Installer will not open

Symptoms: 

When you open the T3RRA InCab Installer you see the following error window.

Cause:

The Tablet may not have the latest version of .NET Framework(v4.8).

Solutions:

Download the latest version of .NET. Also make sure the window version is up to date.

Click this link to Download the latest version.

John Deere related issues

Notes for Dual or Triple Receiver systems.

Symptoms:

There are many strange errors that can result from incorrectly configured dual or triple receiver systems when running iGrade, these can vary from no control outputs to machines behaving erratically, so we have compiled a few things to check if you are having trouble, 

Solutions:

Ensure both SCV1 and SCV3 are configured to “Remote Control”

In the more common machine configurations where SCV1 is used for elevation control and SCV3 is used for “Slope” control these would be the correct settings, but for situations where a user has 2 receivers setup on one implement the SCV’s should both be configured to “Remote Control”

Power Cycle the Machine after making iGrade setting Change

After making any settings changes on iGrade it is important to power cycle the machine, power down the machine, Wait for all displays to save configs and completely shut down, wait 10 seconds, then start the machine, before then going through the settings to confirm all settings have stored correctly,

Confirm SCV’s are connected correctly

SCV1=Left control cyl

SCV3=Right control cyl

Check hoses for Extend and Retract aren’t connected in reverse! It may seem silly but we have seen it stump the most experienced users before, Check and double-check those hoses!

It is also important to note that when using 2 receivers on one implement that both SCV’s operate independently based on their respective receiver, and both SCV’s must be on their own Hydraulic circuits,

Check Receiver Serial Numbers

Check the serial numbers of the receivers, the receivers should be placed in order of their serial number, from lowest to highest.

Ensure the lowest serial number is on the Tractor, the next serial number is on the left side of the implement and first on the loom coming from the tractor, then the receiver with the highest serial number is on the right side and last on the Loom.

The same applies for dual and triple scraper systems where the lowest serial number should be on the tractor. The next goes on on scraper 1 and so on for scraper 2 and 3. With each additional receiver being placed along the harness in order of serial number.

Receiver heights for UCC1 or UCC2 on implements

• When utilising dual scrapers on UCC2 you may need to adjust the receiver height setting in the individual receivers settings through the ISO menus to ensure implements level at the same elevation. NOTE: To lower the blade enter a higher receiver height. To raise the blade position, lower the height set in the receiver setup.

• When utilising dual scrapers with UCC1, both receivers must be mounted the same height above the blade. Implement GPS offsets cannot be entered in the display to account for mounting error. If a constant offset is noticed during operation between scrapers, corrections must be made to the implement mast using shims.

Diagnosing guidance line location issues

Symptoms:

Imported guidance lines into display are not in the correct location:

- Tractor is manually steered down lines displayed on T3RRA.

- Tractor is auto steered down lines.

- Auto and manual steering result in significantly different paths.

Possible causes with solutions:

Cause: For 2630 only - Repeat box was not checked.

Solution: For 2630 only - check Repeat box then cycle.

Cause: Survey data used to Generate paths captured on a different correction source (SF3, Dealer base, SF1 and others).

Solution: Due to the in-ability to complete North-South, East-West shift for Guidance lines in a JD display, we cannot correct or guarantee the accuracy of lines created from another correction then the correction used to survey them. It is best practice and highly recommended that users survey, design, and implement from a single GPS source.

Cause: Survey completed from Dealer base and implementing from a Quick survey base

Solution: It is always good practice to implement with an absolute base. If there is a dealer network base coverage available at the location of the base used for implementation, we highly recommend connecting that base to the dealer network as a vehicle. Take note of the lat/long and elevation values then enter those details into the base location after configuring the base to absolute base. (refer to JD technical documentation for more information on editing base parameters).

Error “Incorrect MD5 Hash” occurs when loading project

Symptoms:

When loading a  project an error similar to “Incorrect MD5 Hash” occurs. The project fails to load.

Cause:

The file has become corrupted somehow. This file will no longer work. It may have happened if Windows shut down unexpectedly while a project was saving, or if a USB drive was removed prematurely while copying a file.

Solution:

There is no solution to this problem. The file is likely unrecoverable. Make sure you have sufficient backups available in case this error occurs. Switch to a backed up version of the project file and delete this one. If this problem continues to occur be aware that it may be a sign that your hard drive is failing. It may be time to replace it.

Dual GPS scraper is not level.

Symptoms:

When using two GPS receivers in a side-by-side configuration on a single scraper, one side of the scraper is consistently lower than the other side.

Cause:

One GPS is mounted lower than the other, or Implement GPS Receiver Offsets are incorrectly entered.

Solution:

Select Controller Setup softkey > Profile tab > GPS Offsets Edit button. Enter the correct GPS height offsets.

 

Height control jumping in and out of Auto

Symptom:

The height control is jumping in and out of Auto control

Possible causes:

During iGrade setup the system has not been reset and setting in both SCV 1 and 2 causing mixed messages.

Fix: 

Turn off the tractor and turn it back on again to reset the system and only the last set setting should remain.

Settings

Changing language has no effect.

Symptoms:

In settings, when you use the pulldown picklist to select a language other than English, the UI does not update to reflect the new language. The selection indicates that you have successfully chosen a new language but nothing else changes.

Causes:

• The language translation files are missing.
• There was an issue with an earlier version of the installer software that placed the translation files in the incorrect location

Solution:

Contact your dealer. The latest version of the installation software needs to be run to correct the issue.

Unable to change language.

Symptoms:

Even in settings you are unable to change the language. There may also be a red warning message indicating a problem with translations.

Causes:

• The language translation files are missing.
• There was an issue with an earlier version of the installer software that placed the translation files in the incorrect location

Solution:

Contact your dealer. The latest version of the installation software needs to be run to correct the issue.

Error reading settings.

Symptoms:

When starting T3RRA software an error message appears referencing a problem reading settings. 

There is an error in XML Document

Normally the program will continue to load, but in severe circumstances the settings file error may cause the software to crash. 

Cause:

There is some problem with the file that T3RRA software uses to store settings on the disk. It may have been corrupted in some fashion.

Solutions:

Normally you can continue running the software. You will likely have to re-enter any settings that you previously had. When you exit the settings dialog these settings will be saved to disk and the bad settings file will be overwritten. If you are unable to continue loading after encountering this error you will need to manually delete the settings file. This file can be found at:

C:\ProgramData\T3RRA\T3RRA <Ditch/Cutta/Plane/Levee/Survey>\Settings\T3RRA <Ditch/Cutta/Plane/Levee/Survey> Saved Settings.xml (or similar).

Note that the ‘ProgramData’ folder is often a hidden folder. It can be viewed by making hidden folders visible within the Windows Explorer settings, or by manually typing ‘C:\ProgramData’ into the Explorer navigation area.

Navigate to the settings folder in Windows File Explorer and rename the existing file by changing the extension to ‘.bad’ (or similar). Then restart the software. A new settings file will be generated.

GPS issues

No GPS signal is being received from iGrade.

Symptoms:

Tractor position icon not appearing on map-screens.

‘GPS info’ button in the bottom right of map-screens is red.

In the ‘Settings’ window there are no characters streaming into the ‘Serial port raw data’ window in the ‘GPS Port Settings’ tab.

Symptoms of incorrect baud:

Incorrect baud rate settings are identifiable by viewing the incoming data in the window provided in the GPS setting tab.

Good data looks like normal text, as below.

 

Incorrect baud looks like:

Causes:

The port for the GPS to T3RRA software may be closed.

Signal sharing is causing iGrade to lose Gps

Drivers for tablets serial port or USB-to-serial port may not be up-to-date.

Cables may not be seated correctly.

Solutions:

1. Ensure all Windows updates are performed.
2. Open the GPS info screen by pressing on the GPS button in the bottom right of the Collect or Apply step. Confirm that you have an RTK GPS signal and that the Open Port button is grayed out.
3. Ensure Signal Sharing is disabled in Autotrac settings
   

    

4. Confirm USB-to-serial cable’s driver is up-to-date if applicable (refer to 'Access to the port ‘COM X’ is denied’. for instructions on how to update driver)
5. Confirm harnessing is correctly installed using AE3166 to connect T3RRA to iGrade app controller or AE3070 to T into receiver for surveying without iGrade.
6. Perform a continuity check on the iGrade harness to make sure the pin configuration is correct and the cable is not damaged.
7. Check settings in both iGrade and T3RRA (iGrade and T3C need identical Baud Rate):

   IMPORTANT: When using T3RRA Products with iGrade you must configure the serial settings in “iGrade Settings”. You only need to configure the serial port in “Receiver Settings” if you are connecting directly to the StarFire (as you might do when you are surveying in a Gator for instance).

In iGrade UCC1:

• Select Main Menu
• Select Control Selection
• Select Serial Port Setup
• Baud Rate – 38400
• NMEA – GGA, GSA
• NMEA Rate – 5 Hz
• Set Last Altitude - Off

Power cycle the UCC1 controller (note that the controller may have been connected to constant power, and so a key off/on may not be sufficient to power cycle the controller).

 

In T3RRA (using iGrade UCC1):

• Open T3RRA program and go to Settings > GPS Port Settings
• Set 'COM Port' to the correct port
• Set Baud rate to 38400
• Select Ok button

Testing Serial harnessing.

The most reliable way to confirm correct serial port harnesses operation when using T3RRA Products is to utilise the Port data window and use a testing method called Serial Loopback.

A loopback test can verify the operation of serial communication by sending and receiving data from the same serial port. It can show problems in the serial port, the cable, or the software generating the messages without having to connect to third party hardware.

VERY CAREFULLY! connect the transmit (TXD) signal to the receive (RXD) signal pins 2&3 on the serial port connector. Or pins 10&3 on the JD SF Receiver connector. Or Pins 5&6 on the iGrade connector.

 

While these pins are connected, press the Open Port button.

The serial port raw data should populate the messages as indicated below, this would indicate both the send and receive pins are working correctly and the harnessing is connected correctly.

No GPS signal is being received when connected directly to a GPS receiver.

Symptom: 

The Tablet PC running T3RRA Software is connected directly to GPS but it is not receiving a GPS data stream.

Cause:

There are two potential causes of this problem.

1. The GPS receiver is not properly configured to output data via serial.
2. The cable between GPS and tablet is not connected or defective.

Solutions:

1. Check your receiver settings to ensure the correct data strings are being sent to the appropriate port. 
   1. NMEA GPGGA @ 5 Hz
   2. NMEA GPGSA @ 5Hz
2. Check your receiver settings to ensure that the baud rate in use matches that expected by your T3RRA software. The rates configured in each must match.
3. Check your cabling.
4. Perform Windows updates.

    

If connecting to a StarFire receiver directly with a T harness (AE3070 from AgExpress), confirm harnessing is correctly installed for surveying without iGrade.

To test if T3RRA software is at fault when no serial data is being received from iGrade it can be helpful to close the T3RRA software and use another independent program to read and display the serial data. One such program is‘RealTerm’ https://realterm.sourceforge.io/ . If you can successfully display incoming iGrade data in a serial terminal program it rules out a bad serial cable or incorrect settings on iGrade. If you are receiving valid text strings in such a program take special note of the port settings (Baud rate, and COM port number). These will be the same ones needed in T3RRA software.

Baud rate is set correctly but messages from iGrade are still garbled.

Symptoms:

Baud rates are set correctly on both T3RRA software and in iGrade. The T3RRA software is not receiving GPS and the GPS diagnostics window is showing an unintelligible data stream.

 

Causes:

The serial connection is not properly grounded. Pin 5 is disconnected or connected to the wrong pin at the other end of the cable. 

Solutions:

Carefully check the remote control cable and the iGrade harness. Ensure that the ground wire is properly grounded. In at least one case we have had a user report that an additional grounding wire was required as shown below.

 

Vertical Performance Issues (GPS drift).

Symptoms:

Blade seems to drift throughout the day. When grading over an area of the field that is thought to be ‘finished’ the blade consistently begins to either cut or fill. For larger sudden jumps in elevation, see Sudden Vertical Shifts.

Possible Cause:

• Using SF6000 and SF3000 receivers together as a base and rover, or as tractor and implement.
• Base is configured as a Quick Survey base when using iGrade.
• Poor GPS availability throughout the day.
• Base station in a non-ideal location.
• Base station being interfered with by passing vehicles.
• High VDOP values are shown by T3RRA Software.

Solutions:

• ALWAYS look for correlations with something that is happening in your vicinity when the issue is occurring. If the issue always happens at a certain time, or in proximity to buildings, trees, powerlines or other features then troubleshooting options can be narrowed.
• If using a 3000 receiver on the implement, John Deere recommends using an external antenna.
• John Deere recommends not mixing Receiver generations, as Base-Rover or as Machine-Implement configurations.
• Ensure the base is always configured as an absolute base when using iGrade.
• You must ensure Signal sharing is turned off in AutoTrac settings when using iGrade.
• Check GPS conditions at http://satpredictor2.deere.com/address. GPS conditions may be non-ideal, shift activities to bulking work until the GPS constellation improves.
• Use a mobile base and place it as close to the working area as practically possible.
• Move the base away from obstructions (building, vehicles, trees) and higher off the ground.
• Tune iGrade hydraulic thresholds.
• If you notice that degraded accuracy consistently occurs at certain times of the day there may be unavoidable satellite/atmosphere conditions. Try and schedule bulking work for this period, leaving high accuracy finishing grading for other periods in the day.

No GPS in T3RRA Cutta v1 when using dual scrapers in iGrade v1.

Symptoms:

Customer is running dual scrapers on iGrade v1. GPS appears to be present in T3RRA Cutta if only one scraper is configured.  Changing to dual scrapers in T3RRA Cutta causes GPS to be lost. 

Cause:

iGrade had been set up in “Plane Control” for SCV1 & SCV3 under the control selection . 

Solution:

Change the control selection to “Remote Control” for SCV1 & SCV3 and cycle power.

You are getting GPS data but the quality is not RTK.

Symptoms:

When you open a COM port you clearly see that positional data is being received. However the GPS Info window is displaying a fix other than FixedRealTimeKinematic.

Cause:

1. You are connected to the wrong COM port. This is possible if your tablet has an internal GPS and you are connecting to its port. 
2. Your GPS is not receiving RTK correction packets from its base station. 

Solutions:

1. Check to see that you are connected to the correct serial port.
2. There are many reasons a GPS may not be receiving correction packets from its base station. Check your GPS documentation for solutions.
   

GPS data stops and COM port number has changed.

Symptoms:

The position stops updating and it is apparent that position data is no longer being received. When you open the ‘GPS Info’ window it is apparent that the COM port has changed to a different port from normal. The regular port may or may not be there. If it is there and you change back to it everything is ok, but the problem may intermittently continue to occur.

Cause:

You are using a USB-to-Serial adapter. It is loose and the connection is randomly lost when the machine vibrates or travels over bumps.

Solutions:

1. Check connector ends for obvious damage.
2. Secure the adapter more securely using cable ties or other restraints.
3. Clean the USB metal contacts using contact cleaner and a cotton swab (or similar).
4. If the tablet has more than one USB port try the USB-to-Serial adapter in an alternative USB port.
5. Replace the USB-to-Serial adapter (please only use an approved FTDI adapter).

You have bench mark locations but they are not in Latitude and Longitude.

Symptoms:

If you are attempting to calibrate your GPS against a design and you have known bench mark locations you can use the “Enter a known location” option to achieve this. However you may find that your bench mark values do not match any of the formats requested.

Cause:

Your bench mark locations are in an incompatible projection or coordinate system. Commonly they are in UTM easting or northings or similar.

Solutions:

Contact your provider and request the bench mark locations in WGS84 Latitude and Longitude format. If possible, request that they use ‘decimal degrees’.

GPS issues with Windows 11

Issue:

T3RRA having GPS inconsistently operating after updating to Windows 11

Cause: 

Out of date COM drivers/ incompatible drivers with Windows 11

Solution:

update USB-RS232 drivers on tablet to restore GPS connection.

Sudden Vertical Shifts/Jumps

Symptoms:

The elevations may suddenly and randomly jump (0.3 to 4m / 1 to 10ft), requiring going back and re-zeroing. This occurs at various times (minute to hours apart), but not predictably. RTK fix is sometimes dropped, but regained in 1-3 seconds, however, the elevations do not return to the original values. For smaller shifts in elevation, see Vertical Performance Issues (GPS drift).

When investigating in detail: In the GPS logs, these jumps only occur at the start of a new second when an RTK correction is applied. 

Possible Cause:

• Base receiver has an intermittent failure.

Solutions:

• Update the receiver software of the base and rover.
• Swap the base receiver with a working receiver.

Surveying issues

Collected survey data is blue and red only.

Symptoms:

Normally collected survey data is colored with a spectrum of red (low) through green through blue (high). In this instance there appears to only be two colors: red and blue.

Causes:

T3RRA software fits a red-green-blue spectrum of color to the survey points. It “stretches” these colors across the range of data points. If the data is “clumped” in groups that are well apart numerically then the majority of the spectrum of color will not be seen.

1. One or more points has received a corrupted elevation value, placing it well above or below the bulk of the points
2. The base station has changed it’s elevation part way through the survey. Points collected before will be offset by this change.

Solutions:

1. If there are only a few corrupted data points, simply delete them using the tools available in surveying or surfacing.
2. If this problem is caught while surveying, stop the survey immediately. Check to see if the base station has been altered and fix it. Then delete the points that were too high or low and begin surveying at the location where the problem began.
3. If it is not possible to resurvey the affected part of the field you have several (bad) options
   1. Export the elevation points as a CSV file. Open the CSV points in a spreadsheet. Add the appropriate offset to all bad points. Save the file as a CSV. Import this CSV file in the T3RRA software.
      OR 
   2. Surface the collected data. Create a region around the section of the field that is too high or too low. Use the ‘Offset Surface’ design tool to change the height of the problem region. Some smoothing across regions may also be required. From this point onwards, use the resultant design surface as the basis for further designs.

Elevation Offset during surveying.

Symptoms:

Recorded elevation data collected while surveying is offset and not in the correct location.

Possible Cause:

• StarFire Receiver needs calibrated.

Solutions:

• Calibrate receiver’s TCM (refer to John Deere SF OM)
• Re-Survey

IMPORTANT: Vehicle must be on a hard, flat level surface for calibration. If TCM is not calibrated on a level surface or TCM mounting angle is not level in relation to vehicle angle (StarFire mounting bracket or vehicle cab being slightly offset, uneven tire pressures from one side to other, etc.) operator may see offset during operation. This offset could look like a consistent skip (A) or overlap (B) in pass­-to-­pass operation. To eliminate offset, re­calibrate on a level surface, drive down a pass, turn around and drive down the same pass in the opposite direction. If the vehicle does not follow the same pass, measure the offset distance and enter in the implement offset. After initial calibration of TCM, it is not necessary to calibrate again unless TCM angle in relation to the vehicle has changed. For example, tire pressure has been lowered on one side of the vehicle.

Drain Survey mode performed in error.

Symptoms:

Drain line is present in the elevation data path.

Possible cause:

T3C user has recorded in Drain survey mode instead of Field survey mode as intended. Drain lines are in a swath pattern across the field.

Solutions:

If a user does not wish to resurvey in Field survey mode, they can:

1. Delete drain line T3RRA Design (T3RRA Cutta owners only).
   1. Load the project into T3RRA Design
   2. Delete the drain line on the Guide tab
   3. Export a control file for T3C
2. In Collect step of Wizard:
   1. Export data as CSV file
   2. Import CSV file into T3RRA Cutta v2.

Elevation points not appearing correctly or with voids.

Symptoms:

1. When you survey a field or drain and the elevation points are faint with black lines through them causing the survey to appear incorrect or with void like spaces.
   
2. Your drain profile view shows incorrect names associated with the drain selected.
    

Cause:

1. The elevation points have been recorded using the Boundary mode instead of the field or drain survey modes
2. Drain was resurveyed without starting a new project or deleting previous surveys.

Solution:

1. Delete the black boundary line using the delete boundary option in the boundary survey mode in the collection screen. After this the elevation points can be used as they normally would.
2. Delete the unwanted drain survey elevation data in the collection screen.

Surveying at heights close to sea level results in an incorrect field surface.

Symptoms:

The collected field elevation map (in T3RRA software) appears vastly different from your expectation of what the actual field looks like. You are surveying a field where elevations can be both negative and positive (i.e., partially above and partially below sea level). When you examine your field map you see that all elevation values are either negative or positive (not both). You are using a StarFire 3000 receiver and receiving serial data directly from the receiver (not via iGrade).

Cause:

The StarFire 3000 has a bug that causes problems with output elevations when it crosses between positive and negative elevation values.

Solution:

1. Alter your base station height so that the whole field can be surveyed using elevations that are either all positive or all negative.
2. Use iGrade and an implement receiver to survey the field.

Designing issues

Levees are jumbled and crossing over.

Symptoms:

When you create levees in T3RRA Cutta, Ditch or Levee, the levee lines seem very ‘messy’. There are frequent line endings and levee paths sometimes appear to cross over each other 

Cause:

The levees are spaced very closely. T3RRA software uses an algorithm that looks at the edges of individual raster pixels and problems can occur if the levee lines are spaced at a width of equal to, or less than, the pixel size.  

Solution:

Resurface the survey data at a smaller pixel size. Then re-do the levees. The correct pixel size will depend on the slope of the land, and the required vertical distance between levees.

 

Imported SWP+ ditch track names are too long.

Symptoms:

After importing SWP+ ditch tracks, you see that their assigned names are too long and cover most of the surface.

Cause:

Previously assigned names are imported along with ditch tracks.

Solutions:

Return to the Surface step and use the Edit Drains button to rename.

Click on the pencil and paper icon, rename drain, choose Ok, then Close.

Drain Design freezing and/or producing jagged profile view OR Small Field design has jagged edge and difficult to see changes in elevation.

Symptoms:

After Applying drain design, the tablet freezes.

Profile view of drain is jagged.

Small field design has jagged edges.

Small field not defined enough.

When I am in the Drains Design step, the profile view of my surveyed drain appears ‘jagged’ and ‘corrupt’. I know what I am viewing in the drain profile window is not an accurate representation of the original surface.

Possible causes:

Pixel size is too large for thin drain.

Drain is long and the drain width is thin.

A drain survey was collected OVER a field survey (or visa versa).

Solutions:

Change Pixel size.

Change width of drain (only if the change will not affect implementation).

Image of profile view of drain with jagged drain line:

Image of small field with large pixel size:

Image of small field with small pixel size:

Solutions if drain and field surveys overlap: 

Delete the field elevation points directly under the drain path of drain surveyed points.

Resurvey in Field survey mode pausing field collection of points when traveling over the drain path then change to Drain survey mode to collect the drain path that is clear of field elevation points.

Attempting to save a PDF report throws an error.

Symptoms:

When attempting to create a PDF report on a tablet running Windows 8.1 an error message appears and no report is created.

Cause:

Windows 8.1 is missing some critical files the PDF creator relies on. 

Solution:

Install the VC++ 2015 Redistributable files.  These are available at www.microsoft.com. Use a search engine to find them. Choose the version that matches your tablet (32 or 64bit).  Install on the tablet. The PDF creation process should then work.

Markers not visible.

Symptoms:

Markers are not visible on the map surface, and you believe they should be present.

When you have created markers (Bench Marks ) in T3RRA Design and have exported your control file for T3RRA Cutta or T3RRA Ditch.

Cause:

A marker may have been given an incorrect elevation value, causing it to be well above or below the surface. This can happen for instance if the design was made in T3RRA Design and the marker was given an elevation of zero.

The  markers have been exported without a height set, therefore will only show up in 3D underneath the surface.

Solutions:

1. Check to see that the marker is actually present. This can be done by tapping the ‘Delete marker’ button in the bottom right of any map-screen and seeing if the marker of interest is in the list to be deleted. If it is then close that dialog and then zoom as far out as you can. You will likely see the marker a long way above or below the surface. If the ‘Delete marker’ button is not present it means there are no markers available on the map.
2. There is currently no way of changing the elevation associated with a marker. Go back to the original source software and fix the issue there. If this is not a satisfactory solution please contact T3RRA to explain the use case and we will examine ways to achieve your goals.
3. When creating markers in T3RRA Design always make sure that you enter the value and tick the “Lock value” before exporting your control file. 

My cut/fill map is totally a single color representing no cut and no fill.

Symptoms:

In the implementation or design phase of T3RRA software, you view a cut/fill map and it is a uniform green or gray color representing no cut and no fill (depending on your cut/fill color schematic selected in Settings). When you touch part of the map it shows the Cut/Fill value as being 0.

Cause:

1. Your original surface and your design surface are exactly the same. This happens if no design has been created. When surfacing first completes a “blank” design is created that matches the original surface exactly. As a cut/fill map is the difference between the original surface and the design surface it will necessarily be a map of zero values.
2. Your ‘Zero Cut/Fill Range’ is too large.

Solution:

 

1.  Go to the design step of the wizard and create a new design. 
2. Open Settings > Application and lower your ‘Zero Cut/Fill Range’ 

There is an ‘offset’ cut area beside my drain.

Symptoms:

When burning a drain profile into a surface, one or more side cut areas appear that seem disconnected with the actual drain path. 

Cause:

The side batter from the drain rises up through an existing surface that undulates in such a way that both cut and no-cut areas result.

Solution:

Increase the batter angle, or smooth the field surface before creating the drains (and create the drains based on the DESIGN, not the ORIGINAL surface). Alternatively, simply ignore the offset cut area.

Drain Design error message ‘not downhill all the way’

Symptoms:

When designing a drain, you receive an error message:

Cause:

Parameters entered do not allow drain to flow downhill all the way.

Solutions:

Change parameters until they produce a drain that will flow downhill all the way. i.e. increase Max Cut.

Drain Design error message ‘drains were affected by this operation’

Symptoms:

When designing a drain, you receive an error message:

Cause:

1. Elevation data was collected from low to high elevation where another drain connects.
2. Drain was split with the Split Drain tool.

Solutions:

Swap AB before designing so the drain is designed from high to low elevation.

Cross Slope issues

Cross slope control is not working.

NOTE: This guide is NOT applicable for systems using two GPS units on a single implement for cross slope control.

Symptoms:

You want the T3RRA software to control the cross slope of the cutting edge but it does not seem to be working.

Cause:

Improper physical setup, iGrade configuration, or T3RRA software settings.

Solutions:

1. Make sure that SCV3 is set up for cross slope control (check your iGrade Operators Manual). IMPORTANT. Choose ‘Cross Slope Control’ from the SCV3 drop down menu in UCC1. Check the ‘Enable Cross Slope’ box in UCC2.
2. Make sure that you have properly calibrated your TCM.
3. Ensure the SCV has had the thresholds calibrated as per the iGrade manual
4. Check the control sensitivity is not set too low causing cross slope to be “lazy”. Increase the value for a more aggressive control.
5. Check that the correct hoses from your implement's cross slope controlling hydraulic ram(s) are plugged in to SCV3
6. Reverse the hoses plugged in to SCV3 if needed.
   1. Reversed hoses will normally cause the blade to rotate completely to either the left or right as soon as you begin working.
   2. iGrade 2 has a checkbox option to reverse the blade tilt without reversing the hoses, iGrade 1 does not. If you have iGrade 2 check your iGrade manual for more information.
7. Make sure that the ‘Output cross slope commands’ box is checked under ‘Settings > Machine’ in the T3RRA software.
   
8. Make sure that an accurate ‘Implement Width’ is entered under  ‘Settings > Machine’ in the T3RRA software.
9. Make sure that cross slope control is set to Auto on the implementation screen.
10. Ensure that the design is actually calling for the expected cross slope.

Cross Slope not working and Front and Rear Error displays are visible.

Symptoms:

If you are seeing Front Error and Rear Error and you are not using dual scrapers, you may have set up the SCV 1 and SCV 3 incorrectly.

Cause:

You have not set Cross Slope up correctly on the Application controller.

Solutions:

Choose ‘Cross Slope Control’ for SCV3’ from the drop down menu in UCC1. 

Check the ‘Enable Cross Slope’ box in UCC2.  

Paddle pots are backwards for manual control of cross slope.

Symptoms:

The operator is accustomed to moving the controls in one direction to achieve left tilt and in the other for right tilt.  iGrade v1 wants the cross slope ram hoses in a certain way and this forces manual control to be backwards from how the operator expects.

Cause:

iGrade v1 only allows the hoses to be plugged in one configuration. 

Solutions:

Short of altering the hydraulic hose configuration on the implement rams, there is no known solution for iGrade v1. 

iGrade v2 gives the option of reversing the outputs.

Scraper cross slope appears to be the opposite of what it should be.

Symptoms:

When T3RRA is commanding a cross slope tilt to one side the scraper blade is doing the opposite. iGrade is showing a current cross slope % as positive when the implement is rolled to the left, and negative when tolled to the right. Reversing hydraulic hoses in the remotes does not help the problem.

Cause:

The implement GPS mount direction has been changed to ‘Backward’ in the John Deere display. This causes receiver TCM readings to be the opposite of what they should be. 

Solution:

Set implement GPS mount direction to ‘Forward’ if the receiver is facing forwards.

 

Implementing issues - iGrade alone

Troubleshooting performance.

Symptoms:

• Implement responds too slowly to changes in grade
• Blade fails to hold grade
• Unexpected shifts in blade elevation occur
• Implement appears not to respond to commands
• Cross slope not working
• Cross slope behaving unexpectedly

Cause:

“Performance” is a subjective term. There are many ways in which a system can suffer poor “performance”. Thus there are also many causes for this. The exact cause will differ with the type of performance degradation present. Specific types will be discussed further in other parts of this document. However the below advice is almost always relevant.

Solutions:

The first step when diagnosing any performance issue is to disconnect the T3RRA software and to test iGrade in isolation. Only once you have confirmed that iGrade is working properly, you can then start to troubleshoot the T3RRA software. Place iGrade in Plane Control or Grade Control and establish that it is performing as expected. If it is, reconnect the T3RRA software and continue with other solutions in this troubleshooting guide. If it isn’t please consult your John Deere dealer.

Implementing issues with iGrade (will occur without T3RRA connected)

NOTE: There will be situations where your dealer may ask you to capture a StarFire message log for further diagnosis. This can be done on the Deere display using the SF6000 VT as follows:

Bi-Directional error in iGrade.

Symptoms:

The implement consistently cuts when heading in one direction and fills in the other direction. Final grade is never achieved. If T3RRA software is halted and iGrade is run in ‘Plane Control’ only the problem is still present. Changing height control to SCV 3 may resolve the issue.

Cause: 

This problem has been seen in cases where check valves within the tractor SCVs are malfunctioning. The implement blade is failing to hold height properly. The bidirectional nature of the issue perhaps comes from different amounts of dirt (weight) within the scraper when it is going in different directions. If changing height control to SCV 3 fixes the issue then it may indicate that only SCV 1 is malfunctioning.

Solutions:

Replace check valves with tractor SCVs.

Blade continuously loads on one side.

Symptoms:

System is grading low on one side.

Cause:

There are multiple possible causes for this.

• iGrade has not been set correctly.
• SCV’s have been put accidently in float instead of detent.
• Manual nudge controls have been turned on by accident.

Solutions:

1. Ensure this is actually the case, try grading in both directions along a single pass be sure to confirm the blade stays low on one side
2. Be sure the SCV is set to the auto detent position
3. If using ‘Cross Slope’, ensure ‘Cross slope’ is set to control. Auto is active when the manual slope nudge buttons are greyed out. The blade controls the set slope when the slope nudge buttons are active. Check the iGrade setup - ensure cross-slope is set to remote commands and also SCV3 is set to cross slope for external commands,
4. Complete a TCM calibration on the receiver, be sure to drive a complete figure eight to wake up the TCM before completing the calibration, ensure the blade is close to the ground and level before proceeding through each step of the TCM cal.
5. If there are two receivers on the one scraper, check to see that the Implement GPS Receiver Offsets are set correctly in iGrade.

Poor “on grade” performance.

Symptoms:

Blade Struggling to hold grade.

Cause:

There are multiple possible causes for this issue.

• Interruptions to GPS.

• Incorrect surface offset.

• Incorrect settings in iGrade.

Solutions:

1. Disconnect T3RRA software. Perform performance tests using iGrade alone to simplify. After you are satisfied with the iGrade performance, reconnect T3RRA software and re-evaluate performance.
2. Be aware of your environment, GPS can experience interference from trees, buildings, the tractor, water and some soil types can cause interference.
3. Ensure the base is set up clear of trees and obstructions of its view of the sky.
4. Ensure the base is set up well clear of any traffic or vehicles passing by.
5. Ensure GPS accuracy is adequate, ensure you are operating within 1 mile (1.6kms) of your base station.
6. Check the GPS accuracy is adequate, Ensure your VDOP is below 1.6, do this by either opening the GPS info window in T3RRA Cutta by tapping the GPS in the lower right of the display.
7. Ensure the settings in iGrade are correct and re-calibrate iGrade thresholds and set the grade sensitivity. Calibrate thresholds using a potentiometer or a pressure gauge. See dealer for details.
8. Check your base has adequate power and is configured as an absolute base, low base power when set as a quick base can cause strange results.
9. If using a StarFire 3000 be aware that John Deere recommended practice is to use an external antenna. Check that the coaxial cable is not squashed or damaged.
10. Dealers are encouraged to file a John Deere DTAC case if vertical accuracy issues are not solved using other recommendations in this guide.
11. Also see - The implement blade does not seem to follow the design surface.

Engaging auto causes the scraper to raise into the air.

Symptoms:

Operator engages scraper into detent (auto mode) and the scraper extends to full stroke on the lift cylinders.

Cause:

iGrade has Load Limiting and/or Max Cut enabled in Application controller settings.

The engine speed (RPM) threshold is set lower than the field working engine speed (RPM) threshold.

User is using UCC2 in Proprietary valve mode (CANBUS). But has the application controller also connected via the legacy option connector.

Solution:

Disable Load Limiting and/or Max Cut in Application controller settings.

Enter an engine speed threshold that is greater than the factory default of 1500 rpm or make sure your working engine speeds are greater than your current load limiting engine speed.

Disconnect the legacy valve mode SCV connector at the application controller.

Scraper is “washboarding”.

Symptoms:

Scraper causes a washboard effect.

A-If washboarding is close together, flow rate is too high.

B- If washboarding is far apart, flow rate is too low.

Cause:

• SCV flow rate is set too high or too low.
• Washboarding can occur when the blade is at an overly aggressive angle (construction model scrapers have a more aggressive angle while 'finishing' scrapers do not).
• It can occur when the ground is hard and has not been prepped for dirt moving.
• It can also occur when the tires' air pressure on the scraper does not match (one is lower than the other). 
• It can also occur if the scraper has split hydraulics and the cylinders controlling height over the right and left walking tandem are not equally pressurized (one cylinder may have a leak). 
• It can also occur if the tractor hitch is mounted to the scraper drawbar too high or too low.

Solutions:

Decrease or increase the SCV flow rate. If still present, adjust counterbalance valve pressure.

Contact implement service provider.

Implement blade moves to an extreme position when placed in Auto.

Symptoms:

When placing the machine in Auto, the implement’s blade dives deep, climbs to full height, or tips fully to one side.

Cause:

SCV hoses are incorrectly configured (reversed).

UCC2 with JD proprietary mode configured for SCV control but JD Legacy “Option connector” is also connected to the tractor.

Solutions:

Short of altering the hydraulic hose configuration on the implement’s cylinders, there is no known solution for iGrade v1. 

iGrade v2 also gives the option of reversing the outputs.

Ensure Option connector on rear of machine is disconnected, Then complete 2X power cycles to reset the SCV Controller

Blade not staying on grade & acting inconsistently.

Symptoms:

Blade is acting erratically.

Blade height is on grade for a while but then moves down a few inches and then back up.

Blade is reacting inconsistently while implementing. The blade wants to cut over ground that is already on grade.

When implementing design, the system is not cutting and filling as per map on screen.

Causes:

Base is being used as a Quick Survey base.

Base power is low.

iGrade and/or application controller need to be updated.

This is related to the GPS receiver not being mounted correctly and not moving with the blade.

Solutions:

Use an Absolute Base.

Charge base to fullest amount.

   

 

Mount GPS receiver so that it moves with the blade.

Contact your John Deere dealer and ask if updates are available for iGrade and/or application controller.

The implement blade does not seem to follow the design surface.

Symptoms:

The blade is moving up and down in ways that indicate that it is being successfully controlled. However the blade positions do not seem to be what is expected based on the design in T3RRA. 

Cause: 

iGrade is not in “Remote Control” mode. It may be in Plane Control, or Grade Control

Drain design bottom width is narrow and the implement is traveling outside the design width. The user is working outside of the drain bottom width design so the blade is not going to the design height.

Solutions:

Place iGrade in “Remote Control” mode and cycle power on the tractor. Consult your iGrade manual for instructions.

Increase the width of the drain bottom in Drain Design to accommodate the desired drain path.

Implement blade is intermittently jumping up or attempting to deep dive.

Symptoms: 

Work is progressing normally but occasionally the blade will suddenly rise up, or attempt to aggressively dig.

Possible Cause:

• A bad USB-to-Serial conversion dongle/adapter is causing corrupted height commands to be sent to iGrade. This can be diagnosed by checking the I/O Voltages page on the iGrade display and observing the last received messages. Occasionally you may see values being received to be truncated or otherwise corrupted.
• Base receiver could have an intermittent failure. See Sudden Vertical Shifts.

Solution:

1. Replace your USB-to-Serial cable with the one recommended. - FTDI US232R.
2. Contact T3RRA or your dealer for a recommended make and model.

Ps

Erratic performance during drain implementation.

Symptoms:

1. Implement moving erratically while implementing drains.
2. Implement moving erratically while implementing drains with Cross Slope enabled.

Cause:

T3RRA creates a surface using a raster which is a grid of elevation heights. These gridded cells are referred to as “pixels” and have a uniform edge size. As the vehicle moves it reads the elevation from consecutive pixels beneath the blade. If the neighboring pixels are significantly different in elevation the blade can move substantially as it crosses pixel boundaries. 

Solutions:

1. In some situations, it may make sense to decrease pixel size so that neighboring pixels are closer in elevation. If your implement is 2 meters wide and your drain width is 4 meters, try decreasing your pixel size or increasing your drain width.
2. Disable Cross Slope.

iGrade is indicating that Remote Commands are not being received from T3RRA software or indicating ‘No Surface Defined’.

Symptoms:

The iGrade display is showing a “No Remote Commands” error message, and iGrade is not controlling your implement.

iGrade v2 displays “No Surface Defined” when moving.

Causes:

• Your T3RRA software may not actually be sending control messages.
• If it is sending messages there may be a problem with the messages, or the cable may be incorrectly attached, or damaged.
• SCV’s have not been set to detent.
• iGrade is expecting Cross Slope commands but they are not being sent from T3RRA.

Solutions:

1. Check that you are in the ‘Implementation’ screen in your T3RRA software, and that you have pressed on the ‘Start’ button.
2. Check that the T3RRA software is not in ‘Demo’ mode.
3. Check that the data sending spinner is rotating (T3RRA v1) or the send arrow is flashing (T3RRA v2).
4. Check that your iGrade Remote Control Harness is in place and connections at both ends are well seated, and that no pins are loose/bent/damaged/pushed-in.
5.  If you are using a USB-to-Serial dongle that has activity lights (recommended) check to see that the appropriate TX light is indicating activity.
6. Make sure that your iGrade Remote Control Harness does not have reversed TX and RX lines. The iGrade manual describes the required pin configuration for this cable. Check that the pin configuration is correct.
7. Check continuity in your iGrade Remote Control Harness TX and RX lines to ensure that a pin has not become disconnected.
   
8. Check the I/O voltages screen on the iGrade display to view the “Last Received Command”. If there are messages being shown it is possible that the messages are defective in some way. Take a photo of this screen and forward it to T3RRA or your dealer for diagnosis.
9. Check that both iGrade and T3RRA are configured to send and receive  Cross Slope commands (if using Cross Slope). If you are not using Cross Slope, check that both do not have Cross Slope enabled.

Error from grade values do not match on iGrade and T3RRA software.

Symptoms:

When stationary, or at very low speeds, the value for error from grade reads 0 on the iGrade display. The error from grade value in the T3RRA software is non-zero and at the expected error value. As soon as you start moving the error value on iGrade returns to expected levels.

Cause:

At low speeds (below iGrade’s activation speed) T3RRA software stops sending iGrade true target elevations. Rather, the T3RRA software returns the current blade height to iGrade. This is done as a safety measure to ensure that the blade will not move, as well as to keep the remote connection alive.

Solutions:

This is a software issue that is being investigated for alternative solutions. Ignore the error value on iGrade when stationary. Make sure your are updated to the latest software version as this problem may have been solved.

User cannot turn “Grade On” with iGrade 2.

Symptoms:

You have iGrade setup for remote Control. You have a field design in T3RRA Cutta with your zero set and you are on the design surface in the field. You select the “Grade Off” button to turn “Grade On” with no luck. 

You have checked T3RRA Cutta to make sure you are sending commands to iGrade and it is.

Under the Status tab near the “Grade Off'' button you will see the “Status: Disabled” and “Last Exit Code: No Surface Defined”.

 

Cause:

iGrade is not receiving messages from T3RRA Cutta, therefore “No Surface Defined” will be displayed and iGrade will not let the user turn “Grade On”

Solution:

Check the serial connection from T3RRA Cutta to iGrade. Use the Diagnostics built into iGrade to ensure serial communications are being received. You should see the “Line Count” steadily counting up.

 

Check that the iGrade harness is not faulty, or has pins backed out

Poor as-applied coverage.

Symptoms:

The as-applied map looks blotchy, streaky, incomplete, or otherwise incorrect.

Cause:

• The as-applied map will only be correct for a single machine working in a field. If part of the field is done by another machine this information will not be relayed to the current machine.
• Blade shift is altering the implementation of the design.
• Pixel size on screen is too large.

Solutions:

1. Ensure the machine and implement settings are correct to allow as-applied to work correctly.
2. Ensure your pixel size is no more than half the implement width you are using.
   1. Pixel size can be adjusted in the “Projects” tab of settings.
   2. It is recommended to select the option closest to ⅓ of your implements width and no more than ½ of its width.
3. Check your zero range setting. Some very low zero range settings can give undesirable results.
4. Ensure your blade shift is set to zero, the blade nudge will apply above or below the design updating the as-applied to show the work is not complete.
   1. If blade shift is on in the T3RRA software it will be seen in the lower left of the screen.
   2. If the shift value here is not zero press the up and down arrows until it is zero.
   3. Do not use the blade shift function for shifts that are meant to be permanent. Alter the vertical offset value for this purpose (ie., re-zero)

Implementing issues - T3RRA

Bi-Directional error in T3RRA.

Symptoms:

The implement consistently cuts when heading in one direction and fills in the other direction. Final grade is never achieved. If T3RRA software is halted and iGrade is run in ‘Plane Control’ only the problem goes away.

Cause: 

There is a slight time lag from when a GPS location is measured to when the blade actually actuates to seek the desired target elevation. If the look-ahead time is set incorrectly, when going up a slope this causes the cutting edge to be consistently low, and when going down a slope it causes the cutting edge to be consistently high. 

The key to understanding this problem is to realize there is a slight time delay from when iGrade first sends the T3RRA software a position, and when the T3RRA software returns a target elevation value to iGrade. In this time the tractor has moved a certain distance and the target elevation is technically out of date. It is intended for a position in the field that is now some distance behind the cutting blade. If the tractor is traveling down a slope this will result in the blade being higher than it should be. If the tractor is traveling up a slope this will result in the blade being lower than it should be. The problem is repeatable and the vertical offset is always in the same direction (relative to whether you are going uphill or downhill). If you understand why the problem occurs it is normally quite simple to adjust for this time delay and nullify the issue.

Solutions:

Refer to the Machine tab section of the Setting chapter of the Operator's  manual for more information.

Tractor position icon is far above or below the surface.

Symptoms:

When implementing the position icon appears to be a long way above or below the surface (the tractor icon will normally rise to surface height if it is below the surface, but as-applied cuts will be far too deep).

Cause:

The zero value has been incorrectly set, or the base station elevation has changed since zeroing.

Solutions:

1. Re-zero the T3RRA software
2. Check to see that the base station coordinates have not changed. If they have, return them to the original coordinates (latitude, longitude, height).
3. Be sure to save your project if you believe you will need to finish implementation at a later date in order to retain the zero value.

Tractor position icon does not adjust when you zero against a benchmark.

Symptoms:

You are parked over a physical benchmark and want to adjust the map location so that the related on-screen benchmark icon matches the location on the tractor icon. However when you perform the “Zero using a marker” action nothing changes. The icons for the benchmark and the tractor remain separated.

Cause:

You have forgotten to check the “Zero X and Y (lat/lng) offsets” box.

Solution:

Check the “Zero X and Y (lat/lng) offsets” box before pressing the Ok button.

Map icon on the T3RRA software screen lags behind the actual field position.

Symptoms:

The screen update appears to be “laggy”. When you turn a corner and are back on a straight path you may see that the position icon on the screen is still turning the corner.

Cause:

This normally indicates that the software is having to do a lot of calculations, or that there are insufficient resources (CPU, HDD, Memory) available on the tablet.

Solutions:

1. Check for updates online. There may have been performance enhancements included in newer versions of code.
2. Check that the tablet you are running meets our minimum specifications.
3. Do any Windows updates that are pending.
4. Make sure that your tablet has no other applications running. Close any unneeded applications.
5. Divide the work area in your project into smaller areas. Having to process a smaller data set should result in better performance.
6. Surface your elevations with a larger pixel size. Larger pixel sizes result in smaller data sets and this will result in a performance increase.  

‘As-Applied’ not updating correctly

Symptoms:

When on the implementation screen, the “As-Applied” Cut/Fill map was not updating as per pass on the field.

Cause:

Ensure the "Implement Width" is entered and they have "As -Applied" enabled.

 

Solution:

If "Implement Width" is entered and "As -Applied'' is enabled, make sure you have selected in "View Settings" the "Terrain" As-Applied and "Layer" Cut/Fill maps. If ‘As Applied’ button is unavailable, it is a good indication that As Applied is disabled in Settings.

 

Project has moved N/S or E/W.

Symptoms:

When you return to an existing job the map is no longer aligned with the position of the tractor. The project surface has moved North/South or East/West. 

Cause:

• Previously entered offsets have been cleared under the Machine tab in settings.
• The Base station has been moved.
• The Base station is configured as a Quick survey and has been power cycled or reset.

Solution:

1. Keep a record of any horizontal offsets you have used for a project in case you need to re-enter them. If you look back in the project ‘activity log’ you may be able to find previously entered ones there (depending on version).
2. Always use a Base configured as ‘Absolute Base’ where possible
3. Reference any newly established base station from a “dealer network” or permanent base network where possible
4. If using a ‘Quick Survey’ have it connected to a permanent and always-on power source for the entire duration of a job.
5. Never move a Base station position during a job.
6. Establish permanent “benchmark” locations to check against and re-align the job.  You can use the regular ‘Zero’ button in the implementation screen for this.  
7. Use T3RRA software offsets to re-align the map.

My drain design is no longer present in the ‘Apply’ wizard step.

Symptoms:

The Cut/fill map of drain surface in the Apply step is representing no cut and no fill.

The profile view in the Apply step of the drain is a solid red line.

Causes:

A drain design was created for one or more of the multiple drains in one project and the user went back to the Collect step and recorded another drain survey within the same project.

All drain designs were ‘overwritten’ when returning to Collect step to add more drains to the same project.

Solutions:

Design and Implement one drain at a time saving each as one project file.

Design and Implement each drain completely within one project before adding more drains.

Survey all drains, design them, and finally implement them without returning to add more drains.

My drains have ‘bumps’ in them that weren’t present when I designed them.

Symptoms:

A drain line was created with a set profile but when implementing it seems to have unexpected deviations. 

Cause:

Multiple drains were designed and have overlapping sections. The profile of a drain gets ‘overwritten’ by the profile of a subsequent drain.

 

Solution:

Design and implement one drain at a time. That way you will get exactly what is shown in the design step (if you always implement on the original surface for instance)

In the design step apply each drain individually rather than choosing the 'Apply all' option. Each subsequent drain should use the 'Design surface' as the surface to apply on rather than the original surface. In this way you are designing the drain profile on a surface that accounts for the effect of previous drain lines. Note that the order of drain design matters in this case.

Drive survey of drains individually instead of driving one drain to inevitably need to ‘split’ the drain where overlapping another drain.

Implement is offset a large amount after 'zeroing'

Symptom:

Your implement is offset by a large amount when you zero before implementing.

Possible causes:

1. A value has been entered into the Blade clearance causing the  zeroed amount to be higher than normal.

Solutions: