FYI: The tilt feature is only applicable to RTK measurements. The tilt feature does not work with post-processed (PPK) shots. Also, if you shoot a point as an Observed Control Point, it will turn the tilt feature off, so make sure you are plumb.
The DOS copy command using /b will copy files into one new file. Files will be merged in the order they are listed in binary format.
copy /b file1 file2 file3 newfile
This won't solve the time gap issue though. This has worked with T files that didn't have large time gaps.
@dave-karoly yeah if I ever get to catch my breath i will be making some phone calls as to what is going on for sure. We have a r10 and r12 for one crew. Then r12 and r12i for another crew. I am working on the next crews purchase as well. We have a new office and having to get everything so i am busier than a 1 legged man in a tator sack race. If I ever get more productive with civil3d it will solve about half of my time issues. But some stuff i know i want to do i am searching all mighty google and email and asking co workers. Usually ends up being so darn simple i want to kick myself. But when ya don’t know you just out of luck. If i get it figured out i will let you know. Hopefully it’s something i am doing a setting and not a bug in the firmware.
@dave-karoly what epoch rate were you collecting at. Might not be a big issue almost like a cycle slip. I am going to have to try this dos thing and see if it works myself. Also why is the Trimble software firmware causing it to stop and end a session is my biggest question. I want it to end a session when i say for it to. Must be a bug or something i am doing wrong. Lol. You are using logging while doing rtk. I wonder if infill will do the same. I always liked the logging when doing other fast static moves because I usually plan for my base to be the center of a pinwheel.
I use 5 second epochs. I never do infill. If I can’t pick up the radio then I do a Faststatic session. Most of my work is boundary. If I’m doing Topo the base is nearby.
5 second recording rate is too often for a 2 or 4 hour session. 1 or 5 seconds is needed only if your session is very short. 4 hour session might be 30 second rate. Somewhere Trimble has a recommend rate based on session length.
5 seconds and 4 constellations, with all the signals and satellites Beidou had, might be a very large file.
you can zip multiple raw files if not much time gap between them, if you use Trimble RTX post processing website fir positioning.
I used to worry more about shorter intervals back when the receivers were short on memory, but nowadays with the amount of storage on the 10s and 12s, I'd rather be able to run short static occupations on the fly rather than have to run back to the base to modify the logging rate. Also if I decide to run PPK I want that base logging at 1Hz. It's really handy to be able to resolve both long and short occupations when needed.
If every single occupation is going to be 2+ hours, such as for a campaign-style network, sure, we'll use 10-second or greater intervals. But that's pretty rare unless we're doing a bluebook-type project.
RTX is great. OPUS might edge it out once it goes full-constellation. I still like to process everything myself and just use the web tools for a check.
I'll fire up a few R12i's on Monday. Both of mine are moved to the latest 6.20 FW. I never saw multiple file generation with the previous FW, this latest one among other things was designed to fix the bloated files. See community forum.
I ran several tests using and R12i as base with RTK&Infill, and RTK. Using latest FW, latest Access on a TSC5. Pushed over the UTC top of hour, and all T04 files remained intact (did not observe split files).
@rover83 I like to use the 1 second for same reason. If i am in a pickle at 1 second at base i can make the call based on geometry and sv#’s at the rover for a quick static session or fast static. Even a ppk. Depending on what i am doing. I tell people if you are setting up the base just set it to log if you don’t need the data fine delete it clear the receiver but if you do need it then hey radio dies you break an antenna you have a base logging and can get those last few points and not have to drive 2 hours one way back the next day. I practiced this even years ago. Saved my rump a few times.
@gisjoel did you try the rtk and logging style by chance. I am going to check our firmware version. We just got the receivers and well i probably assumed they were all upgraded correctly but who knows. Unfortunately my crew is out of town with the kit so it will be next week.
@gisjoel nice. I will get the firmware checked next week and and try again. Thank you.
@dave-karoly I have confirmed this issue of random (splitting an otherwise continuous T04 file) on the base with an RTK survey style is an issue resolved with the 6.2 FW update. I also require RTK&Logging on all my base receivers, so that method is used on the base, and RTK on Rover. Like a previous poster, another survey style I've created to handle loss of radio is simply a copy of RTK&Logging with the Rover set to PPK Kinematic (No Tilt), allowing our users to end survey on the Rover and engage another Style I call PPK on Rover. I can continue to work with no Tilt. When returning to base, we then switch back to RTK survey style on Rover to check back into check shots.
My opinion: This gyration on an R12i as rover was previously handled with one survey style with RTK&Infill on Rover, but not possible since Trimble sees this as a low priority to change (allowing No Tilt, but PPK Kinematic with RTK&Infill) They think 10% of their users ever loose lock anymore and I'm guessing so few of us ever use traditional BASE/Rover single base (Hey, I'm an Alaskan).
@dave-karoly I have confirmed this issue of random (splitting an otherwise continuous T04 file) on the base with an RTK survey style is an issue resolved with the 6.2 FW update. I also require RTK&Logging on all my base receivers, so that method is used on the base, and RTK on Rover. Like a previous poster, another survey style I've created to handle loss of radio is simply a copy of RTK&Logging with the Rover set to PPK Kinematic (No Tilt), allowing our users to end survey on the Rover and engage another Style I call PPK on Rover. I can continue to work with no Tilt. When returning to base, we then switch back to RTK survey style on Rover to check back into check shots.
My opinion: This gyration on an R12i as rover was previously handled with one survey style with RTK&Infill on Rover, but not possible since Trimble sees this as a low priority to change (allowing No Tilt, but PPK Kinematic with RTK&Infill) They think 10% of their users ever loose lock anymore and I'm guessing so few of us ever use traditional BASE/Rover single base (Hey, I'm an Alaskan).
all we use is base/rover because most of our work is out of range of network systems.
I will update the firmware after I get back from vacation.
We've had a few R-10 model 2 do the same thing; log two files. It's just a setting. It can be fixed with the WiFi interface, or just hold down power button for factory resets. Maybe the new firmware will fix it, but the bug is common.
