Hi everybody, thank you all for the replies.
What I found and what has led to the question is that doing tests with short "baselines" below 5 meters and using a combination of Kinematic and Moving Base RTK algorithms is that if Z is shorter or longer that X the system will calculate the "baseline" as X. However when Z and X is equal the system all of a sudden calculates the "baseline" as the hypotenuse. The first image is a screen shot of the results obtained from the first rig where the horizontal distance between the antennas was 820 mm the 3rd image is a newer rig with antennas deployed at various distances from the Base. I unfortunately do not have screen shots of that data set. The units all resolved the triangles perfectly with the "baseline" the horizontal distance value. The last image is the rig I am presently testing with where the "baseline" now has become the hypotenuse.
Thank you for your interest
?ÿ
Sincerely
?ÿ
Anton
The question is really one specific to the software that he is using, I think. I identify with this, as sometimes the GNSS software is very obtuse in the outputs and jargon. It would be fine if it was consistent, but different jargon is used with different brands at times.
@bill93 Hi Bill
What I found and what has led to the question is that doing tests with short "baselines" below 5 meters and using a combination of Kinematic and Moving Base RTK algorithms is that if Z is shorter or longer that X the system will calculate the "baseline" as X. However when Z and X is equal the system all of a sudden calculates the "baseline" as the hypotenuse. The first image is a screen shot of the results obtained from the first rig where the horizontal distance between the antennas was 820 mm the 3rd image is a newer rig with antennas deployed at various distances from the Base. I unfortunately do not have screen shots of that data set. The units all resolved the triangles perfectly with the "baseline" the horizontal distance value. The last image is the rig I am presently testing with where the "baseline" now has become the hypotenuse.
Thank you for your interest
?ÿ
Sincerely
?ÿ
Anton
Hi Paul
What I found and what has led to the question is that doing tests with short "baselines" below 5 meters and using a combination of Kinematic and Moving Base RTK algorithms is that if Z is shorter or longer that X the system will calculate the "baseline" as X. However when Z and X is equal the system all of a sudden calculates the "baseline" as the hypotenuse. The first image is a screen shot of the results obtained from the first rig where the horizontal distance between the antennas was 820 mm the 3rd image is a newer rig with antennas deployed at various distances from the Base. I unfortunately do not have screen shots of that data set. The units all resolved the triangles perfectly with the "baseline" the horizontal distance value. The last image is the rig I am presently testing with where the "baseline" now has become the hypotenuse.
Thank you for your interest
?ÿ
Sincerely
?ÿ
Anton
Many years ago I worked with a complex equation that included hyperbolic trig functions as well as standard trig functions to calculate solar energy transfer based on a wide range of orientations of the surface of the collector throughout the day.?ÿ There was one specific angle where the equation "blew up" the computer.?ÿ As I recall, if an angle was effectively equal to one radian, somewhere in the calculation a value of a tiny bit greater than one could occur ahead of finding the arc cosine or arc sine.
Funny.
Sounds like what Trimble Access still does if you're collecting line work and it doesn't like the PC PT distance you're trying to shove into it from the real world.
Some things never change I suppose.
As others have mentioned, could be software specific.
You have probably checked already, but the top left corner of your report shows Pitch/Yaw/Length and then a pull-down menu arrow.?ÿ Could the difference have occurred by having inadvertently asked the software for two different answer (accidentally changing P/Y/L to some other value between the two data sessions)?
@jon-payne Hi Jon
I am specifically doing tests where the device provides guidance in pitch roll and yaw. Only pitch or roll depending on the installation. I am working on a unit that will be able to give Pitch, Roll and Yaw at the same time.
The other solution displays in the pull down menu are Lat/Lon/Height, X/Y/Z-ECEF, E/N/U-Baseline
?ÿ
Sincerely
?ÿ
Anton
?ÿ
?ÿ
