Downloading now. Fingers crossed it's an improvement from before.?ÿ
This is a big, big update. Lots of added features and bug fixes. Looks like they focused on the TSC5 and Android, which was really needed.
Like every other software update for every other program, I'm hoping the ratio of new bugs to fixed items is low.
Also hoping it is good. Usually I don't jump right on it but my last install of Access was bad. Going back to General Survey it has been very reliable software for me, but that hasn't been my recent experience.?ÿ
Can anyone confirm if they add more Leica total stations in conventional instruments ?
Can anyone confirm if they add more Leica total stations in conventional instruments ?
Release notes are on this page. Doesn't look like it at first glance.
Considering how much more complex newer instruments are, with so many proprietary features, my guess is we're only going to see the number of supported outside instruments continue to go down...
My only recent experience was the last update before this one, and it was very bad. I updated right away because I figured it can't be any worse than it was plus I can always go back to the Leica 1203 and fieldgenius again until the next update.?ÿ
@rover83?ÿ
Apart from a huge amount of UI smoothing (thanks Mike)
The big ticket items that will be of use in the real world are
- Rotate and scale a dxf - can stake the results
- BIM support - rotate pan scale 3d model - stake out direct from IFC model file (sorry TSC7 only)
- Scan and point clouds - new SX series instruments
And more...
?ÿ
?ÿ
Just released - an overview and tutorial videos for the new Access
https://geospatial.trimble.com/blog/whats-new-trimble-access-2022-00
One thing I would really like to see is the ability to communicate between the data collector and the receiver during the survey by wifi rather than just bluetooth. The bluetooth on the receiver has a limited range. The type of survey I usually do is for ground?ÿ control, sometimes the point is 50 feet or more from the road, it would definitely work using wifi but it is too far for BT.?ÿ
The new "feature" they note in the latest version of wifi for the base is nothing great as far as I am concerned. I can use my phone or my laptop (or even the TDC600) to configure the base using the WebUI. Since AT&T turned off 3G we now use an external modem at the base and connect from the R10 to the modem via wifi, and run the NTrip caster on the R10, same as before when we were using the onboard 3G modem.?ÿ
I can confirm at least one glitch is fixed, the one where it switched to passive mode anytime you used "check backsight" function.?ÿ
I think that was the only glitch that I could reproduce almost every time. I've been constantly checking my target settings to make sure it hasn't changed and so far it hasn't.?ÿ
I haven't had any of the major glitches so far since the update but some of them only showed up occasionally so hopefully I don't jinx it.?ÿ
A TSC5 involuntarily restarted 5 times last Tuesday when trying to connect to an R12i. Eventually a dialog came up about some app it wanted to kill, after that it was happy. In my opinion Android is a terrible operating system.
The R12i rover finally lived up to the hype and was happily staying in green check in a 100 foot tall conifer forest, 30SVs. I let it run in the open for 15 minutes while I ate lunch, that seemed to fulfill its needs.
No trouble at all running the S7 the next day except the video is very slow when trying to repoint it to the target. Sometimes it hangs and shows me in view even though I can see it turned 30?ø away.
I've been using Android phones for the last 12 years. It's much more stable than the last Trimble Access was. There are many good android phones made by different manufacturers with different versions of android (google, Samsung, LG, etc) and the current version of Android is 12. The tsc5 runs Android 10, though I heard they are getting updated to 11.?ÿ
@350rocketmike 2021 was the first version for android, so it was to undoubtedly be buggy
@350rocketmike 2021 was the first version for android, so it was to undoubtedly be buggy
No kidding. We were in the middle of switching to Trimble when the 5 came out. Of course management, and some of the field staff, immediately started saying that this was going to be the best thing EVER and we should get them NOW.
I hollered up and down the chain of command that it was a bad idea to get the 5s until they were at least a year down the road, since it was a new build on a totally different platform. Did they listen? Of course not.
Phone apps are pretty simple compared to field software, especially when you consider the development tools and SDK suites that have been created specifically for builds on Android. Access isn't a typical phone app.
@rover83 I remember hardly anything new was added to 2017, that was because they were basically working on programming 2018 for 2 years on Windows 10.
I never got to use those older versions of access with a robot. Just GNSS and one time with a conventional Nikon (ran very slowly with access for whatever reason). I assume it was much more stable and bug free than the current stuff but I would still hate the map screen since I count on it to navigate through the 5000+ point subdivisions for points I can use.?ÿ
the 5000+ point subdivisions for points I can use
Forget points for at least 90% of staking. Doesn't matter what the field software is, anything over 50-100 shown at a time is just going to be a mess, even with the bigger screens and touchscreen navigation.
Either split them up enough into separate files to be useful (by block, street, water vs. sewer, etc.) or just get rid of them altogether. I only use points for a few items these days. Light poles, hydrants, storm & sanitary structures, maybe a couple others. And they are all separate CSVs, as they should be because they are on separate layers in C3D and get exported as such.
Clearing limits, building exterior lines, grid lines? DXFs. All separated out of course.
Curb & gutter, road CL? Alignments with H&V profiles. Or a corridor if we're doing more advanced stuff like slope staking.
Water lines with C/F to FG? Load up a 2D DXF of the water lines plus a TTM of the FG surface.
Setting lot & block corners or CL monuments? I just load up the subdivision linework, along with the text for lots and blocks, which will show up right there in the controller for the crew to see so they can write the correct lot on the lath.
When we made the switch to yellow, several of our offices still insisted on spending hours picking points in CAD, then even more hours moving items around to make staking sheets that show each and every point. I told them they might as well trade in all their gear and go back to non-robotic TS without DCs and booking observations. They're slowly catching on, wasting more and more time and money along the way, and hamstringing the field guys to boot.
?ÿ
I'm installing 2022 today, after getting sidetracked by ALTAs and wind farm projects. Looking forward to playing around with it.
I stand corrected. It's still switching back to passive after check backsight in some jobs.?ÿ
@rover83?ÿ
Unfortunately I'm 100% field and my schedule doesn't allow any time for organizing my own uploads and sorting through them for 20-30 different subdivisions.?ÿ
What data collectors do you use that you have issues with more than 100 points shown at a time?
Fieldgenius handled it with basically zero lag, 3000+ points and a DXF. The map screen would crash after zooming in/out too many times but it happened almost as frequently with smaller jobs, didn't seem like increasing the number of points had a major effect on it. Trimble on the tsc7 lags a little bit in the bigger subdivisions but nothing like the old tsc3 dinosaurs. They can't handle a DXF with more than like 50 points in the job.?ÿ
Our office also uses microsurvey for cad and doesn't have a lot of experience with tbc yet.?ÿ
?ÿ
?ÿ
?ÿ
?ÿ
Unfortunately I'm 100% field and my schedule doesn't allow any time for organizing my own uploads and sorting through them for 20-30 different subdivisions.?ÿ
?ÿThat's something that should be handled by the office. If they have the time to manually drop thousands of points for one subdivision, that time could be used to generate one-tenth of those points plus a handful of DXFs, RXLs, TTMs, etc. for three subdivisions. Unless they just want to stay inefficient in order to bill more hours, it's a no-brainer to optimize workflows for both office and field.
What data collectors do you use that you have issues with more than 100 points shown at a time?
Fieldgenius handled it with basically zero lag, 3000+ points and a DXF. The map screen would crash after zooming in/out too many times but it happened almost as frequently with smaller jobs, didn't seem like increasing the number of points had a major effect on it. Trimble on the tsc7 lags a little bit in the bigger subdivisions but nothing like the old tsc3 dinosaurs. They can't handle a DXF with more than like 50 points in the job.?ÿ
?ÿI wasn't referring to crashing software - newer DCs can certainly handle it - but the fact that displaying tons of points makes for a messy screen and can be difficult to parse when targeting a particular stakeout routine. Making use of different CSVs and DXFs, plus the different layers in the DXF, helps get the operator a clean screen that is easier to work with.
Our office also uses microsurvey for cad and doesn't have a lot of experience with tbc yet.?ÿ
?ÿThat shouldn't be a problem. DXFs have been around forever, same with LandXML for surfaces and alignments, and Microsurvey can handle both. DXFs can go straight to Access, and surfaces and alignments can either go straight to Access or get dropped into TBC and immediately exported as RXLs or TTMs. Takes about 5-10 minutes to get the hang of it in TBC.
It blows my mind how many firms/offices (including my employer in this) refuse to optimize workflow for the gear and software being used. It's the equivalent of a retail location not taking checks or credit/debit, and insisting on cash. Sure, it's technically going to "work" but it's going to cause a lot of unnecessary annoyance and lose them lots of money.