Survey Questions

[Jim Frame]

I used the app early last night to execute a static session with my T2. I wanted to run the session overnight, but was limited to the session lengths shown in the dropdown menu, which has a max of 10 hours. Is this restriction necessary? Couldn't the length be set by the user, including an option to run until stopped or power failure?

Also, I noticed that once I was out of bluetooth range (as indicated by a red light on the receiver and, I think, something red on the Android display), the app continued to update the stored epoch count. If I'm correct about the out-of-range condition, wouldn't this display be misleading, e.g. couldn't the receiver run out of power or have its sky coverage compromised and thus not actually be recording despite the display's indication otherwise?

 

[Kelly Bellis]

I used the app early last night to execute a static session with my T2. I wanted to run the session overnight, but was limited to the session lengths shown in the dropdown menu, which has a max of 10 hours. Is this restriction necessary? Couldn't the length be set by the user, including an option to run until stopped or power failure?

Also, I noticed that once I was out of bluetooth range (as indicated by a red light on the receiver and, I think, something red on the Android display), the app continued to update the stored epoch count. If I'm correct about the out-of-range condition, wouldn't this display be misleading, e.g. couldn't the receiver run out of power or have its sky coverage compromised and thus not actually be recording despite the display's indication otherwise?

Hi Jim - Good request on the pull down regarding session length. Maybe we can ask Yuri to add INFINITE. Such a choice would probably be my default, though I appreciate the timer too.

As for the other Bluetooth range issue, and Yuri, please correct me if I'm wrong, but I think we're just seeing the clock ticking down with the associated/derived epoch count. Maybe an idea to implement when the Bluetooth connection goes south, the epoch counter changes message to Bluetooth connection lost; alternatively, qualify; i.e., Calculated epochs collected... or both, change and qualify.

 

[Jim Frame]

Related question: when the BT connection is broken (as in, I started the receiver at my office via the app, then left for the field) and then reestablished later (as in, I get back from the field, exit the status screen and reconnect), how do I get back to it to control the session? I got to the screen shown below, which appeared to be providing status updates at the top, but I was unable to get back to the screen from which I could stop the session. Pushing the Survey button didn't work, it appeared to be wanting to start a new session.

 

[Kelly Bellis]

Good question - and I'm not sure you can. Yuri will very much want to hear this.

 

[Yuri Noyanov]

Dear Kelly, Jim,
thank you for the real testing. I've already added more occupation time (up to 48 hours) and I'm going to enable user defined time as well.

About Bluetooth break. Internal changes are required to automatically restore connection. I must be done. But it take some time.
The software should restore the session if login is on. But may be this is issue. It should be fixed.
For RTK new session starts. And you are right - this is a problem.

 

[Matt Johnson]

Yuri, I think I've mentioned this for the iOS app before but how about adding a "Until Stopped" option for the occupation time?

 

[Yuri Noyanov]

Yes, very reasonable note. I will add both to iOS and Android app.

 

[Kelly Bellis]

Yes, very reasonable note. I will add both to iOS and Android app.

Thanks Yuri!

 

[Yuri Noyanov]

I did this for Android version 1.2.5
And I'm going to add this for iOS.

 

[Kelly Bellis]

How can I get 1.2.5?