T-2 Base won't start recording when started from T-LS in Base/Rover setup

[Joe Paulin]

Hello all,

I have been using my trial equipment and have been very impressed so far. Last week, I needed to update the OAF files on both the T-2 and the T-LS in order to do more testing. Since I have updated both units, yesterday I had the equipment out and the T-2 would not start recording static after I prompted a 30 second interval and started the base from the Base/Rover Setup. In the past, there was no trouble. When this was done, the recording light on the T-2 turned red, like the memory was full, but there is only about 2MB of data on the receiver. It would start broadcasting corrections, but my RTK performance was dismal compared to prior experiences: it was slow to fix and didn't want to fix in areas where before there was no problem. My previous sessions were great: very quick fixes even with obstructions in the way. Any ideas? I am able to manually start recording by pushing the record button on the T-2.

Thanks

 

[Shawn Billings]

Please try clearing the NVRAM on the Triumph2. This can be done by holding the record button in and powering the Triumph2 on, continue holding the record button until the LED's turn Yellow, then release - this will have no affect on GNSS raw data files stored on the receiver, or through NetView.

 

[Joe Paulin]

Ok, I just did that and it didn't change anything, the red light still comes on. When I had the receiver connected to NetView updating the OAF files, I downloaded and installed the latest firmware from the website, which incidentally it already had. Maybe somehow I messed up a setting? The firmware is: 3.6.1

I have some time this morning if we could get this fixed, that would be great!

 

[Doug Carter]

Joe
I had the same problem with our beta version,We found that the problem was
How I name my projects. please try renaming your project with no spaces.

 

[Joe Paulin]

I created a new project, all one word, and still same thing, recording light is red when I start the base from Base/Rover Setup. I have noticed that if I start recording by pressing the button, the file name is log0316a for example. My static files from the past have been named differently, 3_192841 for example. Maybe this will help id what is going on.

Thanks!

 

[Joe Paulin]

Yesterday, while completing the Base/Rover Setup, the same problem mentioned above happened again: T-2 didn't start recording, red recording light on T-2 lit up like memory was full (it wasn't).
Afterwards, thinking about it and doing some testing and thinking about what Doug Carter had said:

Joe
I had the same problem with our beta version,We found that the problem was
How I name my projects. please try renaming your project with no spaces.

I found that if the BASE POINT has a space it it (example: Point 1), then I will have the problem. If the BASE POINT doesn't have a space (example: POINT1), then it will be fine. So it seems like there is a little bug to be worked out. Doug, is this what you meant? I would like to know if anyone else can confirm this, and is this an issue that's being addressed?

Thanks!

 

[Doug Carter]

Joe, Yes For now don't use spaces. I thought this was repaired in the published version. I have both beta and published on two different LS systems so ill check this out in the morning.I'll forward this information to our engineering teem
Thank You
Doug

 

[Doug Carter]

Joe,
I just tested the published version.you are correct. I was originally talking about, if you had any spaces in the project name the base didn't start recording, Now I see if you name the base with a space it also will not start base recording.
I'm sending this information to our engineers.
Thank you again
Doug

 

[Joe Paulin]

OK, great. It was frustrating for me... until I figured this out, it seemed like one day it would work just fine and another it wouldn't work. Now I know the days it didn't work, I was set up on a point where my base point had a space in it! Hopefully this is just a minor issue. Thanks for getting back to me!

 

[Doug Carter]

Joe,
It should be fixed with the next update check today
Doug