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.
N10,000, E7,000, Z100.00 PLS - MO, KS, CO, MN, KY