Differences

This shows you the differences between two versions of the page.

--- android:machinecontrol:mcstories [2015/02/24 01:58]
mikeclapp [Updated Set Elevation Dialog (Feb 2015)]
+++ android:machinecontrol:mcstories [2015/03/25 22:13] (current)
mikeclapp [Settings]
@@ Line 63: / Line 63: @@
 As per Mike C and Ted (05-07-2014): Set Elevation should lose the Apply button, Elevation and Adjustment cannot be edited, but the Known Elevation can be shot or typed in. The Adjustment value will update during typing or after the shot.  Preferably Set Elevation will be a second window that slides in from the left or bottom. The Adjustment and known elevation should be cached on the device and matched to the recovery BM's LLA's (which will require caching them as well).  If the BM's are the same then allow a simple apply of the adjustment, otherwise the adjustment should be set to 0.0.
-==== Updated Set Elevation Dialog (Feb 2015)====
-The functionality of Set Elevation is working fine but continued usage of Bill's version of it has me making modifications. Bill's version of the dialog showing the actual position while doing a set elevation was an improvement over mine that took the entire screen. After using it a while and discovering that portrait orientation is actually a nice alternative to landscape I'd like to modify the dialog to look like those below. I've done the following in these screens:
+==== Updated Cut/Fill Main Screen View (Feb 2015) ====
-  * Widened the Landscape pane slightly for better spacing
+I haven't been satisfied with the look of the cut/fill numbers, arrows and crosshairs because they're too small and too cramped on this aspect ratio screen. Here's some refinements.
-  * Simplified the instruction wording and moved the controls to be more inline with the instructions.
-  * Used a slightly smaller version of the keypad used in the Blade Preferences rather than the default Android keypad. The problem with the Android keypad is it takes way too much space and makes the Elevation readouts at the top get pushed off the screen. Having those values visible while type elevations is very useful and I want to preserve it.
+  * The crosshairs are useless until under .5 of cut or fill and in fact there's no reason to display them until we get to that level. When we do display them, lets make them bigger too so we can see them. When you reach under .5 feet you aren't steering as much as just controlling cutting height
+  * At over .5 feet use just the cut/fill arrow and bigger text.
-{{:android:machinecontrol:setelevationlandscape.png?600|}} {{:android:machinecontrol:setelevationportrait.png?400|}}
+For Metric blade dimensions use 2 cm tic marks, 8 tics to a side
+Here are some example screens:
-==== Updated Cut/Fill Main Screen View (Feb 2015) ====
+=== Cut or Fill Exceeds .5 feet (16 cm) ===
-I haven't been satisfied with the look of the cut/fill numbers, arrows and crosshairs because they're too small and too cramped on this aspect ratio screen. Here's some refinements.
+{{:android:machinecontrol:gradehud_great_half_foot_landscape.png?400|}}   {{:android:machinecontrol:gradehud_great_half_foot_portrait.png?300|}}
-  * The crosshairs are useless until under .5 of cut or fill and in fact there's no reason to display them until we get to that level. When we do display them, lets make them bigger too so we can see them.
-  * At over .5 feet use just the cut/fill arrow and bigger text.
-Pictures to follow.
+=== Cut or Fill less than .5 feet (16 cm) ===
+{{:android:machinecontrol:gradehud_less_half_foot_landscape.png?400|}}
+{{:android:machinecontrol:gradehud_less_half_foot_portrait.png?300|}}
+===== SmartGrade View Slider screen (March 2015) =====
+Change the old View Screen out to the improved, SmartPlan layer style View Screen
@@ Line 135: / Line 145: @@
 **Grade Point**
 Controls which side the measure point is done from as well as allowing for multiple grade point offsets to be specified. Effectively the grade offset needs to store three values instead of one. Each value reflects the grade offset for the three grade point settings. The user has an onscreen control that shifts the grade point without entering the Settings.
+====== Story 2 ======
+  * Rework Set Elevation Screen
+  * Record points - Save capability
+  * Tracking - ability to upload tracks (like simpletrack,smarttrack)
+  * Direction based on RTK and autonomous Tablet GPS (research feasibility)
+  * Alignment Capability when none present
+==== Updated Set Elevation Dialog (Feb 2015)====
+The functionality of Set Elevation is working fine but continued usage of Bill's version of it has me making modifications. Bill's version of the dialog showing the actual position while doing a set elevation was an improvement over mine that took the entire screen. After using it a while and discovering that portrait orientation is actually a nice alternative to landscape I'd like to modify the dialog to look like those below. I've done the following in these screens:
+  * Widened the Landscape pane slightly for better spacing
+  * Simplified the instruction wording and moved the controls to be more inline with the instructions.
+  * Used a slightly smaller version of the keypad used in the Blade Preferences rather than the default Android keypad. The problem with the Android keypad is it takes way too much space and makes the Elevation readouts at the top get pushed off the screen. Having those values visible while type elevations is very useful and I want to preserve it.
+{{:android:machinecontrol:setelevationlandscape.png?600|}} {{:android:machinecontrol:setelevationportrait.png?400|}}
+===== Recording Points =====
+The interface for recording points is relatively simple but the implication of recording points requires more functionality like saving, etc.
+  * Use the Streaming button button from SmartGrade Grade mode as the method of shooting points
+  * Add Save to the menu along with the Save Screen. Look for the dirty flag when exiting to ensure saving.
+  * Allow tapping the View Layer name/numbers on the top info bar to switch layers.
+  * Change the View screens over to the new SmartGrade view menu
+===== Tracking =====
+Previous Machine control system versions late in their life added tracking to their capabilities. The difference here is that we wish to use the tablet's autonomous GPS for the tracks instead of the RTK device. Unfortunately RTK is somewhat notorious for not necessarily tracking well due to a different optimization
+===== Direction =====
+Compasses have proven to be unreliable in machines or with high vibration. Determining the direction of the machine is useful however.
+===== SmartGrade View Screen Port =====
+The SmartGrade View screen may be ported to SmartBlade before Story 2. This matches the SmartGrade implementation.

AGTEK R & D Wiki

User Tools

Site Tools

Differences

Page Tools