Remote BM

[Rich]

We're having a problem with the Remote BM function and are curious if
anyone else experiencing this issue?

I've seen this issue whether using a known (coordinated) BM or unknown
(one just input as a reference elevation).

The first attempt at shooting the BM (F1/F2) returns a result that
doesn't make any sense. Immedeately trying it again returns the right
answer, but now that is being averaged with something wrong and is, of
course, wrong.

Now, it appears the review of results was designed with the intent of
being able to check certain readings off (N) and leaving others on
(Y). However existing the review turns them all back on and they are
all used in the calculation [Is this a bug?].

Since I can't turn off the wrong reading, I have to back out and read
the BM again. Now, 99.9% or all of the time, these later readings seem
to be correct. But why are we getting such ridiculous answers the
first time we try?

I can't seem to exactly predict when or to what extent the error
occurs. It's happened whether setting up the first time on a job, on
points traversed to, keyed in, etc...

The first few times it happened I blamed myself for possibly not
properly inetering HIs, HTs, etc. I'm always paranoid that if you
don't move off a field or 'Enter' the values won't "take". But we've
been able to make it happen a couple times in the office and we're
carefully double checking each input and making sure it is set.

Our current procedure is going to be to shoot the BM at least twice,
since it always appears correct the 2nd time.

Any similar experience would be appreciated so I don't feel like it's
only us. Note: Happenign on 2 Allegros and 2 Guns.

Take Care,

Rich

[Rich]

Well, it's not just me ... a local friend says "That thing doesn't
work!" He has 2 Allegros and 2 Leicas, like me and he gets the same
errors. However, as soon as he could tell it didn't work he didn't
play with it further. My work around is kinda a pain; telling my
chiefs to try it over again until it looks like it works.

Is this a known bug with the Remote BM routine across the board? This
is a routine we used to use very often with TDS, I'd sure like to know
what is going on.

If someone else with the same equip can tell me they are or are
nothaving the issue below, or are or are not with different equip it
would probably help in working through this issue with Carlson
support. <Please post>

I think I could easily demonstrate the error to a local rep. Maybe if
I repeated the error the Raw file would be helpful?

On Sun, 06 Aug 2006 20:47:20 -0700, Rich <rmaher@kdmmeridian.com>
wrote:

We're having a problem with the Remote BM function and are curious if
anyone else experiencing this issue?

I've seen this issue whether using a known (coordinated) BM or unknown
(one just input as a reference elevation).

The first attempt at shooting the BM (F1/F2) returns a result that
doesn't make any sense. Immedeately trying it again returns the right
answer, but now that is being averaged with something wrong and is, of
course, wrong.

Now, it appears the review of results was designed with the intent of
being able to check certain readings off (N) and leaving others on
(Y). However existing the review turns them all back on and they are
all used in the calculation [Is this a bug?].

Since I can't turn off the wrong reading, I have to back out and read
the BM again. Now, 99.9% or all of the time, these later readings seem
to be correct. But why are we getting such ridiculous answers the
first time we try?

I can't seem to exactly predict when or to what extent the error
occurs. It's happened whether setting up the first time on a job, on
points traversed to, keyed in, etc...

The first few times it happened I blamed myself for possibly not
properly inetering HIs, HTs, etc. I'm always paranoid that if you
don't move off a field or 'Enter' the values won't "take". But we've
been able to make it happen a couple times in the office and we're
carefully double checking each input and making sure it is set.

Our current procedure is going to be to shoot the BM at least twice,
since it always appears correct the 2nd time.

Any similar experience would be appreciated so I don't feel like it's
only us. Note: Happenign on 2 Allegros and 2 Guns.

Take Care,

Rich

[Rich]

Confirmed as a bug by Carlson ... I'm surprised no one chimed in; low
traffic I suppose.


On Tue, 08 Aug 2006 19:17:58 -0700, Rich <rmaher@kdmmeridian.com>
wrote:

Well, it's not just me ... a local friend says "That thing doesn't
work!" He has 2 Allegros and 2 Leicas, like me and he gets the same
errors. However, as soon as he could tell it didn't work he didn't
play with it further. My work around is kinda a pain; telling my
chiefs to try it over again until it looks like it works.

Is this a known bug with the Remote BM routine across the board? This
is a routine we used to use very often with TDS, I'd sure like to know
what is going on.

If someone else with the same equip can tell me they are or are
nothaving the issue below, or are or are not with different equip it
would probably help in working through this issue with Carlson
support. <Please post

I think I could easily demonstrate the error to a local rep. Maybe if
I repeated the error the Raw file would be helpful?

On Sun, 06 Aug 2006 20:47:20 -0700, Rich <rmaher@kdmmeridian.com
wrote:

We're having a problem with the Remote BM function and are curious if
anyone else experiencing this issue?

I've seen this issue whether using a known (coordinated) BM or unknown
(one just input as a reference elevation).

The first attempt at shooting the BM (F1/F2) returns a result that
doesn't make any sense. Immedeately trying it again returns the right
answer, but now that is being averaged with something wrong and is, of
course, wrong.

Now, it appears the review of results was designed with the intent of
being able to check certain readings off (N) and leaving others on
(Y). However existing the review turns them all back on and they are
all used in the calculation [Is this a bug?].

Since I can't turn off the wrong reading, I have to back out and read
the BM again. Now, 99.9% or all of the time, these later readings seem
to be correct. But why are we getting such ridiculous answers the
first time we try?

I can't seem to exactly predict when or to what extent the error
occurs. It's happened whether setting up the first time on a job, on
points traversed to, keyed in, etc...

The first few times it happened I blamed myself for possibly not
properly inetering HIs, HTs, etc. I'm always paranoid that if you
don't move off a field or 'Enter' the values won't "take". But we've
been able to make it happen a couple times in the office and we're
carefully double checking each input and making sure it is set.

Our current procedure is going to be to shoot the BM at least twice,
since it always appears correct the 2nd time.

Any similar experience would be appreciated so I don't feel like it's
only us. Note: Happenign on 2 Allegros and 2 Guns.

Take Care,

Rich