Thomas Campbell
New Member
Hello, newbie TRIUMPH-LS user here and we are working to get our unit setup for our first use...
We will be using to collect asbuilt information for Golf Course Irrigation systems. We plan to have separate Codes set up for various items such as Sprinklers, Valves, Wire Spices, etc. With Code Attributes to further define the various sub types of each item. IE under Valve > a Type Attribute with selections of Gate, Ball, Drain, etc.
We may bounce back and forth from Sprinkler to Valve to several sprinklers and then back to a valve, etc. This issue we are finding is that the Attribute value always reverts back to a default entry. It would be the most beneficial to use for it to automatically use the entry from the last point collected for that particular Code.
We will have a few dozen Sprinkler types to choose from, but will typically on have a few types used on a particular project within a given area.
Example collection...
Sprinkler > Type: 750
Sprinkler > Type: 730
Valve > Type: Gate
Sprinkler > Type: 750
Sprinkler > Type: 750
Sprinkler > Type: 730
Valve > Type: Gate
Sprinkler > Type: 750
WireSplice > Type: 120v
etc.
But if the default sprinkler type is a 700, we have to drill down into the attribute and select the "750" anytime we collect a different code, even when that is the sprinkler used 75% of the time.
This is a somewhat simple example, but just trying to relate what we are tying to do.
Is there a setting that will allow that, (the last attribute used to be the default). If not can that be put on a wish list?
We have used Trimble equipment for years so we are in a sense trying to emulate the process we used in survey controller. If anyone has any other thought, any input would be appreciated!!
Thanks
We will be using to collect asbuilt information for Golf Course Irrigation systems. We plan to have separate Codes set up for various items such as Sprinklers, Valves, Wire Spices, etc. With Code Attributes to further define the various sub types of each item. IE under Valve > a Type Attribute with selections of Gate, Ball, Drain, etc.
We may bounce back and forth from Sprinkler to Valve to several sprinklers and then back to a valve, etc. This issue we are finding is that the Attribute value always reverts back to a default entry. It would be the most beneficial to use for it to automatically use the entry from the last point collected for that particular Code.
We will have a few dozen Sprinkler types to choose from, but will typically on have a few types used on a particular project within a given area.
Example collection...
Sprinkler > Type: 750
Sprinkler > Type: 730
Valve > Type: Gate
Sprinkler > Type: 750
Sprinkler > Type: 750
Sprinkler > Type: 730
Valve > Type: Gate
Sprinkler > Type: 750
WireSplice > Type: 120v
etc.
But if the default sprinkler type is a 700, we have to drill down into the attribute and select the "750" anytime we collect a different code, even when that is the sprinkler used 75% of the time.
This is a somewhat simple example, but just trying to relate what we are tying to do.
Is there a setting that will allow that, (the last attribute used to be the default). If not can that be put on a wish list?
We have used Trimble equipment for years so we are in a sense trying to emulate the process we used in survey controller. If anyone has any other thought, any input would be appreciated!!
Thanks
