Message interpretation

Mark Wheeler

Active Member
Recently, when using LS with T2 base, I have been getting the message "BY Command - No base time tag". To deal with this I stop and start the RTN. Generally this seems to refresh the connection and it fixes. This has just started happening. What does this message mean and what should I do to deal with it. I use two MIFI's for communication.

Mark
 

Michael Stazhkov

Developer
JAVAD GNSS
Recently, when using LS with T2 base, I have been getting the message "BY Command - No base time tag". To deal with this I stop and start the RTN. Generally this seems to refresh the connection and it fixes. This has just started happening. What does this message mean and what should I do to deal with it. I use two MIFI's for communication.
Sorry for the delay. It means RTK can't find base measurements in his buffer. It could be a problem in communication. Or it could be a very big delay in data so the rover can't find base measurements for the rover measurements (with the same time tag).
To investigate the problem we need recorded data. Base measurements (if exist) will be wrapped in the rover file. You can create a new project, start point recording, wait a minute and accept the point manually. Then send the project to support. At least we can understand if rover is getting correction stream from the base or not.
 

Mark Wheeler

Active Member
Michael, I sent project file LS 479 test to support. This afternoon the T2 & LS (2 Static MIFI'S for communication) worked uninterupted for 15 minutes, after that I spent 70% of the time tying to get past the above message by stopping & starting the RTN. I then finished that section of location with state rtn. Later reconnected to T2 and it worked normally.
 

Mark Wheeler

Active Member
Same issue today. Started out fine for about a half hour. The message popped up from time to time, but resolved itself. After a half hour, the majority of the time was spent trying to make the connection. Again I punted and used the rtn.
 

Adam

Well-Known Member
5PLS
Same issue today. Started out fine for about a half hour. The message popped up from time to time, but resolved itself. After a half hour, the majority of the time was spent trying to make the connection. Again I punted and used the rtn.
Where you using the T2 as a base when you started out yesterday but it worked fine the day before? It is odd. How is the internet/wifi quality? Do you have an unlimited plan? It sounds like some kind of throttling on the usage because it works fine for a while. If it was summer time jetpack heat could be the problem, I've seen that before. I know its cold right now. Do you have the jetpacks enclosed where they could get warm? If you have time you should set them up where you know the internet qaulity is great and monitor it for a while. It is difficult to troubleshoot internet issues in the field.
 

Mark Wheeler

Active Member
Adam, Some more detail: The past 3 days I have done wetland location, mostly in bare leaves deciduous areas. In the past under similar conditions the T2/LS would pick the shots up fairly well. Usually I would start the location in float, by the time I typed in the flag number and hung a witness flag it generally was fixed and off to the next point. Each of the 3 days, one at a site 30 miles away, I would start out with in good shape, working away from the base as usual. 10-20 minutes in the "No-Time Tag" message would pop up and not resolve on it's on. At this point the Latency would be 14.2 sec and then go to 600 sec, etc. At first restarting the RTN might resolve it to get a shot or two, but then it bounces to no time tag. This has not been my previous experience. After a half hour of this I switch to the RTN, which is typically significantly slower in getting results. Sometimes after all this I will walk back toward the base, change setups and reconnect. Walk into the woods and get another shot or two and repeat the cycle. MIFI's are definitely not overheating in this weather. They are both static. I tried clearing the T2 NVRAM. I am not familiar with deleting files from the T2. Is it possible to do it from the LS under Base/Rover setup? Any troubleshooting is welcome.
 
Top