We recently upgraded our TSC2 controllers to Trimble Access from Trimble Survey Controller. We are finding that simple functions/commands and the touch screen are running much slower, especially in the cold weather. The cold had not been a problem until Access was installed. Just getting a code from our default code list takes several seconds from the time you hit the first letter key until that part of the list shows up. I am thinking the TSC2's memory may be getting overloaded with the new software.
Is anyone else having this issue or found a resolution? Our dealer is checking into it but we seem to be the only ones having these problems.
We all run Access and I haven't heard of a similar issue, we work at and below freezing on a regular basis.
Are you running more than one function at the same time through the MENU softkey? I've had them bog down regularly when I try to run Stakeout Point and Stakeout Line at the same time.
Have you run a recent update with TAIM (Trimble Access Installation Manager)?
EDIT: Do you still have Survey Controller installed? Could that be taking up too much "program" memory?
Hi,
how long is your code list?
I never liked to use a feature library for reasons of speed ... but I only tested it years ago on our TSCe running Trimble Survey Controller.
Chr.
Good to know!
We just updated to Survey Pro 5.1.1 and
our TSC2 now CRAWLS along....
I even unloaded all the job files, purged all the other
windows app temp files.....
I was thinking of "upgrading" to ACCESS when we
get our GPS system and TSC3 purchase completed....
Now, I wonder if I shoulding stick with Survey Pro MAX
and go back a couple of "Faster" versions....
I never thought "better" would mean slower?
Trimble Access on the TSC3 works exceptionally well, probably a little faster than Survey Controller on our TSC2. We also have Access installed on a TSC2 and it does run slower but that controller has a lot of data on it. Our issue with Access on the TSC2 is that Access will freeze up and had the bluetooth completely stop working. After a soft boot, Access runs fine on the TSC2, but Access on the TSC3 is great.
Brad Luken, LS
AZ, CA, NV & OR
Survey Controller is entirely gone.
I think part of the problem is they were running multiple functions at the same time like Stakeout Point and Stakeout Line as you noted. I don't think the TSC2 has the guts to do that with Access.
I think our other problem with the code list stems from having the wrong file type. The code list has been copied over and over through the years and the file types have changed. This list was compiled long before I came to work here and was originally developed for the SDR33(.fal) and has not been updated to .fcl for TGO and now .fxl for Access. It must be similar enough to recognize the file but not read it efficiently. I'm trying to figure out how to convert this old list from .fal to .fxl but not having any luck so far. I'm hoping that is answer to the slow code list issue.
The list is only about 160 codes. I don't like the code list either and never used one when I was in the field but it was in place when I came to work here 2 years ago. I think it was/is a way to keep consistency between multiple crews. We need to get into line coding and that will require that consistency but think we can do it by simplifying the codes.
Access runs fine on our TSC2s but I don't know the spec.s.
Caltrans gave them to us.
I run Trimble Access on a TCU, it's a little slower but not bad by any means.
I don't have a code list yet but there was a couple on there. I wish it would remember a code when I type it in like TDS did for 20 years.
IMHO the tsc2 does not have enough processing power to run access efficiently. It will work as long as you don't have a bunch of routines running at once. It works great on the tsc3. I wonder if you can add ram to the tsc2?
